retrolisted

# Retro Never re-derive a dead end twice. Record only knowledge future work cannot recover cheaply. ## 1. Scan the session Ask: - What took the longest? - Which attempts **failed**, and why? - What plausible approach was wrong? - What environment/version/flag surprised us? - What had to be rediscovered? Also read the discipline report when installed: prefer local `luciazero discipline --project . --json`, then the checkout/package CLI. Use `npx` only when package resolution is explicitly allowed. A nudge or block is evidence, not cause; state any diagnosis as `likely` until repo evidence confirms it. ## 2. Filter hard Keep only what reading the code cannot tell a future agent: - **Null results**: measured no gain or broke another property. - **Footguns**: an apparently correct action silently breaks something. - Environment facts, ordering constraints, and why a tempting path is wrong. Reject diff/history summaries, session-only values, and Anything a `grep` or `--help` answers. If nothing qualifies, stop: an empty retro is a valid result. ## 3. Route it, then write it - **Anyone who clones the repo:** code/build behavior and disproven approaches. A debugged failure goes to `docs/lessons.md`: ``` ## <greppable symptom; include exact error string> cause: <root cause> | proven-by: `<command>` | fix: <what fixed it> | date: YYYY-MM-DD ``` - **True in every repository:** append one deduplicated line to configured `luciazero-heuristics.md` under `${CLAUDE_