Repository navigation
Advance keyboard epochs after validated input enqueue - #73
Merged
Merged
Conversation
janrysavy
force-pushed
the
codex/keyboard-epoch
branch
from
October 6, 2026 04:53
4f488d5 to
e0855c4
Compare
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.
Keyboard enqueue changes complete snapshot state before the CPU consumes input. Both input.keyboard and keyboard.scancode now advance state_revision once after full batch validation; stale observation/export/import tokens refuse. Running input remains supported, and rejected batches preserve queue and revision.
Validation: 38 affected tests pass under CPython and PyPy. Omitting the enqueue epoch bump fails the three new production-handler/observation/complete snapshot controls; exact restored source passes. Final integration waits for the pending API documentation merge/rebase and final-head public CI.