From 1543ad904e3b53c7b3e9528911e4246c512c4f0c Mon Sep 17 00:00:00 2001 From: Claude Date: Mon, 17 Aug 2026 13:09:09 +0000 Subject: [PATCH] fix(spec): correct stale tags note in doc.json liveness ledger MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit doc.json's `_note` claimed DocSchema declares no `tags` key, so the book-side `include: { tag }` rule could never match. That was true when written, but doc.zod.ts:126 has declared `tags` since 17.0.0 (#4509, ADR-0049) — the enforce half of enforce-or-remove for this key. Correct the note to a current-state statement instead of deleting it: it still carries load-bearing cross-references (the book-side rule, the REST corpus offset) that are worth keeping, now pointed at the props.tags entry for the fix's full history. No behaviour change; no verdict changes. Fixes #9310 --- packages/spec/liveness/doc.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/spec/liveness/doc.json b/packages/spec/liveness/doc.json index 423b9cffa3..e0e471c521 100644 --- a/packages/spec/liveness/doc.json +++ b/packages/spec/liveness/doc.json @@ -1,6 +1,6 @@ { "type": "doc", - "_note": "DocSchema (ADR-0046 flat Markdown package docs). Fully live. The schema header calls docs 'inert data' — true of the KERNEL (it stores `content` unparsed), but every property has a real runtime consumer in the delivery layer: the REST read layer localizes, audience-gates and serves docs (packages/rest/src/rest-server.ts:2944-3022 list, :3384-3390 single item), and the `/meta/book/:name/tree` endpoint resolves book membership from doc headers via the spec's own resolveBookTree (packages/spec/src/system/book.zod.ts:218). objectui's console docs portal is a faithful port of the same resolver (apps/console/src/pages/book-nav.ts @940ba24) rendering the reader UI — a delivery surface for readers, NOT an authoring preview. Seeded 2026-08-01 (#4488). NOTE: DocSchema declares no `tags`, yet the book-side `include: { tag }` rule and the REST corpus (`d.tags`, rest-server.ts:2965) both expect one — the tag rule can currently never match; recorded on book.groups, not silently dropped.", + "_note": "DocSchema (ADR-0046 flat Markdown package docs). Fully live. The schema header calls docs 'inert data' — true of the KERNEL (it stores `content` unparsed), but every property has a real runtime consumer in the delivery layer: the REST read layer localizes, audience-gates and serves docs (packages/rest/src/rest-server.ts:2944-3022 list, :3384-3390 single item), and the `/meta/book/:name/tree` endpoint resolves book membership from doc headers via the spec's own resolveBookTree (packages/spec/src/system/book.zod.ts:218). objectui's console docs portal is a faithful port of the same resolver (apps/console/src/pages/book-nav.ts @940ba24) rendering the reader UI — a delivery surface for readers, NOT an authoring preview. Seeded 2026-08-01 (#4488). NOTE: `tags` was DECLARED in 17.0.0 (#4509, ADR-0049) — the enforce half of enforce-or-remove: the book-side `include: { tag }` rule and the REST corpus (`d.tags`, rest-server.ts:2965) both already expected the key, so declaring it made the previously-inert `{ tag }` include variant live; see the `tags` entry below for the fix's full history.", "props": { "name": { "status": "live",