Skip to content

Apply validated handshake and fault-accounting backports - #2

Open
manudrijvers wants to merge 1 commit into
o5-dex-directfrom
o5-validated-priority-backports
Open

manudrijvers wants to merge 1 commit into
o5-dex-directfrom
o5-validated-priority-backports

Conversation

@manudrijvers

@manudrijvers manudrijvers commented Nov 14, 2026 •

Copy link
Copy Markdown
Owner

Promotes the fully validated priority-backport candidate onto o5-dex-direct. Command sessions are refused while the connection handshake is incomplete, LTK and BLE-handle decoding are independent, and faulted-bolus accounting handles late reads, recovered cancellation and uncertain reset-fault data without double subtraction.

Applies the exact candidate recorded in research PR #10: upstream #201 and #211, their regressions, two O5 fault cases and 12 activation-session replays. Seven changed files match the retained candidate hashes. The packaged source-checksum resource is included unchanged from that candidate; the early control-only hook, command builders, transport and activation inputs retain their validated hashes.

Validation:

  • Repeated on this promotion checkout: 127 portable Swift tests, one existing skip, zero failures; eight source-extracted handshake scenarios, zero failures. Swift 6.2.4 in the pinned container, networking disabled and source mounted read-only.
  • Reused through exact source comparison: November 12 Mac validation, with 50/50 candidate native tests, expected baseline assertion failures, and a successful full unsigned arm64 Trio device build. Native tests and the device build were not rerun here.
  • Full changed-file set, every changed-file hash, all preserved-code hashes, packaged checksums, clean working tree and whitespace checks passed.

Candidate Kit commit: 654f93a652535940811dc2266c9546ddd213c2d3.
Candidate Kit tree: 3e1c22f5e7e2488980966fa842d02042088057c0.
Packaged sourceSHA256: d74e804f70fdb386d46634b05b03ae136fc9690af31fb1f50d4c96b878908442.

The companion Trio PR #1 pins this exact Kit commit and includes the signed-build and journal-verification handoff. Merge this Kit PR first using a merge commit to preserve the referenced commit; a squash or rebase requires updating and reverifying the Trio pin. No signed installation or real-Pod, delivery or E2-prevention outcome is established.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant