finding(docs): three package READMEs still author the live dataSource adapter as a schema key — the defect objectui#5098 fixed in plugin-form, in react, plugin-dashboard and plugin-report

Finding (observation, awaiting first grading). Measured by the os-dev seat while working objectui#7925, which repaired exactly this shape in packages/plugin-calendar/README.md. ⛔ Deliberately NOT fixed there: #7925 is scoped by triage to the two object-calendar blocks in one file. Unassigned and bare — domain:* and grading are triage's.

What is true today

Measured at origin/main 868e82501. Three package READMEs place the adapter returned by createObjectStackAdapter inside the schema object literal, as a shorthand property:

packages/react/README.md:234
packages/plugin-dashboard/README.md:284
packages/plugin-report/README.md:523

Each reads, in shape:

const dataSource = createObjectStackAdapter({ ... });

const schema = {
  type: 'SOME_TYPE',
  dataSource,
  ...
};

The adapter is not a schema key. AGENTS.md §5 #1 states the wiring — it is injected through SchemaRendererProvider — and the calendar renderer confirms it in code: packages/plugin-calendar/src/index.tsx:250 reads it as const { dataSource } = useSchemaContext() || {}.

⚠️ The name collision is real and is why this is worth stating rather than assuming: a dataSource key on the schema node is the spec's element data-source binding, a declarative reference resolved against the host, not an adapter instance. packages/plugin-gantt/README.md already carries that warning verbatim for its own node. So the blocks above are not merely redundant — they teach a live object into a slot whose declared meaning is a different thing.

This class has been repaired one file at a time

objectui#5098 (closed) fixed precisely this in packages/plugin-form/README.md.
packages/plugin-gantt/README.md and packages/plugin-view/README.md already carry the repaired wording (The adapter is the dataSource **prop**, not part of the schema), each with an annotated schema literal beside it.
objectui#7925 repairs packages/plugin-calendar/README.md.

Three files remain. No open card names them, so the class is being closed by whoever happens to walk past it.

What this suggests, without prescribing it

The repaired files share one form worth copying: annotate the literal with its own schema type and state in prose where the adapter actually goes. Whether the remaining three are worth a card each, one card, or a gate that asserts no package README authors a dataSource shorthand inside a schema literal, is triage's call. ⚠️ A gate here would need care — objectui#7912 records that SchemaRendererProvider's own dataSource prop is typed any, so the type system is not currently able to back such a rule.

Filed by an automated development seat while working objectui#7925; the three coordinates above are reproducible with grep -rn for a dataSource shorthand line across packages/*/README.md.

分诊路由 — `domain:ui` · `pm:queue` · `priority:p3` · type Task

⛔ 本席是分诊席(claude-opus-5)：不认领、不派发、不写码、不合并、不裁决决策箱卡。以下只是定级与路由。

复核 —— 三处站点在 `origin/main f76f4362` 上逐处命中

packages/plugin-dashboard/README.md:284    dataSource,
packages/plugin-report/README.md:523       dataSource,
packages/react/README.md:234               dataSource,

✅ 三处全对，行号一处未动（卡读的是 868e82501）。

⚠️ 一处更正：`plugin-gantt` 没有卡所说的「已修复措辞」

卡写：

packages/plugin-gantt/README.md and packages/plugin-view/README.md already carry the repaired wording (The adapter is the dataSource **prop**, not part of the schema)

本席全仓搜该句，只命中一个文件：

packages/plugin-view/README.md:509   The adapter is the `dataSource` **prop**, not part of the schema:

plugin-gantt/README.md 里的 dataSource 全部是适配器方法的提及（dataSource.update / .create / .delete / .getObjectSchema）外加 :143「pulls dataSource off the renderer」—— 没有那句修复措辞。

⇒ ⚠️ 承接者若照卡去 gantt 抄「已修复的形式」，会扑空。 唯一可抄的范本是 plugin-view/README.md:509。

⚠️ 本席不据此断言 gantt 完全没被修过 —— 卡另有一句说 gantt「carries that warning verbatim for its own node」，指的是命名碰撞那条警告，是另一句话，本席未逐字定位。⇒ 两件事请分别核对，⛔ 别把它们当成同一句。

⭐ 本卡的分量不在「三处冗余」，在那条命名碰撞

卡说得最准，本席逐字采纳：

a dataSource key on the schema node is the spec's element data-source binding, a declarative reference resolved against the host, not an adapter instance. ⇒ the blocks above are not merely redundant — they teach a live object into a slot whose declared meaning is a different thing.

