T08 iter 1: scenario runner executes; GROUND setup and Select step
Replaces the RunOutcome::Unimplemented stub with a real runner: - ScenarioGame trait: games own setup presets and the command vocabulary, the runner owns execution, assertions, and determinism. - K8 double-run: every scenario runs twice on the same seed and fails on state-hash divergence. - K4/K11: applied events go through Envelope into EventLog, so seq monotonicity is enforced on the real path, not just in unit tests. - setup.patch was parsed and silently dropped; the runner now applies it generically and errors on a path that does not exist, so a typo in a scenario can never pass as a no-op. - Assertions: dot-path state lookup over objects and arrays, ordered event subsequence matching by field subset, exact rejects-set match. GROUND rules realized: GR-S01..S04 setup (seeded shuffle, deal, Lead, Surface Problem face up), GR-R02 Select commit, GR-R03 stress gate and Freedom spend, GR-A13 targeting legality. cb-sim dispatches by the scenario's game prefix and reports rule coverage. 3 scenarios pass, 7 rules covered; fmt/clippy/tests green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
be52250850
commit
a09d76f370
7 changed files with 848 additions and 47 deletions
21
.claude/ralph-loop.local.md
Normal file
21
.claude/ralph-loop.local.md
Normal file
|
|
@ -0,0 +1,21 @@
|
|||
---
|
||||
active: true
|
||||
iteration: 2
|
||||
session_id: 8cbd5701-a096-45a4-a419-9b7b1c9419bc
|
||||
max_iterations: 20
|
||||
completion_promise: "HEUREKA"
|
||||
workplan_id: CB-WP-0001
|
||||
workplan_file: workplans/CB-WP-0001-inner-loop.md
|
||||
started_at: "2026-07-31T00:08:23Z"
|
||||
---
|
||||
|
||||
Read the workplan at `workplans/CB-WP-0001-inner-loop.md`.
|
||||
|
||||
If every task has `status: done` AND frontmatter `status: done`:
|
||||
run `rm -f .claude/ralph-loop.local.md` first (deactivates the loop so the stop hook exits cleanly),
|
||||
then output <promise>HEUREKA</promise>.
|
||||
|
||||
Otherwise implement the next `todo` task as described in the workplan.
|
||||
Set task `in_progress` when starting, `done` when complete.
|
||||
When all tasks are done set frontmatter `status: done`.
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue