content/docs/core/report-schema.mdx still teaches `objectName`-based column hydration, which has no read point

[os-zhuang]

Found while implementing #5047 (migrating the two plugin-report documents to the dataset-bound form). Filed unassigned and out of that card's scope: #5047 is scoped to packages/plugin-report/README.md and content/docs/plugins/plugin-report.mdx. This is a third document with the same defect.

Measured on origin/main at 958d757.

The claim

content/docs/core/report-schema.mdx:

• :93 — comment on a code block: "object's ObjectField when the report has an objectName."
• :130 — "When the report binds an objectName, columns inherit type, ..."

Why it is wrong twice over

1. objectName is not a report key any more. ReportSchema (@objectstack/spec 17.0.0) is z.core.$strict. Parsing a report that carries it:

unrecognized_keys: Unrecognized key(s) on this report: `objectName`

The type side agrees — TS2353: Object literal may only specify known properties, and 'objectName' does not exist in type ....

2. Nothing implements the hydration. objectName has zero read points in packages/plugin-report/src — the only occurrences are two comments describing the retired query form, plus test fixtures asserting that such a document is not a dataset report:

grep -rn "objectName" packages/plugin-report/src
# ReportRenderer.tsx:102 (comment: "Stored pre-9.0 spec JSON (objectName/columns query form)")
# DatasetReportRenderer.tsx:7 (comment)
# __tests__/DatasetReportRenderer.test.tsx:65 expect(isDatasetReport({ ... objectName: 'task' ... })).toBe(false)

So the sentence promises a runtime behaviour that no code performs, keyed off a property the schema rejects.

The equivalent claim in packages/plugin-report/README.md is removed by #5047's PR. This document was left alone deliberately, to keep that PR to its two documents.

Recheck

grep -n "objectName" content/docs/core/report-schema.mdx
grep -rn "objectName" packages/plugin-report/src # comments + a negative test only

Related: #5047 (the same class in the two plugin-report documents), #4600 (same class, dashboard examples).

[os-support-ai]

Triage: queued as Task (documentation) — a docs page teaching objectName-based column hydration that has no read point is a false affordance on an authoring surface; the fix rewrites the page to the shape the renderer actually reads. (Triage seat, session session_019gCKd9EZfQ6MbGTnMHHJvW.)

---

Generated by Claude Code

[os-support-ai]

Claim: PM loop round 12 (refill)
Session: session_01RV6yuVCxymHYE16PL9vQkE
Branch: claude/issue-5136-report-schema-doc-hydration
Worktree: objectui-issue-5136
Domain: repo:objectui (docs)
File surface: content/docs/core/report-schema.mdx (stop on breach; explain in the report)
Container & model: S, mode:subagent, model: sonnet
Clause-②: no — docs-only; describes what the renderer already does, changes no behaviour.
Serial constraints cleared: content/docs/core/** is free. Sibling #5225 is dispatched in the same batch and writes only inside packages/plugin-report (test isolation) — this card reads that renderer to learn the real hydration shape but writes only docs, so there is no write overlap. ⛔ If #5225's work turns out to change what the renderer reads, stop and report rather than documenting a moving target.

Triage ruling (2026-08-18, session session_019gCKd9EZfQ6MbGTnMHHJvW), binding: queued as Task (documentation) — "a docs page teaching objectName-based column hydration that has no read point is a false affordance on an authoring surface; the fix rewrites the page to the shape the renderer actually reads."

So the deliverable is not "delete the wrong paragraph" — it is: establish, by reading the renderer, what column hydration actually keys on, then rewrite the page to teach that. Zero-hit greps must be counter-probed with a term known present in the same file, or the "no read point" claim is not re-established.

---

Generated by Claude Code

[os-support-ai]

{
 "issue": 5136,
 "status": "done",
 "branch": "claude/issue-5136-report-schema-doc-hydration",
 "pr": "https://github.com/objectstack-ai/objectui/pull/5275",
 "premise_still_valid": true,
 "summary": "Re-verified on origin/main (41f498bcb) that objectName has zero read points in packages/plugin-report/src (comments + a negative test only; counter-probe confirmed grep works). Traced the real column-hydration path to ReportViewer.renderCellValue (packages/plugin-report/src/ReportViewer.tsx), which reads field.type/options/referenceTo/label directly off each author-declared ReportField and hands them to @object-ui/fields's getCellRenderer -- no ObjectField/objectName lookup exists anywhere in the dispatch chain (ReportRenderer -> DatasetReportRenderer / specReportToPresentation). Rewrote the two false objectName-hydration claims in content/docs/core/report-schema.mdx to teach that real, author-provided shape, and fixed the page's three code samples which imported/annotated a ReportSchema type that does not exist in @object-ui/types (real name: ReportComponentSchema) -- same file, same false-affordance defect class.",
 "tests": "node scripts/check-doc-component-types.mjs -> pass (Every documented component type is registered); node scripts/check-doc-links.mjs -> pass (Links are valid across 13 scan roots); node scripts/check-control-bytes.mjs -> pass; node scripts/check-changeset-presence.mjs -> pass (no changeset owed, content/docs/**-only change). node scripts/check-doc-snippet-types.mjs: measured, not run to completion -- content/docs/core/report-schema.mdx has 0 fences in TS_FENCE_LANGUAGES ({ts,tsx,typescript}; script :196) out of 11 total (all plaintext), so scanFences (:349) never collects a block from this file and it correctly has no UNGATED_DOCS entry either way; running it to completion requires building 11 unrelated packages' dist and would not exercise this page's content, so I did not build the workspace for it. All commands run at commit c177e16b4 (final HEAD, matches the branch pushed and the PR).",
 "open_questions": [],
 "out_of_scope_findings": []
}

PR: #5275

---

Generated by Claude Code

---

Generated by Claude Code