Codex Formax Semantic Parity for Terminal and Web Event Order
Use the same event fixture across Formax terminal, app-server, and web clients to verify replay, input lifecycle, and ordering.
中文Install in Codex
Codex with a Formax checkout, its behavior contracts, and a synthetic event fixture.
- Copy the entire pinned `.codex/skills/formax-semantics-parity-workflow/` directory to `.agents/skills/formax-semantics-parity-workflow/` in the target checkout.
- Open Codex in that checkout and invoke `$formax-semantics-parity-workflow` with the example task and desired output.
Example task
Give `$formax-semantics-parity-workflow` synthetic input-start, completion, and replay events in a practice branch. Compare completion ordering in terminal and web views.What to check
The report shows evidence for shared state handling and identifies the layer responsible for any ordering difference.
Original SKILL.md on GitHub · Updated
Frequently asked question
Do different colors or labels indicate a semantic difference?
Check whether the underlying state and event order agree. Each client owns its rendering choices.