docs(pm): express the self-test's size as a floor, not a reading (#13962)

The entry-guard docblock carried "this file carries it at 334" — a frozen
reading of a number that moves on most edits to this file. It had drifted to
1073 by the time anyone looked: a factor of 3.2.

Writing today's number would re-freeze the same defect one value later, so the
figure is now a FLOOR ("more than ten times" #9897's 77), stated as a floor on
purpose and pointing at `--self-test`'s `cases.length` as the live reading.

Measured before choosing the shape: across all 83 commits that have touched
this file, the assertion count went up 72 times, held flat 10 times, and has
never once gone down (14 -> 1047 static call sites; 1073 at runtime after the
file-local loop expansions). A floor is safe precisely because of that.

The neighbouring 77 is left frozen deliberately — it is anchored to PR #9897
and was true there (70 static assertions at that commit), so it is a historical
fact rather than a live count. The sentence now says so explicitly.

No behaviour change: the `invokedDirectly` guard and the self-test are
untouched. `--self-test` still reports 1073 cases pass.


Claude-Session: https://claude.ai/code/session_01Pk26oZ12t5N1hwGW1m1MgC

Co-authored-by: Claude <noreply@anthropic.com>

Author: claude[bot]

scripts/pm/dispatch-gates.mjs

@@ -13740,10 +13740,16 @@ const invokedDirectly = isEntrypoint(import.meta.url);
  * running its own `--self-test` fired all of THIS file's assertions inside it,
  * printing a second summary line and putting an unrelated file's failures on
  * the importer's exit code. That is the same defect PR #9897 fixed in
- * `check-governed-merges.mjs` at 77 assertions; this file carries it at 334. A
- * self-test is a mode of the file being RUN, never a side effect of importing
- * it, and a shared module that exits on import is a shared module nobody can
- * share.
+ * `check-governed-merges.mjs`, which carried 77 assertions at that PR; this
+ * file carries it at more than ten times that many. That multiple is a FLOOR,
+ * and it is written as one on purpose. The live figure is whatever
+ * `--self-test` prints from `cases.length`; it moves on most edits to this
+ * file, and over this file's history it has never once gone down — so a floor
+ * stays true where a reading rots. A reading stood here before and had drifted
+ * by more than a factor of three before anyone repaired it, so do not
+ * "helpfully" refresh this back into one. A self-test is a mode of the file
+ * being RUN, never a side effect of importing it, and a shared module that
+ * exits on import is a shared module nobody can share.
  *
  * The guard is ONE site wrapping the whole chain, not a condition repeated per
  * branch: a branch added inside it later cannot forget to carry it.