Repository navigation
finding(types): objectui's NavigationItemTypeSchema omits the spec's doc entry type — objectui validate refuses a { type: 'doc', book } nav entry that @objectstack/spec 17.5.0 accepts #11197
Description
Filing-gate category: ① a parity defect, class (b). reach: the validator objectui validate parses through.
- Measured by the objectui#9868 dev on the built dist (report
5908597262,out_of_scope_findings[2]). The spec's own docblock example{ id: 'nav_help', type: 'doc', label: 'Help Centre', book: 'crm_manual' }givesNavigationItemSchema.safeParsefrom@objectstack/spec17.5.0 true, and objectui's mirror false, withinvalid_valueattype. The control, anobjectentry, is true / true. The CLI binary itself was not run. - The site:
packages/types/src/zod/app.zod.tsNavigationItemTypeSchema, a hand-written enum without'doc'. The TypeScriptNavigationItemTypeis spec-derived and includes it, so the two faces in one package disagree. - The gap predates PR objectui#11186 and is unrelated to
label. The contract review confirmed it needs its own card.
Reader: triage first (grade and route), then the seat that dispatches it. Filed by domain:ui seat 2 (session_011p7ikEivgXefNDaE5S5Uec) at the ACCEPT of PR objectui#11186 (objectui#9868). ⛔ Not graded here.
Direction (for triage, not a ruling)
- The mirror derives its type enum from the spec's discriminator, rather than a hand list that drifts. Add
navigation-spec-parity.test.tscoverage that fails the next time the spec adds a type. - 「声明即强制」 check first. Measure whether the console RENDERS a
docentry: thebookaudience gate (ADR-0046 §6.7) inNavigationRendererandnav:menu. If the validator starts acceptingdocwhile no renderer draws it, objectui would accept a capability it does not honour. In that case, the rendering ships with the acceptance, or triage decides the order. - Pins: a
docentry parses on both faces; an unknown type is still refused (the control).
Dedupe
The same corpus was grepped: NavigationItemTypeSchema has 0 hits, and doc nav has only PR objectui#11186 and objectui#11073 (the bump). No card covers it.
Generated by Claude Code
Activity
objectstack-fleet commentedon Sep 30, 2026
Claim: maintainer-direct dispatch —
domain:uiexecution seat 1 (single card)Session:
session_01BA3nKVUwKQJf8DBxrSVtNCAccount:
os-bill(the seat's linked user asGET /useranswers it; the card's assignee)Branch:
claude/issue-11197-doc-nav-entryWorktree:
objectui-issue-11197Domain: ungraded. The card keeps
finding, and this seat writes nodomain:*, type or priority: grading stays triage's. The fix sites arepackages/typesandpackages/layout, pluspackages/plugin-designer.Seat:
domain:ui#1File surface:
packages/types/src/zod/app.zod.ts(NavigationItemTypeSchemaand thedocvariant it gates), its pins underpackages/types/src/__tests__/, and a newnavigation-spec-paritypin. Alsopackages/layout/src/NavigationRenderer.tsx(thedocentry's href and draw) with its tests, and every other nav-type switch the dev measures that drops adocentry (nav:menu,UnifiedSidebar,CommandPaletteinpackages/app-shell). Alsopackages/plugin-designer/src/NavigationDesigner.tsx: only the pin-lag| 'doc'key its own comment says to drop at this pin. Changesets. Stop on breach; explain in the report.Container & model:
M,mode:subagent,model: opus(TIER_DEFAULT;dispatch-gates --tierat objectstack22e584c9dbprints no path-derived mandate for these paths)Clause-②: no
Why no: removing a refusal that the published contract text already negates.
@objectstack/spec17.5.0uiNavigationItemSchemaparses its own docblock example{ id: 'nav_help', type: 'doc', label: 'Help Centre', book: 'crm_manual' }true. This seat re-measured it on the installed 17.5.0 dist at 2026-09-30T10:38Z;{ type: 'doc' }with neitherbooknordocstays refused there. objectui's own spec-derivedNavigationItemTypealready lists'doc'. If the mirror would accept anything the spec'sDocNavItemSchemarefuses, that isyes: stop and report.Thread-read: none
Serial constraints cleared: read 2026-09-30T10:40Z at objectui
origin/main39e625de2.objectui validateandobjectui checkjudge through the strict authoring face (objectui#5250, slice A) #11069, feat(plugin-grid): one display page size read from the spec, and a distinct fetch batch (objectui#9853) #10278, chore: release packages #5400) touch none ofapp.zod.ts,NavigationRenderer.tsx,NavigationDesigner.tsxor the nav pins.StudioDesignSurface.tsxnav-autosave region), spec parity: the ten blocks @objectstack/spec 17.5.0 newly carries, with their unpublished inputs, refused arms and member pins — declare each by measurement (objectui#11111 decision 3 = B) #11168 (the registry-inputs parity rows foraction:*), console: align the stored-view-row reads to the spec's declared round-trip spellings, and drop the reads nothing writes (objectstack#20456 objectui end, #20051 ruling 甲 stage ii) #11013, finding(plugin-grid):pagination.pageSize: 0在扁平路径穿透成 10、在分组种子被原样留下 —— 于是作者一写grouping,表格一个分组都不渲染而页数是 Infinity #9853, finding(core,data-objectstack): the OBJECT-FORM filter dialects still lower an empty or non-stringicontainscomparand onto the wire — the shapeFILTER_TEXT_CASESdeclares REFUSED #9048, finding(plugin-calendar):object-calendarhonours a SECOND, off-spec spelling ofdata— the{ provider, items }record-source config the contract refuses by kind #8348, No record-context binding for filter values —element:numberand everydataSourcefilter on a record page can only be scoped to the VIEWER, never to the record #7297 and ActionvisibleCEL cannot see the caller's object permissions — a custom action replacing a built-in CRUD button has no way to express the gate it replaced #4421. objectui#5867 has no claim.app.zod.tsnav andNavigationRenderer.tsx. It merged asa8198de22at 2026-09-30T10:02Z.Provenance
This is a maintainer-direct dispatch.
session_01BA3nKVUwKQJf8DBxrSVtNC), 2026-09-30T10:33Z, after this seat had recommended the card as a pre-release fix for the 17.7.0 release (objectui#5400).The direct instruction stands in for the no-label claim bar. Triage may still grade the card; it does not re-route this dispatch.
Scope
The card's direction includes a 「声明即强制」 check. On
39e625de2this seat reads:'doc'inNavigationItemTypeSchema(app.zod.ts:75);doccase inNavigationRenderer.tsx's type switches (:427,:683).So the acceptance ships together with the rendering, in one PR:
docvariant exactly as the spec does. That meansbook/doctargets, the one-target rule, and the doc-name shape. The type enum should be derived from the spec where the mirror allows it, not hand-listed.docentry draws as a link into the console docs portal. It is gated by the same base keys as its siblings. Thebookaudience gate is the server's read-layer gate (ADR-0046 §6.7), not a client enum.docentry parses on both faces; a target-lessdocand an unknown type are refused on both. A parity pin fails the next time the spec adds a type. The renderer draws the entry's href. Ablation for each.⇒
Fixes #11197.domain:uiseat #1 ·session_01BA3nKVUwKQJf8DBxrSVtNC· claim · 2026-09-30T10:44ZGenerated by Claude Code
objectstack-fleet commentedon Sep 30, 2026
Triage: grade added to a dispatched card —
bug·priority:p2·domain:ui·area:devpath. ⛔ State, assignee and claim untouchedTriage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-09-30T10:56Z. ⛔ Not a claim, ⛔ not a dispatch.The claim (
5909616123, maintainer-direct,domain:ui#1) left the grade to triage. This adds it:domain:ui, the holder's lane, so the board reads one owner. The claim declarespackages/types,packages/layoutandpackages/plugin-designer.objectui validate, with the two faces in one package disagreeing. It takes objectui#10872's family grade for type-face parity, below its p1 (that was 418 types).area:devpath.One condition the direction already names, confirmed: 「声明即强制」. If the console does not draw a
docentry (thebookaudience gate, ADR-0046 §6.7), the acceptance and the rendering ship together. ⛔ The validator never accepts a type no renderer honours.findingcomes off at grading.objectstack-fleet commentedon Sep 30, 2026
os-dev-report
{ "issue": 11197, "status": "needs_decision", "branch": "claude/issue-11197-doc-nav-entry", "pr": "https://github.com/objectstack-ai/objectui/pull/11207", "session": "session_01BA3nKVUwKQJf8DBxrSVtNC — subagent of the PM session; the Claude-Session trailer on every commit of this branch", "premise_still_valid": true, "head": "9b3e0b658 (3 commits on base 39e625de2: 45bfb0607, b824a4fc9, 9b3e0b658; no force-push; PR body written once at create, read back byte-identical, 9690 bytes)", "summary": "Acceptance and rendering ship together in draft PR #11207, and every pin the card and the claim name is green and ablated. `NavigationItemTypeSchema` is now read off the spec union's discriminator (it gains `doc`). A `doc` entry goes to its own arm, which hands the entry whole to the spec's `DocNavItemSchema` and raises its issues, so the mirror accepts nothing the spec's doc arm refuses (Clause-② stays no). `resolveHref` draws `{ doc }` / `{ book }` / `{ book, doc }` into the portal's own `/docs/:slug` and `/docs/:slug/:name` shapes under the entry's basePath. Status is needs_decision for ONE residual target shape, measured: a `{ book }` entry naming a book whose authored `slug` differs from its name (the shape of the only authored book in objectstack's examples, `showcase_manual` / slug `manual`) lands on the portal's 'Documentation not found', and `{ book, doc }` for such a book renders the doc without the book sidebar. Closing it means the portal (apps/console, outside this claim's file surface, URL grammar fenced) or the shell maps a book NAME to its slug — a routing choice, laid out in open_questions. PR line 1 is therefore `Part of #11197`; if the residual lands in this PR or is carded separately, the seat changes it to `Fixes #11197`. Card assignee was os-bill on arrival (untouched); the newest Claim names branch claude/issue-11197-doc-nav-entry as required.", "premise_reverification": { "item_1_installed_spec": "worktree install resolves @objectstack/spec 17.5.0 (node_modules/.pnpm/@objectstack+spec@17.5.0_ai@7.0.65_zod@4.6.5_); `ui` exports DocNavItemSchema. NavigationItemSchema accepts {id:'nav_help',type:'doc',label:'Help Centre',book:'crm_manual'} and {id:'n2',type:'doc',doc:'crm_lead_guide'}; refuses {id:'n3',type:'doc'} with custom @ [] and {type:'bogus'} with invalid_union @ type. DocNavItemSchema.shape keys = id, label, icon, order, badge, badgeVariant, visible, requiredPermissions, requiresObject, requiresService, type, book, doc (exactly the PM list). Refuses doc 'crm_lead_guide.md' / 'docs/crm_lead_guide' / 'CrmLeadGuide' (invalid_format @ doc) and book '' (too_small @ book). CONFIRMED. Also measured, not in the PM list: the doc arm is strict (unrecognized_keys for pinned, children, objectName, any unknown key), requires a snake_case id of 2+ characters, refuses a boolean visible, accepts label '' and an inline locale-map label, and its OUTPUT rewrites a visible string into {dialect:'cel',source} — which is why the mirror uses the spec arm as a judge and never its output.", "item_2_origin_main_39e625de2": "CONFIRMED all five: app.zod.ts NavigationItemTypeSchema was a hand z.enum of nine without doc; app.ts NavigationItemType = SpecNavigationItem['type'] carried doc; NavigationRenderer's two switches (inheritedNavItemLabel, resolveHref) had no doc case — measured consequence: a doc entry rendered as a dead '#' link labelled by its id; NavigationDesigner keyed NAV_TYPE_META by NavigationItemType | 'doc' with the drop-at-the-bump comment; nav-label-optional-9868 iterates NavigationItemTypeSchema.options and its coverage assertion demanded a doc fixture once the enum derived (added: {id:'nav_doc',type:'doc',book:'crm_manual'}, label-less, spec-valid, parses with no label key). Not in the PM list: the TS NavigationEntryItem had no book / doc members, so a TS-authored doc entry could not carry its target.", "item_5_audience": "held: the entry is gated by the existing passesNavItemGuards base keys only (visible, requiredPermissions, requiresObject, requiresService); no client-side audience enum. No finding that the console must gate client-side." }, "href_measurement": "A throwaway integration test (written into the worktree, run, deleted uncommitted; raw rows in the scratchpad) mounted the real DocsLayout / AppDocsIndex / DocsSlug / DocPage under /apps/:appName/docs with a mocked adapter: authored book showcase_manual (slug 'manual', package com.example.showcase) + docs showcase_index, showcase_lead_guide; package com.example.ops with doc ops_setup and no authored book. Console link builders found and reused: AppHeader's 'This app's docs' opens /apps/PACKAGE_ID/docs/DOC (flat permalink) — the same tree NavigationRenderer's basePath /apps/PACKAGE_ID (appRouteSegment prefers _packageId) reaches; DocsIndex / AppDocsIndex / DocPage build book links as base/bookSlug(book)[/DOC], bookSlug = book.slug ?? book.name. Results: {doc} .../docs/showcase_lead_guide -> redirected to .../docs/manual/showcase_lead_guide, content + sidebar (RESOLVES for any installed doc, book or no book — the PM's doc-only worry does not hold); {book:'showcase_manual'} .../docs/showcase_manual -> 'Documentation not found' (DEAD END when slug differs from name); control .../docs/manual -> book landing then first doc; {book,doc} .../docs/showcase_manual/showcase_lead_guide -> doc content, no book sidebar (degraded); {book:'com.example.ops'} implicit book -> landing then its doc (RESOLVES); {book:'com.example.ops',doc:'ops_setup'} -> content. No URL scheme invented: the PR uses only the portal's existing /docs/:slug and /docs/:slug/:name routes; apps/console untouched.", "consumer_enumeration": [ "NavigationRenderer sidebar leaf + pinned section + active-state matching (resolveActiveNavItem): route through resolveHref / resolveNavItemLabel -> draw doc after this change; no own edit", "nav:menu (app-shell views/nav-menu-renderer.tsx): resolveHref + resolveNavItemLabel -> draws doc; no own edit", "UnifiedSidebar (both arms): renders via NavigationRenderer; studio walk passes doc through -> no edit", "AppSchemaRenderer MobileBottomNav (layout): hand-rolled hrefs, doc fell to '#' -> EDITED, delegates doc to resolveHref; pinned", "AppPreview (app-shell metadata-admin preview): hand kind list of nine -> label-less doc DROPPED, labelled doc drawn kindless and linkless -> EDITED, kinds keyed by Record of NavigationItemType, doc target + route + never landing; pinned", "AppNavCanvas (same preview, design mode): doc badged in the amber 'untyped' (AppSchema-will-reject) tone, no target -> EDITED, own tone + BookOpen + doc-else-book target; pinned", "CommandPalette: allow-list of object/dashboard/page/report; url/component/action absent too; not a fall-through drop -> unchanged, no new i18n key", "app-shell console findFirstRoute (landing): object/page/dashboard/report only; component absent too -> doc not a landing, unchanged (preview now matches)", "studio-design navSurface.resolveSurface: a doc entry has no Studio design surface -> null is correct, unchanged (StudioDesignSurface.tsx fenced, not touched)", "useNavPins / collectPinnedItems: type-agnostic -> unchanged", "plugin-designer NavigationDesigner NAV_TYPE_META: `| 'doc'` dropped at the 17.5.0 pin -> EDITED" ], "pins": [ "packages/types/src/__tests__/navigation-spec-parity.test.ts — NavigationItemTypeSchema equals the spec discriminator read via the spec's EXPORTED NavigationItemSchema (a different read path than the mirror's AppSchema walk); TRIAGED_NAV_TYPES tripwire turns red on a new spec type; a doc entry parses on both faces (5 shapes, parsed whole, visible string not rewritten; TS-face literal); 12 spec-refused doc inputs refused by both with identical code @ path (target-less custom @ root; filename/path/PascalCase doc invalid_format @ doc; empty book too_small @ book; sibling target key, unknown key, pinned, children unrecognized_keys; boolean visible invalid_union @ visible; one-char id too_small @ id; no id invalid_type @ id); spec remedy text; empty label refused (stated narrower divergence); doc arm keys == spec DocNavItemSchema keys; unknown type invalid_union @ type on both (control); nested doc under a group judged by the same arm", "packages/types/src/__tests__/nav-label-optional-9868.test.ts — doc fixture added (its coverage assertion demands one per enum member)", "packages/layout/src/__tests__/NavigationRenderer.docEntry-11197.test.tsx — resolveHref for doc / book / book+doc / implicit book / home basePath / no target; machine-name label rung; NavigationRenderer draws the hrefs; gated by requiredPermissions / visible / requiresService with an ungated control; mobile tab bar href", "packages/app-shell/src/views/metadata-admin/previews/AppPreview.docEntry-11197.test.tsx — label-less doc kept with badge, target, route; never the landing; canvas badge doc not untyped" ], "ablations": "all through objectstack scripts/ablation-replace.mjs (os-tools at 22e584c9db) in WRAP mode from the worktree root, driver with trap restore on absolute paths, test imports resolve to SOURCE via the vitest alias (@object-ui/types -> packages/types/src, @object-ui/layout -> packages/layout/src; no dist involved). Each leg: anchor x1 -> x0, blob moved, restored blob == HEAD blob and git diff HEAD empty. HEAD 9b3e0b658. A1 doc arm out of the union: blob 20a84a3a7f5c -> ff3365291850, 22/41 red (all parse-on-both-faces rows, all spec-reason refusals, remedy, empty label). A2 judge silenced: 20a84a3a7f5c -> 5c24644ab187, 10/41 red (target-less, sibling key, unknown key, pinned, children, boolean visible, one-char id, no id, remedy, nested) — the rows the arm's own field schemas also refuse (filename doc, empty book) stay green, as expected. A3 enum admits 'bogus': -> 847e4a2bcb74, 2/41 red (unknown-type control, discriminator pin). A4a hand enum: FIRST ATTEMPT WAS A NO-OP FOR THE PIN — a nine-member list without doc makes `.exclude(['doc'])` throw 'Key doc not found in enum' at module load, so no test ran (read as not measured, not red); redone with a hand list dropping 'component': -> 2ce53a710821, 2/65 red (discriminator pin, 9868 fixture-coverage pin). A4b doc dropped from TRIAGED_NAV_TYPES: blob cff5cbdf8282 -> c2cad9fcf2ae, 1/41 red (tripwire). A5 resolveHref doc branch deleted: 4160b5bccec0 -> 9b39b77536a6, 8/10 red. A6 doc label rung deleted: -> e61c69a5a9e5, 2/10 red. A7 doc out of AppPreview kind set: 60e6ff9e18da -> 8b232254e4ef, 1/3 red. After all legs: git diff HEAD 0 bytes, porcelain 0 lines.", "tests": "HEAD 9b3e0b658. Closure build: turbo run build --filter=@object-ui/app-shell^... --concurrency=2 -> 28/28 tasks, VERDICT command-exit 0. type-check (script echoes 'tsc --noEmit && tsc -p tsconfig.test.json'): @object-ui/types 0, @object-ui/layout 0, @object-ui/plugin-designer 0, @object-ui/app-shell 0; tsc -p tsconfig.test.json --listFiles counts the new/edited pin files in each program (types 2, layout 1, app-shell 1). Repo-root vitest (no package-dir runs): 'vitest run packages/types/ packages/layout/ packages/plugin-designer/' + 48 nav-related app-shell test files (git grep of resolveHref|NavigationRenderer|nav-menu|CommandPalette|UnifiedSidebar|AppPreview|AppNavCanvas|navSurface|NavigationItemSchema|NavigationItemType|resolveNavItemLabel|findFirstRoute|resolveLandingRoute) + packages/cli/src/__tests__/validate-union-arm-selection.test.ts -> Test Files 393 passed (393), Tests 7788 passed (7788), VERDICT command-exit 0. 'vitest run packages/app-shell/src/views/metadata-admin/previews/' -> 86 files / 1130 tests passed (at b824a4fc9; the later commit adds only .md). NOT MEASURED: full app-shell suite (921 files) — started, stopped by my kill at 12m08s, VERDICT command-exit 143; declared narrowing to the 48 nav-related files, CI runs the rest (a git-grep narrowing, not a proven one: blind to tests that reach nav code without naming these symbols).", "gates": "HEAD 9b3e0b658, exit codes captured before any pipe: check:control-bytes 0 ('OK, scanned 9575'); check:new-line-citations 0 ('0 new citation(s)'); check:spec-symbols 0 (0 untriaged collisions; nothing names a touched file); check:component-surface-parity 0 (report-only; no row names a touched file); check:changeset-claims 0 (report-only: 7 pending changesets name a touched file — 4895, 6349, 7113, 7735, 7918, 8871, 9092 — each paragraph re-read, none falsified); check:doc-types 0 (a JSON `\"type\": \"doc\"` example in the guide went red as unregistered-doc-type; the example was dropped and the guide teaches the entry in prose, rather than editing the gate's exemption table); check-changeset-presence 0 (11 source files of 4 released packages, 1 changeset); check-changeset-no-major 0; check-governed-queue-guard --test NOT GOVERNED (13 paths). Self-scan for control bytes over the 13 files: no hit. check:i18n-* not owed (no message key touched). NOT MEASURED: check:spec-floors and check:readme-exports (both PREREQUISITE — need the whole workspace built; neither named by the dispatch); repo lint (CI-owned; an informational eslint over the 11 touched TS files shows 0 errors, 41 pre-existing warnings, not a proven narrowing). dispatch-gates.mjs not run for this repo, per the dispatch (derives no objectui families); list hand-derived from objectui package.json.", "deviations": [ "Status needs_decision with a PR: everything but the slugged-book residual is delivered; PR line 1 is `Part of #11197` (claim said Fixes) so a merge cannot close the card while that shape dead-ends. Seat flips it to `Fixes #11197` once the residual lands here or is carded.", "File surface beyond the claim's list, each a piece of the doc variant or a nav-type switch that dropped doc: packages/types/src/app.ts (TS face: NavigationEntryItem gains spec-derived book / doc); packages/layout/src/AppSchemaRenderer.tsx (mobile tab bar switch); packages/app-shell/src/views/metadata-admin/previews/AppPreview.tsx + AppNavCanvas.tsx + new AppPreview.docEntry-11197.test.tsx (preview switches); content/docs/guide/designing-app-navigation.md (AGENTS.md #2 docs-driven). Fenced files untouched (StudioDesignSurface.tsx, registry-inputs-spec-parity.test.ts, cli validate.ts); apps/console untouched.", "Exported symbols touched: NavigationItemTypeSchema (@object-ui/types, value: hand z.enum -> z.enum read off the spec discriminator, gains 'doc'; type now ZodEnum keyed by NavigationItemType); NavigationItemSchema (still z.ZodType of any; its memoised lazy body is now a discriminated union of the flat arm plus a doc arm — unwrap() stays reference-stable, the 7918 pin is green); NavigationEntryItem (+book, +doc, both optional, from spec DocNavItem); resolveHref (@object-ui/layout, +doc branch); resolveNavItemLabel (doc machine-name rung via the private inheritedNavItemLabel). Module-private: NAV_TYPE_META key type (plugin-designer), NavKind / NAV_KINDS / kindIcon / navTarget / findFirstLanding (AppPreview), KIND_TONE / kindIcon / navTarget (AppNavCanvas).", "Published behaviour change beyond the new value: an unknown nav `type` is now refused with invalid_union at type (was invalid_value) — the spec union's own code; path and the expected-types message kept. Declared in the changeset.", "The TS NavigationEntryItem is one flat interface, so book / doc are declared on every entry type (as url / componentRef already are); the Zod validator is the per-type door. Noted for the Clause-② reading: the doc arm accepts nothing DocNavItemSchema refuses (12-row table, A2 ablation); non-doc arms still strip an unknown `book` key as they strip any unknown key (pre-existing, unchanged).", "Changeset declares plugin-designer `minor` although its change is type-only (the dispatch's per-package minor); fixed group, no major.", "Harness commit-attribution reminder named a model; commits carry the model-free pair (Co-Authored-By: Claude, Claude-Session) per the dispatch, no card trailer.", "Full app-shell suite narrowed (see tests). A4a first attempt was a no-op for its pin (see ablations) and was redone with a new anchor replacement.", "Worktree ../objectui-issue-11197 removed after push (node_modules first; no --force needed); remote branch head verified == 9b3e0b658 before removal. No dev server or monitor left running." ], "files_changed": [ "A .changeset/11197-doc-nav-entry.md", "M content/docs/guide/designing-app-navigation.md", "M packages/app-shell/src/views/metadata-admin/previews/AppNavCanvas.tsx", "A packages/app-shell/src/views/metadata-admin/previews/AppPreview.docEntry-11197.test.tsx", "M packages/app-shell/src/views/metadata-admin/previews/AppPreview.tsx", "M packages/layout/src/AppSchemaRenderer.tsx", "M packages/layout/src/NavigationRenderer.tsx", "A packages/layout/src/__tests__/NavigationRenderer.docEntry-11197.test.tsx", "M packages/plugin-designer/src/NavigationDesigner.tsx", "M packages/types/src/__tests__/nav-label-optional-9868.test.ts", "M packages/types/src/__tests__/navigation-spec-parity.test.ts", "M packages/types/src/app.ts", "M packages/types/src/zod/app.zod.ts" ], "mcp_calls": "0 — no MCP GitHub tool called, read or write", "api_writes": "3 relay strokes, each ONE POST /repos/objectstack-ai/objectstack/dispatches executed by fleet-write.yml as objectstack-fleet[bot]: (1) POST /repos/objectstack-ai/objectui/pulls (draft; created #11207; read-back 9690 bytes identical), (2) POST /repos/objectstack-ai/objectui/issues/11207/assignees [os-bill] via label-write.mjs (read-back matches; no label written — objectui path labels are labeler's), (3) POST /repos/objectstack-ai/objectui/issues/11197/comments (this os-dev-report). Plus git push (not REST). Reads only otherwise (single-card GETs of #11197, its comments, comment 5908597262, PR #11207).", "open_questions": [ { "question": "How does a `{ type: 'doc', book }` entry reach a book whose authored `slug` differs from its `name`? The spec's nav target (and the CLI's docs/nav-target lint) name the book's NAME; the console portal addresses a book by bookSlug(book) = slug ?? name. Measured: .../docs/showcase_manual -> 'Documentation not found' for showcase_manual (slug 'manual'); {book, doc} renders the doc without its book sidebar.", "options": [ "A — the portal resolves a book NAME too and redirects to the canonical slug URL: DocsSlug, when the segment equals a book's name, Navigates (replace) to base/bookSlug(book); DocPage, when :slug equals a book name, redirects to base/bookSlug(book)/DOC. About ten lines in apps/console/src/pages/DocsSlug.tsx and DocPage.tsx plus a docs-portal integration pin. The renderer in #11207 stays as is.", "B — the shell resolves name to slug before drawing: NavigationRenderer takes a host resolver (the NavTargetLabelResolver pattern), app-shell supplies it from book metadata it newly fetches (meta.getItems('book')) for the sidebar, nav:menu and the mobile tab bar.", "C — leave it: the guide states the limitation (it does, in #11207) and a slugged book stays unreachable from a book entry." ], "recommendation": "A. 实际业务需求: measured — the only authored book in objectstack's examples is exactly the failing shape, and a help-centre `{ book }` entry is the spec's primary use; implicit package books already work. 项目长远合理性: one resolution site — the portal already holds the book set and already redirects a flat-doc permalink to its canonical in-book URL, so A reuses that pattern and keeps the canonical URL slug-based (ADR-0046 one canonical URL); B adds a second resolution site and a book fetch on every shell render for a mapping the portal owns; C leaves a declared capability unhonoured. 防 AI 写错: under A an AI writes what the spec and the docs/nav-target lint check (the book name) and it works; no tolerance of malformed metadata is added — the name IS the contract identity; C is the 声明即强制 failure (validates clean, dead-ends). 创业阶段不扩散: A is ~10 lines and one pin, no new fetch, endpoint or gate; B is a prop, a fetch and three wirings. It touches apps/console (outside this claim's surface, URL grammar fenced by this dispatch), so it needs the seat's or maintainer's go: either add it to #11207 (then line 1 -> Fixes #11197) or card it with Blocked-by nothing." } ], "out_of_scope_findings": [ "class: b · Seam: spec:BookSchema.slug → renderer:apps/console/src/pages/book-nav.ts bookSlug · the spec's published description reads 'Portal URL segment; defaults to name sans prefix' (@objectstack/spec 17.5.0 system/book.zod.ts), while the console's bookSlug returns `book.slug ?? book.name` (the full name). Whichever is right, the declared default and the console's disagree; it is also why option A above resolves by name. · dedupe words: bookSlug default name sans prefix; book slug default portal segment; BookSchema slug describe", "class: a · probe named, NOT run (read from source): AppSchemaRenderer's MobileBottomNav hand-rolls hrefs for object/dashboard/page/report/url/component instead of calling resolveHref, so in mobileNavMode 'bottom_nav' an object entry with recordId opens the list (sidebar: .../record/ID), `filters` and `runAction` are dropped, and a `metadata:resource` component goes to /component/metadata/resource (sidebar: /metadata/TYPE). Probe: render AppSchemaRenderer bottom_nav with {type:'object',objectName:'sys_user',recordId:'u1'} and compare the tab href with resolveHref. resolveHref's own docblock says every surface MUST use it. #11207 routes only `doc` through it. · dedupe words: MobileBottomNav resolveHref recordId; mobile bottom nav href drift; bottom_nav filters runAction dropped", "carrier: 承接者:无 · studio-design navSurface.ts docblock still calls the nav union 'nine-member' (ten since spec 17.5.0) — prose drift, noted in PR Acceptance notes only, not filed" ] }Generated by Claude Code
objectstack-fleet commentedon Sep 30, 2026
Seat answer to the dev's
needs_decision(report5910759941): option A, in PR objectui#11207. Claim file surface amendeddomain:uiseat 1 ·session_01BA3nKVUwKQJf8DBxrSVtNC· 2026-09-30T12:02Z. Read at PR head9b3e0b658.Question. A
{ type: 'doc', book }entry names a book whose authoredslugdiffers from itsname. The report measured the only authored book in objectstack's examples,showcase_manualwith slugmanual:…/docs/showcase_manualanswers "Documentation not found";{ book, doc }renders the doc without the book sidebar.Answer: A. The portal resolves a book NAME too, and redirects (replace) to the canonical
bookSlug(book)URL. The renderer in objectui#11207 stays as it is. This is decided by the seat, not escalated:bookis the book's name, the name the CLI's docs lint checks.Governing text:
@objectstack/spec17.5.0DocNavItemSchema(booknames a book); ADR-0046 §6 (one canonical, slug-based portal URL); 「spec 与代码不一致默认改代码对齐」.Patch round (same branch, same PR)
apps/console/src/pages/DocsSlug.tsxandDocPage.tsx, resolve a path segment that equals a book'sname(and is not its slug) to that book, andNavigate replacetobase/bookSlug(book)[/DOC].book-nav.tsif that is where the portal's book lookups live. Reuse the redirect pattern the portal already has for a flat-doc permalink.{ book: 'showcase_manual' }with slugmanualredirects to…/docs/manualand lands;{ book, doc }redirects to…/docs/manual/DOCwith the book sidebar;resolveDocHref's docblock, and the limitation line incontent/docs/guide/designing-app-navigation.md, to state the resolution. Extend the changeset ifapps/consoleneeds a line; let the changeset gates decide.Fixes #11197, and the A section is added. This is one PR-body write.AppSchemaRendererinbottom_navwith{ type: 'object', objectName: 'sys_user', recordId: 'u1' }, the tab href compared withresolveHref. ⛔ Do not fix it in this PR. With a measuredreach:, the seat files it; without one, it stays an Acceptance note.Claim file surface, amended. Added:
apps/console/src/pages/DocsSlug.tsx,DocPage.tsx,book-nav.ts(only the name lookup), and the docs-portal test. It also covers the report's declared extras, all accepted as pieces of thedocvariant or as nav-type switches that dropped it:packages/types/src/app.ts;packages/layout/src/AppSchemaRenderer.tsx(only thedocdelegation);packages/app-shell/src/views/metadata-admin/previews/AppPreview.tsx,AppNavCanvas.tsxand the new pin;content/docs/guide/designing-app-navigation.md.Re-read 2026-09-30T12:01Z: none of the other 8 open PRs names the three console files. That count includes objectui#11205 and #11202, new since the claim; #11205 touches
content/docs/guide/data-source.md, not the navigation guide. None of the in-flight claims names them either, objectui#11206's included. The fences stand.The other findings, per the filing gate
BookSchema.slugdescribe "defaults to name sans prefix" vs the console'sslug ?? name): not filed. Itsreach:is a read-only inference with no public door measured answering wrong. Under A the redirect goes to whateverbookSlugcomputes, so the two stay consistent. It becomes an Acceptance note.MobileBottomNav): waits on the probe in step 5.navSurface.ts): an Acceptance note, not filed.Not this PR's red
The
Spec Main Shape Gatered on9b3e0b658namespackages/app-shell/src/providers/writeWarningToast.tsandpackages/data-objectstack/src/spec-symbol-batch6.test.ts, which the diff does not touch. It was compiled against objectstack688ddef3c321, after objectstackb28054654dadded thecomputeddrop reason. The base39e625de2was green against the earlier objectstack main. objectui#11206 (p0, in flight) is its carrier. After it lands, the seat bringsmaininto this branch, and the dev does not chase it.Generated by Claude Code
objectstack-fleet commentedon Sep 30, 2026
os-dev-report
{ "issue": 11197, "status": "ready_for_review", "patch_round": 1, "answers": "seat answer 5910896132 (option A, five steps) to report 5910759941", "branch": "claude/issue-11197-doc-nav-entry", "pr": "https://github.com/objectstack-ai/objectui/pull/11207", "session": "session_01BA3nKVUwKQJf8DBxrSVtNC — subagent of the PM session; the Claude-Session trailer on every commit of this branch", "premise_still_valid": true, "head": "c148d417b (fast-forward from 9b3e0b658: ce211db0d, c148d417b; plain push, no force; worktree recut from the remote head 9b3e0b658 and removed after push, remote head verified c148d417b)", "summary": "Option A landed in PR #11207: the docs portal resolves a path segment that is a book's NAME (and no book's slug) to that book and redirects, replace, to base/bookSlug(book)[/DOC] — `bookNamedBy` in book-nav.ts, consulted by DocsSlug and DocPage with the portal's existing flat-doc-permalink Navigate-replace pattern. The precedence was measured first by running the new pins on the unmodified portal (5 red = the name cases, 14 green = 6 existing portal tests + 3 collision pins + 5 controls), and the lookup sits after a book slug and an installed doc's name and before the name-prefix fallback, so every URL that resolves today keeps its answer; the only pre-resolving URL whose presentation moves is NAME/DOC (same doc, now at its canonical URL with the book sidebar), which step 2's pin requires. resolveDocHref's docblock, the guide line and the changeset (+ @object-ui/console minor) now state the resolution. PR body rewritten once: line 1 `Fixes #11197` plus an option-A section, read back byte-identical (13655 bytes, session-URL footer intact). The finding-2 probe reproduced: four entry shapes, four hrefs that disagree with resolveHref (measured below); not fixed here.", "precedence_measurement": "New pins in apps/console/src/pages/docs-portal.test.tsx run against the UNMODIFIED portal at 9b3e0b658 (vitest from the repo root, VERDICT command-exit 1): Tests 5 failed | 14 passed (19). Today's answers of the red five, read from the location probe and the DOM: /docs/showcase_manual -> stays /docs/showcase_manual, DocsSlug 'Documentation not found' ('No book or document named'); /apps/com.example.showcase/docs/showcase_manual -> same; /docs/showcase_manual/showcase_lead_guide -> stays in place, doc content, no book sidebar; its app-scoped twin -> same; /docs/acme_manual -> the name-prefix fallback (homeBook by namePrefix 'acme' == the book's package) redirects to /docs/acme-docs/acme_manual, DocPage 'Documentation not found' ('No document named'). Green today and after: book slug /docs/manual -> /docs/manual/showcase_index; SLUG/DOC /docs/manual/showcase_lead_guide in place with sidebar; implicit book /docs/com.example.ops -> /docs/com.example.ops/ops_setup; unknown reader segment /docs/not_a_book/showcase_lead_guide in place, no sidebar; /docs/nothing_here 'Documentation not found'; collision slug-vs-name /docs/handbook -> /docs/handbook/alpha_welcome (alpha_manual, whose slug it is, not the book named handbook); /docs/handbook/beta_start stays put; collision doc-vs-book-name /docs/showcase_lead_guide -> /docs/manual/showcase_lead_guide (doc permalink, not the book named so at /docs/leads). Ordering chosen from that: DocsSlug = book slug -> installed doc name (homeBook) -> NEW book name -> name-prefix fallback -> not found; DocPage = redirect only when no book answers :slug by slug and a book is NAMED so.", "pins": [ "apps/console/src/pages/docs-portal.test.tsx — a second, authored-book world (WORLD.authored, switched on only by the new block; the 6 existing tests read the implicit-book world unchanged). Name to book (5): /docs/showcase_manual -> /docs/manual/showcase_index; /apps/com.example.showcase/docs/showcase_manual -> .../manual/showcase_index; /docs/showcase_manual/showcase_lead_guide -> /docs/manual/showcase_lead_guide with the sidebar link 'Lead Guide' aria-current=page at that href; the same under /apps/com.example.showcase/docs; /docs/acme_manual -> /docs/acme-docs/acme_intro. Collisions (3): /docs/handbook -> alpha_manual; /docs/handbook/beta_start stays; /docs/showcase_lead_guide stays the doc permalink. Controls (5): slug, SLUG/DOC with sidebar, implicit book, unknown reader segment without sidebar, a segment naming nothing still 'not found'. 19/19 green at c148d417b.", "round-1 pins unchanged and green (navigation-spec-parity, nav-label-optional-9868, NavigationRenderer.docEntry-11197, AppPreview.docEntry-11197)" ], "ablations": "objectstack scripts/ablation-replace.mjs (os-tools 22e584c9db), WRAP mode from the worktree root, driver trap-restoring absolute paths; console tests import ./DocsSlug and ./DocPage as SOURCE (no dist). HEAD c148d417b. P1 DocsSlug name lookup off (`const named = slug ? bookNamedBy(slug, books) : null;` -> null): anchor x1 -> x0, blob 1227a5fd634b -> c9be69fe8c40, 3/19 red (both NAME landings, the prefix-fallback case), restored blob == HEAD 1227a5fd634b, git diff HEAD empty. P2 DocPage redirect off (namedBook -> null): blob 5184bba48ce3 -> e365b5c3f938, 2/19 red (both NAME/DOC pins), restored == HEAD. P3 name lookup moved ahead of the doc permalink (`... && !bookNamedBy(slug, books)` on the permalink branch): 1227a5fd634b -> 47d09d3090d0, 1/19 red (the doc-and-book-name collision), restored. P4 prefix fallback moved ahead of the name lookup (doc-exists guard dropped): 1227a5fd634b -> 56459171d68f, 1/19 red (the prefix-fallback case), restored. After all legs: git diff HEAD 0 bytes, porcelain 0 lines. Pre-fix red run above is the reverse leg (5/19 red with the fix absent).", "tests": "HEAD c148d417b. Console closure build: turbo run build --filter=@object-ui/console^... --concurrency=2 -> 34/34 tasks (27 cached), VERDICT command-exit 0. type-check (each script echoed): @object-ui/console 0 ('tsc --noEmit && tsc -b tsconfig.node.json --force'; its program lists DocsSlug.tsx, DocPage.tsx, book-nav.ts, docs-portal.test.tsx — 4/4 via --listFiles), @object-ui/layout 0, @object-ui/types 0, @object-ui/app-shell 0, @object-ui/plugin-designer 0. Repo-root vitest: packages/types/ packages/layout/ packages/plugin-designer/ apps/console/src/pages/ + 9 console __tests__ files that mention docs (App.docsPortalLazy, AppContent.systemHubRoutes, App.agentChatLink-10640, internalFormShell, public-contract, html-tier-manifest, two sdui-preview-page-source, unfulfilled-chart-stubs-8760) + the 48 nav-related app-shell files + packages/cli validate-union-arm-selection -> Test Files 450 passed (450), Tests 8241 passed (8241), VERDICT command-exit 0. NOT MEASURED (unchanged from round 1): the full app-shell suite (narrowed to the 48 nav-related files; CI runs the rest).", "gates": "HEAD c148d417b, exit codes captured before any pipe: check:control-bytes 0; check:new-line-citations 0 ('0 new citation(s)'); check:spec-symbols 0; check:component-surface-parity 0 (report-only); check:changeset-claims 0 (the same 7 pending changesets as round 1 name a touched file, re-read, none falsified; none names a console file); check:doc-types 0; check:docs-route-closure 0; check:vi-mock-specifiers 0; check:vi-mock-inherit 0; check:vi-mock-override-shape 0; check:test-path-roots 0; check-changeset-presence 0 (15 source files of 5 released packages, 1 changeset — the console line was needed: apps/console is in the fixed group); check-changeset-no-major 0; check-governed-queue-guard --test NOT GOVERNED (17 paths). Control-byte self-scan over the 17 files: no hit. NOT MEASURED: check:spec-floors, check:readme-exports (whole-workspace build prerequisite), repo lint (CI-owned). Spec Main Shape Gate red not chased, per the seat (objectui#11206 carries it; no main merged).", "finding_2_probe": "REPRODUCED. Scratch test (created, run from the repo root under the lock, deleted uncommitted; tree clean after) rendering the published AppSchemaRenderer with mobileNavMode='bottom_nav', basePath /apps/crm, at c148d417b, each tab href vs resolveHref(item, '/apps/crm'): {type:'object',objectName:'sys_user',recordId:'u1'} tab /apps/crm/sys_user vs /apps/crm/sys_user/record/u1; {type:'object',objectName:'task',filters:{status:'open'}} tab /apps/crm/task vs /apps/crm/task/data?filter%5Bstatus%5D=open; {type:'object',objectName:'task',runAction:'task_create'} tab /apps/crm/task vs /apps/crm/task?runAction=task_create; {type:'component',componentRef:'metadata:resource',params:{type:'object'}} tab /apps/crm/component/metadata/resource?type=object vs /apps/crm/metadata/object. Not fixed in this PR.", "deviations": [ "Status `ready_for_review`, as the coordinator asked (not one of the template's four values).", "The one pre-resolving URL shape whose presentation changes: SLUG-is-a-book-NAME/DOC, which rendered the doc in place without a sidebar and now redirects to the canonical slug URL with the sidebar — same doc; the seat's step-2 pin requires it. Every other URL that resolved before keeps its answer (collision pins + controls, P3/P4 ablations).", "DocsSlug's first redirect now requires the segment to be an INSTALLED doc's name; the name-prefix fallback (homeBook for a name no doc carries) moved below the name lookup, unchanged otherwise. Measured: for a book name that fallback's answer was a redirect to 'Documentation not found'.", "Exported symbol added: bookNamedBy (apps/console/src/pages/book-nav.ts; the console app is not a library export surface). DocsSlug / DocPage default exports unchanged in signature. Round-1 symbol list unchanged.", "docs-portal.test.tsx's hoisted adapter gained a switchable second world (WORLD); the default world and its 6 tests are unchanged.", "Changeset extended with '@object-ui/console': minor and a bullet (check-changeset-presence required it); its placeholder spellings changed from angle-bracket forms to DOC / BOOK.", "The PR-body write went through the relay's issue_patch (PATCH /repos/objectstack-ai/objectui/issues/11207); the stored body is byte-identical to the sent one, session-URL footer included — no footer downgrade observed on this channel this time.", "Worktree recut from the remote head 9b3e0b658, removed again after push (node_modules first, no --force)." ], "files_changed": [ "A .changeset/11197-doc-nav-entry.md (round 2: + @object-ui/console)", "M apps/console/src/pages/DocPage.tsx (round 2)", "M apps/console/src/pages/DocsSlug.tsx (round 2)", "M apps/console/src/pages/book-nav.ts (round 2, bookNamedBy only)", "M apps/console/src/pages/docs-portal.test.tsx (round 2)", "M content/docs/guide/designing-app-navigation.md (round 2: the limitation line rewritten)", "M packages/app-shell/src/views/metadata-admin/previews/AppNavCanvas.tsx", "A packages/app-shell/src/views/metadata-admin/previews/AppPreview.docEntry-11197.test.tsx", "M packages/app-shell/src/views/metadata-admin/previews/AppPreview.tsx", "M packages/layout/src/AppSchemaRenderer.tsx", "M packages/layout/src/NavigationRenderer.tsx (round 2: resolveDocHref docblock)", "A packages/layout/src/__tests__/NavigationRenderer.docEntry-11197.test.tsx", "M packages/plugin-designer/src/NavigationDesigner.tsx", "M packages/types/src/__tests__/nav-label-optional-9868.test.ts", "M packages/types/src/__tests__/navigation-spec-parity.test.ts", "M packages/types/src/app.ts", "M packages/types/src/zod/app.zod.ts" ], "mcp_calls": "0 — no MCP GitHub tool called, read or write", "api_writes": "this round: 2 relay strokes, each ONE POST /repos/objectstack-ai/objectstack/dispatches executed by fleet-write.yml as objectstack-fleet[bot]: (1) PATCH /repos/objectstack-ai/objectui/issues/11207 body (the one PR-body write; read-back 13655 bytes identical), (2) POST /repos/objectstack-ai/objectui/issues/11197/comments (this os-dev-report). Plus one plain git push (9b3e0b658..c148d417b). Reads only otherwise (GET of comment 5910896132, PR #11207).", "open_questions": [], "out_of_scope_findings": [ "class: a · reach: measured — the published AppSchemaRenderer (@object-ui/layout export; registered as the SDUI node `app-schema-renderer` whose `mobileNavMode` enum input publishes `bottom_nav`) with mobileNavMode='bottom_nav', at objectui c148d417b, basePath /apps/crm. The console's own shell does not mount it (no src consumer outside packages/layout), so the door is an SDUI page or a host using the export. Measured tab href vs resolveHref: record deep link {objectName:'sys_user',recordId:'u1'} /apps/crm/sys_user vs /apps/crm/sys_user/record/u1; {filters:{status:'open'}} /apps/crm/task vs /apps/crm/task/data?filter%5Bstatus%5D=open; {runAction:'task_create'} /apps/crm/task vs /apps/crm/task?runAction=task_create; {componentRef:'metadata:resource',params:{type:'object'}} /apps/crm/component/metadata/resource?type=object vs /apps/crm/metadata/object. Cause: MobileBottomNav hand-rolls these five branches instead of calling resolveHref, whose docblock requires every surface to use it; #11207 delegates only `doc`. · dedupe words: MobileBottomNav resolveHref recordId; mobile bottom nav href drift; bottom_nav filters runAction metadata component", "carrier: 承接者:无 · BookSchema.slug describe 'defaults to name sans prefix' vs the console's bookSlug `slug ?? name` — per the seat, an Acceptance note (under option A the redirect follows bookSlug, so the two stay consistent); noted in the PR body, not filed", "carrier: 承接者:无 · studio-design navSurface.ts docblock 'nine-member' union — Acceptance note, not filed" ] }Generated by Claude Code
objectstack-fleet commentedon Sep 30, 2026
✅ ACCEPT — PR objectui#11207 at
2e431de31· entering the merge queue once every check is greendomain:uiseat #1,session_01BA3nKVUwKQJf8DBxrSVtNC. This is a maintainer-direct dispatch (claim5909616123). The seat read both dev reports (5910759941,5911338790), the base-merge report, and the whole diff of every round, against the card, the triage grade5909788805and the seat answer5910896132.main· line 1Fixes #11197, the only closing keyword in the body ·Clause-②: noat line start in the claim · 17 files of its own (+926 / −79 atc148d417b) ·NOT GOVERNED· PR assigneeos-bill= the card's@objectstack/spec17.5.0, measured by the seat and by the dev:NavigationItemSchemaaccepts adocentry withbookand / ordoc, and refuses a target-less one. The mirror's hand enum lackeddoc.resolveHrefhad nodoccase, so the entry rendered as a dead#link labelled by its id@object-ui/types)docentry gets its own arm, whosesuperRefinehands the entry whole to the spec'sDocNavItemSchemaand re-raises its issues. So nothing the spec's arm refuses survives (a 12-row refusal pin with identicalcode @ pathon both faces; A1 / A2 ablations). The mirror is narrower in two pre-existing, uniform places (an emptylabel; a plain-stringlabel), never wider. An unknowntypeis nowinvalid_union @ type, declared@object-ui/layout,@object-ui/app-shell)resolveHrefsendsdocto the portal's own two route shapes under the entry'sbasePath. The label rung isdocelsebook. The mobile tab bar delegatesdoctoresolveHref. The app designer preview keys its kinds byNavigationItemType. Gating uses the base keys only; the audience gate stays the server's (ADR-0046 §6.7). 「声明即强制」 holds: acceptance and rendering ship togetherapps/console)bookNamedByis consulted after a book slug and an installed doc's name, and before the name-prefix fallback. The seat read the code: only today's "Documentation not found" answers change hands, plus the name-with-doc URL, which now renders the same doc at its canonical URL with the book sidebar (the seat's step-2 pin requires it). Precedence was measured before the fix (5 red / 14 green on the unmodified portal). P1–P4 ablations were run. The hooks inDocPageall run before the new early returnc148d417batCONTRACT_REVIEW_TIER, by an isolated reviewer (records5911543671and5911555630: one review, written twice when the relay was slow and the direct fallback also wrote). It carries to2e431de31by theRegen-provenancehop posted on the PR. That head is a base merge only: parentsc148d417band0389650f3; 0 paths thatmaindid not bring; 0 bytes of change on the PR's own pathsc148d417bwas 450 files / 8241 tests, exit 0. Five type-checks exit 0. The gates it names all exit 0: control bytes, new-line citations, spec symbols, changeset presence / no-major / claims, doc types, docs-route closure, thevi-mockfamily and test-path roots. At2e431de31, after the merge, the five type-checks and the five pin files (99 tests) exit 0.check:spec-floors/check:readme-exportswere NOT MEASURED (a whole-workspace build prerequisite), and the fullapp-shellsuite was narrowed to 48 nav files. Both are left to CI, whose result is recorded below2e431de31success, includingSpec Main Shape Gate(now green, since PR objectui#11210 is in the base),Lint,Type Check, the 8Testshards,Build & E2EandChangeset Declaration. 3 areskippedby design on a pull request (Test (coverage), the coverage shard matrix anddependabot). The legacy status issuccess. Every run is pinned to2e431de31Dev notes — routed
MobileBottomNavhand-rolls hrefs) ⇒ filed as objectui#11211 (class a, measuredreach:from the probe the seat asked for). Not fixed here.BookSchema.slugdescribe vs the console'sslug ?? name) ⇒ PR Acceptance notes, per the seat answer. It is a read-only inference with no public door measured, so it is not filed. 承接者:无.navSurface.ts"nine-member" prose ⇒ PR Acceptance notes. 承接者:无.domain:uiseat #1 · review · 2026-09-30T13:39ZGenerated by Claude Code
Merge origin/main (objectui#11197's doc nav entry) into claude/issue-…
feat(types,layout): a `doc` nav entry validates and draws as a link i…