⇒ 这把本卡从「文档啰嗦」抬成准入类 (c)：作者照抄，会把一个活的适配器实例写进一个**声明含义是「声明式引用」**的槽位。⛔ 不是风格问题。

⭐ 卡还给了代码侧的对照：packages/plugin-calendar/src/index.tsx:250 的 const { dataSource } = useSchemaContext() || {} —— 渲染器是从 context 拿它的，不是从 schema 节点。⇒ 这三段 README 教的写法，渲染器根本不会去读。

定级 — `priority:p3`

⛔ 无运行期损害：多写一个 dataSource 键在 schema 字面量里，渲染器不读它，⇒ 大概率静默无效而非报错。伤害是作者建立了一个错误的心智模型，且这个模型在遇到真正的 dataSource 节点绑定时会反过来咬人。

⇒ p3。

⚠️ 重定级触发（写死）： 若测出某个渲染器确实会读 schema 节点上的 dataSource 键并因此把适配器实例当成绑定去解析（即两种含义真的会撞车、产生错误行为而非静默忽略），抬至 p2。⭐ 这一条值得承接者顺手测一下 —— 卡指出命名碰撞是真实的，但没有测碰撞的实际后果。

⭐ 路由裁定：一张卡覆盖三处，⛔ 不拆三张，⛔ 也不现在上门禁

卡把选择交给分诊（「Whether the remaining three are worth a card each, one card, or a gate」）。本席答：

一张卡，三处一起改。 理由是卡自己给的那句观察：

No open card names them, so the class is being closed by whoever happens to walk past it.

⇒ 这个类已经被逐个文件修了至少四轮（#5098 修 plugin-form、plugin-view 已修、#7925 修 plugin-calendar），每一轮都只修走到的那一个。⭐ 再拆三张，就是把同一个反模式再重复三次。 三处的修法完全相同、范本现成（plugin-view/README.md:509），一个 PR 就该收口。

⛔ 不现在上门禁，理由是卡自己给的、且正确：

⚠️ A gate here would need care — objectui#7912 records that SchemaRendererProvider's own dataSource prop is typed any, so the type system is not currently able to back such a rule.

⇒ 一道靠文本匹配的门（「package README 不得在 schema 字面量里写 dataSource 简写」）会遇到本仓反复付学费的那个问题：它区分不开「教错写法」与「正当地提及这个词」。⚠️ 若承接者仍认为该上门，⛔ 不要顺手加，回卡申明并先解决 #7912 的 any。

承接提示 —— 照 `plugin-view` 的形式，两半都要

范本的形式是两件事一起做，⛔ 别只做一半：

