fix(qa): catch the two line-pin spellings step (1) left, and document the anchor

Measured while sweeping the ledger for anchorable citations: four line pins
survived PR #13786 in two spellings its detector cannot reach — `AiChatPage
.tsx:~605-615` (the tilde INSIDE the colon form; the battery only ever pinned
`~:`) and `~L7246-7331`, which carries no colon at all. Both read exactly like
the class step (1) removed, and both sat green through it.

- the detector gains both branches, with a left AND right boundary on the `L`
  form so `SQL2019` / `L10n` / `L1` stay silent (six new rows, both directions);
- the four citations are repaired — and repairing one surfaced what the
  resolver is for: `registerRecordShareEndpoints` has not been in
  `rest-server.ts` for some time (the record-shares routes are registered
  inline, under no registrar of its own), so the citation had been naming
  nothing while reading as verified;
- README gains the anchor spelling, what is anchorable and why an unresolvable
  citation stays BARE, the shrink-never floor and its ⛔ MAINTAINER-ONLY
  authority — and the note that a red here reaches whoever runs the gate, not
  every PR (#11730);
- the battery roster floors are set from measured counts.

Refs #13788

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

Author: os-try2026

docs/qa/platform-checklist/README.md

@@ -165,6 +165,35 @@ Why this shape:
   tell a rotted one from a fresh one — so it keeps reading as "verified against source"
   while pointing somewhere else. The file plus the symbol name is already the
   load-bearing half. `check:platform-checklist` fails on any that reappear.
+- **Write the symbol as an ANCHOR where the gate can resolve one** — the file path, a
+  `#`, and the symbol, with the prose beside it unchanged:
+
+  ```text
+  packages/core/src/security/platform-admin.ts#parsePlatformAdminEmails (whole-variable refusal)
+  ```
+
+  `check:platform-checklist` resolves every anchor: the file must be in this repo and the
+  symbol must still be in it, **comments masked** — a symbol surviving only in a docblock
+  is ABSENT, because prose about a symbol is not a symbol. A symbol inside a string
+  literal counts as present: much of what this ledger cites *is* a string (capability
+  names, error codes, `sys_*` machine names). Dotted anchors resolve segment by segment.
+  This is presence-in-code, not a declaration analysis — what it catches is the rename or
+  deletion that leaves the pointer naming nothing, which is exactly the rot the line
+  numbers used to carry.
+- **A citation the gate cannot resolve stays BARE — that is honest, not a gap.** Anchors
+  are only for extensions the gate reads symbols out of (`.ts .tsx .mts .cts .js .mjs
+  .cjs .json`); an anchor on a `.md` or a `.yml` is an ERROR rather than a silent skip,
+  since a spelling that resolves nowhere is the false pointer all over again. Same for a
+  sibling-repo citation (`objectui …`) and for a file with no symbol worth naming: cite
+  the path, put the detail in prose.
+- **Anchors are shrink-never.** Deleting a `#symbol` is the silent way past any red the
+  resolver prints, so the count per family file is floored in
+  [`scripts/checklist-symbol-anchor-baseline.json`](../../../scripts/checklist-symbol-anchor-baseline.json)
+  (authored from `node scripts/check-platform-checklist.mjs --anchor-census`, which is a
+  census and not a verdict). Adding anchors never reds; ⛔ lowering a floor is
+  MAINTAINER-ONLY. ⚠️ Note what a red here reaches: `check:platform-checklist` is not
+  CI-wired (see "Operating cadence"), so it reaches whoever runs the gate — **not every
+  PR**. #11730 holds that gap.
 - **`why` is the debt marker.** A recipe exists because stock fixtures cannot demonstrate
   something — the same discipline as a coverage waiver. Landing the fixture in the
   showcase seeds proper retires the recipe; until then `why` says what is missing and

docs/qa/platform-checklist/areas/access-security.json

