ucg-must-be-explicitly-invoked-not-implied
The Universal Completion Gate for multi-file sessions (40+ files, multi-module) must be explicitly invoked and each of the 7 checks individually documented. A session that lists ‘verification done’ without running through the UCG checklist will be blocked by the Stop hook. Implicit compliance is indistinguishable from non-compliance to the hook evaluator.
Related
- stop-hook-catches-code-gen-missing-verification
- stop-hook-loop-on-mid-workflow-user-silence
- stop-hook-false-positive-during-waiting-state
- stop-hook-fires-on-waiting-state-not-just-session-end
- stop-hook-fires-on-user-wait-not-just-agent-stop
- ucg-explicit-invocation-required-stop-hook-blocks-otherwise