April 16: Hook Docs and Opus 4.7
Two doc PRs syncing hook references with reality — plus Opus 4.7 dropped and I got early access to the 1M-context variant.
Developer Journal
Document post-edit-ruff and require-plan-file hooks (#1243)
Two hooks that had been live for weeks without dedicated docs:
post-edit-ruff— runsruff checkon any edited.pyfile underprocessing-engine/immediately after the edit. Surfaces violations before the pre-commit hook would catch them, so the feedback loop is tighter during active development.require-plan-file— warns before Edit/Write if the current branch isfeature/,fix/,refactor/,perf/, orci/and there's no matching plan file indocs/plans/features/. Reminds me to write the plan before heading in.
Documented both in the hooks reference table with what they do, when they fire, and how to work with them when they flag.
Rename block-pr-merge → warn-pr-merge (#1242)
The merge-protection hook was originally named block-pr-merge but has never actually blocked — it warns the operator and asks for confirmation, which is the right design given the tiered merge policy. The name was leading to "why is this blocking" questions. Renamed throughout the docs to warn-pr-merge to match what it actually does. The hook file itself was already named warn-pr-merge.sh; this was doc-only alignment.
Side note: Opus 4.7 release
Opus 4.7 landed today — early access, released more broadly by the afternoon. The non-1M variant was doing frequent auto-compacts on long sessions; the 1M-context version (the one running this retro) doesn't hit that wall. Switching over for work where context preservation matters.
What shipped
| PR | Title |
|---|---|
| #1243 | docs: document post-edit-ruff and require-plan-file hooks |
| #1242 | docs: rename block-pr-merge hook references to warn-pr-merge |