From 49be1bcc90e1d05bf54fcf410ff4d8f0d5554412 Mon Sep 17 00:00:00 2001 From: Claude Date: Fri, 18 Sep 2026 01:50:24 +0000 Subject: [PATCH] docs(scripts): keep the plain-Node reading, drop its dead objectui citation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The manifest generator's header cited an objectui issue number for the 2026-08-29 "browser-only is expired" measurement. That number resolves to nothing — 404 on both the issue and the PR endpoint, with seven neighbouring objectui numbers answering 200 on the same endpoint and token — so the zero is the number, not the channel. The claim it supported is true and independently reproduced, so the fact stays and only the citation goes: the paragraph now carries the readings themselves (17 published @object-ui/* 17.6.0 packages, sdui-parser bundled, this generator under plain Node, byte-identical to the tracked artefact) and a number-free tombstone in the form the two sibling gate scripts already carry, so the next author neither follows a dead link nor assumes there was never a reference here. Prose only — no behaviour: regenerating with this header produces the tracked sdui.manifest.json byte for byte. Claude-Session: https://claude.ai/code/session_01JbZnqu8bt6YqfJsr9vaFb3 Co-authored-by: Claude --- scripts/gen-sdui-manifest-node.mjs | 28 +++++++++++++++++++++------- 1 file changed, 21 insertions(+), 7 deletions(-) diff --git a/scripts/gen-sdui-manifest-node.mjs b/scripts/gen-sdui-manifest-node.mjs index cef1b73b7fd..ad8f285e5a7 100644 --- a/scripts/gen-sdui-manifest-node.mjs +++ b/scripts/gen-sdui-manifest-node.mjs @@ -24,15 +24,29 @@ * ## Why plain Node is a valid producer (the browser-only claim is expired) * * `packages/spec/CHANGELOG.md` records (twice, byte-identically) that only a - * real browser can enumerate the registry. Measured false on 2026-08-29 - * (objectui#6741) and re-measured on 2026-08-30 against published - * `@object-ui/*` 17.6.0: all 16 modules import under plain Node once `.css` - * imports resolve to an empty module — the ONLY failure without the hook is + * real browser can enumerate the registry. Measured false on 2026-08-29 and + * re-measured on 2026-08-30 against published `@object-ui/*` 17.6.0: all 16 + * modules import under plain Node once `.css` imports resolve to an empty + * module — the ONLY failure without the hook is * `ERR_UNKNOWN_FILE_EXTENSION .css` on plugin-dashboard/plugin-map, a loader * limitation, not a browser API. 57 configs, 0 lazy stubs, ~4.5 s, no - * Playwright, no objectui build. The browser route (`pnpm sdui:manifest`) - * still exists for operators holding an objectui checkout; both routes - * serialize the same registry through the same adapter. + * Playwright, no objectui build. Reproduced independently in review of #18608: + * the 17 published `@object-ui/*` 17.6.0 packages installed from npm, + * `sdui-parser` bundled, this generator run under plain Node — `sha256 + * 49211fee7792` / `git hash-object 78f870e42fe9`, `cmp` byte-identical to the + * tracked artefact. The browser route (`pnpm sdui:manifest`) still exists for + * operators holding an objectui checkout; both routes serialize the same + * registry through the same adapter. + * + * ⛔ Do not put an objectui issue number back on the 2026-08-29 measurement. + * The citation this paragraph used to carry resolves to nothing — 404 for both + * the issue and the PR at that number, while seven neighbouring objectui + * numbers answer 200 as controls, so the zero is that NUMBER, not the endpoint + * and not the token — and the readings above stand without one. #18608 dropped + * the same citation from the two sibling gate scripts (check-generated.ts, + * check-react-blocks-declaration-parity.ts) and left the same number-free + * tombstone there; this header is what both of them now send readers to for + * the readings. * * ## Versioning contract *