secondary-text-audit

# Secondary-Text Audit Extract every piece of subordinate copy in a surface and put each one on trial. The ruleset's premise is that **secondary text defaults to absent**: it exists only to carry information the user needs before acting that the label, the control's shape, and the surrounding context do not already give them. Most shipped secondary text describes what something *is*, which the label already did. That text goes. The output is a verdict table, not prose commentary. Every row resolves to `keep`, `rewrite`, or `delete`, and every `rewrite` carries its replacement string. ## Design philosophy (read this — it shapes every judgment call) 1. **Delete is the expected majority outcome.** This is the inversion that makes the skill useful. An audit that keeps most of what it finds has not applied the ruleset; it has admired the copy. If your table is mostly `keep`, re-run the category test on every `keep` row and mean it. 2. **Uncertainty resolves to `delete`.** When a string sits between `delete` and `rewrite`, choose `delete` — the primary label almost always suffices. This is the opposite of the precision-over-recall bias in `ux-semantics-audit`, and deliberately so: there, a false positive makes an agent break working UI; here, the cost of a wrong `delete` is one line of copy, and the cost of a wrong `keep` is permanent noise on the screen. 3. **Judge the rendered pair, never the key name.** A verdict needs the label the user actually s...