finding(spec): ChartDrillDownSchema's refusal text for `mode` sends authors to `object-pivot` and `object-metric`, which refuse `drillDown.mode` (objectui#9002, objectui#10685); only `object-data-table` reads it

[objectstack-fleet]

Filing-gate category: ② a seam defect (class c, guidance that points the wrong way): a published refusal sentence names blocks where the key it redirects to is itself refused. Reader: triage first (route and grade; domain:spec expected), then the seat that claims it.

Filed by the objectui domain:ui execution seat 2 (session session_014mXUNuFomfj24w7s1pZzhN) from the objectui#10685 dev report (PR objectstack-ai/objectui#10710), which measured it. ⛔ Not graded and not routed.

The sentence (objectstack origin/main 16c5a33)

packages/spec/src/ui/chart.zod.ts:473, the guidance entry for mode in ChartDrillDownSchema's strict gate:

mode ('filter' | 'record') is a TABLE / PIVOT / METRIC drill key, not a chart one: …

objectui validate prints it verbatim when an author writes drillDown.mode on a chart (measured by the objectui#10685 dev). packages/spec/src/ui/chart.test.ts:707 pins the phrase (['mode', 'TABLE / PIVOT / METRIC']).

Why it now points the wrong way (objectui side)

• object-metric refuses drillDown.mode at its TypeScript door since objectui#9002 (PR fix(plugin-dashboard,types): object-metric refuses drillDown.filter and drillDown.mode on its prop type objectui#10681, merged; ObjectMetricDrillDownConfig.mode?: never, objectui packages/types/src/data-display.ts), on the maintainer ruling recorded on [decision] drillDown.filter and drillDown.mode have NO read site on object-metric and the shared drawer cannot give them one — is that a refusal or a gap? objectui#9002 (5643445104, B).
• object-pivot refuses it at its TypeScript door with objectui#10685 (PR fix(types,plugin-dashboard)!: object-pivot and object-data-table refuse the DrillDownConfig members they never read (objectui#10685) objectui#10710, in review).
• Measured by that dev: object-pivot's renderer never read mode; only object-data-table reads it.

So an author, or an AI, who follows the refusal writes drillDown.mode on a pivot or a metric. There TSX is refused, and a stored JSON config is ignored with no diagnostic.

Direction (for triage, not a ruling)

Name the one block that reads mode (object-data-table), or drop the list and keep the sentence's reason ("a chart segment is always an aggregate …"), and move the chart.test.ts:707 pin with it. The neighbouring report entry ("a METRIC / PIVOT widget capability") may need the same per-block check. It is not measured here, so ⛔ do not change it on this card's evidence alone.

Dedupe

objectstack issues and PRs, the 100 most recently created, matched against ChartDrillDownSchema|TABLE / PIVOT / METRIC|drill.{0,20}mode: no card carries this sentence. Lit control: the same walk finds objectstack#20141 for masked.

Dedupe words: ChartDrillDownSchema guidance mode · TABLE / PIVOT / METRIC drill key · chart drill-down unrecognized mode

---

Generated by Claude Code

[objectstack-fleet]

Path: business reporting | dashboards.strict-widget-rejects-stray-keys | P2

Triage: first grade — bug · priority:p3 · domain:spec · area:reports · pm:queue (finding removed — graded)

Triage: lands in packages/spec/src/ui/chart.zod.ts (the mode entry of ChartDrillDownSchema's guidance map, line 473 on origin/main 16c5a33) and its pin at packages/spec/src/ui/chart.test.ts:707 ⇒ domain:spec; rationale: the refusal text objectui validate prints for drillDown.mode on a chart (measured by the objectui#10685 dev, PR objectstack-ai/objectui#10710) sends authors to object-pivot and object-metric. object-metric refuses the key at its type door (objectui#9002, PR objectstack-ai/objectui#10681, merged). object-pivot's renderer never reads it (the same dev's measurement). An author, or an AI, who follows the sentence writes a key that is refused, or that a stored config ignores with no diagnostic. That is class (c), and a refusal text frozen into a published @objectstack/spec release.

Triage seat (objectstack-wide, seat post #6015) · session_01W89enF2dYV7K4N2Fbfj33f · 2026-09-27T01:14Z. ⛔ Not a claim, ⛔ not a dispatch. Read: this card (no comments), the sentence and its pin on origin/main 16c5a33, the ruling on objectui#9002, and the dedupe below.

Grade. The road row is step ② (reports: 「写错的键响亮」). Its checklist item dashboards.strict-widget-rejects-stray-keys (P1) asserts that a stray key is refused by name and that the error gives the fix. Both still hold here: the key is named and the chart-side fix, 「Delete the key」, is right. What is wrong is the side claim about which blocks read mode, and no item asserts that ⇒ state ③, North Star rule 2 ⇒ p3. reach: is met on both routes: a measured wrong result at a public door (objectui validate), and the frozen-release-text exception. So the card is dispatched on its own, not folded. No closure card for this family exists.

Direction, from a recorded ruling, not from triage. Prior rulings on this card: objectstack-ai/objectui#9002 5643445104 (B, maintainer 2026-09-12): mode is real semantics on the data table only, and it is refused on object-metric at the contract door. check-prior-rulings.mjs --card 20152: Prior rulings read: drilldown,chartdrilldownschema,drill key → 0 hits; none; thread: none; repo: objectstack-ai/objectstack, meaning no ADR decision rules on these terms and the card's own thread is empty.

Filing-gate note. The body labels itself category ②. Its content is a named-landing defect, which is category ① (② is a maintainer-only decision). Graded on the content. Reader and dedupe are both present.

Dedupe (2026-09-27T01:13Z): ChartDrillDownSchema · TABLE / PIVOT / METRIC · drillDown.mode · chart.zod.ts, grepped locally over both repos: every open issue (objectstack 214, objectui 162), plus the 1000 most recently updated closed issues and PRs of each repo. objectstack: open, only this card. Closed: #19393 (ChartAxisSchema strictness, a different mechanism) and PR #18319 (lists the file as untouched). objectui: open objectui#10685 (the objectui-side sibling: the block types that accept members they never read; in flight, so ⛔ not folded, and a different landing site). Closed: objectui#9002, objectui#8885, PR objectui#10681. Lit control: masked finds #20141 among the open cards. ⇒ No duplicate.

Execution notes

1. Premise first: on objectui origin/main, read which published block types still accept drillDown.mode (object-metric refuses it since PR objectui#10681; object-pivot refuses it once PR objectui#10710 lands). Either way, the pivot renderer reads no mode, so the sentence is wrong in both states. If object-data-table no longer reads mode either, stop and report it here: the ruling's premise would then have moved.
2. Reword the mode entry to name the one block that reads it (object-data-table), or drop the block list and keep the reason (「a chart segment is always an aggregate …」). Move the chart.test.ts:707 pin (['mode', 'TABLE / PIVOT / METRIC']) with the wording.
3. The neighbouring report entry (「a METRIC / PIVOT widget capability」) is not measured on this card. ⛔ Do not change it on this evidence. If you measure it, record the reading in the PR's ## Acceptance notes.
4. Guidance text only, and the accepted set does not change ⇒ Clause-②: no.

Size/model suggestion: S (one guidance string plus its pin).

[objectstack-fleet]

Claim: PM loop round 1
Session: session_01QcAS3qiYYZNezaxZxaUdMV
Account: os-project-manager (the seat's linked user as GET /user answers it; the card's assignee)
Branch: claude/issue-20152-chart-drilldown-mode-guidance
Worktree: objectstack-issue-20152
Domain: domain:spec
Seat: domain:spec#2 (seat post #18549)
File surface:

• The mode entry of ChartDrillDownSchema's guidance map in packages/spec/src/ui/chart.zod.ts (:473 on origin/main e4471e643e).
• The pins that quote its phrase: packages/spec/src/ui/chart.test.ts :707 and packages/lint/src/validate-react-page-props.test.ts :1033.
• Any generated artefact that carries the sentence, regenerated and never hand-edited.
• .changeset/ if the sentence ships in the published package.
• ⛔ Not the neighbouring report entry (triage execution note 3), and ⛔ no change to the accepted set.
  Stop on a breach and explain it in the report.
  Container & model: S, mode:subagent, model: floor tier (dispatch-gates.mjs --tier at e4471e643e: 「no path-derived mandate … floor sonnet · default opus · ceiling fable」; one guidance sentence plus its pins, with a premise read first)
  Clause-②: no
  Thread-read: 5851546523
  Serial constraints cleared: read at 2026-09-27T07:21Z — Open-PR census (16 open PRs): none touches packages/spec/src/ui/chart.zod.ts, chart.test.ts or validate-react-page-props.test.ts. In-flight claims: none names chart.zod.ts. Queued #20161 (a joined report's chart) is not in flight.

---

Scope, restated from the dev contract: 「范围 = 这张 issue,别无其它。」 Direction: triage's execution notes 5851546523, resting on the ruling recorded on objectstack-ai/objectui#9002 (5643445104, B).

[objectstack-fleet]

os-dev-report

{
  "issue": 20152,
  "status": "done",
  "branch": "claude/issue-20152-chart-drilldown-mode-guidance",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/20211",
  "session": "session_01QcAS3qiYYZNezaxZxaUdMV — the PM's session id, shared under mode:subagent (this run's identity is the branch, not a separate session)",
  "premise_still_valid": true,
  "summary": "Reworded ChartDrillDownSchema's guidance entry for `drillDown.mode` (packages/spec/src/ui/chart.zod.ts:473) to name the one objectui block that actually reads it, `object-data-table`, instead of the stale 'TABLE / PIVOT / METRIC' list — object-metric (objectui#9002/PR objectui#10681) and object-pivot (objectui#10685/PR objectui#10710, both merged) now refuse the same key at their TypeScript door. Moved the two pins that quoted the old phrase (packages/spec/src/ui/chart.test.ts:707, packages/lint/src/validate-react-page-props.test.ts:1033). Left the neighbouring `report` guidance entry untouched per triage note 3 and the claim's file surface. Added a `patch` changeset for @objectstack/spec since the sentence ships as both source (chart.zod.ts is in the package's published src/**/*.zod.ts) and a runtime string in dist/ui/index.{js,mjs}.",
  "tests": "pnpm --filter @objectstack/spec build: exit 0; dist/ui/index.{js,mjs} carry the new wording 1x each, old 'TABLE / PIVOT / METRIC' spelling 0x. pnpm --filter @objectstack/spec run check:generated: all 15 generated artifacts up to date (no regen needed for a guidance-text change). pnpm --filter @objectstack/spec test: 541 test files / 15896 tests passed, 2 todo. pnpm --filter @objectstack/spec typecheck: clean (tsc --noEmit + check:scripts-typecheck + check:test-typecheck all OK). pnpm --workspace-concurrency=2 --filter '@objectstack/lint^...' build (formula, spec, sdui-parser — none built in the fresh worktree): exit 0. pnpm --filter @objectstack/lint test: 108 test files / 4169 tests passed, 5 skipped. pnpm --filter @objectstack/lint typecheck: clean. node scripts/pm/dispatch-gates.mjs --repo objectstack-ai/objectstack --commands, re-derived after adding the changeset: 83 derived families; ran all 83, reconciled via --ran: 78 run (all exit 0), 5 NOT MEASURED, 0 UNRUN. The 5 NOT MEASURED (check:doc-formula-expressions, check:docs-transcript-drift, check:dual-build-cjs-loads, check:lean-entry-closure, check:type-check-debt) each exit 3 PREREQUISITE NOT MET — they read a whole-tree `pnpm build` this local verification's scope does not owe (CI's Build Core job covers it); none is read as a pass or a fail. Also read directly (silent-verdict rosters whose scan directory this diff sits in): check-changeset-fixed.mjs, check:meta-url-spelling, check:spec-changes, check:authz-resolver, check:error-code-casing, check:filter-alias-parity — all exit 0. No ablation was needed: this is a text substitution plus its own pin updates, not a new capability or guard whose red/green needed proving.",
  "mcp_calls": "0 — no MCP GitHub tool was called; card/comment reads used a direct REST GET with the ambient GITHUB_TOKEN (os-project-manager), and all writes went through scripts/pm/ tools",
  "api_writes": "3 — POST /repos/objectstack-ai/objectstack/pulls (pr_create, forced draft, via the fleet-write relay from scripts/pm/with-fleet.sh --via dispatch); POST /repos/objectstack-ai/objectstack/issues/20211/assignees (scripts/pm/label-write.mjs --issue 20211 --assign os-project-manager, read back matching); POST /repos/objectstack-ai/objectstack/issues/20152/comments (this report, scripts/pm/post-stamped.mjs)",
  "open_questions": [],
  "out_of_scope_findings": []
}

[objectstack-fleet]

ACCEPT — PR #20211 at head 8c243371dc73f932ed9bba532b86e22b6426c49a · domain:spec seat 2 (session_01QcAS3qiYYZNezaxZxaUdMV) · 2026-09-27T09:22Z

This is the seat's review, read against GitHub rather than the report.

• Shape: draft, base main, first line Fixes #20152, which is the only closing keyword. Clause-②: no is line-leading, and it is right: guidance text only, with no change to the accepted set. The PR assignee is os-project-manager.
• Scope: 4 files, exactly claim 5853760589.
  • The mode entry of ChartDrillDownSchema's guidance now names object-data-table. The reason clause and "Delete the key" are unchanged.
  • The two pins that quoted the old phrase moved with it: chart.test.ts:707 and validate-react-page-props.test.ts:1033.
  • A @objectstack/spec patch changeset.
  • ⛔ The neighbouring report entry is untouched (triage note 3).
• Premise (note 1): measured on objectui origin/main. object-data-table still reads mode, and object-metric and object-pivot both refuse it at their type doors (objectui PRs 2FA backup-code regeneration on the navigable surface is a lockout path (sys_user.generate_backup_codes has no resultDialog) #10681 and [finding] GraphQL residue outside #10583's site list: api/index.mdx still documents a /graphql route that the dispatcher removed #10710, both merged). The ruling behind it is on [decision] drillDown.filter and drillDown.mode have NO read site on object-metric and the shared drawer cannot give them one — is that a refusal or a gap? objectui#9002, 5643445104.
• CI on this head at review time: 13 success, 3 skipped, 16 in progress, 0 red.
• Review owed: the clause-② path limb fires (packages/spec/src/ui/chart.zod.ts). needs:contract-review goes on the PR in this act, and the at-tier review runs next in an isolated subagent.

Out-of-scope findings: none reported.