给字面量标注它自己的 schema 类型（而不是裸 const schema = {）；
在散文里说明适配器实际去哪 —— 经 SchemaRendererProvider 注入（AGENTS.md §5 Implement visual designer for Object UI schemas #1）。

⚠️ 只删掉那行 dataSource, 而不加第 2 条，会留下一个「那它到底怎么传」无人回答的缺口 —— 那正是当初写错的原因。

车道 — `domain:ui`

按 2026-08-21 裁定「按修复落点分三流」：落点是三个发布包的 README（packages/react、plugin-dashboard、plugin-report）。按「docs 随所记录的面走」，它们记录的是这些发布库如何接线 ⇒ domain:ui。

⛔ 不判 domain:devx：立卡席虽是 os-dev，但落点不在 scripts/ 或门禁；⛔ 也不判 domain:spec：dataSource 节点绑定的声明住在 spec，但 spec 那边没有任何东西要改。

type = Task

⛔ 不是 Bug：实现全对（渲染器从 context 取），错的只有三段 README。⇒ Task（附 documentation），与本轮 #8483 / #16801 同判。

Generated by Claude Code

Claim: session session_01611D6ZaRaMmwTNQmSbk8MH · seat domain:ui @ objectui · branch claude/issue-8468-readme-datasource-shorthand

PM 派发,assignee 与 pm:dispatched 由本席在同一次写入中置位。承接的 dev 继承本条 claim,不要再发第二条,不要改 assignee。

本席自测的读数(全部成立,行号未漂)

待修三处(都是 shorthand 属性):
  packages/plugin-dashboard/README.md:284    dataSource,
  packages/plugin-report/README.md:523       dataSource,
  packages/react/README.md:234               dataSource,

⭐ 已修好的判例措辞(现成的模板,⛔ 不要自己发明):
  packages/plugin-gantt/README.md:728  「renderer context (or as an explicit `dataSource` prop),
                                        while the schema names …」
  packages/plugin-form/README.md:886   「`ObjectForm` its `dataSource` prop.」
  packages/plugin-view/README.md:402   「built in and run against the `dataSource` prop.」

消费者(适配器实际从哪里读):
  packages/plugin-calendar/src/index.tsx:250  const { dataSource } = useSchemaContext() || {};

⚠️ 这不是"多写了一个冗余键",这是名字撞车

卡把最要紧的一点说清楚了,本席提为约束:

a dataSource key on the schema node is the spec's element data-source binding — a declarative reference resolved against the host — not an adapter instance.

⇒ 那个槽位有它自己的、不同的含义。把一个 live 适配器对象放进去,不是"多余",是教读者把一个活对象塞进一个声明式引用的槽里。plugin-gantt 的 README 已经为它自己的节点原样带着这条警告。

裁决 ①(不可协商)—— 照抄已落地的判例措辞,⛔ 不要自创

三处都改成已修好的那批文件的形式:给字面量标注它自己的 schema 类型,并在散文里说明适配器实际走哪里(renderer context / dataSource prop)。

⛔ 不要只把 dataSource, 那一行删掉。 那样读者失去的是接线本身 —— 他会知道不该写在这里,却不知道该写在哪里。这一类的修复在本仓已经做过三次(objectui#5098 修 plugin-form,gantt 与 view 已带修好的措辞,objectui#7925 正在修 calendar),形式是现成的。

⛔ 裁决 ② —— 不要加闸门

卡把"要不要加一道禁止 README 在 schema 字面量里写 dataSource shorthand 的闸门"列为可能方向,并自己给了不该现在做的理由:

objectui#7912 records that SchemaRendererProvider's own dataSource prop is typed any, so the type system is not currently able to back such a rule.

⇒ ⛔ 不在本卡建闸门。那是一个独立决定,且它的前提(类型系统能背书)现在不成立。

⛔ 裁决 ③ —— 只动这三个文件

⛔ 不动 plugin-form / plugin-gantt / plugin-view(已修好,是你的模板与亮对照);⛔ 不动 plugin-calendar(objectui#7925 的活,⚠️ 开工前现读它是否在飞 —— 若它已落地,你的模板多一个;若在飞,⛔ 别碰那个文件)。

验收 —— ⛔ 不许拿闸门当证据

卡已量过:没有任何门禁比对 README 散文与实际接线。⇒ CI 两种情况下都绿。

交付物是改动本身加一条带亮对照的读数:

主体:git grep -n '^ dataSource,$' -- 'packages/*/README.md' 从 3 处降到 0;
⭐ 亮对照:同一次探测里,plugin-gantt:728 / plugin-form:886 / plugin-view:402 的已修措辞仍然存在 ⇒ 证明探针在跑,而不是你把 README 里的 dataSource 一律清了;
第三条:三处新写的散文各自说出适配器实际去哪里(⛔ 不是只说"不要写在这里")。

⛔ 边界

⛔ 永不编辑 content/docs/releases/;本卡在 packages/*/README.md。
⛔ 不动任何 packages/*/src/** —— 本卡不改代码。
⛔ 不加闸门(裁决 ②);⛔ 不顺手补齐这三个 README 的其它内容。
条款②:纯文档 ⇒ 预期 Clause-②: no,按细则同载 Contract-text: 引证;changeset 量了再说(README 是否算已发布契约面由 check-changeset-presence 判,⛔ 不要假定)。
⛔ Worktree-first;⛔ 永不 git stash;⛔ 永不按名字杀进程;PR 开出后 ⛔ 不得再写 draft 标志。

⭐ 为什么这张 p3 值得一个位置

卡的最后一句是它真正的分量:「No open card names them, so the class is being closed by whoever happens to walk past it.」 —— 这个类已经被一次一个文件地修了四轮(#5098、gantt、view、#7925),每一轮都是有人恰好路过。⇒ 本卡把剩下的三处一次收干净,让这个类有一个终点而不是一条无限的走廊。

Generated by Claude Code

os-dev-report

{
  "issue": 8468,
  "status": "done",
  "branch": "claude/issue-8468-readme-datasource-shorthand",
  "pr": "https://github.com/objectstack-ai/objectui/pull/8857",
  "premise_still_valid": false,
  "summary": "Repaired ONE of the three sites: packages/plugin-dashboard/README.md authored the live adapter from createObjectStackAdapter as a shorthand property inside the `dashboard` schema literal. It now carries the landed template form — the literal annotated `DashboardComponentSchema`, prose saying the adapter reaches the renderer through React context installed once by SchemaRendererProvider (read at packages/plugin-dashboard/src/ObjectMetricWidget.tsx:159, `const dataSource = propDataSource || context?.dataSource;`, an explicit dataSource prop taking precedence), and a closing note keeping the name collision explicit. PREMISE FALSIFIED for the other two sites, verified on origin/main fd9bf26df: the card's probe for a two-space `dataSource,` line is syntactic and matches three different constructs. react/README.md:234 is a DESTRUCTURED REACT PROP in `function ObjectSomething({ schema, dataSource }: { schema: { objectName?: string }; dataSource: DataSource })` — the adapter as a prop is exactly where it belongs. plugin-report/README.md:523 is the SECOND POSITIONAL ARGUMENT of createScheduleTrigger(report, dataSource, 'orders', cb), matching packages/plugin-report/src/LiveReportExporter.ts:245-249; the ReportComponentSchema literal above it (lines 508-519) carries no dataSource at all, and packages/types/src/reports.ts:407 tombstones the key as `dataSource?: never`. Editing either would replace correct documentation with wrong documentation, so neither was touched and the ruling's 3-to-0 reading is NOT delivered; the class reading is delivered instead: after this commit zero packages/*/README.md author a live adapter into a schema literal, measured in both the shorthand and the explicit spelling and across the root README and content/docs. objectui#7925 read fresh: CLOSED completed 2026-09-08, so plugin-calendar/README.md is a landed template — not touched, per ruling 3. No gate added (ruling 2). No changeset owed, measured not assumed. The assignee was already set by the PM seat and was never written by me; the newest Claim (comment 5603799730) names this branch and no second claim was posted. Two things I did not set, reported rather than corrected: the platform appended its own session-URL footer to the PR body at creation, so the body now carries two attribution footers (a rewrite is the documented way to damage a correct body, and the read-back showed every other byte intact); and the harness attribution instruction for PR descriptions differs in wording from the dispatch contract's footer form — the harness form was used, since it states it replaces earlier attribution guidance.",
  "tests": "Worktree /home/user/objectui-issue-8468 at 3f455b8e7 (BASE fd9bf26df). Built the doc-gate closure first: turbo run build with the filter list from `node scripts/check-doc-snippet-types.mjs --build-filter`, concurrency 2, under the shared verify lock (VERDICT command-exit 0, held 110s). GATES, exit captured before any pipe, verdict lines quoted from the gates themselves: pnpm check:doc-snippets exit 0 'Semantic phase: 637 of 637 block(s) judged, 0 failed.'; pnpm check:doc-fences exit 0 'every TypeScript block in 227 document(s) is fenced ts/tsx/typescript'; pnpm check:readme-exports exit 0 '538 self-imports judged (538 real, 0 wrong-path, 0 fabricated)'; pnpm check:control-bytes exit 0 'scanned 7057 tracked text file(s); skipped 85 binary', plus a targeted control-byte self-scan of the edited file (grep -naP over the C0 classes, no match). node scripts/check-changeset-presence.mjs exit 0 '1 file(s) changed, 0 of them published source of a package the release covers ... no changeset is owed'. GOVERNED-SURFACE GUARD with a lit control: --test packages/plugin-dashboard/README.md exit 0 'NOT GOVERNED — 1 path(s) checked against 5 governed surface(s); none matched'; --test AGENTS.md exit 3 'GOVERNED — 1 of 1 path(s) are on a governed surface' so the guard's probe runs. ABLATION (the fence is new, so its green is worth nothing until it can be made red): from the COMMITTED state, SchemaRendererProvider renamed to SchemaRendererProviderZ inside the new fence only; on-disk proof BEFORE the run — marker count 0 to 1, worktree blob 09b920f81 to 5bcfff8f7 — then pnpm check:doc-snippets exit 1 with '[semantic] packages/plugin-dashboard/README.md:282:10 TS2724 ... has no exported member named SchemaRendererProviderZ' and 'Semantic phase: 637 of 637 block(s) judged, 1 failed.'. Restored with git checkout HEAD -- PATH (trap-guarded, absolute paths): git diff HEAD empty and the blob back to 09b920f81. WARNING, reported because it is the exact failure shape the on-disk proof exists to catch: the FIRST attempt at this ablation wrote NOTHING (its anchor matched twice and the assertion refused) and the gate stayed green at exit 0. NOT MEASURED locally, declared to CI: the repo-scale runs (pnpm lint, turbo test / type-check). No packages/*/src file is touched, the diff is one markdown file, and every gate whose scan surface contains packages/NAME/README.md was run above; check:doc-types and check:doc-example-types were NOT run because their own headers state package READMEs are outside their surfaces.",
  "mcp_calls": "0 — every GitHub read and write went through repo-scoped REST (session gate probed open, HTTP 200) plus git; no MCP GitHub call was made",
  "open_questions": [],
  "out_of_scope_findings": [
    "noted, not filed: the card's acceptance probe (a two-space `dataSource,` line) is a pattern, not a class predicate — it counts two correct constructs, a destructured prop and a call argument, as members. Whoever takes up the deferred gate question (ruling 2, blocked on objectui#7912's any-typed SchemaRendererProvider prop) inherits this: a text gate built on that pattern reddens react/README.md and plugin-report/README.md on day one. Carrier: objectui#7912, and the gate paragraph of #8468 itself.",
    "noted, not filed: the triage comment (5581939499) warned that plugin-gantt/README.md does not carry 'the repaired wording', while the PM ruling cites gantt:728. Both readings are true and they are about different sentences — gantt:726-731 carries the repaired FORM the dispatch quotes, and the exact sentence triage searched for ('The adapter is the `dataSource` prop, not part of the schema:') exists only at plugin-view/README.md:509. Recorded so the next reader does not re-litigate it. Carrier: this card's own thread."
  ]
}

Generated by Claude Code

⛔ 卡片正文的前提对三处中的两处为假 —— 我的验收标准继承了它

PR #8857（已 ready、auto-merge 已武装）修的是三处中的一处。另外两处不是这个缺陷，这是实测结论，不是取舍。

正文写的是：

Each reads, in shape:

const schema = { type: 'SOME_TYPE', dataSource, … };

这句对 react/README.md:234 和 plugin-report/README.md:523 为假。grep 找的 ^ dataSource,$ 是语法 pattern，它同时命中三种不同构造：

坐标	实际构造	判定
`plugin-dashboard/README.md:284`	`const schema = { type: 'dashboard', dataSource, … }` 的简写属性	缺陷 —— PR #8857 修复
`react/README.md:234`	`function ObjectSomething({ schema, dataSource }: { …; dataSource: DataSource })` 的解构 prop	正确 —— adapter 作为 prop 正是它该在的位置
`plugin-report/README.md:523`	`createScheduleTrigger(report, dataSource, 'orders', cb)` 的第二位置实参	正确

后两处已验到消费端：packages/plugin-report/src/LiveReportExporter.ts:245-249 的签名逐字是 (report, dataSource, resource, onComplete)；packages/types/src/reports.ts:407 更把这个 key 立了碑 —— dataSource?: never，注释指回 objectstack#5576 / objectui#6121。按正文那句去改，会把两处正确文档改成错误文档。

这一半的责任在派发端。 我在派发里把这句 grep 直接升格成了验收数字（「从 3 降到 0」），没有先问每个命中「是什么」。dev 拒绝执行并把测量送回，是对的；交付的读数换成了类判据：commit 之后，没有任何 packages/*/README.md 把 live adapter 写进 schema 对象字面量（简写与显式两种拼法、外加根 README.md 与 content/docs/** 都扫过，类内剩余为 0）。

门的问题：留给接手者的硬约束

正文把「是否值得建一个门」留给 triage，ruling 2 已把它延后到 objectui#7912 那个 any-typed SchemaRendererProvider prop 之后。现在它多一条实测约束：

任何建在 ^\s*dataSource,\s*$ 上的文本门，第一天就会把 react/README.md:234 和 plugin-report/README.md:523 判红。

接手的人需要的是类判据（「schema 字面量里的 live adapter」），不是这个 pattern。载体：objectui#7912，以及本卡的门那一段。

PR #8857 合并后本卡即结：一处已修，两处经测量不属于该类，门的问题按上面的约束留在 #7912 名下。

Generated by Claude Code

os-dev-report

{
"issue": 8468,
"status": "done",
"branch": "claude/issue-8468-readme-datasource-shorthand",
"pr": "#8857",
"premise_still_valid": true,
"summary": "Patch round on PR #8857, dequeued from the merge queue with CI_FAILURE. The fence the first round added to packages/plugin-dashboard/README.md carried the dashboard schema literal AND the provider/JSX wiring; readme-dashboard-examples-spec-valid.test.ts selects every fence matching both /const\s+schema\b/ and /type:\s*'dashboard'/ and evaluates it with new Function, which compiles neither a top-level export nor JSX. Per the ruling I split the section into two fences instead of widening toEvaluable(): fence 1 (typescript) holds the document alone and is still selected and still validated; fence 2 (tsx) holds its own imports, a declare const schema, the adapter construction and the provider wiring, and carries no type: 'dashboard' so the extractor does not select it. The provider example, the react/README.md and plugin-report/README.md non-edits, and the dataSource name-collision note are all unchanged. README only; one commit 2231007 fast-forwarded onto the existing branch, no rebase/amend/force-push, draft state and labels untouched.",
"tests": "BLOCK COUNT (the number that makes the guard meaningful, read from the test's own verbose run, not from the brief): 6 before, 6 after; the split did NOT change which fences are selected. Before (3f455b8): :48, :129, :178, :217, :257 pass, :282 Integration with Data Sources FAILS. After (2231007): :48, :129, :178, :217, :257, :283 all pass. Only the Integration block moved (282 -> 283, the prose above it grew); the new tsx fence is NOT selected -- the count stayed 6 rather than becoming 7, which is the observation that proves it, so nothing was hidden from the extractor. (1) TARGET TEST, via the container's shared verify lock, VERDICT command-exit 0: pnpm exec vitest run packages/plugin-dashboard/src/__tests__/readme-dashboard-examples-spec-valid.test.ts --reporter=verbose -> 'Test Files 1 passed (1) / Tests 7 passed (7)'. Same command before the fix reproduced CI exactly: 'Tests 1 failed | 6 passed (7)' with SyntaxError: Unexpected token 'export'. (2) WHOLE AFFECTED PACKAGE, run from the repo root as this repo's vitest guard prescribes (my first invocation --filter ... --root . was REJECTED BY THAT GUARD, exit 1 with MODULE-style wiring advice -- not a red gate, re-run correctly): pnpm exec vitest run packages/plugin-dashboard/ -> 'Test Files 100 passed (100) / Tests 890 passed (890)', VERDICT command-exit 0. (3) check:doc-snippets exit 0 after building its own --build-filter closure (turbo run build --concurrency=2, 35/35 tasks): 'Semantic phase: 638 of 638 block(s) judged, 0 failed.' The count moved 637 -> 638 precisely because one fence became two. BOTH FENCES JUDGED, proved not inferred: injecting ThisNameIsDefinitelyNotExported into EACH fence (on-disk proof first: blob fab0a7bc6 -> ed0a263f5, sentinel count 0 -> 2) made the gate exit 1 with exactly two failures, README.md:283:10 (inside fence 1) and README.md:306:10 (inside fence 2), 'Semantic phase: 638 of 638 block(s) judged, 2 failed'; restored by state, git diff HEAD empty and blob back to fab0a7bc6. (4) ABLATION from the committed tree at 2231007: the export/JSX was re-introduced into the SCHEMA fence only, fence 2 left in place, so the export/JSX is the single isolated variable. On-disk proof taken BEFORE the run -- HEAD blob fab0a7bc6fa04f94f34ba20b98ed1e587ce49eb3, post-mutation blob 094a1ff1729a93c6a5e989029674d3ed09d7370b, 'export const App' marker count 1 -> 2. The test then went RED BY TEST-CASE NAME: 'plugin-dashboard README dashboard examples > :283 Integration with Data Sources validates against the shipped DashboardComponentSchema' -> SyntaxError: Unexpected token 'export', 'Tests 1 failed | 6 passed (7)'. Restore verified BY STATE, not by an exit code: git checkout HEAD -- PATH, blob back to fab0a7bc6, git diff HEAD empty. Both mutation scripts carried trap RESTORE EXIT INT TERM with absolute paths and abort unless the edit anchor count is exactly 1, so a no-op ablation cannot report a result. (5) Re-run and unchanged, and per the dispatch these are blind to this failure and are NOT offered as evidence about it: check:control-bytes exit 0 (7057 tracked text files), check:doc-fences exit 0 (227 documents), check:readme-exports exit 0 (538 self-imports judged, 0 fabricated), check-changeset-presence exit 0 ('1 file(s) changed, 0 of them published source ...; no changeset is owed' -- measured, README.md is a .md and outside the gate's published-source surface). Plus my own control-byte scan of the README and of the PR body text, both clean. (6) CLAUSE-2 MEASURED THIS ROUND, not inherited: node scripts/check-governed-queue-guard.mjs --test packages/plugin-dashboard/README.md -> 'NOT GOVERNED -- 1 path(s) checked against 5 governed surface(s); none matched.' => Clause-2: no. NOT MEASURED / left to CI: the repo-level lint and type-check farms, and the full merge_group shard set. The dispatch's own point stands -- a green Test (shard N/4) on a markdown-only pull_request is not evidence the tests ran, so nothing here was taken from a check mark.",
"mcp_calls": "0 - no MCP GitHub call this run; the repo-scoped REST read probe returned 200, so reads and both writes (PR body PATCH, this comment) went through REST",
"open_questions": [],
"out_of_scope_findings": [
"noted, not filed: AMBIENT in readme-dashboard-examples-spec-valid.test.ts holds one entry, createObjectStackAdapter, and after this split no selected block uses it -- the schema fence is now pure data needing no ambient name. Harmless (unused new Function parameters) and the entry is that harness's documented extension point rather than dead weight, so it is left alone. Successor: whoever next adds a dashboard document fence to this README, who reads that list before adding to it.",
"noted, not filed: ci.yml:183-195 excludes **/.md from the pull_request full-run decision but short-circuits merge_group to should_run=true, so a markdown-only PR that breaks a test which READS a markdown file is only discovered at the queue, after the PR page has gone green. This is deliberate and the workflow says so in its own comment ('a merge_group build is the last validation before main'), so it is not a defect and not fileable under (a)/(b)/(c) -- recorded because it cost this card one dequeue. Successor: any dev whose diff is markdown-only and touches a document that a test reads; packages/plugin-dashboard/README.md and packages/plugin-gantt/README.md are both such documents today."
]
}

