bank-the-suitelisted

# Bank the Suite ## The failure mode this fixes The agent changes a module, runs the three tests next to it, sees green, and moves on. Four tasks later the full suite runs for the first time and 23 tests are red — and now nobody knows *which* of the four changes broke them, the context that would have made the diagnosis cheap is gone, and the "quick fix" becomes an archaeology dig. The inverse failure is just as common: the suite *is* run, 14 tests fail, and the report says "some pre-existing failures, probably unrelated." Probably. Unverified red is a debt that compounds — every subsequent change hides behind it. This skill makes the full suite a **bank**: after each unit of work you deposit a verified green state, so the next unit starts from known-good and any new red has exactly one suspect. ## When to Use This Skill - A feature, fix, or refactor just landed and the next task is queued - Only the tests adjacent to the change were run - You're about to compact context, hand off, or end the session — the next session needs a trusted baseline - The suite is slow and keeps getting skipped because "it takes 20 minutes" - A report says failures are "pre-existing" or "unrelated" without naming them **Don't use when:** the repo has no meaningful suite (then the gap *is* the finding — say so), or mid-exploration when nothing has landed yet. Don't block a one-character doc fix on a 20-minute suite — scale the gate to the blast radius. ## Instructions ### 1. Establish the b