Month two: what it remembers

Every run writes down what it decided and what it assumed. That record is the reason the second month is better than the first.

Ask	Command
Why is this diff like this?	/hyperpower:why <run-id>
Why is the code like this, months later?	/hyperpower:decisions <query>
Why does it keep doing that?	/hyperpower:rules

why is the one to reach for when you are reviewing a change you did not write. It prints each decision with its reason and every assumption with its status, so you can see what the run took on faith rather than guessing.

rules is CODEBASE_RULEBOOK.md: things this repo learned the hard way. A mistake that repeats gets promoted into a rule, and a rule that has prevented nothing in twenty runs gets dropped. --unused shows the latter.

When a run stops

A blocking check that the fix loop cannot clear stops the run. Fix the cause, then continue from where it stopped instead of starting over:

/hyperpower:resume <run-id> --from gates

It shows which files changed since each step before it reruns anything, so a resume onto a tree that moved underneath you is visible rather than silent.