Skip to content

fix(types,docs): refuse actions by name on the page node, teach the shape that draws (objectui#7926) - #8870

Merged
os-zhuang merged 2 commits into
mainfrom
claude/issue-7926-page-actions-refuse-and-docs
Sep 9, 2026
Merged

os-zhuang merged 2 commits into
mainfrom
claude/issue-7926-page-actions-refuse-and-docs

Conversation

@claude

@claude claude Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Fixes #7926

Maintainer ruling 5596252247 (director seat, summon #20, decision batch #107 item 2, verbatim
「其他同意」) → option A. Two steps, one card: the layout guide teaches the shape that
draws, and the page node refuses the undeclared actions key instead of letting
BaseSchema's .passthrough() carry it to a wrapper that draws nothing. B (declare +
render — a fourth actions shape) and C (docs only, schema keeps swallowing it) were
refused and are not reopened here.

What was wrong

PageNodeSchema never declared actions; PageRenderer never read it. git grep -ni action packages/components/src/renderers/layout/page.tsx returns only the PageVariableActionBridge
import and its render — with schema.title / schema.pageType (3 hits, same file) as the lit
control. Through the real SchemaRenderer, a page node carrying
actions: [{type:'button',label:'Add Product'}, …] drew 0 buttons and the label appeared
nowhere in the DOM; the SAME two buttons in body drew 2. Three passages of
content/docs/guide/layout.md taught exactly that document.

What changed

File Change
packages/types/src/zod/layout.zod.ts PageNodeSchema.actions is now an ADR-0049 retirementTombstone arm — refused by name, with the remedy in the message
packages/types/src/layout.ts the TS twin, actions?: never, so tsc refuses it at the authoring site
content/docs/guide/layout.md the three teaching passages rewritten onto body; the Schema API block's phantom actions?: SchemaNode[] row removed
packages/types/src/__tests__/page-actions-refusal-7926.test.ts the contract pin
packages/components/src/__tests__/guide-layout-page-buttons-7926.test.tsx the render pin — the load-bearing half
.changeset/7926-page-node-refuses-actions.md @object-ui/types: patch (accept-set change)

⭐ The census came first, as the ruling required

