require a counter row to say what does not count

Four of these counters were re-scoped the first time anything tested them, and
every re-scoping was a sentence about what had been wrongly included: transforms
were counting parse-phase work goldmark already orders, views were counting
output formats, effects nearly counted an in-memory swap, extensions counts
packages rather than goldmark's own extensions.

So the fix is not another counter but a required shape. The table gains a fifth
column and verify.sh fails on a row that leaves it empty — watched naming the
offending row. Checked by shape rather than by wording, because a gate that
demands a phrase gets the phrase and not the thinking.

Writing the exclusion up front is the cheapest way to find out whether a counter
measures a mechanism or a symptom, and all eight rows could state one, which is
the first evidence that the counters are now scoped right.

Queue entry G6.

HARNESS.md

@@ -141,6 +141,11 @@ Then `docs/README.md` for whichever topic you are actually here for.
 
 ## Why the pieces exist
 
+**Every counter row says what does *not* count**, and `verify.sh` fails on a row that leaves that column
+empty (ADR-0070). Four counters had to be re-scoped the first time anything tested them, and each fix was a
+sentence about what had been wrongly included — so the sentence is now required up front. A counter that
+cannot name an exclusion is measuring a symptom.
+
 **Counters in `docs/state.md`** turn "no abstraction before its second use" into arithmetic. Every
 threshold lives in that one table and nowhere else. The agent cannot argue a pipeline into existence
 one transform early — it writes the next one inline and lets the count force the extraction. Most