Fancy Harden

Test and drift-alignment are one loop: catch a lie (mock theatre, missing path), fix it, lock a regression. Claims are not evidence.

Gate in

Prefer after /fancy-build. A small tool may skip heavy automation, but the happy path must be walked with a log or a screenshot.

Iron rules

1. The model saying pass is not pass. Need a command log, network trace, or screenshot.
2. The agent that wrote the feature should not be the only judge of the core path. Prefer a fresh session for hostile cases and e2e when the user can open one.
3. Every bug becomes a test or a line in memory/FAILURES.md.
4. If the UI still shows data with the backend down, it is acting. Fix or file tasks; do not ship it.
5. Evidence > explanations. No log → treat the test as not run.

Test (step 8)

In order — do not start at unit tests: