Repository navigation
[codex] Align transport framing and track controller convergence - #42
Merged
Merged
Conversation
atomicdeploy
marked this pull request as ready for review
October 30, 2026 13:53
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.
Scope
Related to #41 and atomicdeploy/PCController#702, paired with PCController PR703.
This is the bounded first convergence slice, not a completed transport merger.
Temporarily based on PR40 to keep its earlier Web checkpoint separate; retarget
to main after that PR passes and merges. Do not bypass its outstanding CI gates.
Rust/Dart USB decoders, preserving valid wire bytes, opcodes and frame ownership.
PCController's corresponding C++/Go changes also protect its shared host UDP
decoder; its encoder now enforces its receiver's fragment-size rule.
standard recovery protocols, resource budgets and richer timing/lease semantics.
unrelated-history/file-by-file merger in linked issues. Add a real donor-index
route and retain every unresolved parity/physical gate.
Verification
Canonical Rust shared_cobs_vectors passes, mobile analysis reports no issues and
all13 USB tests pass. The actual C++ protocol framing test passes; the larger
wrapper continues separately and its final result is not inferred. Comparison
generation/Check, transport-convergence reviewed-slice gate, living-contract and
PU route checks pass. Existing fixture SHA256:
81683deafa749b231e483d2b75e4c45cae2a3262cab014ad0a20c74a82b31694.
Paired PCController checks pass for bounded C++ framing, stable-path Go native/UDP
and MCU inventory; its initial source-policy failure was fixed with narrow
per-document reviewed repository links and negative privacy tests, not a bypass.
No board, app installation, production process, settings or network actuation was
changed. No claim of full API/transport parity, new STM32/ESP physical support,
flash/RAM/stack deltas or real LAN/hardware/soak acceptance. Existing owner
worktrees/stashes remain preserved. Under the human's renewed cleanup request,
the exact generated bytecode file was removed by normal PowerShell Remove-Item;
both primary working trees are clean and their source is pushed. No deletion
workaround, ignore rule, source loss or stash cleanup was used. Unrelated drafts
and failed PRs cannot be blindly merged to manufacture a clean repository.
The larger Pakar protocol wrapper exposed a pre-existing LLDP fixture include
failure. Reused test-ethernet's BoardCore include path in test-lldp, which now
compiles/passes its actual scoped SDK-double tests. This does not retroactively
label the entire large wrapper passed. Comparison generation/Check passes with
unchanged donor counts and all remaining acceptance retained.