[dtt-github]

What

A new Which is wrong? answer in the Design view's What actually happened: The example: use what the design did. When the design is right and the example's timing or value was a guess, one click rewrites the failing check from the simulation:

• the expected value appears a few cycles later/earlier → the check moves (a wait is added, or the one before it is shortened);
• wait_until → given enough cycles;
• expect_for that stops holding → covers only the cycles it held;
• otherwise → expects the value the design gave, written the same way (0x/0b/decimal).

The changed example is simulated again (repeating for further failing checks); the changes are listed first and Change the example applies them only if the example then passes. No AI, no cost.

Files

• apps/web/src/lib/fixexample.ts (new): oneFix / findFix.
• apps/web/src/lib/replay.ts: Replay.read(port, cycle).
• apps/web/src/components/Design.tsx: button, preview, apply.
• Docs: docs/user-guide/design-view.md; CHANGELOG.

Checked

• Browser, local: a check one cycle early → "Step 3 (expect led = 1): checked 1 cycle later", applied, saved, 2 of 2 passing; a wrong value → "Step 7 (expect for led = 1): expects led = 0 instead of 1", applied, 2 of 2 passing.
• cargo fmt --check, clippy -D warnings, cargo test --workspace, web typecheck and build.

🤖 Generated with Claude Code