Skip to content

test(fusion): pin the spend cap reason when the cap also stops the turn - #1190

Closed
sosidudku1 wants to merge 1 commit into
fix/fusion-worker-stop-and-swapfrom
fix/ato-1420-worker-budget-stop-test
Closed

sosidudku1 wants to merge 1 commit into
fix/fusion-worker-stop-and-swapfrom
fix/ato-1420-worker-budget-stop-test

Conversation

@sosidudku1

@sosidudku1 sosidudku1 commented Nov 12, 2026 •

Copy link
Copy Markdown
Collaborator

Linear: ATO-1420 (item 2). Stacked on #1139.

#1139 fixed the order "spend cap first, then the stop signal" in worker-runner.ts, but no test pinned it. This adds one test in src/tools/fusion/worker-runner.test.ts: the first worker reaches the spend cap and aborts the turn's signal (as stopForBudget does). The tasks that never started must say not started: the spend cap for this turn is reached, not "the turn was stopped". If the signal is read first again, the test fails.

Test only, no product change.

Checked on the second Mac on 12.11.2026 in the combined run with the other open PRs: build, lint, test types, vitest, desktop unit tests, desktop smoke and live smoke all green.

…ignal

The pool asks the cap before the stop signal. A cap that aborts the
same signal must still leave rows naming the cap, not a stop.
@sosidudku1

Copy link
Copy Markdown
Collaborator Author

Closing: this code is already merged into rel/xp-build via #1257 (and into main via #1256 where it applies). GitHub did not mark it merged because the PR targets another feature branch.

@sosidudku1 sosidudku1 closed this Nov 12, 2026
sheepdogs pushed a commit to sheepdogs/atomic-agent that referenced this pull request Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant