Improve architecture

As the main session, run the loop in use-workflow and size the pass here. As a lane, execute the brief and return its report. Read architecture-language.md when naming a finding, and engineering-discipline.md before judging tests or applying a change.

The owner's purpose for the pass: to "look with a bit more clarity to ensure we didn't just tack things on until something worked, without zooming out a bit and ensuring the code is actually well architected and lean, my testing preferences, comments close to zero to avoid explanation of workarounds and hacks to mask problem areas".

Sizing

• Milestone close, or a change to a shared contract: four reads, named by role: two independent architecture reads on the primary model line, one on the second line with the first two withheld, and one on the tests.
• Normal slice: one blind read per model line.
• Lighter route: none.

The main session compares the reads and is never one of them. Findings are reported, the owner rules, and accepted fixes land as their own PR on top of the stack.

Discovery

Start from caller-visible usage. Name friction as scattered knowledge, pass-through layers, unowned rules, invalid states, workarounds explained by comments, or defensive code and tests with no failure they guard. A finding names the caller, the rule, the owner it proposes, and how unchanged behavior is shown. A no-change verdict needs evidence too.

Apply