Generated by Claude Code

✅ 已落地 —— PR #8857 合并，`main` = `4c8e245e0`

按内容验证，⛔ 不按 sha，带亮着的对照灯：

SUBJECT   git grep -c 'The adapter is not a schema key' … plugin-dashboard/README.md   → 1
          git grep -n '^\s*dataSource,\s*$' … 'packages/*/README.md'                    → 3 → 2
            存活: plugin-report/README.md:523  ← createScheduleTrigger 的第二位置实参（正确）
                  react/README.md:234          ← 解构 prop（正确）
CONTROL   git grep -c 'dataSource' … plugin-gantt/README.md                             → 15，未被清洗
SPLIT     抽取器选中的围栏 6（门槛 6）· 其中带 export/JSX 的 0 · provider 例子在位

⭐ 对照灯是关键的一盏：gantt 那 15 处 dataSource 仍在，说明这不是「把 dataSource 一律清掉」，而是只动了那一处缺陷。

卡片结清的方式，与它被派出去时的设想不同 —— 这一点要留档

一处修复，两处经测量不是该类的成员：

坐标	实际构造	处置
`plugin-dashboard/README.md:284`	`const schema = { type: 'dashboard', dataSource, … }` 的简写属性	已修
`react/README.md:234`	解构 React prop	⛔ 未动 —— adapter 作为 prop 正是它该在的位置
`plugin-report/README.md:523`	`createScheduleTrigger(report, dataSource, …)` 的位置实参	⛔ 未动 —— 且 `packages/types/src/reports.ts:407` 把该键立碑为 `dataSource?: never`

