Repository navigation
Conversation
8 tasks
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
6 of 8 tasks
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.
What: Superseded by PR #322 at
c382af92d82d8b905402da0ad1dc07aad5a5cbd7on a fresh rebased branch.Why: Main advanced, and the fork stack requires rebasing rather than a merge commit.
So what: The parent binds native proof, Sol/Grok reviews and CI to #322 before deciding merge and rollout.
This PR is closed as superseded. Its old branch remains unchanged at
45e7b22c494fcf681e95a099e533217b8fad7840; no force push occurred. Current base isda7034eb8a465303710bccd91d55ea2618da4110. The bounded Claude correction and the current 473-test/type/lint/fork proof are recorded in #322 and the canonical #311 handoff.ships contextmd#34; no Chromeria map part
The following archived notes describe the earlier candidate and its historical evidence, before the Claude fork corrections and current-base rebase.
Closes #311. Implements the server half of contextmd#34 under its accepted design handoff, including the fork-only R2 correction. Companion: ContextMD PR #74, frozen at
1c47c08e6d6a27b899d68583ff8f8304a18da0f8.ships contextmd#34; no Chromeria map part
Change
session/newcalls. Bind immutable creation receipts before ref adoption, then charge/fence attachment before running/prompt dispatch, including rollback, cold load, and expired stages.Focused proof
On bestia, Node
26.8.2, usingnpx -y pnpm@11.10.0:At exact head
937cbc6430eead3e2abb165147dfada7311c1f73: 11 files, 448 tests pass (95.84 s); server typecheck exits 0; scoped lint exits 0 with four unchanged warnings verified in base366f2fff(unusedNodePath, two unusedselfInvocationvariables, and the existingfilter(...).at(-1)warning in ACP tests). Retained logs:TEST-chromeria-937cbc6-focused.log,TEST-chromeria-937cbc6-typecheck.log, andTEST-chromeria-937cbc6-lint.login task-owned/tmp.The tests cover actual Route/Serving/SQL mixed Cue replies, scoped receipts/refunds/replay, strict UTF-8/epoch/budget behavior, persistent Grok attachments, ACP creation/fallback/rollback receipts, manager forwarding/cache behavior, dispatch and rollback fences, and Codex inherited-versus-emitted rollback and projection negatives. Full repository coverage belongs to CI.
Fork ownership correction
The Fork Stack Model CI failure on
937cbc6430eead3e2abb165147dfada7311c1f73was my omitted ownership registration. The same local check reproduced all nine unallowlisted upstream edits, exit 1. Commitcde552474d74fed464dffec3687a5490cac61028registers exactly those necessary start/rollback/ACP seams and their tests under the existingcontextmd-servingowner. It also records the two new pointer test/corpus files and watches six already-owned shared seams without changing their primary owners. The correction touches onlydocs/fork-features.mdandscripts/fork-upstream-edits.txt.Fresh proof on the clean corrected commit:
All exit 0. The fork check uses the exact upstream base from the failed CI run, checks the full 60-commit stack, and reports
fork-features: OK (36 features)andfork-check: OK.Retained red/green logs:/tmp/TEST-chromeria-937cbc6-fork-stack.logand/tmp/TEST-chromeria-cde552474d-fork-stack.log. Both heads have the identicalappstree6f4ac94acf76a5e529a6386b73869d03b3b1d047. The 448 tests, typecheck and lint above were executed on937cbc6430, whose implementation remains unchanged; they were not rerun for this metadata-only correction. GitHub CI and implementation reviews on the new head remain separate gates.Native evidence and remaining gates
Before the final test/parity refinements, an isolated OpenCode
1.19.0subject used the real backend owner, real Cue client against a local stub, and the exact companion plugin with the native root SDK/save endpoint. Eleven controlled scenarios passed: normal mixed save, reversed application order, first PATCH 4xx, missing transport, lost save response, held/late commit with identical retry, lost applying acknowledgement followed by user/retry, two restart cases, and native overflow replay. The normal request held one pointer and storage held one marked part; a rejected save refunded P alone. Native replay changed the part id, kept the marker, and the continuation held one copy with an epoch-1 receipt. All subjects were isolated and stopped by their captured PIDs; external model calls: zero.The restart-after-lost-applying/no-save case reproduces the accepted conservative charged miss. It is recorded as a miss, not first-input acceptance. These experiments are pre-commit evidence, not the remaining exact-candidate native gate. The parent's exclusive native jobs still own final mixed/native barrier and retained-tail/replay acceptance, Codex F1-F4 and the nested fork/rollback/refork recorder proof. No real Codex proof is claimed here. The twelve visible live cells, natural-pressure Grok compaction, supporting builds, CI, and both exact-head implementation statuses remain parent-owned gates.
Task base:
366f2fff6f25f47c14ca86163d8ee8e4dd6c0961. Candidate:cde552474d74fed464dffec3687a5490cac61028. Current main at refresh:d74c023f7816d12282e5cb22fed83db7bc1618b4; its later #304 change has no owned-source overlap. Upstream-first searches at7ac952c630ef8a60d14ca8f6a0c7adce33db4baefound no pointer replacement, as recorded in #311. No package bump, production/config/database change, restart, merge, or deployment. Website impact: none; this is a server capability whose setup documentation ships with the companion PR. #310 and ContextMD #71/#72/#73 remain outside scope.Elon record
Authored by
gpt-6.1-solatmaxreasoning effort through the Codex harness in T3 Code.