fusion/.changeset/harden-semaphore-boundary.md at a67feafccbd7b4ee6594e6ce5e4700887ed7daea

Files

gsxdsm 7b8960f3e9 feat(FN-1496): harden semaphore lane-vs-utility boundary

- Add explicit boundary comments to serve.ts and dashboard.ts clarifying semaphore lane usage
- Add regression tests for semaphore lane-vs-utility boundary in serve.test.ts and dashboard.test.ts
- Add changeset for @gsxdsm/fusion patch release

2026-04-09 21:52:07 -07:00

971 B

Raw Blame History

@gsxdsm/fusion

@gsxdsm/fusion
patch

Harden CLI semaphore boundaries to task lanes only

This change makes the concurrency semaphore boundary explicit in the CLI bootstrap code (runDashboard and runServe):

Task-lane components (semaphore-governed):

TriageProcessor — specification agents
TaskExecutor — execution agents
Scheduler — task coordination
onMerge — merge execution (via semaphore.run())

Utility workflows (NOT semaphore-governed):

HeartbeatMonitor — lightweight heartbeat sessions
HeartbeatTriggerScheduler — trigger scheduling
CronRunner (via createAiPromptExecutor) — scheduled automation
Model sync, auth setup, plugin loading — bootstrap workflows

This boundary prevents utility workflows from being blocked by task-lane saturation and ensures utility work is always available regardless of maxConcurrent settings.

Added regression tests to lock this boundary and prevent future regressions.

971 B Raw Blame History

971 B

Raw Blame History