docs(handoff): record the jointly frozen v1 design

[abruption]

Authorized sequential merge checkpoint — 2026-10-17 KST

The user explicitly requested #106 → #107 → #108 → #109 sequential merges and0.4.0release preparation. This supersedes earlier Draft/no-merge status statements below; prior checkpoints remain historical. No package publication or unqualified platform/ACK extension is included in that preparation.

• Exact head 4f34f087c3ecc9ec06c4cb4c8a3b044f78378d1f, rebased onto current main 7ddded836ef79a7e3384a342ca7011c7abbe127c (public0.3.6 plus publication record).
• Local macOS Node24: full tests200total/195pass/0fail/5Windows-onlyskips, build/types/repository/diff checks passed.
• Frozen handoff document/fixture/pin bytes unchanged. Published0.3.6 VERSION/finiteprofiles, immutable public skill0.2.1source/hash, ordinarystrictSSH/nativeevidence/Windows exit guards retained.
• The existing reviewed Python1.1.0 runtime reference adoption is retained, separately from frozen design provenance; source hashes/oracle were verified.
• Ready transition triggers automatic Code/Security review on this exact source. Current-head CI/CodeQL and normal protection gates are required before a match-head-bound squash merge; older green checks do not qualify this head.

---

Earlier history (superseded source/status checkpoints)

Current refresh checkpoint — 2026-10-14 KST

• Exact head: bd8d240494503aa8ac9b2b4ae93d018ad7b83fd8; latest published main base: a2057940ba19056fcaaa5551a7820f7414bd3bfa.

• Rebased sequentially in dependency order docs(handoff): record the jointly frozen v1 design #106 → feat(handoff): add private correlation ledger and evidence CLI #107 → feat(app-server): add bounded guarded queue-only client #108 → feat(observation): add scoped metadata projection and bounded local waits #109. Each PR keeps base main for current-head full CI and CodeQL; later branches contain the preceding source dependencies and must be reviewed/merged in that order. This is branch preparation, not an integration merge into main.

• Local macOS arm64 checks: 199 total; 194 passed; zero failed; five Windows-only skips. Frozen handoff tests 7/7; build, types and repository/diff checks passed.

• Conformance used the existing exact exported published Python 1.1.0 source 8ca77cf31254c8287a2593fe484bb30a7dba2727; hash-pinned oracle tests executed. Frozen contract bytes/hashes and historical validation records are preserved.

• Published 0.3.5 version, finite skill matrix/pin, strict ordinary SSH response handling and Windows exit propagation are retained. No new native/live delivery, automated ACK or Linux/Windows observer qualification is claimed.

• Current-head Actions completed successfully; automatic reviews remain a separate gate. Earlier green checks below are historical and do not verify this refreshed head. Draft, human review gate, no merge/tag/release/publication.

• Final exact-head CI: 12/12 SUCCESS, CLI 38488499093 and CodeQL 38488494326, including both Windows-native Node 22/24. No rerun/bypass. Branch-scoped CodeQL open-alert API returned zero alerts. No new automatic Code/Security Review completion is claimed. GitHub reports MERGEABLE; the PR remains Draft.

---

Earlier PR history (superseded heads/checkpoints)

Scoped 0.4.0 review coordination — 2026-10-11 KST

The user approved keeping #69/#70/#71/#72 together with narrowly qualified macOS arm64 observation and explicit operator-confirmed receipts. Linux observation #130, Windows observation/private storage #131 and voluntary receipt producer/authenticated collector bootstrap #132 are Future extensions. No automatic ACK from text/turn/queue deletion, resend or receiver dedup is claimed. Required unsupported goals still refuse before effect.

This PR's own head remains a9e5b3b031193e664a6b95939d8e519a204dca86 and its narrower source/evidence below is unchanged. Integrated scope/docs and added pure-validator/ACK/SSH tests are in PR #109 at d830ccaa1a459bfec0f3c67e2b0e682d99bc7734; that integration does not retroactively qualify this standalone head. Companion skill guidance remains pending in session-peer-skill #31. Human review/merge order remains #106 → #107 → #108 → #109 with current-main checks. No merge/version bump/tag/release/publication is performed by this coordination.

