Repository navigation
fix(plugin-form,components): master-detail edit lines and element:record_picker options re-read on the data-invalidation bus (objectui#10853) - #10873
Conversation
…er options re-read on the data-invalidation bus (objectui#10853) An edit-mode object-master-detail-form reads the bus for each detail collection's child object and re-reads that collection's lines in place; unsaved lines hold the re-read, replayed once after a revert or after the save lands. element:record_picker's option read names the nonce for its object; a re-read of the same query stays enabled over the options on screen and never touches the bound page variable. Also appends a dated note to the pending 10778 changeset: the drillDown.report drawer does re-read since objectui#10814. Claude-Session: https://claude.ai/code/session_01MCg3z5cGrV51xEddpGcxEY Co-authored-by: Claude <noreply@anthropic.com>
…ting row and child-schema types (objectui#10853) No behaviour change: the two annotations the reader added use `RowState['rows']` and `ChildSchema` instead of `any`, and an unused lint directive is dropped. Claude-Session: https://claude.ai/code/session_01MCg3z5cGrV51xEddpGcxEY Co-authored-by: Claude <noreply@anthropic.com>
|
changeset-claim-re-read
|
✅ Console Performance Budget
The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it. 📦 Bundle Size Report
Size Limits
|
Contract reviewServed-tier: 229/229 Read: card objectui#10853 body and its three comments (triage ① Derived judgments1. One bus, not a second channel — RIGHT. 2. Held dirty lines — WRONG on one path; the traced paths otherwise hold.
3. The picker — RIGHT. 4. Pins — RIGHT. 5. Prose and shape — RIGHT except the one sentence noted under 2. 6. Out-of-scope notes — all three RIGHT. (a) Read twice on mount: at base the load effect keys on ② Semver level
③ Boundary flags
Implemented-by: VERDICT: FAIL |
…on's bus re-read (objectui#10853) Contract review of ac526b1: the row editor ("Open row") keeps its draft in its own form, not in the collection's rows, so a bus re-read committed fresh rows under it and the editor's reset overwrote the draft (or re-pointed it at a neighbouring row when the server dropped the line). While the editor is open on a collection, that collection counts as unsaved for the re-read decision, a read already in flight does not commit under it, and the held re-read replays through the same path once the editor closes. The editor is not reset, re-keyed or disabled by a re-read. The failed-re-read warning names a collection that has not loaded yet accurately, and the changeset and linesUnsaved doc claim only what holds about the parent link. Claude-Session: https://claude.ai/code/session_01MCg3z5cGrV51xEddpGcxEY Co-authored-by: Claude <noreply@anthropic.com>
…w editor is held directly (objectui#10853) The in-flight commit guard held the read by asking again, which relied on the open editor also counting as unsaved; it now adds the collection to the held set itself, so the two checks do not depend on each other. Claude-Session: https://claude.ai/code/session_01MCg3z5cGrV51xEddpGcxEY Co-authored-by: Claude <noreply@anthropic.com>
✅ Console Performance Budget
The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it. 📦 Bundle Size Report
Size Limits
|
✅ Console Performance Budget
The eager closure is every chunk the entry reaches through static imports — what the browser fetches and parses before the app renders. The entry chunk on its own is a small fraction of it. 📦 Bundle Size Report
Size Limits
|
Contract reviewServed-tier: 82/82 Read: the previous record ( ① Derived judgments1. The row-editor defect is fixed — RIGHT.
2. No regression on the paths the previous record judged RIGHT — RIGHT.
3. The narrow-race wording — RIGHT. The 4. Prose — RIGHT.
5. Pins — RIGHT. The four new tests sit in the same file, rendered through 6. Carry-forward — RIGHT. ② Semver level
③ Boundary flags
Implemented-by: VERDICT: PASS |
…ts name 32 objectui issues that answer 404 (objectui#10803, batch 3) (objectstack-ai#10869) Part of objectstack-ai#10803 Clause-②: no Dispatched implementation of the `domain:ui` seat objectstack-ai#2 claim (comment `5860873556`) on objectui#10803, batch 3, session `https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN`; patch round 1 applies the seat ruling `5861129870` on the round's two open questions, and patch round 2 applies contract review `5861306588` (two wording fixes and one optional nit) and the ruling's amendment `5861311219`. Citations only: no sentence's claim moves, and every edited pending changeset's frontmatter is byte-identical. The runtime text that moves loses its dead pointer and nothing else: four ADR-0049 tombstone guidance strings and two zod `.describe()` strings in `@object-ui/types`, and the Studio CEL authoring advisory in `@object-ui/app-shell`. The six tests that pin the tombstone text, the two changesets and two `content/docs` pages that quote it follow the changed string, and nothing else in them moves. ## Why `Part of`, not a closing line The card stays open for the other 83 numbers of the family remainder (seat amendment `5860244997`, Q2 = A). ## The seat ruling `5861129870` and its amendment `5861311219`, as applied - **Q1, the tombstone guidance class: a seat variant of option A, as amended.** Each of the four runtime tombstone strings keeps the house `RETIRED (REF) —` shape with `ADR-0049` as the reference, in place of the dead card. The ruling first conditioned `ADR-0049` on the key's TypeScript twin comment naming it: the twins of `TreeViewSchema.data` and `ChartDataSeriesSchema.data` (`data-display.ts`) and of `TextSchema.value` (`layout.ts`) each read "RETIRED (SHA, ADR-0049 enforce-or-remove)", while the twin of `DashboardConfigSchema.aria` is a deletion note on `DashboardConfig` in `designer.ts` that names no ADR, so round 1 shipped `RETIRED —` there. The amendment `5861311219` corrects that proxy: the `aria` retirement is itself ADR-0049 (the comment above `DashboardConfigSchema` in `complex.zod.ts`, its landing commit `e7957ab87`, and the pending `dashboard-config-aria-retired-5852.md` all say so), so `aria`'s error and describe strings also open `RETIRED (ADR-0049) —`. All four now read alike. Everything after the dash is unchanged. No sha enters runtime text. - **Q2, the CEL advisory: A.** The pointer drop in `rowCanonAdvisory` stands, as shipped in round 1. - **Folded (triage item 3):** the bare PR numbers objectstack-ai#5505 and objectstack-ai#5758, see **Mapping** and **Special cases** 4 and 2. - **Review `5861306588`, taken in full:** the objectstack-ai#5738 stand-down 3 sites name the card by role behind the sha (**Special cases** 2); the runtime-strings changeset's second sentence no longer says every pointer is dropped; and, the optional nit, the sweep changeset names the role-named case. - **`main`:** `main` (`fab627ff9`) was merged in during round 1 by a merge commit (`2cb9b253f`), no rebase and no force-push. The branch is 0 commits behind it, so round 2 merged nothing. Every reading below is on the head `dd37e35d2`. ## Premise, re-measured - REST `GET /repos/objectstack-ai/objectui/issues/N` for each of the 32: all 32 answer 404, and a second read of each answers 404 again (32 of 32). `GET .../pulls/N` answers 404 for all 32 too. Lit controls: objectui#10533 and objectui#7714 answer 200. No number was dropped from the batch. - The two folded bare PR numbers, objectstack-ai#5505 and objectstack-ai#5758, answer 404 on both `issues/N` and `pulls/N`. - The same 32 in objectstack all answer 200. Their subjects are unrelated to the objectui sentences (for example objectstack#5425 is the U+0000 finding about `useDatasetFields.ts`, objectstack#5418 the language-menu card). The only objectstack-qualified sites these numbers have in the in-scope classes already spell `objectstack#` (`objectstack#5425` in `useDatasetFields.ts`, `objectstack#5418` twice in `i18n`'s `provider.tsx`, and `objectstack#5505` twice in `components`): live sister citations, untouched. Every other site names an objectui card, confirmed by its landing commit below, so no site is re-qualified. - Every edited changeset is pending: it is present in `.changeset/` on `main`. - Branch point: `a60539b07`. Not a shallow checkout. ## Census (the enumeration pin for this batch) The instrument PR objectui#10854 printed, with this batch's 32 numbers and the two folded ones substituted (REF = a commit): ``` git grep -nE '(objectui#|#|issues/)(3499|3559|4784|5197|5221|5286|5309|5399|5401|5413|5414|5416|5417|5418|5425|5505|5518|5533|5709|5738|5741|5758|5852|5859|6296|6464|6661|6740|6757|6854|6859|6864|6896|6951)([^0-9]|$)' REF -- '.changeset/*.md' 'packages/*/src/**' ':!**/__tests__/**' ':!**/*.test.*' ':!**/*.spec.*' ':!**/test/**' ':!**/tests/**' | grep -v 'objectstack#' | wc -l ``` - REF = `a60539b07` (branch point): **217** lines (216 for the 32 alone: 56 changeset lines in 47 files and 160 src-nontest lines in 77 files; the folded objectstack-ai#5758 adds one line, and objectstack-ai#5505 sits on two lines objectstack-ai#5401 already counts). REF = `fab627ff9` (current `main`): 217. - REF = `dd37e35d2` (this head, `main` merged in): **0**. - This head merged with a fresh `main` (`fab627ff9`, `git merge-tree --write-tree`, clean): **0**. - The instrument's blind spot, measured: its `grep -v 'objectstack#'` drops a whole line that ALSO names an objectstack number. One in-scope line was hidden that way, `ActionRunner`'s `onSuccess` block ("objectui#5221, the console half of objectstack#9566/objectstack-ai#9474"); it is re-pointed here too. Without the filter the instrument reads 5 at this head, all live `objectstack#` lines (the three above and `objectstack#5505` twice). - Lit control, the same printed instrument over live objectui#7714 at this head: 17 lines. Hex-colour false positives (a number followed by a hex letter) at the branch point: 0. - Out of scope, as it stands (the card's instrument with the 34 numbers, unfiltered, whole tree at this head): 283 test lines in 121 files, 4 scripts lines in 2 files, 0 `.github`, 0 governed, and 24 other lines in 20 files (published `CHANGELOG.md` history, `content/docs`, two package READMEs, and `apps/console`; see **Acceptance notes** 3). The test count includes the `@ts-expect-error` comments named in **Acceptance notes** 5. ## Citation form - The 9-character backticked sha of the commit on `main` that landed the change the sentence rests on, as in PRs objectui#10707 / objectstack-ai#10766 / objectstack-ai#10797 / objectstack-ai#10854. All 32 distinct shas below (the two folded numbers reuse two of them) are ancestors of `main` (`git merge-base --is-ancestor`, exit 0 each; control leg: the head of PR objectui#10714 answers exit 1, and a known ancestor `5f789538d` answers exit 0 in the same checkout), and `git rev-parse --short=9` returns the same 9 characters for each. - A changeset's pointer to its OWN card is dropped, not replaced: `@changesets/changelog-git` prefixes each released entry with the hash of the commit that added the file, which is that landing. Where dropping the pointer left a dangling word, the clause was minimally repaired (listed in **Special cases**). - Where the sentence cites a RULING and no single commit is the ruling, the ruling is cited by its date: "the 2026-08-23 ruling" (the dashboard widget-options ruling, option B, recorded in `8d58f46b4`'s message), "the maintainer ruling of 2026-08-31" (the chart `categories` ruling, recorded in `b0d308da9`'s). - Runtime text carries no sha. Inside a zod `.describe()` string and in the author-facing CEL advisory the dead pointer is dropped (amendment `5860244997`, Q1 = A; ruling `5861129870`, Q2 = A). A tombstone guidance string keeps its `RETIRED (REF) —` shape with `ADR-0049` as the reference (ruling `5861129870`, Q1, as amended by `5861311219`). - Where nothing answers, the pointer is dropped and the sentence names the card by role (objectstack-ai#5518 only). ## Mapping (number to resolution) Lines and files are the branch-point census for that number. "Method" is how the landing was found. | dead number | resolution | method | lines / files | evidence | |:--|:--|:--|:--|:--| | objectstack-ai#3499 | `48132f7e6` | `git log --grep` | 1 / 1 | the rc.5 bump; its message lists "`HttpMethodSchema` -> spec's `HttpMethodSubsetSchema` (objectstack#5832, objectui#3499)" | | objectstack-ai#3559 | `fbc23e094` | `git log --grep` | 7 / 3 | "keep a field's own option keys when an action param inherits them (objectstack-ai#3559)"; it added `ActionParamOption` and the `normaliseOptions` preservation | | objectstack-ai#4784 | `833c90047` | `git log --grep` | 1 / 1 | "a 400 FLOW_FAILED or 404 on the flow route is terminal, not retryable"; its body names objectstack-ai#4784 as the card it settles | | objectstack-ai#5197 | `9c60144b5` | `git log --grep` | 4 / 3 | "retire the unreachable id-keyed nav label resolvers (objectstack-ai#5197)" | | objectstack-ai#5221 | `053fdc8f9` | `git log --grep` | 4 / 3 | "read ActionSchema.onSuccess for post-success navigation", "Part of objectstack-ai#5221"; it added `5221-onsuccess-navigation.md` and the console `openIn: 'self'` half | | objectstack-ai#5286 | `38ba3ddf3` | `git log --grep` | 1 / 1 | "API Discovery Storage group reads the canonical `storage` slot first (objectstack-ai#5286)": the alias table the changeset's sentence describes | | objectstack-ai#5309 | `c7a74c80d` | `git log -G` (the only commit adding the citation) | 3 / 2 | "approver membership-tier picker reads the server-published enum; delegated_admin stops rendering (invalid)" | | objectstack-ai#5399 | `5a07e67d9` | `git log --grep` + changeset's adding commit | 2 / 2 | "stop the sparse-predicate warning blaming `hidden: true` (objectstack-ai#5399)" | | objectstack-ai#5401 | `c86185eb5` | `git log --grep` | 3 / 3 | the PR objectstack-ai#5505 squash ("Bind `record` into node-level `visibleWhen`"); its body "flip[s] the objectstack-ai#5401 defect pins" and implements the live successor objectui#5454 | | objectstack-ai#5413 | `688cb93ad` | `git log --grep` | 1 / 1 | "resolve four react-pages.md contradictions toward the framework's sources (objectstack-ai#5413)" | | objectstack-ai#5414 | `77f846a8b` | changeset's adding commit | 11 / 5 | "name the pending approver, not a truncated raw id"; its body names objectstack-ai#5414 as the card it settles and states the confirmed-empty-seat surfacing | | objectstack-ai#5416 | `add10d8f9` | `git log --grep` + changeset's adding commit | 9 / 5 | "Studio metadata forms: no errors before input, translated help text, and a publish button clear of the toast" | | objectstack-ai#5417 | `c40f3b8ca` | `git log --grep` + changeset's adding commit | 4 / 3 | "surface a screen flow's resume result, on both outcomes (objectstack-ai#5417)" | | objectstack-ai#5418 | `7a90afdf9` | changeset's adding commit + `git log -G` | 20 / 16 | "Studio's 新建对象 asks for the record-sharing baseline, and an unauthored one is reported before Publish instead of by it"; it added the ten locale keys and `securityPostureLint.ts` | | objectstack-ai#5425 | `56f4e34c0` | `git log --grep` + changeset's adding commit | 5 / 4 | "one header spelling across the table widget family", "Part of objectstack-ai#5425" | | objectstack-ai#5505 (bare PR number, folded) | `c86185eb5` | the PR's own squash (subject ends "(objectstack-ai#5505)") | 2 / 2 | sits beside `c86185eb5` already, so the pair collapses to the sha. See **Special cases** 4 | | objectstack-ai#5518 | nothing answers | `git log --grep`, `git log -S` on the fallback read | 1 / 1 | the `node.objectName ?? node.object` fallback it asks about is still on `main`; no commit lands it. See **Special cases** 1 | | objectstack-ai#5533 | `2573ff434` | `git log --grep` + changeset's adding commit | 12 / 6 | "Marketplace package detail page states the marketplace is off, instead of red-erroring (objectstack-ai#5533)" | | objectstack-ai#5709 | `8d58f46b4`; "the 2026-08-23 ruling" | `git log --grep` + changeset's adding commit | 8 / 6 | "warn on dashboard widget options keys no renderer consumes (objectstack-ai#5709)"; its body records "Maintainer ruling 2026-08-23 (option B)" | | objectstack-ai#5738 | stand-down 3: the card named by role, behind `702c48a62`; the recipe: `702c48a62` | `git log --grep` | 4 / 3 | `702c48a62` ("write the requiredWhen example in the row-predicate canon (objectstack-ai#5738)") is the Phase-0 corpus-sweep landing and carries the `detectNonCanonicalRowSpelling` recipe, but not the stand-down 3 finding, which was recorded only on the dead card. See **Special cases** 2 | | objectstack-ai#5741 | `83fe6e741` | `git log --grep` + changeset's adding commit | 25 / 13 | "row predicates on runtime record surfaces bind record.* only (objectui#5741)"; "executed as ruled on objectui#5741 (2026-09-02, amended 2026-09-05)" | | objectstack-ai#5758 (bare PR number, folded) | `702c48a62` | the PR's own squash (subject ends "(objectstack-ai#5758)") | 1 / 1 | "PR objectstack-ai#5758's recipe" beside `702c48a62` collapses to the sha. See **Special cases** 2 | | objectstack-ai#5852 | `e7957ab87`; runtime text `RETIRED (ADR-0049) —` | `git log --grep` + changeset's adding commit | 5 / 4 | "retire the designer-surface dashboard aria pair (objectstack-ai#5852)"; it wrote the hand-spelled `z.never({ error })` tombstone | | objectstack-ai#5859 | `41df89320` | changeset's adding commit | 1 / 1 | "retire the orphaned ObjectTrigger and ObjectRelationship exports"; own-card pointer only | | objectstack-ai#6296 | `88b15fddc` | `git log --grep` + changeset's adding commit | 8 / 3 | "caller-supplied subject vocabulary for ConditionBuilder", "Part of objectstack-ai#6296"; it added `subjects` and the per-row quote character | | objectstack-ai#6464 | `830ed5803` | changeset's adding commit | 8 / 6 | "offer approval recall to the submitter only" | | objectstack-ai#6661 | `969ba84f4` | changeset's adding commit | 5 / 5 | "console renderers for `app:launcher` and `nav:menu`" | | objectstack-ai#6740 | `7c9b044f4` | changeset's adding commit | 5 / 5 | "flex declares the containment it renders" | | objectstack-ai#6757 | `f99932a42` | `git log --grep` + changeset's adding commit | 11 / 10 | "render `global:search` and `global:notifications` instead of the placeholder"; its body names objectstack-ai#6757 as the card it settles | | objectstack-ai#6854 | `adb2a86db` | changeset's adding commit | 4 / 3 | "render AppAction.items from its declared type, without the two `as any` reads"; it added the pin `LayoutRenderer.appActionItems-6854.test.tsx` and ran the app-document census the Chinese changeset refers to | | objectstack-ai#6859 | `64d937c53` | `git log --grep` + changeset's adding commit | 5 / 2 | "correct the injected-editor commit justification, and pin what actually happens (objectstack-ai#6859)" | | objectstack-ai#6864 | `503cd8b89` | changeset's adding commit | 5 / 4 | "aggregate()'s spec-shape branch refuses the analytics branch's `filter` / `field` / `function`" | | objectstack-ai#6896 | `b0d308da9`; "the maintainer ruling of 2026-08-31"; runtime text `RETIRED (ADR-0049) —` | `git log --grep` + changeset's adding commit | 18 / 10 | "retire ChartDataSeries.data, correct categories' prose (objectstack-ai#6896)" | | objectstack-ai#6951, ruling A1 (`TextSchema.value`) | `5ad86ddee`; runtime text `RETIRED (ADR-0049) —` | `git log --grep` + changeset's adding commit | part of 16 / 7 | "retire TextSchema.value as an ADR-0049 tombstone (objectui#6951 A1 / objectui#7016)" | | objectstack-ai#6951, ruling B1 (`TreeViewSchema.data`) | `16a725f96`; runtime text `RETIRED (ADR-0049) —` | `git log --grep` + changeset's adding commit | part of 16 / 7 | "retire TreeViewSchema.data as an ADR-0049 tombstone (objectui#6951 B1)" | ## Special cases (the judgement calls) 1. **objectstack-ai#5518, `StudioDesignSurface`'s nav inspector.** "is objectui#5518, deliberately left out of objectstack-ai#4881's scope" becomes "is a follow-up card's question, deliberately left out of objectstack-ai#4881's scope". Nothing lands it (the fallback read is still there) and no successor is recorded in history, so the card is named by role. 2. **objectstack-ai#5738 "stand-down 3", and objectstack-ai#5758.** The finding (RLS and flow conditions are not row surfaces) was recorded on the dead Phase-0 corpus-sweep card, not in a commit. `702c48a62` is that sweep's landing and the squash of PR objectstack-ai#5758, but it is a one-line `plugin-form/README.md` edit that says nothing about a stand-down, so it cannot carry the finding (review `5861306588`). The card is therefore named by role, with the sha only to locate it: "(objectui#5738 stand-down 3)" becomes "(stand-down 3 on the corpus-sweep card behind `702c48a62`)" in the `conditionScope.ts` file docblock and in `7727-conditional-formatting-record-scope.md`, and the `sharing_rule` doc of `CONDITION_SCOPE_BY_METADATA_TYPE` reads "a stand-down 3 surface of the corpus-sweep card behind `702c48a62`". `rowPredicateCanon.ts` is different: "(the objectui#5738 corpus sweep, PR objectstack-ai#5758's recipe)" becomes "(the `702c48a62` corpus sweep's recipe)", and that commit's message does carry the recipe (the `detectNonCanonicalRowSpelling` oracle); the review found it correct. 3. **objectstack-ai#5221, `consoleServerAction.ts`.** "precedence — objectui#5221 escalates it" becomes "precedence — the card behind `053fdc8f9` escalates it": the escalation lived on the card, and no later ruling on that precedence is in history. 4. **objectstack-ai#5401 and objectstack-ai#5505.** In `visibilityDiagnostic.ts`, "(objectui#5401 → objectstack-ai#5454)" becomes "(objectui#5454)": the dead predecessor goes, the live successor the sentence already named stays. In `data-table.tsx` and `5926-empty-action-visible-when.md`, "objectui#5401 / objectstack-ai#5505 closed for `record:alert`" becomes "`c86185eb5` closed for `record:alert`": `c86185eb5` is the squash of PR objectstack-ai#5505, so the card / PR pair is one landing. 5. **"that card" after a re-point.** Where the next words leaned on the dead card, they were repaired minimally: "on the flag that card was not about" becomes "that change was not about" (`MarketplacePackagePage.tsx`, `gate-listlocalinstalls-marketplace-5620.md`); "The card's complaint was" becomes "The complaint it answered was" (`StudioDesignSurface.tsx`); "is that card's to declare, not this one's to guess" becomes ", the caller's to declare, not this list's to guess" (`ConditionBuilder.tsx`'s `REFERENCE_ROOTS`); "belongs to objectui#6296" becomes ", which `88b15fddc` added" (`6293-conditionbuilder-reference-value.md`); "the unstaffed state objectui#5414 asks to surface" becomes "the unstaffed state `77f846a8b` surfaces"; "is not what objectui#5414 reports" becomes "is not what `77f846a8b` fixes". 6. **Rulings by date.** "(objectui#5709 ruling)" becomes "(maintainer ruling 2026-08-23)" in the objectstack-ai#5709 changeset (own card) and "(the 2026-08-23 ruling; ...)" in `validate.ts`; "whose objectui#5709 ruling states the constraint" becomes "whose 2026-08-23 ruling states" in `kanban-quick-add.ts`; "ruled LIVE by objectui#6896 (maintainer ruling 2026-08-31, prose follows machine)" becomes "ruled LIVE by the maintainer ruling of 2026-08-31 (prose follows machine)" in `ChartRenderer.tsx`, and `8650-chart-foreign-dialect-retired.md`'s "ruled live by objectui#6896" becomes "ruled live by the maintainer ruling of 2026-08-31". 7. **"Phase 2" wording.** "the warning objectui#5741 deleted" becomes "the warning Phase 2 (`83fe6e741`) deleted" in `celAuthoring.ts`, so the next sentence's "That ruling" keeps its antecedent; "objectui#5741 Phase 2 retired" becomes "Phase 2 (`83fe6e741`) retired" in `ConditionBuilder.tsx` and `8167-conditionbuilder-mount-scope.md`; `layout.ts`'s "objectui#6951 (maintainer ruling A1, 2026-09-04) decided it" becomes "maintainer ruling A1 (2026-09-04, `5ad86ddee`) decided it". 8. **Own-card pointers that needed a word.** `dashboard-table-header-one-spelling-5425.md`: "the defect class objectui#5425 rules out" becomes "the defect class this change rules out". `6757-global-search-notifications-renderers.md` and the two objectstack-ai#6951 changesets: the parenthesis opened on its own card, so the line break moved with it ("page blocks.", "is RETIRED" then "(maintainer ruling ...)"). `6854-layout-renderer-retired-onclick.md`: "(objectui#6854, maintainer ruling ...)" becomes "(the maintainer ruling ...)". 9. **The runtime strings.** Only the listed text moves in each (RECORD below stands for the interpolated canonical root). | file | member | before | after | |:--|:--|:--|:--| | `types/src/zod/complex.zod.ts` | `DashboardConfigSchema.aria`, `error` | "RETIRED (objectui#5852) — `aria` is no longer part of DashboardConfig; ..." | "RETIRED (ADR-0049) — `aria` is no longer part of DashboardConfig; ..." | | `types/src/zod/complex.zod.ts` | `DashboardConfigSchema.aria`, `.describe()` | "RETIRED (objectui#5852) — the `{ label, description }` spellings ..." | "RETIRED (ADR-0049) — the `{ label, description }` spellings ..." | | `types/src/zod/data-display.zod.ts` | `TreeViewSchema.data` (tombstone) | "RETIRED (objectui#6951) — `data` is no longer part of TreeViewSchema; ..." | "RETIRED (ADR-0049) — `data` is no longer part of TreeViewSchema; ..." | | `types/src/zod/data-display.zod.ts` | `ChartDataSeriesSchema.data` (tombstone) | "RETIRED (objectui#6896) — `ChartDataSeries.data` was never read: ..." | "RETIRED (ADR-0049) — `ChartDataSeries.data` was never read: ..." | | `types/src/zod/layout.zod.ts` | `TextSchema.value` (tombstone) | "RETIRED (objectui#6951) — `value` is no longer part of TextSchema; ..." | "RETIRED (ADR-0049) — `value` is no longer part of TextSchema; ..." | | `types/src/zod/data-display.zod.ts` | `TreeViewSchema.nodes` | "... no presence rule exists — objectui#6951 B1). ... the `data` fallback spelling was retired by objectui#6951 (the registration's ..." | "... no presence rule exists). ... the `data` fallback spelling was retired (the registration's ..." | | `types/src/zod/layout.zod.ts` | `TextSchema.content` | "... its `value` fallback spelling was retired by objectui#6951)" | "... its `value` fallback spelling was retired)" | | `app-shell/src/views/metadata-admin/celAuthoring.ts` | the `metadata-layer-root` advisory in `rowCanonAdvisory` | "... binds the record as RECORD and nothing else (objectui#5741). The CEL scope ..." | "... binds the record as RECORD and nothing else. The CEL scope ..." | 10. **What follows the tombstone strings, and nothing else in it.** The literal anchors on the old text in the six pinning tests: `dashboard-config.test.ts` (`/RETIRED \(objectui#5852\)/` becomes `/^RETIRED \(ADR-0049\) — /`; the "delete the key" remedy anchor stays), `tree-view-data-retired-6951.test.ts` and `text-value-retired-6951.test.ts` (the full `GUIDANCE` literal's opening and the `describeOf` anchor; `PRESCRIPTIVE` stays), `chart-inline-data-retired.test.ts` (three anchors; the `xAxisKey` and chart-level `data` remedy anchors stay), `chart-data-model-7113.test.ts` and `chart-series-keys-7546.test.ts` (one anchor each). The two changeset quotes (`6951-text-value-retired.md`, `6951-tree-view-data-retired.md`, frontmatter byte-identical) and the two `content/docs` quotes (`text.mdx`, `tree-view.mdx`) open `RETIRED (ADR-0049) —`. Per the ruling these follow the changed string; they do not widen the card's classes. No test, doc or changeset quotes either `aria` string (whole-tree search after the amendment: the source line is the only hit). ## Held **By the serial rule: nothing.** The open-PR list was read at the start (11 open) and re-read for each round; at round 2 there are 9 open besides this one and the release PR: objectui#10873, objectstack-ai#10871, objectstack-ai#10870, objectstack-ai#10852, objectstack-ai#10821, objectstack-ai#10780, objectstack-ai#10777, objectstack-ai#10714 and objectstack-ai#10278. In round 1, two of them touched files this PR edits: objectui#10821 (`types/src/objectql.ts`, `types/src/zod/objectql.zod.ts`) and objectui#10714 (`types/src/data-display.ts`, `types/src/layout.ts`, `types/src/zod/data-display.zod.ts`, `types/src/zod/layout.zod.ts`). Each one's hunks (3 lines of context) were mapped onto the head through a line alignment of the PR's merge-base file: **none of the 22 lines this PR changes in those files lies inside, or beside, any hunk.** objectui#10871 (new since) touches `celAuthoring.ts` and `metadata-admin/i18n.ts` in disjoint hunks (review `5861306588`), and no open PR touches a file round 2 edits. Trial merges of each open PR head with this head (`git merge-tree --write-tree`): clean for objectstack-ai#10873, objectstack-ai#10871, objectstack-ai#10870, objectstack-ai#10852, objectstack-ai#10780, objectstack-ai#10777 and objectstack-ai#10714; objectstack-ai#10821 (`24bcb0035`) and objectstack-ai#10278 (`eab4c8e52`) conflict, but each conflicts identically against `main` alone, so the conflicts are not this PR's. PR objectstack-ai#5400 (Version Packages) regenerates and is not a hold. ## Changesets - `.changeset/10803-dead-citation-sweep-third-batch.md`, EMPTY frontmatter: the comment-only edits in 12 released packages; no published behaviour changes through them. Its list of citation forms now ends "or a live successor, and where nothing answers they name the card by role" (the review's optional nit), and it points at the second file for the runtime text. - `.changeset/10803-third-batch-runtime-strings.md`, `'@object-ui/types': patch` and `'@object-ui/app-shell': patch`. Its second sentence now reads "so no dead pointer becomes a commit: tombstones cite `ADR-0049` in its place, and every other pointer is simply dropped" (review `5861306588` fix 2, in the amendment's all-four wording). It names the four tombstones, all now opening `RETIRED (ADR-0049) —` (`TreeViewSchema.data`, `TextSchema.value`, `ChartDataSeriesSchema.data`, and `DashboardConfigSchema.aria`'s error and describe text), with no process clause about a TypeScript twin; then the two describe strings and the advisory. Nothing after a tombstone's dash moves, and no key, path, issue code, accept set, refusal or severity moves. ## Proof of prose-only (C4), against `main` `fab627ff9` - **Source.** Each of the 77 touched non-test `.ts` / `.tsx` files was parsed at `fab627ff9` (the `main` merged in, so the diff is exactly this PR's) and at this head with TypeScript 6.0.3's `createSourceFile` and re-printed by `createPrinter({ removeComments: true })`: 73 of 77 prints are identical, and the other 4 (`celAuthoring.ts`, `complex.zod.ts`, `data-display.zod.ts`, `layout.zod.ts`) are equal after exactly the 9 listed string substitutions are applied to the `main` print (each matched once): the 4 tombstone strings in 5 literals, the 3 describe-string deletions and the advisory's. 0 parse diagnostics. Lit controls on the same instrument: dropping "(ADR-0049)" from the `TextSchema.value` string moves the print; re-spacing a comment does not. - **Changesets.** The frontmatter block of every one of the 47 edited changesets is byte-identical at `fab627ff9` and this head (47 of 47); the overwrite gate below agrees. - **Scope of the diff against `main`:** 134 files, +287 / −237: 47 edited and 2 new changesets, 77 non-test source files, the 6 pinning tests and the 2 `content/docs` pages. ## Gates, on this head `dd37e35d2` Each line is the gate's own verdict and exit code, captured by redirect-then-`$?`. - `node scripts/check-changeset-presence.mjs`, exit 0: "83 source file(s) of 12 released package(s) changed, and this change declares 2 changeset(s): .changeset/10803-dead-citation-sweep-third-batch.md, .changeset/10803-third-batch-runtime-strings.md." (83 = the 77 sources and the 6 tests under `packages/types/src`). - `pnpm changeset:check`, exit 0: "All workspace packages are in the changeset fixed group." / "No changeset declares a `major` bump." - `node scripts/check-changeset-overwrite.mjs` (report-only), exit 0: "2 changeset(s) added, 47 modified, 0 deleted"; `declared at base` equals `declares now` for 47 of 47. - `pnpm check:changeset-claims` (report-only), exit 0: born-false "Every one of those 9 address(es) either names the tree it was read from, or points at a line this change does not move"; self-contradiction "Every package declared across those 45 body(ies) is either not negated ..."; and the standing notice "92 pending changeset(s) describe a file this change touches". Read against the diff: a pending changeset quoting a replaced pointer would itself carry the dead number and so sit in the census; the only pending quotes of the four tombstone strings are the two edited here; and none of the words repaired beyond a pointer (**Special cases** 1, 3 and 5) occurs in any pending changeset. - `pnpm check:control-bytes`, exit 0: "check-control-bytes: OK (scanned 9113 tracked text file(s); skipped 85 binary)." Self-scan of the 134 changed files for C0 / DEL bytes: 0. - Also run: `pnpm check:new-line-citations`, "VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0"; governed-surface predicate over the 134 paths, exit 0, "NOT GOVERNED — 134 path(s) checked against 5 governed surface(s); none matched." (lit control `AGENTS.md`: exit 3). **Tests**, through the shared verify lock (`VERDICT command-exit 0`). Round 2, on this head: the six pinning files (`dashboard-config`, `tree-view-data-retired-6951`, `text-value-retired-6951`, `chart-inline-data-retired`, `chart-data-model-7113`, `chart-series-keys-7546`) and `tombstone-discriminator-agreement-9684`: `Test Files 7 passed (7)`, `Tests 144 passed (144)`. Round 1, on `e4bce25b8` (round 2 changed no other tested string): those seven plus `tree-view-data-optional-6939`, `undeclared-but-consumed-keys-6150`, `zod-mirror-parity`, `layout-default-jsdoc-7361` in `packages/types`, and `celAuthoring.fieldRuleVerdict-9318`, `recordScopeDataRoot-8166`, `ConditionalFormattingEditor` in `packages/app-shell`: `Test Files 14 passed (14)`, `Tests 393 passed (393)`. **Whole-tree search for other verbatim quotes of the four old strings** (tests, docs, examples, skills, apps): every hit is one of the source strings, the six anchors, the two changeset quotes or the two docs quotes, all updated. Remaining mentions of the old prefix are six `@ts-expect-error` comments in `text-value-retired-6951.test.ts` and `tree-view-data-retired-6951.test.ts` that describe the TypeScript face, not the runtime string; left as they are (see **Acceptance notes** 5). **Declared narrowing (per the dispatch: the named checks, not wider sweeps).** NOT MEASURED locally: the full suites and type-check of the 12 touched packages, and eslint. Reason: the comment-stripped syntax tree of 73 of the 77 touched source files is identical to `main` and the other 4 differ only by the listed string-literal edits; every test that quotes a changed string was found by search and run above. CI runs the full farm. ## Acceptance notes 1. **The remainder rides this card, unchanged (seat amendment `5860244997`, Q2 = A).** Of the 115 numbers PR objectui#10854's Acceptance notes item 1 lists, this PR carries the first 30 in ascending order plus objectstack-ai#6896 and objectstack-ai#6951, which that PR's release named. The other **83** are: objectstack-ai#6872 objectstack-ai#6879 objectstack-ai#6882 objectstack-ai#6887 objectstack-ai#6888 objectstack-ai#6889 objectstack-ai#6892 objectstack-ai#6905 objectstack-ai#6907 objectstack-ai#6921 objectstack-ai#6923 objectstack-ai#6924 objectstack-ai#6931 objectstack-ai#6940 objectstack-ai#6942 objectstack-ai#6958 objectstack-ai#6959 objectstack-ai#6962 objectstack-ai#6965 objectstack-ai#7004 objectstack-ai#7008 objectstack-ai#7023 objectstack-ai#7025 objectstack-ai#7036 objectstack-ai#7068 objectstack-ai#7069 objectstack-ai#7077 objectstack-ai#7079 objectstack-ai#7087 objectstack-ai#7088 objectstack-ai#7091 objectstack-ai#7097 objectstack-ai#7108 objectstack-ai#7177 objectstack-ai#7612 objectstack-ai#7620 objectstack-ai#7623 objectstack-ai#7658 objectstack-ai#7666 objectstack-ai#7667 objectstack-ai#7669 objectstack-ai#7678 objectstack-ai#7681 objectstack-ai#7682 objectstack-ai#7703 objectstack-ai#7704 objectstack-ai#7708 objectstack-ai#7804 objectstack-ai#7844 objectstack-ai#7853 objectstack-ai#7869 objectstack-ai#7874 objectstack-ai#7877 objectstack-ai#7926 objectstack-ai#7959 objectstack-ai#7967 objectstack-ai#7979 objectstack-ai#7980 objectstack-ai#8058 objectstack-ai#8060 objectstack-ai#8072 objectstack-ai#8127 objectstack-ai#8137 objectstack-ai#8204 objectstack-ai#8229 objectstack-ai#8248 objectstack-ai#8307 objectstack-ai#8408 objectstack-ai#9231 objectstack-ai#9241 objectstack-ai#9244 objectstack-ai#9365 objectstack-ai#9373 objectstack-ai#9375 objectstack-ai#9542 objectstack-ai#9553 objectstack-ai#9585 objectstack-ai#10117 objectstack-ai#10119 objectstack-ai#10120 objectstack-ai#10129 objectstack-ai#10132 #14026. None of them was touched here. 2. **The census instrument is blind to bare PR numbers, and so is the family list.** PR objectui#10854's census enumerated `objectui#N` and objectui URLs only, so a bare `#N` that answers 404 never entered the 115: this batch found two by reading its own sentences, objectstack-ai#5505 and objectstack-ai#5758, both the PRs whose squashes the sentence already cited, and folded them in (ruling `5861129870`, triage item 3). The printed instrument above counts a bare number only when the batch names it. ⇒ The next batch's census should first enumerate every distinct bare `#N` in the two in-scope classes, read each by REST (`issues/N` and `pulls/N`), and add the 404s to its number list before it counts. Until that is done the family pin is incomplete for bare numbers, and nothing here re-derives how many there are. 3. **Published text outside the two in-scope classes still names some of these numbers**, untouched by scope (another class, which the triage split did not scope here): `apps/console`'s `useApiDiscovery.ts` (non-test source of `@object-ui/console`, bare objectstack-ai#5286, not under `packages/*/src`), the `@object-ui/data-objectstack` README (objectstack-ai#6864) and the `@object-ui/plugin-detail` README (objectstack-ai#6464), `content/docs` (objectstack-ai#6896, and the `text.mdx` / `tree-view.mdx` "Retired" notes that name objectstack-ai#6951; only their verbatim message quotes moved here), and published `CHANGELOG.md` history (never re-addressed). Carrier: none. 4. **Filenames are not citations.** Pending changeset FILENAMES carry several of these numbers; they stay, as in PRs objectui#10707, objectstack-ai#10797 and objectstack-ai#10854. 5. **Test comments left as they are.** `text-value-retired-6951.test.ts` and `tree-view-data-retired-6951.test.ts` each keep three `@ts-expect-error` comments reading "RETIRED (objectui#6951)"; they describe the `?: never` TypeScript face, quote no runtime string, and tests are otherwise out of this card's classes. --- _Generated by [Claude Code](https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN)_ --------- Co-authored-by: Claude <noreply@anthropic.com>
…ts name 30 objectui issues that answer 404 (objectui#10803, batch 4) (objectstack-ai#10875) Part of objectstack-ai#10803 Clause-②: no Dispatched implementation of the `domain:ui` seat 2 claim (comment `5861571015`) on objectui#10803, batch 4, session `https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN`. Citations only: no sentence's claim moves, and every edited pending changeset's frontmatter is byte-identical. The runtime text that moves loses its dead pointer and nothing else: the legacy `ActionSchema` `onSuccess` / `onFailure` tombstone guidance strings open `RETIRED (ADR-0049) —` (ruling `5861129870` as amended by `5861311219`), and two `DataTableSchema` zod `.describe()` strings drop their pointer (amendment `5860244997`, Q1 = A), all in `@object-ui/types`. The one test that pins the tombstone strings verbatim follows them, and nothing else in it moves. **Patch round 1** answers contract review `5861897723` (FAIL on `d21aeb0f6`) under seat ruling `5861900779` (route a: tests that pin changed comment text follow it, anchor only). `Test (shard 6/8)` was red on `layout-default-jsdoc-7361`, whose `TextSchema.variant` pin anchored on `6942`. The round does four things: - Three comment-text anchors follow the re-pointed text: the one in `layout-default-jsdoc-7361` and two in `cellClassNameCensusProse-6921`. - The `MarkdownSchema` docblock stops crediting `8063bcbdc` with retirements it never touched (**Special cases** 9). - The `7004-cli-root-path-line.md` remnant "(the mechanical half)" goes. - `main` (`de1b879a6`) is merged in by a merge commit (`ae0b81089`), with no rebase and no force-push. The round's anchor sweep (**Special cases** 10) shows those three pins are the only anchors on changed text. ## Why `Part of`, not a closing line The card stays open for the other 53 numbers of the family remainder (seat amendment `5860244997`, Q2 = A), listed in **Acceptance notes** 1, and for the bare-number 404s the C0 census below found. ## Premise, re-measured - REST `GET /repos/objectstack-ai/objectui/issues/N` for each of the 30: all 30 answer 404, and a second read of each answers 404 again (30 of 30). `GET .../pulls/N` answers 404 for all 30 too. Lit controls: objectui#10533 and objectui#7714 answer 200. No number was dropped from the batch. - The same 30 in objectstack all answer 200, with subjects unrelated to the objectui sentences (for example objectstack#6882 is an `examples/app-todo` trigger finding, while the objectui sentences are about `DataTableSchema.renderCellEditor`). Two exceptions were read, not guessed: - `objectstack#6888` already appears on 5 in-scope lines (`i18n.ts`, `ActionDefaultInspector.tsx`, `ActionPreview.tsx`, `block-config.ts`, `action-bar.tsx`), each about the `global_nav` retirement, which is objectstack#6888's own subject. They are live sister citations, untouched. - `UnpublishedAppBar.tsx` wrote "framework PR objectstack-ai#6942" bare. objectstack#6942 is the pull request "the ADR-0045 publish gate gets its own machine-managed key — `app.hidden` goes back to meaning navigation", exactly the `_unpublished` / `hidden` split that heading describes. It is re-qualified to `objectstack#6942` (Zone 1 item 5). - Every other site names an objectui card or pull request, confirmed by its landing commit below. - Every edited changeset is pending: it is present in `.changeset/` on `main`. - Branch point: `e32dae160`. `main` was merged in at `de1b879a6` in patch round 1 (merge commit `ae0b81089`). Not a shallow checkout. ## C0: the bare-number census (measurement only; PR objectui#10869 Acceptance note 2) The instrument, over the two in-scope classes at the branch point (a `#` not preceded by a word character, `#`, `&`, `/`, `.` or `-`, so `objectui#N`, `objectstack#N`, `cloud#N`, `hotcrm#N` and every other `word#N` are excluded, as is a `#N` inside a URL): ``` git grep -hoP '(?:^|(?<=[^\w#&/.\-]))#\d+(?![0-9A-Za-z_])' e32dae1 -- '.changeset/*.md' 'packages/*/src/**' ':!**/__tests__/**' ':!**/*.test.*' ':!**/*.spec.*' ':!**/test/**' ':!**/tests/**' | sort -u | wc -l ``` - **1002 distinct bare numbers.** That is over 600, so by the order's budget only the **980** at or below 10900 were read (replace the final `wc -l` with `tr -d '#' | awk '$1+0 <= 10900' | wc -l` to reproduce 980). The 22 above 10900 were NOT read. - Each of the 980 was read once with REST `GET .../issues/N`: **955 answer 200 and 25 answer 404.** Each of the 25 was read a second time and answered 404 again (25 of 25), and `GET .../pulls/N` answers 404 for all 25. - Lit control on the same instrument: objectstack-ai#5026, objectstack-ai#6905 and objectstack-ai#3720 are all in its output at the branch point. At this head none of the eight batch numbers it found bare remains. - The 25, with site counts (lines / files, at the branch point): - **This batch's own numbers (8), all fixed here:** objectstack-ai#6882 (5 / 2), objectstack-ai#6905 (7 / 2), objectstack-ai#6907 (5 / 1), objectstack-ai#6942 (1 / 1, the objectstack pull request above, re-qualified), objectstack-ai#6959 (1 / 1), objectstack-ai#6962 (1 / 1), objectstack-ai#7036 (8 / 1), objectstack-ai#7087 (2 / 2). The printed census below already counts a bare `#N` for these. - **Already on the family list (3), for their own batches:** objectstack-ai#7620 (2 / 2), objectstack-ai#7678 (3 / 3), objectstack-ai#7853 (1 / 1). - **New to the family (11), for later batches:** objectstack-ai#3720 (5 / 3), objectstack-ai#5420 (1 / 1), objectstack-ai#5503 (1 / 1), objectstack-ai#5506 (1 / 1), objectstack-ai#5737 (4 / 4), objectstack-ai#6467 (1 / 1), objectstack-ai#6936 (1 / 1), objectstack-ai#6945 (1 / 1), objectstack-ai#7622 (1 / 1), objectstack-ai#7662 (1 / 1), objectstack-ai#7684 (2 / 2). - **Not citations (3):** `#0` (257 / 187, the `#0` of "AGENTS.md #0.1"), `#000` (2 / 2) and `#000000` (10 / 6), which are CSS colours. - **Folded here: none.** No C0 404 outside this batch's 30 sits in a sentence this batch edits: none of the 11 new numbers, nor any of the other 53 family numbers, occurs in any hunk of this diff (3 lines of context). - The 200 set is not a citation census: many bare numbers are decision-batch, summons or commandment numbers, or React error codes, that happen to name a live issue. ## Census (the enumeration pin for this batch) The instrument PR objectui#10854 printed and PR objectui#10869 reused, with this batch's 30 numbers substituted (REF = a commit or tree): ``` git grep -nE '(objectui#|#|issues/)(6872|6879|6882|6887|6888|6889|6892|6905|6907|6921|6923|6924|6931|6940|6942|6958|6959|6962|6965|7004|7008|7023|7025|7036|7068|7069|7077|7079|7087|7088)([^0-9]|$)' REF -- '.changeset/*.md' 'packages/*/src/**' ':!**/__tests__/**' ':!**/*.test.*' ':!**/*.spec.*' ':!**/test/**' ':!**/tests/**' | grep -v 'objectstack#' | wc -l ``` - REF = `e32dae160` (branch point): **170** lines, 48 changeset lines in 38 files and 122 src lines in 45 files. REF = `de1b879a6` (the `main` merged in): 170. REF = `c6678b1bd` (`main` at the round's final read): 170. - REF = `ae0b81089` (this head, `de1b879a6` merged in): **0**. Round 0's head `d21aeb0f6` also read 0. - This head merged with a fresh `main` (`c6678b1bd`, `git merge-tree --write-tree`, clean, tree `e109a3bd0`): **0**. - **The instrument's blind spot, as batch 3 measured it.** Its `grep -v 'objectstack#'` drops a whole line that also names an objectstack number. Three in-scope lines were hidden that way, each naming objectui#6965 beside objectstack#9343: in `10039-publish-drafts-advisories.md`, `6965-batch-publish-advisories.md` and `render-publish-advisory-findings-5026.md`. They are re-pointed here too, so the batch's true base population is 173 lines (51 changeset lines in 40 files, 122 src lines in 45 files). Without the filter the instrument reads 178 at the branch point and **7** at this head, all live: the five `objectstack#6888` lines, `objectstack#6942` in `UnpublishedAppBar.tsx`, and the same spelling in the new sweep changeset. - Other spellings at this head: a search for the 30 numbers with no `#` finds only filenames (`action-callback-retired-7068.test.ts`, `data-table-declared-keys-6882.test.ts` and the like) and two SVG path coordinates. Hex-colour false positives (a number followed by a hex letter) at the branch point: 0. - Lit control, the same printed instrument over live objectui#7714 at this head: 17 lines. - **Out of scope, as it stands** (the instrument with the 30 numbers, unfiltered, whole tree at this head): 226 test lines in 96 files (`scripts/__tests__` included), 22 scripts lines in 5 files, 0 `.github`, 0 governed, and 18 other lines in 10 files: published `CHANGELOG.md` history, three `content/docs` lines, and four lines of the private `@object-ui/test-support` README. See **Acceptance notes** 3. ## Citation form - The 9-character backticked sha of the commit on `main` that landed the change the sentence rests on, as in PRs objectui#10707 / objectstack-ai#10766 / objectstack-ai#10797 / objectstack-ai#10854 / objectstack-ai#10869. All 24 distinct shas below are ancestors of `main`: `git merge-base --is-ancestor`, exit 0 each. Control leg in the same checkout: the head of PR objectui#10714 (`d2afdb6bf`) answers exit 1, and a known ancestor, `5f789538d`, answers exit 0. `git rev-parse --short=9` returns the same 9 characters for each. - A changeset's pointer to its OWN card is dropped, not replaced: `@changesets/changelog-git` prefixes each released entry with the hash of the commit that added the file, which is that landing. Where dropping the pointer left a dangling word, the clause was minimally repaired (**Special cases** 5). - Where the sentence rests on a RULING, the ruling is cited by its date, next to the sha that carried it out where one exists (**Special cases** 4). - Where a dead card sits beside a live pull request that IS its landing, the dead card is dropped and the live pointer stays (**Special cases** 1), as batch 3 dropped the dead predecessor in "(objectui#5401 → objectstack-ai#5454)". - Where the claim lived only on the dead card (a finding, a triage, a deferral, a quoted ruling), the sha only locates the card: "the card behind SHA" (**Special cases** 3). This is review `5861306588`'s lesson: a sha must carry what the sentence cites it for. - Where nothing answers, the pointer is dropped and the sentence names the card by role (objectstack-ai#7023 only). - Runtime text carries no sha: see **Special cases** 7. ## Mapping (number to resolution) Lines / files are the branch-point census for that number (a line naming two batch numbers counts for each, and the three hidden objectstack-ai#6965 lines are included). "Method" is how the landing was found. The last column is why that commit carries what the sentence cites it for. | dead number | resolution | method | lines / files | why the commit carries it | |:--|:--|:--|:--|:--| | objectstack-ai#6872 | own-card pointer dropped (landing `d9a0490b7`) | changeset's adding commit | 1 / 1 | the only site is the objectstack-ai#6872 changeset's own pointer | | objectstack-ai#6879 | `3619792bf` | changeset's adding commit, `git log --grep` | 1 / 1 | it curates `box` into `PUBLIC_BLOCKS`, the list the comment sits in | | objectstack-ai#6882 | `bf97b98c8` | changeset's adding commit | 20 / 7 | it declares `renderCellEditor` and schema-level `cellClassName` on `DataTableSchema`, adds the `Equal` exact-shape pin, and corrects `cellClassName`'s reach to the three utility cells | | objectstack-ai#6887 | `5c09cca27` | changeset's adding commit | 1 / 1 | it derives metadata-viewer's option shape from the spec's `SelectOption` with the `Omit` the comment names | | objectstack-ai#6888 | `320374d2a` | changeset's adding commit | 9 / 7 | it keys `LocationField`'s residue refusal and the two coordinate nouns into the locale packs | | objectstack-ai#6889 | `f75810e7c` | changeset's adding commit, `git log -S` | 8 / 1 | it parses a dropped-fields entry's `fields` and `object` instead of asserting them, the gate the comments describe | | objectstack-ai#6892 | own-card pointers dropped (landings `8d40c18a7`, `951fa8e0d`) | changesets' adding commits | 2 / 2 | both sites are slice changesets' pointers to their own card | | objectstack-ai#6905 (a pull request) | `85f6a6097` | `git log --grep`: its squash subject ends "(objectstack-ai#6905)" | 8 / 2 | it judges gantt dates by TYPE before `new Date`, the "objectstack-ai#6781 type rule" the sentences name | | objectstack-ai#6907 | `7fc5c3c12` | changeset's adding commit, `git log -S` | 7 / 2 | it spells a refused gantt date by a rule, and its changeset records the measured throwing-getter crash | | objectstack-ai#6921 | `4eb665bcf` | changeset's adding commit, `git log --grep` | 2 / 2 | it pins, in the rendered DOM, which body cells schema-level `cellClassName` reaches | | objectstack-ai#6923 | `d3bf4fa6f`; "the 2026-08-31 ruling" | changeset's adding commit, `git log --grep` | 5 / 4 | it gives the wrapper-key list its build-free JSON home "per the 2026-08-31 ruling on objectui#6923" | | objectstack-ai#6924 | `78e98bf44`; PR objectstack-ai#7024 kept | changeset's adding commit, `git log --grep` | 5 / 3 | it adds the one enum-options walk for the top-level reader family | | objectstack-ai#6931 | `8063bcbdc` | changeset's adding commit, `git log -S` | 8 / 5 | it converts the remaining eleven tombstones, `confirm` and the menu divider `type` included, to `retirementTombstone()`. At the `MarkdownSchema` site, which `8063bcbdc` never touched (`446d93d4e` retired those keys), it is cited only as the commit that made that spelling uniform: see **Special cases** 9 | | objectstack-ai#6940 | pointers dropped (landing `0c386dd7f`) | changeset's adding commit | 2 / 2 | the only sites are its own changeset's pointer and a `.describe()` string | | objectstack-ai#6942 | `57f9b077b`; one site re-qualified to objectstack#6942 | `git log --grep`; REST for the sister PR | 6 / 4 | it makes `ui:text` honour the published `variant` enum, with a node that omits the key left without a typography class | | objectstack-ai#6958 | `6a449fc49` | changeset's adding commit | 6 / 5 | it clears a field its own `visibleWhen` hides | | objectstack-ai#6959 | `c0c436db8` | changeset's adding commit | 2 / 1 | it keeps the find-call gate and adds a second one, and records the trap that a mock call is one resolution ahead of its value | | objectstack-ai#6962 | `7b433197d` | changeset's adding commit | 3 / 2 | it removes `publishDraft`'s envelope unwrap after measuring the route at the producer | | objectstack-ai#6965 | `ce986aafc`; PR objectui#10038 kept at three sites | changeset's adding commit, `git log --grep`; its body names the card it settles | 21 / 9 | it routes "publish whole app" through the advisory seam, adds `publishPackageDrafts`, and writes the "Corrected before release" note | | objectstack-ai#7004 | `85b495795` (root Path line); `a5d55472b` (arm selection) | both changesets' adding commits | 7 / 4 | the first gives a root-level issue a Path line; the second prints the arm the document selected, per the 2026-09-02 ruling | | objectstack-ai#7008 | `f08bcd9af` | changeset's adding commit | 15 / 11 | it makes `FieldEditWidget` deliver the declared NON-DOM block through `toHostProps`, and corrects `RequiredFieldsDialog` | | objectstack-ai#7023 | nothing answers: the card named by role | `git log --grep` finds only `d88e20f55`, the objectstack-ai#4895 retirement it dissolved into | 1 / 1 | see **Special cases** 3 | | objectstack-ai#7025 | own-card pointer dropped (landing `14884620e`) | changeset's adding commit | 1 / 1 | the only site is its own changeset's pointer | | objectstack-ai#7036 | `869b876c8` | `git log -S` on the timeline renderer | 11 / 1 | it scopes the speller's totality claim, and refuses a `catch` because it would substitute `an object` for a failure | | objectstack-ai#7068 | `6bca0e4e8`; runtime text `RETIRED (ADR-0049) —` | changeset's adding commit | 8 / 3 | it retires the callback pair as ADR-0049 tombstones and deletes `ActionCallback` / `ActionCallbackSchema` | | objectstack-ai#7069 | `2760075ff` | changeset's adding commit | 3 / 3 | it adds the fifth parity ledger that watches the mirror-wider-than-declared direction | | objectstack-ai#7077 | own-card pointer dropped (landing `00d3f09c5`) | changeset's adding commit | 1 / 1 | the only site is its own changeset's pointer | | objectstack-ai#7079 | own-card pointer dropped (landing `ab7dc31ce`) | changeset's adding commit | 1 / 1 | the only site is its own changeset's pointer | | objectstack-ai#7087 | `c93b4d5f3` | changeset's adding commit | 8 / 6 | it drops the 18 `disabled?: boolean` narrowings, adds the twin-symmetry pin, and keeps the six independent `boolean` declarations | | objectstack-ai#7088 | `c1fe272ad` | changeset's adding commit | 4 / 3 | it corrects `BaseSchema.hidden`'s JSDoc to the single hide path and records the synonymy | ## Special cases (the judgement calls) 1. **A dead card beside its own live landing.** - "objectui#6965 / PR objectui#10038" (`AiChatPage.tsx`, `PendingDraftsBar.tsx`, `StudioDesignSurface.tsx`) becomes "PR objectui#10038". PR objectui#10038 answers 200 and is the landing of `ce986aafc`, so the dead half goes and the live half stays. - `7025-nonoptional-enum-cast.md`: "the same walk objectui#6924 converged the optional-cast family onto in PR objectstack-ai#7024" becomes "the same walk PR objectstack-ai#7024 converged the optional-cast family onto". PR objectstack-ai#7024 answers 200 and is `78e98bf44`'s pull request. 2. **The sister-repo number.** In `UnpublishedAppBar.tsx`, "(objectstack#4829 A1, framework PR objectstack-ai#6942)" becomes "(objectstack#4829 A1, framework PR objectstack#6942)". See **Premise**. 3. **The card named by role.** - **objectstack-ai#7023**, in `4895-retire-block-schema-family.md`: "and objectui#7023 — the narrower validator-only fix — dissolves into this retirement" becomes "and the separate card for the narrower validator-only fix dissolves into this retirement". That card never landed on its own. - **"The card behind SHA"**, where the sentence rests on something that lived only on the card: - `6755-field-diagnostics-i18n.md`: "objectui#6888 carries it" becomes "The card behind `320374d2a` carries it". Carrying a pending item is the card's act. - `data-objectstack` `index.ts`: "Unlike objectui#6889's exotic case" becomes "Unlike the exotic case on the card behind `f75810e7c`". The exotic case is not in the commit. - `toHostProps.ts`: "the specific mistake objectui#7008's ruling fences off" becomes "the specific mistake the ruling on the card behind `f08bcd9af` fences off". The quoted ruling text is the card's, not the commit's. - `zod-wrapper-keys.ts`: "the wall objectui#6923 was filed to get a ruling on" becomes "the wall the card behind `d3bf4fa6f` was filed to get a ruling on". - `base.zod.ts`: "objectui#7069 called this repo's systematic producer" becomes "the card behind `2760075ff` called this repo's systematic producer". The commit's own diff attributes that phrase to the card. - The timeline renderer names objectstack-ai#7036's deferral, triage and "1 of 6" trade. These become "the file surface the card behind `869b876c8` deferred", "the triage of the card behind `869b876c8`" and "the card behind `869b876c8` was stopped from making". None of the three is in the commit. 4. **Rulings by date.** - `union-arm-diagnostics.ts`: "the 2026-09-02 ruling on objectui#7004 asks for" becomes "the 2026-09-02 ruling `a5d55472b` implements asks for". - `validate.ts`: "The ARM-SELECTION half of objectui#7004 landed on the 2026-09-02 maintainer ruling" becomes "The ARM-SELECTION half (`a5d55472b`) landed on the 2026-09-02 maintainer ruling". - `7201-schema-slot-census-gate.md`: "across objectui#6882, the ruling that expired both holds" becomes "across the 2026-08-30 ruling that expired both holds (`bf97b98c8`)". - `7687-combobox-option-disabled.md`: "by the objectui#7087 twin-symmetry ruling" becomes "by the 2026-09-01 twin-symmetry ruling, `c93b4d5f3`". - `defaults-table-scan.ts`: "the one objectui#6923 already ruled for exactly that wall" becomes "the one the 2026-08-31 ruling (`d3bf4fa6f`) already set for exactly that wall". 5. **Own-card pointers that needed a word.** - `6931-tombstone-guidance-remainder.md` and `6888-location-residue-refusal-keyed.md`: the pointer sat on its own line, so the period moved up with it. - `7087-disabled-twin-symmetry.md`: the parenthesis opened on the dead card, so the line break moved with it. - `7004-cli-root-path-line.md`: "(objectui#7004, mechanical half)" is dropped, so the sentence ends "sits at the document root." (patch round 1 took the review's nit), and "left open on objectui#7004 for a maintainer ruling" becomes "left open for a maintainer ruling". - `shared-zod-wrapper-keys-6923.md`: "objectui#6923: the Zod wrapper-key list" becomes "The Zod wrapper-key list". - `vi-mock-inherit-slice2.md` and `slice3.md`: "(objectui#6892 slice 2)" becomes "(slice 2)", and likewise for slice 3. 6. **The totality sequence in the timeline renderer.** "(objectstack-ai#6759 -> objectstack-ai#6905 -> objectstack-ai#6907 -> objectstack-ai#7027)" becomes "(objectstack-ai#6759 -> `85f6a6097` -> `7fc5c3c12` -> objectstack-ai#7027)", and likewise with "-> objectstack-ai#7036" as `869b876c8`. objectstack-ai#6759 and objectstack-ai#7027 answer 200 and stay. objectstack-ai#6905 was the pull request whose squash is `85f6a6097`. "⚠️ objectui#7036 — READ THE TWO PARAGRAPHS" becomes "⚠️ `869b876c8` — READ…", and the "see the objectui#7036 note below" that points at it follows. 7. **The runtime strings.** Only the listed text moves in each. | file | member | before | after | |:--|:--|:--|:--| | `types/src/zod/crud.zod.ts` | `ActionSchema.onSuccess` (tombstone) | "RETIRED (objectui#7068) — `onSuccess` is no longer part of this legacy ActionSchema; ..." | "RETIRED (ADR-0049) — `onSuccess` is no longer part of this legacy ActionSchema; ..." | | `types/src/zod/crud.zod.ts` | `ActionSchema.onFailure` (tombstone) | "RETIRED (objectui#7068) — `onFailure` is no longer part of this legacy ActionSchema; ..." | "RETIRED (ADR-0049) — `onFailure` is no longer part of this legacy ActionSchema; ..." | | `types/src/zod/data-display.zod.ts` | `DataTableSchema.rowActions` `.describe()` | "... mirrors the boolean the renderer truthiness-tests (objectui#6940)" | "... mirrors the boolean the renderer truthiness-tests" | | `types/src/zod/data-display.zod.ts` | `DataTableSchema.cellClassName` `.describe()` | "... so row density has to be set on both (objectui#6882)" | "... so row density has to be set on both" | **The ADR-0049 condition, measured from the retirement itself** (Zone 1 item 4): - the zod comment above the two keys opens "ADR-0049 RETIREMENT TOMBSTONES"; - its landing commit `6bca0e4e8` writes them as tombstones, not deletions, and adds the pending `action-callback-retired-7068.md`, which says "ADR-0049 enforce-or-remove"; - each string already ends "Retired under ADR-0049 enforce-or-remove". Both open `RETIRED (ADR-0049) —`. Their TypeScript twins in `crud.ts` read "RETIRED (`6bca0e4e8`, ADR-0049 enforce-or-remove)", the batch 3 twin form. 8. **What follows the strings, and nothing else in it.** `action-callback-retired-7068.test.ts` pins both guidance strings as full literals (`ON_SUCCESS_GUIDANCE`, `ON_FAILURE_GUIDANCE`), and their openings follow. Its test names and four `@ts-expect-error` comments still read "RETIRED (objectui#7068)". They describe the `?: never` TypeScript face, quote no runtime string, and are out of the card's classes (**Acceptance notes** 3). No test, doc or changeset quotes either `.describe()` string: a whole-tree search for each old string returns only the source line. - Patch round 1: three pins quoted re-pointed COMMENT text, and they follow it, anchor only (ruling `5861900779`, route a). - `layout-default-jsdoc-7361.test.ts`: `toContain('6942')` becomes `toContain('57f9b077b')` (the `TextSchema.variant` docblock). - `cellClassNameCensusProse-6921.test.ts`: `toMatch(/objectui#6882|objectstack-ai#6882/)` becomes `toMatch(/bf97b98c8/)` (the `cellClassName` census entry). - The same file: `toMatch(/REDUNDANT since objectui#6882/)` becomes a match on "REDUNDANT since `bf97b98c8`" (the holds-member docblock). - Their titles, messages and comments stay as they are. 9. **The `MarkdownSchema` docblock (patch round 1, review `5861897723`).** Round 0 wrote "Both refuse BY NAME through `retirementTombstone()` (`8063bcbdc`), with the remedy in the message". `8063bcbdc` never touched `MarkdownSchema`; `446d93d4e` retired `sanitize` / `components`. So the sha did not carry what it was cited for, the objectstack-ai#5738 class. It now reads "through `retirementTombstone()`, the spelling `8063bcbdc` made uniform, with the remedy in the message". That commit's own subject says the remaining tombstones carry their remediation text. The edit is a comment, and the file's C4 print is unchanged by it. 10. **The anchor sweep that closes the gap (patch round 1).** - **Instrument:** every string, template, numeric and regex literal in all 3814 test and script files under `packages/` and `scripts/`, enumerated with `git ls-tree` at this head and parsed with TypeScript. - **Test applied to each literal:** does its occurrence count DROP between `main` and this head in any of the 90 files this PR changes? Raw text and a comment-flattened form are both checked. - **Specific anchors found** (a batch number, a changed phrase, or a pattern keyed to them), after reading every hit against the file it sits in: - the three pins above; - `tombstone-discriminator-agreement-9684`'s /RETIRED \(objectui#/ note search, which reads only `mobile.ts` and is untouched by this PR. - **Everything else:** generic tokens (whitespace, punctuation, `objectui#` spellings in ledger checks over the tests' own data, digit and letter classes), none of them an assertion over text this PR changed. - **Round 0's quote search** covered runtime strings only. That is the gap this sweep closes. ## Held **By the serial rule: nothing.** Round 0's list: objectui#10873, objectstack-ai#10871, objectstack-ai#10870, objectstack-ai#10852, objectstack-ai#10821, objectstack-ai#10780, objectstack-ai#10777, objectstack-ai#10714, objectstack-ai#10278 and objectstack-ai#5400. Since then objectstack-ai#10873, objectstack-ai#10871, objectstack-ai#10870 and objectstack-ai#10821 have merged. objectstack-ai#10870 touched `base.zod.ts` in a region apart from this PR's line, and the merge with it is clean. - Re-read before the round-1 push: 11 open. Besides this PR they are objectui#10880, objectstack-ai#10879, objectstack-ai#10878, objectstack-ai#10876, objectstack-ai#10852, objectstack-ai#10780, objectstack-ai#10777, objectstack-ai#10714, objectstack-ai#10278 and the release PR objectstack-ai#5400. - Four of them hold files this PR edits: - objectui#10879: `types/src/zod/data-display.zod.ts`; - objectui#10878: `data-objectstack/src/index.ts` and `plugin-grid/src/ObjectGrid.tsx`; - objectui#10714: `types/src/data-display.ts`, `types/src/layout.ts` and `types/src/zod/data-display.zod.ts`; - objectui#10278: `plugin-grid/src/ObjectGrid.tsx`. - Each one's hunks were read against its merge-base, with 3 lines of context. **None of the 29 lines this PR changes in those files appears inside or beside any of their hunks.** - Trial merges of each open PR head with this head (`git merge-tree --write-tree`) are clean for objectstack-ai#10880, objectstack-ai#10879, objectstack-ai#10878, objectstack-ai#10876, objectstack-ai#10852, objectstack-ai#10780, objectstack-ai#10777 and objectstack-ai#10714. - objectstack-ai#10278 (`eab4c8e52`) conflicts in `ObjectGrid.tsx`, but it conflicts identically against `main` alone: one conflict hunk in its own page-size region either way. - PR objectstack-ai#5400 (Version Packages) regenerates and is not a hold. ## Changesets - `.changeset/10803-dead-citation-sweep-fourth-batch.md`, EMPTY frontmatter: the comment-only edits in 12 released packages and the private `@object-ui/test-support`. No published behaviour changes through them. It points at the second file for the runtime text. - `.changeset/10803-fourth-batch-runtime-strings.md`, `'@object-ui/types': patch`: the two tombstones open `RETIRED (ADR-0049) —` with everything after the dash unchanged, and the two describe strings lose their pointer. No key, path, issue code, accept set, refusal or severity moves. ## Proof of prose-only (C4), against the merged `main` `de1b879a6` - **Source.** Each of the 48 touched `.ts` / `.tsx` files was parsed at `de1b879a6` and at this head with TypeScript 6.0.3's `createSourceFile` and re-printed by `createPrinter({ removeComments: true })`. The 48 are the 45 non-test sources and three tests: the one pinning the strings, and the two whose comment-text anchors follow. - 43 of 48 prints are identical. That includes all 45 non-test sources except `crud.zod.ts` and `data-display.zod.ts`, whose `MarkdownSchema` comment edit moves nothing. - The other 5 are equal once exactly the 9 listed substitutions are applied to the `main` print, each matched once: - `crud.zod.ts`: the two tombstone strings; - `data-display.zod.ts`: the two describe-string deletions; - `action-callback-retired-7068.test.ts`: the same two tombstone strings; - `layout-default-jsdoc-7361.test.ts`: the one anchor; - `cellClassNameCensusProse-6921.test.ts`: the two anchors. - 0 parse diagnostics. - Lit controls on the same instrument: dropping "(ADR-0049)" from the `onSuccess` string moves the print; re-spacing the "ADR-0049 RETIREMENT TOMBSTONES" comment does not. - **Changesets.** The frontmatter block of every one of the 40 edited changesets is byte-identical at `de1b879a6` and this head (40 of 40, by md5). The overwrite gate below agrees. - **Scope of the diff against the merged `main`:** 90 files, +227 / −184: 40 edited and 2 new changesets, 45 non-test source files, and 3 tests. ## Gates, on this head `ae0b81089` Each line is the gate's own verdict and exit code, captured by redirect-then-`$?`. - `node scripts/check-changeset-presence.mjs`, exit 0: "44 source file(s) of 12 released package(s) changed, and this change declares 2 changeset(s): .changeset/10803-dead-citation-sweep-fourth-batch.md, .changeset/10803-fourth-batch-runtime-strings.md." (44 = the 41 released sources and the 3 tests under released packages' `src/`; the four `test-support` files sit under a package changesets ignores.) - `pnpm changeset:check`, exit 0: "All workspace packages are in the changeset fixed group." / "No changeset declares a `major` bump." - `node scripts/check-changeset-overwrite.mjs` (report-only), exit 0: "2 changeset(s) added, 40 modified, 0 deleted". `declared at base` equals `declares now` for 40 of 40. - `pnpm check:changeset-claims` (report-only), exit 0: - born-false: "Every one of those 1 address(es) either names the tree it was read from, or points at a line this change does not move"; - self-contradiction: "Every package declared across those 30 body(ies) is either not negated in its own prose, or negated only in an ASPECT of it that may legitimately hold still"; - the standing notice "83 pending changeset(s) describe a file this change touches". - Read against the diff: a pending changeset quoting a replaced pointer would itself carry the dead number and so sit in the census. No pending changeset quotes either tombstone string or either describe string; the one textual hit, "truthiness-tests" in `6940-rowactions-boolean-mirror.md`, is prose, not a quote. - `pnpm check:control-bytes`, exit 0: "check-control-bytes: OK (scanned 9125 tracked text file(s); skipped 85 binary)." - `pnpm check:new-line-citations`, exit 0: "VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0". - Also run: the governed-surface predicate over the 90 paths, exit 0: "NOT GOVERNED — 90 path(s) checked against 5 governed surface(s); none matched." (lit control `AGENTS.md`: exit 3). **Tests**, through the shared verify lock. - **Red, reproduced first.** - `layout-default-jsdoc-7361` on `d21aeb0f6` itself gives `VERDICT command-exit 1`, `Tests 1 failed | 74 passed (75)`: "expected '/**\n * Text variant/style. …' to contain '6942'". - `cellClassNameCensusProse-6921`: its `d21aeb0f6` copy was checked out over this tree and run. `ObjectGrid.tsx` and the census changesets it reads are identical at `d21aeb0f6` and here. Result: `Tests 2 failed | 3 passed (5)`, on `/objectui#6882|objectstack-ai#6882/` and `/REDUNDANT since objectui#6882/`. The file was then restored with `git checkout HEAD --`, checked by blob hash against `HEAD`, and `git diff HEAD` came back empty. - **Green, on this head `ae0b81089`:** `layout-default-jsdoc-7361`, `cellClassNameCensusProse-6921`, `action-callback-retired-7068`, `data-table-declared-keys-6882`, `tombstone-discriminator-agreement-9684` and `zod-mirror-parity` give `Test Files 6 passed (6)`, `Tests 181 passed (181)`. - The run was the last part of the locked batch, so its exit is the one the lock's `VERDICT batch-last-exit 0` reports. **Declared narrowing (per the dispatch: the named checks, not wider sweeps).** NOT MEASURED locally: the full suites and type-check of the 12 touched packages, and eslint. Reason: the comment-stripped syntax tree of 43 of the 48 touched files is identical to `main`, and the other 5 differ only by the listed literal edits. Every test that anchors on a changed string or comment was found by the anchor sweep (**Special cases** 10) and run above. CI runs the full farm. ## Acceptance notes 1. **The remainder rides this card, unchanged (seat amendment `5860244997`, Q2 = A).** Of the 83 numbers PR objectui#10869's Acceptance notes item 1 lists, this PR carries the first 30 in ascending order. The other **53** are: objectstack-ai#7091 objectstack-ai#7097 objectstack-ai#7108 objectstack-ai#7177 objectstack-ai#7612 objectstack-ai#7620 objectstack-ai#7623 objectstack-ai#7658 objectstack-ai#7666 objectstack-ai#7667 objectstack-ai#7669 objectstack-ai#7678 objectstack-ai#7681 objectstack-ai#7682 objectstack-ai#7703 objectstack-ai#7704 objectstack-ai#7708 objectstack-ai#7804 objectstack-ai#7844 objectstack-ai#7853 objectstack-ai#7869 objectstack-ai#7874 objectstack-ai#7877 objectstack-ai#7926 objectstack-ai#7959 objectstack-ai#7967 objectstack-ai#7979 objectstack-ai#7980 objectstack-ai#8058 objectstack-ai#8060 objectstack-ai#8072 objectstack-ai#8127 objectstack-ai#8137 objectstack-ai#8204 objectstack-ai#8229 objectstack-ai#8248 objectstack-ai#8307 objectstack-ai#8408 objectstack-ai#9231 objectstack-ai#9241 objectstack-ai#9244 objectstack-ai#9365 objectstack-ai#9373 objectstack-ai#9375 objectstack-ai#9542 objectstack-ai#9553 objectstack-ai#9585 objectstack-ai#10117 objectstack-ai#10119 objectstack-ai#10120 objectstack-ai#10129 objectstack-ai#10132 #14026. None of them occurs in any hunk of this diff. 2. **The C0 bare-number 404s, for later batches** (sites at `e32dae160`, lines / files): - **New to the family:** objectstack-ai#3720 (5 / 3), objectstack-ai#5420 (1 / 1), objectstack-ai#5503 (1 / 1), objectstack-ai#5506 (1 / 1), objectstack-ai#5737 (4 / 4), objectstack-ai#6467 (1 / 1), objectstack-ai#6936 (1 / 1), objectstack-ai#6945 (1 / 1), objectstack-ai#7622 (1 / 1), objectstack-ai#7662 (1 / 1), objectstack-ai#7684 (2 / 2). - objectstack-ai#5737, objectstack-ai#6945, objectstack-ai#7622, objectstack-ai#7662 and objectstack-ai#7684 are written "PR #N". A later batch can look for each one's squash commit, as batch 3 did for objectstack-ai#5505 and objectstack-ai#5758. - The objectstack-ai#3720 sites are in `ObjectGrid.tsx`, `rowCrudAffordances.ts` and `ListView.tsx`. `ObjectGrid.tsx` is also held by open PR objectui#10278. - **Already on the family list:** objectstack-ai#7620, objectstack-ai#7678 and objectstack-ai#7853. They have bare sites too, which the printed instrument counts. - **Not read:** the 22 distinct bare numbers above 10900 (budget). Nothing here re-derives whether any of them is dead. 3. **Published or shipped text outside the two in-scope classes still names some of these numbers.** It is untouched by scope, as another class the triage split did not scope here: - `content/docs`: `enhanced-actions.mdx` and `schema-overview.md` say the callbacks were "RETIRED (objectui#7068)" in prose, not as verbatim quotes of the runtime string; `plugin-form.mdx` names objectui#6958. - The private `@object-ui/test-support` README names objectui#6923 and objectstack-ai#6924. - Published `CHANGELOG.md` history, which is never re-addressed. It includes a bare "framework PR objectstack-ai#6942" in `@object-ui/app-shell`'s. - In tests: `action-callback-retired-7068.test.ts`'s test names and four `@ts-expect-error` comments reading "RETIRED (objectui#7068)"; `layout-default-jsdoc-7361.test.ts`'s header-table comment naming objectui#6942; and the test names and comments in `cellClassNameCensusProse-6921.test.ts` that name objectstack-ai#6882. Only anchors moved (ruling `5861900779`). - Carrier: none. 4. **Filenames are not citations.** Pending changeset and test FILENAMES carry several of these numbers. They stay, as in PRs objectui#10707, objectstack-ai#10797, objectstack-ai#10854 and objectstack-ai#10869. --- _Generated by [Claude Code](https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN)_ --------- Co-authored-by: Claude <noreply@anthropic.com>
Fixes #10853
Clause-②: no — two readers subscribe to the existing invalidation bus; no declared key, export or accept set moves.
This is the fifth batch of bus readers under decision B on objectui#10519 ("readers first"). After PR objectui#10777 removes
PageView's remount, these two blocks would otherwise keep showing data from before a page action. objectui#10519 remains open.Dispatched by the
domain:uiseat 4 PM (claim comment 5860833997, triage 5860720827). Session:https://claude.ai/code/session_01MCg3z5cGrV51xEddpGcxEY. Inmode:subagentthat id is also this run's. Branchclaude/issue-10853-master-detail-picker-bus-readerswas cut fromorigin/maina7fd877(BASE). Head isa13048c, after one patch round on the contract review ofac526b1(see Patch round below).What changed
Each read now takes a nonce from the data-invalidation bus for the object it queries. This follows the objectui#10623 / objectui#10778 shape: the same bus, the same matcher (
dataChangeMatches), no second channel and no remount.packages/plugin-form/src/MasterDetailForm.tsx, edit mode. Each detail collection'sfindof its child object now re-reads when the bus reports a change to that child object, or'*'. The re-read happens in place, and the rows and the save baseline move together.useDataInvalidationcall per object cannot be made. A localuseObjectsInvalidation(names)subscribes throughsubscribeDataChanges, the listener setuseDataInvalidationitself uses. It tests each change withdataChangeMatchesat object level and keys on the set's content.Clause-②: noholds.ObjectForm(objectui#10572), which is unchanged.packages/components/src/renderers/basic/record-picker.tsx. The option read's effect now namesuseDataInvalidation(object), subscribed only when the adapter reads and the object has resolved. A read of exactly the query whose options are already on screen (same adapter, object, filter, sort and limit) runs in place:setLoading(true), so the control stays enabled and shows no "Loading…";Any other read starts from "Loading…", as before. The
placeholderinput's description now says so ("while it reads a new set of options"). That is a text change only; the input'stypeis unchanged.object-formwithsubformsroutes to the sameMasterDetailForm, so the same reader covers it. This is pinned. The spec refusessubformsonobject-form, so this does not gate (triage note 5)..changeset/10853-master-detail-picker-bus-readers.md:@object-ui/plugin-formpatch and@object-ui/componentspatch..changeset/10778-dashboard-bus-readers.md: one appended dated note in the objectui#10533 form (triage note 4). It says thedrillDown.reportdrawer does re-read since objectui#10814 (PR objectui#10836), and points atdrillDownReport.invalidationRefetch-10814.test.tsx. The single-record drawer half of that sentence still holds. The frontmatter is byte-identical: md5 of lines 1-3 isd527064c725ab089f1c5e8f4c419e8cdbefore and after, andcheck-changeset-overwrite.mjsreports the declared bump unchanged (@object-ui/plugin-dashboard: patch).Unsaved lines (B3): held, then replayed after a save or a revert
This is the objectui#10712 R3 / objectui#10572 rule, applied to each collection separately.
Unsaved means the edit save's row diff (
buildMasterDetailEditBatch) finds something to write to that collection other than the parent link. A user's edit therefore reads as unsaved exactly when the save would send it, and a line changed back to its stored value reads as saved again.sendBatchis unchanged.An open row editor counts as unsaved for its collection (patch round). The editor keeps its draft in its own form, not in the rows, so the rows alone cannot show it.
A held bus re-read is replayed once, when the row editor is closed (Apply or Close) and either:
sendBatchmarks every collection the batch wrote, and the replay runs once the save guard releases.After Apply the applied line is unsaved, so the re-read stays held until that line is saved or changed back.
A line typed while a re-read is in flight is kept, in the grid or in the row editor.
setRowStateupdater.LineItemsPanel, the grid is not disabled during a re-read, and the row editor is never reset, re-keyed or disabled by one. Only a save disables it, as before.A failed re-read keeps the lines on screen and warns. A failed load still leaves the collection empty, as before.
The picker's bound value (B4)
limit.All of this is pinned.
Patch round (contract review of
ac526b1: FAIL)The review (comment 5861421338) found one defect, and it is verified: with the row editor open on a line, a bus event committed fresh row copies under it.
expandedRowthen changed, and the editor's inlineinitialDatareset overwrote the draft.ac526b1with the new pins: the draft read'first (server)'where the user had typed'first (draft)'.'second'), so a later Apply would have mapped onto that row.What changed in the fix:
MasterDetailForm.tsx: theexpandedstate moves above the lines reader. A render-timerowEditorEntryRef(the same pattern asrowStateRef) names the collection the editor is open on, and three places read it:expandedchanges.linesUnsaved's doc, the changeset and this body now claim only what holds about the parent link..changeset/6726-find-envelope-records-arms.md: its row "element:record_pickeroptions" still describes the picker, whose read is stillres?.data ?? (Array.isArray(res) ? res : []). A{ records }answer still reads as no rows, on a first read and on a re-read..changeset/6783-readprops-degenerate-config-bag.md: the picker still reads its bag throughreadProps, which this diff does not touch.Mechanism assumptions, measured
B1 (templates). I read both merged diffs.
LineItemsPanelholds edits and keeps the grid drawn withrefreshing.DatasetWidget/DashboardRenderer, one reader per widget component.I reused the seam. The picker needed the in-place path because its re-read flipped
loading. The master-detail lines needed no refreshing state: at BASE their edit-mode read had no loading branch, so a re-read never blanked them.B2 (sites re-read 0 times at BASE). Confirmed with an uncommitted scratch probe on BASE
a7fd877: the realSchemaRenderer, real registrations, onenotifyDataChanged({ objectName: '*' }), and a bareuseDataInvalidationreader as the lit control. Results, counted as reads on mount → reads after the event:findofpo_line)2 → 2findOne)1 → 21 → 11Mount reads the lines twice because the load effect runs again once the resolved details are set. That is unchanged, and the pins count from rest.
B3 / B4. See the two sections above.
Pins and ablation
MasterDetailForm.busReread-10853.test.tsx(12 tests: 8, plus 4 for the row editor) andrecord-picker.busReread-10853.test.tsx(4 tests) render through the realSchemaRendererand the packages' own registrations. The master-detail pins use the real line-item grid; the picker pins sit in a realPageVariablesProviderwith a variable bound to the picker. A bareuseDataInvalidationreader is the lit control, and reads can be held open to look at the block mid-flight.'*'re-reads once in place: the same input node, no blanking. A save afterwards writes no line, so the baseline moved.update l1 { label, memo }, and the held re-read replays once after the save;l1, not its neighbour;subformsroute re-reads.ee5c87dTests 12 passed (12)157fa2762a/b5217ead2d== BASE; reader hitslinesBusNonces0,invalidationNonce0Tests 10 failed, 2 passed (12). Every red is a read-count miss (expected 2 to be 3,expected "vi.fn()" to be called 2 times, but got 1 times); the 2 green are the two controls. Restored withgit checkout HEAD -- ABSOLUTE_PATH: blobsbc3724ddf8/d11d0e1fcc== HEAD,git diff HEAD0 bytesablation-replace.mjs(objectstackorigin/main):if (unsavedLines(entry)) {→if (false) {, anchor 1 → 0, blobbc3724ddf8→9347b55e8eTests 3 failed, 5 passed (8): exactly the three hold cases ("a bus re-read ran over unsaved lines" ×2, "re-read again over the unsaved line"). Restored by the tool: blob == HEAD,git diff HEADemptyconst inPlace = …signature;→const inPlace = false;, anchor 1 → 0, blobd11d0e1fcc→4fb57ece38Tests 1 failed, 3 passed (4): exactly "the re-read disabled the picker". Restored by the tool: blob == HEAD,git diff HEADemptyMasterDetailForm.tsxchecked out atac526b1under the committed pins atea52c79(trap restore); blobc4a5fdc81c==ac526b1;rowEditorEntryRefhits 0Tests 4 failed, 8 passed (12): all four editor cases, each on the draft (expected 'first (server)' to be 'first (draft)'×3;expected 'second' to be 'first (draft)'). Restored: blobd147657e95== HEAD,git diff HEAD0 bytesa13048c)rowEditorEntryRef.current === entry.id ||→false ||(the hold decision), anchor 1 → 0, blob1a74a580d7→b2dda3c6baTests 3 failed, 9 passed (12): the three editor cases, on "a bus re-read ran under an open row editor". The draft stays intact there because the commit guard still holds. Restored by the toola13048c)1a74a580d7→4fc16f6691Tests 1 failed, 11 passed (12): exactly "the in-flight re-read reset the editor’s draft". Restored: blob == HEAD,git diff HEAD0 bytesTwo ablation attempts in the patch round, reported as they happened:
ea52c79, crashed the worker (Worker exited unexpectedly) instead of failing. At that head the commit guard held by re-asking, and with the hold decision ablated the re-ask looped. The shipped code cannot loop, because both checks read the same ref, buta13048cmakes the guard hold directly so the two checks no longer depend on each other. A5 was then re-run cleanly (above).Tests 12 passed): the updater site alone covers it. That is why A6 mutates both sites.No
dist/preflight applies: each pin imports its package's registration through a relative source path, and both mutated files are reached through it.Gates
Pinned to head
a13048cunless marked.packages/componentsis byte-identical sinceee5c87d:git diff ee5c87d a13048c -- packages/componentsis empty, so its runs atee5c87dstand.turbo run build --concurrency=2 --filter=@object-ui/plugin-form^...(Tasks: 11 successful), thenpnpm --filter @object-ui/plugin-form type-check: script echoed,VERDICT command-exit 0.--listFilescounts the pin intsconfig.test.json: 1.pnpm exec vitest run --maxWorkers=2 packages/plugin-form/ packages/components/src/renderers/basic/__tests__/record-picker.busReread-10853.test.tsx:Test Files 137 passed (137),Tests 1597 passed | 1 skipped (1598),VERDICT command-exit 0.ee5c87d:pnpm --filter @object-ui/components type-check: exit 0.packages/components/in 3 shards, allVERDICT command-exit 0: 108 files / 1039 tests passed; 107 files / 1212 passed + 10 skipped; 106 files passed + 1 skipped / 887 passed + 7 skipped.Tests 1166 passed (1166).a13048c:eslint --format jsonoverMasterDetailForm.tsxand its pin read 2 files: 0 errors / 23 warnings and 0 / 6.MasterDetailForm.tsxis 0 / 23 as atac526b1(BASE 0 / 25); with--no-inline-configit is 0 / 29 (exhaustive-deps6, the file's existing disables).record-picker.tsxis unchanged sinceee5c87d(0 / 10 = BASE).eslint.config.jsis not type-aware, so this diff moves no verdict in an untouched file.a13048c, all exit 0:check:new-line-citations:VERDICT … 0 new citation(s).check:control-bytes: OK. A self-scan of the changed files found no control byte.check:test-path-roots,check:vi-mock-specifiers,check:vi-mock-inherit,check:unreferenced-sources,check:element-data-source-declaration: OK.check:phantom-deps,check:changeset-claims,check:pending-changeset-literals: ✅.scripts/check-changeset-presence.mjs✅,scripts/check-changeset-no-major.mjs✅,scripts/check-changeset-fixed.mjs✅,scripts/check-type-check-coverage.mjs✅.scripts/check-changeset-overwrite.mjs(report-only): 1 added, 1 modified; the 10778 note, case 2.check:sdui-registration-pins. Reason: it exits 2 without a console build. This diff changes no registration and nosideEffectsarray. CI builds the console.Serial
git merge-tree --write-tree HEAData13048cagainst a freshorigin/main(e32dae1, fetched into a private ref, since deleted): clean. No commit on main since BASE touches these three files.PageViewis not touched (PR objectui#10777, seat 2).Acceptance notes
Not changed here. Each was read at source unless it says it was measured.
'*', whichPageViewwill send, does both. This is the same boundaryLineItemsPanelhas.onMutation, so this is not pinned.element:record_picker'semptyTextinput description cites a line address,:213read ata7fd877, for the "No records" default. Ata7fd877that line is inside a comment block, not the default. This is a stale same-file line address in published registry text, outside this card's class, so it is not repaired here. Carrier: none.Generated by Claude Code