docs(dogfood): refresh the last stale runtime-ledger population claim

`authz-ledger-population.baseline.ts`'s header still stated the runtime route
ledger at 80 rows. The number moved to 82 with the two operator run-lifecycle
rows; the date the measurement was taken is kept, because the key arithmetic
the sentence goes on to state (40 minted, 6 classified, 34 baselined) is the
part that did not move — both new rows sit under the already-classified
`/automation` domain.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012zTkyNHJ7TkuN2oXtP5x37

Author: claude

packages/qa/dogfood/test/authz-ledger-population.baseline.ts

@@ -59,7 +59,9 @@
  * Ledger-sourced population keys with no classifying matrix row.
  *
  * MEASURED 2026-08-31 against `rest-route-ledger.ts` (94 rows / 19 families)
- * and `route-ledger.ts` (80 rows / 21 domains): 40 keys minted, 6 classified
+ * and `route-ledger.ts` (80 rows / 21 domains — 82 since the two operator
+ * run-lifecycle rows landed, both under the already-classified `/automation`
+ * domain, so the key arithmetic below is unmoved): 40 keys minted, 6 classified
  * by rows that already pin the same surface through the probe table, 34 here.
  *
  * ⛔ SHRINK-ONLY. See rules 1–4 above; the test enforces all four.