quality-loop

Inventory what the code actually does, then test, fix, and regress until the sheet is complete. Expected behaviour comes from implementation, not from docs or memory.

This loop will not fit one smart-zone session. Write the sheet to disk and come back. Do not ingest the whole tree into chat.

Docs describe shipped behavior. Aspirational product copy is not a row.

When

• A shipped product needs an honest feature inventory and test pass.
• A plan or diff needs a P0/P1/P2 read → use review instead (a shipped product audit is quality-loop, not review).
• Orientation in an unfamiliar codebase → use learn-codebase instead.

Before you start