Repository navigation
Conversation
Signed-off-by: aihop <4408344+hhyykk@users.noreply.github.com>
hhyykk
requested review from
huangruiteng,
loopx-agent and
songoow
as code owners
October 21, 2026 05:43
This branch has not been deployed
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.
A canonical Todo collection rebuilds the same acceptance authority and Todo indexes while producing its contract, oracle context and work guards. This proposal reuses that validated basis within one loaded provider head. Each later head/page and every standalone public helper still starts fresh.
The existing acceptance owner now supplies
GoalAcceptanceRead;canonicalTodoCollectionshares it and projects guards at the original call site. Input checks, first-error precedence, exact/retiring ownership, held work, output container independence and wire fields remain intact. No persistent cache, RPC, Python bridge, setting or write authority is added.Based on the accepted migration RFC §§2.5, 2.8 and 6. Head
501c88099a68f9f75d018360c394c657556c3ebd, base4e6baa51afdc2ad522012c1f691ae166c9d67e7b. All 47 other open PRs and their paginated file lists were checked: none changes these three production or two test files. Shared RFC bookkeeping is a separate paragraph. Larger interaction/quota rewrites overlap existing work; Hook batching adds compatibility bridge cost; several large adapters have no live caller or already use one native transaction.Migration economics:
goals/acceptance_contract.ts, before and afterObserved native cost, milliseconds p50 / p95:
Each row uses 32 alternating A/B–B/A pairs, real provider IO, the complete public native
listLocalCoordinationTodosresult and JSON serialization, with identical result bytes. This is not a Python CLI or managed-IPC benchmark. An unchanged-code A/A control measured 188.4 / 250.8 versus 182.0 / 212.2: tail variance is retained, so these observations do not certify a full-CLI performance gate or a universal percentage gain. The earlier exploratory samples remain separate evidence.Validation:
Remaining qualification: full control-plane typecheck still reports the seven unchanged
conversation_binding.tsnullability errors reproduced on main (separate #6980). Quick premerge passes its four direct checks, then fails the risk-characterization smoke before dispatch at the local IPC permission boundary. Full CLI cold/warm cost, managed-runtime/daemon memory, installed managed callers, PostgreSQL and live App adoption remain unqualified. Existing budgets and failed evidence are unchanged. This is an author proposal for exact-head review, with no merge or release claim.