fix(scripts): correct the RETIRED_FIELD_TYPES excluded sentence that dropping the line refutes (objectui#10070) (#10961)

Fixes #10070

Clause-②: no — a comment in a source file; no accept set or public
contract surface moves

## What was false, and where it actually lives

The sentence objectui#9803 corrected on the
`RETIRED_DASHBOARD_NODE_TYPES` entry has a twin on the
`RETIRED_FIELD_TYPES` entry of `INDIRECT_REGISTRATIONS` in
`scripts/check-doc-component-types.mjs`, in that entry's `excluded`
string. Before this change it read:

> Deciding it either way flips one switch and nothing else — DROP this
`excluded` line and the collection's keys (today `field:owner`) enter
the universe, so a document teaching `field:owner` turns GREEN; keep it
and such a document stays RED, which is what happens today.

The corrected copy on the dashboard entry reads, in part: "DROPPING this
`excluded` line does NOT re-admit `view:dashboard` — … it makes THIS
entry report `stale-indirect-registration`". The field entry's own
`reason` already stated the cause: "RETIRED_FIELD_TYPES is IMPORTED into
this file from `@object-ui/core`, so nothing here could read it anyway."

⚠️ **The fix is not in the file the dispatch expected.** The dispatch
expected the sentence in the `RETIRED_FIELD_TYPES` docblock in
`packages/core/src/utils/retired-field-types.ts`. That docblock has no
copy of it: the only matches for "flips one switch", "enter the
universe" and "turns GREEN" in the tracked tree are in the gate script's
entry. The card's own description ("the same entry's `reason` half")
points at the gate-table entry, and this PR edits that entry.
`packages/core` is untouched.

## The change

The false sentence is replaced with one sentence stating what dropping
the line does, and naming the two commands that re-derive it. The rest
of the entry is unchanged: the `WITHHELD` question and the whole
`reason` field stay as they are. The diff touches one file, +7 −3.

The text is the only thing that changes. The derivation checks
`excluded` only for truthiness (`typeof entry.excluded === 'string' &&
entry.excluded.length > 0`), and the string is still non-empty. No key,
collection, namespace or site changes, and no other entry changes.

## Measured before the sentence was written, and again on the committed
fix

Both runs deleted the entry's `excluded` property with objectstack's
`scripts/ablation-replace.mjs`. That tool requires the anchor to match,
checks the mutation on disk, and restores the file afterwards, proving
the restore with `git diff HEAD`. Each run used a lit probe doc under
`content/docs/`: one block teaching `field:owner` and one teaching
`field:user`. The probe was removed by a trap.

| reading | unmutated | `excluded` dropped |
| --- | --- | --- |
| `pnpm check:doc-types` | exit 0 | exit 1:
`packages/fields/src/index.tsx (RETIRED_FIELD_TYPES)
[stale-indirect-registration]` |
| `node scripts/regenerate-known-schema-types.mjs --check` | exit 0 |
exit 1, same finding, "nothing was written" |
| derived universe size | 648 | 648 |
| `packages/cli/src/utils/known-schema-types.ts` blob | `3447617c5d` |
`3447617c5d` |
| probe doc teaching `field:owner` | RED, `unregistered-doc-type` | RED,
`unregistered-doc-type` plus the stale finding |
| lit control `field:user` in the same probe | counted registered |
counted registered |

Base run on `06a96e9480`, re-run on `c9d3b58b50` (this PR's commit). In
both runs the mutated file hashed to the same blob, `587fcde4ffb9`, so
the sentence text has no effect on what the ablation measures. Every
restore ended with blob equal to HEAD and an empty `git diff HEAD`.

⚠️ The first ablation attempt was a no-op. `ablation-replace` refused it
because the replacement text was a substring of the anchor, restored the
file and ran nothing. The run was repeated in `--delete` mode with an
exact anchor. That second run is the one reported above.

## Verification at `c9d3b58b50`

Exit codes were captured to a file before any pipe.

- `pnpm check:doc-types` exit 0 ("Every documented component type is
registered."). `node scripts/regenerate-known-schema-types.mjs --check`
exit 0.
- `pnpm check:control-bytes` exit 0. `pnpm check:new-line-citations`
exit 0 (`VERDICT new-cross-file-line-citations: 0 new citation(s)`).
- `pnpm check:prompt-keys` exit 0 and `pnpm check:registry-bare-names`
exit 0. Both import `INDIRECT_REGISTRATIONS` or its derivation.
- `node scripts/check-changeset-presence.mjs` exit 0: "No source or
published contract of a released package changed in this range, so no
changeset is owed." No changeset is added.
- `node scripts/check-governed-queue-guard.mjs --test
scripts/check-doc-component-types.mjs` answers NOT GOVERNED.
- Tests, run from the repo root through the shared verify lock: every
test file that `git grep`s `check-doc-component-types`, plus
`scripts/__tests__/registry-bare-name-collisions.test.ts`. The result is
**26 files, 1404 tests passed** (`VERDICT command-exit 0`).
- Dispatch-named, run although the diff does not touch
`@object-ui/core`: the `@object-ui/core` dependency closure was built,
then `pnpm --filter @object-ui/core type-check` exited 0 (the script
echoed `tsc --noEmit && tsc -p tsconfig.test.json`).
`packages/core/src/utils/__tests__/retired-field-types.test.ts` passed 9
of 9.
- Lint: `pnpm exec eslint scripts/check-doc-component-types.mjs --format
json` judged 1 file with 0 errors and 0 warnings. ⚠️ This is a parse
check only. `eslint --print-config` for this file shows 0 enabled rules
and the `espree` parser with no type-aware parser options, so this diff
cannot change any other file's lint verdict. The full `pnpm lint` run is
left to CI.

## Acceptance notes

- Not changed here, noted for whoever next edits
`INDIRECT_REGISTRATIONS`: the same `excluded` string still opens with
"WITHHELD pending objectui#9717, which is open on exactly this
question". objectui#9717 was closed as completed on 2026-09-20 under
ruling letter A: retired spellings stay out of the universe. The same
stale "open question" wording appears in the
`RETIRED_DASHBOARD_NODE_TYPES` entry's `excluded` text. A comment in
`scripts/__tests__/check-doc-component-types.test.ts` also says "while
objectui#9717 is open". The withheld disposition is still correct; only
the status wording is out of date. That is a separate sentence from the
one this card names, so it is left untouched.
- The card body refers to "the triage comment on this card" for its
re-measurement. At the time of this PR, the card's thread holds only the
claim comment. The measurement above was taken fresh.

Seat session, in prose so it survives an edit:
`https://claude.ai/code/session_01EBx9rvB7dufCz4at53x35U`.

---
_Generated by [Claude
Code](https://claude.ai/code/session_01EBx9rvB7dufCz4at53x35U)_

---------

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

Author: objectstack-fleet[bot]

scripts/__tests__/check-doc-component-types.test.ts

@@ -1274,7 +1274,7 @@ describe("the indirect bypass is keyed by COLLECTION, the way the table's covera
 
   it('⭐ takes a WITHHELD declaration as coverage — no finding, and no keys either', () => {
     // The other legitimate answer to `uncovered-indirect-collection`, and the
-    // one the live table gives RETIRED_FIELD_TYPES while objectui#9717 is open:
+    // one the live table gives RETIRED_FIELD_TYPES by ruling objectui#9717 letter A:
     // the registration is declared, its keys deliberately stay OUT, and the
     // reason is written down. ⛔ The point is not that the finding goes away —
     // it is that the exclusion becomes a reviewable line instead of a silence.

scripts/check-doc-component-types.mjs

@@ -614,11 +614,15 @@ export const INDIRECT_REGISTRATIONS = [
     kind: 'object-keys',
     namespace: 'field',
     excluded:
-      'WITHHELD pending objectui#9717, which is open on exactly this question: does a RETIRED ' +
-      'TOMBSTONE SPELLING belong in a universe whose job is "does this string name a component that ' +
-      'exists"? Deciding it either way flips one switch and nothing else — DROP this `excluded` line ' +
-      'and the collection\'s keys (today `field:owner`) enter the universe, so a document teaching ' +
-      '`field:owner` turns GREEN; keep it and such a document stays RED, which is what happens today.',
+      'WITHHELD by ruling objectui#9717 letter A, which answered NO to exactly this question: does a ' +
+      'RETIRED TOMBSTONE SPELLING belong in a universe whose job is "does this string name a component that ' +
+      'exists"? ⚠️ DROPPING this `excluded` line does NOT admit the collection\'s keys (today ' +
+      '`field:owner`): without the exclusion the derivation has to read the collection literal in the ' +
+      'site file, where RETIRED_FIELD_TYPES is IMPORTED from `@object-ui/core` (the `reason` below says ' +
+      'so), so THIS entry reports `stale-indirect-registration`, `check:doc-types` and ' +
+      '`regenerate-known-schema-types.mjs --check` both exit non-zero, and a document teaching ' +
+      '`field:owner` stays RED for that different reason — admitting the spelling is NOT a one-line ' +
+      'change; re-derive this by deleting the line and running those two commands.',
     reason:
       '`registerAllFields()` registers every key of RETIRED_FIELD_TYPES a second time, last, under the ' +
       '`field:` namespace with `skipFallback: true` — a tombstone widget that renders a visible refusal ' +
@@ -638,8 +642,9 @@ export const INDIRECT_REGISTRATIONS = [
     kind: 'object-keys',
     namespace: 'view',
     excluded:
-      'WITHHELD, the same disposition and the same open question as the RETIRED_FIELD_TYPES entry ' +
-      'above (objectui#9717): does a RETIRED TOMBSTONE SPELLING belong in a universe whose job is ' +
+      'WITHHELD, the same disposition and the same ruling as the RETIRED_FIELD_TYPES entry ' +
+      'above (objectui#9717 letter A: retired spellings stay OUT): does a RETIRED TOMBSTONE SPELLING ' +
+      'belong in a universe whose job is ' +
       '"does this string name a component that exists"? Held the same way here so the two answers ' +
       'cannot drift apart. ⭐ For this collection the exclusion also carries the point of the ' +
       'retirement: objectui#8760 graded a key that passes every authoring check and fails only in ' +