Repository navigation
fix: bind dispatch to fresh catalogs and verified provider results - #60
Merged
Merged
Conversation
added 30 commits
September 9, 2026 06:51
This was referenced Sep 8, 2026
Closed
Owner
Author
|
Refreshing pull_request event after enabling fork Actions; no code/head change. |
Owner
Author
|
Refreshing pull_request event after fork-level Actions permission reset; no code/head change. |
This was referenced Sep 10, 2026
This was referenced Oct 8, 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
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.
Direct provider/model requests were advertised but rejected by the profile-only backend, catalog observations could disagree with dispatch validation, and provider output could be attributed to the wrong turn. This change carries exact selection and catalog evidence through preflight, worker startup and continuation, refreshes OpenCode and Cline catalogs, requires current-turn results, and freezes elapsed time after termination.
Cline ACP now configures and reads back the session's actual provider/model because the installed CLI accepts flags that its ACP entry point ignores. Explicit thinking remains rejected without a verified session-setting path. Missing, stale, or changed catalog evidence fails closed; discovery does not imply account entitlement, free pricing, calibration, or Nexus admission.
Related to #5, #15, #30, #58 and #59. Native ChatGPT MCP acceptance and controlled deployment are separate gates, so this PR does not close those issues or claim stable live dispatch. The dependent Swarm change is reviewed separately.
Independent verification on this split head: typecheck, all 34 server tests and diff checks passed. Worker-focused OpenCode/Cline catalog and profile/execution-contract tests passed. The combined candidate previously passed the full npm test chain plus standalone session tests; cross-platform CI for this exact PR remains required.
Current dependency rebind
Current head
8a8844d426d26d35a1c26a27af5b4ce0db33c0acmerges exact main502b4f240200b5ca73ac504d6a2d719abc42c177without rewriting branch history. The test command retains main CI wrappers and both catalog suites; server recovery wiring retains both catalog services. The previously accepted continuation fixture shutdown correction is applied separately. Exact-head continuation 9/9, typecheck, build and diff check passed. Merge-baseline affected tests passed 64/64 at predecessor239fbfdc; that result is not a current-head rerun. Independent whole-source review accepted exact head with verification gaps: 114 reported tests across eight focused files passed, with no source blocker identified. CI run 34508772695 has passed Ubuntu and macOS; Windows remains in progress. The tested merge commit 37d3831 has the same tree as this Candidate. Integration still requires all three platform jobs to finish successfully. This is a required upstream dependency for #62; #62 acceptance does not approve this PR. No deployment or native-runtime acceptance is claimed.