test(scripts): batch 10c pilot (Tier C) — per-entry recipe-A partitions for check-durability-degradation-log-level (#15329)

* test(scripts): per-entry recipe-A floors for check-durability-degradation-log-level

This file is two recipe-A self-tests sharing a module: `selfTest()` and
`selfTestReadSeams()` each own a literal `cases` table, a driving loop and a
verdict, and one `--self-test` dispatch runs both. `failures === 0` was each
entry's only success condition, so "every case held" and "the cases never ran"
printed the same line.

One module-level `SELF_TEST_BATTERIES`, partitioned per entry (an object per
entry, keys = that entry's own row labels verbatim, floor 1 each), a size pin
per partition in one frozen map (63 / 57, measured on a run) and the roster
total pinned (120). `registerCase(name)` is the first statement of each driving
loop; each entry's verdict site calls the shared floor over ONLY its own
partition, before its success line, and every refusal names the partition and
the row. Cross-checked both ways per partition, with duplicate refusal within a
partition and across partitions.

The two tables shared one row label; it is namespaced in the read-seam table
(`... judged for a READ seam ...`) rather than refused, and the site says why.
No assertion condition, message or argument is changed; the only deleted lines
are the two red verdict lines, reworded to recipe A's `N failure(s) (cases and
floor)`. Both green lines are byte-identical, and the flag handshake
(`selfTestReachedVerdict` / `readSeamsReachedVerdict`) is untouched and stays
orthogonal to the floor.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012zGPuVVX3deAx9LdjK8jCk

* tooling(pm): classify the new compound self-test name in COMPOUND_ANCHOR_LEDGER

`checkSelfTestFloor` in `check-durability-degradation-log-level.mjs` is a
compound self-test name, so the anchor fires on it and
`check:pm-dispatch-gates` refuses it until the ledger classifies it. It is
self-test-only machinery reached from the two verdict sites, not production
code the anchor caught by accident, so it is classified `accidental: false`.

Classified rather than renamed, as the ledger's own maintenance note requires:
the row is the record, and a name chosen to dodge the anchor is the next one
nobody notices.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012zGPuVVX3deAx9LdjK8jCk

---------

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

Author: claude[bot]