test(daemon): observation-script replay simulator for step() (coupling-core D1)#466
Merged
Conversation
…g-core D1) Adds a deterministic scenario harness over the pure transition core: a script of (clock advance, observation) ticks is replayed through stepRun with status effects folded back like the updateStatus executor, and the exact sequence of committed transition targets is asserted. Five scenarios pin past incident classes and laws as replayable scripts: duplicate terminal events (merged PR commits done exactly once, L1a/L4), prompt debounce with streak reset (L6), completion verdict terminal absorption, rate_limited resume, and never-alive remote grace then unknown (L3). All pass against the current core, which also validates the transition matrix in docs/design/run-state-machine.md against the implementation. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Phase D1 of the coupling-core roadmap: a deterministic observation-script replay harness (
step_sim_test.go) over the purestepRuncore, plus five scenarios that pin incident classes and laws as replayable scripts:donedoneunknownAll five passed on first run against the current core — the harness doubles as a conformance check of the §3 transition matrix in
docs/design/run-state-machine.mdagainst the implementation. Independent of the Phase A/B PRs; merges off main.🤖 Generated with Claude Code