assist-reviewlisted

# Draft Assist Review: Human-in-the-Loop Gateway Help human reviewers effectively review an executed track without shifting the entire cognitive burden onto them. ## Red Flags - STOP if you're: - Conducting standard unit tests; use `/draft:review` for that. - Fixing code rather than explaining logic and risk profiles to the human. - Reviewing output without first summarizing the source `spec.md` intent. --- ## Workflow Constraints 1. **Context Extraction:** - Load the track's `spec.md` and `plan.md`. - Load the track's `hld.md` and `lld.md` if present — extract Key Design Decisions, Alternatives Considered, and (LLD) class invariants and error policies. - Re-summarize the **Intent** of what this track was supposed to achieve in exactly two sentences. 2. **Blast Radius Isolation:** - Scan the `git diff` generated by the target track. - Separate trivial edits (naming, routing adjustments, formatting) from **Structural Edits** (schema updates, concurrency alterations, middleware auth changes, API surface changes). - Present structural edits first — these are where review time should be spent. 3. **Generate the Human Helper Guide:** - Instead of a traditional bug hunt, generate an executive summary containing a **Risk Assessment**. - For each structural edit, cite the originating decision: *"I chose `[Pattern]` for `[File/Function]` because hld.md §Key Design Decisions / Alternatives Considered selected it over [rejected alternative]. You should spe