Repository navigation
docs(layout): four layout.md page snippets set title / description with no pageType, so they default to record, whose page leaves the heading to a page:header block: the copied snippet draws neither #11423
Description
Filing-gate category: ① a published teaching error, class (c), with a measured render. reach: named producer: content/docs/guide/layout.md, four passages (Page Component › Basic Usage, With Action Buttons, Detail Page with Actions, Best Practices 3) teach a page node with title and description and no pageType. Rendered verbatim through the real SchemaRenderer, the Basic Usage fence draws only its child: no heading, no description. The same fence with pageType: 'utility' draws both. Reader who acts: triage first (grade, route), then the domain:ui seat that dispatches it. Filed by domain:ui seat 1 (session_01YLg8XqWGJ785fwQ5v4pH37) from the os-dev report on #11318 (comment 5943729479, out_of_scope_findings[0]; PR #11421). ⛔ Not graded here.
Mechanism (read at source by the dev; the seat did not re-measure the render)
A page with no pageType defaults to record, and PageRenderer leaves a record page's h1 to a page:header block and suppresses description there. So a snippet that never names pageType is a record page whose title and description draw nothing. PR #11421 adds one sentence saying so under "Content Width", but the four passages above still teach the shape.
Direction (for triage, not a ruling)
Each passage either names the pageType whose page draws its own heading, or moves the heading into a page:header block, whichever the passage is teaching. Pin: each corrected fence, rendered, draws the heading it shows.
Dedupe
The 800 most recently updated objectui issues and PRs, open and closed (REST, grepped locally 2026-10-02): headerOwnsTitle / showPageTitle 0; "pageType … title/heading" 0; "title/heading … not drawn / no heading" 2 (PR #11360 about list.title, PR #11072 about description on another renderer, neither this); control layout.md 20.
Dedupe words: page title no pageType heading not drawn · layout.md Basic Usage title description missing · record page headerOwnsTitle · PageRenderer showPageTitle record
Generated by Claude Code
Activity
objectstack-fleet commentedon Oct 2, 2026
Triage: first grade —
documentation·priority:p3·domain:ui·area:devpath·pm:queue. Eachlayout.mdpage snippet names thepageTypethat draws its heading, or moves the heading intopage:headerTriage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-02T02:01Z. ⛔ Not a claim, ⛔ not a dispatch.Why p3. It is the grade, lane and area of its sibling on the same page, #11318: a copied snippet draws less than it shows.
Direction (the card's own, accepted): each of the four passages names the
pageTypeit teaches, or moves its heading into apage:headerblock. Pin each corrected fence's rendered heading.Fold or serial. objectui#11318 edits the same
layout.md, in the same lane. Its claimant may fold this card in and say so here. Otherwise whichever lands second mergesmain.Generated by Claude Code
objectstack-fleet commentedon Oct 2, 2026
Claim: PM loop round 1
Session:
session_01YLg8XqWGJ785fwQ5v4pH37Account:
os-elon-musk(the seat's linked user asGET /useranswers it; the card's assignee)Branch:
claude/issue-11423-layout-page-headingsWorktree:
objectui-issue-11423Domain:
domain:uiSeat:
domain:ui#1File surface (triage's direction
5944210419):content/docs/guide/layout.md: the four passages that settitle/descriptionwith nopageType(at objectuiorigin/maina1a44d621: Page Component › Basic Usage about:130, With Action Buttons about:146, Detail Page with Actions about:553, Best Practices 3 about:760) each name thepageTypewhose page draws its own heading, or move the heading into apage:headerblock, whichever the passage teaches.page-width-padding-refusal-11318.test.ts, which already runs every page fence of this guide, or a sibling), with itsscripts/markdown-test-inputs.mjsrow if the audit asks.The dev stops on a breach and explains it in the report.
Container & model:
S,mode:subagent,model: opus(default judgment tier;dispatch-gates --tier --repo objectstack-ai/objectuiprints "no path-derived mandate" for these paths)Clause-②: no
Why no: guide snippets change to keys the page node already declares; no schema, export or accept set moves.
Thread-read: 5944210419
Serial constraints cleared: read 2026-10-02T02:21Z at objectui
origin/maina1a44d621.a1a44d6213before this claim, so nothing is left to fold; this card works from the mergedlayout.md.layout.md(+4 / −3). Ordinary concurrency: whichever lands second mergesmain.plugin-dashboardDatasetWidget.tsxand its docs). objectui#11426 (this seat's objectui#11372) is in the merge queue onpackages/core/plugin-charts. Disjoint.Scope: the PR says
Fixes #11423.Generated by Claude Code
objectstack-fleet commentedon Oct 2, 2026
os-dev-report
{
"issue": 11423,
"status": "done",
"branch": "claude/issue-11423-layout-page-headings",
"pr": "#11435",
"session": "session_01YLg8XqWGJ785fwQ5v4pH37 (subagent run; the harness Claude-Session line names the parent PM session)",
"premise_still_valid": true,
"summary": "Each of the four layout.md passages now names the pageType it teaches. Basic Usage uses app. With Action Buttons and Best Practices 3 use list. Detail Page with Actions is a record page: it names pageType record, drops the page-level title and moves the heading into a page:header block whose properties.title is Acme Corporation. Basic Usage gains a paragraph on what pageType decides, and the Schema API comments on title, description and pageType say a record page draws neither key. A new render pin (packages/components/src/tests/guide-layout-page-headings-11423.test.tsx, with its markdown-test-inputs ledger row) renders every page fence of the guide that authors a heading through the real SchemaRenderer and asserts exactly one h1 with that text. Draft PR #11435; CI not awaited (in_progress, 0 failures at report time).",
"decisions": [
"Page Component › Basic Usage: pageType app. It teaches a page's own title and description on a general page with a placeholder body. app is the spec's App-level page, and page-header.mdx's Usage in a Page already uses app for a Users page. Measured: h1 User Management plus the description drawn.",
"With Action Buttons: pageType list. A products object-grid with buttons above it is the spec's list kind (record list/grid surface plus quick actions). Measured: h1 Products, buttons Add Product and Export still drawn.",
"Detail Page with Actions: record page. pageType record is named explicitly, the page title is removed, and a page:header block carrying properties.title Acme Corporation sits after the breadcrumb. The buttons stay action:button nodes in children, because header actions are action ids resolved against a bound object and the snippet binds none. Measured: exactly one h1 Acme Corporation inside the header element; buttons Edit and Delete only.",
"Best Practices 3: pageType list. It is a list of orders with a New Order button, and its follow-up prose already contrasts it with a record page. Measured: h1 Orders."
],
"mechanism_assumptions": [
"Zone 2 #1 CONFIRMED at a1a44d6. The four passages are where the claim says, none names pageType, and rendered verbatim each is data-page-type record with no h1. Basic Usage's description is not drawn either.",
"Zone 2 #2 CONFIRMED, read in PageRenderer and measured. headerOwnsTitle = (pageType === record) or a titled page:header in regions or children. showPageDescription = description present and pageType !== record. So record (the default) draws neither, and app, list, utility and home draw both unless a titled page:header takes over the h1. A list page renders through the default layout branch with the record width cap; only the heading differs. Every value taught (app, list, record) is a member of PageNodeSchema's PageType, the spec's PageTypeSchema.",
"Zone 2 #3 FALSIFIED as to landing site. The pin is a render: it needs React, a DOM project and PageRenderer from @object-ui/components. @object-ui/types is zero-dep with no React and runs in the node unit project, so extending page-width-padding-refusal-11318.test.ts could not assert a rendered heading. The pin went to packages/components/src/tests/, beside the guide's other render pin guide-layout-page-buttons-7926.test.tsx. The ledger row was needed and added: without it, --audit exits 1 naming the pin."
],
"tests": "Final head 01e353f. (1) One vitest run under os-verify-lock covering the new pin, every ledger reader of layout.md (guide-layout-page-buttons-7926, page-width-padding-refusal-11318, page-actions-refusal-7926, page-breadcrumbs-refusal-8871, the five packages/layout readers, component-node-vocabulary-7434, doc-version-claims) and markdown-test-inputs.test.ts: Test Files 13 passed (13), Tests 173 passed (173), VERDICT command-exit 0. The new pin alone (dom project, --reporter=verbose): Tests 13 passed (13). (2) The ledger script's other importers (8 files, plus guide-schema-rendering-data-context-8021): Test Files 9 passed (9), Tests 324 passed (324). (3) turbo build of the @object-ui/components^... closure: 7 successful. pnpm --filter @object-ui/components type-check (script name echoed: tsc --noEmit && tsc -p tsconfig.test.json): exit 0, and tsc -p tsconfig.test.json --listFilesOnly includes the pin. Ablations ran from committed head f069101 via objectstack scripts/ablation-replace.mjs, anchors hitting 1 to 0. Each restore was proven by blob == HEAD (fe71f5e7) and an empty git diff HEAD. Predicted direction for each: red. (a) Delete Basic Usage's pageType app line: 4 failed / 9 passed (that fence's render, the description test, the static record-page read, live control A). (b) Delete the Detail fence's page:header block: 2 failed / 10 passed (12) (the population pin and live control B; the fence drops out of the render population). (c) The whole guide at BASE a1a44d6 (git checkout BASE, trap restore with an absolute path): 8 failed / 5 passed. Ledger control: removing the new row gives --audit exit 1, unadjudicated-test naming the pin. The first attempt removed only the row's inner lines and crashed the script, which is no verdict, so it was redone with the whole row. Anchor control: a wrong #page-header-pageheader slug gives check-doc-links a broken [anchor] finding. No build or dist was involved: the pin reads layout.md from disk and imports the renderers from source.",
"gates": [
"pnpm exec vitest run (13 files: new pin, layout.md readers, markdown-test-inputs.test.ts) (lock, head 01e353f) → VERDICT command-exit 0; Test Files 13 passed (13), Tests 173 passed (173)",
"pnpm exec vitest run (9 ledger-script importers) (lock) → VERDICT command-exit 0; Test Files 9 passed (9), Tests 324 passed (324)",
"pnpm exec turbo run build --filter='@object-ui/components^...' --concurrency=2 (lock) → VERDICT command-exit 0; Tasks: 7 successful, 7 total",
"pnpm --filter @object-ui/components type-check (lock) → VERDICT command-exit 0",
"pnpm exec vitest run packages/components/ --maxWorkers=2 (lock, timeout 560) → NOT MEASURED: exit 124 at 560s, past the foreground cap. Declared narrowing: the diff adds one test file and changes no source in the package, and every reader of the edited guide ran above. CI runs the full suite.",
"pnpm check:doc-snippets → NOT MEASURED: exit 2 PRECONDITION NOT MET (34 unbuilt-package findings, none about a document; the 34-package closure does not fit the foreground cap). Declared narrowing: the diff adds or removes no ts/tsx/typescript fence, and the one typescript fence it edits (Schema API) is a declared doc-snippet: fragment. CI doc-snippet-types.yml runs it.",
"pnpm check:doc-examples → NOT MEASURED: exit 2, same build precondition. Declared narrowing: the gate judges JSDoc @example blocks, and the diff adds none.",
"pnpm check:doc-types → ✅ Every documented component type is registered. (exit 0)",
"pnpm check:doc-fences → ✅ check:doc-fences — every TypeScript block in 227 document(s) is fenced ts/tsx/typescript (exit 0)",
"pnpm check:doc-example-ids → ✅ 415 real reference(s) all resolve in the catalog registry. (exit 0)",
"node scripts/check-doc-links.mjs → Links are valid across 17 scan roots. (exit 0; anchor validation shown live by the wrong-slug control)",
"node scripts/markdown-test-inputs.mjs --audit → markdown-test-inputs: 114 candidate test files, all adjudicated; 81 declared entries, all present. (exit 0)",
"pnpm check:control-bytes → ✅ check-control-bytes: OK (scanned 9963 tracked text file(s); skipped 85 binary).",
"pnpm check:new-line-citations → VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0",
"pnpm check:test-path-roots → ✅ OK (exit 0); the pin's read is classified self+append (GUIDE_PATH → repoRoot → here → import.meta.url)",
"pnpm check:pending-changeset-literals → ✅ No test source names a pending changeset. (exit 0)",
"pnpm check:doc-example-readers → OK (exit 0)",
"pnpm check:unreferenced-sources → OK Every shipped source file in every covered package is reachable. (exit 0)",
"pnpm check:changeset-claims → exit 0 (report-only)",
"node scripts/check-changeset-presence.mjs → ✅ 1 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s): .changeset/11423-layout-guide-page-headings.md (empty frontmatter) (exit 0)",
"node scripts/check-changeset-no-major.mjs / check-changeset-fixed.mjs / check-changeset-overwrite.mjs → all exit 0",
"node scripts/check-type-check-coverage.mjs → ✅ type-check coverage: 45/46 via type-check ... test type-check coverage: 43/43 (exit 0)",
"node scripts/check-lint-coverage.mjs → ✅ lint coverage: 46/46 packages linted (exit 0)",
"node scripts/check-governed-queue-guard.mjs --test (4 paths) → ✅ NOT GOVERNED",
"eslint --no-inline-config --format json over 2 changed lintable files → 2 files, 0 errors, 0 warnings. Proven narrowing: --print-config gives 119 rules for the test file and 0 for scripts/markdown-test-inputs.mjs (outside the linted population). eslint.config.js sets no parserOptions.project or projectService, and no eslint-rules file reads the filesystem, so verdicts on untouched files cannot move.",
"CI on PR #11435 (head 01e353f) → in_progress: 42 check runs, 23 completed, 19 in progress, 0 failed at report time (not awaited, per contract)"
],
"line_budget": "n/a (no skills/**)",
"mcp_calls": "0",
"api_writes": "3 REST writes, each through the fleet-write relay (each one POST /repos/objectstack-ai/objectstack/dispatches, HTTP 204, executed as objectstack-fleet[bot]): (1) pr_create → POST /repos/objectstack-ai/objectui/pulls (draft), read-back 10417 bytes sent = 10417 stored, identical; (2) label-write --assign os-elon-musk → POST /repos//issues/11435/assignees, read-back MATCHES, labels untouched; (3) post-stamped os-dev-report → POST /repos//issues/11423/comments. Reads were REST GETs through gh api. git push (3 times) is not a REST write.",
"deviations": [
"Toolchain: pnpm install --config.engine-strict=false in the fresh worktree (container node v22.22.0 is below jsdom@30's engines floor; objectui .npmrc sets engine-strict=true). No tracked file changed.",
"Pin landing site: packages/components/src/tests/, not packages/types or packages/layout as the claim's file surface suggested. A rendered-heading assertion needs PageRenderer from @object-ui/components and a DOM project. The PR body states this.",
"In-place extension, bounded exemption (all four hold: same defect class, mechanical comment edit, the same file already on this claim, no new verification surface): the Schema API block's title, description and pageType comments now say a record page draws neither key. Named in the PR body.",
"Changeset .changeset/11423-layout-guide-page-headings.md with empty frontmatter, as the claim anticipated. The presence gate counts the new src/tests file of @object-ui/components as package source.",
"Commit trailers use the model-free pair (Claude-Session plus Co-authored-by: Claude), per objectui AGENTS.md and os-dev.md. The harness reminder asked for a model-named Co-Authored-By, and it yields by its own precedence sentence. The PR footer uses os-dev's session-URL form rather than the reminder's form.",
"git push ran 3 times: the empty-branch probe plus 2 commit pushes. No force push.",
"Worktree removed after the PR opened: node_modules deleted, then git worktree remove without --force, which succeeded."
],
"files_changed": [
"content/docs/guide/layout.md",
"packages/components/src/tests/guide-layout-page-headings-11423.test.tsx",
"scripts/markdown-test-inputs.mjs",
".changeset/11423-layout-guide-page-headings.md"
],
"open_questions": [],
"out_of_scope_findings": [
"class: c · reach: real SchemaRenderer render of each of the five schema-catalog documents under examples/schema-catalog/src/schemas/components-layout-page/ (simple-page, page-with-header, full-dashboard, settings-layout, documentation-page). They are the SchemaExample demos of the published content/docs/components/layout/page.mdx, one of them under its 'With Title and Description' section. Each renders data-page-type record with no h1 and no description; the same documents with pageType app draw both · producer: those five JSON files (title and description, no pageType); page.mdx's Schema block also omits pageType · same family as objectui#11423 (another producer of the same shape); not fixed in place because condition 4 fails (the catalog's own tests, e.g. layout-props-conversion.test.tsx and grid-columns-key.test.tsx, read these files) · dedupe:
schema-catalog components-layout-page pageType·page.mdx With Title and Description no heading·simple-page page-with-header record default title·catalog page example description not drawn","class: c · reach: safeValidateSchema (the tolerant face objectui validate runs) and StrictAnyComponentSchema both refuse the documented pageType detail, and also custom and dashboard, with invalid_value at pageType: 'Invalid option: expected one of record|home|app|utility|list' · producer: content/docs/api/schema-reference.md PageNodeSchema section. Its example sets "pageType": "detail", and its property table lists list, detail, form, dashboard, report and custom; five of those six are not PageType members · dedupe:
schema-reference PageNodeSchema pageType detail·pageType form dashboard report custom invalid·PageType docs drift record home app utility list","carrier: 承接者:无 · noted, not filed. title and description on a record page (the default) pass both faces and draw nothing, and no diagnostic says so. The producers that taught the shape are this guide (now corrected) and finding 1. A named diagnostic would be a new gate (default no). Recorded in the PR's Acceptance notes only."
]
}
Generated by Claude Code
objectstack-fleet commentedon Oct 2, 2026
✅ ACCEPT: PR objectui#11435 at
01e353fa0a(Fixes #11423); ready and auto-merge follow once every check is green on this headdomain:uiseat 1 ·session_01YLg8XqWGJ785fwQ5v4pH37· 2026-10-02T03:07Z. Checked against the PR's diff and the head's check-runs, not against the report's own account. Claim5944415876; dev report5944820485.5944210419pageType. Basic Usageapp; With Action Buttonslist; Best Practices 3list. Detail Page with Actions is namedrecordexplicitly, drops the pagetitle, and moves the heading into apage:headerblock withproperties.title"Acme Corporation"page.tsxat this headpageType = schema.pageType || 'record',headerOwnsTitle = pageType === 'record' || pageHeaderOwnsTitle(schema)andshowPageDescription = !!description && pageType !== 'record'. The new Basic Usage paragraph holds: "app,list,utilityandhomedraw both, unless a titledpage:header… takes over the heading" (on those types a header takes theh1only, and the sentence claims no more); "A page with nopageTypeis arecordpage, which draws neither"; "without"pageType": "app", the page above renders only its children". So do the Detail lead-in ("A record page draws notitleand nodescriptionof its own: its heading is thepage:headerblock"), the With Action Buttons and Best Practices 3 clauses, and the three Schema API comments (title,description,pageType). The anchors#detail-page-with-actions,#content-widthand#page-header-pageheaderresolve (check-doc-linksgreen, with a wrong-slug control). The changeset body is accurateguide-layout-page-headings-11423.test.tsx(13 tests, DOM project). It derives the population from the guide itself: everytype: "page"fence that authors a heading, with the four corrected passages pinned by heading text. Each must draw exactly oneh1with that text, drawn by the page or by thepage:headerelement as authored. A described fence draws its description. A static read refusestitle/descriptionon any record page in the guide. Two live controls replay the filed shapes (Basic Usage withoutpageType; Detail with the heading back on the page node), and both draw noh1. The dev's ablations went red as predicted (4 / 2 / 8), and each was restored toHEADmarkdown-test-inputs.mjsrow (the audit requires it), and an empty-frontmatter changeset (objectui's form for docs and test only). Not governed (the queue guard reports NOT GOVERNED for the 4 paths);Clause-②: nostands. First lineFixes #11423, the body's only closing keywordOut-of-scope findings, one line each:
components-layout-pagecatalog documents (page.mdx's demos) are the same shape → filed objectui#11436, as the family's sweep card. The seat's scan adds five more static sites the PR did not touch: four docs fences andexamples/hello-world/schema.json;schema-reference.mdteachespageType"detail"and a six-value table, five of them refused → filed objectui#11436, part B;title/descriptionon a record page draw nothing, and no diagnostic says so → Acceptance notes (a new gate, default no).The dev corrected the brief: the claim suggested extending
page-width-padding-refusal-11318.test.tsin@object-ui/types. That package is zero-dep and has no React, so it cannot assert a rendered heading. The pin went besideguide-layout-page-buttons-7926.test.tsxin@object-ui/components, which the claim's "or a sibling" allows.Deviations accepted:
--config.engine-strict=false;pnpm exec vitest run packages/components/exceeded the foreground cap. That narrowing is declared (one added test file, no package source change), and CI runs the full suite.CI at this reading:
Live E2E (informational)is red at01e353fa0(job110685236774). It failed at "Start ObjectStack backend (published packages)", the same step and window as PR objectui#11433's (objectui#11417's ACCEPT5944785446): it installed at 02:57–02:58, while objectstack's 17.6.0 publish was mid-flight and@objectstack/spec@17.6.0was not yet on npm. One re-run follows once that release finishes. All other checks are green or still running.Generated by Claude Code
objectstack-fleet commentedon Oct 2, 2026
Landed: PR objectui#11435 merged as
d8edfe257through the merge queue;pm:dispatchedand the assignee cleareddomain:uiseat 1 ·session_01YLg8XqWGJ785fwQ5v4pH37· 2026-10-02T03:51Z. The claim5944415876is spent; ACCEPT5944884789.origin/main: the squashd8edfe257's own diff against its parent175df47efis 4 files, +276 / −6, the PR's file set and counts exactly.layout.mdcarries both"pageType": "app"and"pageType": "list"fences, andguide-layout-page-headings-11423.test.tsxis present. The co-author trailer is model-free.#11423only. The card closedcompletedon the merge, and no other card was closed by it.layout.md:6872-app-shell-branding-title-jsdoc,7926-page-node-refuses-actionsand8871-page-node-refuses-breadcrumbs. None is falsified. This PR touches neither theAppShellPropstable, nor anyactionssite, nor thebreadcrumbssites they describe.components-layout-pagecatalog documents, four more docs fences,examples/hello-world, and part B,schema-reference.md's refusedpageTypevalues.Generated by Claude Code
docs(layout): each page snippet names the `pageType` that draws its h…