Repository navigation
docs(skills,console): record why the seven sectioning tags stay off the curated tier; retract the section row (objectui#8775) - #10852
Merged
Conversation
…he curated tier; retract the section row (objectui#8775) Ruling 5857078807, letter B. The seven HTML sectioning tags stay out of PUBLIC_BLOCKS, and the console ledger now records why, sentence by sentence: zero JSON-surface pull in real apps, html-tier intrinsics that render on kind:'html' pages, the four page:* blocks already carry the landmarks, and curating one would add a near-synonym pair. The ledger const is renamed SECTIONING_TAG_UNRULED -> SECTIONING_TAG_REFUSED, following the aspect-ratio entry's "RULED: refused on stated merits" form. The page-builder guide drops its `section` row, rewrites the box prose for box alone, and points an author who needs a landmark at page:section, page:header, page:footer and page:sidebar. semantic.mdx stops teaching the `body` child-list key that objectui#6771 retired. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN
apps/console/src is released source of @object-ui/console, so the presence gate asks for a declaration; the change is a test-ledger text and two docs pages, so the changeset carries an empty frontmatter. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN
…for all seven Two clauses of the recorded reason overreached. hotcrm authors no box, flex or card, so its lit control is its own layout blocks (grid, page:header, page:card), not box/flex/card. And main, nav and article have no page:* twin, so the near-synonym pair is stated through box, which all seven shadow (a verbatim-className neutral wrapper), with the four page:* twins as the stronger case. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN
Contributor
|
changeset-claim-re-read
|
Contributor
✅ 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
|
Contributor
Author
Contract reviewServed-tier: This is the at-tier record for a Tier H PR ( ① Derived judgmentsDiff. Merge-base Parameter 1: the ledger is true, sentence by sentence.
Parameter 2:
Parameter 3:
Parameter 4: byte-unchanged. Nothing under Changeset. An empty frontmatter is the repo's convention: there are 12 or more precedents on main, including the aspect-ratio twin Remaining JSON uses of Non-blocking.
② Semver levelNone. The changeset has an empty frontmatter and releases no package. ③ Boundary flags
Implemented-by: VERDICT: PASS Generated by Claude Code |
…block adds (objectui#8775 review) Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN
Contributor
✅ 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
|
Contributor
Author
Contract reviewServed-tier: Round 2, an in-seat narrow re-review against the round-1 PASS record ① Derived judgments
② Semver levelNone. There is no change from round 1: the changeset has an empty frontmatter, and Clause-② is no. ③ Boundary flags
Implemented-by: VERDICT: PASS Generated by Claude Code |
This was referenced Sep 27, 2026
hotlong
approved these changes
Sep 28, 2026
hotlong
marked this pull request as ready for review
September 28, 2026 03:39
hotlong
approved these changes
Sep 28, 2026
hotlong
enabled auto-merge
September 28, 2026 03:40
Contributor
✅ 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
|
Contributor
Author
Contract reviewServed-tier: Round 3, adopting the round-2 PASS record ① Derived judgments
② Semver levelNone, unchanged from rounds 1–2: empty changeset frontmatter, Clause-② no. ③ Boundary flags
Implemented-by: VERDICT: PASS |
akarma-synetal
pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Sep 28, 2026
…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>
akarma-synetal
pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Sep 28, 2026
…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>
akarma-synetal
pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Sep 28, 2026
…imports (^17.4.0) (objectstack-ai#10882) Fixes objectstack-ai#10864 Clause-②: no ## What changed - Raised `packages/app-shell/package.json`'s declared `@objectstack/spec` range from `^17.3.0` to `^17.4.0` — the first published spec version that exports the four symbols two shipped app-shell sources import at runtime (`predicateSlotRefusal`, `structuralConditionRefusal` from `@objectstack/spec/automation`; `EVALUATED_EXPRESSION_SOURCE_REQUIRED`, `EvaluatedExpressionSchema` from `@objectstack/spec/shared`), matching the range `@object-ui/types` already declares. - Regenerated `pnpm-lock.yaml` with `pnpm install --lockfile-only` — moves only the app-shell `@objectstack/spec` specifier line. - Added `.changeset/10864-app-shell-spec-floor.md` (`patch`, `@object-ui/app-shell`). - Amended the pending `.changeset/5920-flow-runner-translation-overlay.md` with a dated note: its closing sentence claimed the package "now declares `^17.3.0`", which this change makes false. Frontmatter untouched — only the body gained the note, following the objectui#10533 precedent. - No source files changed, and no revert of anything to lower a floor. ## M1 to M4 - **M1** (reproduce red on `main`): full workspace build (`turbo run build --filter='!@object-ui/site' --concurrency=2`, 43/43 tasks successful), then `pnpm check:spec-floors` exited 1 with exactly 4 `floor-too-low` findings, all in `@object-ui/app-shell`, matching the issue: `predicateSlotRefusal` and `structuralConditionRefusal` from `packages/app-shell/dist/views/metadata-admin/previews/screen-spec.js` / `flow-sim-validate.js`, plus `EVALUATED_EXPRESSION_SOURCE_REQUIRED` and `EvaluatedExpressionSchema` from `flow-sim-validate.js`. No other package surfaced a finding. - **M2** (confirm the four symbols): `npm pack @objectstack/spec@17.3.0` and `@17.4.0`, unpacked and grepped `dist/`. All four names: 0 hits anywhere under 17.3.0's `dist/`; present under 17.4.0's `dist/automation` and `dist/shared` (`.js` / `.mjs` / `.d.ts` / `.d.mts`). - **M3** (regenerate lockfile with pnpm): `pnpm-lock.yaml` diff is `1 file changed, 1 insertion(+), 1 deletion(-)` — only the `@object-ui/app-shell` importer's `@objectstack/spec` `specifier:` line moves, from `^17.3.0` to `^17.4.0`. The resolved `version:` on that line was already `17.4.0` before this change (normal resolution already picked the newest 17.x; `pnpm install` after the edit reported "Already up to date"). - **M4** (after the change): `pnpm check:spec-floors` exits 0 — "✅ Every consumer-facing `@objectstack/spec` floor carries the symbols its package's artifact references" (19 of 39 published packages inspected, 341 (subpath, symbol) pairs judged). `pnpm --filter @object-ui/app-shell type-check` exits 0 (`tsc --noEmit && tsc -p tsconfig.test.json`). ## Gates - `pnpm check:spec-floors` — red before (4 `floor-too-low` findings) → green after (0 findings; see M1/M4). - `pnpm --filter @object-ui/app-shell type-check` — exit 0. - `pnpm --filter @object-ui/app-shell test` — exit 0: `Test Files 841 passed | 1 skipped (842)`, `Tests 8618 passed | 9 skipped (8627)` (root-form invocation, `vitest run --root ../.. packages/app-shell/`, no filtering trap). - `node scripts/check-control-bytes.mjs` — exit 0 (9120 tracked text files scanned, 85 binary skipped). - `node scripts/check-changeset-presence.mjs` — exit 0 (1 changeset added; the `dependencies` version bump itself is not one of the eight published-contract fields the gate tracks, so it reported "no changeset is owed" independent of the one added). - `node scripts/check-changeset-fixed.mjs` / `check-changeset-no-major.mjs` — both exit 0. - `node scripts/check-lockfile-integrity.mjs` — VERDICT clean (no `@objectstack/*` identity moved backward, no package gained a copy). - `node scripts/check-lockfile-dedupe.mjs` — VERDICT deduped (`pnpm dedupe` would collapse nothing). - `node scripts/check-installed-spec-pin-claims.mjs` — OK (`@objectstack/spec = 17.4.0`, lockfile and resolved tree agree). - `node scripts/check-changeset-claims.mjs` (report-only) — flagged 4 pending changesets naming a file this PR touches (`pnpm-lock.yaml` or `packages/app-shell/package.json`). Read each against this diff: `5793-spec-range-floors.md` and `6361-spec-floor-17-2-0.md` describe a different importer's edge (their own packages resolving `17.2.0`, an edge this one-line specifier bump does not move); `6776-metadata-admin-lazy-registration.md` describes the `sideEffects` array, which this diff does not touch; `7122-objectstack-family-17-3-0.md` describes the `@objectstack/client` / `core` / `formula` / `lint` family pins, also untouched. None falsified — this is the fifth pending changeset the gate named, `5920-flow-runner-translation-overlay.md`, and that one *was* falsified and is amended above. - `node scripts/check-changeset-overwrite.mjs` (report-only) — reports the one changeset this PR modifies (`5920-…`); case 2, "correcting a declaration on purpose" — same package and bump level declared at base and now, only the body gained a dated note. - `node scripts/check-new-cross-file-line-citations.mjs` — 0 new citations. - `node scripts/check-pending-changeset-literals.mjs` — exit 0. ## Serial Re-checked open PRs against this branch's file surface: 11 open (`objectstack-ai#10880, objectstack-ai#10879, objectstack-ai#10878, objectstack-ai#10876, objectstack-ai#10875, objectstack-ai#10852, objectstack-ai#10780, objectstack-ai#10777, objectstack-ai#10714, objectstack-ai#10278`) plus the release PR `objectstack-ai#5400`. Only `objectstack-ai#10878` touches `pnpm-lock.yaml`, and only at the `@object-ui/data-objectstack` and `@object-ui/plugin-grid` importer blocks (each raising its own `@objectstack/spec` floor to `^17.4.0` independently) — not the `@object-ui/app-shell` block this PR moves. No open PR touches `packages/app-shell/package.json` or either changeset file. The release PR regenerates and is not a hold. --- _Generated by [Claude Code](https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN)_ --------- Co-authored-by: Claude <noreply@anthropic.com>
akarma-synetal
pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Sep 28, 2026
… accepts — a separator without label, branding kept on edit, no Layout control (objectui#10867) (objectstack-ai#10889) Fixes objectstack-ai#10867 Clause-②: yes (narrowing). Published `@object-ui/types` members narrow: the separator arm of `NavigationItem` loses `label`, and `AppWizardDraft` loses `layout`. That makes this `minor` plus a BREAKING (authoring) banner, and never `major`. Dispatched by the `domain:ui` seat 2 PM (claim comment 5861866471, triage 5861615446), session `https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN` (`mode:subagent`, so that id is also this run's). Branch `claude/issue-10867-app-wizard-saves-spec-app`, cut from `origin/main` `b93e245f9` (BASE); head `2c19f3047` after fix round 1 (round-0 head `e2493c796`). ## What changed **Member 1 — a separator carries only `type`, `id` and `order` (the p1).** - `@object-ui/types`: `NavigationItem` is now a union of two arms, discriminated by `type`. `NavigationEntryItem` is the former interface with `type` narrowed to every spec nav type except `'separator'`, and it keeps its required `label`. `NavigationSeparatorItem` admits `type`, `id` and `order`, the spec separator's keys, and every other entry key is `?: never` on it. Those `never` keys are derived from `NavigationEntryItem`, so a key added there is refused on the separator without an edit. Both arms are exported from the package root. `menuItemToNavigationItem` maps a legacy separator to `{ id, type: 'separator' }` and drops its label. - `spec-derived-unions.test.ts`: the blocker-3 pin (`_specSeparatorStillHasNoLabel`) is lifted. It is replaced by three agreement pins. `_separatorAdmitsTheSpecKeys` and `_separatorAdmitsTheSpecInputKeys` say the separator arm admits exactly the spec separator's keys at the output and input tiers. `_localSeparatorIsSpecValid` says the value types of the keys the arm admits are ones the spec's separator accepts at both tiers. `extends` ignores extra keys, so the key agreement is carried by the first two: the third alone passes a labelled arm, and it is vacuous on BASE. "Admits" means a key whose type is not `never`. The two remaining blockers (`visible: boolean`, and `pinned` / `defaultOpen`) are unchanged, and so is the umbrella verdict. - `@object-ui/types` zod mirror (fix round 1): `NavigationItemSchema`'s refinement has an explicit separator branch, and it used to return early, so `objectui validate` passed a separator `label` that the save door refuses with 422. That branch now refuses every key the spec's separator does not declare, each at its own path, with a message that names the key and the fix ("a separator carries only `type`, `id` and `order`; drop `label`"). The allowed set is read off the spec, not restated: the spec does not export `SeparatorNavItemSchema`, so it is taken from the separator arm of the spec `AppSchema`'s own `navigation` union. That schema already crosses the mirror's import boundary, so the objectui#8317 population is unchanged. The read throws if the arm is ever missing, instead of silently allowing everything. - `@object-ui/plugin-designer`: `AppCreationWizard`'s "Add separator" and `NavigationDesigner`'s two add paths (now one `newNavItem` helper) write `{ id, type }`. `NavigationDesigner` no longer writes a `label` onto a new separator, and its label, icon and visibility patchers skip one. - The union makes code that writes an entry-only key onto an unnarrowed item fail to compile, and each such site now narrows first. None of these edits changes what renders for valid data. - `@object-ui/layout`: `resolveNavItemLabel` answers `''` for every separator. A stored separator carrying a non-empty `label`, which `menuItemToNavigationItem` produced before this change, used to resolve to that label. No renderer asks it for a separator's label. The mobile bottom nav's leaf list, which already skipped separators, is typed as entries. `collectPinnedItems` tests the type before `pinned`. - `@object-ui/app-shell`: `useNavPins` registers a favorite only for an entry and leaves a separator as it is. The Studio sidebar's navigation walk passes a separator through unchanged. - Test fixtures that spread an item and add `visible` or `requiredPermissions` are typed as `NavigationEntryItem`. These are in layout's `AppSchemaRenderer` and `resolveHref` tests and app-shell's `UnifiedSidebar.derivedAreaVisibility` test. **Member 2 — an edit keeps the stored branding.** `EditAppPage` now merges `branding` one level down, by the objectui#10842 rule. It keeps every stored key the spec's `AppBrandingSchema` declares, read from `AppBrandingSchema.shape`, and the wizard's values win for the keys it maintains. A stored `accentColor` survives the save. A stored key the spec does not declare is still left out. **Member 3 — the Layout control is gone.** `AppWizardDraft.layout` is removed. The Basic Info step's Layout fieldset is removed, with its three icons and the draft default. `EditAppPage` no longer pre-fills `layout`. The step description now reads "Name, title, and icon". The four `appDesigner` layout keys are removed from `DESIGNER_DEFAULT_TRANSLATIONS` and from all ten locale packs, and `appDesigner.stepBasicDesc` is retranslated in all ten. **Text that the change made false:** - the `app.ts` module header and the `NavigationArea` docblock; - the `wizardDraftToAppSchema` docblock; - the `@object-ui/types:NavigationItem` and `@object-ui/types:NavigationItemSchema` ledger reasons in `scripts/check-spec-symbol-derivation.mjs` (the second now counts four divergences, not five); - the mirror's own `NavigationAreaSchema` docblock, which listed a separator `label` among the keys only the spec refuses; - the "separator label" row in `navigation-spec-parity.test.ts`: the faces now agree, so it left the divergence list and is asserted as an agreement (both refuse it); - the ROADMAP line for the wizard's Basic Info step. **Changesets.** - New `.changeset/10867-app-wizard-saves-spec-app.md`: `@object-ui/types` and `@object-ui/i18n` minor (removing published pack keys is a narrowing), and `@object-ui/plugin-designer`, `@object-ui/layout` and `@object-ui/app-shell` patch, with the `Clause-②: yes` line. The BREAKING (authoring) banner names every consequence, and each was checked against the code at TypeScript 6.0.3 by a throwaway probe: - a read of `label` into a `string` slot fails (TS2322); - a spread of an entry-only key fails (TS2322); - `interface … extends NavigationItem` fails (TS2312); - an augmentation of `NavigationItem` fails (TS2300); - `objectui validate` refuses a separator `label`; - `t()` on a removed key renders the raw key unless the call passes a `defaultValue`. The provider-less fallback is the defaults table, then `defaultValue`, then the key, and i18next is configured with `returnNull: false` and no missing-key parser. - Dated notes in the objectui#10533 form on two pending entries. - `10842-wizard-app-declared-keys.md`, titled "the wizard has no layout choice": its "the wizard's layout choice is not saved" has no choice left. Frontmatter md5 `5b8e68791c8bc51ef72179570fd15a1c` before and after. - `3162-types-ledger-batch8-verdicts.md`: its "three semantic blockers" count. Frontmatter md5 `2ee28f1e1b449ccc2dd97fdcc6c2bc1f` before and after. **Fixture triage:** - The `layout` key was dropped from the `AppWizardDraft` fixtures in `app-creation-types`, `app-declared-keys-10842` and `app-logo-one-spelling-10827`. These are spelling fixes: the key was there only because the type required it. - The vacuous `'layout' in schema` assertion in `app-creation-types` "should handle draft with empty navigation" was removed. - `navigation-model`'s "should convert a separator" pinned the removed `label: ''` branch, so it was replaced by an exact-shape assertion. - The `label: ''` was dropped from separator fixtures in `navigation-model`, layout's `AppSchemaRenderer.test` and app-shell's `phase1-page-blocks.render.test`. ## H1 to H3 (measured on BASE `b93e245f9`, installed `@objectstack/spec` 17.4.0) **H1 — reproduced.** A probe run through `wizardDraftToAppSchema`, then the spec's `AppSchema.safeParse`: - a draft with one object entry plus the separator the wizard wrote, `{ id, type: 'separator', label: '' }`, gave `[{"code":"unrecognized_keys","path":"navigation.1","keys":["label"]}]`; - control, the same draft without the separator: parses green; - control, the same separator without `label`: parses green; - `menuItemToNavigationItem({ type: 'separator', label: 'Section' })` gave `{"id":"migrated_0","type":"separator","label":"Section"}`. The new DOM pin gives the same reading through the real wizard and `CreateAppPage` on the base source: "the saved document parses green through the spec `AppSchema`" fails with `unrecognized_keys` `["label"]` at `navigation.1`. **H2 — reproduced.** The new pin "a stored `accentColor` survives the edit round trip" drives the real wizard through `EditAppPage`. On the base source it fails: the saved `branding` is `{ favicon, logo, primaryColor }`, and `"accentColor": "#f59e0b"` is missing. **H3 — census** (`git grep` over packages, apps, docs, examples, skills and content). Each hit goes or is corrected: - **`AppWizardDraft.layout` and the draft default:** - the member in `app.ts` — removed; - `DEFAULT_DRAFT.layout` in `AppCreationWizard` — removed; - `EditAppPage`'s `layout: appToEdit.layout || 'sidebar'` pre-fill — removed; - four draft fixtures — the key dropped (see the triage above). - **The step's UI:** the Layout fieldset (`app-layout-*` test ids, `draft.layout` reads and writes) and its three icon imports — removed. - **The step's strings:** - `appDesigner.layout`, `layoutSidebar`, `layoutHeader` and `layoutEmpty` in `DESIGNER_DEFAULT_TRANSLATIONS` and in ten locale packs — removed; - `appDesigner.stepBasicDesc` ("Name, title, and layout") in eleven places — corrected. - **Docs:** the ROADMAP Basic Info line — corrected. `content/docs/guide/console.md` and `console-architecture.md` describe the wizard's four steps and never the Layout control, so they are unchanged. - **Not this member:** the `layout: 'sidebar'` hits in `content/docs/core/app-schema.mdx`, `content/docs/guide/schema-overview.md`, the runner tests and the `AppComponentSchema` fixtures are `AppComponentSchema.layout`, the renderer node's own layout strategy. They are untouched, and the changeset says so. ## Pins and ablation New pins: - `packages/types/src/__tests__/app-wizard-separator-layout-10867.test.ts`: vitest halves, and `@ts-expect-error` / `satisfies` halves run under `tsc -p tsconfig.test.json`. - `packages/plugin-designer/src/__tests__/AppWizard.specDocument-10867.test.tsx`: drives the real `AppCreationWizard` through `CreateAppPage` and `EditAppPage` and reads what reaches `saveItem`. - The `spec-derived-unions.test.ts` agreement pins. - Fix round 1: `packages/types/src/__tests__/nav-separator-mirror-refusal-10867.test.ts`. `safeValidateSchema`, the strict authoring face (`StrictAnyComponentSchema`) and the mirror itself each refuse a separator `label`, each at its own path; the mirror also refuses `icon` and `pinned` on a separator. Controls: a bare `{ id, type: 'separator' }` (and one with `order`) is accepted by both faces and the spec, the spec refuses the same `label`, and an entry keeps its `label`. - Fix round 1: a new `EditAppPage` row, "a logo the author clears saves as cleared, not as the stored value". It is a guard, not a red-on-BASE pin: green on BASE and on HEAD, it fails if a later tidy-up drops empty strings from the merge. **Red on BASE.** Run from a committed tree: the source files were checked out at BASE, the new pins kept, and everything was restored from `HEAD` under a trap. The restore was proven by blob hash equal to HEAD and an empty `git diff HEAD`. - vitest `Tests 8 failed | 6 passed (14)`. The 8 failures are every non-control row: - `menuItemToNavigationItem`; - the two create-with-separator rows; - the three branding rows; - the two Layout rows. - The 6 passes are the controls and compile-only rows. - `tsc -p tsconfig.test.json` in `packages/types` gives the new pins': - TS2741 ×2 (a bare separator is missing `label`); - TS2578 ×2 (unused `@ts-expect-error` for a labelled separator and for a draft with `layout`); - TS1360 ×3 (the no-`layout` `satisfies` and the two separator-agreement pins). **Red before the mirror fix (round 1).** From the committed round-1 head, only `app.zod.ts` was checked out at the round-0 head `e2493c796`, under a trap; the restore was proven blob == HEAD and `git diff HEAD` empty. The new mirror pins plus `navigation-spec-parity` gave vitest `Tests 4 failed | 17 passed (21)`. The 4 failures are the refusal rows and the new agreement row; the controls passed. **Green on HEAD.** Round 0, at `e2493c796`: `Test Files 284 passed (284)`, `Tests 5676 passed (5676)`. Round 1, at `2c19f3047`: see Gates. The `packages/types` `tsc -p tsconfig.test.json` has 0 errors at both heads. **Ablation: the separator branch is reverted, and only the separator rows redden.** Three anchored mutations went through `ablation-replace.mjs`, each proven landed and restored by blob hash: - the `NavigationItem` alias gives its separator arm a required `label` again; - `menuItemToNavigationItem` writes `label` again; - the wizard's add-separator writes `label: ''` again. Result: - vitest `Tests 3 failed | 11 passed (14)`. The failures are `menuItemToNavigationItem`, "the saved document parses green" and "the saved separator carries only `type` and `id`". The branding and Layout rows stay green. - `tsc -p tsconfig.test.json`: 5 errors, all on separator lines. TS2322 ×2 (bare separators), TS2578 ×1 (labelled separator) and TS1360 ×2 (the two agreement pins). The Layout type pin stays green. - Restore: `blob == HEAD` and `git diff HEAD` empty for both files. **Cross-package reverse check.** The downstream type-checks resolve `@object-ui/types` through its rebuilt `dist`. Their first runs went red only on sites the new union refuses: layout 3, plugin-designer 4, app-shell 3 in source plus 4 in tests. They were green after narrowing. That red could only come from the rebuilt declaration. ## Gates Fix round 1, at `2c19f3047`, all under the verify lock: - vitest `packages/types/`, `packages/plugin-designer/` and `packages/i18n/`: `Test Files 356 passed (356)`, `Tests 6861 passed (6861)`. - vitest over the 18 app-shell navigation, pins and sidebar files, `examples/schema-catalog/test/`, the two cli `validate` suites and the three spec-symbol script suites: `Test Files 57 passed (57)`, `Tests 2487 passed (2487)`. - **Arm-list consumer sweep** for the mirror change. Every test that imports `NavigationItemSchema` or the app zod mirror, or runs `safeValidateSchema` / `StrictAnyComponentSchema` over an app or navigation document, was found by `git grep` and run with per-file verdicts: 34 files, 1251 tests, 0 failed. They include `zod-mirror-parity` 37/37, `navigation-spec-parity` 15/15, `imported-defaults-8317` 124/124, `nav-target-exclusivity-8563` 15/15, `navigation-model` 28/28, `zod-lazy-getter-identity-7918` 31/31, `page-nav-misc-spec-parity` 44/44, `handler-keys-json-refusal-6124` 336/336, the two app-shell studio-design nav suites 22/22 and 3/3, cli `validate-root-path-line` 6/6 and the catalog `tree-view-nodes-mirror-6939` 22/22. - `tsc -p packages/types/tsconfig.test.json`: 0 errors. `@object-ui/types` `type-check`: 0 `error TS`. `@object-ui/plugin-designer` `type-check`, after rebuilding its closure: clean. - Changeset gates: - `check-changeset-presence` ✅; - `changeset:check` ✅ (no `major`); - `check:changeset-claims` (report-only) lists 15 pending entries naming a touched file; the six new ones (4895, 6335, 7113, 7735, 7918 and 8871) were read, and none claims anything a separator refusal falsifies; - `check-changeset-overwrite` (report-only): the two dated-note edits; - `check:pending-changeset-literals` ✅. - Other gates: `check:control-bytes` OK, `check:new-line-citations` 0 new, `check:spec-symbols` ✅, the three i18n gates ✅, `type-check:coverage` ✅. - Round 1 changed no exported type and no layout, app-shell or console source, so the round-0 downstream type-checks below still describe this head. Round 0, at `e2493c796` unless noted: - `pnpm exec vitest run packages/types/ packages/plugin-designer/`: `Test Files 284 passed (284)`, `Tests 5676 passed (5676)`. - `pnpm --filter` `@object-ui/types`, `@object-ui/layout`, `@object-ui/plugin-designer` and `@object-ui/app-shell` `run type-check` (each `tsc --noEmit && tsc -p tsconfig.test.json`; types also runs `tsconfig.examples.json`): verify-lock `VERDICT command-exit 0`. - `@object-ui/console` `type-check` after rebuilding its dependency closure: exit 0, 0 `error TS`. - vitest `packages/layout/` and `packages/plugin-designer/` (after the narrowing): `Tests 436 passed (436)`. - vitest `packages/i18n/`, app-shell `defaults-maps-mirror-en-pack`, `phase1-page-blocks.render` and layout `AppSchemaRenderer`, plus the `check-spec-symbol-derivation`, `spec-symbol-ledger-anchor-liveness-9537` and `spec-symbol-ledger-types-7265` script suites: `Tests 1354 passed (1354)`. - 17 app-shell files covering pins, favorites, the sidebar and nav fixtures: `Tests 160 passed (160)`. - Changeset gates: - `check-changeset-presence` ✅ (5 released packages, 1 changeset); - `changeset:check` ✅ (no `major`); - `check:changeset-claims` (report-only): 9 pending entries name a touched file, and each was read — none is falsified; - `check-changeset-overwrite` (report-only): lists the two dated-note edits; - `check:pending-changeset-literals` ✅. - i18n gates: `check:i18n-keys` ✅, `check:i18n-drift` ✅ ("Every changed en value was followed by all nine translation packs"), `check:i18n-designer-parity` ✅. - Other gates: - `check:spec-symbols` ✅; - `check:control-bytes` OK; - `check:new-line-citations`: `VERDICT new-cross-file-line-citations: 0 new citation(s)`; - `type-check:coverage` ✅ (43/43); - `check:test-path-roots` OK; - `check:vi-mock-specifiers`, `check:vi-mock-inherit` and `check:vi-mock-override-shape` OK; - `check:metadata-write-doors` OK; - `check:unreferenced-sources` OK; - `check:handler-key-reads` OK. - ESLint on the 34 changed `.ts` / `.tsx` / `.mjs` files (repo config, inline config honoured): 0 errors and 47 warnings. Each warned file carries the same warning count at BASE, measured by linting the BASE blob through `--stdin`, so no warning is new. The repo-wide `pnpm lint` is CI's. - NOT MEASURED: - the full app-shell suite, because it runs past the foreground cap; declared to CI; - `check:readme-exports` for the unbuilt `@object-ui/cli` and `@object-ui/plugin-ai` READMEs, which are untouched here. Its judged population read 548 self-imports and 0 fabricated. - Scheduling: two light runs (the red-on-BASE pair) went outside the verify lock. The lock was held for more than 20 minutes by a sibling's full app-shell suite, and this is declared as a narrowing. Every build, suite and type-check above ran under the lock. ## Serial - Open PRs read at 2026-09-28T03:3xZ: objectstack-ai#10888, objectstack-ai#10886, objectstack-ai#10884, objectstack-ai#10852, objectstack-ai#10780, objectstack-ai#10777, objectstack-ai#10714 and objectstack-ai#10278, plus the release PR. None of their file lists intersects this diff. - `origin/main` has moved to `b2683a2c0` since BASE. `git merge-tree --write-tree` against it is clean. Of the files main moved, only `en.ts` overlaps, on other keys. No file main moved mentions `NavigationItem`, `AppWizardDraft` or the removed keys. ## Acceptance notes - **The zod twin, corrected in fix round 1.** Round 0 read the claim's "if the mirror carries the separator branch" as not met, because the mirror is one flat object. The contract review measured that the refinement does have an explicit separator branch, so the condition held, and the mirror now refuses what the TypeScript face refuses (see What changed). - **Boundary note, not taken: pre-17 tombstones.** Dropping the spec's tombstone keys from `EditAppPage`'s kept set would make the save succeed silently and lose the author's value. The spec's current loud refusal carries a prescription, so this is left as it is. - **Boundary note, not taken: `BrandingConfig.fontFamily`.** `BrandingEditor` reads and writes it, and removing it is not a cheap change inside these files. - **`AppComponentSchema.layout` is untouched.** It is a different member, the renderer node's layout strategy. - **An edit through the wizard drops stored navigation** (found while pinning member 2; not fixed here; the seat is filing it as its own card, and the review confirmed this PR does not make it worse). Leaving the Objects step regenerates `navigation` from the selected objects unconditionally. In edit mode that replaces the stored tree, so separators, groups, URL entries and dashboards are lost on every save. Measured with a throwaway probe through `EditAppPage` and the real wizard: a stored `[object, separator, group with a dashboard child, url]` saved as `[object]` only. --- _Generated by [Claude Code](https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN)_ --------- Co-authored-by: Claude <noreply@anthropic.com>
akarma-synetal
pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Sep 28, 2026
…ts name 41 objectui issues that answer 404 (objectui#10803, batch 5) (objectstack-ai#10892) Part of objectstack-ai#10803 Clause-②: no Dispatched implementation of the `domain:ui` seat 2 claim (comment `5862515185`) on objectui#10803, batch 5, 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, all in `@object-ui/types`: the six `ChatbotSchema` tombstone guidance strings open `RETIRED (ADR-0049) —` (rulings `5861129870` and `5861311219`), the `page` node's `actions` refusal, an ADR-0049 tombstone too, cites `(ADR-0049)` in place of its dead card (ruling `5861129870`, as measured in patch round 1), and the `ChartDataSeriesSchema.variant` description drops its pointer (amendment `5860244997`, Q1 = A). Two tests that pin changed text follow it, anchor only (ruling `5861900779`, route a). **Patch round 1** answers the contract review's one FAIL item on `afed8aa6b`: Special cases 7 had read the `actions` refusal as not ADR-0049 from a proxy (the `breadcrumbs` changeset, which only says the 2026-09-09 RULING is not borrowed). Measured from the retirement itself, it is an ADR-0049 tombstone, so under the seat's option (a) its string now reads "never was (ADR-0049): no renderer reads it". The runtime-strings changeset follows, and the sweep changeset notes that `@object-ui/types`' runtime text is declared separately. One text-only commit, `8255f14f4`; no merge, no force-push. ## Why `Part of`, not a closing line The card stays open for the other 23 numbers of the family remainder (seat amendment `5860244997`, Q2 = A), listed in **Acceptance notes** 1, and for the bare sister-repo numbers the C0 census below lists. ## Premise, re-measured - REST `GET /repos/objectstack-ai/objectui/issues/N` for each of the 41: all 41 answer 404, and a second read of each answers 404 again (41 of 41). `GET .../pulls/N` answers 404 for all 41 too. Lit controls: objectui#10533 and objectui#7714 answer 200. No number was dropped from the batch. - The same 41 in objectstack all answer 200. Three of them are the sites' real subject, read not guessed, and are re-qualified (Zone 1 item 5): - objectstack#3720 "列表行级 edit/delete 与批量删除未接入服务端 effective 操作集": the five `[objectstack-ai#3720]` sites in `ObjectGrid.tsx`, `rowCrudAffordances.ts` and `ListView.tsx` describe that gate, and their landing `ba4514511` is titled "gate list row Edit/Delete and bulk delete on the effective operation set (objectstack#3720)". - objectstack#5506, the "five more hardcoded English chrome strings" card: `useDetailTranslation.ts` wrote "the SAME key objectstack-ai#5506 gave NavigationOverlay's identical handle", and nine sibling in-scope lines already cite `objectstack#5506` for those strings. - objectstack#6936, the metadata-admin predicate fail-CLOSED card: `predicate.ts` wrote "objectstack-ai#6936's `true` verdict" one line below "objectstack#6936's unresolved-path ruling". - Every other site names an objectui card or pull request, confirmed by its landing commit below (for example objectstack#7853 is a `driver-memory` finding, while objectui#7853 is the cite-by-content ruling AGENTS.md objectstack-ai#11 names). - Every edited changeset is pending: it is present in `.changeset/` on `main`. - Branch point: `b2683a2c0`. `main` is now `4f8b7f86a`; its census still reads 215, and the merge of this head with it reads 0. Not a shallow checkout. ## C0: the bare-number remainder (measurement only) The instrument of PR objectui#10875, at the branch point: ``` git grep -hoP '(?:^|(?<=[^\w#&/.\-]))#\d+(?![0-9A-Za-z_])' b2683a2 -- '.changeset/*.md' 'packages/*/src/**' ':!**/__tests__/**' ':!**/*.test.*' ':!**/*.spec.*' ':!**/test/**' ':!**/tests/**' | sort -u | wc -l ``` - **998 distinct bare numbers** at `b2683a2c0` (1002 at batch 4's `e32dae160`): the eight batch 4 re-pointed are gone, and four are new since: objectstack-ai#10321, objectstack-ai#8365 and objectstack-ai#9242 (at or below 10900, each read once: 200) and #20051. - **Above 10900: 23**, batch 4's 22 plus #20051. Each was read once with REST `GET .../issues/N`: **23 answer 404**, and each answered 404 again on a second read (23 of 23); `GET .../pulls/N` answers 404 for the 18 that are not colours. - None of them is an objectui citation, and none sits in a sentence or hunk this batch edits, so **nothing is folded here**: - **5 are CSS colours:** #334155, #336699, #475569, #737373, #953800. - **18 are objectstack numbers**, 16 of which answer 200 there with the sites' own subject. #13033 and #13413 answer 404 in objectstack too. Sites (lines / files, at `b2683a2c0`) are listed in **Acceptance notes** 2 for later batches. ## Census (the enumeration pin for this batch) The instrument PR objectui#10854 printed and PRs objectui#10869 / objectstack-ai#10875 reused, with this batch's 41 numbers substituted (REF = a commit or tree): ``` git grep -nE '(objectui#|#|issues/)(7091|7097|7108|7177|7612|7620|7623|7658|7666|7667|7669|7678|7681|7682|7703|7704|7708|7804|7844|7853|7869|7874|7877|7926|7959|7967|7979|7980|8058|8060|3720|5420|5503|5506|5737|6467|6936|6945|7622|7662|7684)([^0-9]|$)' REF -- '.changeset/*.md' 'packages/*/src/**' ':!**/__tests__/**' ':!**/*.test.*' ':!**/*.spec.*' ':!**/test/**' ':!**/tests/**' | grep -v 'objectstack#' | wc -l ``` - REF = `b2683a2c0` (branch point, and `main` now): **215** lines, 74 changeset lines in 55 files and 141 src lines in 47 files. - REF = `8255f14f4` (this head): **0**. Round 0's head `afed8aa6b` also read 0. - This head merged with a fresh `main` (`4f8b7f86a`, `git merge-tree --write-tree`, clean, tree `08f80168a`): **0**. REF = `4f8b7f86a` alone: 215. - **The filter hid nothing this time.** The 18 branch-point lines the `grep -v 'objectstack#'` drops name only objectstack#6936 or objectstack#5506; with those tokens deleted, none of them matches the instrument (0). Unfiltered, this head reads **26**, all live `objectstack#` lines: the 18, the seven re-qualified here, and the same spelling in the new sweep changeset. - 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 instrument with the 41 numbers, unfiltered, whole tree at this head): 367 test lines in 98 files, 23 scripts lines in 5 files, 0 `.github`, 5 governed lines in 4 files (`AGENTS.md` and three `skills/objectui` files), and 51 other lines in 18 files: published `CHANGELOG.md` history (21 lines in 8 files), `content/docs` (11 in 4), `apps/console` (7 in 3), `eslint-rules` (8 in 2) and `eslint.config.js` (4). See **Acceptance notes** 4. ## 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 / objectstack-ai#10875. All 40 distinct shas in the mapping 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 it 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 (**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). - Where the claim lived only on the dead card (a finding, a ruling, a scope, a comment), the sha only locates it: "the card behind SHA", "the ruling behind SHA" (**Special cases** 3). 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#7612, objectstack-ai#7666, objectstack-ai#7682, objectstack-ai#7844, and the open objectstack-ai#7804 parent). - Runtime text carries no sha: see **Special cases** 7. ## Mapping (number to resolution) Lines / files are the branch-point census for that number. "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#7091 (a pull request) | `969ba84f4` | `git log --grep`: its squash subject ends "(objectstack-ai#7091)" | 1 / 1 | it registers the console `app:launcher` renderer, which is what made the "not a page" clause false | | objectstack-ai#7097 | `3cab5703b`; own-card pointer dropped | changeset's adding commit | 3 / 3 | it adds the `2xl` read arm and the literal `GRID_COLS_2XL` class map, the value-level fix both sentences name | | objectstack-ai#7108 | `1267508ea`; own-card pointer dropped | changeset's adding commit | 3 / 2 | it tombstones a deleted record reference in the approvals inbox, the platform-flagged class the sentences name | | objectstack-ai#7177 | own-card pointer dropped (landing `ebc05b4d6`) | changeset's adding commit | 1 / 1 | the only site is its own changeset's pointer | | objectstack-ai#7612 | "the 2026-09-20 ruling"; the card by role | `git log --grep` finds only `2ca238075`, the objectui#10150 record of the ruling; the switch, PR objectui#10054, closed unmerged | 3 / 2 | nothing landed: the ruling was "no". See **Special cases** 3 and 4 | | objectstack-ai#7620 | `c15d7eca6`; "ruling A behind `c15d7eca6`" where the sentence cites the ruling; own-card pointer dropped | changeset's adding commit, `git log -S` | 13 / 10 | it moves `data-table`'s date-only fallback onto `formatDate`'s default face, and its message records the two-faces fact pattern the sentences cite | | objectstack-ai#7623 | `5d0876c5c`; own-card pointer dropped | changeset's adding commit | 3 / 3 | it retires the inert dashboard-root `title` declaration | | objectstack-ai#7658 | `90c6d090d`; own-card pointer dropped | changeset's adding commit | 2 / 2 | it keeps code-span content out of `extractToc`'s HTML strip | | objectstack-ai#7666 | nothing answers: the card by role ("already-filed defect") | `git log -S` finds only `a472b0716`, which records it as an already-filed defect | 1 / 1 | see **Special cases** 3 | | objectstack-ai#7667 | `a472b0716`; own-card pointer dropped | changeset's adding commit | 2 / 2 | it gives `extractToc`'s emphasis rules the flanking rule that keeps `SCREAMING_SNAKE` underscores | | objectstack-ai#7669 (a pull request) | `a3eb5d07a` | `git log --grep`: its squash subject ends "(objectstack-ai#7669)" | 2 / 2 | it retires `FloatingChatbotConfig.triggerIcon` as the tombstone both sentences name | | objectstack-ai#7678 | `5f8190c8c` ("in its amended form"); own-card pointers dropped | changeset's adding commit; its body opens "Part of objectstack-ai#7678" | 21 / 14 | it brings every statement of the retire-vs-remove discriminator to the amended form, the surviving-carrier precondition included. See **Special cases** 6 | | objectstack-ai#7681 | `01c27c431`; own-card pointer dropped | changeset's adding commit | 6 / 4 | it routes a `dataKey`-shaped series through `normalizeSeries`, removing the fast path, so its `type` override is honoured | | objectstack-ai#7682 | nothing answers: "a separate card"; runtime pointer dropped | `git log -S` finds only `8fe8e5c16`, which defers that decision to it | 3 / 3 | see **Special cases** 3 | | objectstack-ai#7703 | `a4611b3e2`; runtime text `RETIRED (ADR-0049) —`; own-card pointer dropped | changeset's adding commit | 15 / 3 | it retires the six dark `ChatbotSchema` keys as ADR-0049 tombstones | | objectstack-ai#7704 | `20316bac3`; "the card behind `20316bac3`" for the scope note; own-card pointer dropped | changeset's adding commit | 3 / 2 | it adds `chatbot-enhanced` and `chatbot-floating` to `SchemaRegistry` | | objectstack-ai#7708 | `d3499b315`; PR objectstack-ai#8077 kept where it stands beside the dead card; "the card behind `d3499b315`" for the ruling; own-card and runtime pointers dropped | changeset's adding commit, `git log --grep` | 13 / 6 | it fences `chatbot-floating`'s raw props spread through `toDomProps` at the head of the element | | objectstack-ai#7804 (the handler-key parent) | per slice, by `git blame`: `75fca9669` (data-table), `7ca6ddd4b` (detail), `f1cd29032` (list-view), `5a41ce733` (object-kanban), `8d50bc2bf` (objectql.ts), `604476d97` (tree-view); own-card pointers dropped; "the handler-key parent card" where the sentence means the open parent | each slice changeset's adding commit, and `git blame` per line | 49 / 17 | each commit declares exactly the handler keys the site's arm or face names | | objectstack-ai#7844 | nothing answers: "their own card" | `git log -S` finds only `c4a1d39fe`, which leaves both sub-shapes dark | 1 / 1 | see **Special cases** 3 | | objectstack-ai#7853 | "the card behind `fa7d66c45`" | AGENTS.md objectstack-ai#11 names `fa7d66c45` as its landing | 3 / 3 | the ruling lived on the card; `fa7d66c45` is its one-site landing | | objectstack-ai#7869 | "the finding objectui#8344 discharged" / "the finding this card discharges" (landing `841dd2b7e`) | `841dd2b7e`'s message; the live objectui#8344's body, "Discharges the finding objectstack-ai#7869" | 2 / 2 | the measurement lived on the dead finding, and the live card that discharged it restates it | | objectstack-ai#7874 | `d9580f464`; PR objectstack-ai#7887 kept beside the dead card; own-card pointer dropped | changeset's adding commit | 3 / 3 | it retires the five dead `timeline.relative.*` rows | | objectstack-ai#7877 | `7dcda9cd4` | `git log -S` on the heading | 1 / 1 | it moves the hand-rolled-table data into `hand-rolled-tables.json`, the heading's subject | | objectstack-ai#7926 | `12b599219`; "the 2026-09-09 ruling"; "the `actions` refusal" by role beside PR objectstack-ai#8870; runtime text `(ADR-0049)`; own-card pointer dropped | changeset's adding commit | 15 / 6 | it refuses `actions` by name on the `page` node, measures `breadcrumbs` at 1 site and leaves it parsing, and pins that | | objectstack-ai#7959 | `36fc74629`; "the card behind `36fc74629`" for its scope restraint | the tests it added are headed "objectui#7959" | 8 / 6 | it adds `readEnvelopeFailureText`, the userMessage-first rule on `PackagesPage`, and the load-failure testid | | objectstack-ai#7967 | own-card pointer dropped (landing `0544ae958`) | changeset's adding commit | 1 / 1 | the only site is its own changeset's pointer | | objectstack-ai#7979 | own-card pointer dropped (landing `bfa4fe728`) | changeset's adding commit | 1 / 1 | the only site is its own changeset's pointer | | objectstack-ai#7980 | `a810bb2ae`; "the card behind `a810bb2ae`" for its surface and its comment; own-card pointer dropped | changeset's adding commit | 4 / 3 | it publishes `readEnvelopeFailureText` from the package entry | | objectstack-ai#8058 | `3f4b45886` | `git log -S storedRelationshipTarget` | 5 / 2 | it adds `storedRelationshipTarget`, the read door under both spellings, and rewrites the "costs nothing" claim | | objectstack-ai#8060 | `7dc31bb8d`; "step 1 of the card behind `7dc31bb8d`" | `git log --grep`: its subject names "(objectstack-ai#8060)" | 8 / 3 | it carries a stored type the designer cannot author through verbatim (`partitionStoredFields`) instead of flattening it to `text` | | objectstack-ai#3720 (C0) | re-qualified `objectstack#3720` | `ba4514511`'s subject; objectstack#3720's subject | 5 / 3 | see **Premise** | | objectstack-ai#5420 (C0) | own-card pointer dropped (landing `b470e9150`) | the adding commit's subject names "(objectstack-ai#5420)" | 1 / 1 | the only site is its own changeset's heading | | objectstack-ai#5503 (C0, a pull request) | `6f017e99c` | its squash subject ends "(objectstack-ai#5503)" | 1 / 1 | it puts the chart min-height floor on the element Recharts measures | | objectstack-ai#5506 (C0) | re-qualified `objectstack#5506` | nine sibling in-scope lines already cite it for the same strings | 1 / 1 | see **Premise** | | objectstack-ai#5737 (C0, "PR objectstack-ai#5737") | `d1ab06f0f` | its squash subject ends "(objectstack-ai#5737)" | 4 / 4 | it declares `record.*` the row-predicate canon and warns on the two deprecated spellings, which is Phase 1 | | objectstack-ai#6467 (C0) | own-card pointer dropped (landing `5ad0641e0`) | its subject names "(objectstack-ai#6467)" before its own "(objectstack-ai#7332)" | 1 / 1 | the only site is its own changeset's pointer | | objectstack-ai#6936 (C0) | re-qualified `objectstack#6936` | the line above already cites it | 1 / 1 | see **Premise** | | objectstack-ai#6945 (C0, "PR objectstack-ai#6945") | `2c45966ff` | its squash subject ends "(objectstack-ai#6945)" | 1 / 1 | it declares the 13 renderer-read keys the sentence says objectui#6150 declared first | | objectstack-ai#7622 (C0, "PR objectstack-ai#7622") | `1cca678ba` | its squash subject ends "(objectstack-ai#7622)" | 1 / 1 | it retires the dashboard-root `title` read on all five surfaces | | objectstack-ai#7662 (C0, "PR objectstack-ai#7662") | `bc640ec56` | its squash subject ends "(objectstack-ai#7662)" | 1 / 1 | it is the change to `SchemaRegistry`'s kanban entry the sentence ascribes to objectui#7645 | | objectstack-ai#7684 (C0, "PR objectstack-ai#7684") | "the contract review of `8fe8e5c16`'s pull request" | its squash subject ends "(objectstack-ai#7684)" | 2 / 2 | the review lived on the dead pull request; the sha only locates it | ## Special cases (the judgement calls) 1. **A dead card beside its own live landing.** - `defaults-table-scan.ts`: "rows of objectui#7874 at all (retired in objectstack-ai#7887)" becomes "rows at all (retired in objectstack-ai#7887)". PR objectstack-ai#7887 answers 200 and is `d9580f464`'s pull request. - `7703-chatbot-dark-keys-retired.md`: "**after** objectui#7708's fence landed as PR objectstack-ai#8077" becomes "**after** the fence landed as PR objectstack-ai#8077". In the same file "until objectui#7708 the `chatbot-floating` registration ended…" becomes "until PR objectstack-ai#8077 the…", and the next sentence's "That card was ruled **fence**, not declare, and landed as PR objectstack-ai#8077" becomes "Its card was ruled **fence**, not declare, and landed as that PR", so it keeps an antecedent. - `8871-page-node-refuses-breadcrumbs.md` and `layout.zod.ts`: "corrects objectui#7926's "1 site"", beside "(PR objectstack-ai#8870)", becomes "corrects the `actions` refusal's "1 site"". The changeset's "objectui#7926's `patch` does not transfer here" becomes "The `actions` refusal's `patch` does not transfer here". 2. **The sister-repo numbers.** `[objectstack-ai#3720]` becomes `[objectstack#3720]` at five sites; "objectstack-ai#5506" and "objectstack-ai#6936's" become `objectstack#5506` and `objectstack#6936`'s. See **Premise**. 3. **The card named by role.** - **objectstack-ai#7612**, `clientValidation.ts`: "The switch was then put to the maintainer on objectui#7612" becomes "…on its own card". Nothing landed: the ruling said no, and the switch PR closed unmerged. The verbatim ruling quote 「7612 只需要服务端校验」 stays as the maintainer wrote it; it carries no `#`. - **objectstack-ai#7666**, `7667-toc-emphasis-flanking.md`: "(objectui#7666, a heading `extractToc` lists…)" becomes "(a heading `extractToc` lists…)". The sentence already calls it "a different, already-filed defect". - **objectstack-ai#7682**: "objectui#7682 owns that decision" becomes "a separate card owns that decision" (`7546-chart-series-keys-declared.md`), and "objectui#7682's decision" becomes "a separate card's decision" (`data-display.ts`). - **objectstack-ai#7844**, `8754-…` changeset: "the two further sub-shapes objectui#7844 records" becomes "the two further sub-shapes recorded on their own card". - **objectstack-ai#7804 as the open parent**: "whose disposition is still open on objectui#7804" becomes "…on the handler-key parent card" (`9447-…`); "both are ledgered to objectui#7804, which owns it" becomes "…to the handler-key parent card" (`handler-key-reads-follow-cast-receivers.md`); `crud.zod.ts`'s "objectui#7804's rows are the handler keys" becomes "the handler-key parent card's rows…". - **"The card behind SHA"**, where the sentence rests on something that lived only on the card: - objectstack-ai#7620's ruling A: "following the maintainer's ruling A on objectui#7620" becomes "…ruling A behind `c15d7eca6`" in four `@object-ui/fields` widgets, and `GridField`'s "the split objectstack-ai#7620 ruled on" becomes "the split ruling A settled". `RelatedList.tsx`: "objectui#7443 and objectui#7620 spent two cards" becomes "objectui#7443 and the card behind `c15d7eca6` spent two cards". - objectstack-ai#7708's ruling: "objectui#7708 ruled FENCE" becomes "The card behind `d3499b315` ruled FENCE", and "That ruling was FENCE" after it becomes "The ruling behind it was FENCE" (`complex.ts`). - objectstack-ai#7853: "objectui#7853 ruled…" becomes "The card behind `fa7d66c45` ruled…" in both objectstack-ai#8875 changesets and in `defaults-table-scan.ts`'s list. - objectstack-ai#7959's scope restraint: "objectui#7959 kept/left it off the public entry as scope restraint — that card's file surface was…" becomes "The card behind `36fc74629` …" (`7980-…` changeset, `app-shell` `index.ts`). - objectstack-ai#7980: "see objectui#7980 comment 5583988475" becomes "as the card behind `a810bb2ae` records" (a comment on a dead card resolves nowhere); `PackageFormDialog.tsx`'s "is objectui#7980's surface" becomes "is the surface of the card behind `a810bb2ae`". - objectstack-ai#7704's scope note (`registry.ts`) and objectstack-ai#8060's "step 1" (`MetadataFieldsPage.tsx`) take the same form. - objectstack-ai#7869: the finding card is dead, and the live objectui#8344 discharged it and restates the measurement, so `base.zod.ts` reads "That is the finding objectui#8344 discharged: an off-spec `size`…" and objectstack-ai#8344's own changeset reads "the finding this card discharges measured…". 4. **Rulings by date.** - objectstack-ai#7612: the `AUTHOR_SHAPE_ONLY_TYPES` heading ends "(the 2026-09-20 ruling)"; `10150-author-shape-header-ruling.md` reads "the switch was put to the maintainer, and the 2026-09-20 ruling was option A". Its last sentence, "requires the docblock to name the ruling's card", becomes "…to name the ruling", because the pin it describes now anchors on the ruling (**Special cases** 8). - objectstack-ai#7926: "objectui#7926's maintainer ruling covers `actions`" becomes "The 2026-09-09 maintainer ruling covers `actions`", and "objectui#7926 does not rule on it" becomes "the 2026-09-09 ruling does not cover it" (`layout.zod.ts`). 5. **Own-card pointers that needed a word.** - `7097-grid-2xl-breakpoint.md`: the pointer sat on its own line, so the period moved up with it. - `7678-tombstone-discriminator-agreement.md`: "the site objectui#7678 was filed about" becomes "the site this card was filed about", the file's own wording two lines earlier. - `7804-object-kanban-handler-keys-judged.md`: "its `KNOWN_UNDECLARED_READS` row naming objectui#7804, which stays open and stays the parent" becomes "its `KNOWN_UNDECLARED_READS` row, which names the parent card". - The six `7804-*` slice changesets keep "(the … slice)" once the pointer goes, as batch 4 kept "(slice 2)". 6. **The discriminator form (objectstack-ai#7678).** "in the form objectui#7678 amended it to" becomes "in its amended form (`5f8190c8c`)" at every site; "as amended by objectui#7678" and "amended by objectui#7678" take the same wording; a bare "objectstack-ai#7678" in a precedent list becomes `5f8190c8c`. `mobile.ts`'s "without the precondition objectui#7678 added" becomes "without the precondition the amendment added", whose antecedent is the preamble's "amended form" two sentences up. `9684-discriminator-cited-once.md`: "objectui#7678's amendment had to be applied by hand" becomes "the amendment (`5f8190c8c`) had to be applied by hand", which is what that commit did. 7. **The runtime strings.** Only the listed text moves in each. | file | member | before | after | |:--|:--|:--|:--| | `types/src/zod/complex.zod.ts` | `ChatbotSchema.loading`, `.showAvatars`, `.userAvatar`, `.assistantAvatar`, `.markdown`, `.height` (tombstones) | "RETIRED (objectui#7703, ADR-0049) — …" | "RETIRED (ADR-0049) — …" | | `types/src/zod/complex.zod.ts` | `ChatbotSchema.showAvatars` (tombstone) | "… unfiltered props spread — was fenced by objectui#7708. Delete the key: …" | "… unfiltered props spread — was fenced. Delete the key: …" | | `types/src/zod/layout.zod.ts` | `PageNodeSchema.actions` refusal | "`actions` is not a key of the `page` node and never was (objectui#7926): no renderer reads it, …" | "`actions` is not a key of the `page` node and never was (ADR-0049): no renderer reads it, …" | | `types/src/zod/data-display.zod.ts` | `ChartDataSeriesSchema.variant` `.describe()` | "… the renderer-internal `current` spelling is not a member (objectui#7682)" | "… the renderer-internal `current` spelling is not a member" | **The ADR-0049 condition, measured from the retirement itself** (Zone 1 item 4): the six tombstones already cited `ADR-0049` beside the dead card; the zod comment above them opens "ADR-0049 retirement tombstones"; their landing `a4611b3e2` is titled "retire six dark ChatbotSchema keys as ADR-0049 tombstones"; and the pending `7703-chatbot-dark-keys-retired.md` says "ADR-0049 retirement tombstones". The `actions` refusal is an ADR-0049 tombstone too, measured the same way: its arm is `retirementTombstone(PAGE_ACTIONS_REFUSAL)`, its landing `12b599219` calls it "an ADR-0049 `retirementTombstone` arm", and `7926-page-node-refuses-actions.md` calls it "an ADR-0049 refusal arm". Its string has no `RETIRED` opener, so its own parenthetical becomes `(ADR-0049)`, the spelling its `breadcrumbs` sibling already uses. The TypeScript twins in `complex.ts` read "ADR-0049 RETIREMENT TOMBSTONE — `loading` (`a4611b3e2`)", the comment form. 8. **What follows the text, and nothing else in it** (ruling `5861900779`, route a; ruling `5861129870`). - `chatbot-dark-keys-retired-7703.test.ts` pins the six guidance strings as full literals. Their openings follow to `RETIRED (ADR-0049) — `, the `showAvatars` literal follows "was fenced.", its `prescriptive` anchor `'was fenced by objectui#7708'` becomes `'was fenced.'`, and `toContain('RETIRED (objectui#7703')` becomes `toContain('RETIRED (ADR-0049) —')`. Its test names and `@ts-expect-error` comments still read "RETIRED (objectui#7703)"; they describe the `?: never` TypeScript face and are out of class (**Acceptance notes** 6). - `clientValidation.authorShapeRuling-10150.test.ts` pins that the `AUTHOR_SHAPE_ONLY_TYPES` header names the ruling and `extractDraftBody`. Its subject `'objectui#7612'` becomes `'the 2026-09-20 ruling'`; its message and title are unchanged. - No test, doc or changeset quotes the `actions` refusal or the `variant` description verbatim: a whole-tree search for the old strings returns only the source lines. 9. **The anchor sweep (PR objectui#10875 Special cases 10 shape).** - **Instrument:** every string, template, numeric and regex literal in all 3822 test and script files under `packages/` and `scripts/`, enumerated with `git ls-tree` at head and parsed with TypeScript (113091 distinct literals). - **Test applied to each literal:** does its occurrence count DROP between `b2683a2c0` and head in any file this PR changes, in raw text or in a comment-flattened form? - **Run 1, on `8c267051f`** (the sweep commit, before any test moved): 336 distinct literals drop. Read against the files they sit in, the specific anchors are the two pins in item 8 (the six literals, the `prescriptive` anchor and the `toContain` in the first; `'objectui#7612'` in the second). Also listed and read: the `'objectui#7804'` values of `check-handler-key-read-sites`'s `KNOWN_UNDECLARED_READS` ledger and its test, which assert over the script's own data and never read a changed file, and `tombstone-discriminator-agreement-9684`'s `/RETIRED \(objectui#/`, which it applies to `mobile.ts` alone, untouched here. - **Everything else** is a generic token (whitespace, punctuation, single letters and digits, `objectui#`, character-class regexes of whole-tree scanners), none an assertion over text this PR changed. - **Run 2, on round 0's head `afed8aa6b`:** 327 distinct literals; the nine literals the two pins moved are gone from the drop set, nothing new appears, and the only one left naming a batch number is that ledger value. - **Run 3, patch round 1, over the delta `afed8aa6b..8255f14`:** 18 (literal, file) drops, every one a generic token (`' is'`, `'dropped'`, a `/(\w+):/g` scanner); no test pins the changed refusal text. ## Held **By the serial rule: nothing.** Patch round 1 re-read: 8 open besides this PR (objectui#10896, objectstack-ai#10891, objectstack-ai#10890, objectstack-ai#10889, objectstack-ai#10888, objectstack-ai#10777, objectstack-ai#10278 and the release PR objectstack-ai#5400; objectstack-ai#10886 and objectstack-ai#10714 have left the open list). New since round 0, objectui#10896 shares `plugin-grid/src/ObjectGrid.tsx` and `plugin-list/src/ListView.tsx`; trial merges of this head with every open head are clean except objectstack-ai#10278 (conflicts identical against `main` alone) and the release PR objectstack-ai#5400, which regenerates. The round's one source edit, in `layout.zod.ts`, is held by no open PR. Round 0, re-read before its push: 11 open besides this PR. They are objectui#10890, objectstack-ai#10889, objectstack-ai#10888, objectstack-ai#10886, objectstack-ai#10884, objectstack-ai#10852, objectstack-ai#10780, objectstack-ai#10777, objectstack-ai#10714, objectstack-ai#10278 and the release PR objectstack-ai#5400. - Five of them hold files this PR edits: - objectui#10890: `types/src/ai.ts`; - objectui#10888: `.changeset/8344-node-recursion-point-redirect.md`; - objectui#10886: `types/src/objectql.ts` and `types/src/zod/objectql.zod.ts`; - objectui#10714: `types/src/data-display.ts`, `types/src/layout.ts`, `types/src/zod/data-display.zod.ts` and `types/src/zod/layout.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 47 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#10890, objectstack-ai#10889, objectstack-ai#10888, objectstack-ai#10886, objectstack-ai#10884, objectstack-ai#10852, objectstack-ai#10780, objectstack-ai#10777 and objectstack-ai#10714. - objectstack-ai#10278 (`eab4c8e52`) conflicts in `ObjectGrid.tsx`, `plugin-grid/README.md` and `content/docs/plugins/plugin-grid.mdx`, and conflicts identically against `main` alone. - PR objectstack-ai#5400 (Version Packages) regenerates and is not a hold. ## Changesets - `.changeset/10803-dead-citation-sweep-fifth-batch.md`, EMPTY frontmatter: the comment-only edits in 15 released packages and the private `@object-ui/test-support`. No published behaviour changes through them. It marks `@object-ui/types` as the package "whose runtime text is declared separately below" (patch round 1) and points at the second file for it. - `.changeset/10803-fifth-batch-runtime-strings.md`, `'@object-ui/types': patch`: the six tombstones open `RETIRED (ADR-0049) —` with everything after the dash unchanged except the `showAvatars` pointer; the `actions` tombstone cites `ADR-0049` in place of its dead card; and the `variant` description loses its pointer. No key, path, issue code, accept set, refusal or severity moves. ## Proof of prose-only (C4), against `b2683a2c0`, on this head `8255f14f4` - **Source.** Each of the 49 touched `.ts` / `.tsx` files (47 non-test sources and the two pins) was parsed at `b2683a2c0` and at this head with TypeScript's `createSourceFile` and re-printed by `createPrinter({ removeComments: true })`. - 44 of 49 prints are identical. - The other 5 are equal once exactly the 19 listed substitutions are applied to the base print, each matched once: `complex.zod.ts` 7 (six openings and the fence pointer), `layout.zod.ts` 1 (the pointer becomes `(ADR-0049)`), `data-display.zod.ts` 1, `chatbot-dark-keys-retired-7703.test.ts` 9 (the same seven, the `prescriptive` anchor and the `toContain` anchor), `clientValidation.authorShapeRuling-10150.test.ts` 1. - 0 parse diagnostics. - Lit controls on the same instrument: dropping "(ADR-0049)" from the `loading` string moves the print; re-spacing the "ADR-0049 retirement tombstones" comment does not. - **Changesets.** The frontmatter block of every one of the 55 edited changesets is byte-identical at `b2683a2c0` and this head (55 of 55, by md5). The overwrite gate below agrees. - **Scope of the diff:** 106 files: 55 edited and 2 new changesets, 47 non-test source files, and 2 tests. ## Gates, on this head `8255f14f4` Each line is the gate's own verdict and exit code, captured by redirect-then-`$?`. - `node scripts/check-changeset-presence.mjs`, exit 0: "48 source file(s) of 15 released package(s) changed, and this change declares 2 changeset(s): .changeset/10803-dead-citation-sweep-fifth-batch.md, .changeset/10803-fifth-batch-runtime-strings.md." (48 = the 46 released sources and the 2 tests under released packages' `src/`; `test-support` is 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, 55 modified, 0 deleted". `declared at base` equals `declares now` for 55 of 55. - `pnpm check:changeset-claims` (report-only), exit 0: - born-false: "Every one of those 2 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 in its own prose, or negated only in an ASPECT of it that may legitimately hold still"; - the standing notice "103 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, which reads 0. No pending changeset quotes a changed runtime string. - `pnpm check:control-bytes`, exit 0: "check-control-bytes: OK (scanned 9145 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: `pnpm check:pending-changeset-literals`, exit 0: "No test source names a pending changeset."; the governed-surface predicate over the 106 paths, exit 0: "NOT GOVERNED — 106 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.** The branch-point copies of the two pins were written over the committed sweep tree and run: `Test Files 2 failed (2)`, `Tests 13 failed | 29 passed (42)`, for example "expected 'RETIRED (ADR-0049) — never read: chat…' to contain 'RETIRED (objectui#7703'". Both files were then restored with `git checkout HEAD --`, each checked by blob hash against `HEAD`, and `git diff HEAD` came back empty. - **Patch round 1, on this head `8255f14f4`:** `page-actions-refusal-7926` (it pins the message's remedy words `actions`, `children` and `page:header` and that it is not zod's generic text, never the pointer; verified by reading it), `page-breadcrumbs-refusal-8871`, `guide-layout-page-buttons-7926`, `zod-mirror-parity`, `chatbot-dark-keys-retired-7703`, `clientValidation.authorShapeRuling-10150` and `tombstone-discriminator-agreement-9684` give `Test Files 7 passed (7)`, `Tests 134 passed (134)`, under `VERDICT command-exit 0`. A whole-tree search for "never was: no renderer" finds no test or doc quoting it (only the source line and the runtime-strings changeset, both updated); an anchor sweep over the round's delta finds only generic tokens. - **Green, round 0, on `afed8aa6b`:** `chatbot-dark-keys-retired-7703`, `clientValidation.authorShapeRuling-10150`, `tombstone-discriminator-agreement-9684`, `page-actions-refusal-7926`, `page-breadcrumbs-refusal-8871`, `chart-series-keys-7546`, `zod-mirror-parity`, `chatbot-display-mode-retired` and `schema-registry-chatbot-keys-7704` give `Test Files 9 passed (9)`, `Tests 173 passed (173)`, under `VERDICT command-exit 0`. **Declared narrowing (per the dispatch: the named checks, not wider sweeps).** NOT MEASURED locally: the full suites and type-check of the 15 touched packages, and eslint. Reason: the comment-stripped syntax tree of 44 of the 49 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** 9) and run above. CI runs the full farm. ## Acceptance notes 1. **The remainder rides this card, unchanged (seat amendment `5860244997`, Q2 = A).** Of the 53 numbers PR objectui#10875's Acceptance notes 1 lists, this PR carries the first 30 in ascending order, plus the 11 C0 404s of its Acceptance notes 2. The other **23** are: 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 numbers above 10900, for later batches** (sites at `b2683a2c0`, lines / files). Each answers 404 as an objectui issue, and none is an objectui citation, so the fix is a re-qualification to objectstack, not a landing sha: - written with a word that names the repository but not in `repo#N` form ("objectstack PR #N", "upstream #N", "framework #N", "spec #N"): objectstack-ai#11289 (2 / 2), objectstack-ai#11662 (1 / 1), #12616 (1 / 1), #12718 (1 / 1), #13033 (1 / 1), #13413 (1 / 1), #13733 (1 / 1), #13906 (6 / 3), #14274 (1 / 1), #15469 (2 / 2), #20160 (2 / 2); - written bare: #13337 (1 / 1), #13632 (3 / 3), #13855 (1 / 1), #14945 (1 / 1), #15948 (1 / 1), #17493 (1 / 1), #20051 (1 / 1); - #13033 and #13413 answer 404 in objectstack as well; - not citations: #334155, #336699, #475569, #737373, #953800 (CSS colours). 3. **A live-but-wrong bare number beside a re-qualified one.** `rowCrudAffordances.ts` cites "(`/me/permissions` `apiOperations`, objectstack-ai#3391)" at the two sites that now read `[objectstack#3720]`. objectui#3391 answers 200 with an unrelated subject (a record-header api action placeholder), while objectstack#3391 is the apiMethods whitelist contract card that objectstack#3720's own title names. It is not a 404, so it is outside the family pin and was not touched. Carrier: none. 4. **Published or shipped text outside the two in-scope classes still names some of these numbers** (counts in **Census**). It is untouched by scope, as another class the triage split did not scope here: published `CHANGELOG.md` history (never re-addressed), `content/docs` (for example the chatbot and layout guides), `apps/console` (the approvals inbox and the agent-connect section), `eslint-rules` and `eslint.config.js`, three `skills/objectui` files and `AGENTS.md` (governed). Carrier: none. 5. **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, objectstack-ai#10869 and objectstack-ai#10875. 6. **Test comments left as they are.** `chatbot-dark-keys-retired-7703.test.ts`'s test names and `@ts-expect-error` comments still read "RETIRED (objectui#7703)", and `clientValidation.authorShapeRuling-10150.test.ts`'s header, title and message still name objectui#7612. Only anchors moved (ruling `5861900779`). --- _Generated by [Claude Code](https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN)_ --------- Co-authored-by: Claude <noreply@anthropic.com>
akarma-synetal
pushed a commit
to akarma-synetal/objectui
that referenced
this pull request
Sep 28, 2026
…tchet counts the namespaced half (objectui#10872, batch 1) (objectstack-ai#10888) Part of objectstack-ai#10872 Clause-②: yes Batch 1 of the namespaced slice of the objectui#10859 family. **20 of the 28 namespaced ADR-0080 public blocks** now validate — every one whose props `@objectstack/spec` declares as a `ComponentPropsMap` row, less `element:number`. The other 8 are held on measured readings, and the seat's ruling on objectui#10872 keeps them held (Acceptance notes). Measured split posted on the card before this PR: comment 5862647089. Head `0212421eda`: fix round 1 (`42f1cd1d2c`) fixed the two CI shards red at `4679a3120` (block-config node oracle, handler-key alias census) and swept the repo for suites that introspect the arm list; fix round 2 (`0212421eda`) is text only — the contract review's wording corrections to the changeset, the module docblock and one checker comment. ## What changed - **`packages/types/src/zod/public-blocks.zod.ts` (new).** One arm per armed block — `PageHeaderBlockSchema`, `PageTabsBlockSchema`, `PageCardBlockSchema`, `PageAccordionBlockSchema`, `PageSectionBlockSchema`, `PageFooterBlockSchema`, `PageSidebarBlockSchema`, `RecordDetailsBlockSchema`, `RecordHighlightsBlockSchema`, `RecordRelatedListBlockSchema`, `RecordPathBlockSchema`, `RecordActivityBlockSchema`, `RecordDiscussionBlockSchema`, `RecordHistoryBlockSchema`, `RecordQuickActionsBlockSchema`, `RecordReferenceRailBlockSchema`, `RecordAlertBlockSchema`, `ElementTextBlockSchema`, `ElementButtonBlockSchema`, `ElementDividerBlockSchema` — and the category union `PublicBlockComponentSchema`. - **`packages/types/src/zod/index.zod.ts`.** The 21 names on the `./zod` barrel; `PublicBlockComponentSchema` joins `AnyComponentSchema`'s arm list. - **`packages/types/src/zod/README.md`.** An "ADR-0080 Public Blocks (20)" group. - **Pins:** `packages/types/src/__tests__/public-block-arms-10872.test.ts` (new), and the objectui#10859 ratchet file `packages/cli/src/__tests__/registered-types-validate-ratchet-10859.test.ts` extended with the namespaced count and an in-process `objectui validate` run. - **Ledgers:** 21 `EXCLUSIONS` rows in `zod-mirror-parity.test.ts`; the 17 `ComponentPropsMap` row symbols the arms read added to `imported-defaults-8317.test.ts`'s `IMPORTED` differential. - **Fix round 1 (`42f1cd1d2c`):** `block-config-schema-parity-8216.test.ts` (app-shell previews) — the NODE oracle judges an arm whose props live in a `properties` object member AT that member, derived from the arm (`propsLevelOf`), plus a control row; `check-handler-key-read-sites.test.ts` — `page:tabs` leaves the objectui#9573 alias population and its `onTabChange` read is pinned as judged on its own arm; `check-handler-key-read-sites.mjs` — two prose paragraphs that named `page:tabs` as an alias, amended. - **Fix round 2 (`0212421eda`, text only):** the changeset's lead sentence names twenty blocks; its flat-props bullet separates keys `BaseSchema` does not declare from the ones it does; the `action:*` reason in the changeset and in `public-blocks.zod.ts`'s docblock is the seat's (no spec row yet, measured upstream on objectstack-ai/objectstack#20371), and the docblock's flat-key paragraph carries the same `BaseSchema` distinction; `check-handler-key-read-sites.mjs`'s amendment points at boundary 3. - **Changesets:** `.changeset/10872-public-block-zod-arms.md` (`'@object-ui/types': minor`, the `Clause-②: yes` line, no BREAKING banner); one dated note on `.changeset/8344-node-recursion-point-redirect.md` (objectui#10533 form, frontmatter byte-identical) — see Acceptance notes. ## M1 — reproduced on `main` (`c6678b1bd`) - `safeValidateSchema({ type: KEY })` over the 419 namespaced keys of `KNOWN_SCHEMA_TYPES`: **418 refused** with `invalid_union` at `type`; `ui:calendar` accepted. Bare: 76 (the objectui#10859 pin). - `objectui validate` (the CLI's `validate`, in-process on source) on a page whose children are `page:header` (`properties.title`), `action:button` (`label`, `actionType: "url"`, `target`) and `record:details`: exit 1, `Schema validation failed`, one refusal per block — `No arm accepts type "page:header" at children → 0.`, `… "action:button" at children → 1.`, `… "record:details" at children → 2.` - At head the same page fails at `action:button` alone; the page of `page:header` + `record:details` + `element:text` — batch 1's page pin as the seat's ruling amends it — prints `✓ Schema is valid!`, `Type: page`, exit 0. ### The α / β split (419 namespaced keys) Twin = text after the first colon. "Same registration" = the namespaced key and its bare twin come out of the same registration call (read from `deriveRegistryKeys`, the derivation `KNOWN_SCHEMA_TYPES` is generated from). | class | keys | refused at `type` | |---|---|---| | (α) same registration, bare twin validates | 149 | 149 | | (α′) same registration, bare twin itself refused — objectui#10859's bare half | 77 | 77 | | (β) bare spelling belongs to a DIFFERENT registration | 44 | 43 (`ui:calendar` accepted) | | (β) no bare spelling | 149 | 149 | By spelling alone α would read 189; 40 of those are false twins, the triage's own example among them (`view:grid` is plugin-grid's registration, bare `grid` the layout primitive). All 28 public blocks are β (15 with no bare spelling, 13 whose bare spelling is another component). ## M2 — the 28 public blocks, by declaration source | source | count | blocks | |---|---|---| | spec `ComponentPropsMap` row (installed 17.4.0) | 21 | `page:header` `page:tabs` `page:card` `page:accordion` `page:section` `page:footer` `page:sidebar` · `record:details` `record:highlights` `record:related_list` `record:path` `record:activity` `record:discussion` `record:history` `record:quick_actions` `record:reference_rail` `record:alert` · `element:text` `element:number` `element:button` `element:divider` | | no spec row; registration `inputs` only | 3 | `record:line_items` `element:definition-list` `element:repeater` | | no spec row; TS schema types in `@object-ui/components` + registration `inputs` | 4 | `action:button` `action:group` `action:menu` `action:icon` | | no declaration anywhere | 0 | — | | bare-key twin arm | 0 | — | Disagreements, spec wins: `element:definition-list` / `element:repeater` are in the spec's reserved `element:` namespace but not its vocabulary (`isKnownComponentType` false, `hasReservedComponentNamespace` true), so the spec refuses the TYPE at author time; `record:line_items` is in the spec's `STRING_ARM_REGISTERED_TYPES` ledger as a row still to be measured. ## M3 — homes, Serial New module `public-blocks.zod.ts` (no open PR can hold it) plus `index.zod.ts`. ⛔ Not `blocks.zod.ts`: it is the objectui#4895 tombstone, pinned empty by `block-family-retired-4895.test.ts`. Re-read at fix round 2. `origin/main` is `45dbf1cbae`: since `b2683a2c0e` it has landed objectui#10714, objectstack-ai#10780 and objectstack-ai#10852. None of them touches a file of this diff, a `type` literal, `BaseSchema` (`base.zod.ts` / `base.ts`), `known-schema-types.ts` or `public-blocks.ts` — objectstack-ai#10714's zod edits are the list-item and tabs-item `body` refusals in `data-display.zod.ts` / `layout.zod.ts`. `git merge-tree --write-tree` of this branch (`0212421eda`) against `45dbf1cbae` is clean (exit 0), so main was not merged in. CI on `42f1cd1d2c` ran on a merge ref over `b2683a2c0e` — every workflow run for that head reports PR base `b2683a2c0e`, all 26 completed `success` or `skipped`. Open PRs on these surfaces: objectui#10890 edits `zod-mirror-parity.test.ts` in a different hunk (merge-tree of the two heads, `0212421eda` against `f6891cde45`, exit 0); objectui#10889 edits other `packages/types` files and none of this diff's; objectui#10892 (a citation sweep, 106 files) edits `.changeset/8344-node-recursion-point-redirect.md`, which this diff also touches, in a different hunk (merge-tree against `afed8aa6b4`, exit 0). The other open PRs (objectui#10891, objectstack-ai#10886, objectstack-ai#10884, objectstack-ai#10777, objectstack-ai#10278) touch no file of this diff. ## M4 — the strict face Confirmed derived, no edit: `StrictAnyComponentSchema` walks `AnyComponentSchema`, and the pins read it accepting every minimal and every spec-valid document of the 20, and refusing an undeclared node key by name (`unrecognized_keys`). ## The arms - **Where the props live.** A `ComponentPropsMap` row is the spec's declaration of the props BAG — `PageComponentSchema.properties` — so each arm is `BaseSchema` + the `type` literal + `properties`, whose value IS the row, by reference through `stripImportedDefaults` (objectui#8317). Members, value types, `.describe()` text, strictness, refinements and the spec's retired-key tombstones all arrive from the spec; nothing is restated. The bag is what every one of these renderers reads (`SchemaRenderer` hoists it onto the node; the `element:*` renderers read nothing else), and what the synthesizer and page designer write. - **Optional bag.** As on `PageComponentSchema`; the spec's props gate (`validateComponentProps`) judges a bag only when present, and so do the arms. - **One restatement.** `element:divider`'s row is `emptyProps('element:divider')`, exported under no name, so it cannot cross the objectui#8317 boundary (its census admits only a spec binding passed straight to `stripImportedDefaults`). The arm restates it as a member-less strict object; the pin holds its key set and accept set equal to the row's. - **One `on*` member.** `page:tabs`' renderer calls a host-injected `onTabChange` (app-shell's `withPageTabsUrlSync`), so `check:handler-key-reads` required it declared: `handlerKeyRefusal('onTabChange', 'runtime-slot', …)`. No other arm's renderer reads an `on*` key off the node (the gate: 128 arms, 50 reads, all judged). - **Flat keys** are not judged against the block's row. A key `BaseSchema` does not declare (`{ "type": "record:details", "columns": "2" }`) passes the tolerant face, as an undeclared key does on any arm, and the strict face refuses it. A key the base does declare is judged by the base instead: `children` (`page:card`, `page:section`, `page:footer`, `page:sidebar`), `label` and `disabled` (`element:button`) and `visible` (`record:alert`) against the base's own types, and `body` (`page:card`, `record:alert`) is refused on both faces by the base's objectui#6771 retirement — a `record:alert` banner's `body` goes inside `properties`. Measured by probe on source: flat `columns` tolerant-accepted and strict-refused; flat `body` on `record:alert` and `page:card` refused on both; flat `label: 5` and `visible: 5` refused on both; the same `body` inside `record:alert`'s `properties` accepted on both. ## Census rows `zod-mirror-parity.test.ts` `EXCLUSIONS`, 21 rows: 19 "spec-owned BY REFERENCE" (`page:tabs`' names its `onTabChange` refusal), `ElementDividerBlockSchema` "spec-owned, RESTATED" pointing at its pin, `PublicBlockComponentSchema` "a union OVER the public-block arms". No `MIRRORS` pair: no TS declaration in `@object-ui/types` restates any of these nodes. `record-components.ts`'s `Record*ComponentProps` restate six of these bags (not the nodes) on the TS face and are pinned to the spec by their own tests, not to these arms. One measured difference: `RecordRelatedListComponentProps.title` is `string` where the row takes `I18nLabel` (the row accepts `{ en: 'Tasks', 'zh-CN': '任务' }` as `title`). No `KnownDrift` or other ledger row moved. ## Pins and ablation `public-block-arms-10872.test.ts` — per armed block: minimal document and a spec-valid bag accepted by `safeValidateSchema` and by `StrictAnyComponentSchema` (each fixture first parsed by the spec's own row); bag key set equal to the row's, and the bag IS the row object wherever the boundary strips nothing. Plus: an undeclared member inside the bag refused on the TOLERANT face by name; an undeclared node key refused on the STRICT face by name (control: tolerant passes it); a spec-refused value refused at `properties.variant`; a spec-retired key (`page:card` `actions`) refused at the member; `onTabChange` refused `custom`; a nested block judged by its own arm; `element:divider` pinned to its row both ways. | run | result | |---|---| | base — detached worktree at `c6678b1bd`, the two pin files copied in | `Tests 94 failed / 6 passed (100)`. The 6 green: the four pre-existing bare-ratchet rows, the objectui#10859 README row, the namespaced non-vacuity control | | head `4679a3120` | `100 passed` — both files, inside the full `5967 passed` run under Gates | | ablation: `PublicBlockComponentSchema` dropped from `AnyComponentSchema`'s list | `Tests 51 failed / 49 passed (100)` | Ablation, observed direction: red — all 40 acceptance rows, both page documents, the namespaced ratchet (`refuses 418 … the pin is 398.` + the MORE-than-the-pin guidance), the armed-list row, and every refusal row (with no arm they refuse at `type`, not by name). Green — the 43 rows that read the arms directly off `PublicBlockComponentSchema` (literal list, barrel, key sets, identity, divider) plus the 6 above; those rows are introspection, not validation. Mutation and restore through objectstack's `scripts/ablation-replace.mjs` in WRAP mode inside a script with its own EXIT/INT/TERM trap: anchor x1 → x0, blob `0a4466287501` → `c53fe2dc222a`, restored to the HEAD blob with `git diff HEAD` empty. Vitest aliases `@object-ui/types/zod` to `src/`, so no build sits between mutation and reading. ## The ratchet Same file, same style, a second pin: `NAMESPACED_REFUSED_AT_TYPE = 398` (418 on `main`, less the 20), lower-it / never-raise messages, refused keys printed either way; non-vacuity (population over 400, `ui:calendar` lit, an invented key refused); a row naming the 20 armed keys. Counted apart from the bare pin because it is another card's batches. **The bare pin stays 76**: no bare literal was added. The file also runs `objectui validate` on the three-block page (exit 0, `Schema is valid`) and on the same page with an invented bag key (exit 1, the key named). ## Gates **Fix round 2, at head `0212421eda` (text only), under the verify lock:** the tests that pin the changed texts — `check-changeset-claims.test.ts`, `changeset-polarity-census.test.ts`, `render-changeset-claims-comment.test.ts`, `markdown-test-inputs.test.ts`, `check-handler-key-read-sites.test.ts`, `public-block-arms-10872.test.ts`, `zod-mirror-parity.test.ts` and the ratchet file → `Test Files 8 passed (8)`, `Tests 421 passed (421)`. No test or script quotes the rewritten prose of `public-blocks.zod.ts` (a `git grep` of that file name in tests finds the census reason keys and one header path only). exit 0: `check-changeset-presence` (`8 source file(s) of 3 released package(s) changed, and this change declares 1 changeset(s)`), `pnpm changeset:check` (`No changeset declares a major bump`), `check-changeset-overwrite` (report-only: the 8344 note, frontmatter unchanged), `check:changeset-claims` (report-only; self-contradiction corpus 2 bodies, `✅ Every package declared … is either not negated`; 20 paragraphs named, the one new name — `9447-detail-view-handler-key-refusal.md`, on `check-handler-key-read-sites.mjs` — describes the gate's transitive hop and is untouched by a comment edit), `check:pending-changeset-literals`, `census:changeset-polarity`, `markdown-test-inputs.mjs --audit` (`105 candidate test files, all adjudicated`), `check:handler-key-reads` (`OK 128 arm(s)`), `check:control-bytes`, `check:new-line-citations` (`0 new citation(s)`). At head `42f1cd1d2c` (fix round 1), all under the verify lock where they run tests or builds: - `pnpm exec vitest run packages/types/ packages/cli/ scripts/__tests__/markdown-test-inputs.test.ts` plus the checker's other test readers (`detail-handler-slots-7804`, `detail-view-handler-slots-9447`, `handlerKeyDispositionsMeasured-7804`, `check-component-surface-parity`) → `Test Files 285 passed (285)`, `Tests 6049 passed (6049)` — **0 failed**. - **CI shard 6/8 — `block-config-schema-parity-8216.test.ts`.** Red at `4679a3120`, reproduced locally by running that revision's copy of the file against the arms: "unledgered BLOCK_CONFIG field names refused by their schema", **29 rows**, all `@node` (28 MISSING such as `page:header::title@node`, `element:text::content@node`, `record:related_list::objectName@node`, and `record:alert::body@node` RETIRED — `BaseSchema`'s node-level `body` refusal, not the row's `body`). The oracle was reading the node's top level while the designer edits `properties`. Green at the fix: the node oracle descends into a `properties` member that unwraps to an object (derived from the arm, no type list), and **0 rows stay red** — every designer field of the 20 blocks is a member of its spec row, so there is no real designer-to-row mismatch to report. No ledger or exemption row was added. Non-vacuity at the fix: `no node arms resolved` (more than 20) passes; the `object-kanban` `groupField` RETIRED / `groupBy` accepted pair passes; a new control row pins the descent both ways (`page:header` judged at its bag: `title` accepted, `icon` RETIRED, `properties` not a listed key; `object-kanban` still judged at its top level). - **CI shard 2/8 — `check-handler-key-read-sites.test.ts`.** Red at `4679a3120` (same probe method): the objectui#9344 leg (`page:tabs` `unmirroredAlias` read `undefined`) and the objectui#9573 population (5 aliases, not 6). Green at the fix: the population is the five remaining aliases, and the `page:tabs` row asserts the new state — no `unmirroredAlias`, `schema` `PageTabsBlockSchema`, `declared` true, disposition `runtime-slot`, the arm table's own `onTabChange` member `runtime-slot`, no re-keying onto `tabs`. Ablation, WRAP mode inside a script with its own EXIT/INT/TERM trap: `type: z.literal('page:tabs'),` → `…'page:tabs-ablated-10872'…` (anchor x1 → x0, blob `33a2d8a26927` → `4f91055807d6`) → `Tests 2 failed | 47 passed (49)`: the new row (`page:tabs is an armed type, not an alias: expected { bareType: 'tabs', … } to be undefined`) and the population (6 vs 5); restored, blob == HEAD, `git diff HEAD` empty. - **The sweep round 0 missed.** Every test file in the repo matching `AnyComponentSchema`, `StrictAnyComponentSchema`, `safeValidateSchema`, `nodeOracles`, `KNOWN_SCHEMA_TYPES`, `PUBLIC_BLOCKS`, `unmirroredAlias`, `collectArms`, `getPublicConfigs` or `ComponentPropsMap`, plus every test importing `@object-ui/types/zod` that walks `Object.values` / `.entries` / `.keys` or `.options`: **204 files**. The 88 under `packages/types` and `packages/cli` ran in the suite above; the other **116** ran together → `Test Files 116 passed (116)`, `Tests 2044 passed (2044)`. By package: `examples/schema-catalog` 15, `packages/components` 15, `packages/plugin-calendar` 10, `packages/plugin-kanban` 8, `apps/console` 7 (incl. `registry-inputs-spec-parity`, `public-contract`, `public-block-binding-reach`, `record-block-record-reach`, `html-tier-manifest`), `scripts/__tests__` 6, `packages/app-shell` 8 (incl. the four previews suites `block-config-schema-parity-8216`, `block-config`, `definition-list-item-keys-8279`, `page-tabs-item-value-8278`), `packages/plugin-view` 5, `packages/plugin-grid` 5, `packages/plugin-map` 4, `packages/plugin-list` 4, `packages/plugin-detail` 7, `packages/core` 6, `packages/plugin-tree` 3, `packages/plugin-form` 4, `packages/plugin-dashboard` 3, `packages/sdui-parser` 2, and one each in `test-support`, `plugin-gantt`, `plugin-chatbot`, `plugin-charts`. Every one passed; the per-file list is on the card's report. - `pnpm --filter @object-ui/types type-check` (all three programs) → exit 0 and `pnpm --filter @object-ui/cli type-check` → exit 0 (both at `4679a3120`; round 1 changed neither package); `pnpm type-check:scripts` → exit 0 at `42f1cd1d2c`. - exit 0 at `42f1cd1d2c`: `check:handler-key-reads` ("OK 128 arm(s)"), `check:control-bytes`, `check:new-line-citations` ("0 new citation(s)"), `check-changeset-presence`, `check:pending-changeset-literals`, `check:test-path-roots`. Earlier at `4679a3120` and untouched by round 1: `pnpm changeset:check`, `check-changeset-overwrite` (report-only; the 8344 note), `check:changeset-claims` (report-only; read below), `check:spec-symbols`, `check-type-check-coverage`, `check:unreferenced-sources`, `check:esm-specifiers`, `check:doc-types`, `check:prompt-keys`, `check:registry-bare-names`, `check:side-effects-array`, `check:self-import`; `markdown-test-inputs.mjs --audit` → "105 candidate test files, all adjudicated". - eslint, a proven narrowing, `--no-inline-config --format json`: round 0's six `.ts` files → 0 errors, 2 warnings; round 1's three files → 0 errors, 4 warnings. All six warnings are `no-explicit-any` on lines this diff did not write, and the same files at `c6678b1bd` / `4679a3120` carry the same counts. Population: `@object-ui/types` lints `.`, `@object-ui/cli` lints `src`, `@object-ui/app-shell` and the root `scripts/` sit under the root `eslint .`; `eslint.config.js` sets no `projectService` / `parserOptions.project`, so no type-aware rule can move an untouched file's verdict. The full `pnpm lint` is CI's. - NOT MEASURED: `@object-ui/app-shell` `type-check` (its `tsconfig.test.json` leg covers the edited previews test) — reason: it needs the app-shell dependency closure built, the cost the order's scope does not name; the edit is two `unknown`-typed helpers. CI's `Type Check` measures it. Also `check:readme-exports`, `check:doc-snippets`, `check:doc-examples` — they need the full package build; no README or content doc changed. ## Acceptance notes - **Held — with a declaration, not armed:** - `element:number` — the row requires `object`, which the spec's props gate waives when the node binds through `dataSource.object` (`DATASOURCE_SUPPLIED_PROP`, `@objectstack/lint`); the row alone would refuse that spec-valid node. Arming needs that carve-out, and `dataSource` itself is an envelope key no arm declares yet. - `record:line_items` — no spec row on purpose (the `STRING_ARM_REGISTERED_TYPES` ledger: to be measured from the renderer's read points). Its five registration `inputs` undercount real authoring: the showcase's project-detail page authors `title` in the bag. - `element:definition-list`, `element:repeater` — the spec's closed `element:` vocabulary does not declare them, so the spec refuses the type at author time while `PUBLIC_BLOCKS` curates both. Per the seat's ruling on objectui#10872 (option A), they get spec rows upstream first and stay held here until then; arming them now would make `objectui validate` accept what `os validate` refuses. - `action:button`, `action:group`, `action:menu`, `action:icon` — no spec row. Per the seat's ruling on objectui#10872 they stay held (option D now, route C next): no spec row yet; one is being measured from the renderers' read points upstream (objectstack-ai/objectstack#20371). The ruling's reading: `action-button.tsx` reads `schema.name ?? schema.label`, so `name` is optional where the renderer reads it, and AGENTS.md objectstack-ai#4's taught `action:button` carries none; the spec `Action` is a different declaration (object-metadata actions keyed by `name`, recorded as structurally unrelated in `ui-action.ts`), so restating it would refuse the governed instructions file's canonical example. - **The page pin:** the seat's ruling on objectui#10872 amends batch 1's page pin to `page:header` + `record:details` + `element:text`, which is what ships; the `action:button` page pin moves to this card's `action:*` batch. - **No declaration anywhere:** none of the 28. - **α batch plan (not this batch):** pair by registration, never spelling — 149 α keys reuse their bare arm under a second literal, one schema, two literals, ⛔ no copy; the 77 α′ keys follow as objectui#10859 arms each bare key. The 40 false spelling-twins (`view:grid` first among them) are β and need their own declarations. - **Flat props channel:** whether `page:` / `record:` blocks may also author props flat on the node (their renderers read the hoisted keys) is not decided here; declaring it later is additive, and never for `element:*`, whose renderers do not read a flat key. - **Envelope keys** the spec's `PageComponentSchema` declares beside `properties` and `BaseSchema` does not — `events`, `responsiveStyles`, `dataSource`, `aria`, `visibility` (the spec's deprecated alias of `visibleWhen`) and `responsive` (which the spec itself retired) — are not on these arms: tolerant passes them, strict refuses them. No taught public-block document carries one (the 14 teaching sites in `content`, `skills`, `docs`, `examples` and the READMEs that name an armed type, read 12 lines past each), and the strict face has no in-repo consumer, so nothing taught is newly refused. - **Nested blocks inside a bag** (`properties.children`, `items[].children` on `page:tabs` / `page:accordion`) are `z.array(z.unknown())` in the spec rows, so a child block there is not judged by this validator — measured: an invented child type with an invented key inside `page:section`'s `properties.children` parses. That is correct by reference: the row is the spec's, and the spec does not judge it either. - **Content channels:** objectui#9256's per-channel narrowing is not applied to the new arms (not measured for these renderers in this batch). - **Pending changesets read.** `check:changeset-claims` named the entries that cite a file this diff touches. Falsified by this change: `8344-node-recursion-point-redirect.md` — its objectui#10859 dated note says both module counts are "one higher"; with `public-blocks.zod.ts` they are two higher. Dated note added, frontmatter byte-identical. Read and left, true of this diff: `5903`, `5928`, `6051`, `6150`, `6175`, `6639`, `7344`, `7654`, `7694`, `7804`, `8338`, `8498` and `8784` (their objectui#10859 notes describe that change's addition; no `type` literal collides), `8499` (every new arm is named on the barrel, so its figure does not move), `8572`, `8598`, `9067`, `9511`, `9659`, `object-view-unmirrored-keys-7779`, `10859-ai-node-zod-arms`. `7917-export-breadcrumb-object-tree-zod-schemas.md` ("107 node component types") was already stale before this diff. A scan of pending entries naming a public-block literal beside `safeValidateSchema` / `objectui validate` / `AnyComponentSchema` found none claiming a refusal. - **Fix round 1's census follows the change, anchor only** (ruling 5861900779 route a): the objectui#9573 alias population loses `page:tabs` because it gained an arm, not because a read was exempted, and `check-handler-key-read-sites.mjs`'s two prose paragraphs that used `page:tabs` as the alias example carry an objectui#10872 amendment. Attribution: the batch-1 dev of `domain:ui` seat 2, session `https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN`. --- _Generated by [Claude Code](https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN)_ --------- Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #8775
Clause-②: no — the ruling records a reason in a test ledger and retracts a teaching line;
PUBLIC_BLOCKS, the manifest and every published type are byte-unchanged (ruling execution parameter 4)Ruling: 5857078807 (B)
Dispatched by the
domain:uiseat 2 (claim 5859939443). Implemented by theos-devsubagent of sessionhttps://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN.What changed
apps/console/src/__tests__/public-contract.test.ts,SECTIONING_TAG_UNRULEDbecomesSECTIONING_TAG_REFUSED, which carries the ruled reason. The rename follows the file's own convention: theaspect-ratioentry beside it opens'RULED: refused on stated merits (objectui#8628, ruling 5634038424, letter B, ratified 5810240972). ', so this one opens'RULED: refused on stated merits (objectui#8775, ruling 5857078807, letter B). '. The ledger docblock no longer says objectui#8775 "holds the decision". Nothing in the tree asserts the ledger's text; the pins over it (population equals ledger keys, a#NNNper entry, more than 40 characters, no stale entry) keep their assertions.skills/objectui/guides/page-builder.md, section "3b. Pick the right layout primitive": thesectionrow is retracted. The prose that saidboxandsectionexist for the same reason now coversboxalone. It points an author who needs a landmark on a JSON page topage:section/page:footer/page:sidebar/page:header, and says what each one renders.content/docs/components/layout/semantic.mdxstops teachingbody?: SchemaNode[]; // Alternative content prop, which objectui#6771 retired. It now states thatchildrenis the one child-list key, as the renderer and the schema read today. Prose only..changeset/8775-sectioning-tags-ruled-reason.md, with empty frontmatter, releases nothing. The presence gate asked for it, becauseapps/console/src/**is released source of@object-ui/console.container-declaration-census.test.tsxis unchanged. Its premise text names neitherSECTIONING_TAG_UNRULEDnorUNCURATED_LAYOUT_CONTAINERSnor objectui#8775 (grep: 0 hits), and it still reads true: "The seven sectioning tags are declared for the html tier and nowhere else".semantic.tsx's registration comment is also unchanged and still true.The reason, sentence by sentence, and the reading behind each one
(a) Zero pull in real apps
The subject grep is a JSON
typeliteral of one of the seven:(type|"type")\s*:\s*["'](article|aside|footer|header|main|nav|section)["']. The control is the same grep shape over each corpus's ordinary layout blocks.examples/atorigin/main4e0f72e8d2(showcase, crm, todo, multi-package, embed)git grepexit 1)box/flex/card: 15 lines, incommand-center.page.ts(8) andstyling-gallery.page.ts(7)2f7b232(depth-1 clone; the same head the ruling read)grid/page:header/page:card: 50 lines in 21 files (hotcrm authors nobox/flex/cardat all, so that control would read 0)examples/outsideexamples/schema-catalogbox/flex/card: 1 (hello-world/schema.json,card)examples/schema-catalogcomponents-layout-semantic/(9 fixtures)components-layout-aspect-ratio/crm-workbench.page.ts(3 lines) andtask-desk.page.ts(1 line) are bothkind: 'react', so those hits are DOM intrinsics. The threekind: 'html'showcase pages (capability-map,command-center-jsx,start-here) use none of the seven.src/is a prose comment inhome.page.ts.(b) The seven are html-tier intrinsics that render on
kind:'html'pagesThis reading comes from a one-off probe, run once under the verify lock and deleted, never committed. It used the full console registration graph, the same imports as
html-tier-code-element-10756.test.tsx.The tier half is re-derived by the census pin "none of the eight is in the curated public contract". The render half is this one-time reading, and the ledger text says so, per AGENTS.md commandment 9.
(c) The curated tier already carries the landmarks, one spelling each
This reading comes from the same probe.
page:headeris the page's title row, and it declares no child slot. The guide therefore says it "takes nochildren" rather than calling it a container.page:footeralso renders a separator above itsfooterelement.EXPECTED_COVEREDin the same test file.(d) Curating any of the seven adds a near-synonym pair
semantic.tsxpassesclassNamethrough verbatim, exactly asboxdoes.classNamepasses through verbatim, exactly likebox".boxwith a different element. For four of them there is also a curatedpage:*block that renders the same element.main,navandarticlehave nopage:*twin. The ledger therefore states the pair throughboxfor all seven, and throughpage:*for four. That is narrower than the first draft of the text, and it is true for all seven.semantic.mdx: what the renderer and the schema read nowThis reading comes from the same probe.
Parameter 6: other teaching of the seven as JSON blocks
The grep is the subject pattern above, over
skills/,content/and.changeset/, plus a backticked`section`inskills/.skills/objectui/guides/page-builder.md: the row and the prose. Corrected here.content/docs/components/layout/semantic.mdx: thetype:union in its schema block. This is the renderer's own reference page, and it stays: the seven still ship and render. Only itsbodyline was corrected, per parameter 3..changeset/: none.report-schema.mdx(type: 'header'is a report-section kind) anduser-state-persistence.md(type:'nav'is a favorite kind) are different vocabularies, not hits.section.skills/objectui/evals/page-builder.jsonmentions "sections" only in a prompt; itsmust_containishidden/admin/card.Skill size readings (
skills/**diff)skills/objectui/guides/page-builder.md: 337 → 342 lines (+5). One table row was removed, and the landmark pointer the ruling asked for was folded into the existingboxparagraph.SKILL.mdunderskills/(1 file): 137 → 137 (unchanged). The wholeskills/tree: 5368 → 5373.check-skill-line-ratchet.mjsscopes it out deliberately).Gates, all on head
91c8cc39a3(the final commit)OS_VERIFY_LOCK_SLOT=issue-8775-dev bash …/os-verify-lock.sh -c 'NODE_OPTIONS=--max-old-space-size=4096 pnpm exec vitest run --maxWorkers=2 apps/console/src/__tests__/public-contract.test.ts packages/components/src/renderers/__tests__/container-declaration-census.test.tsx'gaveTest Files 2 passed (2)andTests 49 passed (49),VERDICT command-exit 0.pnpm check:control-bytes: exit 0,OK (scanned 9086 tracked text file(s); skipped 85 binary). A self-scan of the four files for control bytes found none (grep exit 1).pnpm check:new-line-citations: exit 0,VERDICT new-cross-file-line-citations: 0 new citation(s).pnpm docs:check-links: exit 0,Links are valid across 17 scan roots.pnpm check:skills-paths: exit 0,skills/ — 28/28 resolve across 16 file(s).pnpm check:skill-eval-tokens: exit 0.pnpm check:doc-types: exit 0.pnpm check:doc-fences: exit 0.pnpm check:doc-example-ids: exit 0.pnpm check:doc-example-readers: exit 0.pnpm check:prompt-keys: exit 0.node scripts/check-changeset-presence.mjs: exit 0,1 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s). It was exit 1 before the changeset was added.check:changeset-claims: exit 0..changeset/6475-gantt-block-face-declared.md, which namespage-builder.mdin a sentence aboutganttblocks.gantttext, so that sentence still holds.check:pending-changeset-literals,check-changeset-no-major,check-changeset-overwrite: all exit 0.pnpm exec eslint --no-inline-config --format json apps/console/src/__tests__/public-contract.test.tsgave 1 file, 0 errors, 0 warnings.eslint.config.js's**/*.{ts,tsx}block plus its test override; the file was linted, not ignored.projectService/parserOptions.project(grep count 0), so linting is not type-aware and this diff cannot move any untouched file's verdict..md/.mdx, outside eslint'sfiles.git merge-tree --write-treeagainst freshly fetchedmain4aebea00a7: exit 0, clean treef3a8040fd7. The one commit main gained touches none of these files.git log --format=%Bover the branch shows only the model-free pair (Co-Authored-By: Claude,Claude-Session:), three times, and no card trailer.BASE..HEAD, the three-dot set):node scripts/check-governed-queue-guard.mjs --test PATHS: exit 3, GOVERNED,skills/** x1 — the published skills catalog.node scripts/pm/check-governed-merges.mjs --test PATHS: exit 3, GOVERNED,landing tier: H.check-governed-queue-guard.mjs --testthat the dispatch named exited 1,could not read GITHUB_EVENT_PATH. That copy has no path mode (its seat-side predicate ischeck-governed-merges.mjs --test), so that exit is "could not look", not a verdict.NOT MEASURED, as a declared narrowing:
check:skill-examples,check:doc-snippetsandcheck:doc-examples.PRECONDITION NOT MET: it needs a scoped build of 12 to 34 packages first. CI builds and runs all three.doc-examplesreads JSDoc@exampleblocks underpackages/*/src, and none is touched.doc-snippetscompiles onlyts/tsx/typescriptfences.skill-examplesreads marked fences inskills/.HEAD:page-builder.md: hunks [86], [91–99], against 10 fences, touching none.semantic.mdx: hunks [55], [67–68], touching only theplaintextfence.public-contract.test.ts: no fences.Tier H
skills/**is governed, so this PR stays a draft. The seat handles the at-tier review record, the 终稿速读,needs-user-decision, and the review request to os-zhuang / hotlong. It lands only after an APPROVED review. This dev requested no reviewers and did not ready the PR.Acceptance notes
These were named, not changed: parameter 6 corrects only the files the ruling names.
content/docs/components/navigation/header-bar.mdxauthorstype: 'main'as a JSON block inside an example that also authors the deprecatedtype: 'div'.content/docs/guide/expressions.mduses"type": "section"as the carrier of itshiddenOnexample.page:section/box.SemanticElementSchemainterface docblock inpackages/types/src/layout.tssays the factory "declares exactly one authoring input,className". Since objectui#9910 the registration declares two (className, plus thechildrenslot; probemdx.semantic.inputs). This is a stale comment, not a contract, and it is not touched here.mainlandmark on JSON pages. This is the ruling's own carried confidence gap, and it does not change the letter.维护者速读
article/aside/footer/header/main/nav/section)在控制台的「精选积木」账本里,从「尚未裁决」改为「已裁决不收」,并逐句写明理由。section的那一行,改为指向page:section/page:header/page:footer/page:sidebar。semantic.mdx删掉已退役的body写法。page:*的那句补上各自自带的版式。page:section子项间距space-y-4；page:footer上方加分隔线、行内两端对齐、弱化字色；page:sidebar从md起是固定 20rem 宽的列，不是中性的aside。kind:'html'页面,在那里本来就能渲染。page:*各有一种拼写承载。PUBLIC_BLOCKS、manifest、类型都不动,七个标签照常渲染、照常通过校验。section这一行教学。5860159692)，逐句核对裁决 B 的参数 1–4：账本理由每句为真，PUBLIC_BLOCKS/ manifest / 类型零改动，指南与semantic.mdx与渲染器一致。containers.tsx核对了三处类名)。main(SidebarInset)，所以page:header/page:footer在其中不算页面级 banner / contentinfo 地标。「地标」一词沿用裁决原文，不改结论。skills/**属受管面,需 os-zhuang / hotlong 的 APPROVED 后由席位落地)。Generated by Claude Code