[HT-68]: Replay viewer — step-through reconstruction on the real table

[Maiz27]

Parent

PRD-05: Game History & Replay — #111

What to build

Let the player open a saved match from history and replay it step by step on the real table. Build a reusable replay driver that wraps the existing transcript replay engine to expose each intermediate snapshot — step forward/back, seek, and per-round/turn markers — since the engine today returns only the final reconstructed snapshot. This driver is the shared foundation reused later by the branch sandbox, so build it once here.

The viewer renders each reconstructed snapshot on the actual table UI and lets the player navigate per applied action with round and turn markers. This slice is neutral — no coach overlay yet. A replay record that cannot be reconstructed (e.g. a version-gated transcript from an incompatible build) is caught and surfaced as "replay unavailable," never a crash.

Acceptance criteria

• A reusable replay driver yields each intermediate snapshot and supports stepping forward/back and seeking to an arbitrary action, including across round boundaries.
• Opening a replayable match from history shows the match on the real table and lets the player step through it per action.
• Round and turn markers allow jumping between rounds.
• A record that fails to reconstruct surfaces a graceful "replay unavailable" state instead of crashing.
• The driver is domain-layer and Flutter-free; the viewer screen is a thin consumer.
• Unit tests assert the driver's stepwise reconstruction matches the engine's result, including round-crossing and arbitrary seeks; a thin widget scenario covers viewer navigation and the unavailable state.

Blocked by

• [HT-65]: Record completed matches to history (summary + replay record, resume-safe) #113
• [HT-66]: History list screen — browse saved matches, setup & outcome, delete #114

[coderabbitai]

🔗 Related PRs

#25 - Build playable Classic Hareeg slice [merged]
#40 - test(scenario): add L1 ClassicHareegScenario DSL with regression coverage [merged]
#58 - refactor: deepen game table architecture boundaries [merged]
#95 - Harden stock-exhaustion round-liveness root cause + no-recovery sweep coverage [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!