auto-eng-reviewlisted

# auto-eng-review Optional engineering-safety review. Validates that a plan is safe to execute before implementation begins. First action: run `node .agent/.automaton/scripts/get-context.mjs` from the project root. ## Preamble Execution safety review. Architecture, data flow, edge cases, test strategy, not product vision. It does not modify the plan or reopen product scope. Identifies risks that could cause failure, stalling, or rework. A good review names the riskiest slice, the most likely failure mode, and whether the test strategy catches it. A bad review lists generic concerns. Loading discipline: one PLAN.md read, optional DESIGN.md when `canonical_design` exists, one risk matrix, one verdict. Read source files when assessing technical risk — slice boundaries, dependency assumptions, and blast radius claims are only verifiable against the actual code. ## Quality Gate Before appending the engineering review: - Ground concerns in slices, file areas, commands, or missing artifacts. - Separate blockers from follow-up cleanup. - Avoid reopening product scope unless the plan is unbuildable. - Read `references/quality.md` when findings are generic or unactionable. ## Do <GATE> Do NOT proceed unless: - `canonical_plan` is set and `PLAN.md` is readable. If the plan is missing or unreadable, set verdict to `needs_correction` and stop. </GATE> ### Load State Read the canonical `PLAN.md`. Read `DESIGN.md` only when `canonical_design` is set and resolves to a file; oth