universal-completion-gate-must-re-run-after-every-material-edit
The Stop hook blocked session exit twice because the Universal Completion Gate was run at session midpoint but additional material edits followed without re-invoking it. The UCG is not a one-time ceremony — it must be re-run after every material change (any write that changes behavior or state). Running it once early and then making more edits leaves the final state unverified.
Related
- stop-hook-forces-pristine-sweep-before-exit
- stop-hook-verification-gate-catches-incomplete-completion
- 2026-04-04-oracle-001-self-architecture-analysis
- claude-code-v2-1-78-root-restriction-non-root-user-workaround
- clawteam-openclaw-multi-agent-swarm-evaluation
- postcompact-4-probe-verification-blocks-resumption-on-failur
- tmp-backup-cleanup-required-in-ucg
- stop-hook-blocks-on-incomplete-verification-gates
- stop-hook-actively-blocks-on-missing-verification-steps