hooks-test

name	hooks-test
description	Dry-run OmG hook pipeline against simulated event sequences and report efficiency.

Run OmG hook dry-run test.

Scenario: $ARGUMENTS

Test protocol:

1. Select or infer event sequence (default):
   • SessionStart
   • BeforeAgent
   • stage-transition (derived from AfterAgent)
   • BeforeTool -> pre-verify (derived)
   • AfterTool -> post-verify -> checkpoint-save (derived)
   • AfterAgent -> blocker-raised -> agent-blocked (derived)
   • Notification -> blocker-repeat -> loop-stall (derived)
   • PreCompress -> context-drift (derived)
   • SessionEnd
2. Evaluate trigger firing order by lane (P0-safety -> P1-quality -> P2-optimization).
3. Simulate all defined derived signals:
   • context-drift: when summary entropy or token usage spikes
   • risk-spike: when failure density or tool errors grow
   • loop-stall: when same blocker repeats across turns
   • token-burst: when single-turn token usage exceeds threshold
   • blocker-repeat: when a previously resolved blocker reappears
   • agent-blocked: when delegated execution requests continuation or hits a hard blocker
   • agent-finished-early: when delegated execution returns a non-goal terminal state
   • stage-transition: when workflow stage (e.g., plan -> exec) changes
   • pre-verify: before critical tool execution or state change
   • post-verify: after tool execution to confirm outcome
   • checkpoint-save: when state is persisted to disk
   • blocker-raised: when a new execution blocker is identified
4. Verify lifecycle symmetry:
   • check for before/enter vs after/exit parity
   • identify potential double-fire risks in retries
   • validate re-entry into P0-safety after blocks
5. Record skip reasons (debounce, cooldown, disabled profile, worker-session safety, lifecycle duplicate suppression).
6. Estimate hook overhead and value:
   • estimated time spent
   • estimated redundant-loop reduction
   • estimated token savings from early drift/blocker detection
   • estimated repeated-hook suppression from lifecycle symmetry
7. If filesystem tools are available, write/update .omg/state/hooks-last-test.md.

Output format:

Dry-Run Summary

• profile:
• sequence:
• hooks fired:
• hooks skipped:

Event Trace

Step	Event	Signal	Fired Hooks	Skipped Hooks	Notes

Lifecycle & Lane Validation

• P0-safety status:
• Symmetry check:
• Re-entry logic:

Efficiency Estimate

Metric	Value	Comment

Next Command

• ...