smokeable claims: just smoke <claim>, BREAK=1, and the record on the evidence page - #147
Merged
Conversation
…evidence page Four scenarios under scripts/smoke/scenarios, one per claim, run on forgejo-warden's throwaway Forgejo at the commit the demo pins, each step printing one SMOKE verdict line. no-execution folds a policy with a planted top-level side effect and the marker never appears; BREAK=1 runs the same file and it does. fold-equals-run passes check mode; BREAK=1 plants an environment read and the fold refuses it at the line. rules-over-values applies a removal under the cap; BREAK=1 asks for three of four and the guardrail blocks the apply. round-trip applies, reads live back and finds nothing; BREAK=1 drifts one field and the plan names it. scripts/smoke-record.sh runs all eight and writes docs/data/smoke.json, which the weekly demo workflow commits and the evidence page renders; each claim page carries its scenario's prompt and the lines it prints, and the tutorial lists the commands.
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.
Closes #146. The site's three claims now have scenarios a reader can run, each with a
BREAK=1variant that watches the check catch the broken case, the shape choudoufu's smoke has.just smokelists four claims;just smoke <claim>runs one against forgejo-warden's Docker Compose sandbox at the commitdemo.ymlpins (cloned into.forgejo-wardenifWARDEN_DIRis unset), printingSMOKE op=… verdict=pass|caught|failper step. Findings on the way: a top-level side-effect call is invisible to the fold byS-Module, so the same file folds to its plan with no marker and runs with one, which is the no-execution scenario as it stands; warden's bootstrap is not idempotent for its token, so the runner starts each sandbox fromdown -v; branch protection cannot exist on an empty repo, so the smoke policy carries repo settings only.scripts/smoke-record.shruns all eight and writesdocs/data/smoke.json; the weekly demo workflow gains that step and commits the record with the workflow token, and a newsmoke-rowsshortcode renders it on the evidence page with the run's commit and date. Each claim page has a "See it hold" section with the paste-to-an-agent prompt and the verdict lines in order; the tutorial lists the commands. All eight runs pass locally, the committed record is from that run.