refusing-busyworklisted

# Refusing busywork Ceremony is the tax a long-horizon loop pays every single iteration, and it compounds exactly like interest. A full suite run that was never needed costs the same on turn 400 as on turn 4 — except by turn 400 it has been paid 400 times. This skill owns what not to do. It does not judge what a check proves once you have run it. Most contributor guides say the opposite of this skill. They tell you to run everything, keep everything, and shorten everything. Each of those is a reflex standing in for a judgment, and the judgment is cheap once you know which one to make. Read `.ledger.yml` for this project's lanes, hooks, and what CI already owns. ## Run the narrowest check that would fail There is no universal local baseline beyond what the hooks already do. For any change, the question is: **which check would actually fail if this change were wrong?** Run that one. Add broader checks only for surfaces the change genuinely reaches. - **Never default to the full suite.** Leave repository-wide coverage to CI unless the change is genuinely cross-cutting, or the user asked for it. - **Never repeat a passing check because a commit or push follows.** In particular, do not run a static check immediately before pushing solely to duplicate a hook that already ran it — read `hooks` in the adapter and skip what it lists. - **Test selection is not coverage selection.** Running the affected tests and measuring coverage on the affected source are two different decisio