ci(dispatch-gates): add the seventh no-check-families row for the declaration beside it

The declaration added to `checklist-status.yml` is the SEVENTH in the tree, and
the live-marker census pins the roster by NAME with an exact match — so adding
one reds it. That is the pin working, and its own comment says why it is a
roster and not a count: "a bare count reddens for a seventh declaration without
saying which six were already read". The maintenance it forces is this commit.

⛔ The two halves are atomically coupled and cannot be split across PRs: the
declaration without this row reds the census, and this row without the
declaration reds it too (the census reads the live files). They land together
or `dispatch-gates --self-test` is red on `main` either way.

Also bumps the companion `liveMarkerCensus.length === 6` guard, which is the
count half of the same reading, and the prose that states it.

Measured on this head: `node scripts/pm/dispatch-gates.mjs --self-test`
EXIT=0, 1866 cases pass (it was EXIT=1, 2 of 1866, with the declaration alone).
The three rows this touches all read green: the paths-filtered guard at
"gaps: none", the census at seven rows, and "every live reason ENDS on its own
marker line (cut: none)".

Claude-Session: https://claude.ai/code/session_01AmH9bKvGoLjiY86Q4Z3og2
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

scripts/pm/dispatch-gates.mjs

@@ -22173,8 +22173,16 @@ function selfTest() {
   }
   const censusRows = liveMarkerCensus.map((r) => `${r.file}:${r.line} ${r.key}`).sort();
   t(
-    `the live tree carries the six declarations this card measured, and no others (${censusRows.join(' · ') || 'none'})`,
+    `the live tree carries the seven declarations measured for this census, and no others (${censusRows.join(' · ') || 'none'})`,
     censusRows.join(' · ') === [
+      // Seventh row, added with the declaration it names: `checklist-status.yml`
+      // is paths-filtered (its `pull_request:` trigger is filtered to itself) and
+      // its only working step invokes the GENERATOR `pnpm gen:checklist-status`,
+      // so it discovers no `check:` family and declares why. ⚠️ This roster is the
+      // maintenance this pin exists to force: it is NAMED rather than counted
+      // precisely so a seventh declaration reddens WITH the six already read
+      // printed beside it, and the author adds their row instead of a number.
+      '.github/workflows/checklist-status.yml:57 no-check-families',
       '.github/workflows/merged-branch-reaper.yml:212 no-check-families',
       '.github/workflows/os-create-smoke.yml:48 no-check-families',
       '.github/workflows/scaffold-e2e.yml:23 no-check-families',
@@ -22187,7 +22195,7 @@ function selfTest() {
   const censusCut = liveMarkerCensus.filter((r) => !r.whole).map((r) => `${r.file}:${r.line} ${r.key}`);
   t(
     `every live reason on those markers ENDS on its own marker line (cut: ${censusCut.join(', ') || 'none'})`,
-    censusCut.length === 0 && liveMarkerCensus.length === 6,
+    censusCut.length === 0 && liveMarkerCensus.length === 7,
   );
   t(
     'and every one of them carries a non-empty reason — whole is not the same claim as present, and both are owed',