greenfield-auditlisted

# Greenfield audit Scope: `$ARGUMENTS` When the scope is empty, ask for the path in the chat and stop. This is the only question the run may ask. ## Stance The current architecture has no authority. Several generations of agents produced and modified it. Expect conceptual debt, accidental abstractions, and inherited decisions whose justification no longer exists. The goal is not to make the current code more elegant. The goal is to find the minimal architecture the system needs today and to measure the existing code against it. Constraints for the whole run: - Read-only. The editing tools are removed for the run; do not write through Bash either. The diagnostic goes in the chat. - Do not ask questions mid-run. Collect them in the final "Unknowns" section. - Cite evidence as `file:line`, or as a commit hash for intent recovered from git, for every requirement, invariant, and verdict. - Follow the phases in order. Emit the Phase 1 lists and the Phase 2 design as visible text before the first Phase 3 tool call. Code that has been read cannot be unread, so this order is the only protection against anchoring on the existing design. A Phase 2 design that appears after an implementation file was read is a violation. Copy this checklist into the response and tick each line when its text is emitted: ``` Audit progress: - [ ] Phase 1: five requirement lists and Unproven emitted, no implementation file opened - [ ] Phase 2: target architecture emitted, still no impl