[tupe12334]

Summary

• Problem: block messages said When finished, run: sh ~/.config/steplock/sessions/<id>/<flow>/ack.sh. Claude Code auto mode flags this as "Auto-Mode Bypass", because the agent runs an opaque script that approves its own gate. Agents in auto mode cannot finish any steplock checklist.
• New flow: the block reads as a checklist step: Checklist step 2 of 18. Do what it asks, then record the result: steplock step done <checklist> <step> --session <id> --evidence "<what you did and what you saw>". steplock checks that the step is the current one and that the --next outcome is valid. It writes the evidence to audit.log as a step_done event. A wrong or repeated step fails and changes nothing.
• Gates never block a plain steplock step ... command, so evidence that quotes git push or gh pr merge does not deadlock. Commands with ;&|<>$, backtick or newline are gated as usual.
• allow_preview_request = true now lists every step in the first block message. Before, it pointed to preview.sh, and the agent had to read a file under ~/.config/steplock.
• Back-compat: ack.sh and preview.sh are still written to each session dir (deprecated, documented in Architecture.md). Old sessions keep working.
• Docs updated: README, Architecture, Installation, CONTRIBUTING, core docs, schemas, examples, CHANGELOG. Also promotes clippy::unused_self to deny (ratchet rule).

Test plan

• cargo test passes (new step_tests.rs unit tests plus a CLI end-to-end test: block, then step done with git push in the evidence, then the retry is approved and the evidence is in the audit log)
• cargo clippy --all-targets -- -D warnings passes
• cargo fmt -- --check passes
• Manual smoke test: rendered a branching block message from the debug binary in a temp .steplock/

🤖 Generated with Claude Code