compact-contextlisted

# Compact context The ledger is the primary's off-context memory. Verbose artifacts — briefs, worker reports, and diffs — already live under `state_dir` (default `~/.teammate/`), so they never need to sit in the context window. When the window fills, the primary loses the thread, not the work: everything needed to resume is on disk. This skill moves context *out* of the window deliberately, before a harness compaction forces it. The trigger is **boundaries plus explicit**, not a token threshold. Team Mate cannot measure the context window, and a guessed threshold fires at the wrong moment. Checkpoint where the state is already settled, or when the developer asks. ## The rule - **Raw artifacts stay in the ledger and are read on demand.** Never carry a whole brief, report, or diff in context: `tm report <name>` reads a worker's report, `tm diff --cwd <root>` shows the change, and `tm brief` wrote the brief that the harness subagent call already used. Pull one in only when the current step needs it, and drop it once used. - **A checkpoint carries the *state*, not the *evidence*.** The packet holds the goal, the open tasks, the plan, the decisions, and the next action — a few lines a fresh context can reload in one read. The evidence stays behind the `tm report` / `tm diff` commands. - **Checkpoint at boundaries, not continuously.** The packet is a resume point, not a log; it is overwritten each time. ## When to use - **A worker just settled** (its report is