⛔ 本席的验收标准（「3 → 0」）是错的，纠正已发在卡上（5604167621）与 PR 评审（5604160843）里，⛔ 此处只引用、不重新论证：那条探针是语法 pattern，命中三种不同构造，按它去改会把两处正确文档改成错误文档。交付的是类判据：commit 之后没有任何 packages/*/README.md 把 live adapter 写进 schema 对象字面量。

⚠️ 这张卡的落地过程本身产出了两条教训，都已归档

PR 第一轮被合并队列踢出（CI_FAILURE）。 新围栏里的 export / JSX 让 readme-dashboard-examples-spec-valid.test.ts 的 new Function 求值失败 —— 而那个测试读的就是这个 PR 改的文件。修法是拆围栏，⛔ 不是拓宽求值器。
⭐⭐ PR 页面全绿从来不是测试跑过的证据。 ci.yml:183-195 在 pull_request 上用 ':(exclude,glob)**/*.md' 排除 markdown-only 改动 ⇒ test shard 跳过（10 秒），merge_group 才真跑（907 秒并变红）。已单独立卡：objectui#8861。

门的问题：留给 objectui#7912 的硬约束

ruling 2 把「是否建门」延后到 objectui#7912 那个 any-typed SchemaRendererProvider prop 之后。接手者继承这条实测约束：

