Skip to content

Clarify RPC completion, input and snapshot documentation - #72

Merged
janrysavy merged 1 commit into
masterfrom
codex/rpc-api-docs
Oct 6, 2026
Merged

janrysavy merged 1 commit into
masterfrom
codex/rpc-api-docs

Conversation

@janrysavy

Copy link
Copy Markdown
Owner

The API documentation treated steps as executed opcodes and omitted step polling from the wait summary. Clarify accepted entry state versus completed stop registers, Tick budgets, memory-watchpoint resumption, keyboard enqueue semantics and breakpoint preservation on restore. Replace the single-recv example with the existing framing-safe client.

Validation: 49 focused API/contract tests and 101 subtests passed; documentation inventory matches runtime capabilities. Changes are limited to JSON_RPC_API.md. Emulator behavior is unchanged.

Verified 49 focused API/contract tests plus 101 subtests against current implementation. Document Tick budgets, completed registers, watchpoint resume behavior, keyboard queue semantics and snapshot policy; use the framing-safe existing client.
@janrysavy
janrysavy merged commit 48867c9 into master Oct 6, 2026
5 checks passed
@janrysavy
janrysavy deleted the codex/rpc-api-docs branch October 6, 2026 04:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant