thermo-nuclear-code-quality-reviewlisted

# Thermo-Nuclear Code Quality Review Review **current branch changes** through five lenses, in order (the checkout you were launched in — execute-plan launches the reviewer in the ticket worktree). Phases 0–3 are **review-first**: report findings, change code only if the user says "fix". Phase 4 (docs) is **always applied** where a feature-docs flow exists. **Maker/checker is unconditional for agent-authored diffs:** if any part of the diff was written by an agent in any session (execute-plan or otherwise — resumed agent-authored branches included), run the review as a **read-only subagent** — the reviewer must not share the implementer's context or be able to edit. Manual invocation on a human-authored diff may run inline. Number every finding `N | file:line | severity | problem | fix` so accepted findings can be appended to the plan file as structured remediation tasks (see the review loop below). **Pinned review model:** the reviewer subagent is launched with a **pinned review model** — record your chosen slug here (pick the strongest reasoning/thinking model available in your tool) — never inherit the implementer session's model (auto included). If the slug is unavailable, stop and ask the user; never silently substitute. **This section is the single source of truth for the slug** — write-plan and execute-plan reference it instead of hardcoding it; when the model changes, update it here only. **Persist the verdict:** when a plan file exists for the branch, the **invok