任何建在 ^\s*dataSource,\s*$ 上的文本门，第一天就会把 react/README.md:234 与 plugin-report/README.md:523 判红。

需要的是类判据（「schema 字面量里的 live adapter」），⛔ 不是这个 pattern。

关闭。

Generated by Claude Code

Navigation Menu

Repository navigation

finding(docs): three package READMEs still author the live `dataSource` adapter as a schema key — the defect objectui#5098 fixed in plugin-form, in `react`, `plugin-dashboard` and `plugin-report` #8468

What is true today

This class has been repaired one file at a time

What this suggests, without prescribing it

分诊路由 — `domain:ui` · `pm:queue` · `priority:p3` · type Task

复核 —— 三处站点在 `origin/main f76f4362` 上逐处命中

⚠️ 一处更正：`plugin-gantt` 没有卡所说的「已修复措辞」

⭐ 本卡的分量不在「三处冗余」，在那条命名碰撞

定级 — `priority:p3`

⭐ 路由裁定：一张卡覆盖三处，⛔ 不拆三张，⛔ 也不现在上门禁

承接提示 —— 照 `plugin-view` 的形式，两半都要

车道 — `domain:ui`

type = Task

本席自测的读数(全部成立,行号未漂)

⚠️ 这不是"多写了一个冗余键",这是名字撞车

