Repository navigation
Apply validated handshake and fault-accounting backports - #2
Open
manudrijvers wants to merge 1 commit into
Open
manudrijvers wants to merge 1 commit into
manudrijvers wants to merge 1 commit into
Conversation
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.
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:
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.