Current verification checkpoint — 2026-10-11

Head: a9e5b3b031193e664a6b95939d8e519a204dca86. The ordinary conformance reference now pins published Python 1.1.0 at 8ca77cf31254c8287a2593fe484bb30a7dba2727; selected source hashes are checked before conformance tests. The ordinary list/discovery comparison does not establish full handoff, receipt or SSH runtime parity.

The published handoff document and fixture are byte-identical to frozen design commit 99d8ec3855d57da34a6fa789f3a375820a8fbe85. Fixture SHA-256 is 963b94e78f510c2535e405813558275d512a5bfe6bbd99ffdf0994b4d2e6e441. Any older checkpoint claiming a different published fixture hash or changed negative vectors is superseded. Frozen bytes and the historical Python 1.0.3 design baseline are unchanged.

Local Node 24.16.0/macOS arm64: build and type checks passed; npm test: 194 total / 189 passed / 5 Windows-only skipped, zero failures. Package smoke, bash/zsh shorthand contract/lifecycle, repository metadata/links and diff checks passed. Current-head Actions are pending after this push; prior green checks are not presented as new-head success. Draft and human merge gate remain in place. No version bump, merge, tag, release, global installation or publication.

---

Earlier checkpoints (history)

Current checkpoint — 2026-10-11 KST

Exact head: d62e813c8146e9832659654a850734fc986fd3d7. Refreshed against published 0.3.3 main c0ed30273b9e9c0049df86ae3c38486a94289527 using fast-forward branch updates and integration merges; the earlier Cloud CodeQL fixes are retained. This stays Draft, refs #69, within the unchanged four-issue 0.4.0 milestone.

Changes in this checkpoint

Record the published Python 1.1.0 contract checkpoint without replacing the jointly frozen document, fixture or ordinary Python 1.0.2 oracle. The published document is byte-identical; two negative control-character vectors differ. Added a pin-separation regression.

Validation actually performed

• macOS arm64, Node 24.16.0; existing exact Python 1.0.2 conformance source 47c23713d0a2a3c11ebde6186afd8c43489b8b65, extracted from the local reference repository. No runtime/reference repin.
• npm test (including build and test:types): 194 tests, 189 pass, 0 fail, 5 Windows-only skips.
• npm run test:package: bash/zsh contract + in-place fixture-version lifecycle, reproducible package, isolated install/uninstall pass. Repository checker, release helper pack/artifact, npm audit (0 vulnerabilities) and diff check pass. These are unpublished validation tarballs, not the public 0.3.3 bytes.
• Synthetic private homes, DBs, writer/SSH/native tools only for the new regressions. No user session delivery, transcript read, live injection/ACK, installed Codex 0.162.1 queue call, or Windows/Linux native qualification was performed.
• The first full invocation omitted SESSION_PEER_PYTHON_ROOT and failed to locate the oracle; the corrected invocation used the exact reference above and passed.
• Exact-head CI: 12/12 SUCCESS, including macOS/Ubuntu Node 22/24, Windows native 22/24, repository policy, release gate, CodeQL and GitGuardian. CLI run, CodeQL run; no reruns. These are fixture/CI results, not broader native integration qualification. No new current-head Codex review is posted as of this check; historical reviews are not counted, and no manual review mention was posted.

Remaining gates

Cross-runtime execution and any later runtime-reference repin remain unverified. Design freeze is not runtime acceptance.

Required unsupported goals refuse before native effect. No fallback/retry after a possible native submission; queued/posted is not receipt ACK or completion. The milestone remains incomplete. No merge, release/version bump, npm publication, tag, protection change, operations change or issue closure is requested by this checkpoint.

Earlier implementation/validation record (historical checkpoint)

Status and scope

JOINT DESIGN FREEZE RECORDED for the exact reviewed tuple. Runtime is NOT IMPLEMENTED. Refs #69; does not close it. #69/#70/#71/#72 remain together in milestone 0.4.0. No merge, implementation, operational change, live test or publication is authorized by this design record.

Mirror final Python Draft PR abruption/session-peer#261, exact candidate 99d8ec3855d57da34a6fa789f3a375820a8fbe85:

• Document SHA-256: 46a953010c49214bd8f969412f26713384fbe09a0ba78ebf0fef75da40d0d889.
• Fixture SHA-256: 963b94e78f510c2535e405813558275d512a5bfe6bbd99ffdf0994b4d2e6e441.
• Separate published Python baseline: 1.0.3 / 0d252550ab40c26d1ac4a19193df6ca2f84d830b.

Current TS runtime/conformance/referenceVersion markers remain unchanged. Design fixture approval is not runtime parity with an unshipped feature release.

Review outcome

The previous seven security/lifecycle amendments and three final alignment findings are addressed in the exact document, fixture and test-only helper. Static review has no remaining normative change requested on this candidate:

• Original-request native profiles preserve Python Claude absence, TS nullable/optional target fields and Codex status/UUID/home/consumption/optional queue ID.
• Post-submission unsupported preserves effect/injection facts under an explicit-wait exit-1 tuple.
• Pending wait interruption is stopped/stopped_by_operator with complete ok:false/exit130 output; status query is exit0, and terminal history remains immutable.

Python exact acceptance and joint freeze record confirms the same source/document/fixture tuple. handoff-v1.pin.json records jointFreezeApproved=true, runtimeImplemented=false and no outstanding design review gates, including source hashes, external record and the TS approval commit. Raw upstream document/fixture bytes are unchanged: their historical proposal/draft labels remain; DESIGN approval is separate provenance. Any normative/schema/vector edit needs a new exact joint review. No source regeneration or automatic fixture update occurred.

Changes and bounds

• Exact upstream MD/JSON copies and pin manifest under test/fixtures, excluded from the unchanged 51-file npm allowlist.
• PARITY review plus four-language README/guide links; current install/CLI contract unchanged.
• Six static test-only checks for exact pins, historical synthetic bytes and scoped design freeze and selected shared safety/profile/query/wire/wait facts. They do not run a collector, private authentication, native observer, crash/clock engine or transport.
• No src, package/lock metadata, release helper/workflow, native/SSH/API behavior, version or public type-export changes.

Upstream exact99d8 documentation/CodeQL checks succeeded; four optional Control dependency-audit jobs and required release gate failed. That repository CI boundary is separate; no bypass/repair/full-green claim is made. Producer/collector/bootstrap, durable fences, original-generation/body-free observation and per-platform cleanup remain implementation acceptance gates.

Verification

Local macOS arm64, Node 24.16.0/npm 11.15.0:

• Build/test:types and npm test: 157 tests, 152 passed, 5 Windows-only skipped, 0 failed. Existing runtime conformance used the existing Python1.0.2 reference.
• npm run test:package passed reproducible 51-file packaging, isolated install/removal and Bash/zsh shorthand lifecycle.
• Repository metadata/docs/links and diff checks passed.
• Independently ran exact upstream test-only documentation validator: 20 tests passed. Its39 request-aware wire vectors and behavioral cases remain synthetic schema/static checks, not runtime or live acceptance.

The local full check preceded approval-record-only metadata edits. After the joint freeze record and localized status links changed, test:types, all six targeted pin/golden checks, repository links/metadata and diff checks passed again. Independent scope review confirmed raw source MD/JSON and runtime/package/workflow/version/reference-marker bytes unchanged. Latest-head CI is tracked separately. No auto merge, implementation or publication.
Windows native CI retains the existing selected test list; the six new checks run in the full macOS/Linux suite. No Windows receipt/collector or live ACK claim is made.

Joint freeze record verification

Latest TS metadata head a2f06d324f9439bddfd723e04474db4268971711: all 12 CI/check entries succeeded, including macOS/Linux Node 22/24, Windows native Node 22/24, repository policy, release gate, CodeQL and GitGuardian. Draft is retained; no merge or implementation approval. External Python acceptance was independently verified at the exact source/hash tuple, and raw mirrored MD/JSON bytes remain unchanged.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-17T14:24:41.072404Z	4f34f08	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-17T14:25:17.850879Z	4f34f08	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.