| # Rust scoreboard packet admission cache and ring-buffer policy | |
| RE-808. Reproduce with `python3 scripts/analyze_rust_scoreboard_packet.py`; focused validation: `cargo xtask test-group rust-scoreboard-packet`. [Machine report](rust-scoreboard-packet.json). | |
| The packet API validates complete input shape before mutation, admits a prefix with at most1024 row bytes and increments the ring counter even for an empty packet. Names retain the existing explicit fallback/truncation/raw-byte model. Unit tests independently construct an exact1024-byte packet, verify the19th attempted cache mutation, and check atomic malformed-order rejection. Native formatter/copy/send parity is still not claimed. | |
| Original executable/native runtime and complete Linux/macOS Rust/Bevy/Solari acceptance remain unverified. | |
| RE-818 supersedes the earlier formatter model for current packet parity: original37914 now executes in the reference, and Rust uses its recovered decimal semantics. Native copy/send assumptions remain explicit. See [current evidence](RUST_SCOREBOARD_ORIGINAL.md). | |