Repository navigation
feat(runbook): add recipes, exact height pauses, and visual editor - #1
Conversation
IntentProvide reusable YAML runbooks and a visual editor for transactions, state queries, assertions, scripts, exact committed-height pause, manual hold/resume, and raw store inspection using stock chain binaries. Land the reviewed feature in main with a rebase merge. Reviewers
Act onAll three original findings from Reviewer B are fixed in 1deac56.
Regressions failed on the previous source for each actual defect and passed after the fixes. The current committed head passes just check and GitHub CI. ConsiderNone. NotedTemplate-bearing store fields can still be invalid after rendering and can therefore fail after earlier steps. Their values may depend on earlier outputs, so preflight does not resolve them. This matches the documented validation boundary. The tmux driver used the documented Ctrl+C close binding. Injected bare Escape did not close overlays in that driver. Escape unit tests pass; the live driver does not establish bare Escape behavior. DismissedNone. Agreement mapAll reviewers agree the three accepted fixes satisfy the original intent. No remaining code findings block landing. The updated head has fresh independent real execution evidence and current CI. Approved landing revision
The independent verifier did not write the implementation. This comment records its verdict through the repository-owner CLI session. Rebase merge is authorized by the user. No auto-merge or queue request is armed. |
Why
Debugging a restored chain requires repeatable transactions and state checks. Add YAML runbooks and a visual TUI editor so users can save and rerun the same test without editing YAML by hand.
The engine runs the lab's stock binary. Exact pauses use a separate halt strategy and verify committed application height on every validator while query RPC remains available.
Scope
Verification
just checkpasses, including lint, race tests, and build.Current review fixes include regressions that fail on the previous head for wrong-lab targeting, draft loss, and an earlier transaction preceding invalid store validation. A fresh terminal test created and saved a recipe, preserved the draft during cancellation, and executed an assertion against beta while alpha was active. The terminal driver used the documented Ctrl+C close binding.