Analyze — Read-Only Deep Analysis

Use $analyze to answer a repository question with grounded, read-only evidence. Explain what the code most likely says; do not turn analysis into implementation or generic fix planning.

Shared operating, delegation, state, hook, team, cancellation, and verification invariants live in templates/AGENTS.md. Follow that source instead of duplicating its rules here.

Use when

• The user needs a causal, architectural, behavioral, impact, or tradeoff explanation.
• The answer requires tracing multiple files or boundaries, or ranking plausible explanations.
• The user needs confidence and concrete evidence before changing anything.

Do not use it for edits, implementation, a new product plan, a simple one-file lookup, or OMX team-runtime operation.

Inputs and method

1. Restate the question and define the evidence-backed scope.
2. Identify the smallest files, tests, configs, and docs likely to answer it.
3. Read direct code paths and contracts first; trace boundaries only as far as needed.
4. Compare competing explanations, rank them by support, and mark unresolved points.
5. Stop when the question is answered w…