diff --git a/.changeset/10039-publish-drafts-advisories.md b/.changeset/10039-publish-drafts-advisories.md
index b239a9b27d..a5e02996f2 100644
--- a/.changeset/10039-publish-drafts-advisories.md
+++ b/.changeset/10039-publish-drafts-advisories.md
@@ -5,7 +5,7 @@
 The AI build bar, the Studio workbench and the chat transcript's draft cards report the runtime authoring gate's per-draft advisories (objectui#10039)
 
 `POST /packages/:id/publish-drafts` has answered `advisories` on each
-`published[]` element since objectstack#9343 landed, and objectui#6965 built the
+`published[]` element since objectstack#9343 landed, and `ce986aafc` built the
 seam that reports them — `MetadataClient.publishPackageDrafts`, which emits one
 advisory event per advised element into the sink, renderer and wording the save
 and single-item publish doors use. Three app-shell call sites were still firing
@@ -14,7 +14,7 @@ nobody: `console/ai/PendingDraftsBar`, `views/studio-design/StudioDesignSurface`
 and the chat draft card's publish handler in `console/ai/AiChatPage`. Each of the
 three now takes its client from `useMetadataClient` and calls that method, which
 is the whole change — the advisory toast is the client's, so all three surfaces
-report identically to the two objectui#6965 routed, with no new UI shape.
+report identically to the two `ce986aafc` routed, with no new UI shape.
 
 What moves with the route, at all three:
 
diff --git a/.changeset/10803-dead-citation-sweep-fourth-batch.md b/.changeset/10803-dead-citation-sweep-fourth-batch.md
new file mode 100644
index 0000000000..370cdd3129
--- /dev/null
+++ b/.changeset/10803-dead-citation-sweep-fourth-batch.md
@@ -0,0 +1,21 @@
+---
+---
+
+Comment-only in `@object-ui/app-shell`, `@object-ui/cli`, `@object-ui/components`,
+`@object-ui/core`, `@object-ui/data-objectstack`, `@object-ui/fields`, `@object-ui/i18n`,
+`@object-ui/plugin-chatbot`, `@object-ui/plugin-grid`, `@object-ui/plugin-kanban`,
+`@object-ui/plugin-timeline` and `@object-ui/types`, plus the private
+`@object-ui/test-support`: docblocks and code comments that cited objectui issues which
+answer 404 now cite the commit that landed each change, as a 9-character sha, the ruling
+by its date where the sentence cites a ruling, or a live pointer the sentence already
+named, and where nothing answers they name the card by role (objectui#10803, the fourth
+batch). One bare number that was a sister-repo pull request is now written
+`objectstack#6942`. Some of these docblocks reach the emitted `.d.ts` and `.js`; none of
+them moves a claim, and none of these comment edits changes a code or type token. No
+published behaviour changes through them, so this declares no release. The runtime text
+the sweep touches, two tombstone guidance strings and two zod `.describe()` strings in
+`@object-ui/types`, is declared on its own as a patch in
+`10803-fourth-batch-runtime-strings.md`.
+
+The same repair in the pending changesets that carried these citations is prose-only, and
+their frontmatter is byte-identical.
diff --git a/.changeset/10803-fourth-batch-runtime-strings.md b/.changeset/10803-fourth-batch-runtime-strings.md
new file mode 100644
index 0000000000..8a1cad1a5f
--- /dev/null
+++ b/.changeset/10803-fourth-batch-runtime-strings.md
@@ -0,0 +1,23 @@
+---
+'@object-ui/types': patch
+---
+
+fix(types): four more runtime strings no longer point at objectui issues that answer 404
+
+Two ADR-0049 retirement tombstones in the published zod mirrors and two runtime
+descriptions carried a pointer to an objectui issue that answers 404. A reader of a parse
+error or a zod `description` has no repository to resolve a commit against, so no dead
+pointer becomes a commit: the tombstones cite `ADR-0049` in its place, and the two
+description pointers are simply dropped (objectui#10803).
+
+- **The tombstone guidance.** The legacy `ActionSchema`'s `onSuccess` and `onFailure`
+  tombstones feed both the parse error an author reads and the `.describe()` text, and
+  each now opens `RETIRED (ADR-0049) —` in place of the dead card. Everything after the
+  dash is unchanged, so the remedy each message gives is word for word what it was.
+- **Two descriptions.** `DataTableSchema.rowActions` now ends "mirrors the boolean the
+  renderer truthiness-tests", and `DataTableSchema.cellClassName` ends "so row density has
+  to be set on both".
+
+Nothing else in any string moves, and no key, path, issue code, accept set, refusal or
+severity changes: every document that parsed before parses the same way and is refused at
+the same path with the same code.
diff --git a/.changeset/4895-retire-block-schema-family.md b/.changeset/4895-retire-block-schema-family.md
index 67af25b994..8910954ca7 100644
--- a/.changeset/4895-retire-block-schema-family.md
+++ b/.changeset/4895-retire-block-schema-family.md
@@ -49,4 +49,4 @@ the node type `SchemaRenderer` actually takes.
 `packages/types/src/blocks.ts` and `packages/types/src/zod/blocks.zod.ts` are kept as
 ADR-0049 tombstones exporting nothing, and `block-family-retired-4895.test.ts` pins every
 retired name out of them. `content/docs/blocks/block-schema.mdx` is deleted with the family,
-and objectui#7023 — the narrower validator-only fix — dissolves into this retirement.
+and the separate card for the narrower validator-only fix dissolves into this retirement.
diff --git a/.changeset/6755-field-diagnostics-i18n.md b/.changeset/6755-field-diagnostics-i18n.md
index 06b1c97359..ccc0c1b3b6 100644
--- a/.changeset/6755-field-diagnostics-i18n.md
+++ b/.changeset/6755-field-diagnostics-i18n.md
@@ -25,4 +25,4 @@ labels, gate hints and validation copy were all translated.
   not restate the spec's bounds (a hand-copied range is a second contract).
 - Not in scope, and recorded rather than folded in: `LocationField`'s third
   refusal sentence — the residue arm objectui#6715 added after the ruling was
-  written — is still a literal. objectui#6888 carries it.
+  written — is still a literal. The card behind `320374d2a` carries it.
diff --git a/.changeset/6872-app-shell-branding-title-jsdoc.md b/.changeset/6872-app-shell-branding-title-jsdoc.md
index 02fa1f1f1d..62c1c26d14 100644
--- a/.changeset/6872-app-shell-branding-title-jsdoc.md
+++ b/.changeset/6872-app-shell-branding-title-jsdoc.md
@@ -2,7 +2,7 @@
 '@object-ui/layout': patch
 ---
 
-Correct the `AppShellBranding.title` doc comment (objectui#6872). It read "Page title
+Correct the `AppShellBranding.title` doc comment. It read "Page title
 suffix (sets document.title)" while `useAppShellBranding` assigns `document.title = title`
 wholesale — nothing is appended; the caller composes the whole string (the console passes
 `"App label — Product name"`). That comment ships in `dist/index.d.ts` and is the only
diff --git a/.changeset/6888-location-residue-refusal-keyed.md b/.changeset/6888-location-residue-refusal-keyed.md
index 125bddc61c..89c1343bb4 100644
--- a/.changeset/6888-location-residue-refusal-keyed.md
+++ b/.changeset/6888-location-residue-refusal-keyed.md
@@ -4,7 +4,7 @@
 ---
 
 Key `LocationField`'s THIRD refusal sentence — the residue arm — into the locale
-packs (objectui#6888).
+packs.
 
 Typing a half that is only PARTLY a number (`12abc, 34`) is refused by
 `LocationField` with its own sentence, added by objectui#6715. objectui#6755 had
diff --git a/.changeset/6907-gantt-date-spelling-rule.md b/.changeset/6907-gantt-date-spelling-rule.md
index 78decea6dd..1a63aaf179 100644
--- a/.changeset/6907-gantt-date-spelling-rule.md
+++ b/.changeset/6907-gantt-date-spelling-rule.md
@@ -2,12 +2,12 @@
 '@object-ui/plugin-timeline': patch
 ---
 
-Spell a refused gantt date by a RULE, not by `String` (objectui#6907)
+Spell a refused gantt date by a RULE, not by `String`
 
 `spellGanttDateValue` fills the `{{value}}` hole of the unusable-gantt-date
 alert, whose job is to name the value the author wrote. Its `String(value)`
 fallback was written when nothing but `[object Object]`-shaped values could
-reach it; objectui#6905's type rule routes the whole non-date type space
+reach it; `85f6a6097`'s type rule routes the whole non-date type space
 through it, and it failed three ways — measured on `b458300ca`:
 
 - it **VANISHES**: `endDate: []` rendered "endDate is , which is not a valid
@@ -18,7 +18,7 @@ through it, and it failed three ways — measured on `b458300ca`:
   with no hint the wrapper was at fault;
 - it **THROWS**: `{ toString() { throw } }`, a throwing `Symbol.toStringTag`
   getter and `Object.create(null)` each crashed the render outright. #6759 built
-  this helper "total by construction" and #6905 made that load-bearing, but the
+  this helper "total by construction" and `85f6a6097` made that load-bearing, but the
   type gate only stopped `new Date` from throwing — `String(value)` handed
   control to author code one line later, so the crash class moved into the
   speller instead of going away.
diff --git a/.changeset/6921-cellclassname-cell-population-pins.md b/.changeset/6921-cellclassname-cell-population-pins.md
index a47e7f3535..44b83712ae 100644
--- a/.changeset/6921-cellclassname-cell-population-pins.md
+++ b/.changeset/6921-cellclassname-cell-population-pins.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-Test-only and comment-only change (objectui#6921); no published behaviour changes.
+Test-only and comment-only change; no published behaviour changes.
 
 Pins, in the rendered DOM, which body cells the SCHEMA-level `cellClassName` on
 `DataTableSchema` reaches: exactly the three utility cells (selection, row-number,
diff --git a/.changeset/6931-tombstone-guidance-remainder.md b/.changeset/6931-tombstone-guidance-remainder.md
index cb29f6bcdc..bb7cd077e5 100644
--- a/.changeset/6931-tombstone-guidance-remainder.md
+++ b/.changeset/6931-tombstone-guidance-remainder.md
@@ -2,8 +2,7 @@
 '@object-ui/types': patch
 ---
 
-The remaining eleven ADR-0049 tombstones now refuse with their remediation text
-(objectui#6931).
+The remaining eleven ADR-0049 tombstones now refuse with their remediation text.
 
 objectui#6105 converted nine tombstones on `StaticTableColumnSchema` to
 `retirementTombstone()`, which writes a guidance string ONCE into both
diff --git a/.changeset/6940-rowactions-boolean-mirror.md b/.changeset/6940-rowactions-boolean-mirror.md
index 845de6de5b..e159176783 100644
--- a/.changeset/6940-rowactions-boolean-mirror.md
+++ b/.changeset/6940-rowactions-boolean-mirror.md
@@ -3,7 +3,7 @@
 ---
 
 `DataTableSchema.rowActions` validates as the boolean it has always been declared to be
-(objectui#6940, maintainer ruling 2026-09-02, director seat summon #8, option A).
+(maintainer ruling 2026-09-02, director seat summon #8, option A).
 
 The hand-written zod mirror in `zod/data-display.zod.ts` declared
 `rowActions: z.array(z.any()).optional()`. Every other face of the same key says
diff --git a/.changeset/6958-visiblewhen-clears-the-field-it-hides.md b/.changeset/6958-visiblewhen-clears-the-field-it-hides.md
index 4042a06dea..2a5b74c2b9 100644
--- a/.changeset/6958-visiblewhen-clears-the-field-it-hides.md
+++ b/.changeset/6958-visiblewhen-clears-the-field-it-hides.md
@@ -3,7 +3,7 @@
 ---
 
 A field its own `visibleWhen` hides is now cleared, so it stops carrying a stale value
-to the server (objectui#6958).
+to the server.
 
 **Breaking, deliberately.** Until now a field the form renderer hid because the field's
 own `visibleWhen` (or its deprecated view-level sibling `visibleOn`) resolved FALSE kept
diff --git a/.changeset/6965-batch-publish-advisories.md b/.changeset/6965-batch-publish-advisories.md
index 14e433cdff..f9a49cd103 100644
--- a/.changeset/6965-batch-publish-advisories.md
+++ b/.changeset/6965-batch-publish-advisories.md
@@ -4,7 +4,7 @@
 ---
 
 Studio's "publish whole app" reports the runtime authoring gate's per-draft
-advisories (objectui#6965; server half objectstack#9343).
+advisories (server half objectstack#9343).
 
 `POST /packages/:id/publish-drafts` began answering `advisories` on each
 `published[]` element when objectstack#9343 landed, but the author publishing a
diff --git a/.changeset/7004-cli-root-path-line.md b/.changeset/7004-cli-root-path-line.md
index 1b9708c16d..a6166e17fb 100644
--- a/.changeset/7004-cli-root-path-line.md
+++ b/.changeset/7004-cli-root-path-line.md
@@ -2,8 +2,7 @@
 '@object-ui/cli': patch
 ---
 
-`objectui validate` now says when a validation issue sits at the document root
-(objectui#7004, mechanical half).
+`objectui validate` now says when a validation issue sits at the document root.
 
 The printer guarded its Path line with `issue.path.length > 0`, so an issue at
 `path: []` printed no Path line at all — silent in exactly the case a reader
@@ -24,5 +23,5 @@ Every reported issue now carries a Path line; a root-level one reads
 
 Scope: the printer still reads only top-level issues. Whether a failing union
 should also surface its per-arm diagnoses — and if so which arm's — is an
-author-facing diagnostic contract left open on objectui#7004 for a maintainer
+author-facing diagnostic contract left open for a maintainer
 ruling, and is deliberately not decided here.
diff --git a/.changeset/7004-cli-union-arm-selection.md b/.changeset/7004-cli-union-arm-selection.md
index 690dede100..878891bc10 100644
--- a/.changeset/7004-cli-union-arm-selection.md
+++ b/.changeset/7004-cli-union-arm-selection.md
@@ -3,14 +3,14 @@
 ---
 
 `objectui validate` now prints the failing union arm the document selected, instead of a
-bare "Invalid input" (objectui#7004, maintainer ruling 2026-09-02 — option B).
+bare "Invalid input" (maintainer ruling 2026-09-02 — option B).
 
 `safeValidateSchema` checks a document against `AnyComponentSchema`, a `z.union`. When a
 document matches no arm, Zod reports ONE top-level issue — `invalid_union` · `Invalid
 input` · path `(root)` — and hangs every arm's real diagnosis off that issue's `errors`
 array, which nothing read. So a menu whose item used the divider spelling retired in
 objectui#6523 printed a bare verdict on the whole document, while the remediation text
-objectui#6931 wrote into that arm sat one level down, unreachable.
+`8063bcbdc` wrote into that arm sat one level down, unreachable.
 
 **What is printed now.** When the top-level issue is a failing union:
 
diff --git a/.changeset/7007-relatedlist-schema-chain-gate.md b/.changeset/7007-relatedlist-schema-chain-gate.md
index a19c1bed1f..07246878fc 100644
--- a/.changeset/7007-relatedlist-schema-chain-gate.md
+++ b/.changeset/7007-relatedlist-schema-chain-gate.md
@@ -20,12 +20,12 @@ fails at `:123` (`expected true to be false`) and at `:153` (`expected <button>T
 to be null`), with the stored-column controls present in both blocks, reproducing the race.
 The new spelling passes under the same delay.
 
-Each block KEEPS its existing gate and ADDS the second one (the objectui#6959 precedent and
+Each block KEEPS its existing gate and ADDS the second one (the `c0c436db8` precedent and
 its trap): the first gate proves the view committed with rows at all, which is what keeps
 `queryBy…).toBeNull()` from passing vacuously; the second proves the schema the verdict is
 derived from has landed. Trading one for the other would have left the block blind on
 whichever side it dropped.
 
 The gate is not `expect(getObjectSchema).toHaveBeenCalled()` — a mock CALL is issued one
-resolution before its value reaches state, which is the trap #6959 recorded. It awaits the
+resolution before its value reaches state, which is the trap `c0c436db8` recorded. It awaits the
 promise the component itself awaited and flushes the commit through `act`.
diff --git a/.changeset/7008-field-edit-widget-host-plumbing.md b/.changeset/7008-field-edit-widget-host-plumbing.md
index fe56d13482..268b97e64d 100644
--- a/.changeset/7008-field-edit-widget-host-plumbing.md
+++ b/.changeset/7008-field-edit-widget-host-plumbing.md
@@ -3,7 +3,7 @@
 '@object-ui/plugin-kanban': patch
 ---
 
-`FieldEditWidget` now delivers the NON-DOM half of the contract it declares (objectui#7008).
+`FieldEditWidget` now delivers the NON-DOM half of the contract it declares.
 
 objectui#7009 made the factory forward its declared DOM pass-through block. The rest of
 `FieldWidgetComponentProps` was still dropped: `error`, `onUploadingChange`, and the whole
diff --git a/.changeset/7025-nonoptional-enum-cast.md b/.changeset/7025-nonoptional-enum-cast.md
index cdf00e8bcf..4c9fd621b8 100644
--- a/.changeset/7025-nonoptional-enum-cast.md
+++ b/.changeset/7025-nonoptional-enum-cast.md
@@ -1,13 +1,13 @@
 ---
 ---
 
-Internal test-only change, no user-visible behaviour (objectui#7025).
+Internal test-only change, no user-visible behaviour.
 
 The SIXTH spelling of the Zod-internals reader hazard objectui#5872 catalogues:
 9 spec-parity test files in 7 packages cast an enum node NON-optionally to an
 options-bearing shape and read `.options` straight off it. They converge onto
-`@object-ui/test-support`'s `enumOptions(node)` — the same walk objectui#6924
-converged the optional-cast family onto in PR #7024.
+`@object-ui/test-support`'s `enumOptions(node)` — the same walk PR #7024
+converged the optional-cast family onto.
 
 Unlike that family, these sites failed LOUDLY (spreading `undefined` throws), and
 the shared reader deliberately answers `[]` rather than raising. So every site
diff --git a/.changeset/7077-button-group-retire-authored-surface.md b/.changeset/7077-button-group-retire-authored-surface.md
index a645e7941a..9be9b6c417 100644
--- a/.changeset/7077-button-group-retire-authored-surface.md
+++ b/.changeset/7077-button-group-retire-authored-surface.md
@@ -3,7 +3,7 @@
 ---
 
 `button-group` honors per-button `disabled`, and the catalog stops authoring 29 keys
-nothing reads (objectui#7077, maintainer ruling 2026-09-04, decision batch #25).
+nothing reads (maintainer ruling 2026-09-04, decision batch #25).
 
 **The renderer change.** `ButtonGroupButton` declares `disabled?: boolean` and the
 renderer read it nowhere — it mapped `schema.buttons` to `Button` elements passing
diff --git a/.changeset/7079-schema-reference-base-props.md b/.changeset/7079-schema-reference-base-props.md
index dfcfe3b8e3..e043c840de 100644
--- a/.changeset/7079-schema-reference-base-props.md
+++ b/.changeset/7079-schema-reference-base-props.md
@@ -2,7 +2,7 @@
 ---
 
 Docs only — the canonical `BaseSchema` "Common Properties" table in
-`content/docs/api/schema-reference.md` (objectui#7079). No package source, no
+`content/docs/api/schema-reference.md`. No package source, no
 published contract and no runtime behaviour is touched, hence the empty
 declaration; `apps/site` is `private: true` and sits in `.changeset/config.json`'s
 `ignore` list, so nothing under `content/` ships from this change.
diff --git a/.changeset/7087-disabled-twin-symmetry.md b/.changeset/7087-disabled-twin-symmetry.md
index a4e1a68a54..375151038e 100644
--- a/.changeset/7087-disabled-twin-symmetry.md
+++ b/.changeset/7087-disabled-twin-symmetry.md
@@ -3,8 +3,8 @@
 ---
 
 `disabled` accepts a predicate string — `boolean | string`, the `BaseSchema` union — on
-the 18 concrete schemas that used to narrow it back to `boolean` (objectui#7087,
-maintainer ruling 2026-09-01: option 1, scoped to `disabled`).
+the 18 concrete schemas that used to narrow it back to `boolean`
+(maintainer ruling 2026-09-01: option 1, scoped to `disabled`).
 
 `visible` and `disabled` are twins: objectui#4581 widened both on `BaseSchema` on the same
 evidence — `SchemaRenderer` evaluates both through `evaluator.evaluateCondition` rather
diff --git a/.changeset/7088-hidden-jsdoc-single-hide-path.md b/.changeset/7088-hidden-jsdoc-single-hide-path.md
index aca98a42e6..c0a406c2c3 100644
--- a/.changeset/7088-hidden-jsdoc-single-hide-path.md
+++ b/.changeset/7088-hidden-jsdoc-single-hide-path.md
@@ -3,7 +3,7 @@
 ---
 
 Correct `BaseSchema.hidden`'s JSDoc: it hides by NOT RENDERING, exactly as
-`visible: false` does (objectui#7088, maintainer ruling 2026-09-01).
+`visible: false` does (maintainer ruling 2026-09-01).
 
 The declaration promised "Controls whether the component is hidden (but still
 rendered) … component is rendered but not visible (visibility: hidden)". The
diff --git a/.changeset/7126-inline-widgets-read-error.md b/.changeset/7126-inline-widgets-read-error.md
index 2229bcffde..105425d5e3 100644
--- a/.changeset/7126-inline-widgets-read-error.md
+++ b/.changeset/7126-inline-widgets-read-error.md
@@ -6,7 +6,7 @@ The last five inline edit widgets read the delivered `error` slot, so a failed
 required `text` / `boolean` / `date` / `datetime` / `time` control finally
 reports `aria-invalid` (objectui#7126).
 
-objectui#7008 made `FieldEditWidget` DELIVER the declared `error` key to
+`f08bcd9af` made `FieldEditWidget` DELIVER the declared `error` key to
 whichever widget it resolves. Of the 27 distinct components in `EDIT_WIDGETS`,
 21 read it; five did not — `TextField`, `BooleanField` (serving both `boolean`
 and `toggle`), `DateField`, `DateTimeField` and `TimeField` — so for their field
diff --git a/.changeset/7188-types-render-cell-editor-pending-row.md b/.changeset/7188-types-render-cell-editor-pending-row.md
index af3a4be0b8..608027b472 100644
--- a/.changeset/7188-types-render-cell-editor-pending-row.md
+++ b/.changeset/7188-types-render-cell-editor-pending-row.md
@@ -4,7 +4,7 @@
 
 feat(types): `renderCellEditor`'s context gains `pendingRow` — the persisted row merged with its staged, unsaved edits (#7188)
 
-The inline cell editor's context on `DataTableSchema` (declared by #6882) carried the row
+The inline cell editor's context on `DataTableSchema` (declared by `bf97b98c8`) carried the row
 once, as `row` — the **persisted** record. A widget that scopes itself by a sibling field
 (a `dependsOn` lookup) had no way to see a parent that was edited in the same row but not
 yet saved, so it kept listing candidates for the old parent.
@@ -19,6 +19,6 @@ The context now carries the row twice, deliberately:
 already-published member, and a host that needs the persisted value would have lost its
 only source. Both are addressable. The zod mirror's `renderCellEditor` is `z.function()`
 and encodes no parameter shape; its description records the delta and names the member
-on `DataTableSchema` as the authority. The #6882 exact-shape pin was extended (not
+on `DataTableSchema` as the authority. The `bf97b98c8` exact-shape pin was extended (not
 weakened) in the same change, with a control proving the pin can tell the seventh member's
 presence from its absence.
diff --git a/.changeset/7196-plugin-grid-held-key-census.md b/.changeset/7196-plugin-grid-held-key-census.md
index 9cb04a82ba..cda265df70 100644
--- a/.changeset/7196-plugin-grid-held-key-census.md
+++ b/.changeset/7196-plugin-grid-held-key-census.md
@@ -7,14 +7,14 @@ runtime code, no exported type, no declared member moves, so nothing publishes.
 
 The card (objectui#7196) was filed on ONE measured entry: the schema-level census still
 listed `renderCellEditor` as an undeclared-but-live HELD key and called the `packages/types`
-ruling on it "pending", when objectui#6882 had declared it on 2026-08-30. The card
+ruling on it "pending", when `bf97b98c8` had declared it on 2026-08-30. The card
 deliberately did not claim the other entries were correct, only that nobody had checked, so
 all sixteen claims across both censuses in the file were re-derived against `origin/main`
 rather than read. Seven were defective:
 
 Stale — correct when written, drifted since:
 
-- `renderCellEditor` — declared by objectui#6882 on three surfaces (the member, the Zod
+- `renderCellEditor` — declared by `bf97b98c8` on three surfaces (the member, the Zod
   mirror, an `Equal` exact-shape pin). The `(schema as any)` cast the census cites went
   with the declaration.
 - `cellClassName` — declared by the SAME ruling. The card did not name this one; the
@@ -29,7 +29,7 @@ Wrong when written, not drift:
 - the schema-level `cellClassName` was described as folded "into every body cell's
   `className`". It reaches exactly three UTILITY cells (selection, row-number,
   row-actions) and never a data cell, which folds the per-column twin. The failure mode
-  the census names is wrong in the same way. objectui#6882's declaration carries the
+  the census names is wrong in the same way. `bf97b98c8`'s declaration carries the
   correct version upstream; this makes the local copy agree with it.
 - "the 7-literal union `TableColumn` declares" — it has been eight since objectui#6370
   (2026-08-25), a day before the docblock was written; that commit's own subject says
diff --git a/.changeset/7201-schema-slot-census-gate.md b/.changeset/7201-schema-slot-census-gate.md
index 947874b2a4..825f0bcf77 100644
--- a/.changeset/7201-schema-slot-census-gate.md
+++ b/.changeset/7201-schema-slot-census-gate.md
@@ -5,7 +5,7 @@ Gate the `plugin-grid` schema-level held-key census on its ENTRY CONDITION
 (objectui#7201). The census's only pin asserted that the seam ACCEPTS
 `renderCellEditor` and `cellClassName` — equally true while the keys are held
 locally and once they arrive through `DataTableSchema` — so it stayed green
-across objectui#6882, the ruling that expired both holds. The suite now also
+across the 2026-08-30 ruling that expired both holds (`bf97b98c8`). The suite now also
 carries the column-level twin's shape (`columnHoldsExpiry-6424.test.ts`):
 a compile-time verdict per member of `ObjectGridDataTableSchemaHolds` recording
 whether `DataTableSchema` declares that key, plus a pin on the member set so the
diff --git a/.changeset/7344-handler-string-any-mirrors.md b/.changeset/7344-handler-string-any-mirrors.md
index 47fb1a24f5..6ce5cb9826 100644
--- a/.changeset/7344-handler-string-any-mirrors.md
+++ b/.changeset/7344-handler-string-any-mirrors.md
@@ -14,7 +14,7 @@ string dialect is not a supported authoring form, executed in the objectui#6124
   (`DetailView.handleBack`), throwing `onBack is not a function` at click.
 - Three declared `z.any()` — `ActionSchema.onClick`, `DetailSchema.onBack`,
   `CRUDDialogSchema.onClose` — wider than the callable the TypeScript face declares, so
-  any JSON value parsed green (the objectui#7069 direction).
+  any JSON value parsed green (the `2760075ff` direction).
 - One, `CalendarViewSchema.onEventClick`, was `z.function()` in a multi-line spelling the
   anchored census missed.
 
diff --git a/.changeset/7655-chatbot-registration-authoring-faces.md b/.changeset/7655-chatbot-registration-authoring-faces.md
index 15a4b96435..222688e9a0 100644
--- a/.changeset/7655-chatbot-registration-authoring-faces.md
+++ b/.changeset/7655-chatbot-registration-authoring-faces.md
@@ -49,7 +49,7 @@ per key on the PR's base (one `schema.KEY` read per registration body in
 - Neither face declares `ChatbotSchema`'s six legacy members (`loading`,
   `showAvatars`, `userAvatar`, `assistantAvatar`, `markdown`, `height`) — no
   registration reads them by name — and neither redeclares `disabled`, which
-  stays `BaseSchema`'s `boolean | string` (objectui#7087).
+  stays `BaseSchema`'s `boolean | string` (`c93b4d5f3`).
 
 **`ChatbotSchema` is unchanged.** It keeps `displayMode` and `floatingConfig`
 (declarations verbatim), and the floating face declares the same two, so
diff --git a/.changeset/7687-combobox-option-disabled.md b/.changeset/7687-combobox-option-disabled.md
index 8d8fb4c507..077d53d4d0 100644
--- a/.changeset/7687-combobox-option-disabled.md
+++ b/.changeset/7687-combobox-option-disabled.md
@@ -7,7 +7,7 @@ Honour `options[].disabled` on a `combobox` node (objectui#7687).
 **User-visible behaviour change, deliberately — hence `minor`, not `patch`.** The
 member was already declared by `@object-ui/types` (`ComboboxOption.disabled`) and
 already validated by the zod mirror (`ComboboxOptionSchema`, pinned as `boolean`
-on both faces by the objectui#7087 twin-symmetry ruling), but the component never
+on both faces by the 2026-09-01 twin-symmetry ruling, `c93b4d5f3`), but the component never
 read it: `Combobox` mapped each option to a `CommandItem` carrying `key`, `value`
 and `onSelect` only. So an option authored `{ value, label, disabled: true }`
 passed `safeValidateSchema`, type-checked against the published `ComboboxSchema`,
@@ -22,7 +22,7 @@ internal fix, so it is priced as a behaviour change rather than a patch.
 
 The alternative remedy, retiring `disabled` from `ComboboxOption` and the zod
 mirror, was weighed and **not** adopted: it narrows a published surface and would
-require the objectui#7087 twin-symmetry pin to be changed, where honouring the key
+require the `c93b4d5f3` twin-symmetry pin to be changed, where honouring the key
 restores declared = enforced at the cost of one prop. The spelling follows the
 sibling select renderer, which already sets `disabled={opt.disabled}` on its
 `SelectItem`.
diff --git a/.changeset/7735-zod-mirrors-stop-authoring-defaults.md b/.changeset/7735-zod-mirrors-stop-authoring-defaults.md
index 8944d97e34..ece941b9e0 100644
--- a/.changeset/7735-zod-mirrors-stop-authoring-defaults.md
+++ b/.changeset/7735-zod-mirrors-stop-authoring-defaults.md
@@ -53,7 +53,7 @@ keys against their renderers finds **six** disagreements, not two:
 | `container.maxWidth` | `'lg'` | `container.tsx`: `?? 'xl'` |
 | `flex.align` | `'center'` | `flex.tsx`: `\|\| 'start'` |
 | `grid.columns` | `3` | `grid.tsx`: `let baseCols = 2` |
-| `text.variant` | `'body'` | `text.tsx`: none — a bare node, no typography class (objectui#6942) |
+| `text.variant` | `'body'` | `text.tsx`: none — a bare node, no typography class (`57f9b077b`) |
 | `resizable.withHandle` | `true` | forwarded bare; `undefined` draws NO grip |
 | `page.template` | `'default'` | `page.tsx`: a null template falls through to the `pageType` dispatch |
 
diff --git a/.changeset/8070-name-visiblewhen-clear.md b/.changeset/8070-name-visiblewhen-clear.md
index dfe50af19c..81e66c029e 100644
--- a/.changeset/8070-name-visiblewhen-clear.md
+++ b/.changeset/8070-name-visiblewhen-clear.md
@@ -6,7 +6,7 @@
 The record form now tells the user when a `visibleWhen` transition clears a field
 (objectui#8070, ruling letter A).
 
-Since objectui#6958 a field whose own `visibleWhen` / `visibleOn` turns it
+Since `6a449fc49` a field whose own `visibleWhen` / `visibleOn` turns it
 invisible while it holds a value has that value cleared, so the server does not
 refuse the row over a column that is no longer on screen. That clear was silent:
 the field disappeared and nothing said a stored value went with it. The ruling
diff --git a/.changeset/8148-number-badinput-refusal-keyed.md b/.changeset/8148-number-badinput-refusal-keyed.md
index 6e86677e0c..9d2a7dc2fe 100644
--- a/.changeset/8148-number-badinput-refusal-keyed.md
+++ b/.changeset/8148-number-badinput-refusal-keyed.md
@@ -7,7 +7,7 @@ Key the `type="number"` bad-input refusal — the FIFTH sentence of this class,
 and the only shared one — into the locale packs (objectui#8148).
 
 objectui#6755 ruled that a widget's OWN refusal sentence goes through
-`useFieldTranslation` + `FIELD_DEFAULTS`, and objectui#6888 applied that to
+`useFieldTranslation` + `FIELD_DEFAULTS`, and `320374d2a` applied that to
 `LocationField`'s residue arm as the fourth. The four already keyed are each one
 widget's. This one is not: a single literal in `widgets/numberBadInput.tsx`
 produced the sentence for `NumberField`, `CurrencyField`, `PercentField` and
diff --git a/.changeset/8149-location-placeholder-localized.md b/.changeset/8149-location-placeholder-localized.md
index 25e51c0fe1..6f89028067 100644
--- a/.changeset/8149-location-placeholder-localized.md
+++ b/.changeset/8149-location-placeholder-localized.md
@@ -6,7 +6,7 @@
 (objectui#8149).
 
 When a `location` field declares no `placeholder`, the box used to show the
-English literal `latitude, longitude`. objectui#6888 had already keyed the two
+English literal `latitude, longitude`. `320374d2a` had already keyed the two
 coordinate nouns for the widget's residue refusal, so on a Chinese console the
 box said `latitude` while the refusal one line beneath it said the Chinese word
 for the same coordinate. The fallback is now composed from those same keys,
diff --git a/.changeset/8268-testid-emitted-as-data-testid.md b/.changeset/8268-testid-emitted-as-data-testid.md
index 7cd9a1982c..e5be0313dd 100644
--- a/.changeset/8268-testid-emitted-as-data-testid.md
+++ b/.changeset/8268-testid-emitted-as-data-testid.md
@@ -26,7 +26,7 @@ after   id="my-scroll" data-testid="my-tid" data-obj-id="my-scroll"
 strip list and the spread were working as designed; only this key had no mapping.
 
 The other direction — retiring the promise — was considered and declined. It is what
-objectui#7088 did for `BaseSchema.hidden`, but that key had a working behaviour to describe and
+`c1fe272ad` did for `BaseSchema.hidden`, but that key had a working behaviour to describe and
 zero named consumers, and the ruling's decline turned on exactly that. This promise already has
 carriers outside the type declaration: `content/docs/api/schema-reference.md` states it as a
 table row and authors `testId` in that page's own base-schema example, `@object-ui/cli`'s
diff --git a/.changeset/action-callback-retired-7068.md b/.changeset/action-callback-retired-7068.md
index 0ed6b08f8d..08f956405d 100644
--- a/.changeset/action-callback-retired-7068.md
+++ b/.changeset/action-callback-retired-7068.md
@@ -6,7 +6,7 @@
 pair — `onSuccess` / `onFailure`, each carrying an `ActionCallback` object — is
 RETIRED, and the `ActionCallback` type and its Zod mirror `ActionCallbackSchema`
 (with the inferred `ActionCallbackSchemaType`) are DELETED from `@object-ui/types`
-and `@object-ui/types/zod` (objectui#7068; maintainer ruling option 1 of
+and `@object-ui/types/zod` (maintainer ruling option 1 of
 2026-09-05, immediate, no deprecation window; ADR-0049 enforce-or-remove).
 
 **What an author who wrote the shape sees now.** A `{ type: 'action', … }`
diff --git a/.changeset/component-docs-disabled-inherited-7239.md b/.changeset/component-docs-disabled-inherited-7239.md
index a09347042f..ab80937f29 100644
--- a/.changeset/component-docs-disabled-inherited-7239.md
+++ b/.changeset/component-docs-disabled-inherited-7239.md
@@ -3,7 +3,7 @@
 
 Docs-only: 13 `content/docs/components/**` pages spelled an inherited
 `disabled?: boolean` in their illustrative interfaces, which went stale when
-objectui#7087 removed the 18 narrowings and left the member inherited from
+`c93b4d5f3` removed the 18 narrowings and left the member inherited from
 `BaseSchema` as `boolean | string`. The pages now spell the shipped union
 (objectui#7239), and a new test-only pin
 (`packages/types/src/__tests__/component-docs-disabled-inherited-7239.test.ts`)
diff --git a/.changeset/olive-moons-shave.md b/.changeset/olive-moons-shave.md
index 507ad25d28..f4f8d58a5d 100644
--- a/.changeset/olive-moons-shave.md
+++ b/.changeset/olive-moons-shave.md
@@ -1,7 +1,7 @@
 ---
 ---
 
-Internal test-support change, no user-visible behaviour (objectui#6924).
+Internal test-support change, no user-visible behaviour.
 
 The 17 hand-written `(Schema as { options?: readonly string[] }).options` casts
 across 16 spec-parity test files converge onto `@object-ui/test-support`'s
diff --git a/.changeset/publish-envelope-one-spelling-6962.md b/.changeset/publish-envelope-one-spelling-6962.md
index d4d69ec9bd..1493a2b29b 100644
--- a/.changeset/publish-envelope-one-spelling-6962.md
+++ b/.changeset/publish-envelope-one-spelling-6962.md
@@ -4,7 +4,7 @@
 
 **Fix:** `MetadataClient.publishDraft` no longer unwraps a `{ success, data }`
 envelope, so it and `MetadataClient.publish` hold ONE belief about the route
-they share (objectui#6962).
+they share.
 
 The two methods sit ~250 lines apart in `metadata-client.ts` and both POST
 `/api/v1/meta/:type/:name/publish`. `publishDraft` tolerated a dispatcher-shaped
diff --git a/.changeset/render-publish-advisory-findings-5026.md b/.changeset/render-publish-advisory-findings-5026.md
index 887dc04278..508311abd7 100644
--- a/.changeset/render-publish-advisory-findings-5026.md
+++ b/.changeset/render-publish-advisory-findings-5026.md
@@ -18,4 +18,4 @@ One thing had to differ, and it is the frame's verb. Save and Publish are two di
 
 Unchanged, deliberately: the **batch** door. "Publish whole app" (`POST /packages/:id/publish-drafts`) discarded per-draft advisories server-side when this change was written — objectstack#9343, open and unruled at the time — and nothing here compensated for that from the client side. A test pinned the absence, so a later traversal of a batch-shaped `published[]` could not be added without turning it red.
 
-*Corrected before release (objectui#6965): both present-tense claims in the paragraph above went false after it was written — objectstack#9343 landed, the batch response now carries per-draft advisories, and objectui#6965 routes that door through the same seam and flips the absence pin to a presence pin. The paragraph is kept in the past tense as the record of what this change did and did not do; this note is what the CHANGELOG publishes instead of a sentence that was true only while it sat here.*
+*Corrected before release (`ce986aafc`): both present-tense claims in the paragraph above went false after it was written — objectstack#9343 landed, the batch response now carries per-draft advisories, and `ce986aafc` routes that door through the same seam and flips the absence pin to a presence pin. The paragraph is kept in the past tense as the record of what this change did and did not do; this note is what the CHANGELOG publishes instead of a sentence that was true only while it sat here.*
diff --git a/.changeset/shared-zod-wrapper-keys-6923.md b/.changeset/shared-zod-wrapper-keys-6923.md
index 317c2a9eff..949630b562 100644
--- a/.changeset/shared-zod-wrapper-keys-6923.md
+++ b/.changeset/shared-zod-wrapper-keys-6923.md
@@ -3,7 +3,7 @@
 
 Internal only — no user-visible change, nothing to release.
 
-objectui#6923: the Zod wrapper-key list that five test/gate sites each spelled
+The Zod wrapper-key list that five test/gate sites each spelled
 out by hand now lives once, in `packages/test-support` (a `private: true`,
 never-published package), and is read by both the TypeScript suites and the
 `.mjs` CI gates. Only test files, CI gate scripts and the private
diff --git a/.changeset/vi-mock-inherit-slice2.md b/.changeset/vi-mock-inherit-slice2.md
index fbe8d6d86b..8039e48dac 100644
--- a/.changeset/vi-mock-inherit-slice2.md
+++ b/.changeset/vi-mock-inherit-slice2.md
@@ -4,4 +4,4 @@
 Test-only change: the four frozen `vi.mock` factories on `@object-ui/plugin-charts`
 and `@object-ui/plugin-dashboard` now inherit the real module's export surface, and
 those two specifiers join `COVERED_SPECIFIERS` in `scripts/check-vi-mock-inherit.mjs`
-(objectui#6892 slice 2). No published behaviour changes.
+(slice 2). No published behaviour changes.
diff --git a/.changeset/vi-mock-inherit-slice3.md b/.changeset/vi-mock-inherit-slice3.md
index cf7cd96961..f0fd622106 100644
--- a/.changeset/vi-mock-inherit-slice3.md
+++ b/.changeset/vi-mock-inherit-slice3.md
@@ -3,6 +3,6 @@
 
 Test-only change: the 102 frozen `vi.mock` factories on `@object-ui/auth` now inherit
 the real module's export surface, and that specifier joins `COVERED_SPECIFIERS` in
-`scripts/check-vi-mock-inherit.mjs` (objectui#6892 slice 3). The barrel was measured
+`scripts/check-vi-mock-inherit.mjs` (slice 3). The barrel was measured
 inert at module scope before converting, so nothing new runs at import time. No
 published behaviour changes.
diff --git a/packages/app-shell/src/console/ai/AiChatPage.tsx b/packages/app-shell/src/console/ai/AiChatPage.tsx
index 244f2173fe..7d03dae6be 100644
--- a/packages/app-shell/src/console/ai/AiChatPage.tsx
+++ b/packages/app-shell/src/console/ai/AiChatPage.tsx
@@ -2462,7 +2462,7 @@ export function ChatPane({
           // uses. A bare fetch had nothing to report THROUGH — so on the one
           // surface where the author never sees the metadata they are
           // publishing, the gate's findings were the thing that vanished.
-          // Same move objectui#6965 / PR objectui#10038 made for the two
+          // Same move PR objectui#10038 made for the two
           // sibling call sites.
           try {
             const payload = (await metadataClient.publishPackageDrafts(packageId)) as
diff --git a/packages/app-shell/src/console/ai/PendingDraftsBar.tsx b/packages/app-shell/src/console/ai/PendingDraftsBar.tsx
index e1903a185d..cc86bf3902 100644
--- a/packages/app-shell/src/console/ai/PendingDraftsBar.tsx
+++ b/packages/app-shell/src/console/ai/PendingDraftsBar.tsx
@@ -32,7 +32,7 @@
  * same sink, renderer and wording every other write door uses. A bare fetch
  * had nothing to report THROUGH, so every one of those findings was parsed by
  * nobody — while the probe findings a few lines below were already shouting.
- * objectui#6965 / PR objectui#10038 did this for the two sibling call sites;
+ * PR objectui#10038 did this for the two sibling call sites;
  * this is the same move, not a second mechanism.
  *
  * Count freshness: re-read when the package binding changes and whenever the
diff --git a/packages/app-shell/src/preview/UnpublishedAppBar.tsx b/packages/app-shell/src/preview/UnpublishedAppBar.tsx
index c4398205a2..0ddde9a634 100644
--- a/packages/app-shell/src/preview/UnpublishedAppBar.tsx
+++ b/packages/app-shell/src/preview/UnpublishedAppBar.tsx
@@ -15,7 +15,7 @@
  * (`_unpublished: false`) — instant and reversible, per ADR-0045.
  *
  * ## Why `_unpublished` and not `hidden` (objectstack#4829 A1, framework PR
- * #6942)
+ * objectstack#6942)
  *
  * These were one flag and are now two, with disjoint meanings:
  *
diff --git a/packages/app-shell/src/preview/usePublishAllDrafts.ts b/packages/app-shell/src/preview/usePublishAllDrafts.ts
index 6c35d5a612..ee53bcdc7c 100644
--- a/packages/app-shell/src/preview/usePublishAllDrafts.ts
+++ b/packages/app-shell/src/preview/usePublishAllDrafts.ts
@@ -17,7 +17,7 @@
  * blind "Published!". Package-less drafts fall back to by-reference publish
  * (structure first, seeds last) so they never dead-end.
  *
- * Both halves of that call now run through `MetadataClient` (objectui#6965):
+ * Both halves of that call now run through `MetadataClient` (`ce986aafc`):
  * the batch one so the runtime authoring gate's per-draft advisories reach the
  * console's advisory toast, the by-reference one because it always did. The
  * asymmetry this closes was inside this very function — its own client-side
@@ -83,7 +83,7 @@ export function usePublishAllDrafts(t: TranslateFn) {
       };
 
       for (const packageId of packageIds) {
-        // objectui#6965 — through `MetadataClient`, not a bare `fetch`. The
+        // `ce986aafc` — through `MetadataClient`, not a bare `fetch`. The
         // route now answers the runtime authoring gate's per-draft advisories
         // on each `published[]` element (objectstack#9343), and the client is
         // the seam that reports them: it emits one advisory event per advised
diff --git a/packages/app-shell/src/views/metadata-admin/PackagesPage.tsx b/packages/app-shell/src/views/metadata-admin/PackagesPage.tsx
index a1a12c5ca2..e9720ba0a6 100644
--- a/packages/app-shell/src/views/metadata-admin/PackagesPage.tsx
+++ b/packages/app-shell/src/views/metadata-admin/PackagesPage.tsx
@@ -281,7 +281,7 @@ export function PackageDetailSheet({
   onChanged: () => void;
 }) {
   const locale = useMetadataLocale();
-  // objectui#6965 — the console's metadata client, for the ONE action on this
+  // `ce986aafc` — the console's metadata client, for the ONE action on this
   // sheet that must report: "publish drafts" promotes metadata, and the runtime
   // authoring gate's findings for those promotions ride the response. This hook
   // is where the advisory sink is wired (`useMetadataClient` → the toast
@@ -370,7 +370,7 @@ export function PackageDetailSheet({
   // refresh the pending list (it should now be empty). Distinct from the
   // registry-based `publish` above; this hits `/publish-drafts`.
   //
-  // objectui#6965 — through `MetadataClient`, not `apiJson`. This promotes
+  // `ce986aafc` — through `MetadataClient`, not `apiJson`. This promotes
   // metadata, so the runtime authoring gate grades it and answers its findings
   // on each `published[]` element (objectstack#9343); the client is the seam
   // that reports them to the author. `apiJson` could not — and the response
diff --git a/packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx b/packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx
index 462f969705..36d4647642 100644
--- a/packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx
+++ b/packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx
@@ -890,7 +890,7 @@ export function StudioDesignSurface({ aiSlot }: StudioDesignSurfaceProps): React
       // seam that reports them: one advisory event per advised item, into the
       // same sink, renderer and wording every other write door on this surface
       // uses. A bare fetch had nothing to report THROUGH. Same move
-      // objectui#6965 / PR objectui#10038 made for the two sibling call sites.
+      // PR objectui#10038 made for the two sibling call sites.
       const payload = (await shellClient.publishPackageDrafts(packageId)) as {
         success?: boolean;
         error?: { message?: string; details?: { issues?: unknown } };
diff --git a/packages/cli/src/commands/validate.ts b/packages/cli/src/commands/validate.ts
index 63dc6cd451..b9478bb528 100644
--- a/packages/cli/src/commands/validate.ts
+++ b/packages/cli/src/commands/validate.ts
@@ -104,7 +104,7 @@ export async function validate(schemaPath: string) {
       // undefined and this loop threw a TypeError that the catch below
       // reported as "Error reading or parsing schema file", hiding the very
       // errors this command exists to print.
-      // Every issue gets a Path line, INCLUDING a root-level one (objectui#7004).
+      // Every issue gets a Path line, INCLUDING a root-level one (`85b495795`).
       //
       // The guard here used to be `issue.path.length > 0`, which dropped the
       // line entirely for `path: []` — silent in exactly the case a reader
@@ -124,7 +124,7 @@ export async function validate(schemaPath: string) {
       // `(root)` is parenthesised so it cannot be read as a real key literally
       // named `root` — a genuine path to one would print as `root`.
       //
-      // The ARM-SELECTION half of objectui#7004 landed on the 2026-09-02
+      // The ARM-SELECTION half (`a5d55472b`) landed on the 2026-09-02
       // maintainer ruling (option B): print the issues of the arm the authored
       // `type` selects, and nothing from the others. Since objectui#8498 ZOD
       // does that selecting — a matched discriminator yields the arm's issues
diff --git a/packages/cli/src/utils/union-arm-diagnostics.ts b/packages/cli/src/utils/union-arm-diagnostics.ts
index 080e4d9175..f881a6e059 100644
--- a/packages/cli/src/utils/union-arm-diagnostics.ts
+++ b/packages/cli/src/utils/union-arm-diagnostics.ts
@@ -7,7 +7,7 @@
  */
 
 /**
- * Arm selection for a failing union (objectui#7004, arm-selection half).
+ * Arm selection for a failing union (`a5d55472b`).
  *
  * ## What this exists for
  *
@@ -223,7 +223,7 @@ function editDistance(a: string, b: string): number {
  * deliberately case-only under a DIFFERENT ruling (objectui#5247) for a
  * DIFFERENT surface (`objectui check`) over a DIFFERENT candidate set
  * (`KNOWN_SCHEMA_TYPES`, the registry's keys). This surface's candidates are the
- * schema union's arms, and the 2026-09-02 ruling on objectui#7004 asks for the
+ * schema union's arms, and the 2026-09-02 ruling `a5d55472b` implements asks for the
  * "nearest" ones by name — so proximity is granted here and is not a widening
  * of that one.
  */
diff --git a/packages/components/src/renderers/basic/metadata-viewer.tsx b/packages/components/src/renderers/basic/metadata-viewer.tsx
index 35a8621d45..9a9eb056dd 100644
--- a/packages/components/src/renderers/basic/metadata-viewer.tsx
+++ b/packages/components/src/renderers/basic/metadata-viewer.tsx
@@ -110,7 +110,7 @@ function Placeholder({ tone = 'muted', children }: { tone?: 'muted' | 'warn'; ch
 /**
  * One declared option of the object field a state machine runs on — DERIVED
  * from the spec's own `SelectOption` (`@objectstack/spec/data`), with the one
- * narrowing this projection needs named in the `Omit` below (objectui#6887).
+ * narrowing this projection needs named in the `Omit` below (`5c09cca27`).
  *
  * It was a hand-written `{ label?; value; color?; default? }` quadruple: four of
  * the spec's five keys, with the fifth dropped by SILENCE — no `Omit` naming it,
diff --git a/packages/components/src/renderers/basic/text.tsx b/packages/components/src/renderers/basic/text.tsx
index c5f7b9bd8e..07d6e98308 100644
--- a/packages/components/src/renderers/basic/text.tsx
+++ b/packages/components/src/renderers/basic/text.tsx
@@ -15,7 +15,7 @@ type TextAlign = NonNullable<TextSchema['align']>;
 
 /**
  * `TextSchema.variant` -> one visibly distinct typographic class per published
- * value (objectui#6942, maintainer ruling B1 of 2026-09-02).
+ * value (`57f9b077b`, maintainer ruling B1 of 2026-09-02).
  *
  * ## What was measured before this map existed
  *
@@ -134,7 +134,7 @@ ComponentRegistry.register('text',
     const { style, ...hostProps } = props;
     const dataObjId = hostProps['data-obj-id'];
 
-    // ABSENCE IS NOT `body` (objectui#6942). Nothing writes a variant into a
+    // ABSENCE IS NOT `body` (`57f9b077b`). Nothing writes a variant into a
     // node that omits the key: the Zod mirror used to declare `.default('body')`
     // and materialise it on a PARSED document, and objectui#7735 removed that —
     // a validator validates, it does not author, and this renderer's own
@@ -175,7 +175,7 @@ ComponentRegistry.register('text',
     inputs: [
       { name: 'content', type: 'string', required: true },
       // Declared because they are READ, in the same change as the read sites
-      // above (objectui#6942). While these were missing, `page.tsx`'s JSX-page
+      // above (`57f9b077b`). While these were missing, `page.tsx`'s JSX-page
       // prop whitelist — built from `getKnownTypes()` plus these `inputs` —
       // reported `unknown-prop` for two keys `TextSchema` publishes.
       //
diff --git a/packages/components/src/renderers/complex/data-table.tsx b/packages/components/src/renderers/complex/data-table.tsx
index d7890c611b..c778df5d79 100644
--- a/packages/components/src/renderers/complex/data-table.tsx
+++ b/packages/components/src/renderers/complex/data-table.tsx
@@ -2573,7 +2573,7 @@ const DataTableRenderer = ({ schema }: { schema: DataTableSchema }) => {
                                 // reason only: `DataTableSchema` did not declare the key
                                 // this renderer has always read, so the read had to
                                 // re-state the contract locally and the schema had to be
-                                // opened up to let it. objectui#6882 declared it (the
+                                // opened up to let it. `bf97b98c8` declared it (the
                                 // 2026-08-30 ruling), so the read is typed at its source
                                 // and the ctx shape below is checked against the
                                 // declaration instead of asserted against nothing.
diff --git a/packages/components/src/renderers/form/form.tsx b/packages/components/src/renderers/form/form.tsx
index 718be29727..735978c1c2 100644
--- a/packages/components/src/renderers/form/form.tsx
+++ b/packages/components/src/renderers/form/form.tsx
@@ -1482,7 +1482,7 @@ ComponentRegistry.register('form',
     // now stands", and splitting them would give one authored intent two
     // behaviours.
     //
-    // Feeds the clear-on-hide effect (objectui#6958). Fields declaring NEITHER
+    // Feeds the clear-on-hide effect (`6a449fc49`). Fields declaring NEITHER
     // key are skipped outright, so a form that does not use conditional
     // visibility recomputes nothing and behaves exactly as before.
     //
@@ -1966,7 +1966,7 @@ ComponentRegistry.register('form',
       // eslint-disable-next-line react-hooks/exhaustive-deps
     }, [ruleRecord, predicateScope]);
 
-    // Clear-on-hide (objectui#6958) — the field's own `visibleWhen` turning it
+    // Clear-on-hide (`6a449fc49`) — the field's own `visibleWhen` turning it
     // invisible clears its value.
     //
     // ## The dead end this closes
diff --git a/packages/core/src/evaluator/fieldRules.ts b/packages/core/src/evaluator/fieldRules.ts
index 6c005f69a1..d24a45f62f 100644
--- a/packages/core/src/evaluator/fieldRules.ts
+++ b/packages/core/src/evaluator/fieldRules.ts
@@ -316,7 +316,7 @@ export function evalFieldPredicate(
  * explicitly undecided ("appeal 1").
  *
  * ⛔ These values are shipped behaviour. Changing one is not a refactor, it is
- * objectui#8069's decision — and objectui#6958 leans on the `visibleWhen` half
+ * objectui#8069's decision — and `6a449fc49` leans on the `visibleWhen` half
  * staying fail-open (a broken predicate must never silently null a stored
  * column).
  */
diff --git a/packages/core/src/registry/public-blocks.ts b/packages/core/src/registry/public-blocks.ts
index 7c03769559..1b382afaeb 100644
--- a/packages/core/src/registry/public-blocks.ts
+++ b/packages/core/src/registry/public-blocks.ts
@@ -133,7 +133,7 @@ export const PUBLIC_BLOCKS: readonly string[] = [
   // It landed on every other declaration face — interface, zod mirror,
   // `SchemaRegistry`, registration, docs page, and 27 catalog fixtures — and
   // this list was the one face it missed, so the vocabulary taught a type the
-  // contract did not carry (objectui#6879).
+  // contract did not carry (`3619792bf`).
   //
   // MEASURED before it was added, because "add it and see" is how a gate
   // discovers a new population at merge time. `registry-inputs-spec-parity`
diff --git a/packages/data-objectstack/src/index.ts b/packages/data-objectstack/src/index.ts
index 5fda0559cb..1a247f3c08 100644
--- a/packages/data-objectstack/src/index.ts
+++ b/packages/data-objectstack/src/index.ts
@@ -2005,7 +2005,7 @@ export type DroppedFieldsNotice = DroppedFieldsEvent | UnrecognizedDropReasonEve
  *
  * It used to be `Omit<DroppedFieldsEvent, 'reason'> & { reason?: unknown }`,
  * which was honest about `reason` and dishonest about the other two
- * (objectui#6889). `Omit` carried the spec's `fields: string[]` and its
+ * (`f75810e7c`). `Omit` carried the spec's `fields: string[]` and its
  * REQUIRED `object: string` through untouched, while the structural gate below
  * read neither: `fields: [42]` and an entry with no `object` at all both passed
  * and reached subscribers typed as if they had been checked. Required is what
@@ -2033,7 +2033,7 @@ function isRecognizedDropReason(reason: unknown): reason is DroppedFieldsEvent['
  * one string (so the parsed notice below names something). An array holding no
  * string at all — `fields: [42]`, `fields: []` — reports no field name, and an
  * entry that names no field has nothing truthful to tell the user; the
- * pre-objectui#6889 gate already dropped the empty case for exactly that
+ * pre-`f75810e7c` gate already dropped the empty case for exactly that
  * reason, and this is the same rule one level deeper.
  *
  * `object` and `reason` are deliberately NOT gated on. Nothing is dropped for
@@ -2051,7 +2051,7 @@ function isWireDroppedFieldsEntry(e: unknown): e is WireDroppedFieldsEntry {
 }
 
 /**
- * Parse ONE wire entry into a notice (objectui#4934, objectui#6889).
+ * Parse ONE wire entry into a notice (objectui#4934, `f75810e7c`).
  *
  * Three parses, one per field the gate above does not establish, and the
  * result is built rather than asserted — so the last cast in this seam is gone:
@@ -2118,7 +2118,7 @@ function asDroppedFieldsNotice(
  * cannot produce this entry; it takes one that omits (or non-strings) `object`
  * AND sends an index naming no operation, in the same entry. Nothing in this
  * repo emits that shape, and whether a deployed backend does is not answerable
- * from here. Unlike objectui#6889's exotic case this is not structurally
+ * from here. Unlike the exotic case on the card behind `f75810e7c`, this is not structurally
  * impossible — the payload arrives as parsed JSON, and a non-conformant server
  * can send it.
  *
@@ -2142,7 +2142,7 @@ function asDroppedFieldsNotice(
  *
  * So this is neither the skew arm's "tolerate" (objectui#4934 — a `reason` from
  * the future is the producer running AHEAD of us, expected version skew) nor
- * `fields`' "refuse" (objectui#6889 — an off-spec element that would otherwise
+ * `fields`' "refuse" (`f75810e7c` — an off-spec element that would otherwise
  * reach a consumer typed as a field name). There is no producer value to keep
  * or drop here: the question is only what WE write when the response supplied
  * nothing. The answer is a DECLARED placeholder rather than a bare literal that
@@ -3582,7 +3582,7 @@ export class ObjectStackAdapter<T = unknown> implements DataSource<T> {
    * field); `object`, `fields` and `reason` are then PARSED — an unrecognized
    * reason routed to the skew arm, a non-string field element refused, a missing
    * `object` healed from `resource` — never asserted into the union, and the
-   * entry itself never dropped for them (objectui#4934, objectui#6889).
+   * entry itself never dropped for them (objectui#4934, `f75810e7c`).
    */
   private notifyDroppedFields(
     operation: 'create' | 'update',
@@ -3625,7 +3625,7 @@ export class ObjectStackAdapter<T = unknown> implements DataSource<T> {
     for (const entry of dropped) {
       // Same gate as the single-record path, so the two agree on what an entry
       // even is. The remaining cast adds only `index`, which this loop reads
-      // and the gate has no opinion about (objectui#4934, objectui#6889).
+      // and the gate has no opinion about (objectui#4934, `f75810e7c`).
       if (!isWireDroppedFieldsEntry(entry)) continue;
       const e = entry as WireDroppedFieldsEntry & { index?: number };
       const op = typeof e.index === 'number' ? operations[e.index] : undefined;
@@ -3654,7 +3654,7 @@ export class ObjectStackAdapter<T = unknown> implements DataSource<T> {
           : undefined;
       // `object`, `fields` and `reason` are parsed here too — the batch path
       // used to re-assert all three into the union via the cast above
-      // (objectui#4934, objectui#6889). `index` is deliberately not carried onto
+      // (objectui#4934, `f75810e7c`). `index` is deliberately not carried onto
       // the notice: it addresses an operation in THIS response, not the strip,
       // which is why the entry is rebuilt rather than spread.
       const [live] = withoutNoOpDrops(
diff --git a/packages/data-objectstack/src/metadata-client.ts b/packages/data-objectstack/src/metadata-client.ts
index 1d5fa99c3b..f643b95900 100644
--- a/packages/data-objectstack/src/metadata-client.ts
+++ b/packages/data-objectstack/src/metadata-client.ts
@@ -86,7 +86,7 @@ export type { RuntimeAuthoringIssue };
  * one event serve both. Measured against the installed `@objectstack/spec`
  * rather than assumed — see the PR for the probe.
  *
- * ## And the BATCH publish door (objectui#6965)
+ * ## And the BATCH publish door (`ce986aafc`)
  *
  * `PublishPackageDraftsResponseSchema` declares the same key with the same
  * element type, riding EACH `published[]` element rather than a parallel
@@ -122,7 +122,7 @@ export interface MetadataSaveAdvisoryEvent {
    *   ({@link MetadataClient.publishPackageDrafts}), which emits ONE event per
    *   `published[]` element carrying that element's own `type` / `name`.
    *
-   * ## Why the batch route is not a third value (objectui#6965)
+   * ## Why the batch route is not a third value (`ce986aafc`)
    *
    * The batch door promotes drafts to active — the author pressed Publish, and
    * every item this event names really was published. What `door` decides is
@@ -156,7 +156,7 @@ export type MetadataSaveAdvisoryListener = (event: MetadataSaveAdvisoryEvent) =>
 /**
  * Read the `advisories` array off a metadata write response, defensively.
  *
- * Serves EVERY write door unchanged (#5026, objectui#6965):
+ * Serves EVERY write door unchanged (#5026, `ce986aafc`):
  * `SaveMetaItemResponseSchema` and `PublishMetaItemResponseSchema` declare the
  * key at the same top level, and `PublishPackageDraftsResponseSchema` declares
  * it on each `published[]` element — under the same name, with the same element
@@ -222,7 +222,7 @@ export interface MetadataClientConfig {
    * Called after a {@link MetadataClient.save} whose 2xx response carried a
    * non-empty `advisories` array (objectstack#7435). Since #5026 the SAME sink
    * also receives the publish door's findings (objectstack#9176), and since
-   * objectui#6965 the batch publish door's too, one event per advised
+   * `ce986aafc` the batch publish door's too, one event per advised
    * `published[]` element (objectstack#9343) — read `event.door` to tell a
    * save from a promotion, and `event.type` / `event.name` for which item. The
    * write already succeeded; this is how the shell learns there is something to
@@ -261,7 +261,7 @@ export interface MetadataDraftHeader {
 /**
  * What {@link MetadataClient.publishPackageDrafts} resolves with — the "publish
  * whole app" body, DERIVED from `PublishPackageDraftsResponseSchema` rather
- * than re-spelled (objectui#6965).
+ * than re-spelled (`ce986aafc`).
  *
  * Derived, and then widened in exactly two ways, each for a measured reason:
  *
@@ -664,7 +664,7 @@ function buildBase(config: MetadataClientConfig): string {
 }
 
 /**
- * The `/api/v1/packages` sibling of this client's `/meta` base (objectui#6965).
+ * The `/api/v1/packages` sibling of this client's `/meta` base (`ce986aafc`).
  *
  * Derived from the base rather than stored, so the two clone methods carry it
  * for free. It keeps the ORIGIN the client was configured with (split-origin
@@ -686,7 +686,7 @@ function packagesBaseOf(metaBase: string): string {
 
 /**
  * Unwrap the HTTP dispatcher's `{ success, data }` envelope — for the ONE route
- * whose spec declaration says it arrives inside one (objectui#6965).
+ * whose spec declaration says it arrives inside one (`ce986aafc`).
  *
  * ⛔ Not a general tolerance, and the difference is per-route rather than per
  * file: {@link MetadataClient.publishDraft} refuses to unwrap because
@@ -1022,7 +1022,7 @@ export class MetadataClient {
    *
    * One helper rather than a copy per door: every door's response declares the
    * key identically, so a second inline copy could only ever drift. The batch
-   * door (objectui#6965) calls it once per `published[]` element, handing it
+   * door (`ce986aafc`) calls it once per `published[]` element, handing it
    * the element — the object that carries the key there — and the same
    * best-effort contract covers that loop unchanged.
    */
@@ -1111,7 +1111,7 @@ export class MetadataClient {
    * too. It did not when this paragraph was first written: it discarded
    * per-draft advisories server-side, which was objectstack#9343, and that card
    * has since landed with a ruling that each `published[]` element carries
-   * them (objectui#6965 is the client half).
+   * them (`ce986aafc` is the client half).
    *
    * What survives that change is the READING RULE, which is about this method
    * rather than about the other route: it reads the top level of the
@@ -1120,7 +1120,7 @@ export class MetadataClient {
    * `published[]` and a client that went looking for findings wherever they
    * might be would be inventing a contract instead of reading one.
    *
-   * ## Why there is no `{ success, data }` unwrapping here (objectui#6962)
+   * ## Why there is no `{ success, data }` unwrapping here (`7b433197d`)
    *
    * This method used to unwrap a dispatcher-shaped envelope before returning,
    * while {@link publish} — the same route, a couple of hundred lines down —
@@ -1176,7 +1176,7 @@ export class MetadataClient {
     // #5026 — this is the SAME single-item publish door `publish()` uses, so it
     // reports the same way, and now off the SAME object: the response body
     // itself. `advisories` is declared at the TOP LEVEL of
-    // `PublishMetaItemResponse`, which is what this route answers (#6962).
+    // `PublishMetaItemResponse`, which is what this route answers (`7b433197d`).
     this.emitAdvisories(body, { type, name, door: 'publish', mode: 'publish' });
     return body as any;
   }
@@ -1187,7 +1187,7 @@ export class MetadataClient {
    * that orders structure-before-seeds server-side and runs the ADR-0038 L3
    * runtime probes).
    *
-   * ## Why it is expressed here at all (objectui#6965)
+   * ## Why it is expressed here at all (`ce986aafc`)
    *
    * It was not, and that was the defect. Two app-shell call sites fired this
    * route with a bare `fetch` / a page-private `apiJson`, outside the seam that
diff --git a/packages/fields/src/FieldEditWidget.tsx b/packages/fields/src/FieldEditWidget.tsx
index 7d8556abc1..07772d11c5 100644
--- a/packages/fields/src/FieldEditWidget.tsx
+++ b/packages/fields/src/FieldEditWidget.tsx
@@ -12,7 +12,7 @@ import type { FieldWidgetComponentProps } from './widgets/types.js';
 // rather than re-listed — see the note on this component's return statement.
 import { toDomProps } from './widgets/toDomProps.js';
 // The package's own executor of the NON-DOM half of the same declaration
-// (objectui#7008) — a separate function because those keys are not DOM-legal.
+// (`f08bcd9af`) — a separate function because those keys are not DOM-legal.
 import { toHostProps } from './widgets/toHostProps.js';
 
 // The SAME dedicated widgets the form renders — reused for in-place editing
@@ -275,7 +275,7 @@ const COMPACT_EDIT_TYPES = new Set<string>(['lookup', 'master_detail', 'user']);
  * nothing here needs to know which element that is. A host that passes nothing
  * is unaffected.
  *
- * The host's NON-DOM set is forwarded WHOLE too (objectui#7008), through the
+ * The host's NON-DOM set is forwarded WHOLE too (`f08bcd9af`), through the
  * sibling executor `toHostProps`. The DOM fix left the other half of the
  * contract undelivered: `error`, `onUploadingChange` and the "Host plumbing"
  * block (`dataSource`, `dependentValues`, `dependsOn`, `dependsOnLabels`,
@@ -363,7 +363,7 @@ export function FieldEditWidget(
   // states that this component OWNS them and a host cannot displace them.
   //
   // `toHostProps` is the same reuse argument applied to the other half of the
-  // declaration (objectui#7008): the declared NON-DOM keys — `error` and the
+  // declaration (`f08bcd9af`): the declared NON-DOM keys — `error` and the
   // "Host plumbing" block — travel as COMPONENT props, never through the DOM
   // whitelist, which is closed against exactly them. The two executors are
   // asserted disjoint at compile time, so neither spread can shadow the other,
diff --git a/packages/fields/src/index.tsx b/packages/fields/src/index.tsx
index b0aecedaf4..8d81f60c89 100644
--- a/packages/fields/src/index.tsx
+++ b/packages/fields/src/index.tsx
@@ -4516,7 +4516,7 @@ export { toDomProps } from './widgets/toDomProps.js';
 export type { DomProps } from './widgets/toDomProps.js';
 
 // The sibling executor for the NON-DOM half of the same declaration
-// (objectui#7008): `error` plus the "Host plumbing" block, forwarded as
+// (`f08bcd9af`): `error` plus the "Host plumbing" block, forwarded as
 // COMPONENT props because none of them is DOM-legal. Exported alongside
 // `toDomProps` because a host factory authored outside this repo needs the
 // pair — reaching for only the first one is how `FieldEditWidget` came to
diff --git a/packages/fields/src/widgets/DateField.tsx b/packages/fields/src/widgets/DateField.tsx
index de5e5aa6ba..9b35247b88 100644
--- a/packages/fields/src/widgets/DateField.tsx
+++ b/packages/fields/src/widgets/DateField.tsx
@@ -106,7 +106,7 @@ export function DateField({ value, onChange, field, readonly, error, ...props }:
    * untouched; every host WITHOUT that Slot -- `FieldEditWidget`, i.e. the
    * kanban required-fields dialog and the grid / detail inline editors --
    * hands the state over as the declared `error` prop (delivered since
-   * objectui#7008) and nothing read it. MARKING only: the message TEXT stays
+   * `f08bcd9af`) and nothing read it. MARKING only: the message TEXT stays
    * with the host.
    */
   const control = (
diff --git a/packages/fields/src/widgets/DateTimeField.tsx b/packages/fields/src/widgets/DateTimeField.tsx
index 12bf16a833..fd8ae4fec7 100644
--- a/packages/fields/src/widgets/DateTimeField.tsx
+++ b/packages/fields/src/widgets/DateTimeField.tsx
@@ -77,7 +77,7 @@ export function DateTimeField({ value, onChange, field, readonly, error, ...prop
    * untouched; every host WITHOUT that Slot -- `FieldEditWidget`, i.e. the
    * kanban required-fields dialog and the grid / detail inline editors --
    * hands the state over as the declared `error` prop (delivered since
-   * objectui#7008) and nothing read it. MARKING only: the message TEXT stays
+   * `f08bcd9af`) and nothing read it. MARKING only: the message TEXT stays
    * with the host.
    */
   const control = (
diff --git a/packages/fields/src/widgets/LocationField.tsx b/packages/fields/src/widgets/LocationField.tsx
index f3dc943bfd..70b3915b87 100644
--- a/packages/fields/src/widgets/LocationField.tsx
+++ b/packages/fields/src/widgets/LocationField.tsx
@@ -197,7 +197,7 @@ type CoordinateLabel = (typeof COORDINATE_LABELS)[number];
 /**
  * One half of the typed pair that carried non-numeric residue.
  *
- * `label` is the COORDINATE_LABELS member, not free text: since objectui#6888
+ * `label` is the COORDINATE_LABELS member, not free text: since `320374d2a`
  * it selects a locale key, so widening it to `string` would make
  * {@link coordinateName}'s branch fall through to `longitude` silently.
  */
@@ -323,7 +323,7 @@ function refusedRangeMessage(t: TranslateFn, candidate: LocationValue): string {
  * ruling declines that parse, so pointing at it would advertise a route this
  * widget refuses.
  *
- * objectui#6888 — keyed, closing the gap objectui#6755's scope lock left open:
+ * `320374d2a` — keyed, closing the gap objectui#6755's scope lock left open:
  * that ruling was written before this arm existed, so it named three sentences
  * and this is the fourth. All three arms share ONE `<p>` and one
  * `refusalError`, so leaving this one a literal made a single line speak the
@@ -389,7 +389,7 @@ function coordinateName(t: TranslateFn, label: CoordinateLabel): string {
  * extends that principle to the widget's own placeholder copy, as objectui#3342
  * did for `TagsField`'s. Before it, a zh form showed the English literal
  * `latitude, longitude` in the box while the refusal one line beneath it named
- * the same coordinate in Chinese — objectui#6888 had already keyed the nouns.
+ * the same coordinate in Chinese — `320374d2a` had already keyed the nouns.
  *
  * ⭐ Two halves, two owners:
  *
diff --git a/packages/fields/src/widgets/TextField.tsx b/packages/fields/src/widgets/TextField.tsx
index 1cdb0f45da..6d6863fc03 100644
--- a/packages/fields/src/widgets/TextField.tsx
+++ b/packages/fields/src/widgets/TextField.tsx
@@ -42,7 +42,7 @@ export function TextField({ value, onChange, field, readonly, error, ...props }:
    * through the spread untouched. Every OTHER host of this widget was not:
    * `FieldEditWidget` renders no Slot, so the kanban required-fields dialog and
    * the grid / detail inline editors hand the state over as the declared
-   * `error` prop (delivered since objectui#7008) and nothing read it — the red
+   * `error` prop (delivered since `f08bcd9af`) and nothing read it — the red
    * "Required" hint was on screen while assistive tech was told nothing.
    *
    * MARKING only. The message TEXT stays with the host (`<FormMessage/>` in the
diff --git a/packages/fields/src/widgets/TimeField.tsx b/packages/fields/src/widgets/TimeField.tsx
index 239728047c..923415f802 100644
--- a/packages/fields/src/widgets/TimeField.tsx
+++ b/packages/fields/src/widgets/TimeField.tsx
@@ -35,7 +35,7 @@ export function TimeField({ value, onChange, field, readonly, error, ...props }:
    * untouched; every host WITHOUT that Slot -- `FieldEditWidget`, i.e. the
    * kanban required-fields dialog and the grid / detail inline editors --
    * hands the state over as the declared `error` prop (delivered since
-   * objectui#7008) and nothing read it. MARKING only: the message TEXT stays
+   * `f08bcd9af`) and nothing read it. MARKING only: the message TEXT stays
    * with the host.
    */
   return (
diff --git a/packages/fields/src/widgets/numberBadInput.tsx b/packages/fields/src/widgets/numberBadInput.tsx
index b004b4a0e3..7829901e3e 100644
--- a/packages/fields/src/widgets/numberBadInput.tsx
+++ b/packages/fields/src/widgets/numberBadInput.tsx
@@ -95,7 +95,7 @@ import { useFieldTranslation } from './useFieldTranslation.js';
  * package's locale channel (objectui#8148).
  *
  * objectui#6755 ruled that a widget's OWN refusal sentence goes through
- * `useFieldTranslation` + `FIELD_DEFAULTS`; objectui#6888 applied it to
+ * `useFieldTranslation` + `FIELD_DEFAULTS`; `320374d2a` applied it to
  * `LocationField`'s residue arm. This was the FIFTH such sentence and the only
  * SHARED one — the four already keyed are each one widget's, while this literal
  * served `NumberField`, `CurrencyField`, `PercentField` and both of
diff --git a/packages/fields/src/widgets/toDomProps.ts b/packages/fields/src/widgets/toDomProps.ts
index a618567521..4591acc2ca 100644
--- a/packages/fields/src/widgets/toDomProps.ts
+++ b/packages/fields/src/widgets/toDomProps.ts
@@ -127,7 +127,7 @@ const DOM_PASS_THROUGH_KEYS = [
  * The keys this helper forwards.
  *
  * Exported so the SIBLING executor — `toHostProps`, which carries the declared
- * NON-DOM keys (objectui#7008) — can subtract this set from the contract and
+ * NON-DOM keys (`f08bcd9af`) — can subtract this set from the contract and
  * assert that the two together cover every declared key exactly once. Without
  * that subtraction there is no way to state "these keys are handled elsewhere"
  * as a compile-time fact rather than as a comment.
diff --git a/packages/fields/src/widgets/toHostProps.ts b/packages/fields/src/widgets/toHostProps.ts
index 7035903982..eb2b2ba8df 100644
--- a/packages/fields/src/widgets/toHostProps.ts
+++ b/packages/fields/src/widgets/toHostProps.ts
@@ -12,7 +12,7 @@ import type { FieldWidgetComponentProps } from './types.js';
 
 /**
  * The RUNTIME EXECUTOR of the NON-DOM half of {@link FieldWidgetComponentProps}
- * (objectui#7008) — the sibling of `toDomProps`, and deliberately a SEPARATE
+ * (`f08bcd9af`) — the sibling of `toDomProps`, and deliberately a SEPARATE
  * function rather than more entries in that whitelist.
  *
  * ## The defect
@@ -174,7 +174,7 @@ void _everyDeclaredHostKeyIsForwarded;
  * Direction 3 of 3: the two executors are DISJOINT — nothing forwarded here is
  * also a DOM pass-through key.
  *
- * Catches the specific mistake objectui#7008's ruling fences off: "route the
+ * Catches the specific mistake the ruling on the card behind `f08bcd9af` fences off: "route the
  * host-plumbing keys through `toDomProps`". Add `error` or `dataSource` to
  * `DOM_PASS_THROUGH_KEYS` and that file's own two assertions stay green (the
  * keys ARE declared) — this one is what goes red, because the key would leave
diff --git a/packages/fields/src/widgets/useFieldTranslation.ts b/packages/fields/src/widgets/useFieldTranslation.ts
index 539f0166d4..57d82d398a 100644
--- a/packages/fields/src/widgets/useFieldTranslation.ts
+++ b/packages/fields/src/widgets/useFieldTranslation.ts
@@ -118,7 +118,7 @@ const FIELD_DEFAULTS: Record<string, string> = {
   'fields.location.refusedFormat':
     'Not saved: enter a latitude, longitude pair (example: 30.2741, 120.1551).',
   'fields.location.refusedRange': 'Not saved: {{detail}}',
-  // objectui#6888 — the THIRD refusal arm (`12abc, 34`), added by objectui#6715
+  // `320374d2a` — the THIRD refusal arm (`12abc, 34`), added by objectui#6715
   // after #6755's ruling was written and therefore outside the three sentences
   // it named. All three arms share one `<p>`, so a literal here made ONE line
   // bilingual rather than one screen.
diff --git a/packages/i18n/src/locales/en.ts b/packages/i18n/src/locales/en.ts
index 94c3513e22..214f9f1b41 100644
--- a/packages/i18n/src/locales/en.ts
+++ b/packages/i18n/src/locales/en.ts
@@ -201,7 +201,7 @@ const en = {
     uploadInFlight: 'Wait for the upload to finish before saving.',
     // The notice the record form raises when a field's own `visibleWhen` turns
     // it invisible and the form clears the value it held (objectui#8070 names
-    // the objectui#6958 clear). `{{fields}}` is the cleared fields' labels joined
+    // the `6a449fc49` clear). `{{fields}}` is the cleared fields' labels joined
     // with `validation.formInvalidJoiner`. A list after a colon, so no word has
     // to agree with how many fields were cleared.
     clearedOnHide: 'Cleared — no longer applicable given the current values: {{fields}}',
diff --git a/packages/plugin-chatbot/src/renderer.tsx b/packages/plugin-chatbot/src/renderer.tsx
index dfcde8353a..1e20b6a3a9 100644
--- a/packages/plugin-chatbot/src/renderer.tsx
+++ b/packages/plugin-chatbot/src/renderer.tsx
@@ -391,9 +391,9 @@ ComponentRegistry.register('chatbot-floating',
   // spread after that prop, so the verdict overrode the raw value on every
   // render. Naming it changes no outcome; it keeps one carrier for one
   // question (AGENTS.md #0.1) and lets the published face inherit
-  // `BaseSchema.disabled` (`boolean | string`) unnarrowed (objectui#7087) —
+  // `BaseSchema.disabled` (`boolean | string`) unnarrowed (`c93b4d5f3`) —
   // a raw forward of that union into the panel's `boolean` prop would not
-  // type-check, and narrowing the face to make it fit is the shape #7087
+  // type-check, and narrowing the face to make it fit is the shape `c93b4d5f3`
   // retired.
   ({ schema, className, disabled: hostDisabled, ...props }: { schema: ChatbotFloatingSchema; className?: string; disabled?: boolean; [key: string]: any }) => {
     const {
diff --git a/packages/plugin-grid/src/ObjectGrid.tsx b/packages/plugin-grid/src/ObjectGrid.tsx
index 597881f3a7..184e0a84c0 100644
--- a/packages/plugin-grid/src/ObjectGrid.tsx
+++ b/packages/plugin-grid/src/ObjectGrid.tsx
@@ -1100,7 +1100,7 @@ export type ObjectGridColumn =
  *     `disableInnerScroll`, `borderless`) was already declared then, and is
  *     still declared now;
  *   - the two keys that survived that diff, `renderCellEditor` and
- *     `cellClassName`, were DECLARED by objectui#6882 (maintainer ruling
+ *     `cellClassName`, were DECLARED by `bf97b98c8` (maintainer ruling
  *     2026-08-30) on three surfaces:
  *       · `packages/types/src/data-display.ts` — the members themselves
  *       · `packages/types/src/zod/data-display.zod.ts` — the Zod mirror
@@ -1124,7 +1124,7 @@ export type ObjectGridColumn =
  *     was — a returned widget takes the cell, `null` falls through to the
  *     built-in text / number / date inputs.
  *   - `cellClassName` — said HELD, and described the key as folded "into every
- *     body cell's `className`". The hold is over (declared by the same #6882);
+ *     body cell's `className`". The hold is over (declared by the same `bf97b98c8`);
  *     the DESCRIPTION was wrong from the day it was written, which is the more
  *     useful half of this correction. Measured: `data-table.tsx` folds the
  *     SCHEMA-level key at exactly three sites and every one is a UTILITY cell —
@@ -1136,9 +1136,9 @@ export type ObjectGridColumn =
  *     their density, because `applyDensity` below puts the same class on every
  *     column. What breaks is the checkbox / row-number / row-actions cells
  *     falling out of height alignment with the data beside them, which is why
- *     this grid sets BOTH slots. #6882's declaration is where the authoritative
+ *     this grid sets BOTH slots. `bf97b98c8`'s declaration is where the authoritative
  *     version of this now lives; this is the local copy agreeing with it.
- *     ⭐ GUARDED SINCE objectui#6921: the cell set is MEASURED in the rendered
+ *     ⭐ GUARDED SINCE `4eb665bcf`: the cell set is MEASURED in the rendered
  *     DOM by `packages/components/src/renderers/complex/__tests__/`
  *     `data-table-cellClassName-population-6921.test.tsx` — the fence (a data
  *     cell does NOT fold this key) and the non-regression (the three utility
@@ -1150,7 +1150,7 @@ export type ObjectGridColumn =
  * ⛔ The old closing note ("do not fix either hold by declaring the key on
  * `DataTableSchema` as a rider — that package is published surface with its own
  * review floor") governs nothing now. It was asking for the ruling to be taken
- * deliberately at that package's floor, and that is exactly how #6882 took it.
+ * deliberately at that package's floor, and that is exactly how `bf97b98c8` took it.
  */
 type RemoveIndexSignature<T> = {
   [K in keyof T as string extends K ? never : number extends K ? never : K]: T[K];
@@ -1167,7 +1167,7 @@ export type DeclaredDataTableSchema = RemoveIndexSignature<DataTableSchema>;
  * ⚠️ "Undeclared by `DataTableSchema`" was this type's ENTRY CONDITION, and —
  * exactly as `ObjectGridColumnHolds` warns about its own — it is a claim about
  * ANOTHER package that can stop being true with nothing going red here. It
- * stopped being true on 2026-08-30: objectui#6882 declared BOTH members. As of
+ * stopped being true on 2026-08-30: `bf97b98c8` declared BOTH members. As of
  * objectui#7196 this type holds nothing; every member is redundant with
  * `DeclaredDataTableSchema`.
  *
@@ -1212,7 +1212,7 @@ export type DeclaredDataTableSchema = RemoveIndexSignature<DataTableSchema>;
  */
 export type ObjectGridDataTableSchemaHolds = {
   /**
-   * REDUNDANT since objectui#6882 (2026-08-30) — `DataTableSchema` declares this
+   * REDUNDANT since `bf97b98c8` (2026-08-30) — `DataTableSchema` declares this
    * key itself now, with a shape measured `Equal` to this one. `data-table`
    * calls it to render a host cell editor; returning `null` falls through to the
    * built-in text / number / date inputs. objectui#7188 added `pendingRow` (the
@@ -1231,7 +1231,7 @@ export type ObjectGridDataTableSchemaHolds = {
     cancel: () => void;
   }) => React.ReactNode;
   /**
-   * REDUNDANT since objectui#6882 (2026-08-30) — `DataTableSchema` declares this
+   * REDUNDANT since `bf97b98c8` (2026-08-30) — `DataTableSchema` declares this
    * key itself now, with a shape measured `Equal` to this one. `data-table`
    * folds it into the three UTILITY body cells (selection, row-number,
    * row-actions) and never into a data cell, which folds
@@ -5011,7 +5011,7 @@ export const ObjectGrid: React.FC<ObjectGridComponentProps> = ({
               // the child before anything is saved — the form's semantics.
               // `ctx.row` alone was #7165's interim and scoped by the SAVED
               // parent. `pendingRow` is a REQUIRED member of the declared
-              // context (`@object-ui/types`, objectui#6882 + #7188), so the
+              // context (`@object-ui/types`, `bf97b98c8` + #7188), so the
               // `?? ctx.row` never selects for a conforming host; it is spelled
               // so a context handed to this factory WITHOUT it degrades to the
               // saved-row scoping rather than to `{}` — gated forever — and it
diff --git a/packages/plugin-grid/src/__tests__/cellClassNameCensusProse-6921.test.ts b/packages/plugin-grid/src/__tests__/cellClassNameCensusProse-6921.test.ts
index 0647fa0760..f00eec69b9 100644
--- a/packages/plugin-grid/src/__tests__/cellClassNameCensusProse-6921.test.ts
+++ b/packages/plugin-grid/src/__tests__/cellClassNameCensusProse-6921.test.ts
@@ -177,7 +177,7 @@ describe('objectui#6921 — the ObjectGrid schema-slot census names the cells ce
   it('the entry records the hold as OVER and no longer carries the stale HELD-pending wording', () => {
     const entry = censusEntry('cellClassName')!;
     expect(entry).toMatch(/hold is over/i);
-    expect(entry).toMatch(/objectui#6882|#6882/);
+    expect(entry).toMatch(/bf97b98c8/);
     expect(entry).not.toMatch(/HELD\. Live/);
     expect(entry).not.toMatch(/pending ruling/i);
     expect(entry).not.toMatch(/folds (it|them|the key) into every body cell/i);
@@ -191,7 +191,7 @@ describe('objectui#6921 — the ObjectGrid schema-slot census names the cells ce
   it('the ObjectGridDataTableSchemaHolds member docblock agrees: redundant since #6882, three utility cells, never a data cell', () => {
     const doc = holdsMemberDoc('cellClassName')!;
     expect(doc).not.toBeNull();
-    expect(doc).toMatch(/REDUNDANT since objectui#6882/);
+    expect(doc).toMatch(/REDUNDANT since `bf97b98c8`/);
     for (const cell of MEASURED_UTILITY_CELLS) {
       expect(doc, `member docblock should name the ${cell} cell`).toMatch(new RegExp(cell, 'i'));
     }
diff --git a/packages/plugin-kanban/src/RequiredFieldsDialog.tsx b/packages/plugin-kanban/src/RequiredFieldsDialog.tsx
index 804761e6bf..5d62cb749c 100644
--- a/packages/plugin-kanban/src/RequiredFieldsDialog.tsx
+++ b/packages/plugin-kanban/src/RequiredFieldsDialog.tsx
@@ -120,7 +120,7 @@ export function RequiredFieldsDialog({
               // FALSE since objectui#7009 put `id` in `DOM_PASS_THROUGH_KEYS`:
               // the factory takes an `id` and lands it on the real control.
               // The reason is corrected rather than the markup changed
-              // (objectui#7008), because a dead constraint left in a comment is
+              // (`f08bcd9af`), because a dead constraint left in a comment is
               // how the next reader concludes it still binds.
               //
               // The wrapping form is still the right choice here, for a reason
@@ -143,7 +143,7 @@ export function RequiredFieldsDialog({
                     setValues((prev) => ({ ...prev, [f.name]: v }))
                   }
                   readonly={submitting}
-                  // The a11y half of the red text below (objectui#7008). The
+                  // The a11y half of the red text below (`f08bcd9af`). The
                   // dialog has always COMPUTED this state and shown it to a
                   // sighted user; until `FieldEditWidget` forwarded the declared
                   // `error` key there was no way to hand it to the control, so
diff --git a/packages/plugin-timeline/src/renderer.tsx b/packages/plugin-timeline/src/renderer.tsx
index cc4cf9f1b1..f46f58bf9c 100644
--- a/packages/plugin-timeline/src/renderer.tsx
+++ b/packages/plugin-timeline/src/renderer.tsx
@@ -443,7 +443,7 @@ function calculateDateRange(rows: readonly GanttRow[]): { minDate: string; maxDa
  * reached `Date.prototype[Symbol.toPrimitive]`, reached
  * `Date.prototype.toString` on a receiver with no slot, and took the render
  * down with it. That is a blank screen where a named diagnostic belongs, which
- * is the exact failure mode #6781 put the type gate here to remove and #6907
+ * is the exact failure mode #6781 put the type gate here to remove and `7fc5c3c12`
  * removed one function downstream.
  *
  * `instanceof` is not even total on its own terms: it walks
@@ -455,7 +455,7 @@ function calculateDateRange(rows: readonly GanttRow[]): { minDate: string; maxDa
  * - `Object.prototype.toString.call(value) === '[object Date]'` performs
  *   `Get(O, @@toStringTag)` UNCONDITIONALLY (ES2015 19.1.3.6 step 16), even
  *   once the builtin tag is decided. A `@@toStringTag` getter that throws is
- *   an authored value, and #6907 measured that exact input crashing the
+ *   an authored value, and `7fc5c3c12` measured that exact input crashing the
  *   speller. It trades an impostor crash for a getter crash.
  * - `Number.isFinite(value.getTime())` calls the AUTHOR'S `getTime`. A
  *   `class X extends Date` that overrides it is a REAL Date — `super()` gave
@@ -492,7 +492,7 @@ const isDate = (value: unknown): value is Date => {
 
 /**
  * How a gantt date value is SPELLED inside a diagnostic (objectui#6759,
- * ruled into a rule by objectui#6907).
+ * ruled into a rule by `7fc5c3c12`).
  *
  * ## THE RULE
  *
@@ -512,7 +512,7 @@ const isDate = (value: unknown): value is Date => {
  * ## Why the old `String` fallback had to go — three faults, all measured
  *
  * The fallback was written by #6759 when nothing but `[object Object]`-shaped
- * values could reach it. #6905 (the #6781 type rule) routes the whole
+ * values could reach it. `85f6a6097` (the #6781 type rule) routes the whole
  * non-date type space through it. Measured on this card's base b458300ca, one
  * row item and a throwaway probe (`startDate: '2024-01-01'`, `endDate` varied):
  *
@@ -539,7 +539,7 @@ const isDate = (value: unknown): value is Date => {
  *    no hint that the wrapper is the fault.
  * 3. It THROWS. The last three rows are live crashes on `main`, and they are
  *    the reason this is not a cosmetic card. #6759 declared this helper "total
- *    by construction" and #6905 made that property load-bearing by putting the
+ *    by construction" and `85f6a6097` made that property load-bearing by putting the
  *    type gate BEFORE `new Date`. But the gate only stopped `new Date` from
  *    throwing; `String(value)` still handed control to author code one line
  *    later, so the crash class did not go away — it moved from
@@ -581,7 +581,7 @@ const isDate = (value: unknown): value is Date => {
  * - `undefined` / `null` -> themselves (#6759 / #6770's pins; how an author
  *   reads a key they forgot to write versus one they wrote as empty).
  * - `symbol` -> `Symbol(desc)` via `Symbol.prototype.toString`, which no
- *   instance can override. `String(aSymbol)` THROWS; #6905's type-first
+ *   instance can override. `String(aSymbol)` THROWS; `85f6a6097`'s type-first
  *   ordering is what finally made this branch reachable.
  * - `bigint` -> the LITERAL, with its `n`. `String(0n)` is `"0"`, which is
  *   fault 2; `${value}n` is what the author typed and is unmistakable.
@@ -606,7 +606,7 @@ const isDate = (value: unknown): value is Date => {
  *   more informative spelling is the non-total one. `Array.isArray` reads no
  *   property and is STILL not total — on a revoked `Proxy` it throws. That is
  *   the one exclusion this docblock claims, and it is stated and exercised
- *   rather than repaired: see the objectui#7036 note below.
+ *   rather than repaired: see the `869b876c8` note below.
  *
  * All eight `typeof` results are covered and no branch falls through to author
  * code. The single reflective operation it performs is the Date test, which is
@@ -622,9 +622,9 @@ const isDate = (value: unknown): value is Date => {
  * operation adds no throw site because it HAS none — not because the gate
  * absorbed it first.
  *
- * ⚠️ objectui#7036 — READ THE TWO PARAGRAPHS ABOVE AS A SEQUENCE, NOT AS A
+ * ⚠️ `869b876c8` — READ THE TWO PARAGRAPHS ABOVE AS A SEQUENCE, NOT AS A
  * CONCLUSION. Each was written as the settled answer and the next card's
- * measurement moved it (#6759 -> #6905 -> #6907 -> #7027). This is the fifth
+ * measurement moved it (#6759 -> `85f6a6097` -> `7fc5c3c12` -> #7027). This is the fifth
  * entry and it is deliberately NOT a fifth claim of totality. The sentence it
  * falsifies is the one directly above the #7027 note: this function DOES add
  * a throw site the accept gate does not have, and it is `Array.isArray`.
@@ -938,7 +938,7 @@ type UnusableGanttDate = { path: string; value: unknown };
  * `timeline-gantt-date-brand-7027.test.tsx`.
  *
  * ⛔ That is the fourth totality claim in this code path and the third to be
- * falsified by the next card's measurement (#6759 -> #6905 -> #6907 -> this).
+ * falsified by the next card's measurement (#6759 -> `85f6a6097` -> `7fc5c3c12` -> this).
  * The pattern is the lesson: totality asserted in prose is a hypothesis, and
  * the only thing that has ever settled it here is an exercised input set. Do
  * not answer a future gap with a fifth sentence — add the row to that file.
@@ -957,12 +957,12 @@ const isGanttDateType = (value: unknown): value is string | number | Date =>
 
 /**
  * WHAT THE ROW WALK BELOW READS, AND WHERE THAT READING IS NOT TOTAL —
- * objectui#7153, the enumeration objectui#7036's docblock pointed at.
+ * objectui#7153, the enumeration `869b876c8`'s docblock pointed at.
  *
  * ## Read this as a BOUNDED READING, not as a totality claim
  *
  * Five cards before this one made a totality claim about this code path
- * (#6759 -> #6905 -> #6907 -> #7027 -> #7036) and FOUR were falsified by the
+ * (#6759 -> `85f6a6097` -> `7fc5c3c12` -> #7027 -> `869b876c8`) and FOUR were falsified by the
  * next card's measurement. #7153 is the fourth falsification: it measured that
  * `spellGanttDateValue`'s `Array.isArray` is not "the last non-total operation
  * on the gantt date path", only the last one inside that function.
@@ -991,7 +991,7 @@ const isGanttDateType = (value: unknown): value is string | number | Date =>
  *                                           the item has a throwing date getter
  *
  * SIX here, and THREE more in `calculateDateRange` (see that function). NINE
- * measured, where #7153's card said five and #7036's docblock repeated it. The
+ * measured, where #7153's card said five and `869b876c8`'s docblock repeated it. The
  * count was never the point, but it is the evidence that prose counting on
  * this path is a hypothesis: both numbers were written after a real
  * measurement, and both were short.
@@ -1034,9 +1034,9 @@ const isGanttDateType = (value: unknown): value is string | number | Date =>
  *    true of the six and was false of the three, and collapsing the two is how
  *    this docblock would start overclaiming again.
  *
- * ## WHY A `catch` IS NOT PUT HERE — re-tested, not inherited from #7036
+ * ## WHY A `catch` IS NOT PUT HERE — re-tested, not inherited from `869b876c8`
  *
- * #7036 refused a `catch` at the speller because it would SUBSTITUTE `an
+ * `869b876c8` refused a `catch` at the speller because it would SUBSTITUTE `an
  * object` for a failure rather than read anything, the opposite of `isDate`'s
  * `catch` (which IS the read, because the language exposes `[[DateValue]]`
  * only by throwing). #7153's dispatch required that argument to be re-tested
@@ -1055,18 +1055,18 @@ const isGanttDateType = (value: unknown): value is string | number | Date =>
  * in the `{value}` hole of `timeline.gantt.unusableRange.malformedDate`. There
  * is no true spelling for a value that cannot be touched, so a real repair
  * needs a value-less diagnostic, which is a new i18n key across ten locale
- * packs: the file surface #7036 deferred as a separate decision.
+ * packs: the file surface the card behind `869b876c8` deferred as a separate decision.
  *
- * And the coverage is the same shape of error #7036's triage caught. That
+ * And the coverage is the same shape of error the triage of the card behind `869b876c8` caught. That
  * `catch` converted THREE of the nine measured sites (U5, U6, and the
  * throwing-getter item) and left the other six throwing — U1 through U4 are
  * upstream of it, and `calculateDateRange`'s three are downstream. The PASSING
  * control held either way: an ordinary row drew 1 bar over a 3-cell axis
  * before and after. One `catch` here would buy 3 of 9 while a docblock went on
- * implying the walk was safe, which is exactly the "1 of 6" trade #7036 was
- * stopped from making.
+ * implying the walk was safe, which is exactly the "1 of 6" trade the card behind
+ * `869b876c8` was stopped from making.
  *
- * ## So this is STATED AND EXERCISED, on #7036's terms
+ * ## So this is STATED AND EXERCISED, on `869b876c8`'s terms
  *
  * The rows are in `./__tests__/timeline-gantt-date-brand-7027.test.tsx`, pin
  * 5, asserting each throw's own MESSAGE so the pin fails if a site MOVES as
diff --git a/packages/test-support/src/defaults-table-scan.ts b/packages/test-support/src/defaults-table-scan.ts
index 93e0a8eae9..b582058b2f 100644
--- a/packages/test-support/src/defaults-table-scan.ts
+++ b/packages/test-support/src/defaults-table-scan.ts
@@ -127,7 +127,7 @@ export interface HandRolledTable {
  * value-compare over these tables (objectui#7567 Q2's B half). That gate is a
  * bare `node scripts/check-*.mjs`, so it cannot import this module at all —
  * `exports["./defaults-table-scan"]` resolves to TypeScript SOURCE with no build
- * artefact. The shape here is the one objectui#6923 already ruled for exactly
+ * artefact. The shape here is the one the 2026-08-31 ruling (`d3bf4fa6f`) already set for exactly
  * that wall, and `zod-wrapper-keys.json` is its first instance: the DATA moves
  * to build-free JSON with its own `exports` subpath
  * (`@object-ui/test-support/hand-rolled-tables`), `resolveJsonModule` types it
diff --git a/packages/test-support/src/index.ts b/packages/test-support/src/index.ts
index c07f615605..27b38c9041 100644
--- a/packages/test-support/src/index.ts
+++ b/packages/test-support/src/index.ts
@@ -60,7 +60,7 @@ export { enumOptions, shapeEnumOptions } from './spec-enum-options';
 export { arrayElementSchema } from './spec-array-element';
 
 /**
- * The Zod wrapper-key vocabulary (objectui#6923). The DATA lives in
+ * The Zod wrapper-key vocabulary (`d3bf4fa6f`). The DATA lives in
  * `zod-wrapper-keys.json` so that `node scripts/check-*.mjs` can read the same
  * bytes through `@object-ui/test-support/zod-wrapper-keys` — the one thing this
  * package's `.` entry, being TypeScript source, cannot offer a bare-node
diff --git a/packages/test-support/src/spec-enum-options.ts b/packages/test-support/src/spec-enum-options.ts
index 46a91e65a1..5b65023864 100644
--- a/packages/test-support/src/spec-enum-options.ts
+++ b/packages/test-support/src/spec-enum-options.ts
@@ -8,7 +8,7 @@
 
 /**
  * SPEC ENUM VOCABULARY — one reader for every parity gate that asks
- * "which names does this contract accept?" (objectui#5872, objectui#6924).
+ * "which names does this contract accept?" (objectui#5872, `78e98bf44`).
  *
  * Two exports, ONE walk. `enumOptions(node)` reads the vocabulary at each level
  * of that walk; `shapeEnumOptions` is the same reader entered through a shape
@@ -64,7 +64,7 @@
  * installed pin (`@objectstack/spec@17.2.0`, `zod@4.4.3`) it returns the
  * identical array, in the identical order, for all four (schema, key) pairs.
  *
- * ## Two entry points, one walk (objectui#6924)
+ * ## Two entry points, one walk (`78e98bf44`)
  *
  * A SECOND, larger family — 16 call sites across 11 packages — asked the same
  * question of a node that IS the enum: a top-level `z.enum` imported straight
@@ -102,7 +102,7 @@ import { firstInWrapperChain } from './spec-zod-wrappers';
  * `.nullable()` — `[]` when it cannot be read.
  *
  * Takes the node itself, so it answers for a top-level `z.enum` imported from
- * `@objectstack/spec` (objectui#6924's family) and for a shape member the
+ * `@objectstack/spec` (`78e98bf44`'s family) and for a shape member the
  * caller already holds. `shapeEnumOptions` is this same walk entered through
  * `resolvePropsShape`.
  *
diff --git a/packages/test-support/src/zod-wrapper-keys.ts b/packages/test-support/src/zod-wrapper-keys.ts
index ed90796308..ef66bc4acf 100644
--- a/packages/test-support/src/zod-wrapper-keys.ts
+++ b/packages/test-support/src/zod-wrapper-keys.ts
@@ -8,7 +8,7 @@
 
 /**
  * ZOD WRAPPER KEYS — the one literal list both language sides read
- * (objectui#6923, ruled 2026-08-31; objectui#5872 class (3)).
+ * (`d3bf4fa6f`, ruled 2026-08-31; objectui#5872 class (3)).
  *
  * ## What the list is
  *
@@ -24,7 +24,7 @@
  * they now span a language boundary. `@object-ui/test-support` is `private:
  * true` and its `exports["."]` resolves to `./src/index.ts` — TypeScript
  * SOURCE — so a bare `node scripts/check-*.mjs` cannot import it and there is
- * no build artefact for it to reach. That is the wall objectui#6923 was filed
+ * no build artefact for it to reach. That is the wall the card behind `d3bf4fa6f` was filed
  * to get a ruling on, and the ruling's answer is this file's shape:
  *
  *   - the data lives in `zod-wrapper-keys.json`, which needs no build step and
diff --git a/packages/types/src/__tests__/action-callback-retired-7068.test.ts b/packages/types/src/__tests__/action-callback-retired-7068.test.ts
index 444baf2e08..0ae8f38df2 100644
--- a/packages/types/src/__tests__/action-callback-retired-7068.test.ts
+++ b/packages/types/src/__tests__/action-callback-retired-7068.test.ts
@@ -73,7 +73,7 @@ const CRUD_TS = resolve(__dirname, '../crud.ts');
  * acts on: the retired key, and where the live meaning lives.
  */
 const ON_SUCCESS_GUIDANCE =
-  'RETIRED (objectui#7068) — `onSuccess` is no longer part of this legacy ActionSchema; nothing reads '
+  'RETIRED (ADR-0049) — `onSuccess` is no longer part of this legacy ActionSchema; nothing reads '
   + 'it. It carried a Phase-2 `ActionCallback` object (`{ type: \'toast\' | \'message\' | \'redirect\' | '
   + '\'reload\' | \'custom\' | \'ajax\' | \'dialog\', message?, url?, api?, method?, dialog?, handler? }`) that '
   + 'no renderer or runner ever consumed — the THIRD meaning of this key — and that `@objectstack/spec`\'s '
@@ -82,7 +82,7 @@ const ON_SUCCESS_GUIDANCE =
   + 'UIActionSchema (objectui#5934); a success notice is `successMessage`. Retired under ADR-0049 '
   + 'enforce-or-remove with no deprecation window (maintainer ruling option 1, 2026-09-05).';
 const ON_FAILURE_GUIDANCE =
-  'RETIRED (objectui#7068) — `onFailure` is no longer part of this legacy ActionSchema; nothing reads '
+  'RETIRED (ADR-0049) — `onFailure` is no longer part of this legacy ActionSchema; nothing reads '
   + 'it. It carried the same Phase-2 `ActionCallback` object `onSuccess` carried, and '
   + '`@objectstack/spec`\'s ActionSchema declares no `onFailure` at all (an authored one is refused at '
   + 'publish as an unrecognized key). A failure notice is `errorMessage`. Retired under ADR-0049 '
diff --git a/packages/types/src/__tests__/layout-default-jsdoc-7361.test.ts b/packages/types/src/__tests__/layout-default-jsdoc-7361.test.ts
index 189ba6aba6..15e5a86db8 100644
--- a/packages/types/src/__tests__/layout-default-jsdoc-7361.test.ts
+++ b/packages/types/src/__tests__/layout-default-jsdoc-7361.test.ts
@@ -324,7 +324,7 @@ describe('layout.ts `@default` docs agree with the renderer, re-measured (object
     it('names the read site and the rule it belongs to', () => {
       const doc = docblockFor(interfaceBody(types, 'TextSchema'), 'variant');
       expect(doc).toContain('text.tsx');
-      expect(doc).toContain('6942');
+      expect(doc).toContain('57f9b077b');
     });
 
     /**
diff --git a/packages/types/src/base.ts b/packages/types/src/base.ts
index 33b3b21241..b1abfe909a 100644
--- a/packages/types/src/base.ts
+++ b/packages/types/src/base.ts
@@ -347,7 +347,7 @@ export interface BaseSchema {
    * When false, the component is NOT RENDERED: `SchemaRenderer` returns `null`
    * for the node. Nothing emits `display: none` — the element never reaches the
    * DOM at all, and `hidden: true` one slot below takes this exact same path
-   * (objectui#7088).
+   * (`c1fe272ad`).
    *
    * Accepts a PREDICATE STRING as well as a boolean (objectui#4581): the
    * renderer does not read this key as a boolean, it evaluates it —
@@ -398,7 +398,7 @@ export interface BaseSchema {
    * `visibility: hidden`.
    *
    * ⚠️ `hidden` and `visible` are DELIBERATELY SYNONYMOUS — one hide path, not
-   * two behaviours (objectui#7088, ruled 2026-09-01). This comment used to
+   * two behaviours (`c1fe272ad`, ruled 2026-09-01). This comment used to
    * promise "rendered but not visible (visibility: hidden)", which the renderer
    * has never done: `_hidden` has exactly one consumer, the `return null` in
    * `SchemaRenderer.tsx`, and by the time it is read the key that set it is no
diff --git a/packages/types/src/complex.ts b/packages/types/src/complex.ts
index e59a2affbe..b459d27008 100644
--- a/packages/types/src/complex.ts
+++ b/packages/types/src/complex.ts
@@ -1737,7 +1737,7 @@ export type ChatbotSharedKey =
  * {@link BaseSchema}: `SchemaRenderer` evaluates `disabled` / `disabledOn`
  * for every node type and hands the verdict to the registration as a prop, so
  * redeclaring `disabled` here as `boolean` would only narrow away the
- * expression-string half of an inherited field (objectui#6169, #7087).
+ * expression-string half of an inherited field (objectui#6169, `c93b4d5f3`).
  */
 export interface ChatbotEnhancedSchema
   extends BaseSchema,
diff --git a/packages/types/src/crud.ts b/packages/types/src/crud.ts
index 33b51eff3c..9fafc277ea 100644
--- a/packages/types/src/crud.ts
+++ b/packages/types/src/crud.ts
@@ -24,7 +24,7 @@ import type { BaseSchema, SchemaNode } from './base.js';
 export type ActionExecutionMode = 'sequential' | 'parallel';
 
 // `ActionCallback` — the Phase-2 callback object the legacy `ActionSchema.onSuccess` /
-// `onFailure` keys carried — was DELETED by objectui#7068 (the objectui#7664 route for
+// `onFailure` keys carried — was DELETED by `6bca0e4e8` (the objectui#7664 route for
 // a standalone retired type: name gone from both faces and from the barrels, absence
 // pinned). The two keys below stay declared as `?: never` tombstones so an authored
 // callback is a `tsc` error at the site instead of a silent index-signature admit;
@@ -144,7 +144,7 @@ export interface ActionSchema extends BaseSchema {
    */
   errorMessage?: string;
   /**
-   * RETIRED (objectui#7068, ADR-0049 enforce-or-remove) — the Phase-2 success
+   * RETIRED (`6bca0e4e8`, ADR-0049 enforce-or-remove) — the Phase-2 success
    * callback, an `ActionCallback` object (`{ type: 'toast' | 'message' | 'redirect'
    * | 'reload' | 'custom' | 'ajax' | 'dialog', message?, url?, api?, method?,
    * dialog?, handler? }`). Measured before the retirement: zero producers outside
@@ -166,7 +166,7 @@ export interface ActionSchema extends BaseSchema {
    */
   onSuccess?: never;
   /**
-   * RETIRED (objectui#7068, ADR-0049 enforce-or-remove) — the Phase-2 failure
+   * RETIRED (`6bca0e4e8`, ADR-0049 enforce-or-remove) — the Phase-2 failure
    * callback, the same `ActionCallback` object shape {@link ActionSchema.onSuccess}
    * carried. Zero producers, zero runtime readers (measured, see `onSuccess`), and
    * `@objectstack/spec`'s `ActionSchema` declares no `onFailure` at all — an
diff --git a/packages/types/src/data-display.ts b/packages/types/src/data-display.ts
index 58b3f146a2..49b29d28d2 100644
--- a/packages/types/src/data-display.ts
+++ b/packages/types/src/data-display.ts
@@ -1374,7 +1374,7 @@ export interface DataTableSchema extends BaseSchema {
    */
   singleClickEdit?: boolean;
   /**
-   * Host-supplied cell editor for inline editing (objectui#6882).
+   * Host-supplied cell editor for inline editing (`bf97b98c8`).
    *
    * RUNTIME SLOT (objectui#7759 group E, objectui#6124 shape) — a host-supplied
    * function, NOT authorable metadata: JSON has no function value, so the zod
@@ -1394,7 +1394,7 @@ export interface DataTableSchema extends BaseSchema {
    * input, Escape cancels, click-outside commits); `stage` records a value
    * without leaving edit mode, `commit` saves, `cancel` discards.
    *
-   * ⚠️ Declared as of objectui#6882 (maintainer ruling 2026-08-30). `data-table`
+   * ⚠️ Declared as of `bf97b98c8` (maintainer ruling 2026-08-30). `data-table`
    * has read this key on the production path since inline editing landed — it
    * did so through a `(schema as any)` cast, which existed for no reason other
    * than this declaration's absence and is gone with it. Nothing new runs; a
@@ -1506,7 +1506,7 @@ export interface DataTableSchema extends BaseSchema {
   rowStyle?: (row: any, index: number) => React.CSSProperties | undefined;
   /**
    * Extra CSS classes folded into the table's UTILITY body cells
-   * (objectui#6882) — and ONLY those three, each rendered only when its
+   * (`bf97b98c8`) — and ONLY those three, each rendered only when its
    * feature is on: the leading selection-checkbox cell (`selectable`), the
    * row-number cell (`showRowNumbers`), and the trailing row-actions cell
    * (`rowActions`).
@@ -1528,7 +1528,7 @@ export interface DataTableSchema extends BaseSchema {
    * them. Setting only this key leaves every data cell at the table
    * primitive's default `p-4`.
    *
-   * ⚠️ Declared as of objectui#6882 (maintainer ruling 2026-08-30). `data-table`
+   * ⚠️ Declared as of `bf97b98c8` (maintainer ruling 2026-08-30). `data-table`
    * has destructured this key off the schema and folded it into those three
    * cells all along; only the declaration was missing. `string` matches
    * {@link BaseSchema.className} and {@link TableColumn.cellClassName} — the
diff --git a/packages/types/src/layout.ts b/packages/types/src/layout.ts
index a1f0114fb6..502da1ea87 100644
--- a/packages/types/src/layout.ts
+++ b/packages/types/src/layout.ts
@@ -167,7 +167,7 @@ export interface TextSchema extends BaseSchema {
    * NO `@default`, deliberately (objectui#7735). `text.tsx` reads this as
    * `schema.variant ? VARIANT_CLASS[schema.variant] : undefined`, so a node
    * that omits the key gets NO typography class and no wrapping tag — absence
-   * is not `body`, which is the whole point of objectui#6942 and is spelled out
+   * is not `body`, which is the whole point of `57f9b077b` and is spelled out
    * at that read site. The retired `@default 'body'` described the zod mirror's
    * `.default('body')`, which substituted the value into a PARSED document and
    * which objectui#7735 removed; no renderer ever applied it.
diff --git a/packages/types/src/zod/base.zod.ts b/packages/types/src/zod/base.zod.ts
index c77e70b866..6ebc53f93a 100644
--- a/packages/types/src/zod/base.zod.ts
+++ b/packages/types/src/zod/base.zod.ts
@@ -272,7 +272,7 @@ export function defineNodeComponentUnion<T extends z.ZodType>(union: T): T {
  *
  * ⭐ What #7760 bought: `__tests__/zod-mirror-parity.test.ts` can now compare the
  * `z.union([SchemaNodeSchema, z.array(SchemaNodeSchema)])` single-or-list slots that
- * objectui#7069 called this repo's systematic producer and had to EXCLUDE — its
+ * the card behind `2760075ff` called this repo's systematic producer and had to EXCLUDE — its
  * `Unconstrained` predicate was dropping every one of them. Three real widenings came
  * out of that region on the first run and are ledgered there.
  *
diff --git a/packages/types/src/zod/crud.zod.ts b/packages/types/src/zod/crud.zod.ts
index e70c301567..c59f03d73d 100644
--- a/packages/types/src/zod/crud.zod.ts
+++ b/packages/types/src/zod/crud.zod.ts
@@ -29,7 +29,7 @@ import type { ActionSchema as ActionDeclaration } from '../crud.js';
 export const ActionExecutionModeSchema = z.enum(['sequential', 'parallel']).describe('Action execution mode for chaining');
 
 // `ActionCallbackSchema` — the mirror of the Phase-2 `ActionCallback` object the legacy
-// `ActionSchema.onSuccess` / `onFailure` keys carried — was DELETED by objectui#7068
+// `ActionSchema.onSuccess` / `onFailure` keys carried — was DELETED by `6bca0e4e8`
 // (the objectui#7664 route for a standalone retired pair: const, TS declaration and
 // barrel exports gone, parity-ledger rows removed, absence pinned in
 // `../__tests__/action-callback-retired-7068.test.ts`). The two keys below stay
@@ -85,7 +85,7 @@ export const ActionSchema: z.ZodType<ActionDeclaration, ActionDeclaration> = z.l
   // loud parse rejection (absent stays valid), mirroring how `@objectstack/spec`
   // retires keys. One confirm spelling: `confirmText` below.
   // This key ESTABLISHED the convention and was the last one still answering
-  // with zod's generic `expected never`; objectui#6931 routes it through
+  // with zod's generic `expected never`; `8063bcbdc` routes it through
   // `retirementTombstone()` so the refusal carries the remedy it teaches.
   confirm: retirementTombstone('RETIRED (objectui#4314) — author confirmText instead'),
   confirmText: z.string().optional().describe('Confirmation message — shows a confirm dialog before executing'),
@@ -97,7 +97,7 @@ export const ActionSchema: z.ZodType<ActionDeclaration, ActionDeclaration> = z.l
   }).optional().describe('Dialog configuration (for dialog actions)'),
   successMessage: z.string().optional().describe('Success message after execution'),
   errorMessage: z.string().optional().describe('Error message on failure'),
-  // ADR-0049 RETIREMENT TOMBSTONES (objectui#7068, maintainer ruling option 1 of
+  // ADR-0049 RETIREMENT TOMBSTONES (`6bca0e4e8`, maintainer ruling option 1 of
   // 2026-09-05). Both keys carried a Phase-2 `ActionCallback` object that no renderer
   // or runner ever read and that the spec refuses at publish (`onSuccess`: wrong
   // block shape; `onFailure`: no such key). A plain deletion here would NOT refuse
@@ -107,7 +107,7 @@ export const ActionSchema: z.ZodType<ActionDeclaration, ActionDeclaration> = z.l
   // TS twins are `?: never` (`../crud.ts`). Pinned in
   // `../__tests__/action-callback-retired-7068.test.ts`.
   onSuccess: retirementTombstone(
-    'RETIRED (objectui#7068) — `onSuccess` is no longer part of this legacy ActionSchema; nothing reads '
+    'RETIRED (ADR-0049) — `onSuccess` is no longer part of this legacy ActionSchema; nothing reads '
     + 'it. It carried a Phase-2 `ActionCallback` object (`{ type: \'toast\' | \'message\' | \'redirect\' | '
     + '\'reload\' | \'custom\' | \'ajax\' | \'dialog\', message?, url?, api?, method?, dialog?, handler? }`) that '
     + 'no renderer or runner ever consumed — the THIRD meaning of this key — and that `@objectstack/spec`\'s '
@@ -117,7 +117,7 @@ export const ActionSchema: z.ZodType<ActionDeclaration, ActionDeclaration> = z.l
     + 'enforce-or-remove with no deprecation window (maintainer ruling option 1, 2026-09-05).',
   ),
   onFailure: retirementTombstone(
-    'RETIRED (objectui#7068) — `onFailure` is no longer part of this legacy ActionSchema; nothing reads '
+    'RETIRED (ADR-0049) — `onFailure` is no longer part of this legacy ActionSchema; nothing reads '
     + 'it. It carried the same Phase-2 `ActionCallback` object `onSuccess` carried, and '
     + '`@objectstack/spec`\'s ActionSchema declares no `onFailure` at all (an authored one is refused at '
     + 'publish as an unrecognized key). A failure notice is `errorMessage`. Retired under ADR-0049 '
@@ -131,7 +131,7 @@ export const ActionSchema: z.ZodType<ActionDeclaration, ActionDeclaration> = z.l
   // RUNTIME SLOT (objectui#7344): `ActionRunner` awaits `action.onClick()` and
   // the action renderers guard `typeof action.onClick === 'function'`. The
   // `z.any()` this replaces accepted an authored string or object that then
-  // reached that call (objectui#7069's mirror-wider-than-declared direction).
+  // reached that call (`2760075ff`'s mirror-wider-than-declared direction).
   onClick: handlerKeyRefusal('onClick', 'runtime-slot', 'Custom click handler'),
   redirect: z.string().optional().describe('Redirect URL after success'),
   tracking: z.object({
diff --git a/packages/types/src/zod/data-display.zod.ts b/packages/types/src/zod/data-display.zod.ts
index 517a43c838..72a46d8107 100644
--- a/packages/types/src/zod/data-display.zod.ts
+++ b/packages/types/src/zod/data-display.zod.ts
@@ -320,7 +320,7 @@ export const TableColumnSchema = z.object({
  * The later arrivals below (`headerIcon` / `fitContent`, objectui#6424;
  * `format` / `options` / `currency`, objectui#6425; `wrap`, objectui#6650;
  * `masked`, objectui#10583) were outside #6105's reviewed scope; the first
- * five carried the bare spelling until objectui#6931 converted them here
+ * five carried the bare spelling until `8063bcbdc` converted them here
  * (`wrap` and `masked` were born converted). That
  * mattered because a half-converted shape teaches worse than a uniform one:
  * an author reading guidance on nine keys and zod's generic on five learns the
@@ -359,7 +359,7 @@ export const StaticTableColumnSchema = z.object({
  * reference-page teaching describing behaviour that did not exist. An
  * authored value now fails parse loudly rather than doing nothing silently,
  * and the refusal carries its own remediation text through
- * `retirementTombstone()` (objectui#6931) rather than zod's generic
+ * `retirementTombstone()` (`8063bcbdc`) rather than zod's generic
  * `expected never`.
  */
 export const TableSchema = BaseSchema.extend({
@@ -403,7 +403,7 @@ export const DataTableSchema = BaseSchema.extend({
   selectable: z.union([z.boolean(), z.enum(['single', 'multiple'])]).optional().describe('Enable row selection — `true`/`multiple` = multi-select, `single` = replace-on-select with no select-all'),
   sortable: z.boolean().optional().describe('Enable sorting'),
   exportable: z.boolean().optional().describe('Enable data export'),
-  rowActions: z.boolean().optional().describe('Show the row actions column (edit/delete) — mirrors the boolean the renderer truthiness-tests (objectui#6940)'),
+  rowActions: z.boolean().optional().describe('Show the row actions column (edit/delete) — mirrors the boolean the renderer truthiness-tests'),
   resizableColumns: z.boolean().optional().describe('Allow column resizing'),
   reorderableColumns: z.boolean().optional().describe('Allow column reordering'),
   onRowEdit: handlerKeyRefusal('onRowEdit', 'runtime-slot', 'Row edit handler'),
@@ -463,7 +463,7 @@ export const DataTableSchema = BaseSchema.extend({
   onRowActionDef: handlerKeyRefusal('onRowActionDef', 'runtime-slot', 'Row action handler'),
   onRowClick: handlerKeyRefusal('onRowClick', 'runtime-slot', 'Row click handler'),
   onRowSave: handlerKeyRefusal('onRowSave', 'runtime-slot', 'Row save handler'),
-  cellClassName: z.string().optional().describe('Extra classes folded into the utility body cells only — the selection, row-number and row-actions cells; data cells fold the per-column `cellClassName` instead, so row density has to be set on both (objectui#6882)'),
+  cellClassName: z.string().optional().describe('Extra classes folded into the utility body cells only — the selection, row-number and row-actions cells; data cells fold the per-column `cellClassName` instead, so row density has to be set on both'),
   // RUNTIME SLOT (objectui#7759 group E, the objectui#6124 shape): `data-table`
   // reads `schema.renderCellEditor` and calls it with the edit context; its
   // supplier is `ObjectGrid` (`@object-ui/plugin-grid`). The context's shape —
@@ -506,8 +506,9 @@ export const DataTableSchema = BaseSchema.extend({
  * and the key retired. `components` was a `Record<string, any>` of React
  * overrides nothing read — not a JSON-authorable value, and no host path
  * consumes such a map either, so there is no runtime slot to keep. Both
- * refuse BY NAME through `retirementTombstone()` (objectui#6931), with the
- * remedy in the message, rather than parsing green and doing nothing. The TS
+ * refuse BY NAME through `retirementTombstone()`, the spelling `8063bcbdc`
+ * made uniform, with the remedy in the message, rather than parsing green and
+ * doing nothing. The TS
  * twins are `?: never` in `../data-display.ts`; both published faces carry the
  * refusal (`@object-ui/types`, and `@object-ui/plugin-markdown`'s re-export of
  * the same authority — objectui#6172).
@@ -1270,7 +1271,7 @@ const timelineItemsFitVariant = (
  * `timeScale` is RETIRED (objectui#6355), and `events` / `orientation` /
  * `position` are RETIRED (objectui#6170, ADR-0049 stage 2 — no renderer ever
  * read any of the three). All four carry the `retirementTombstone()` spelling
- * below (objectui#6931), each message naming what to author instead — still
+ * below (`8063bcbdc`), each message naming what to author instead — still
  * mirrored, deliberately, because the parity ratchet compares key SETS and
  * because a tombstone must be present on both halves to be audible.
  *
diff --git a/packages/types/src/zod/overlay.zod.ts b/packages/types/src/zod/overlay.zod.ts
index f0cc803742..a6bd98edd9 100644
--- a/packages/types/src/zod/overlay.zod.ts
+++ b/packages/types/src/zod/overlay.zod.ts
@@ -422,7 +422,7 @@ export const HoverCardSchema = BaseSchema.extend({
  * optional `label`, and why `type` is tombstoned on both arms.
  *
  * Both tombstones carry their guidance through `retirementTombstone()`
- * (objectui#6931), so the arm-level issue reads the remediation instead of
+ * (`8063bcbdc`), so the arm-level issue reads the remediation instead of
  * zod's generic `expected never`. Note what a UNION does to that: the
  * top-level issue this schema reports is zod's own `invalid_union`
  * (`"Invalid input"`, path `[]`), and the per-arm issues — where the guidance