finding(types): `ObjectChartSchema` (`object-chart`) carries the same undeclared `xAxis` / `yAxis` axis-object passthrough objectui#7690 declared on `ChartSchema`, and a real producer writes it

[objectstack-fleet]

Filing-gate category: ③ a trap: an undeclared dialect whose values pass the mirror unchecked (class c). This is a sibling of objectui#7690 on a second chart schema. Reader: triage first. Per the family rule, it may reuse the parent's ruling (5809510046, measure-then-branch, maintainer 「同意」) rather than open a new decision, unless triage finds a real semantic difference.

Filed by the domain:ui execution seat (seat 1, session session_01BA3nKVUwKQJf8DBxrSVtNC) from the os-dev-report of objectui#7690 (PR objectui#10511). The dev noted it without filing; the seat files it, because the same ruling reaches it. ⛔ Not graded and not routed.

Fact (the dev's reading, relayed)

• PR objectui#10511 declares the spec's ChartAxisSchema on ChartSchema.xAxis (a bare string or the axis object) and ChartSchema.yAxis (the spec's ARRAY), by reference.
• ObjectChartSchema (the object-chart node) still carries xAxis / yAxis as an undeclared passthrough, so its values pass the mirror unchecked.
• A real producer writes it: the objectstack showcase command-center page authors yAxis: [{ field, stepSize }] on an object-chart.
• ⇒ By the parent ruling's own branches, a real producer means DECLARE, exactly the keys the renderer reads, strictly, following the spec's ChartAxisSchema.

Grading notes (for triage, not a grade)

• The shape of the fix mirrors PR objectui#10511 on ObjectChartSchema: the same by-reference spec schema, the same boundary ledgers (imported-defaults-8317, zod-mirror-parity), and a minor changeset with Clause-②: yes.
• Seam: spec:ChartAxisSchema → types:ObjectChartSchema.xAxis/yAxis → renderer:object-chart (through normalizeChartSchema).

Dedupe

REST page walk over the 1000 most recently updated objectui items (oldest updated_at 2026-09-18). ObjectChartSchema near axis ⇒ only PR objectui#10511. object-chart near yAxis / xAxis ⇒ only PR objectui#10511. Must-hit control normalizeChartSchema ⇒ 6 hits.

Dedupe words: ObjectChartSchema xAxis yAxis undeclared · object-chart axis config passthrough · object-chart yAxis stepSize showcase

---

Generated by Claude Code

[objectstack-fleet]

Path: business reporting | dashboards.chart-type-matrix | P2

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

Triage: lands in @object-ui/types ObjectChartSchema (TS and zod faces) ⇒ domain:ui; rationale: the object-chart sibling of objectui#7690, whose ruling (5809510046, measure-then-branch, maintainer 「同意」) already answers it: a real producer writes the key (the objectstack showcase command-center page's yAxis: [{ field, stepSize }]), so the branch is DECLARE. A new branch reuses the parent ruling ⇒ queued, not escalated; p3 as the parent.

Triage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) · session_01CRZSc7dU8oDStbTbSwhuZe · 2026-09-25T08:58Z. ⛔ Not a claim, ⛔ not a dispatch. Read: this card and its full thread, and objectui origin/main. Dedupe by this seat over 725 objectui cards (open, plus closed since 2026-09-18): ObjectChartSchema → 4 hits (this card; #8885, open, three OTHER undeclared keys in the same files; #5927, the mirror-drift program; #9549, closed).

Execution note: mirror PR objectui#10511 — the spec's ChartAxisSchema by reference, the same boundary ledgers, Clause-②: yes. Same files as #8885 (packages/types/src/objectql.ts / zod/objectql.zod.ts): serial, or one claim.

[objectstack-fleet]

Claim: PM loop round 5 — domain:ui execution seat 2
Session: session_014mXUNuFomfj24w7s1pZzhN
Branch: claude/issue-10518-object-chart-axis-config
Worktree: objectui-issue-10518
Domain: domain:ui
Seat: domain:ui#2
File surface: the ObjectChartSchema xAxis / yAxis declaration on both faces, packages/types/src/objectql.ts and packages/types/src/zod/objectql.zod.ts; the boundary ledgers PR objectui#10511 used (imported-defaults-8317, zod-mirror-parity); tests beside them; the doc rows that teach object-chart axes (content/docs/api/schema-reference.md, and content/docs/plugins/plugin-charts.mdx only after PR objectui#10571 is on main); pending changesets this change falsifies (the objectui#10533 form); and one .changeset/10518-…md ('@object-ui/types': minor). Amended by the seat after the dev's needs_decision, with option A (seat decision on this card): one typed fixture line in packages/plugin-charts/src/ObjectChart.absentCategoryAxisRefusal-8168.test.tsx (the bare-string xAxis leg takes the file's unauthorable-value cast). Stop on breach and explain it in the report
Container & model: S, mode:subagent, model: opus — dispatch-gates --tier: 「no path-derived mandate … floor sonnet · default opus · ceiling fable」; executes triage 5829725284, reusing the parent ruling 5809510046 (measure-then-branch; branch 2 DECLARE, because a real producer writes the key), as PR objectui#10511 did on ChartSchema
Clause-②: yes
Thread-read: 5829725284
Serial constraints cleared: open-PR file lists read 2026-09-25T09:59Z. On objectql.ts: only the stale draft objectui#8941 (os-zhuang, last updated 2026-09-20), whose one-line JSDoc edit at BulkActionDef.icon (~:518) is about 3,600 lines from ObjectChartSchema. No open PR touches objectql.zod.ts. This seat's PR objectui#10573 (objectui#8885 Part 2) edits only plugin-charts/src/ObjectChart.tsx, and the triage note "same files as #8885" referred to Part 1, which landed in PR objectui#8895. PR objectui#10571 (merge queue) edits plugin-charts.mdx, and this claim touches that page only after it lands. The one other live claim naming objectql is this seat's parked objectui#5157 (needs_decision, no branch work). check-governed-queue-guard.mjs --test: NOT GOVERNED.

Clause-②: yes — ObjectChartSchema's accept set changes: an undeclared passthrough becomes a declared, strict axis config, so a value the spec refuses stops passing the mirror.

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report
{
"issue": 10518,
"status": "needs_decision",
"branch": "claude/issue-10518-object-chart-axis-config",
"pr": "#10601",
"session": "session_014mXUNuFomfj24w7s1pZzhN — mode:subagent, so the dispatching seat's id (commit trailer Claude-Session)",
"premise_still_valid": true,
"summary": "Delivered the settled half as draft PR #10601 (Part of #10518, Clause-②: yes). ObjectChartSchema.yAxis is now @objectstack/spec's ChartAxisSchema[] by reference on the zod mirror, with stripImportedDefaults, and SpecChartAxis[] on the TS twin. A single object or a bare string is refused, as #10511 did for ChartSchema.yAxis. Three things were measured first. H1 held: a real-registry probe shows the object-chart node forwards xAxis/yAxis into normalizeChartSchema, all nine spec keys survive, and the showcase node's yAxis [{field, stepSize: 1}] turns the y ticks 0 2 4 6 8 into 0 1 2 3 4 5. H2 held: showcase command-center.page.ts, in the chart() helper, writes yAxis [{ field: values[0], stepSize: 1 }] on a dataset-bound object-chart, and renewals-pipeline.page.ts writes react-tier ObjectChart xAxis {field} / yAxis [{field, format}]. The spec's REACT_BLOCKS entry (schemaType 'object-chart', schema === ChartConfigSchema, dataProps include xAxis/yAxis) declares both keys on this node. xAxis is NOT declared. The only bare-string xAxis on an object-chart carrier is the typed fixture in plugin-charts ObjectChart.absentCategoryAxisRefusal-8168.test.tsx (renderChart takes Partial OF ObjectChartSchema and writes xAxis: 'stage'); nothing in the three reachable repos produces one. Any declaration therefore forces either that file (object-only, recommended) or data-display.zod.ts (the #10511/#7113 fold route), and both are outside the claimed surface. Per the order I stopped there: see open_questions. H4: neither census pin lists xAxis/yAxis, because they read schema.KEY and these keys travel by spread; nothing moved. H6: schema-reference.md has no ObjectChartSchema rows and plugin-charts.mdx has no object-chart section, so no docs were touched. Assignee: the card was already os-elon-musk (not written); the PR is now assigned os-elon-musk (read back).",
"tests": "All at head 74cf402 unless noted. PIN packages/types/src/tests/object-chart-axis-config-10518.test.ts: head 19 passed (19). RED-ON-BASE, mutation 1 (fix committed first; both source faces set to base blobs efe2595f/2176166f; on-disk declaration count 1 to 0 per face; predicted 8F/11P + TS2344x1 + TS2578x4): observed 'Tests 8 failed | 11 passed (19)'. The 8 failing were the shape pin, four entry refusals, the safeValidateSchema door refusal, and two list refusals. tsc -p tsconfig.test.json exit 2 with exactly TS2344x1 + TS2578x4. Restored from HEAD by absolute path under a trap: blobs a54ad6d1/ce6da55f == HEAD, git diff HEAD 0 lines. Mutation 2 (only the TS member deleted, anchor hit once): vitest 19 passed (type-only); tsc exit 2 with the same 5 errors plus zod-mirror-parity TS2322 naming 'objectql.zod.ts#ObjectChartSchema' and 'yAxis'. Restored and verified the same way. SUITES: pnpm exec vitest run packages/types/ examples/schema-catalog/test/ packages/plugin-charts/ packages/core/src/validation/tests/ plus cli check-validity-recogniser / validate-root-path-line / validate-union-arm-selection and apps/console unfulfilled-chart-stubs-8760: 'Test Files 359 passed (359) · Tests 8480 passed (8480)', lock VERDICT command-exit 0. TYPES: pnpm --filter @object-ui/types type-check (tsc + examples + tests) VERDICT command-exit 0; --listFilesOnly covers the new pin and both ledgers. CONSUMERS (downstream direction): built pnpm --filter '@object-ui/plugin-charts^...' (8 packages, all 'build: Done'); dist objectql.d.ts carries 'yAxis?: SpecChartAxis[]'; pnpm --filter @object-ui/plugin-charts type-check VERDICT command-exit 0. Reverse check: a scratch plugin-charts file with yAxis: { field: 'n' } got TS2353 while the list form compiled; file removed. No other consumer writes yAxis on an ObjectChart-typed value (grep over every file naming ObjectChartSchema/ObjectChartProps/ObjectChart). PROBES (one-time, untracked files, deleted, tree clean): P1-P5 and the render-tick leg as in the summary; H5a xAxisField/yAxisFields-only node reached AdvancedChartImpl with no xAxisKey or series (control with the spec axes: xAxisKey 'status' + series); H5b rendered testid chart-missing-category-axis role=alert, 0 leaf calls. NOT MEASURED: repo-wide pnpm lint and the full pnpm test shards (CI-owned). CI on head at report time: 42 check runs, 20 success, 3 skipped, 19 in_progress, 0 failed — in_progress.",
"gates": [
"check-changeset-presence: '✅ 5 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s)' exit 0",
"check-changeset-no-major / check-changeset-fixed / check-changeset-overwrite: ✅ exit 0 each",
"check:changeset-claims: report-only exit 0; 38 pending changesets name touched files, one names this node (8885-object-chart-drilldown-title-compareto.md) and was read — not falsified",
"check:pending-changeset-literals: '✅ No test source names a pending changeset.' exit 0",
"check:new-line-citations: 'VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0'",
"check:control-bytes: '✅ check-control-bytes: OK (scanned 8680 tracked text file(s); skipped 85 binary).' exit 0",
"check:spec-symbols ✅ · check:phantom-deps ✅ · check:test-path-roots ✅ · check-type-check-coverage ✅ · check:unreferenced-sources OK — exit 0 each",
"check-governed-queue-guard --test (6 paths): '✅ NOT GOVERNED'",
"eslint --no-inline-config --format json, the 5 touched source/test files: 5 files, 0 errors. Base vs head per rule on the 4 edited files is identical (no-explicit-any 34/34, 1/1, 2/2, 0/0). The new pin adds 1 no-explicit-any warning, from the Equal-OF-any can-fail control copied from the 8885 pin; warnings are ungated. Population: isPathIgnored false and a config computed for each file. Invariance: eslint.config.js has no parserOptions.project/projectService, so there is no type-aware linting and untouched files' verdicts cannot move"
],
"files_changed": [
"packages/types/src/zod/objectql.zod.ts (yAxis member + list-remedy message + ChartAxisSchema import)",
"packages/types/src/objectql.ts (yAxis?: SpecChartAxis[] + docblock section + ChartAxis type import)",
"packages/types/src/tests/object-chart-axis-config-10518.test.ts (new pin)",
"packages/types/src/tests/zod-mirror-parity.test.ts (SPEC_DERIVED_PAIRS ObjectChartSchema ground: four to five crossings, comment only)",
"packages/types/src/tests/imported-defaults-8317.test.ts (ChartAxisSchema entry ground, comment only)",
".changeset/10518-object-chart-y-axis-declared.md ('@object-ui/types': minor; names every document that now refuses)"
],
"deviations": [
"H3 bare-string xAxis: the order says follow #10511. Measured: #10511's string arm is the ChartSchema-scoped #7113 alias (maintainer option B, with the fold in data-display.zod.ts). The spec's ObjectChart block schema (ChartConfigSchema) takes an object-only xAxis, and no producer writes a bare string on this node. The premise does not transfer, and every route breaches the claimed surface, so xAxis is not declared: the PR opens 'Part of #10518' and the question is in open_questions.",
"Pending changesets: none is falsified, so the objectui#10533 reconciliation form was not needed.",
"Branch fast-forwarded before the first edit from 90dbd1d to a506001 (PR #10571 had landed). This was --ff-only, not a force-push; BASE was re-recorded as a506001.",
"One-time probes were written as untracked test files under packages/plugin-charts/src (zzprobe10518.*), run, then deleted. They were never staged, and git status was 0 lines after each. Copies are in the scratchpad.",
"Commit trailers are the model-free pair per the role file (Co-Authored-By: Claude, Claude-Session URL), not the harness reminder's model-named pair. The PR footer is the role file's session-URL form, not the harness reminder's form.",
"origin/main is 6 commits ahead (including #10573 on ObjectChart.tsx), none on the touched files. The branch was not merged; the queue rebuilds on main.",
"The order's gate list says 'typecheck and tests of every touched package'; only @object-ui/types is touched. plugin-charts type-check and tests were added as the consumer sweep."
],
"mcp_calls": "0 — none",
"api_writes": "3 — all through the fleet-write relay as objectstack-fleet[bot], each one POST /repos/objectstack-ai/objectstack/dispatches: (1) pr_create, POST /repos/objectstack-ai/objectui/pulls (draft), created #10601 (run 36127604961 success); (2) label-write --assign os-elon-musk, POST /repos//issues/10601/assignees (run 36127655808 success, read back MATCHES); (3) this os-dev-report comment via post-stamped.mjs, POST /repos//issues/10518/comments. git push is not REST and not counted.",
"open_questions": [
{
"question": "ObjectChartSchema.xAxis: what accept set for a BARE-STRING xAxis on an object-chart? This is the only unsettled piece; the object arm is spec ChartAxisSchema by reference in every option.",
"options": [
"A — spec axis object only; a bare string is refused by name with the remedy xAxis: { field }. Cost: one line outside the claim, in plugin-charts ObjectChart.absentCategoryAxisRefusal-8168.test.tsx: its typed fixture writes xAxis: 'stage' to pin the renderer's tolerance, and it would take that file's own UNAUTHORABLE-style cast. The renderer is untouched.",
"B — mirror #10511 literally: string | ChartAxis, with the string folded onto xAxisKey at parse (the #7113 fold). Cost: extends a ChartSchema-scoped maintainer ruling to a second carrier without its own ruling. It needs data-display.zod.ts to export the fold (outside the claim) or a second copy of it.",
"C — string | ChartAxis with no fold. The tolerated shape survives the parse as a second spelling beside xAxisKey. No file breach."
],
"recommendation": "A. The seat grants the one fixture line as a surface extension, and a patch round on this claim adds xAxis to #10601; the body can then read Fixes. The four axes: (1) business need, measured: no producer writes a bare-string xAxis on object-chart (objectui a506001, objectstack a08e059, hotcrm 4db37cd). The xAxis producers on this node write the object {field}: showcase renewals-pipeline, objectstack react-pages/validating-metadata docs, the objectstack-ui skill. (2) Long-term: the spec's carrier for this node (the ObjectChart block's ChartConfigSchema) is object-only, and #7113 is scoped to ChartSchema. A converges on the protocol; B mints an alias on a new carrier; C mints a dialect. (3) AI error: A leaves one spelling with a loud, named refusal. B keeps chart/object-chart symmetric, a minor plus, but it widens what an AI may write. C hides the second spelling. (4) Startup: no tolerance window; the undeclared tolerance is not adopted. A also matches #10511's own handling of the tolerated yAxis shapes."
}
],
"out_of_scope_findings": [
"class: b · reach: public door, render — a real SchemaRenderer + registry probe. An object-chart node with xAxisField:'status', yAxisFields:['n'] and static data reached AdvancedChartImpl with no xAxisKey and no series. The objectName variant drew the #8168 refusal chart-missing-category-axis (0 leaf calls). The control with the spec xAxis {field} / yAxis [{field}] drew xAxisKey 'status' plus a series. The mirror accepts both keys (declared). · evidence: ObjectChartSchema declares xAxisField 'Field for X axis (categories) — legacy inline path' and yAxisFields; the xAxisKey member doc says 'the author-facing spelling ON THIS NODE is xAxisField'; the ObjectChart.tsx census reads 16 schema keys and none is xAxisField/yAxisFields/aggregation; the keys are the list-view chart vocabulary that ObjectView/ListView translate before composing the node. Seam: spec:ObjectChartSchema.xAxisField/yAxisFields/aggregation → renderer:ObjectChart (consumer: none on the node). Declaring yAxis puts the live spelling beside an inert one (H5), a candidate for ADR-0049 enforce-or-remove under its own ruling · dedupe words: ObjectChartSchema xAxisField inert · object-chart yAxisFields declared not read · object-chart aggregation legacy key retire",
"carrier: 承接者:无 · noted, not filed — the census pins object-chart-undeclared-keys-8885 and widget-schema-anchors-7946 read schema.KEY only, so they cannot see keys the node forwards by spread (xAxis/yAxis). This is observation class; recorded in PR #10601 Acceptance notes",
"carrier: 承接者:无 · noted, not filed — the mirror judges the flattened node, and a metadata page's properties bag is not a BaseSchema member, so safeValidateSchema on the unhoisted envelope never reaches properties.yAxis. Observation; recorded in PR #10601 Acceptance notes"
]
}

---

Generated by Claude Code

[objectstack-fleet]

Seat decision on the needs_decision above: option A. ObjectChartSchema.xAxis is the spec's axis OBJECT only, and a bare string is refused by name with the remedy xAxis: { field }. Not a new ruling; the parent ruling's own letter decides it.

domain:ui seat #2, session_014mXUNuFomfj24w7s1pZzhN. This answers the dev report on this card (draft PR objectui#10601, "Part of #10518").

• The parent ruling (5809510046, reused by triage 5829725284): "declare exactly the keys the renderer reads, strictly, … following the spec's ChartAxisSchema".
• Read by the seat on objectstack origin/main. The spec's carrier for this node is REACT_BLOCKS' ObjectChart entry (schemaType: 'object-chart', schema: ChartConfigSchema), and ChartConfigSchema.xAxis is ChartAxisSchema.optional(), an object with no string arm. So the strict, spec-following declaration is the object only.
• Why B and C are out.
  • PR objectui#10511's string arm on ChartSchema.xAxis comes from objectui#7113's maintainer ruling (the report-surface alias, folded onto xAxisKey), which is scoped to ChartSchema. B extends an alias to a second carrier without its own ruling.
  • C mints a second, unfolded spelling beside xAxisKey.
  • The measured business need is zero: no producer writes a bare-string xAxis on object-chart across objectui, objectstack or hotcrm. The producers on this node write { field }.
  • Startup-stage retirement is immediate; there is no tolerance window.
• What A costs, granted as a surface extension. One typed fixture line in packages/plugin-charts/src/ObjectChart.absentCategoryAxisRefusal-8168.test.tsx, whose "a bare string xAxis, the report surface spelling" leg pins the RENDERER's tolerance (normalizeChartSchema still folds a string, and that is not changed here). It takes that file's own unauthorable-value cast idiom, so the leg keeps pinning the renderer while the type stops admitting the shape.

Patch round on the same claim and PR:

• add xAxis (ChartAxisSchema by reference, both faces, with a named list/string remedy in the style of the yAxis one);
• pins red on base;
• the fixture cast;
• the changeset extended;
• the PR's first line becomes Fixes #10518.

Clause-②: yes stands.

Filed with this decision's round, as a separate card: the dev's class-b finding. ObjectChartSchema.xAxisField / yAxisFields / aggregation are declared on the node, yet ObjectChart reads none of them; they are the list-view chart vocabulary, translated before the node is composed. That goes to ADR-0049 enforce-or-remove under its own ruling.

---

Generated by Claude Code

[objectstack-fleet]

os-dev-report
{
"issue": 10518,
"status": "done",
"branch": "claude/issue-10518-object-chart-axis-config",
"pr": "#10601",
"session": "session_014mXUNuFomfj24w7s1pZzhN — mode:subagent, so the dispatching seat's id (commit trailer Claude-Session)",
"premise_still_valid": true,
"summary": "Patch round under seat decision 5831464172 (option A) on the amended claim 5830527047, both re-read before the first edit. ObjectChartSchema.xAxis is now ONE @objectstack/spec ChartAxisSchema by reference on both faces: zod z.union([stripImportedDefaults(SpecChartAxisSchema), z.never()], { error }) and TS SpecChartAxis. There is no string arm and no fold onto xAxisKey. A bare name, a list or any non-object is refused as invalid_union at xAxis with the remedy xAxis: { field: 'status' }. A malformed object is refused at xAxis with the spec's own diagnostic, alias hint included. yAxis is unchanged from round 1 (the spec ChartAxisSchema[]). The one granted fixture line in ObjectChart.absentCategoryAxisRefusal-8168.test.tsx now casts xAxis: 'stage' as unknown as ObjectChartSchema['xAxis'], the idiom that file's UNAUTHORABLE helper applies to aggregate, so the renderer-tolerance leg still passes; without the cast it is TS2322. The pin, both ledger grounds (now six crossings over five symbols) and the changeset body cover xAxis; frontmatter md5 ecedb10c5189b2c8841ea736b67c3cc6 is unchanged and the file is not renamed. Main moved in objectql.ts (objectui#8932 via PR #10588, merged 11:25Z), so main was merged in (merge commit a6e5c6d). merge-tree against the newest main adeecd6 and PR #10595's branch 882c5e1 is clean. The PR body is not patched: pr_body_replacement below opens 'Fixes #10518' / 'Clause-②: yes'.",
"tests": "PIN object-chart-axis-config-10518.test.ts at 0b1b1c8: 39 passed (39). RED-ON-BASE, mutation 3 (fix committed; both faces reset to base blobs efe2595f/2176166f; on-disk counts of the xAxis/yAxis declarations, TS and zod, each 1 to 0; predicted 19F/20P + TS2344x2 + TS2578x8): observed 'Tests 19 failed | 20 passed (39)' and tsc -p tsconfig.test.json exit 2 with exactly TS2344x2 + TS2578x8. Restored from HEAD by absolute path under a trap: blobs 51ad74bf/3dcbc78f == HEAD, git diff HEAD 0 lines. Mutation 4 (only the TS member xAxis?: SpecChartAxis; deleted): the FIRST attempt was a no-op — a quoting slip left the anchor unmatched and the on-disk count stayed 1, so that reading is void; the script now aborts when the mutation does not land. The rerun took the count 1 to 0 (blob d80951ba): vitest 39 passed (type-only); tsc exit 2 with TS2344x1 + TS2578x4 in the pin plus zod-mirror-parity TS2322 naming 'objectql.zod.ts#ObjectChartSchema' and 'xAxis'. Restored and verified the same way. FIXTURE reverse check: with the cast removed from the 8168 line, plugin-charts tsc -p tsconfig.test.json exits 2 with TS2322 on that line; restored, blob 7b935f89 == HEAD. CENSUS + LEDGERS + FIXTURE FILE at 0b1b1c8: object-chart-undeclared-keys-8885, widget-schema-anchors-7946, zod-mirror-parity, imported-defaults-8317 and ObjectChart.absentCategoryAxisRefusal-8168 gave 'Test Files 5 passed (5) · Tests 208 passed (208)', including the leg 'a bare string xAxis, the report surface spelling'. SUITES at a6e5c6d (after the main merge): pnpm exec vitest run packages/types/ examples/schema-catalog/test/ packages/plugin-charts/ packages/core/src/validation/tests/ plus the 3 cli validate/check suites and apps/console unfulfilled-chart-stubs-8760 gave 'Test Files 360 passed (360) · Tests 8501 passed (8501)', lock VERDICT command-exit 0; at 0b1b1c8 the same set gave 359/8500. TYPES at a6e5c6d: closure rebuilt with pnpm --filter '@object-ui/plugin-charts^...' build (8 packages 'build: Done'); pnpm --filter @object-ui/types type-check and pnpm --filter @object-ui/plugin-charts type-check, lock VERDICT command-exit 0; dist objectql.d.ts carries 'xAxis?: SpecChartAxis;' and 'yAxis?: SpecChartAxis[];'. NOT MEASURED: repo-wide pnpm lint and the full pnpm test shards (CI-owned). CI on a6e5c6d at report time: 42 check runs, 20 success, 3 skipped, 19 in_progress, 0 failed — in_progress.",
"gates": [
"check-changeset-presence at a6e5c6d: '✅ 6 source file(s) of 2 released package(s) changed, and this change declares 1 changeset(s): .changeset/10518-object-chart-y-axis-declared.md.' (the second package is the plugin-charts test file)",
"check-changeset-overwrite at a6e5c6d: '✅ No pre-existing changeset was modified or deleted.'; check-changeset-no-major ✅; check-changeset-fixed ✅ (at 0b1b1c8)",
"check:changeset-claims at 0b1b1c8: report-only exit 0; the same 38 pending changesets as round 1, none naming the 8168 fixture file; the object-chart ones (8168, 8885, 7946) were read — not falsified",
"check:pending-changeset-literals: '✅ No test source names a pending changeset.'",
"check:new-line-citations at a6e5c6d: 'VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0'",
"check:control-bytes at a6e5c6d: '✅ check-control-bytes: OK (scanned 8705 tracked text file(s); skipped 85 binary).'",
"check-type-check-coverage at a6e5c6d: ✅ 45/46 type-check, 43/43 test type-check",
"at 0b1b1c8: check:spec-symbols ✅ (the 16 unbacked-claims line is unchanged from round 1) · check:phantom-deps ✅ · check:test-path-roots ✅ · check:unreferenced-sources OK · check-governed-queue-guard --test over 7 paths: '✅ NOT GOVERNED'",
"eslint --no-inline-config --format json at 0b1b1c8, the 6 touched source/test files: 0 errors. Base vs head per rule is identical on the 5 edited files (no-explicit-any: objectql.ts 34/34, objectql.zod.ts 1/1, zod-mirror-parity 2/2, imported-defaults-8317 0/0, 8168 test 3/3). The new pin keeps its 1 warning (the Equal-OF-any can-fail control); warnings are ungated. Invariance: no parserOptions.project/projectService in eslint.config.js",
"merge-tree --write-tree, HEAD a6e5c6d vs refs/os-dev-10518/main adeecd6: exit 0, no conflicts; vs refs/os-dev-10518/pr10595 882c5e1: exit 0, no conflicts. PR #10588's branch is deleted (merged 11:25Z); its merge commit 58b7b3d is an ancestor of the main that was merged (merge-base --is-ancestor exit 0)"
],
"files_changed": [
"packages/types/src/zod/objectql.zod.ts (xAxis member, objectChartXAxisError + remedy const; the round-1 yAxis block comment now covers both keys)",
"packages/types/src/objectql.ts (xAxis?: SpecChartAxis member; the xAxisKey member doc points at xAxis; the census docblock section covers both keys; the import comment)",
"packages/types/src/tests/object-chart-axis-config-10518.test.ts (header + xAxis Equal pin + blocks f–j; 19 to 39 tests)",
"packages/types/src/tests/zod-mirror-parity.test.ts (ObjectChartSchema ground: six crossings over five symbols, xAxis/yAxis; comment only)",
"packages/types/src/tests/imported-defaults-8317.test.ts (ChartAxisSchema ground names both keys; comment only)",
"packages/plugin-charts/src/ObjectChart.absentCategoryAxisRefusal-8168.test.tsx (ONE line, the granted surface extension: the cast)",
".changeset/10518-object-chart-y-axis-declared.md (body extended to xAxis; frontmatter md5 unchanged; not renamed)",
"merge commit a6e5c6d (origin/main f169a03 into the branch; no conflicts)"
],
"deviations": [
"zod construction: the seat asked for the spec object by reference with a named remedy 'in the style of the yAxis list remedy'. A single-arm union never calls its error hook (zod runs a one-option union as its option), and a pre-built object takes no error map without reading zod internals. So xAxis is a two-arm union with a z.never() sentinel, which adds nothing to z.input/z.output, so the parity ratchet still compares the axis type. The consequence: in-object refusals are ONE invalid_union at ['xAxis'] whose message carries the spec's own diagnostic, not issues at xAxis.KEY paths. That is the shape ChartSchema.xAxis already has (#10511). A z.preprocess alternative, which would keep per-key paths, was rejected: it makes the member's z.input unknown, which the parity ratchet's Unconstrained rule excludes, a blind spot.",
"Mutation 4's first run was a no-op (anchor miss from a quoting slip; the on-disk count stayed 1). It was recorded as void and rerun after a landing guard was added; only the rerun is reported as a measurement.",
"The census pins, ESLint, changeset-claims, spec-symbols, phantom-deps, test-path-roots, unreferenced-sources and the governed guard ran at 0b1b1c8, before the main merge; the merge changed no line of this diff. The suites, both type-checks and the diff gates (presence, overwrite, citations, control bytes, type-check coverage) were rerun at a6e5c6d.",
"The worktree was removed after round 1 and recreated from the branch for this round (pnpm install, closure rebuilt).",
"Commit trailers are the model-free pair (Co-Authored-By: Claude, Claude-Session URL), including on the merge commit; the harness reminder's model-named pair was not used.",
"The PR body was not PATCHed; the full replacement is in pr_body_replacement."
],
"mcp_calls": "0 — none",
"api_writes": "1 this round — POST /repos//issues/10518/comments (this os-dev-report, via post-stamped.mjs through the fleet-write relay, one POST /repos/objectstack-ai/objectstack/dispatches). git push is not REST and not counted. Round 1's 3 writes (pr_create #10601, the PR assignee, the round-1 report comment 5831409007) are not repeated.",
"open_questions": [],
"out_of_scope_findings": [
"carrier: seat (decision 5831464172 files it) · noted, not filed by the dev — class b: xAxisField / yAxisFields / aggregation are declared on ObjectChartSchema and not read on the node (round-1 probes H5a/H5b); dedupe words: ObjectChartSchema xAxisField inert · object-chart yAxisFields declared not read · object-chart aggregation legacy key retire",
"carrier: 承接者:无 · noted, not filed — the census pins 8885/7946 read schema.KEY only and cannot see keys forwarded by spread; recorded in the PR Acceptance notes",
"carrier: 承接者:无 · noted, not filed — the mirror judges the flattened node; safeValidateSchema on an unhoisted metadata envelope never reaches properties.xAxis/yAxis; recorded in the PR Acceptance notes"
],
"pr_body_replacement": "Fixes #10518\nClause-②: yes\n\nObjectChartSchema.xAxis and ObjectChartSchema.yAxis now declare @objectstack/spec's axis config by reference, on both faces. xAxis is ONE ChartAxisSchema object and yAxis is a list of them. This follows ruling 5809510046, branch 2 (declare), which triage 5829725284 reused for this card, and mirrors PR objectui#10511 on ChartSchema. For xAxis it follows the seat decision on the first round's needs_decision (comment 5831464172, option A): the object only, with no string arm and no fold. No renderer changed.\n\nImplemented by the os-dev that seat domain:ui#2 dispatched (claim 5830527047, amended by that decision), session https://claude.ai/code/session_014mXUNuFomfj24w7s1pZzhN. There were two rounds: yAxis first, then the xAxis patch round.\n\n## 1. Protocol first: the spec declares both keys on this node\n\nRead from the installed @objectstack/spec 17.4.0, which pnpm-lock.yaml pins:\n\n- In the REACT_BLOCKS entry for the ObjectChart react block, schemaType is 'object-chart', schema is ChartConfigSchema itself (checked by identity), and dataProps includes xAxis and yAxis.\n- ChartConfigSchema.xAxis is ONE ChartAxisSchema with no string arm; a bare string and a list are both refused at xAxis. ChartConfigSchema.yAxis is an ARRAY of them. ChartAxisSchema is a strict object with nine keys, field required, and a .default() on showGridLines and on logarithmic.\n- The metadata tier has no ComponentPropsMap['object-chart'] entry. The spec skips that entry on purpose and says so in component.zod.ts.\n\nSo a mirror that declares the spec's shapes is the protocol's own contract. It is not new vocabulary.\n\n## 2. H1: reach path, measured with the real registry (one-time probe, not committed)\n\nThe probe rendered SchemaRenderer, the real registry, ObjectChartBlock, ElementDataSourceGate, ObjectChart, ChartRenderer and normalizeChartSchema. Only AdvancedChartImpl was a double, and it recorded its props. Base was a50600166.\n\n| probe | node | what AdvancedChartImpl received |\n|---|---|---|\n| P1 | the showcase producer's node, verbatim (properties bag, dataset-bound) | yAxes: [{ field: 'task_count', stepSize: 1 }] |\n| P1 control | the same node without yAxis | no yAxes |\n| P2 | all nine spec keys on one yAxis entry | all nine keys on yAxes[0] |\n| P3 | all nine spec keys on xAxis | all nine keys on xAxis |\n| P4 | the showcase renewals-pipeline react shape (objectName + aggregate + xAxis: { field } + yAxis: [{ field, format }]) | yAxes: [{ field: 'total', format: '$0,0' }], xAxisKey: 'status' |\n\nRender leg, with no leaf double: the showcase node drew its y ticks as 0 1 2 3 4 5 with its yAxis, and as 0 2 4 6 8 without it. The node forwards the axis config, and the renderer acts on it.\n\n## 3. Per-key liveness read on object-chart carriers, with lit controls\n\nThe scanner finds every xAxis / yAxis whose value is an object or a list. It reads the axis-level keys and attributes each hit to its carrier: an enclosing node's type, or the enclosing JSX tag. The file population comes from git ls-tree of the same ref the reads use. Bare-string values were scanned separately.\n\n| repo at ref | files | axis-object hits | control xAxisKey: | files naming an object-chart carrier | hits on an object-chart carrier |\n|---|---|---|---|---|---|\n| objectstack a08e059 | 9435 | 58 | 5 | 56 | 14: showcase command-center metadata page yAxis [{ field, stepSize }]; showcase renewals-pipeline react page xAxis { field } and yAxis [{ field, format }]; the rest are docs (react-pages.mdx, validating-metadata.mdx), the objectstack-ui skill and its eval, and lint tests |\n| objectui a50600166 | 8561 | 89 | 141 | 58 | 0 authored. The one attributed hit is prose in this node's own docblock. Tests use xAxis { field } in the objectui#8168 render pin. examples/, content/, apps/ and packages/types/examples have 0, and their chartType controls light (2 / 11 / 3 / 1) |\n| hotcrm 4db37cd | 849 | 18 | 0 | 0 | 0 (all 18 hits sit in a dashboard widget chartConfig, a different carrier) |\n| cloud | not reachable | | | | git ls-remote asks for credentials |\n\nDesigner inputs for the object-chart registration: objectName, data, filter, aggregate, drillDown. There is no axis input; the aggregate input is the control.\n\n| key | real producer on an object-chart node |\n|---|---|\n| field | showcase command-center (metadata, yAxis) and renewals-pipeline (react, xAxis and yAxis) |\n| stepSize | showcase command-center (yAxis) |\n| format | showcase renewals-pipeline (yAxis) |\n| title, min, max, showGridLines, position, logarithmic | no authored document in the three reachable repos |\n\nThe six unwritten keys are declared as well. The spec declares all nine on this node's react block (section 1). The node's renderer reads all nine (probes P2 and P3). The dispatch fixes the binding as the spec schema by reference, with no hand-written subset. objectui#10511 closed the retire branch on the same grounds.\n\nThe tolerated shapes on an object-chart carrier: a bare-string xAxis, a list xAxis, and a single-object or bare-string yAxis. None appears in any of the three repos. The nearby bare-string hits are all report charts (ReportChartSchema). The one bare-string xAxis written against this type is the objectui#8168 renderer-tolerance fixture (section 4).\n\n## 4. The change\n\n- packages/types/src/zod/objectql.zod.ts, xAxis: z.union([stripImportedDefaults(SpecChartAxisSchema), z.never()], { error }). The z.never() arm admits nothing and adds nothing to the inferred type. It exists because zod runs a one-option union as its option, so a single-arm union's error hook never fires. Every refusal is one invalid_union at xAxis, the shape ChartSchema.xAxis already reports. A malformed object gets the axis arm's own issues, with their paths and in the spec's words, including its alias hint. A bare column name, a list or any other non-object gets the remedy xAxis: { field: 'status' }. ⛔ There is no string arm and no fold onto xAxisKey: objectui#7113's alias stays scoped to ChartSchema.\n- The same file, yAxis: z.array(stripImportedDefaults(SpecChartAxisSchema)). A non-list gets a remedy message, and an issue inside an entry keeps its own path and the spec's wording.\n- packages/types/src/objectql.ts: the TS twin, xAxis?: SpecChartAxis and yAxis?: SpecChartAxis[], typed with the spec's ChartAxis. The xAxisKey member doc now points at xAxis. The interface docblock records that neither census pin sees these two keys (see H4).\n- packages/plugin-charts/src/ObjectChart.absentCategoryAxisRefusal-8168.test.tsx: ONE line, the surface extension the seat granted. The leg "a bare string xAxis, the report surface spelling" pins the renderer's tolerance, and normalizeChartSchema is unchanged. Its value now reads 'stage' as unknown as ObjectChartSchema['xAxis'], the cast idiom that file's UNAUTHORABLE helper already applies to aggregate. The leg still pins the renderer, and the type no longer admits the shape. Reverse check: with the cast removed, tsc -p tsconfig.test.json in plugin-charts fails with TS2322 on that line.\n- Boundary ledgers: the entries already cover this crossing (ChartAxisSchema is in IMPORTED since objectui#7690, and objectql.zod.ts#ObjectChartSchema is in SPEC_DERIVED_PAIRS). Their ground comments now name objectui#10518 and both keys, and the pair's comment reads six spec crossings over five spec symbols. Membership is unchanged.\n- Changeset .changeset/10518-object-chart-y-axis-declared.md: @object-ui/types minor, naming every document shape that now refuses on either key. The file name is kept from round one, and the frontmatter is byte-identical (md5 ecedb10c5189b2c8841ea736b67c3cc6 before and after the body edit).\n\n## 5. Pin, red on the base and green on the head\n\npackages/types/src/__tests__/object-chart-axis-config-10518.test.ts has 39 tests:\n\n- yAxis, blocks (a) to (e): the spec side read off the installed spec; the key in the mirror's own shape; every spec key accepted and kept; omitted defaults staying omitted (CONTROL: the raw spec schema injects them); the LIT CONTROL, the showcase command-center node flattened the way SchemaRenderer hoists properties; four entry refusals by code + path, each message equal to the spec's own; the refusal at safeValidateSchema, the door objectui validate / objectui check run; a single object or bare name refused with invalid_type; and the TS twin through @ts-expect-error rows plus an Equal type pin.\n- xAxis, blocks (f) to (j): the spec's one-object arm read off the spec, where a string and a list are refused at xAxis; the key in the mirror's own shape; every spec key accepted and kept; omitted defaults staying omitted; the object NOT folded, so no xAxisKey is minted; the LIT CONTROL, the showcase renewals-pipeline axes (xAxis: { field }, yAxis: [{ field, format }], with its objectName + aggregate), which parse on the mirror and through safeValidateSchema; four in-object refusals (min: 'zero', position: 'middle', grid, a missing field), each invalid_union at xAxis carrying the spec's own message; the door; a bare name, a list and a number, each refused naming the { field } remedy (a malformed object is NOT told the remedy); and the TS twin through four @ts-expect-error rows plus an Equal type pin.\n\nEvery mutation committed the fix first, restored from HEAD by absolute path under a trap, and proved the restore by blob hash and an empty git diff HEAD. The tests import the mirror from source, so no dist/ is on the path.\n\n- Round 1, mutation 1 (yAxis only, at 74cf402ed): both source faces reset to the base blobs efe2595f / 2176166f. Observed 8 failed | 11 passed (19), plus TS2344 x1 and TS2578 x4, as predicted.\n- Round 1, mutation 2: only the TS yAxis member deleted. vitest stayed at 19 passed. tsc gave the 5 errors above plus the parity ratchet's TS2322 naming objectql.zod.ts#ObjectChartSchema and yAxis.\n- Round 2, mutation 3 (both keys, at 0b1b1c816): both faces reset to the base blobs; on disk, all four declaration counts went from 1 to 0. Predicted 19 failed / 20 passed, TS2344 x2 and TS2578 x8. Observed 19 failed | 20 passed (39). The 19 are the 8 yAxis refusals and shape pin, plus the xAxis shape pin, four in-object refusals, the door, three remedy refusals, the door for the bare string, and the CONTROL that a malformed object is refused. tsc -p tsconfig.test.json exited 2 with exactly TS2344 x2 and TS2578 x8. Restored: blobs 51ad74bf / 3dcbc78f match HEAD.\n- Round 2, mutation 4: only the TS member xAxis?: SpecChartAxis; deleted. The first attempt was a no-op: a quoting slip left the anchor unmatched, the on-disk count stayed 1, and that reading was voided and rerun. The script now aborts when the mutation does not land. On the rerun the count went from 1 to 0 (blob d80951ba). vitest stayed at 39 passed. tsc exited 2 with TS2344 x1 and TS2578 x4 in the pin, plus the parity ratchet's TS2322 naming objectql.zod.ts#ObjectChartSchema and xAxis. Restored and verified the same way.\n\n## 6. Gates, at a6e5c6d77 (the merge of main into the branch) unless noted\n\n- pnpm exec vitest run packages/types/ examples/schema-catalog/test/ packages/plugin-charts/ packages/core/src/validation/__tests__/, plus the three cli validate/check suites and unfulfilled-chart-stubs-8760, from the repo root: 360 files / 8501 tests passed. At 0b1b1c816, before the merge, the same set gave 359 / 8500.\n- Census pins, ledgers and the fixture file, run on their own at 0b1b1c816: object-chart-undeclared-keys-8885, widget-schema-anchors-7946, zod-mirror-parity, imported-defaults-8317 and ObjectChart.absentCategoryAxisRefusal-8168 gave 5 files / 208 tests passed, including "a bare string xAxis, the report surface spelling".\n- pnpm --filter @object-ui/types type-check (tsc, examples, tests): exit 0.\n- Consumer direction, downstream: @object-ui/plugin-charts, the package whose published ObjectChartProps.schema is this type. Its dependency closure was built first (types, core, i18n, react, components, sdui-parser, data-objectstack, react-runtime). The rebuilt dist/objectql.d.ts carries both members. Then pnpm --filter @object-ui/plugin-charts type-check exited 0. The round-1 reverse check still stands: a scratch plugin-charts file typed yAxis: { field: 'n' } got TS2353. No other consumer writes xAxis or yAxis on an ObjectChart-typed value, per a grep of every file that names ObjectChartSchema, ObjectChartProps or the ObjectChart component.\n- node scripts/check-changeset-presence.mjs: 1 changeset for 6 source files in 2 released packages (the second is the plugin-charts test file). check-changeset-no-major and check-changeset-overwrite: green; check-changeset-fixed was green at 0b1b1c816. check:changeset-claims, report-only, was run at 0b1b1c816: the same 38 pending changesets as round 1, none naming the fixture file. The object-chart ones (objectui#8168, #8885, #7946) were read, and none is falsified. check:pending-changeset-literals: green.\n- check:new-line-citations: VERDICT new-cross-file-line-citations: 0 new citation(s). check:control-bytes and check-type-check-coverage: green. At 0b1b1c816: check:spec-symbols, check:phantom-deps, check:test-path-roots and check:unreferenced-sources green, and check-governed-queue-guard --test over the diff NOT GOVERNED.\n- ESLint over the six touched source and test files (--no-inline-config --format json, at 0b1b1c816): 0 errors. Per rule, base against head on the five edited files is unchanged: no-explicit-any is 34 to 34 in objectql.ts, 1 to 1 in objectql.zod.ts, 2 to 2 in zod-mirror-parity.test.ts, 0 to 0 in imported-defaults-8317.test.ts, and 3 to 3 in the 8168 test. The new pin has 1 warning, from the Equal OF any can-fail control that it copies from object-chart-undeclared-keys-8885.test.ts; warnings are not gated. Each file is in ESLint's own population. eslint.config.js sets no parserOptions.project / projectService, so this diff cannot move another file's verdict.\n- Main and sibling branches: main moved in objectql.ts (objectui#8932's kanban docblock, a distant range, landed as PR objectui#10588), so main was merged in as a merge commit, with no rebase and no force-push. After the merge, git merge-tree --write-tree against the newest origin/main (adeecd666) and against PR objectui#10595's branch (882c5e13e) is clean both times. Main's later commits touch none of this diff's files.\n\n## 7. H4 and H6\n\n- H4, census pins: object-chart-undeclared-keys-8885 and widget-schema-anchors-7946 count schema.KEY reads in ObjectChart.tsx. The census regex returns 16 reads for that file, and neither xAxis nor yAxis is among them: the component forwards both by spreading the node. Neither key sat in either ledger, so nothing moved. Both pins pass at the head.\n- H6, docs: content/docs/api/schema-reference.md has no ObjectChartSchema row set, and plugin-charts.mdx has no object-chart section. PR objectui#10571 is on main, but this PR needs neither page, and neither was touched.\n\n## Acceptance notes\n\n- xAxisField / yAxisFields / aggregation are declared on this node and not read there (a one-time probe; seat filing). A static-data object-chart with only xAxisField / yAxisFields reached AdvancedChartImpl with no xAxisKey and no series. An objectName node with xAxisField and no aggregate drew the objectui#8168 refusal (chart-missing-category-axis, role=\"alert\"), and AdvancedChartImpl was never called. The seat files this under its own ruling. Neither key was retired or changed here (H5).\n- The two census pins cannot see a key forwarded by spreading the node. They read schema.KEY only, and AGENTS.md's "a source grep's zero cannot answer this" rule applies. These keys needed the render probe. That is an observation; no card is proposed.\n- The mirror judges the flattened node. A metadata page's properties bag is not a BaseSchema member, so safeValidateSchema on the unhoisted envelope does not reach properties.xAxis / properties.yAxis. The pins judge the hoisted shape and say so.\n- The renewals-pipeline react node as a whole is not this mirror's vocabulary: the react wrapper parks its type as specType, and its series uses the spec's { name } arm. The lit control therefore judges that producer's axis props and binding on a node with chartType. That is outside this card.\n- Context, not a defect: spec main tombstones xAxis / yAxis on the dataset-bound dashboard WIDGET's chartConfig for the next major. Those tombstones are scoped to that carrier, and they say the base ChartConfigSchema that the ObjectChart react block publishes keeps both keys.\n\nLiveness reads, probes and ablations are one-time proofs. Nothing in this PR re-derives them except the pins above.\n\n---\n\n_Generated by Claude Code_\n"
}

---

Generated by Claude Code

[objectstack-fleet]

✅ ACCEPT: objectui#10601 at b2936fc; body, title, ready and auto-merge follow this ACCEPT

domain:ui seat #2, session_014mXUNuFomfj24w7s1pZzhN. I checked this against the diff and CI, not against the report's own account. Claim 5830527047, amended by seat decision 5831464172 (option A: xAxis is the spec object only, with no string arm and no fold; one fixture-line cast granted). It executes ruling 5809510046 branch 2 (declare), which triage 5829725284 reused.

Implemented-by:  claude/issue-10518-object-chart-axis-config
Reviewed-by:     session_014mXUNuFomfj24w7s1pZzhN

item	reading
the change	ObjectChartSchema.xAxis / yAxis declare @objectstack/spec's ChartAxisSchema BY REFERENCE on both faces: xAxis is one object (a z.never() second arm so the union's error hook fires, as ChartSchema.xAxis reports), and yAxis is a list. No key list, no subset; stripImportedDefaults as in PR objectui#10511. No renderer changed; the only hunk outside packages/types is the granted fixture-line cast
pins	39 tests; mutation 3 (both faces reset to base) gives 19 failed | 20 passed plus the exact TS2344 / TS2578 set. The round-1 reviewer re-ran it
changeset	'@object-ui/types': minor, Clause-②: yes. After four prose rounds, every sentence was confirmed at source for every chart type and row set. The lead-in now gives the version policy's own reason (a narrowed accept set is breaking semantics, shipped as minor), and the bullets state only equivalences that hold through the one normalization point. Frontmatter byte-identical across all rounds (md5 ecedb10c5189b2c8841ea736b67c3cc6)
reviews	round 1 PASS at a6e5c6d (5832280197), which also found the lead-in "each of them draws a chart today" false; the seat held landing on it. Round 2 FAIL at 0e71020 (5832703331: three over-broad conditions). Round 3 FAIL at 5367bc1 (5833163424: the minor clause). Round 4 PASS at CONTRACT_REVIEW_TIER on this head, record posted with this landing. The seat read all four transcripts: every turn ran at tier
serial	git merge-tree against main 98b1a7cac: clean. Main's intervening objectql.ts commits (PR objectui#10595, PR objectui#10626) are at distant lines
governed	NOT GOVERNED
CI	on b2936fc: 0 red at review time; landing waits on the queue's own run
closing keywords	Fixes #10518 only (the live body still reads Part of; the landing body replaces it)