@@ -1111,7 +1111,7 @@
       ],
       "source": [
         "packages/rest/src/rest-route-ledger.ts#shareId (record-shares family: GET/POST /data/:object/:id/shares, DELETE .../:shareId; sharing-rules family evaluate)",
-        "packages/rest/src/rest-server.ts#registerSharingRuleEndpoints (registerRecordShareEndpoints ~L7246-7331; registerSharingRuleEndpoints evaluate ~L7477-7493)",
+        "packages/rest/src/rest-server.ts#registerSharingRuleEndpoints (the evaluate leg; the record-shares family GET/POST /data/:object/:id/shares + DELETE .../:shareId is registered inline, under no registrar of its own — #13788 measured that the registerRecordShareEndpoints this citation used to name is not in the file)",
         "packages/plugins/plugin-sharing/src/objects/sys-record-share.object.ts#recipient_type (recipient_type/recipient_id/access_level/source fields)",
         "packages/plugins/plugin-sharing/src/sharing-rule-service.ts#evaluateRule (evaluateRule → SharingRuleEvaluationResult)",
         "examples/app-showcase/src/security/sharing-rules.ts#share_key_account_qualified_contacts_with_managers (share_key_account_qualified_contacts_with_managers seeded criteria rule)",
@@ -1752,7 +1752,7 @@
         "hydration-race"
       ],
       "source": [
-        "packages/rest/src/rest-server.ts#registerSharingRuleEndpoints (registerSharingRuleEndpoints ~L7345-7494: list/create/get/delete)",
+        "packages/rest/src/rest-server.ts#registerSharingRuleEndpoints (list/create/get/delete)",
         "packages/spec/src/security/sharing.zod.ts (criteria rule authoring + match-all refusal #3896)",
         "packages/plugins/plugin-sharing/src/objects/sys-sharing-rule.object.ts + sys-record-share.object.ts",
         "objectui packages/plugins/plugin-sharing/src/sharing-plugin.ts#nav_sharing_rules (nav_sharing_rules Setup nav → sys_sharing_rule)",

docs/qa/platform-checklist/areas/platform-core.json

@@ -2163,7 +2163,7 @@
         "objectui packages/app-shell/src/context/CommandPaletteProvider.tsx (⌘/Ctrl+K — wired)",
         "objectui packages/components/src/ui/sidebar.tsx (SIDEBAR_KEYBOARD_SHORTCUT = 'b'), (the handler requires metaKey||ctrlKey — the source of the B-vs-⌘B display mismatch)",
         "objectui packages/app-shell/src/layout/chatDockState.ts (matchChatDockShortcut — ⌘/Ctrl+Shift+I, composer-safe)",
-        "objectui packages/app-shell/src/console/ai/AiChatPage.tsx:~605-615 (matchAiChatShortcut — ⌘⇧O/⌘⇧S, PAGE-scoped)",
+        "objectui packages/app-shell/src/console/ai/AiChatPage.tsx (matchAiChatShortcut — ⌘⇧O/⌘⇧S, PAGE-scoped)",
         "repo-grep evidence for the five dead accelerators: no handler for ⌘/ / N / R / ⌘E / ⌘D anywhere in app-shell, console or components (the only near-misses are page-scoped: ApprovalsInboxPage's plain `r` quick-decide and useDebugMode's Ctrl+Shift+D — neither matches an advertised accelerator)"
       ],
       "history": [

scripts/check-platform-checklist.mjs

@@ -764,12 +764,12 @@ const BATTERY_SOURCE_LINE_CITATIONS = 'selfTestSourceLineCitations: the `:NNN` r
 const BATTERY_SYMBOL_ANCHORS = 'selfTestSymbolAnchors: the anchor detector, the resolver and the floor';
 
 const SELF_TEST_BATTERIES = Object.freeze({
-  [BATTERY_TRAP_VOCABULARY]: 0,
-  [BATTERY_PROVISIONING_USE]: 0,
-  [BATTERY_UNREFERENCED_RECIPES]: 0,
-  [BATTERY_META_CALL_SPELLING]: 0,
-  [BATTERY_SOURCE_LINE_CITATIONS]: 0,
-  [BATTERY_SYMBOL_ANCHORS]: 0,
+  [BATTERY_TRAP_VOCABULARY]: 22,
+  [BATTERY_PROVISIONING_USE]: 34,
+  [BATTERY_UNREFERENCED_RECIPES]: 19,
+  [BATTERY_META_CALL_SPELLING]: 53,
+  [BATTERY_SOURCE_LINE_CITATIONS]: 19,
+  [BATTERY_SYMBOL_ANCHORS]: 29,
 });
 const SELF_TEST_BATTERY_FLOOR = 6;
 
@@ -1283,8 +1283,17 @@ export const NEIGHBOURING_MAP: Readonly<Record<string, string>> = Object.freeze(
 // silent — HTTP status (`status:409`), config literals (`{maxRetries:3}`),
 // ports (`http://localhost:3000`), clock times (`08:00`, `...T00:00:00Z`) and
 // JSON quoted in prose (`{"scannedTypes":1}`). Each is pinned below.
+//
+// A THIRD branch was added by #13788, measured rather than reasoned: sweeping
+// the ledger for anchorable citations turned up four line pins the two
+// branches above do not reach — `AiChatPage.tsx:~605-615` (the tilde INSIDE
+// the colon form, where the battery only ever pinned `~:`) and the `~L7246-7331`
+// spelling, which carries no colon at all. Both read exactly like the class
+// step (1) removed, and both sat green through it. The `L` form needs its own
+// left boundary so an identifier ending in a capital L before digits
+// (`SQL2019`) is not read as a line pin.
 const SOURCE_LINE_CITATION =
-  /(?:\.(?:ts|tsx|mts|cts|js|mjs|cjs|json|jsonc|md|mdx|ya?ml|sql|css|html|sh|py|toml)|(?<![A-Za-z0-9_"])):\d+(?:-\d+)?/g;
+  /(?:\.(?:ts|tsx|mts|cts|js|mjs|cjs|json|jsonc|md|mdx|ya?ml|sql|css|html|sh|py|toml)|(?<![A-Za-z0-9_"])):~?\d+(?:-\d+)?|(?<![A-Za-z0-9_])~?L\d{2,}(?:-\d+)?(?![A-Za-z0-9_])/g;
 
 /**
  * @param {string} text
@@ -1322,6 +1331,11 @@ function selfTestSourceLineCitations() {
   t('C5 an approximate `~:` citation is caught', n('computeAuthGate ~:5084-5160') === 1);
   t('C6 a comma/slash-chained run is caught in full', n('storage-routes.ts:241-243,:255,:267') === 3);
 
+  // FIRES — the two spellings #13788 measured still in the ledger after step (1).
+  t('C7 a colon-TILDE citation is caught — the tilde inside the colon form', n('AiChatPage.tsx:~605-615') === 1);
+  t('C8 a `~L` line pin is caught, colon or no colon', n('registerRecordShareEndpoints ~L7246-7331') === 1);
+  t('C9 a bare `L` line pin is caught', n('the evaluate leg L7477-7493') === 1);
+
   // STAYS SILENT — the neighbours that share the colon-then-digit shape.
   t('S1 an HTTP status in prose is not a citation', n("thrown {code:'DELETE_RESTRICTED', status:409}") === 0);
   t('S2 a config literal is not a citation', n('retry {maxRetries:3, backoffMs:1000}') === 0);
@@ -1330,6 +1344,9 @@ function selfTestSourceLineCitations() {
   t('S5 JSON quoted in prose is not a citation', n('a 200 {"scannedTypes":1,"stats":{}}') === 0);
   t('S6 an ADR section reference is not a citation', n('ADR-0025 §3.3 and #13479') === 0);
   t('S7 the README placeholder spelling of the ban is not itself a citation', n('never pin `file.ts:NNN` or a bare `:NNN`') === 0);
+  t('S8 a capital L ending an identifier before digits is not a line pin', n('SQL2019 and a TTL3600 budget') === 0);
+  t('S9 an i18n-style token is not a line pin', n('the L10n bundle') === 0);
+  t('S10 a one-digit `L` reference is not a line pin — the floor is two digits', n('lane L1 of the queue') === 0);
 
   citationsReachedVerdict = true;
   return { failures, checked };

scripts/checklist-symbol-anchor-baseline.json

@@ -2,6 +2,7 @@
   "$comment": "Symbol-anchor floor for docs/qa/platform-checklist/ — the shrink-never population of `path/to/file.ts#symbol` citations that scripts/check-platform-checklist.mjs resolves against real source. Authored from `node scripts/check-platform-checklist.mjs --anchor-census` (#13788, step (2) of #13482's ruling). Each entry is the count of anchors that RESOLVED in that family file; adding anchors is ordinary work and never reds. A count that falls below its floor means citations gave up the one half this gate can read, which is the silent remedy every red here would otherwise have.",
   "$authority": "⛔ MAINTAINER-ONLY: lowering a floor is a maintainer's call. Retiring items legitimately removes anchors — that is the case a maintainer rules on, per instance, and never the author's way past a red.",
   "floors": {
+    "README.md": 1,
     "areas/access-security.json": 44,
     "areas/ai.json": 18,
     "areas/api-backend.json": 41,