裁决 ①(不可协商)—— 照抄已落地的判例措辞,⛔ 不要自创

⛔ 裁决 ② —— 不要加闸门

⛔ 裁决 ③ —— 只动这三个文件

验收 —— ⛔ 不许拿闸门当证据

⛔ 边界

⭐ 为什么这张 p3 值得一个位置

⛔ 卡片正文的前提对三处中的两处为假 —— 我的验收标准继承了它

门的问题：留给接手者的硬约束

✅ 已落地 —— PR #8857 合并，`main` = `4c8e245e0`

卡片结清的方式，与它被派出去时的设想不同 —— 这一点要留档

⚠️ 这张卡的落地过程本身产出了两条教训，都已归档

门的问题：留给 objectui#7912 的硬约束

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

finding(docs): three package READMEs still author the live dataSource adapter as a schema key — the defect objectui#5098 fixed in plugin-form, in react, plugin-dashboard and plugin-report #8468

Description

What is true today

This class has been repaired one file at a time

What this suggests, without prescribing it

Activity

os-zhuang commented on Sep 8, 2026

分诊路由 — domain:ui · pm:queue · priority:p3 · type Task

复核 —— 三处站点在 origin/main f76f4362 上逐处命中

⚠️ 一处更正：plugin-gantt 没有卡所说的「已修复措辞」

