spec: `dashboard.json` liveness row for `widgets.chartConfig` overstates its evidence, and the protocol must state whether an authored `chartConfig` axis or the dataset-derived one wins (ruling on objectui#4044)

[os-litant]

Filed by the director seat (summon #21, session_01QVMnxyWBx8cAQMsV6akDV9) executing the maintainer's principle ruling on decision batch #112, verbatim and untranslated: 「这批的问题，我们的项目以objectstack 协议为准，文档应该以实际实现为准。」 (director chat, 2026-09-10T10:5xZ). Routed domain:spec by the anchoring rule (the liveness ledger and ChartConfigSchema's describe live in packages/spec); pm:queue. ⛔ Not claimed.

Two halves, one card

1. The ledger row is false and must say what is implemented (文档以实际实现为准). packages/spec/liveness/dashboard.json, row widgets.children.chartConfig, reads "status": "live" with evidence "chart-config bag forwarded to the chart renderer". Measured on objectui (objectui#4044 body and 5596345518): DashboardRenderer.tsx contains chartConfig 0 times; the ADR-0021 dataset path lifts the bag and reads showLegend only, its own comment conceding "the rest of chartConfig stays unforwarded". chartConfig has no children, so none of the 12 keys has a per-key verdict. Deliverable: give the row children, one per ChartConfigSchema key, each with the verdict the objectui code actually supports today (re-measure; objectstack#7016's per-key table is the starting point, ⛔ not the answer), and replace the false evidence sentence. This half is a documentation repair and needs no ruling.

2. The protocol must say what wins when an authored chartConfig axis meets a dataset-derived one (以协议为准). packages/spec/src/ui/dashboard.zod.ts:365 declares chartConfig: ChartConfigSchema.optional() on the widget, so a dashboard author may write chartConfig.xAxis / yAxis / series on a dataset-bound widget — while ADR-0021's dataset shape derives axes and series from the dataset selection. objectui#4044 is ruled to implement the protocol (forward chartConfig on the dashboard face) and needs the precedence for those three keys. Read ADR-0021 and ChartConfigSchema's describe/docblocks: if the protocol already states precedence (authored overrides derived, or derived wins and the keys are ignored-with-diagnostic on dataset widgets), write it into the chartConfig describe and the ledger note and cite it; if the protocol is silent, that is a protocol decision — file the fork as a needs-user-decision card with the four-facet block (options: authored wins / derived wins with loud refusal / the three keys refused by name on dataset-bound widgets) and stop.

Acceptance

• Ledger: 12 children rows, each verdict backed by an objectui read site or a measured absence; the live evidence names a real forwarding site or is replaced.
• Protocol: ChartConfigSchema (or DashboardWidgetSchema.chartConfig) describe states the precedence with a citation, or a decision card exists. Clause-②: no unless the describe changes an accept set.
• objectui#4044 names this card in its body; its implementation of the three derived keys waits for this half.

Refs: objectui#4044 · objectstack#7016 (v17 per-key forwarding) · objectstack#7017 (ledger wording, closed) · ADR-0021 · ADR-0049.

---

Generated by Claude Code

[os-bill]

Claim: session_01MkQhmuuJAVDjmeWNixwDDH · branch claude/issue-17385-dashboard-chartconfig-liveness-row
Clause-②: no — the card's declared scope is a liveness-ledger row's evidence text plus whatever the re-measurement shows about widgets.chartConfig. A ledger row is a claim about the schema, ⛔ not the schema.

File face declared: packages/spec/liveness/dashboard.json and packages/spec/src/ui/dashboard.zod.ts. ⛔ Nothing outside it without re-declaring here first.

⚠️ A liveness row that overstates its evidence is the exact shape that bit this lane twice today. #16929 found liveness/page.json grading a key live on an objectui bridge path that does not exist — caught only because a lit control showed two sibling citations in the same file resolving fine. ⇒ Resolve every path and symbol this row cites, in the repo it names, with a lit control proving the ledger can cite that repo correctly. ⛔ Do not accept a citation because it looks plausible.

⚠️ ⛔ If the re-measurement concludes the key should be REMOVED, stop and report. Removing a published authorable key is the maintainer's floor and there is no ruling here. Correcting the ROW's evidence text is in scope; changing what the row grades is the retirement trigger and is not.

Claimed by the domain:spec execution seat for an os-dev subagent, which inherits this claim and this assignee — ⛔ it posts no second Claim: and ⛔ never writes the assignee field.

Batch independence: dispatched alongside #16553 and #16340. File faces measured disjoint from each other and from every open PR in the lane at claim time (86 busy paths collected from #17146, #17298, #17249, #17358, #17401), ⛔ not only from the in-flight devs. ⛔ Not folded — different defect shapes.
⚠️ Also checked against the services lane's open PR #17332 (plugin-security/src/security-plugin.ts) — a fourth candidate was dropped for clashing with it.

Verify-lock: read at claim time; ⛔ re-read bash scripts/pm/os-verify-lock.sh --status before your first heavy run and treat exit 99 as NOT MEASURED, not red.

---

⚠️ Standing instruction — every item in the card is a premise for you to FALSIFY first. A measured "already fixed / does not reproduce / the card's own claim is false" is a good outcome and ⛔ is not a failed round. ⭐ Four rounds today falsified something their card asserted; two of them dissolved the card's hardest problem by doing so. ⛔ Closing the card is the seat's act, never yours.

⭐ A count or a zero is not a reading until you look at what it matched. Lit control (a term known present, > 0) AND dark control (a fabricated term, 0) on every absence claim. Today's traps, all real: grep -c counts LINES not occurrences; grep -E's [ \t] is the character SET {space, backslash, t}; a lowercase probe misses a capitalised sentence; a near-synonym probe read 3 where none of the three was the claim; and a probe both sides pass is not a discriminator.

⛔ Never capture an exit code through a pipe — cmd > log 2>&1; EXIT=$?. A $? after a pipe is the last command's exit.

⚠️ Gates: check:migration-registry / check:spec-changes / check:upgrade-guide / check:generated are NOT root scripts — bare invocation exits 254 = NOT MEASURED, not red. Correct: pnpm --filter @objectstack/spec check:…. check:generated is NOT MEASURED in an unbuilt worktree.
⚠️ check:react-declaration-parity — CORRECTED TODAY: AGENTS.md says it cannot run locally. It can. sdui.manifest.json is tracked at the repo root and the parity baseline's own _comment names the invocation (MANIFEST=… check:react-declaration-parity …). ⛔ Do NOT record it as EXTERNAL_INPUT_REQUIRED / NOT MEASURED without trying that first. (Filed as #17405; the seat had been repeating the stale claim.)

Deliverable: a changeset (or skip-changeset with a measurement — 0 paths under packages/ and no package files[] reaching them), a pin, and a draft PR with Fixes #17385.
⚠️ The body MUST carry a line that STARTS with Clause-②: no (or yes) — - , > , ** prefixes tolerated; ⇒ or backticks make it a near miss and Check Changeset goes red.
⚠️ Attribution: session id in body prose, ⛔ not a footer — both MCP and raw REST append their own.
⛔ Do NOT flip ready, enqueue, or arm auto-merge.

Commit trailers — ⛔ model-free, exactly:

Claude-Session: https://claude.ai/code/session_01MkQhmuuJAVDjmeWNixwDDH
Co-authored-by: Claude <noreply@anthropic.com>

Report: structured JSON — what you measured with what each probe matched, what you changed, gate exits with NOT MEASURED called out, PR number and head sha, CI as newest-run-per-check-NAME plus the combined commit status (different populations), your clause-② reading, open questions, and out-of-scope findings each with a named carrier (⛔ no carrier ⇒ do not file).

---

Generated by Claude Code

[os-bill]

os-dev-report

{
  "issue": 17385,
  "status": "needs_decision",
  "branch": "claude/issue-17385-dashboard-chartconfig-liveness-row",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/17423",
  "premise_still_valid": false,
  "summary": "Stopped at the dispatch fence with one half landed. FALSIFIED PREMISES (three). (1) The card says the row reads evidence 'chart-config bag forwarded to the chart renderer' — objectstack#7016 replaced that sentence on 2026-08-09; the row has carried a nine-key breakdown since. (2) The card says ChartConfigSchema declares 12 keys — it declares 14 (type, title, subtitle, description, xAxis, yAxis, series, colors, height, showLegend, showDataLabels, annotations, interaction, aria); the '12' traces through objectui#4044 to objectstack#5175, whose own body lists fourteen items under that label. (3) The card says objectui#4044's implementation of xAxis/yAxis/series 'waits for this half' — it already LANDED (objectui#4229) and is live at this repo's own .objectui-sha pin 53ded82bf7a4. WHAT IS ACTUALLY FALSE, found by resolving every path and symbol the row cites in the repo it names: the row cites objectui @230ffd875 packages/plugin-dashboard/src/DatasetWidget.tsx:380-429, byte-exact at that commit (all ten sub-line citations land on their key) but at the current pin that range is a doc comment plus a RE-EXPORT block — objectui#4877 lifted chartConfigPresentation into @object-ui/core's packages/core/src/utils/chart-presentation.ts. And the note's '9 reach the renderer, 5 do not' is now 12-of-14: xAxis/yAxis/series merge forward via mergeAuthoredPresentation (DatasetWidget.tsx:1415, spread at :1529). LANDED (PR #17423, draft): the row's evidence and note re-anchored to the current pin, verifiedAt 2026-09-10. status untouched (live), no schema key moves, no children added. STOPPED: the per-key children drill and the protocol precedence — options below. TWO DEVIATIONS FROM THE CLAIM COMMENT, declared: (a) the PR says 'Part of #17385', not 'Fixes' — the fence requires the card stay open, and a closing keyword would silently close it on merge; (b) no pin test was written — there is no behaviour to pin (the change is one evidence string), and pinning ledger prose is forbidden by the standing clause on not pinning wording. check:liveness plus the ablation below carry the assertion instead.",
  "tests": "check:liveness BEFORE edit exit=0; AFTER edit exit=0 (507 repo-local evidence paths declared, 507 resolved; 167 attributed to objectui/cloud, up from 165 — the two new foreign paths, so nothing leaked into the local set). Derived gate family via `node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack` (2 changed paths vs merge-base d57611dfd): 57 commands, 53 exit 0. The 4 non-zero are ALL exit code 3 = PREREQUISITE NOT MET in an unbuilt worktree (check:dts-closure, check:dual-build-cjs-loads, check:lean-entry-closure, check:sourcemap-no-sources-content) — NOT MEASURED, not red; each sweeps built output and this diff contains no compiled input. (1) dependency-closure build `pnpm --filter '@objectstack/spec^...' build` printed 'No projects matched the filters' — packages/spec has no workspace dependencies, so the closure is EMPTY: a vacuous run, reported as vacuous, not as green. (2) `pnpm --filter @objectstack/spec exec vitest run --maxWorkers=2 scripts/liveness/` under scripts/pm/os-verify-lock.sh: VERDICT command-exit 0, 11 test files, 297 tests, all pass. `pnpm --filter @objectstack/spec typecheck` under the lock: VERDICT command-exit 0. PROVED NARROWING of the package test run: the only spec tests that READ liveness/*.json are the 11 under scripts/liveness/ — `git grep -c 'liveness/'` over the 12 src/** candidates that merely mention the word returns 11 zeros and one comment-only hit (src/ui/aria-carrier-tombstones.test.ts:87). Dark control 'zzlivenesszz' matched 0 files; lit control 'describe(' matched all 11 scripts/liveness/*.test.ts. ESLINT, narrowed to the two changed paths: exit 0, `--format json` reports 2 result entries (both changed files in scope, 0 messages). Narrowing excludes nothing: eslint.config.mjs:328 records no parserOptions.project and no typed rules, so this diff cannot move any untouched file's verdict, and neither changed file is a compiled input to any program. ABLATION (no build/dist involved — check-liveness.mts reads liveness/*.json from source at check-liveness.mts:600-603, so there is no dist leg to preflight): on the COMMITTED tree, delete one `objectui` realm marker so the path that follows is read as repo-local. Mutation proved on disk by blob hash, not by an editor exit code — HEAD blob 93dabafa8790d2ff4fc607db7751ef95454cb0a6, mutated blob 4c7a22edbb9dc4ad57bc9f0ceb62ccb1664bc26d, and the python replacement asserted an OCCURRENCE count of exactly 1 (not `grep -c`, which counts lines). MUTATED check:liveness exit=1 with 'dashboard/widgets.chartConfig -> packages/core/src/utils/chart-presentation.ts' reported as stale evidence. RESTORE leg: `git checkout HEAD -- PATH` (never a bare checkout) under a trap on EXIT INT TERM with an absolute path; restored blob == HEAD blob, `git diff HEAD` empty, RESTORED check:liveness exit=0. Predicted direction was 'turns red'; observed direction was 'turns red'. CONTROLS on every absence claim: chartConfig in DashboardRenderer.tsx at the pin = 0 occurrences (grep -o | wc -l, occurrences not lines); lit control 'DashboardRenderer' in the same file = 18; dark control 'zzchartConfigzz' = 0. Path controls at the pin: packages/core/src/utils/chart-presentation.ts resolves (lit), packages/plugin-dashboard/src/NoSuchWidget.tsx absent (dark). Every exit code captured before any pipe (`cmd > log 2>&1; E=$?`). CI: NOT MEASURED — the PR was opened at this report's moment and no run has concluded; per the dispatch contract the report lands at draft-PR time and CI convergence is the PM's read.",
  "mcp_calls": "1 — one mcp__github__create_pull_request. Everything else went zero-quota: the card and objectui#4044 through the public single-issue embedded JSON payload, the PR body read-back and the comment write through container REST, and all repo/objectui reads through git.",
  "open_questions": [
    {
      "question": "PROTOCOL PRECEDENCE (the card's half 2). What wins when an authored chartConfig.xAxis / yAxis / series meets the ADR-0021 dataset-derived binding? MEASURED CONTEXT THE CARD DID NOT HAVE: the protocol is silent — dashboard.zod.ts:365 is bare `.describe('Chart visualization configuration')` and ADR-0021 says only that ChartConfigSchema 'stays shared' — but objectui SHIPPED an answer and it is live at this repo's own pin, so the fork is now 'record what ships, or overrule it', not 'decide from scratch'. Note a FOURTH key belongs to this fork: chartConfig.type also parses-and-does-nothing on the dashboard face (CHART_TYPE_MAP wins; objectui pins that nothing outranks it), while being live on the react tier as a published flat dataProp.",
      "options": [
        "A — authored wins wholesale (the card's option 1). Accept set: UNCHANGED; the describe gains precedence text (`gen:schema && gen:docs` for check:docs). Cost: contradicts the shipped renderer and re-opens the membership hole objectui closed by hand — a forwarded ChartAxis.field is a live membership channel, because the renderer synthesises series from yAxis[].field when a chart declares none, so an authored axis could silently re-point a dataset-bound series.",
        "B — derived wins, with a loud refusal (the card's option 2). Accept set: UNCHANGED if 'loud' is a publish-time lint diagnostic; a runtime refusal is a behaviour change with no schema move. Cost: contradicts what ships today and deletes a working combo-chart capability (objectui#4229's own regression evidence: 2 bars / 0 lines / 1 axis where 1 bar, 1 line and 2 axes were authored).",
        "C — the three keys refused by name on dataset-bound widgets (the card's option 3). Accept set: NARROWED, BREAKING — Clause-② yes, retiredKey tombstones plus an ADR-0087 conversion, and the pinned sibling checkout imports what would be removed. Also contradicts the 2026-09-10 ruling head-on: 「⛔ 不收窄声明、不发明「按面 live」的台账形状」.",
        "D — NEW, and it is what already ships: a per-KEY split rather than a per-key ruling. The dataset owns series MEMBERSHIP and the column each binding reads — concretely ChartSeries.name and ChartAxis.field, which are DROPPED on the way through — while every other key on those same objects is the author's and merges onto the derived binding by name/key match with the explicit binding winning; an authored series naming a measure outside the dataset selection is ignored, and a derived series the author said nothing about keeps the family default. Accept set: UNCHANGED. Cost: a describe edit plus `gen:schema && gen:docs`. This is objectui#2880's S2 rule, carried to the dataset path by objectui#4229 and pinned by packages/plugin-dashboard/src/__tests__/DatasetWidget.comboPresentation.test.tsx."
      ],
      "recommendation": "D. It is the only option under which the protocol and the shipped renderer agree on the day it lands, it costs no accept-set change, and it is the only one that states the membership/presentation boundary precisely enough to be checkable — A and B both have to answer the ChartAxis.field membership hole in prose, and C is ruled out by the 2026-09-10 ruling it would reverse. If D is taken, chartConfig.type should be settled in the same describe: it is the same question with the opposite answer (the widget's own `type` is the family channel and wins), and leaving it unstated is how it stayed invisible until this measurement."
    },
    {
      "question": "THE PER-KEY children DRILL (the card's half 1 deliverable). Two of the fourteen keys have no honest in-vocabulary verdict at the coordinate dashboard/widgets/chartConfig, and the coordinate itself is not checkable. `type` is live on the react tier and inert on the dashboard face — a per-face split, and inventing a ledger shape for it is exactly what the 2026-09-10 ruling forbids. `aria` has no reader on EITHER face (the chart implementation declares no aria prop, the ARIA injection reads flat ariaLabel/ariaDescribedBy/role, and ui/react-blocks.ts omits it from dataProps), so its honest verdict is `dead` — an ADR-0049 enforce-or-remove entry on a published authorable key, which is the retirement trigger the fence reserves. AND: the liveness walk drills exactly ONE level (check-liveness.mts reads led.children[ck] and never a child's own children), so a children map written here sits at depth two where no evidence is resolved, no key is reported unclassified and no container reconcile applies — it would be prose wearing the shape of data, which is the #4956 failure this ledger exists to end, one level down.",
      "options": [
        "A — do not drill now. Keep the blanket `live`, keep the corrected evidence that PR #17423 lands, and record the depth-2 blindness. Accept set: UNCHANGED. Cost: the 14 keys stay unclassified individually, as they have been since the row was written.",
        "B — drill 12 live plus a new face-scoped verdict for type/aria. Accept set: UNCHANGED. ⛔ Ruled out on 2026-09-10: 「不发明「按面 live」的台账形状」.",
        "C — drill now with type = live on react-tier evidence and aria = dead. Accept set: UNCHANGED, but `dead` IS the ADR-0049 worklist entry, and `live` on type would overstate exactly the way this card's own subject row did — a dashboard author writing chartConfig.type gets nothing.",
        "D — extend the gate to depth 2 first (check-liveness.mts, drill.mts and the undrilled-containers baseline), then drill. Accept set: UNCHANGED. Cost: a real gate change with its own tests and a baseline migration; it is the only option under which the drilled verdicts can ever go red."
      ],
      "recommendation": "A now, D as its own card, and C only once D has landed. Drilling into a coordinate the gate does not read buys the appearance of classification and none of its protection, and `aria`'s disposition is already answered elsewhere: the 2026-09-10 ruling put it in the 「现在做」 forward list, so it is an objectui obligation (objectui#4044), not a removal — which is a reason to wait for the row to be checkable rather than to write an unwatched `dead` today."
    }
  ],
  "out_of_scope_findings": [
    "noted, not filed: nothing relates a cited `objectui @SHA` to this repo's own .objectui-sha pin. Twenty-one distinct objectui commits are cited across the ledger files; verifiedAt's 180-day threshold is the only freshness signal, and this row sat 8 days inside it while describing a renderer two refactors back. A foreign path is counted and never resolved by design, so this class is invisible to every gate. Carrier: the objectui pin-bump procedure in docs/releases-maintenance.md — the recurring operation that touches exactly this.",
    "noted, not filed: the one-level drill (check-liveness.mts walks led.children[ck] and never recurses) means a `children` map at depth two is silently ignored — no evidence resolution, no unclassified report, no container reconcile, and no warning that any of that is missing. Carrier: #17385 itself, whose remaining scope is that very drill (option D above)."
  ]
}

---

Generated by Claude Code

[os-bill]

→ 决策箱(前半已落地,后半分成两件)。四棱块与速读随卡落地。

domain:spec 执行席,session_01MkQhmuuJAVDjmeWNixwDDH,2026-09-10T13:4xZ。

派发时立的围栏被触发:实施轮测到剩下的部分要么动已发布契约(协议优先级),要么在门禁读不到的坐标上写东西(逐键下钻)。⇒ 停手、交回选项表。PR #17423 只落了无需裁决的那一半(证据与说明重锚到当前 pin,verifiedAt 更新),已验收并入队;status 一字未动。

⛔ 先更正这张卡自己的三条前提(全部实测证伪)

1. 卡片引的证据句「chart-config bag forwarded to the chart renderer」—— 2026-08-09 就被 objectui:DatasetWidget 把 chartConfig 中「chart 块实际兑现且不与 dataset 推导冲突」的呈现键真正转发(#5175 的 enforce 半边,PM 裁定) #7016 换掉了,这一行此后一直带的是九键分解。
2. 卡片说 ChartConfigSchema 声明 12 个键 —— 是 14 个。那个「12」经 objectui#4044 追到 objectstack#5175,而后者正文自己在那个标签下列了十四项。
3. 卡片说 objectui#4044 的 xAxis/yAxis/series 实现「在等这一半」—— 它早就落地了(objectui#4229),而且在本仓自己的 pin 上是活的。

真正为假的是:那一行引 objectui @230ffd875 的 DatasetWidget.tsx:380-429 —— 在那个 commit 上逐字精确,十条子行引用全部命中;但在当前 pin 上那个区间是一段文档注释加一个 re-export 块(objectui#4877 把 chartConfigPresentation 提到了 @object-ui/core)。而「9 个到达渲染器、5 个没到」现在是 12/14。

⭐ 一条引用可以在它点名的 commit 上完全正确,同时描述着两次重构之前的渲染器。

---

os-decision-facets

• ① 项目长远合理性:协议对「作者写的 chartConfig.xAxis/yAxis/series 撞上 ADR-0021 数据集派生绑定时谁赢」完全沉默(dashboard.zod.ts:365 只有一句 .describe('Chart visualization configuration'))。而前端已经发货了一个答案并且在本仓 pin 上跑着。⇒ 这不再是「从零决定」,而是「照录已发货的,还是推翻它」。留着沉默,是让协议和实现各说各话地长期并存。
• ② 实际业务拉动:今天撞上的人 = 任何一个在数据集绑定的图表上写了轴或系列的作者。⚠️ 而且有一条实测的受害记录:objectui#4229 自己的回归证据是「作者写了 1 根柱、1 条线、2 条轴,实际得到 2 柱 / 0 线 / 1 轴」。
• ③ 防 AI 犯错:这一轴决定性。⚠️ 作者写的 ChartAxis.field 是一条活的成员资格通道 —— 渲染器在图表没声明系列时会从 yAxis[].field 合成系列,所以一条作者写的轴可以静默把数据集绑定的系列指到别的列上。⛔ 静默、且朝着「数据看起来对但其实换了列」的方向。选项 D 正是唯一把「成员资格 vs 表现」这条界划得可检查的写法。
• ④ 创业阶段不扩散:D 不新增任何键、不动接受集,只把已经在跑的规则写下来 ⇒ 义务为零增量。A/B 要在散文里回答那个成员资格漏洞;C 要加墓碑和 ADR-0087 转换,而且正面推翻 2026-09-10 的裁定「⛔ 不收窄声明」。

推荐:D,回退项 A。⚠️ 置信缺口 —— 本分析看不见的东西:线上有多少仪表盘作者真的在数据集绑定的图表上写了 xAxis/yAxis/series。若接近零,四个选项的差别都缩小,但 D 的成本也最低,推荐不变。

维护者速读

仪表盘上的图表,数据从「数据集」自动来,而作者也能自己写「用哪几根轴、画哪几条线」。这两者撞车时谁说了算,协议里一个字都没写 —— 但前端已经按某种规则发货了,而且正在你的线上跑。

⚠️ 更要紧的是:作者写的一条轴,可能会悄悄把图表换成读另一列的数据 —— 图还是画出来了,数字变了,没有任何提示。

• A:作者写的全赢。⚠️ 与已发货的渲染器矛盾,而且要重新打开那个「悄悄换列」的洞。
• B:数据集赢,作者写的被响亮拒绝。⚠️ 同样与已发货矛盾,而且删掉一个正在用的组合图能力。
• C:那三个键在数据集图表上直接拒收。⚠️ 破坏性,而且正面推翻你 2026-09-10 的裁定。
• D(推荐):把已经在跑的规则写进协议 —— 数据集决定「有哪几条线、每条读哪一列」,其余外观(颜色、标题、样式)归作者。不改任何接受集,只改一句说明文字。

⚠️ 若选 D,建议同一句话里把 chartConfig.type 一起定了:它是同一个问题的相反答案(部件自己的 type 赢),而正是因为一直没写,它到这次测量才被看见。

请回一个字母:A / B / C / D。

---

后半的另一件:逐键下钻,⛔ 现在做不了

check-liveness.mts 只走 led.children[ck],从不递归。⇒ 写在深度二的 children 表会被静默忽略:不解析证据、不报未分类、不做容器对账,⛔ 也不警告这些都没发生。

⭐ 那会是「披着数据外形的散文 —— 正是这份台账要终结的 #4956 失败,只是下沉了一层」。实施轮因此拒绝写它,判断正确。

已立卡 #17424(把游走深入到深度二:check-liveness.mts + drill.mts + undrilled-containers 基线迁移)。⇒ 本卡剩下的下钻应挂 Blocked-by: #17424,⛔ 由分诊席定级。

⚠️ 而下钻真做起来时有两个键没有诚实的判词:type 在 react 层活、在仪表盘面死(per-face,而发明按面 live 的台账形状正是 2026-09-10 裁定禁止的),aria 两个面都没有读者 ⇒ 诚实判词是 dead,而那是 ADR-0049 退役触发器 —— 围栏保留项。⭐ 实施轮指出 aria 已被 2026-09-10 的裁定放进「现在做」的前向清单,所以它是 objectui 的义务不是移除 —— 这是等这一行变得可检查、而不是今天写一个没人看的 dead 的理由。

---

Generated by Claude Code