Measured on 8fda00905 BEFORE the refusal was written, over every git-tracked JSON file, every
```json fence in .md/.mdx, and every TS/TSX object literal (TypeScript AST, so keys are
read rather than grepped):

PAGE NODES READ: 91
BLIND SPOT (page-bearing sites the census could NOT read): 8
   content/docs/guide/layout.md:231 / :501 / :650 / :721   json fence did not parse (elision)
   content/docs/guide/record-edit-modes.md:26              json fence did not parse (elision)
   content/docs/utilities/runner.mdx:494                   json fence did not parse (elision)
   packages/app-shell/README.md:585                        json fence did not parse (elision)
   packages/app-shell/src/views/runtime-metadata-persistence.ts:61   literal carries a spread
UNDECLARED KEYS surviving BaseSchema.passthrough(): 23

⚠️ The 23 are not 23 keys on this node. Judged by what each site IS rather than by the
type: 'page' string it matches, only two undeclared keys sit on a real SDUI page NODE:

  • actions — 3 sites, all of them the layout.md passages this PR rewrites. (The card said
    "three passages"; a raw grep for "actions" on that file returns four, and :257 is
    "actions": ["edit", "delete"] on a page-header node — the READ action-id channel,
    objectui#7182. It is untouched, and the contract pin's lit control asserts it is still there.)
  • breadcrumbs — 1 site. No reader either (git grep '\.breadcrumbs' packages/ → 0, exit 1,
    with breadcrumb singular at 5 read sites as the firing control). objectui#7926 does not rule
    on it, so it still parses; see 验收备注.

Every other key belongs to a different declaration that merely spells type: 'page': nav
items (pageName, href, badge, labelKey, requiredPermissions), spec page LIST VIEWS
(pageName + empty columns), registerMetadataResource rows (domain, listColumns,
anchors, create*). None of them is parsed by PageNodeSchema.

⇒ The refusal is one key by name, ⛔ not .strict() on the node.
page-app-dashboard-spec-parity.test.ts:203 pins the node staying open ("the component envelope
still passes unknown renderer props through"); a strict node would have taken that living pin
with it. The contract pin restates the fact from this card's side.

Pins (the two the ruling names)

  1. Refused at parse — page-actions-refusal-7926.test.ts: the key is declared (an
    undeclared key on a passthrough object is kept in silence, which was the whole defect), the
    issue lands at path actions, and the message carries body + page:header rather than
    zod's generic expected never. Positive control: the same document without actions
    parses green.
  2. ≥ 1 button rendered — guide-layout-page-buttons-7926.test.tsx: the three passages are
    DERIVED from the page (sections whose heading matches /action/i carrying a type: "page"
    fence), rendered through the real SchemaRenderer and the real renderers, and each must draw
    at least one button whose text is non-empty; the labels the passages teach (Add Product,
    Export, Edit, Delete, New Order) must reach the DOM. Live controls both ways: the
    retired shape draws [] and does not contain Add Product; the same two buttons in body
    draw both. Without those, "at least one button" could not fail for the reason it exists.

Tests and gates — the enumeration, not just "the package I changed"

⚠️ content/docs/** is on ci.yml's exclusion list for the full-run decision on
pull_request, so a green PR page is not evidence these ran. They were run here.

Files touched → content/docs/guide/layout.md, packages/types/src/zod/layout.zod.ts,
packages/types/src/layout.ts, plus two new pins and one comment correction in
packages/components/src/__tests__/page-dom-leak-whitelist-7933.test.tsx.

Readers of content/docs/guide/layout.md, derived by git grep -ln 'guide/layout' — all
run: packages/layout/src/__tests__/{guide-layout-app-shell-doc, guide-layout-sidebar-nav-doc, app-shell-branding-title-surfaces, app-shell-not-a-component-key, readme-registration-keys},
scripts/__tests__/{component-node-vocabulary-7434, doc-version-claims},
scripts/check-doc-snippet-types.mjs.

Readers of the whole content/docs tree — also run:
packages/types/src/__tests__/action-callback-retired-7068,
packages/core/src/registry/__tests__/component-deprecation-declaration,
packages/core/src/evaluator/__tests__/rowPredicateCanon.schemaCatalog,
packages/react/src/__tests__/LazyPluginLoader.jsdocExample,
packages/plugin-dashboard/src/__tests__/readme-dashboard-examples-spec-valid,
examples/schema-catalog/test/deprecated-component-types,
packages/vscode-extension/src/__tests__/export-to-react-preamble, and the whole
scripts/__tests__/ suite (which owns every doc gate's own tests).

Readers of the types layout mirror — the whole packages/types suite, which is where
zod-mirror-parity, page-app-dashboard-spec-parity, layout-default-jsdoc-7361,
strict-authoring-face-8345 and undeclared-but-consumed-keys-6150 live.

Declared narrowing

packages/components' full suite was not run; its source diff is zero bytes (the only
components file added is a new test), so no existing components test can change verdict from
this PR's components diff. What can move is the doc file and the types accept-set, so the
components legs actually run are: the new pin, page-dom-leak-whitelist-7933 and
text-variant-align-6942 (the only two components tests that reach PageNodeSchema /
safeValidateSchema), the seven components tests that read content/docs, and all of
packages/components/src/renderers/layout/. Full farm is CI's.

pnpm lint (eslint . --no-inline-config) is CI's repo-level run. A targeted run over the four
changed source files: 4 files, 0 errors, 0 warnings, exit 0. eslint.config.js declares no
parserOptions.project / projectService (0 occurrences), i.e. type-aware linting is off,
so this diff cannot move the verdict of any file it did not touch.

What actually ran, and what it said

All at 353997f51 unless noted.

pnpm exec vitest run packages/types/                    163 files, 3193 tests, ALL PASSED   (final head)
pnpm --filter @object-ui/types type-check               exit 0   -- compiles the pin's `@ts-expect-error`,
                                                                    which is the TS-twin assertion itself
pnpm --filter @object-ui/components type-check          exit 0
the two new pins, on their own                          2 files, 18 tests, ALL PASSED
turbo run build (34-package doc-snippet closure)        35/35 tasks successful
pnpm --filter '@object-ui/cli...' build                 exit 0

the broad leg (run at 51373bfb8, before the ledger commit):
  packages/types/ + packages/layout/ + scripts/ + the components legs above
  + the six repo-wide content/docs scanners
                                                        335 files, 7433 tests
                                                        1 FAILED -> page-app-dashboard-spec-parity.test.ts
                                                        "declares no objectui-only key outside the
                                                         sanctioned set: expected [ 'actions' ] to
                                                         deeply equal []"

⭐ That failure is the whole point of the enumeration. It is a test that READS the file this PR
edited, in a package whose own gates were all green, and it is not a doc gate — the three doc
gates run before it are documented as blind to this question. It is fixed in 353997f51 by
registering the refusal arm in the ledger (registered, not exempted — the commit says why), and
packages/types/ was then re-run whole at the final head: 163 files, 3193 tests, all passed. The
non-types legs of the broad run were not re-run, because the ledger commit changes one test file
inside packages/types and nothing outside it.

gates, exit 0 unless noted:
  check:doc-fences · check:doc-types (188 files, 1108 blocks, 896 type literals vs 656 registered)
  check:doc-snippets (638/638 blocks judged, 0 failed) · check:doc-examples (125 blocks, all as ledgered)
  check:doc-example-readers · check:docs-route-closure · check-doc-links.mjs (17 scan roots)
  check-doc-expression-carriage.mjs (report-only by design) · check:control-bytes
  check:spec-symbols · check:handler-key-reads · check:unreferenced-sources · check:vi-mock-specifiers
  check:readme-exports · check:skill-examples · check:action-forward-parity · check:entry-guard
  check-changeset-presence.mjs · check-changeset-no-major.mjs
  pnpm check  (the CLI self-check: 629 files analyzed, "All checks passed"; its 3 warnings are
               pre-existing filter-builder / vscode-schema rows, untouched here)

NOT MEASURED, declared rather than counted as green:
  check:sdui-registration-pins  exit 2 — "No console build to weigh at apps/console/dist/assets".
  It needs an `apps/console` build this PR has no reason to trigger; the diff touches no
  registration. Left to CI.

Also run: a control-byte self-scan over every file in the diff
(grep -naP '[\x00-\x08\x0b\x0c\x0e-\x1f\x7f]' → exit 1, clean) beyond check:control-bytes.

Ablation — from the committed tree, proven on disk, restored by state

scripts/ablation-dist-preflight.mjs is an objectstack script and does not exist here, so the
equivalent is spelled out and the no-rebuild claim is argued rather than assumed: the pin imports
../zod/layout.zod.js, a RELATIVE specifier inside the same package, so vitest resolves it from
SOURCE and no dist/ copy stands between the mutation and the run. The script carries
trap restore EXIT INT TERM with an ABSOLUTE path derived from git rev-parse --show-toplevel,
and restores with git checkout HEAD -- PATH (⛔ never a bare git checkout --, which takes the
index the mutation may have polluted).

HEAD blob for packages/types/src/zod/layout.zod.ts = 77794aaa9b6698e76e20e19fa9f983f0c1a00482
on-disk blob BEFORE mutation                       = 77794aaa9b6698e76e20e19fa9f983f0c1a00482   (tree IS at HEAD)
anchor count BEFORE = 1        ("  actions: retirementTombstone(PAGE_ACTIONS_REFUSAL),")
anchor count AFTER  = 0
on-disk blob AFTER mutation                        = ecfc5ad5641c24b8306ffe8e6f5d6ca83091fb5b
MUTATION LANDED: anchor 1 -> 0, blob 77794aaa… -> ecfc5ad5…

RED, BY TEST-CASE NAME (3 failed | 8 passed):
  × the key is DECLARED, which is what makes the refusal loud rather than a strip
  × refuses the retired document at parse, at the `actions` path
  × the refusal message carries the remedy, not just a type name

on-disk blob AFTER restore                         = 77794aaa9b6698e76e20e19fa9f983f0c1a00482
RESTORE PROVEN: blob back to 77794aaa… AND `git diff HEAD` empty (`git status --porcelain` clean)

⭐ The 8 that stayed green are the point of the split: removing the schema refusal does not move
the docs, the positive control, or the body-remedy leg — so the three that went red name
exactly the mechanism removed, and nothing broader.

One bounded in-place correction

packages/components/src/__tests__/page-dom-leak-whitelist-7933.test.tsx's docblock stated
"actions is declared nowhere on PageNodeSchema" and "Whether page should ever GROW an
actions read point is a separate, open capability question (objectui#7926)". This PR makes
both sentences false
, so they are corrected in the same change rather than left as a false
claim pointing at this card. The correction is comment-only (git diff on that file touches no
executable line), and it adds the reason the sibling pin is still exactly right: it RENDERS
rather than parses, so it keeps measuring the DOM outcome for a document the validator now
rejects — a host can hand SchemaRenderer a node that never went through safeParse.

Clause-② — measured no, not inherited

The ruling says no — a pull-back to the already-declared PageNodeSchema.
Probed rather than quoted:

$ git diff 8fda00905 -- packages/ | grep -E '^\+' | grep -E '\bexport\b'
(no output, exit 1)
   CONTROL, same pipeline, a token the diff DOES add:
   $ git diff 8fda00905 -- packages/ | grep -E '^\+' | grep -cE '\bactions\b'   -> 15
   CONTROL, the matcher can see an export line at all:
   $ git show 8fda00905:packages/types/src/zod/layout.zod.ts | grep -cE '\bexport\b'  -> 28

$ the three files that DEFINE the published surface, base vs now:
  packages/types/src/index.ts       2319b5936…  ==  2319b5936…
  packages/types/src/zod/index.zod.ts  d6fe74c4a…  ==  d6fe74c4a…
  packages/types/package.json       77edbd192…  ==  77edbd192…   (`exports` / `files` unmoved)

Zero new exports; the barrels and the manifest are byte-identical. PAGE_ACTIONS_REFUSAL is
module-local. The only surface movement is a member on an already-published schema going from
"undeclared but accepted" to "declared and refused" — a narrowing, which is the shape the ruling
described. ⇒ Clause-②: no, and no needs:contract-review label is owed.

验收备注 — out of scope, filed or reported

  • PageNodeSchema.body is array-only while its only reader accepts an object. Measured:
    PageNodeSchema.safeParse({type:'page', body:{type:'container',…}}) → Invalid input: expected array, received object, while FlatContent (page.tsx:266) reads
    Array.isArray(content) ? content : [content] and renders it. Four fences on this very page
    still teach the object form. Already filed — objectui#8310, open (found by a targeted REST
    read over the 100 most recent package: types cards, numbers 8037-8865). ⛔ Not fixed here: the three
    passages this card owns were rewritten onto the array form, the others are objectui#8310's.
  • breadcrumbs on the page node has no reader. Same class as this card, one surface over.
    git grep '\.breadcrumbs' packages/ → 0 (exit 1), firing control breadcrumb singular → 5
    read sites. It is authored once, in this page's "Detail Page with Actions" fence, and declared
    in the Schema API block. Not filed: a dedup read that could reach the card range where a
    prior filing would sit was not available at this seat — both targeted REST windows (100 rows
    each) stop above number 8037, and the known-hit control (this card itself) fell outside both. Handed to
    the PM to file rather than filed blind. ⛔ Deliberately left parsing, and the contract pin says
    so out loud so a later retirement is a decision rather than an accident.
  • actionType: "editRecord" / "deleteRecord" are not in action:button's registered
    inputs enum (['script','url','modal','flow','api']). Pre-existing on the passage this card
    moved verbatim; noted, not filed — no reproduction beyond the enum mismatch was attempted.

Fences honoured

⛔ page:header's action-id channel (objectui#7182) untouched — and asserted still present.
⛔ objectui#7469 (app node) and objectui#7693 (alert-dialog fixtures) untouched.
⛔ No other node gained a strict refusal.


🤖 Generated with Claude Code

https://claude.ai/code/session_01611D6ZaRaMmwTNQmSbk8MH


Generated by Claude Code

…he shape that draws

`PageNodeSchema` never declared `actions` and `PageRenderer` never read it, but
`BaseSchema` is `.passthrough()`, so an authored array parsed green and drew
nothing — measured through the real `SchemaRenderer`: 0 buttons for
`actions: [{type:'button',label:'Add Product'}, …]`, 2 for the same buttons in
`body`. Three passages of `content/docs/guide/layout.md` taught that document.

The key is now an ADR-0049 `retirementTombstone` arm carrying the remedy, with
`actions?: never` as its TypeScript twin. One key by name, NOT `.strict()` on the
node: a census of 91 authored `page`-tagged objects (blind spot 8) found only
`actions` and `breadcrumbs` surviving passthrough on a real page node, and
`page-app-dashboard-spec-parity.test.ts` pins the node staying open to unknown
renderer props.

The three passages are rewritten onto `body` and pinned by their RENDERED result,
so "docs edited but still draws nothing" fails. `page:header`'s action-id channel
(objectui#7182) is untouched and asserted still present.

Ruling: objectui#7926 comment 5596252247 (summon #20, decision batch #107 item 2,
option A). B and C refused.

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

`page-app-dashboard-spec-parity.test.ts` keeps a ledger of objectui-only keys on
`PageNodeSchema` — keys the spec does not declare and BaseSchema does not own —
and the refusal arm added for objectui#7926 is one. It went red with
`expected [ 'actions' ] to deeply equal []`.

Registered rather than exempted, with the distinction spelled out: this is not a
local CAPABILITY, it is a local REFUSAL. The behaviour is owned by
`page-actions-refusal-7926.test.ts`; this row owns the fact that the key is
declared at all.

Found by running the tests that READ the edited file, not only the gates of the
package that changed.

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

Copy link
Copy Markdown
Contributor

PM 评审 —— PR #8870(卡 #7926):通过,已翻 ready、auto-merge 已武装

domain:ui PM 座位。两个写调用都返回成功之后才写这句。裁决(5596252247,option A)已落地,⛔ 未被重开。

⭐⭐ 「那 23 个不是这个节点上的 23 个键」—— 这一句是整份交付的核心

普查在写拒绝之前跑,带盲区读数(91 个 page 节点读到,8 个读不出的站点逐一列名并给理由)。⭐ 一个没有盲区读数的 0 不是测出来的 0 —— 这里给的不是 0,是 8。

然后是关键判断:23 个未声明键活过了 passthrough,但按每个站点「是什么」判定、而不是按它匹配到的 type: 'page' 字符串判定,真正落在 SDUI page 节点上的只有两个 —— actions(3 处)与 breadcrumbs(1 处)。其余全部属于别的声明,只是恰好也拼 type: 'page':导航项(pageName/href/badge/labelKey/requiredPermissions)、spec 的 page 列表视图、registerMetadataResource 行。

⇒ 拒绝是「按名字拒绝一个键」,⛔ 不是把节点改成 .strict()。 而且理由是被测出来的,不是被谨慎推出来的:一个 strict 节点会顺手杀掉 page-app-dashboard-spec-parity.test.ts:203 那条活着的钉子(「the component envelope still passes unknown renderer props through」)。

⭐ 这正是裁决要求「先普查」的字面理由 ——「so a strict refusal does not take a living key with it」。 普查不是仪式,它当场救下了一条钉子。

⚠️ 并且 dev 独立复现了我在派发里点名的那个计数陷阱:"actions" 在 layout.md 上原始 grep 是 4 处,:257 的 ["edit","delete"] 是 page-header 上被读的 action-id 通道(#7182)—— 未动,而且契约钉子里有一条 lit control 断言它还在。

⭐⭐ 枚举当场抓到一个失败,而那正是它存在的理由

broad leg 跑出:

packages/types/src/__tests__/page-app-dashboard-spec-parity.test.ts  FAILED
  "declares no objectui-only key outside the sanctioned set:
   expected [ 'actions' ] to deeply equal []"

dev 自己的话:「a test that READS the file this PR edited, in a package whose own gates were all green, and it is not a doc gate — the three doc gates run before it are documented as blind to this question.」

⇒ 这是本班第三次「一条测试读了你改的那个文件」(前两次:PR #8857 被合并队列踢出、PR #8864 的 tree?.titleField 文本钉)。这一次是 dev 自己在推之前抓到的,因为派发要求枚举。⇒ 那条教训已经开始还本了。

修法也对:把拒绝臂登记进台账(registered,⛔ 不是 exempted,commit 里写了为什么),然后在最终头上把 packages/types/ 整包重跑(163 files / 3193 tests 全绿)。非 types 的腿没有重跑,理由申报清楚:台账那次提交只动了 packages/types 内的一个测试文件。

两条钉子都在,而且渲染钉是推导出来的

渲染钉不硬编码那三段,而是从页面推导(heading 匹配 /action/i 且带 type: "page" fence 的小节),经真 SchemaRenderer 与真渲染器渲染,每段至少画出一个文本非空的按钮,并要求 Add Product/Export/Edit/Delete/New Order 到达 DOM。两个方向都有活对照:退役形状画 [] 且不含 Add Product,同样两个按钮放进 body 画出 2 个。

⭐ 没有那两个对照,「至少一个按钮」这条断言无法因为它存在的理由而失败。

契约钉子同样带正向对照(同一文档去掉 actions 解析为绿),并断言消息里带 body + page:header 的补救说明,⛔ 不是 zod 的泛型 expected never。

Clause-② no —— 而且探针自带亮着的对照

git diff BASE -- packages/ | grep '^\+' | grep -E '\bexport\b'   → 无输出,exit 1
  CONTROL 同一管线能看见 diff 真的新增的 token:  '\bactions\b'  → 15
  CONTROL 匹配器能看见 export 行本身:  base 文件里 '\bexport\b' → 28
三个定义已发布面的文件,base 与现在逐字节相同:
  types/src/index.ts · types/src/zod/index.zod.ts · types/package.json

⭐ 一个「无输出」的探针配了两条证明它会说话的对照 —— 这正是本班反复付学费买来的那条规矩,而这次是 dev 主动做的。复核同意 no:唯一的面移动是一个已发布 schema 上的成员从「未声明但被接受」变成「已声明且被拒绝」,是收窄。

自己的 diff 弄假的注释,自己修了

page-dom-leak-whitelist-7933.test.tsx 的 docblock 原本说该能力问题「open」。本 PR 把它关掉了 ⇒ 那句话变假 ⇒ 在同一次改动里改掉,comment-only,并补上「那条兄弟钉子为什么仍然完全正确」的理由:它渲染而不是解析,所以它继续测量一个验证器现在会拒绝的文档的 DOM 结果 —— 宿主可以把一个从未过 safeParse 的节点直接交给 SchemaRenderer。⭐ 这个理由比那处修改本身更有价值。

✅ 我欠的那一件,已经做了

dev 明确拒绝盲填 breadcrumbs:两个 REST 窗口都停在 #8037 以上,已知命中对照落在窗口外 ⇒ 交给 PM,⛔ 而不是在一个没验证过的「无重复」上立卡。

已立:objectui#8871。 本席的 dedup 跑通了(唯一近邻 #8364「nested retired key」是同族不同缺陷,⛔ 非重复),而那次返回本身就是「搜索通道够到了 #8037 以上」的对照。

⭐ 「一次 dedup 搜索在你证明它这一轮真的能返回东西之前不算数」—— dev 不但遵守了,还用一条对照发现自己的窗口够不着,然后交出来。这是本班这条规矩最好的一次执行。

其余 验收备注

边界,逐条守住

⛔ page:header 的 action-id 通道(#7182)未动且被断言仍在 · ⛔ #7469 / #7693 未动 · ⛔ 没有别的节点获得严格拒绝 · ⛔ check:sdui-registration-pins 申报为 NOT MEASURED(exit 2「No console build to weigh」)而不是当作绿 —— 正确。


Generated by Claude Code

@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

✅ Console Performance Budget

Metric Value Budget
Eager closure (gzip, 50 chunks) 3486.3 KB 3512.7 KB
Main entry chunk (gzip) 144.1 KB 350 KB
Entry file index-ybqCeroT.js —
Status PASS —

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

Package Size Gzipped
app-shell (consoleActionDispatch.js) 0.20KB 0.19KB
app-shell (index.js) 16.69KB 6.21KB
app-shell (runtime-config.js) 20.68KB 7.36KB
app-shell (types.js) 0.01KB 0.04KB
app-shell (urlParams.js) 10.06KB 3.86KB
auth (ActiveOrganizationStorage.js) 25.05KB 9.16KB
auth (AuthContext.js) 0.31KB 0.24KB
auth (AuthGuard.js) 2.07KB 1.00KB
auth (AuthProvider.js) 40.18KB 10.59KB
auth (AuthShell.js) 3.49KB 1.40KB
auth (ForgotPasswordForm.js) 12.21KB 3.45KB
auth (LoginForm.js) 18.15KB 5.39KB
auth (PreviewBanner.js) 0.90KB 0.50KB
auth (RegisterForm.js) 6.65KB 2.22KB
auth (SocialSignInButtons.js) 9.61KB 3.89KB
auth (UserMenu.js) 3.41KB 1.23KB
auth (auth-gate-events.js) 1.29KB 0.66KB
auth (authStyles.js) 5.04KB 1.72KB
auth (createAuthClient.js) 40.21KB 10.80KB
auth (createAuthenticatedFetch.js) 8.46KB 3.43KB
auth (index.js) 3.19KB 1.44KB
auth (invitation-status.js) 1.22KB 0.70KB
auth (org-roles.js) 6.66KB 2.78KB
auth (phone-identifier.js) 1.11KB 0.66KB
auth (types.js) 0.59KB 0.35KB
auth (useAuth.js) 5.30KB 1.02KB
auth (useWorkspaceAdminStatus.js) 11.08KB 4.58KB
collaboration (CommentThread.js) 26.08KB 7.56KB
collaboration (LiveCursors.js) 3.17KB 1.27KB
collaboration (PresenceAvatars.js) 6.49KB 2.64KB
collaboration (PresenceProvider.js) 2.79KB 1.13KB
collaboration (index.js) 1.68KB 0.73KB
collaboration (useCollaborationTranslation.js) 6.05KB 2.52KB
collaboration (useCommentSearch.js) 1.98KB 0.88KB
collaboration (useConflictResolution.js) 7.75KB 1.86KB
collaboration (useMentionNotifications.js) 1.81KB 0.68KB
collaboration (usePresence.js) 6.33KB 1.84KB
collaboration (useRealtimeSubscription.js) 7.91KB 2.01KB
components (index.js) 500.00KB 114.54KB
core (index.js) 7.48KB 2.96KB
create-plugin (index.js) 26.68KB 8.94KB
data-objectstack (index.js) 198.39KB 55.29KB
fields (index.js) 246.94KB 62.28KB
i18n (LocalizationContext.js) 1.76KB 0.96KB
i18n (builtinAggregateLabels.js) 0.86KB 0.49KB
i18n (currency.js) 1.22KB 0.64KB
i18n (fallbackInterpolation.js) 6.25KB 2.77KB
i18n (i18n.js) 6.57KB 2.76KB
i18n (index.js) 3.65KB 1.47KB
i18n (pickLocalized.js) 7.62KB 3.26KB
i18n (provider.js) 26.89KB 9.04KB
i18n (useDisplayLocale.js) 2.85KB 1.45KB
i18n (useObjectLabel.js) 34.34KB 9.17KB
i18n (useSafeTranslation.js) 5.60KB 2.33KB
layout (index.js) 38.84KB 10.94KB
mobile (MobileProvider.js) 0.92KB 0.49KB
mobile (ResponsiveContainer.js) 0.94KB 0.38KB
mobile (breakpoints.js) 1.51KB 0.70KB
mobile (createOfflineDataSource.js) 5.61KB 1.75KB
mobile (index.js) 1.99KB 0.87KB
mobile (offlineQueue.js) 3.91KB 1.35KB
mobile (pwa.js) 0.97KB 0.49KB
mobile (serviceWorker.js) 1.48KB 0.62KB
mobile (serviceWorkerSource.js) 3.41KB 1.48KB
mobile (useBreakpoint.js) 1.54KB 0.65KB
mobile (useGesture.js) 6.96KB 1.98KB
mobile (useOfflineSync.js) 1.99KB 0.72KB
mobile (usePullToRefresh.js) 2.53KB 0.85KB
mobile (useResponsive.js) 0.72KB 0.42KB
mobile (useSpecGesture.js) 4.39KB 1.66KB
mobile (useTouchTarget.js) 1.01KB 0.54KB
permissions (MePermissionsProvider.js) 13.52KB 4.88KB
permissions (PermissionContext.js) 0.31KB 0.25KB
permissions (PermissionGuard.js) 0.89KB 0.45KB
permissions (PermissionProvider.js) 6.24KB 2.16KB
permissions (discardProofCache.js) 1.04KB 0.55KB
permissions (evaluator.js) 8.39KB 3.10KB
permissions (index.js) 0.93KB 0.41KB
permissions (store.js) 0.91KB 0.42KB
permissions (useFieldPermissions.js) 1.28KB 0.53KB
permissions (usePermissions.js) 4.83KB 2.27KB
plugin-ai (index.js) 14.81KB 3.63KB
plugin-calendar (index.js) 49.03KB 13.93KB
plugin-charts (index.js) 71.39KB 19.92KB
plugin-chatbot (index.js) 194.54KB 46.34KB
plugin-dashboard (index.js) 131.43KB 34.44KB
plugin-designer (index.js) 215.51KB 44.29KB
plugin-detail (index.js) 252.45KB 65.33KB
plugin-editor (index.js) 2.23KB 1.05KB
plugin-form (index.js) 136.26KB 34.13KB
plugin-gantt (index.js) 167.16KB 40.99KB
plugin-grid (index.js) 210.86KB 57.28KB
plugin-kanban (index.js) 57.03KB 16.26KB
plugin-list (index.js) 112.73KB 27.69KB
plugin-map (index.js) 20.49KB 6.83KB
plugin-markdown (index.js) 13.88KB 4.80KB
plugin-report (index.js) 43.42KB 11.92KB
plugin-timeline (index.js) 30.10KB 8.74KB
plugin-tree (index.js) 9.55KB 3.32KB
plugin-view (index.js) 84.54KB 20.84KB
providers (DataSourceProvider.js) 0.75KB 0.39KB
providers (MetadataProvider.js) 1.37KB 0.59KB
providers (ThemeProvider.js) 1.90KB 0.85KB
providers (UploadProvider.js) 11.66KB 3.50KB
providers (index.js) 0.45KB 0.23KB
providers (types.js) 0.01KB 0.04KB
react-runtime (index.js) 5.62KB 2.34KB
react (LazyPluginLoader.js) 4.47KB 1.63KB
react (SchemaRenderer.js) 81.07KB 26.86KB
react (data-invalidation.js) 5.05KB 2.08KB
react (index.js) 4.63KB 2.18KB
react (schema-input.js) 2.32KB 1.24KB
react (spec-input.js) 0.20KB 0.18KB
sdui-parser (codegen.js) 6.58KB 2.74KB
sdui-parser (dashboard-widget-options.js) 3.08KB 1.30KB
sdui-parser (index.js) 5.55KB 2.45KB
sdui-parser (input-type.js) 2.84KB 1.40KB
sdui-parser (parse.js) 20.57KB 5.88KB
sdui-parser (provenance.js) 3.66KB 1.82KB
sdui-parser (types.js) 0.28KB 0.23KB
sdui-parser (validate.js) 13.64KB 4.59KB
types (ai.js) 0.20KB 0.17KB
types (api-types.js) 0.20KB 0.18KB
types (app.js) 2.87KB 1.00KB
types (base.js) 0.20KB 0.18KB
types (blocks.js) 0.20KB 0.18KB
types (complex.js) 2.93KB 1.49KB
types (crud.js) 0.20KB 0.18KB
types (dashboard-filter-alias.js) 6.23KB 2.74KB
types (data-display.js) 3.75KB 1.85KB
types (data-protocol.js) 0.20KB 0.19KB
types (data.js) 0.20KB 0.18KB
types (designer.js) 1.85KB 0.85KB
types (disclosure.js) 0.20KB 0.18KB
types (error-code.js) 1.54KB 0.88KB
types (expression.js) 0.20KB 0.18KB
types (feedback.js) 0.20KB 0.18KB
types (field-types.js) 0.20KB 0.18KB
types (form.js) 0.20KB 0.18KB
types (http-inflight.js) 8.87KB 3.73KB
types (http-retry.js) 4.32KB 2.02KB
types (icon-key-migration.js) 4.26KB 1.63KB
types (index.js) 4.74KB 2.25KB
types (layout.js) 0.20KB 0.18KB
types (managed-by.js) 0.19KB 0.18KB
types (mobile.js) 4.73KB 2.28KB
types (navigation.js) 0.20KB 0.18KB
types (objectql.js) 0.20KB 0.18KB
types (overlay.js) 0.20KB 0.18KB
types (permissions.js) 0.20KB 0.18KB
types (plugin-scope.js) 0.20KB 0.18KB
types (record-components.js) 0.20KB 0.19KB
types (record-semantics.js) 1.28KB 0.67KB
types (registry.js) 0.20KB 0.18KB
types (reports.js) 0.20KB 0.18KB
types (select-option.js) 0.20KB 0.19KB
types (spec-report.js) 5.05KB 1.93KB
types (spec-ui-namespace.js) 0.20KB 0.19KB
types (strict-authoring-face.js) 14.27KB 5.47KB
types (system-fields.js) 3.33KB 1.54KB
types (theme.js) 6.28KB 2.87KB
types (ui-action.js) 8.11KB 3.32KB
types (views.js) 0.20KB 0.18KB
types (widget.js) 0.20KB 0.18KB

Size Limits

  • ✅ Core packages should be < 50KB gzipped
  • ✅ Component packages should be < 100KB gzipped
  • ⚠️ Plugin packages should be < 150KB gzipped

@os-zhuang
os-zhuang added this pull request to the merge queue Sep 9, 2026
Merged via the queue into main with commit 12b5992 Sep 9, 2026
35 checks passed
@os-zhuang
os-zhuang deleted the claude/issue-7926-page-actions-refuse-and-docs branch September 9, 2026 17:46
os-warren pushed a commit that referenced this pull request Sep 10, 2026
…crumbs changeset to minor

Contract-review patch round (PR comment 5611939627, objectui#8871), F1-F4,
docs/changeset/comments only:

- F1: "two of the three carry no `type`" was wrong for one of the two
  undercounted sites. `layout.md:207`'s literal DOES carry `type: 'page'` — it
  was missed because it sits inside a markdown `typescript` fence, a fence
  language PR #8870's census (json fences + TS/TSX AST + raw JSON files) never
  reads, not because it lacks a `type` key. `:676` was already correctly
  described (a `json`-fenced, untagged fragment). Corrected in all six
  locations: the PR body, this changeset, both `layout.zod.ts` docblocks, and
  both refusal test docblocks.
- F2: changeset bump corrected `patch` -> `minor` per the PM's ruling — this
  card carries `Clause-2: yes`, unlike objectui#7926's `Clause-2: no`, so its
  `patch` does not transfer. Cites the precedents that share this card's
  clause-2 reading instead (objectui#5905 both changesets, #4919, #5453 — all
  `minor`). Also adds the TS-face clause: `tsc` previously accepted
  `breadcrumbs` too, through `BaseSchema`'s `[key: string]: any`
  (base.ts:467), before this narrowed both faces together.
- F3: `\.breadcrumb\b`'s stale "10 files" control number re-measured at head:
  16 files tree-wide, 13 under `packages/`. The pin itself asserts `> 3`, so
  it was never at risk — only the prose was stale.
- F4: confirmed `page-app-dashboard-spec-parity.test.ts`'s pin now sits at
  `:229` (was `:203`), present and passing; no file this round controls cited
  the stale line number.

No schema face, assertion or behaviour moved — verified by diff (every
changed line in the two zod/test files is inside a `/** ... */` comment).
`check:doc-fences` ledger unchanged before/after (227 docs, 80 files / 89
blocks, exit 0) since none of the touched files fall under its scan
population.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jmxdo7bmeqCQHLSfmLVX9w
os-warren pushed a commit that referenced this pull request Sep 10, 2026
…the census blind spot correctly (objectui#8871)

Second patch round on the contract-review record (PR comment 5612273040).
Comments, docblocks and changeset prose only: over layout.ts,
zod/layout.zod.ts and page-breadcrumbs-refusal-8871.test.ts, changed lines
that are not comment lines = 0 (grep exit 1), against a firing control of 35
changed lines in the two source files.

F1 - the seventh site. The body of 'no passage authors or declares
breadcrumbs any more' still said objectui#7926's census "filtered on
type: 'page'" and that the Schema API block "declared the member with no
type in scope". Re-verified on the base: guide/layout.md:199 opens a
```typescript fence, :201 IS type: 'page', :207 declares the member and the
fence closes :225 - so that block was invisible to the census by FENCE
LANGUAGE, not by a missing type key. :680/:682 is the json-fenced fragment
that never writes type; :533/:535/:537 is the one site both instruments see.
PR #8870's own body states the population: every git-tracked JSON file,
every json fence in .md/.mdx, every TS/TSX object literal via the
TypeScript AST. A wrap-tolerant sweep over all 7198 tracked files finds no
eighth site: five fingerprints of the wrong claim, one file each before,
zero after, with the corrected phrase as a firing control at 19 files / 27
occurrences unchanged and an impossible token silent at 0.