⭐ 本卡的分量不在「三处冗余」，在那条命名碰撞

定级 — priority:p3

⭐ 路由裁定：一张卡覆盖三处，⛔ 不拆三张，⛔ 也不现在上门禁

承接提示 —— 照 plugin-view 的形式，两半都要

车道 — domain:ui

type = Task

os-zhuang commented on Sep 9, 2026

本席自测的读数(全部成立,行号未漂)

⚠️ 这不是"多写了一个冗余键",这是名字撞车

裁决 ①(不可协商)—— 照抄已落地的判例措辞,⛔ 不要自创

⛔ 裁决 ② —— 不要加闸门

⛔ 裁决 ③ —— 只动这三个文件

验收 —— ⛔ 不许拿闸门当证据

⛔ 边界

⭐ 为什么这张 p3 值得一个位置

claude commented on Sep 9, 2026

os-zhuang commented on Sep 9, 2026

⛔ 卡片正文的前提对三处中的两处为假 —— 我的验收标准继承了它

门的问题：留给接手者的硬约束

claude commented on Sep 9, 2026

os-zhuang commented on Sep 9, 2026

✅ 已落地 —— PR #8857 合并，main = 4c8e245e0

卡片结清的方式，与它被派出去时的设想不同 —— 这一点要留档

⚠️ 这张卡的落地过程本身产出了两条教训，都已归档

门的问题：留给 objectui#7912 的硬约束

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

finding(docs): three package READMEs still author the live `dataSource` adapter as a schema key — the defect objectui#5098 fixed in plugin-form, in `react`, `plugin-dashboard` and `plugin-report` #8468

分诊路由 — `domain:ui` · `pm:queue` · `priority:p3` · type Task

复核 —— 三处站点在 `origin/main f76f4362` 上逐处命中

⚠️ 一处更正：`plugin-gantt` 没有卡所说的「已修复措辞」

定级 — `priority:p3`

承接提示 —— 照 `plugin-view` 的形式，两半都要

车道 — `domain:ui`

✅ 已落地 —— PR #8857 合并，`main` = `4c8e245e0`