Repository navigation
Record one-byte macro controls with an explicit encoding - #263
Merged
Merged
Conversation
Co-authored-by: Codex GPT-6 <codex@openai.com>
relh
marked this pull request as ready for review
October 4, 2026 19:38
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
1 participant
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.
Pistonball and Crewrift execute one unsigned control byte per seat per tick. The private macro recorder now declares a typed
u8encoding and validates its exact stride. Existingi8-i8-i8-u8records retain their four-byte contract. Both encodings require canonical base64 and positive exclusive tick intervals.Nim2.2.4 private trajectory tests passed remotely under1CPU/768MiB/Nice19/noSwap with a finite90-second limit. The new three-tick00/7f/fe case round-trips exact bytes and rejects four-byte padding and noncanonical base64. Initial sparse-checkout fixture setup failure is retained; the complete source passed in invocation2e037f1d79124fc99ad9fd0b6db36a02.
Both CI checks passed. The actual Pistonball producer compiled and ran ten complete diagnostic episodes. Current Metta5bf831 SDK raw-event→complete-episode→raw-event roundtrip retained200 decision intervals and19,680 real one-byte controls over984 engine ticks. Every per-seat byte matched the corresponding authoritative whole-engine trace. Invocation8d25b23ca4c54d518031f23e4c405b35 exited0; completeSHA d38ed47b68bca19b8b3bcc475bb5edeba858a478bf9ba234652c2c47afa6177e. The task-only emitter declares its exact source-archive checksum; this fixture provides format evidence, no external teacher authority. Parent source review remains required. No production publication or model authority claim. Existing game source/image receipts keep their immutable pins.