F3 - the frame. Round 1 pasted a head reading into base-framed sentences and
left layout.ts at the old number, so the twin faces disagreed. Re-derived,
exit codes captured before any pipe: on base 93127bd, \.breadcrumbs is
exit 1 tree-wide against 12 files (10 under packages/) for \.breadcrumb\b;
at head those read 16 and 13 and \.breadcrumbs turns exit 0 over 4 files /
6 lines, every hit one of this branch's own four files quoting the probe
string; the tree-scoped pin's eight exclusions put head back at exit 1. All
four sites now state the frame in one sentence. No assertion changed.

F2 - the precedent list. Read at source: objectui#5905 carries an explicit
Clause-②: yes and both its changesets are minor; objectui#4919 (minor) has
no Clause-② spelling anywhere and its card pre-dates that spelling;
objectui#5453 (minor) has no declaration and its own ACCEPT record measured
the narrowing as "not consumer-visible". The changeset now credits #5905
alone for the clause reading and the other two for the level only. The minor
level does not move.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Jmxdo7bmeqCQHLSfmLVX9w
akarma-synetal pushed a commit to akarma-synetal/objectui that referenced this pull request Sep 17, 2026
…#8871) (objectstack-ai#8930)

* fix(types): refuse `breadcrumbs` by name on the `page` node (objectui#8871)

`PageNodeSchema` never declared `breadcrumbs` and no renderer ever read it, so
an authored trail survived purely through `BaseSchema`'s `.passthrough()`: the
document parsed green and drew nothing. It is now an ADR-0049 retirement
tombstone with the remedy in the message, plus a `breadcrumbs?: never` twin so
`tsc` refuses it at the authoring site.

objectui#7926 refused `actions` on this same node and deliberately left this key
parsing, with a pin saying a later retirement had to say so out loud. That pin is
flipped rather than deleted. Its maintainer ruling is NOT borrowed - it covers
`actions` only; the authority here is the standing ADR-0049 enforce-or-remove
gate, which this package already applies to this face.

Measured with a point-access probe, never a bare word: `\.breadcrumbs` scores 0
tree-wide against 10 files for `\.breadcrumb\b` as the lit control. Three author
sites, all teaching passages in content/docs/guide/layout.md - correcting objectstack-ai#7926's
"1 site", whose census filtered on `page`-tagged objects while two of the three
passages carry no `type` at all. All three are rewritten onto the `breadcrumb`
NODE, which is a registered renderer taking the same item shape.

The node is NOT strict, and the census leg that says so is re-asserted.

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

* docs(types): name the fence-language blind spot correctly, bump breadcrumbs changeset to minor

Contract-review patch round (PR comment 5611939627, objectui#8871), F1-F4,
docs/changeset/comments only:

- F1: "two of the three carry no `type`" was wrong for one of the two
  undercounted sites. `layout.md:207`'s literal DOES carry `type: 'page'` — it
  was missed because it sits inside a markdown `typescript` fence, a fence
  language PR objectstack-ai#8870's census (json fences + TS/TSX AST + raw JSON files) never
  reads, not because it lacks a `type` key. `:676` was already correctly
  described (a `json`-fenced, untagged fragment). Corrected in all six
  locations: the PR body, this changeset, both `layout.zod.ts` docblocks, and
  both refusal test docblocks.
- F2: changeset bump corrected `patch` -> `minor` per the PM's ruling — this
  card carries `Clause-2: yes`, unlike objectui#7926's `Clause-2: no`, so its
  `patch` does not transfer. Cites the precedents that share this card's
  clause-2 reading instead (objectui#5905 both changesets, objectstack-ai#4919, objectstack-ai#5453 — all
  `minor`). Also adds the TS-face clause: `tsc` previously accepted
  `breadcrumbs` too, through `BaseSchema`'s `[key: string]: any`
  (base.ts:467), before this narrowed both faces together.
- F3: `\.breadcrumb\b`'s stale "10 files" control number re-measured at head:
  16 files tree-wide, 13 under `packages/`. The pin itself asserts `> 3`, so
  it was never at risk — only the prose was stale.
- F4: confirmed `page-app-dashboard-spec-parity.test.ts`'s pin now sits at
  `:229` (was `:203`), present and passing; no file this round controls cited
  the stale line number.

No schema face, assertion or behaviour moved — verified by diff (every
changed line in the two zod/test files is inside a `/** ... */` comment).
`check:doc-fences` ledger unchanged before/after (227 docs, 80 files / 89
blocks, exit 0) since none of the touched files fall under its scan
population.

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

* docs(types): state the base/head frame at all four probe sites, name the census blind spot correctly (objectui#8871)

Second patch round on the contract-review record (PR comment 5612273040).
Comments, docblocks and changeset prose only: over layout.ts,
zod/layout.zod.ts and page-breadcrumbs-refusal-8871.test.ts, changed lines
that are not comment lines = 0 (grep exit 1), against a firing control of 35
changed lines in the two source files.

F1 - the seventh site. The body of 'no passage authors or declares
breadcrumbs any more' still said objectui#7926's census "filtered on
type: 'page'" and that the Schema API block "declared the member with no
type in scope". Re-verified on the base: guide/layout.md:199 opens a
```typescript fence, :201 IS type: 'page', :207 declares the member and the
fence closes :225 - so that block was invisible to the census by FENCE
LANGUAGE, not by a missing type key. :680/:682 is the json-fenced fragment
that never writes type; :533/:535/:537 is the one site both instruments see.
PR objectstack-ai#8870's own body states the population: every git-tracked JSON file,
every json fence in .md/.mdx, every TS/TSX object literal via the
TypeScript AST. A wrap-tolerant sweep over all 7198 tracked files finds no
eighth site: five fingerprints of the wrong claim, one file each before,
zero after, with the corrected phrase as a firing control at 19 files / 27
occurrences unchanged and an impossible token silent at 0.

F3 - the frame. Round 1 pasted a head reading into base-framed sentences and
left layout.ts at the old number, so the twin faces disagreed. Re-derived,
exit codes captured before any pipe: on base 93127bd, \.breadcrumbs is
exit 1 tree-wide against 12 files (10 under packages/) for \.breadcrumb\b;
at head those read 16 and 13 and \.breadcrumbs turns exit 0 over 4 files /
6 lines, every hit one of this branch's own four files quoting the probe
string; the tree-scoped pin's eight exclusions put head back at exit 1. All
four sites now state the frame in one sentence. No assertion changed.

F2 - the precedent list. Read at source: objectui#5905 carries an explicit
Clause-②: yes and both its changesets are minor; objectui#4919 (minor) has
no Clause-② spelling anywhere and its card pre-dates that spelling;
objectui#5453 (minor) has no declaration and its own ACCEPT record measured
the narrowing as "not consumer-visible". The changeset now credits objectstack-ai#5905
alone for the clause reading and the other two for the level only. The minor
level does not move.

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

---------

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants