review-epiclisted

# review-epic Review: $ARGUMENTS ## Objective Prove that one implemented epic satisfies its outcome, child acceptance criteria, integration contracts, and applicable security boundaries. Correct confirmed defects, run one consolidated verification bundle, then roll up story, epic, and PRD status. `SCOPE -> AUDIT -> REMEDIATE -> VERIFY -> STATUS` Print one compact progress line per phase. Maintain a `Proof Ledger` under 300 tokens containing: epic ID, dependency-ordered child stories, review baseline, criterion evidence, review files, context files, risk axes, confirmed findings, commands, status path, and blockers. Update it instead of repeating plans. The epic is the execution unit. Child stories organize acceptance evidence and dependency reasoning; they never trigger separate review pipelines. ## Profiles Select the lowest profile covering the highest-risk changed surface. An explicit profile may escalate but never hide a DEEP condition. | Profile | Use when | Independent audit | Verification budget | |---|---|---|---| | FAST | Isolated behavior, clear in-repo pattern, bounded failure impact, no sensitive boundary | None; orchestrator audits the epic diff | At most 2 commands | | DEFAULT | Shared integration, public behavior, multi-module change, or a familiar new dependency | One correctness review | At most 4 commands | | DEEP | Auth, payments, PII, destructive data operations, migration, untrusted shell/file/network input, crypto, LLM tools, cross-service behav