catchup

1Brief the human in plain language from live project state.
2 
3## Goal
4 
5`catchup` restores the owner's understanding before the next move is decided. Long agent cycles coin words, rename files, run experiments, and make decisions faster than the owner can follow. Read live project state and return a briefing someone with no retained context can act on, so the next decision rests on current facts.
6 
7## Workflow
8 
91. Read live state only: recent file modification times, version-control history and diffs, plan and state docs, re0-memo notes, and task boards. Never brief from conversation memory alone; memory is what drifted.
102. Anchor on the human's last message, judgment, or commit. Cover changes after that point; assume earlier material is known and leave it out. When the human asks where the work stands against a goal (a thread goal, an objective in the plan, an OKR file), read that goal too, and take each item's measured standing from the records that measure it, such as the latest re0-memo; an item no record measures is reported as not measured, never estimated, and a standing carries the date its record measured it, so an old measurement reads as old.
113. Compose in decision order, not chronological order:
12   - **Needs you**: decisions, judgments, or inputs only the human can give, each actionable without opening another file.
13   - **Changed while you were away**: outcomes, not process. "The plan's scoring rule was replaced" beats "I ran three analysis passes."
14…