docs(skills): move the three published guides off the retired dataSource expression root

[os-tesla]

Fixes #9370

⛔ GOVERNED SURFACE (skills/**, GOVERNED_SURFACES skills-catalog). This PR parks as a draft by design and needs an APPROVED review from an authorized approver (os-zhuang, hotlong). ⛔ Not flipped ready, not enqueued, no auto-merge. The precedent on this exact surface is #9352 / card #9311, merged as 28be0786d.

⚠️ Merge after #9369, and this PR states which world it measured in. Re-derived from my own tree at base 69aa9c017, not assumed: SchemaRenderer.tsx still carries the data: dataSource binding, and SchemaRendererContext.tsx still reads const dataSource = context?.dataSource inside useDataScope. Both halves are still LIVE on this base — #9369 is open, not merged. So these pages become true the moment #9369 lands and are ahead of the code until then. Every evaluator measurement below is from that same pre-#9369 tree, which is the right place to take it: the evaluator itself is what #9369 stops feeding, and the evaluator's own behaviour does not move. Sequencing is a maintainer decision, not something this PR can enforce.

What moved

The maintainer ruled objectui#9308 option B on 2026-09-13: SchemaRenderer stops publishing the injected DataSource adapter as the expression root data (b1), and useDataScope — what a node's bind resolves through — reads the ambient scope a host publishes via PredicateScopeProvider instead of walking that adapter (b2). The published skill package still taught both halves.

Three files, matching the shape #9369 used for content/docs/guide/schema-rendering.md and packages/react/README.md: publish the host values under real names through PredicateScopeProvider, read them by those names, and state that dataSource is the adapter and not a root.

file	what changed
guides/schema-expressions.md	the scope table, a new COMPILED wiring example, the migration callout, the bind resolution prose, the bound-list comment, debugging-checklist item 3
guides/data-integration.md	the architecture diagram's channel split, "Static data" rewritten onto the scope channel as a COMPILED example, the useDataScope resolution sentence, the data root claim
rules/protocol.md	both measured tables' WIRING restated, the bind comment and nested-path sentence, plus a callout carrying the retirement and pointing at the verdict flip

⛔ Untouched, as the card requires: the object-* reader-list paragraph and the data-table bind pothole (objectui#6575 still rules data-table does not read bind).

⭐ The part that is not a renaming

A migration note that only swaps provider names is wrong here, because the verdict moved. Measured by me on the built evaluator (packages/core/dist), with firing controls — ⛔ and the true on a missing root belongs to the predicate layer, not to the evaluator:

scope, expression	evaluateExpression	evaluateCondition
CONTROL { data: { status: 'draft' } }, ${data.status}	"draft"	true
CONTROL same scope, Status: ${data.status}	"Status: draft"	true
CONTROL same scope, ${data.nope} — present root, absent member	undefined	false
{ data: {} } — adapter-shaped, ${data.status == 'draft'}	false	false
{ data: undefined }, same predicate	false	false
{} — no data root, ${data.status}	"${data.status}"	true
{} — no data root, Status: ${data.status}	"Status: ${data.status}"	true
{} — no data root, ${data.status == 'draft'}	"${data.status == 'draft'}"	true

The third control is the discriminating one: a root that is PRESENT with an absent member yields undefined, while a root that is MISSING yields the template's own source characters. So the two layers answer a missing root differently, and each has its own reader-visible symptom:

• predicate layer — fails soft to true. A "visible": "${data.status == 'draft'}" authored from these pages was hidden on every row and is now shown on every row; spelled "hidden" it flips the other way.
• interpolation layer — does not fail soft at all. A content built from a missing root paints the literal characters ${data.status} on screen.

The callout carries one column per layer and tells the reader to read both. It also states that re-publishing data restores the OLD always-false verdict rather than fixing the gate, and points row gates at record — the runtime-layer root under ADR-0089 D3.

What I decided about the ~two dozen ${data.…} examples

Measured, not estimated: schema-expressions.md carries 21 lines spelling ${data. (one of them is the census's own scope-table row). Repo-wide under skills/: 21 here, 14 in rules/protocol.md, 5 in page-builder.md, 4 in testing.md, 2 each in data-integration.md and auth-permissions.md, 1 in architecture.md, plus 4 in evals/*.json.

Decision: keep every one of them verbatim and make them reachable, rather than rewrite them to bare roots. The page's new wiring example publishes a root literally named data, and the scope table says in a row that every ${data.*} example on the page assumes exactly that. Three reasons this is the right divergence from #9369's content/docs shape:

1. A pin renders those exact spellings. skill-guide-provider-envelope.test.tsx, as re-derived in feat(react)!: unbind the data-source adapter from the expression scope, and point bind at the scope channel #9369, publishes scope = { data: PROVIDER } and renders ${data.customers} / ${data.label}. Rewriting the guide spellings would move that pin's subject from inside a second pull request — the "green alone, red together" shape.
2. ADR-0089 D3 does not forbid the name. CANONICAL_ROOT_BY_LAYER puts data at the metadata layer. What was retired is the renderer AUTO-publishing the adapter there, not the name.
3. Most of those examples are about something else — which text keys carry expressions, type preservation, the troubleshooting section. The root name is scaffolding, and churning 20 lines of scaffolding on a governed surface buys the reader nothing.

⛔ Nothing was silently rewritten: the only expression text this PR changes is the two dataSource = {…} comments that named the retired wiring.

Re-measurement of the card's per-line census

The card measured on the objectui#9308 branch. Re-measured against origin/main 69aa9c017 — every cited line still lands on the cited text:

cited	on origin/main 69aa9c017	verdict
112	`	Top-level data fields
113	`	`data`
302-303	dataSource = { customerNames: … }, useDataScope("customerNames")	exact
305	**Nested paths work:** … resolves \dataSource.app.settings.users``	exact
393	// ✅ Bound data, already node-shaped: dataSource = { rows: … }	exact

premise_still_valid: true.

Enumeration beyond the census (⛔ out of scope for this PR)

--measure judges every candidate fence, marked or not, so a page can be wrong where no gate looks. Reading the prose as well turned up two more:

• guides/auth-permissions.md carries the same retired claim in its own words — a scope table row | \data` | the `dataSource` passed to `SchemaRendererProvider` |, the sentence "Keys of the dataSourceobject are reachable only under thedata.root", and "With no host scope mounted,dataandpage` are all you get". ⛔ Out of scope here: PR docs(skills): guard both useAuth members in the auth-permissions example #9374 holds that file, so an in-place edit would collide. Filed as finding(skills): auth-permissions.md still teaches dataSource as the data expression root — a fourth file the objectui#9370 census missed #9379.
• guides/testing.md Pattern 5 asserts getByText('Secret') for a node gated on ${userRole !== "admin"} — a BARE root that no channel publishes, before or after the ruling. Copy the example and the assertion fails. Different defect class from this card, and independent of the ruling — it is wrong on main today. Filed as bug(skills): testing.md Pattern 5 gates on a bare userRole root nothing publishes — copy the example and the assertion throws #9380.

Noted, not filed: the ${data.*} examples in page-builder.md, architecture.md, i18n.md, project-setup.md and evals/*.json are in the same reachable-only-if-the-host-publishes class; they are not falsifiably wrong and the skills lane that takes the auth-permissions card is their natural carrier.

Verification

Reproduce-first, as required — the harness is trustworthy before any red or green from it is read:

$ node scripts/check-skill-examples.mjs --self-test     # BEFORE the build
EXIT=2 — PRECONDITION NOT MET: the self-test's type-check leg needs the workspace built

$ ...os-verify-lock.sh -c 'turbo run build $(--build-filter) --concurrency=2'
VERDICT command-exit 0 · held the lock 44s · waited 0s

$ node scripts/check-skill-examples.mjs --self-test     # AFTER the build
EXIT=0 — ✓ 59 cases pass

Gate, verbatim, before and after this diff:

BEFORE (exit 0)
Scanned 20 guide(s) under skills, .claude/skills: 121 ts/tsx/typescript fence(s), 70 json/jsonc fence(s).
Marked: 14 ts fence(s) (floor 13), 70 json fence(s) (floor 70)
Semantic phase: 14 of 14 ts fence(s) judged, 0 failed.
JSON phase:     70 fence(s) parsed, 0 failed.
Every marked skill example holds up against the built types.

AFTER (exit 0)
Scanned 20 guide(s) under skills, .claude/skills: 122 ts/tsx/typescript fence(s), 70 json/jsonc fence(s).
Marked: 16 ts fence(s) (floor 13), 70 json fence(s) (floor 70)
Semantic phase: 16 of 16 ts fence(s) judged, 0 failed.
JSON phase:     70 fence(s) parsed, 0 failed.
Every marked skill example holds up against the built types.

⭐ The marked ts population moves 14 to 16 and the json population is unmoved at 70 — both floors are SHRINK-ONLY and neither is breached. The two new marked fences are the wiring examples, so the thing this card is about is now COMPILED against the built dist/*.d.ts rather than only read.

Derived by hand from package.json plus .github/workflows/ (this repo has no dispatch-gates.mjs); every one run on this tree:

gate	exit
check-skill-examples.mjs --self-test	0
check-skill-examples.mjs	0
check-skills-paths.mjs	0 — 88/89 stated paths resolve, 1 pre-existing baselined
check-skill-eval-tokens.mjs --self-test / check-skill-eval-tokens.mjs	0 / 0
check-control-bytes.mjs	0 — 7539 tracked text files
check-shell-escape-residue.mjs	0 — 16/16 skills documents under a declared root
check-new-cross-file-line-citations.mjs	0 — 0 new citations
check-changeset-presence.mjs	0
check-doc-links.mjs	0
check-governed-queue-guard.mjs --self-test	0 — 185 cases

Package tests that READ these three documents (markdown-test-inputs.mjs --changed names all three as test inputs, so CI runs the full shards): reported below the fold once the shared verify lock grants a turn.

Line readings for the governed surface, as the contract requires:

reading	before	after	delta
guides/schema-expressions.md	569	635	+66
guides/data-integration.md	485	513	+28
rules/protocol.md	341	354	+13
whole published package skills/**	5201	5308	+107 (+2.1%)

The added lines are the correction itself: one migration callout, two now-compiled wiring examples, and the sentences that replace the retired claims. No re-wrap was used to buy lines.

Changeset

None owed, by measurement rather than by inheritance:

1. node scripts/check-changeset-presence.mjs — "Compared the working tree with 69aa9c017 (merge-base with origin/main): 3 file(s) changed, 0 of them published source of a package the release covers, 0 of them a manifest whose published contract moved … No source or published contract of a released package changed in this range, so no changeset is owed." (exit 0)
2. Independently: 0 of 43 workspace manifests mention skills in files / exports / main / module / types / bin. Positive control on the same scan: 38 manifests list dist in files[]. Nothing under skills/ is shipped by any npm package.
3. The merged precedent on this surface, 28be0786d (fix(skills): guard the DataSource read in the marked data-integration example #9352), changed one skills/ file and carried no changeset.

⚠️ One inconsistency worth a maintainer's eye rather than my guess: open PR #9374, also a single skills/ guide, DOES carry an empty-frontmatter changeset declaring "no package is released by this change". Both forms pass the gate. If the empty-frontmatter declaration is the house style for this surface, say so and I will add one.

Governed-queue-guard verdict on this diff (verbatim)

$ node scripts/check-governed-queue-guard.mjs --test skills/objectui/guides/schema-expressions.md skills/objectui/guides/data-integration.md skills/objectui/rules/protocol.md
⛔ GOVERNED — 3 of 3 path(s) are on a governed surface:
   skills/** x3 — the published skills catalog
     - skills/objectui/guides/schema-expressions.md
     - skills/objectui/guides/data-integration.md
     - skills/objectui/rules/protocol.md

   One governed path governs the WHOLE pull request — proportion is not a question.
   ⛔ Do not flip it ready, enqueue it, or arm auto-merge. Park it as a DRAFT and leave the merge
      to the maintainer; a human merge IS the review record for a governed surface.
   The merge-queue run of "Governed Surface Queue Guard" refuses this diff unless an APPROVED review by an
   authorized approver (GOVERNED_APPROVERS: os-zhuang, hotlong) is on the pull request — on
   whichever commit it was left (maintainer ruling 2026-09-04).
exit 3

Clause-② — contract review

needs:contract-review is hung on this PR in the same stroke as opening it, mirroring the card. Published skills/** making falsifiable contract-semantics claims about which roots a tier binds. ⛔ The governed-surface human merge does not substitute for it; the two stack, and neither limb is mine to clear.

Inherited reds — ⛔ not from this PR

• Bundle Analysis is red on main (arrived with chore(deps): run pnpm dedupe --lockfile-only on an untouched main — the measurement (objectui#9215) #9316; a maintainer decision).
• Doc Snippet Type Check is red on main until feat(react)!: unbind the data-source adapter from the expression scope, and point bind at the scope channel #9369 lands. This diff touches no document that gate scans (content/docs + package READMEs + root README.md, explicitly not skills/**).

Acceptance notes

• ⛔ No test was skipped, quarantined or weakened. No assertion was loosened. The marked-fence floors both hold and the ts population grew.
• The card's "the pins are green while the prose beside them is wrong" warning was taken literally: the six packages/components pins feat(react)!: unbind the data-source adapter from the expression scope, and point bind at the scope channel #9369 re-derived were read for what they assert about these files before a byte was changed, and every string they pin is intact — Rule: Keys Live on the Node, the hoists every key onto\s+the node regex, the absence of the two retired sentences, the no md matches "instead of \props.`"class guard, and the"bind": "customerNames"` list example in each of the three guides.
• Noted, not filed: rules/protocol.md's two measured tables still cite origin/main f1c27f037 as the commit they were measured on. This PR restates their WIRING, not their outcomes, and says so inline; a re-measurement on a current commit is a separate piece of work, and the skill-guide-provider-envelope pin is what actually holds those outcomes today. Carrier: whoever next re-derives that pin.

维护者速读(草稿)

改了什么

把发布中的 skills/objectui 三份指南从「dataSource 就是表达式根 data、bind 走 dataSource」改成 ruling 之后的真实通道:宿主用 PredicateScopeProvider 发布作用域,dataSource 只是取数适配器。另外给两个接线示例加上 os:check 标记,让它们第一次真的被编译校验。

为什么改

2026-09-13 的裁决(objectui#9308 option B)已经把这两件事退役,但发布给 AI 读的技能包还在教它们。更要紧的是:这不是改名。同一条 data.* 门,旧接线下恒判 false、新接线下因为根缺失走 fail-soft 恒判 true —— 一个 visible 门从「每行都藏」变成「每行都显」。只换 provider 名字的迁移说明会让读者踩正这一脚。

风险与代价(含回滚)

• 排序风险(主要): feat(react)!: unbind the data-source adapter from the expression scope, and point bind at the scope channel #9369 还没合。在它合进去之前,这三页描述的是尚未落地的行为。⚠️ 建议排在 feat(react)!: unbind the data-source adapter from the expression scope, and point bind at the scope channel #9369 之后合。
• 保留了全部 ${data.*} 示例原文,只让接线示例发布一个叫 data 的根 —— 因为 skill-guide-provider-envelope 这个 pin 正在渲染这些拼写,改写它们会在另一个 PR 的盲区里挪动 pin 的被测主体。
• 回滚代价:纯文档,git revert 一笔即可,不影响任何已发布包(本仓 43 个 manifest 无一发布 skills/)。

席位意见

(留空,待 os-zhuang / hotlong 定稿)

你要做的

1. 确认合并顺序:先 feat(react)!: unbind the data-source adapter from the expression scope, and point bind at the scope channel #9369,再本 PR。
2. 作为受管面的人工合并方给出 APPROVED review(这一道是 check-governed-queue-guard 机械要求的)。
3. clause-② 的 needs:contract-review 需要一份书面复核记录后才清 —— ⛔ 两道保障叠加,人工合并不替代它。
4. 顺带定一句话:本仓单文件 skills/ 改动到底要不要写空 frontmatter changeset(fix(skills): guard the DataSource read in the marked data-integration example #9352 没写、docs(skills): guard both useAuth members in the auth-permissions example #9374 写了,门禁两边都放行)。

---

Generated by Claude Code

---

Generated by Claude Code

[os-tesla]

Contract review

Served-tier: CONTRACT_REVIEW_TIER
Head-sha: 5df0ee9719178037689ca3fb7c61394eab88ec2d

In-seat review by the domain:skills seat at the contract-review tier (served tier read at seating, objectstack#7623 marker 5738863635) — the lane's record, taken under the reconciliation ask 5739015009 on objectui#9370 (ruling objectstack#18862 item 2) after one working day's silence: ask 2026-09-19T03:31Z, window read at 2026-09-20T03:33Z — no comment from a live holder on the card, and the domain:ui seat post objectui#9771 names neither this card nor this PR. ⛔ No Claim: by this seat on the card: the claim of record stays 5652138683 (restated with its Branch: line by 5689310818), because the claim reader retracts only by the same login (objectstack#19240) — this seat acts as the lane's reviewing and landing seat. Clause-②: yes is declared on that claim; needs:contract-review is on both carriers (check-clause2-carriers --pair 9378 exit 0 at 2026-09-20T03:07Z: 「both carriers agree」; the PR body spells the clause as a heading, which the reader reports as input only). Verified against GitHub (GET /pulls/9378/files: three files — skills/objectui/guides/data-integration.md +40 / −12, skills/objectui/guides/schema-expressions.md +76 / −10, skills/objectui/rules/protocol.md +18 / −5) and the fetched branch (origin/claude/issue-9370-skills-data-root at 5df0ee97, git rev-parse pasted above; base 69aa9c017, 347 commits behind origin/main e86445f5; git merge-tree --write-tree origin/main HEAD clean after deepening to the merge base; REST mergeable: true, mergeable_state: behind), ⛔ not against the report: two commits, no model identifier in either message; ten hunks.

① Derived judgments

• The public-surface claim the three files now make: expression roots and bind paths resolve against the ambient scope a host publishes with PredicateScopeProvider (@object-ui/react); SchemaRendererProvider's dataSource is the fetch adapter — it publishes no root and answers no bind; the renderer adds record (the bound row) and page, and derives current_user from the scope's user. Read on objectui origin/main: packages/react/src/context/SchemaRendererContext.tsx :113–:114 (useDataScope reads usePredicateScope()); packages/react/src/SchemaRenderer.tsx :866, :940–:953 (the removed data: dataSource binding, named as the decision), :969–:974 (...predicateScope, current_user: predicateScope.user, { record: boundRecord }, page: pageVariables); packages/react/src/hooks/useExpression.ts :36 PredicateScopeProvider and :50 usePredicateScope, exported through hooks/index.ts :9 and packages/react/src/index.ts :11 — so the two new os:check fences' imports ({ PredicateScopeProvider, SchemaRenderer } from @object-ui/react, type { BaseSchema } from @object-ui/types, packages/types/src/index.ts :95) name real exports; packages/components/src/renderers/data-display/list.tsx :11 / :17 still reads bind through useDataScope. Every sentence in the diff is a reading of that code: the guides teach the channel that exists and stop teaching the one that resolves to undefined. Correct per the card's census and objectui#9308 (merged as PR feat(react)!: unbind the data-source adapter from the expression scope, and point bind at the scope channel #9369, 85243729, 2026-09-13T09:02Z — the PR body's 「merge after feat(react)!: unbind the data-source adapter from the expression scope, and point bind at the scope channel #9369」 condition is met, so the prose is true on main today).
• The verdict-flip callout (schema-expressions.md, the ⛔ block): one column per layer — the predicate layer fails soft to true, the interpolation layer returns the template's own characters — is the dev's measurement on the built evaluator with three firing controls (report 5652297355, migration_note_states_the_verdict_flip), and the two roots it names match CANONICAL_ROOT_BY_LAYER = { runtime: 'record', metadata: 'data' } (objectstack packages/lint/src/validate-visibility-predicates.ts :894–:897, ADR-0089 D3). The seat did not re-run the evaluator (no built dist here); the code readings above are the seat's, the table is the dev's with its controls stated.
• The ${data.*} examples are KEPT and made reachable (the wiring fence publishes a root named data; the scope-table row says every such example assumes it), not rewritten as PR feat(react)!: unbind the data-source adapter from the expression scope, and point bind at the scope channel #9369 did for content/docs — the dev's stated divergence, with reasons the seat checked: the pin skill-guide-provider-envelope.test.tsx :106 publishes scope={{ data: PROVIDER }} and renders those spellings, and ADR-0089 keeps data at the metadata layer. Residual ${data. on the branch: schema-expressions.md 23 (21 on main; the +2 are the wiring fence and the table row), data-integration.md 2, protocol.md 14 (+1, the re-attributed measurement line). Accepted: no example is false under the prose that now precedes it.
• protocol.md's two measured tables keep their f1c27f037 outcomes and only re-attribute the wiring, saying so inline; today those outcomes are held by skill-guide-provider-envelope.test.tsx (:218 / :246 read this file). Region fence held: origin/main's one later change to this file (efc1c9c4, :107–:115) and open PR docs(skills,AGENTS): teach action:button + actionType, retire the events bag #9592's hunk (:238–:262) are both disjoint from this PR's two hunks (:134–:140, :208–:235 on its base); the merge is clean.
• Value density, read from the loading agent's seat: the three pages now name the one channel that works, say what dataSource still is, and tell a reader who authored a data.* gate from the old pages what moved, per layer. Lines: data-integration.md 485 → 513, schema-expressions.md 569 → 635, protocol.md 344 → 354 (+104 by count, +134 / −27 by diff); the dispatching claim set no net-line cap.

② Semver level

None owed — skills/** publishes no package; scripts/check-changeset-presence.mjs exit 0 at this head against merge-base 69aa9c017.

③ Boundary flags

• open_questions (2): merge ordering (A) — moot, feat(react)!: unbind the data-source adapter from the expression scope, and point bind at the scope channel #9369 merged; changeset house style (A) — the gate decides, exit 0. out_of_scope_findings: objectui#9379 and bug(skills): testing.md Pattern 5 gates on a bare userRole root nothing publishes — copy the example and the assertion throws #9380 filed by the dev; the page-builder.md member of the same class landed as its own card (objectui#9672 → PR docs(skills): page-builder.md names the channel that publishes expression roots (objectui#9672) #9997, at its terminal).
• CI: ⛔ NOT MEASURED on this head — 0 check-runs; all 22 workflow runs of 2026-09-13T08:45Z ended startup_failure or stayed queued (a runner-side failure that day, not this diff). The seat's PUT /pulls/9378/update-branch — the one PM-legal way to obtain a fresh run — was refused by this session's command classifier at 2026-09-20T03:34Z, and MCP writes are outside the seat's channel. Gates the seat ran at the head without a build, in a detached read-only worktree: check-skills-paths exit 0, check-skill-eval-tokens exit 0, check-changeset-presence exit 0. NOT MEASURED here: check-skill-examples (needs the built dist; the dev's reading at the branch: 16 of 16 marked fences pass, floor 13) and the two guide-reading pins (skill-guide-data-table-binding.test.tsx, skill-guide-provider-envelope.test.tsx). The queue builds and tests the merge result on the way in; an approver who wants the PR-level checks first can press 「Update branch」 — one click, and this record stays valid for the content (the merge adds no line to the three files).
• Attribution: the PR body carries the dev's session footer plus the platform's appended one (the dev's report names it); neither commit carries a model identifier.

Implemented-by: claude/issue-9370-skills-data-root
Reviewed-by: session_01W5y9kRg1YtYaMQYExVLRc2

VERDICT: PASS

---

Generated by Claude Code

[github-actions]

changeset-claim-re-read

⚠️ 5 pending changeset(s) describe a file this change touches

Their bodies publish verbatim into the CHANGELOG at the next release, so this is a request to re-read them against your diff — addressed here because you are the one seat that can answer it without re-deriving anything.

⛔ Nothing here blocks, and nothing here is a verdict on your change. This gate exits 0, is not a required context, and judges name resolution, never meaning: it asked whether a pending body names a file you touched. "Is this sentence still true?" is the one question it will not answer, and the one you are being asked to answer.

.changeset/4795-bindable-text-keys.md

• names skills/objectui/rules/protocol.md → skills/objectui/rules/protocol.md — edited by this change

  Published authoring guidance updated to match: skills/objectui/rules/protocol.md (new "Bindable Text Keys" rule), plus the page-builder, schema-expressions and data-integration guides, which taught the now-retired "never evaluated" statement and its host-pre-resolution workaround.

.changeset/5120-retire-data-table-name-alias.md

• names skills/objectui/guides/data-integration.md → skills/objectui/guides/data-integration.md — edited by this change

  The two published skill guides that taught the name spelling (skills/objectui/guides/data-integration.md, schema-expressions.md) migrate in this same release, so the platform never refuses a spelling it still ships.

• names schema-expressions.md → skills/objectui/guides/schema-expressions.md — edited by this change

  The two published skill guides that taught the name spelling (skills/objectui/guides/data-integration.md, schema-expressions.md) migrate in this same release, so the platform never refuses a spelling it still ships.

.changeset/6357-basechema-bind-declaration.md

• names skills/objectui/rules/protocol.md → skills/objectui/rules/protocol.md — edited by this change

  bind was read by ten production sites and declared by no schema shape. It resolved as any through BaseSchema's index signature and rode .passthrough() on the validator, while three separate documents taught it as an authorable key of every node: this repo's own AGENTS.md §4 ("Every node in the UI tree follows this shape (@object-ui/types)"), the published agent-facing skills/objectui/rules/protocol.md ("Every UI component node MUST follow this shape"), and content/docs/fields/grid.mdx. So the agent-facing protocol told authors to write a key the published types did not know existed.

.changeset/6575-data-table-bind-diagnostic.md

• names skills/objectui/rules/protocol.md → skills/objectui/rules/protocol.md — edited by this change

  The platform was already paying for this in teaching rather than in diagnostics: skills/objectui/rules/protocol.md documents the pothole verbatim and a pin test locks the behaviour. The warning now also reaches the console, where the author who did not read the docs is standing:

.changeset/6665-data-table-non-array-data-diagnostic.md

• names skills/objectui/rules/protocol.md → skills/objectui/rules/protocol.md — edited by this change

  The spelling that opened the card is a ${...} expression string, and it is a defect rather than a design because the SAME expression is evaluated one key over. Re-measured on merge-base 5967be095 through the real SchemaRenderer (the table was previously quoted from skills/objectui/rules/protocol.md as a measurement on f1c27f037 and had not been re-run); all four legs reproduced, and they are now pinned as tests rather than prose:

Read the paragraph, not the line: both false halves of the objectui#8617 claim sat in one paragraph, and correcting either alone would have left it asserting the same wrong thing.

If a claim did go false, correct the body. That is precedented and prose-only, frontmatter untouched; check-changeset-overwrite.mjs will report the correction as its own case 2 ("correcting a declaration on purpose … legitimate"), which is the intended shape — one gate asks for the read, the other records the write.

Not covered, stated so nobody reads this as more: a born-false claim that spells no line address at all (objectui#9495 coordinated one by ORDINAL — "a grep finds that member first" — and deciding that means reading what the sentence means), a claim spelled as a symbol or a package rather than a backticked file name, and a file named ambiguously.

Compared the checked-out tree with c2f0f4832 (merge-base with origin/main): 3 file(s) changed outside .changeset/, read against 1223 pending declaration(s) that publish a body (1783 pending in total). · run

[os-tesla]

Parked back to DRAFT at 2026-09-20T09:11Z — this is the queue guard's own step 1, ⛔ not a judgement on the change. Acted by the domain:ui#2 execution seat (PM session session_018HrVaotisyhgmot9o2MLRq) under a direct maintainer instruction, quoted below.

Why it had to leave the queue

This PR entered the merge queue at 2026-09-20T08:56:39Z while both clause-② carriers were still open: the needs:contract-review label is on this PR and on its card objectui#9370. The merge-group job Governed Surface Queue Guard failed on that, exit code 6, and its own output quotes the governing rule verbatim:

「双肢命中任一 ⇒ 无席内条款②复核 PASS 在案 ⛔ 禁止入队」

and names the remedy, which is what this comment records doing:

1. ⭐ Take the pull request out of the queue: convert it back to DRAFT (disarming auto-merge alone does NOT dequeue it — objectui#6183 measured exactly that), and leave it parked.

⚠️ The approval is not the thing that was missing. os-zhuang submitted an APPROVED review at 2026-09-20T08:36:26Z and flipped the PR ready four seconds later. This guard does ⛔ not read approvals — it reads the clause-② carrier, which is a different gate and is still hung on both carriers.

⛔ What this seat did NOT do

⛔ Did not strip the needs:contract-review label. The guard's own words: 「Stripping the label to get past this check, with no verdict on record, is the defect this leg was built from — not a way through it.」 Both carriers stay exactly as they were.
⛔ Did not touch the change, the branch, the approval, or the card.

Why it mattered to other work

The queue stacks entries. While this PR's group kept failing, three other PRs were queued on top of it — objectui#10052, objectui#9996 and objectui#9924 — and were being rebuilt behind a group that could not pass. ⭐ objectui#9996 had already been ejected twice (2026-09-19 05:35Z and 06:49Z) for an unrelated reason of its own.

The authority for acting outside this lane, and its three parts

• Whose: the maintainer, speaking to this seat directly.
• Words, quoted and ⛔ not translated: 「6小时之前的所有开发 pr」…「你接手以上所有pr的开发。除了 Version Packages」
• Where: this PM session's chat, 2026-09-20T09:09Z.

What unparks it

The dispatching seat completes the in-seat clause-② review and posts the verdict on this PR or on objectui#9370; on PASS that same seat strips the carrier from both carriers, cites the record, then flips ready and re-enqueues. On FAIL it is a patch round. ⚠️ Note objectui#9370 also carries needs-user-decision, so the card is in the decision inbox as well.

---

Generated by Claude Code