The behavior guide is generated from the Given/When/Then scenarios in the acceptance catalog. Each implemented step is executable against an isolated repository and the real command hook. Proposed scenarios are displayed separately and do not count as passing tests. Generation and CI checks run the implemented scenarios first; failing scenarios cannot publish a verified behavior page.
Add a scenario by composing Scenario(...).given(...).when(...).then(...) with fixture actions for every implemented step. Titles must be unique. Use status="proposed" with no executable actions for a planned behavior. Keep hook payloads, temporary paths, and test setup in the fixture rather than the prose.
python3 scripts/table.py # after editing watchers.json
python3 scripts/scenarios.py # verify scenarios and regenerate the behavior guide
python3 scripts/scenarios.py --check # verify scenarios and reject stale behavior docs
python3 docs/sync.py --write # regenerate site pages from README and the verified behavior guide
python3 -m unittest discover -s tests -p 'test_*.py'
node --test tests/test_integrations.mjs
nvim --headless -l tests/overwatch_spec.lua
claude plugin validate .
claude plugin test .
claude --plugin-dir .
cd docs && zine # the site, served locally