stop-hook-blocks-on-incomplete-verification-gates

The session-close Stop hook actively evaluates whether verification steps were completed and will block session closure if multi-file changes lack Pristine Sweep, /tmp/ residue check, or Universal Completion Gate confirmation. The hook differentiates pure Q&A sessions (approve) from file modification sessions (block until verified). This is not advisory — it fired three times in this session, each time identifying a specific skipped step.

Related

• stop-hook-forces-pristine-sweep-before-exit
• stop-hook-verification-gate-catches-incomplete-completion
• universal-completion-gate-must-re-run-after-every-material-e
• stop-hook-blocks-proposals-awaiting-permission
• post-infra-modification-verification-checklist
• stop-hook-actively-blocks-on-missing-verification-steps
• pristine-sweep-blind-to-its-own-enforcement-artifacts