Findings, each with its disposition

• Round-2 reviewer, class a: an object-bound chart that names its category with aggregate.groupBy alone draws missing-category-key, although the objectui#8168 remedy list names groupBy first. ObjectChart never forwards it as xAxisKey ⇒ filed as objectui#10634.
• Dev, round 1: xAxisField / yAxisFields / aggregation are declared on this node and not read ⇒ filed earlier as objectui#10608.
• Round-1 reviewer: the yAxis non-list refusals are pinned by code and path only, and the remedy text is unpinned ⇒ Acceptance notes.

Deviations recorded (seat)

• The round-1 PASS was not landed: the seat treats a false published changeset sentence as blocking, and four prose rounds followed. Twice (rounds 2 and 3) the seat's own direction left a clause the review then refused; round 5 applied the reviewer's exact replacement text.
• The PR body is the dev's round-4 replacement. The seat edited it in four places: the round count, which review round found what, the round-5 bullet, and "the body edits". It also retitles the PR to name both keys, with !, because the changeset states breaking semantics: feat(types)!: declare the spec's axis config on ObjectChartSchema.xAxis / yAxis (objectui#10518).
• The PR assignee is set (os-elon-musk).

State

In one stroke: the PR body and title, ready and auto-merge (squash), through the relay ops issue_patch + pr_ready + automerge_enable.

---

Generated by Claude Code