Repository navigation
feat: add opt-in durable ChatGPT peer swarm - #61
Merged
Merged
Conversation
This was referenced Sep 8, 2026
Closed
James3014
changed the base branch from
codex/dispatch-catalog-reliability-20260909-v2
to
main
September 10, 2026 22:56
This was referenced Sep 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an opt-in ChatGPT peer Swarm with durable task ownership, replay/conflict checks and ten MCP tools. Worker carriers cannot submit another worker's task, and ambiguous work requires reconciliation after restart. An exclusive SQLite runtime owner prevents two enabled servers from independently recovering or operating the same Swarm state.
Production registration follows the actual lifecycle and is checked against MCP tools/list schemas. Drain rejects new work while preserving permitted terminal results. Initialization failures release ownership so the next server can recover. The feature remains disabled by default and adds database migrations 13 and 14.
Related to #46, #47 and #48. Depends on the dispatch/catalog reliability PR. Source tests do not establish the two-real-ChatGPT-conversation canary in #49; durable conversation rollover in #51 remains a later gate. This PR adds no coding-agent mutation grants, model selection policy, or automatic scaling.
The combined Git tree is byte-for-byte identical to verified candidate 09402a40 (tree 8789318b18c6de38f599560f3ae3942599283908). Its full npm test baseline, final 38 server tests, additional catalog/session checks, typecheck and build passed. Independent process-race, dead-owner recovery and token-fencing checks also passed. This exact split head still requires remote CI and native runtime acceptance.
Current revision verification
Current head
68760cd42ce772dfc2eeb5d3fe9df824a37a209dincludes accepted main710e5f1afb3dbb19042c17c492a2f5cb0881f10d. Drain permits existing-task completion with an exact-current-task fence, and failed server initialization closes acquired stores while preserving the original error and existing runtime owner. Mac verification on this exact revision passed 125 affected tests, typecheck and build. The archive build has an unknown build identity; this proves compilation, not installed runtime identity. Independent cumulative source review accepted the cleanup correction with 2 focused tests and no remaining source blocker. CI run 34540102873 is in progress on all three platforms. Earlier verification above is historical and is not substituted for this revision. Native conversation provenance, live grants, two-real-ChatGPT acceptance and deployment remain separate, unverified outcomes.