Skip to content

fix([issue-3182]): dispatch output hooks from recovery paths - #3197

Merged
atomantic merged 5 commits into
mainfrom
claim/issue-3182
Jul 29, 2026
Merged

fix([issue-3182]): dispatch output hooks from recovery paths#3197
atomantic merged 5 commits into
mainfrom
claim/issue-3182

Conversation

@atomantic

Copy link
Copy Markdown
Owner

Summary

  • route orphan cleanup and post-restart completion through the shared output-hook dispatcher
  • persist an exactly-once marker and serialize same-agent dispatch races
  • keep recovery payloads null while preserving the existing timeout bound and early-termination behavior

Test plan

  • npm test -- --run services/agentFinalization.outputHooks.test.js services/agentFinalization.successCriteria.test.js services/agentManagement.test.js services/agentLifecycle.test.js services/agentImportCycles.test.js
  • full non-DB suite attempted with MEMORY_BACKEND=file; unrelated installState worktree assertion failed before the remaining suite completed

Closes #3182

@atomantic
atomantic merged commit c494cd2 into main Jul 29, 2026
@atomantic
atomantic deleted the claim/issue-3182 branch July 29, 2026 00:21
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.

Output hooks never run when an agent completes outside finalizeAgent, losing the quota-burn dispatch record

1 participant