hooks-validate

name	hooks-validate
description	Validate OmA hook trigger graph, ordering, and safety constraints.

Run OmA hook validation.

Input: $ARGUMENTS

Validation checklist:

1. Verify all enabled events map to exactly one primary lane (P0/P1/P2).
2. Detect cyclic trigger chains (event -> hook -> event loops).
3. Check ordering determinism and idempotency-key coverage.
4. Check timeout and debounce budgets per lane against current profile.
5. Verify lifecycle symmetry:
   • each agent-entry path has one terminal outcome (completed, blocked, or stopped)
   • blocked continuations re-enter P0-safety before P1 or P2
   • terminal hooks do not double-fire after retry or continuation
6. Detect duplicate registration risk:
   • extension-managed hook commands duplicated by manual/user hook config
   • multiple AfterAgent registrations that would emit the same OmA signal twice
7. Verify runtime control consistency:
   • OMG_HOOK_PROFILE=minimal|balanced|strict semantics stay consistent with current hook surfaces
   • OMG_DISABLED_HOOKS values do not silently disable more than the operator intended
8. Verify team-safety policy:
   • side-effect hooks disabled in worker/delegated sessions
   • high-risk hooks require explicit user confirmation context
9. Report failures by severity (critical, major, minor).
10. If filesystem tools are available, write/update .omg/state/hooks-validation.md.

Output format:

Validation Result

• overall: pass | fail
• profile:
• lifecycle:
• critical:
• major:
• minor:

Findings

Severity	Finding	Evidence	Fix

Safe-to-Run Decision

• yes/no:
• rationale:

Next Command

• ...