Save → Green: the SageFS test feedback pipeline

Save → Green: the SageFS test feedback pipeline A data-flow diagram generated by Archify. 01 / Trigger 02 / Engine 03 / Test pipeline 04 / Propagation 05 / Clients Editor · save file · 01 / Trigger Editor save file Watcher · daemon-side · 02 / Engine Watcher daemon-side Tree-sitter · detect tests · 03 / Test pipeline · broken code OK Tree-sitter detect tests broken code OK FCS Analyze · dep graph · 03 / Test pipeline · affected tests FCS Analyze dep graph affected tests Test Exec · run affected · 03 / Test pipeline · frameworks Test Exec run affected frameworks SSE Events · SessionId-tagged · 04 / Propagation SSE Events SessionId-tagged Gutter · pass / fail / none · 05 / Clients Gutter pass / fail / none save changed found affected results events Legend primary data data flow

Three-speed pipeline

  • • Tree-sitter detects test attributes even in broken code (~50ms design goal)
  • • F# Compiler Service type-checks and builds the dependency graph (~350ms)
  • • Only affected tests execute (~500ms); results stream via SSE

Client rendering

  • • Editors paint pass/fail/no-coverage gutter signs from file_annotations events
  • • Events are SessionId-tagged so multi-session setups stay isolated
  • • Timings are design goals; the engine README cites 300–800ms typical today