Weekly hardening: 6 new v153 references + 3 v147 MDN-shape upgrades

[PaulKinlan]

Weekly depth run (2026-09-13). Channels at run time: stable cut = 154 (2026-09-22, so live stable is 153), beta 155, dev 156.

Coverage — v153 complete (6 new pages)

Page	Outcome
v153/iterator-join	MDN stub — MDN covers Iterator.prototype.join with BCD (Chrome 153)
v153/xml-parsing-in-rust-for-non-xslt-scenarios	Full reference + 3 child routes; parser-selection algorithm, compat differences and libxml2 remainder quoted from Chromium source and the Intent thread
v153/js-self-profiling-markers	Full reference + 2 child routes; OT warn-block; IDL from WICG/js-self-profiling#89 (unmerged status disclosed)
v153/spell-check-custom-dictionary-api	Full reference + 2 child routes; dev-trial warn-block; draft-vs-shipped IDL divergence documented
v153/support-long-animation-frames-api-in-web-workers	Full reference + 2 child routes; dev-trial warn-block; exposure delta + 200 ms/5 ms constants verbatim from Chromium
v153/webtransport-headers-and-responseheaders	Full reference + 2 child routes; dev-trial warn-block; IDL/algorithms verbatim from the editor's draft; 155 ship plan disclosed

MDN-shape upgrades — v147, in place (durable contract preserved)

• v147/update-device-memory-api-limits — Baseline banner, verbatim IDL+ABNF, real BCD per-version compat, showcase embed, 2 child routes; fixed the unlinked mail-archive label and kill-switch framing; added sourced rollout history.
• v147/autofill-event — factual corrections with evidence (event dispatches at Document, before values commit; old field-level example replaced), OT warn-block, verbatim WICG IDL, showcase embed, 2 child routes.
• v147/js-profiling-in-dedicated-workers — Baseline banner, [Exposed] delta from spec commit e603c27, Document Policy section, showcase embed, profiler/ child route; honest note that the dev trial now targets Chrome 154 per the current listing.

Every full reference ships with an implementation-sufficient reference-contract.json, _questions.json critique (non-empty guidanceConsulted), and a conformance suite.

Gates (all green before push)

• deno fmt --check, deno check server.ts
• deno task check-routes — 6 added, 0 regressions
• deno task validate-artifacts — PASS (42 implementation-sufficient contracts)
• deno task test-reference-contract — structural + browser visibility PASS
• deno task check-conformance — 202/202 suites, no weakened assertions, touched pages matrix-validated
• Per-page conformance: 9/9 green (0 fail; blocked = manual-evidenced only)
• Responsive matrix: 9/9 ok/ok (runner scan + screenshots read at 360×740 DPR3 and 1280×800)

Integrator interventions worth review

• The xml-rust page's auto-generated suite initially extracted the wrong identity (the lede's XSLT chromestatus link preceded the page's own) — fixed by relinking the lede reference to the child page and regenerating the (uncommitted) suite; its demo-embed-own-feature assertion was authored pre-commit to pin the canonical CPS route, which lives at v147 (no v153 showcase route exists).
• Showcase iframes are curl-verified (HEAD 200 + real demo HTML) but render blank in this sandbox's headless Chrome (egress resets browser-originated TLS) — same limitation recorded on the accepted v147/css-border-shape precedent; disclosed per page in _questions.json.

Known backlog (not in this PR)

• Coverage gaps: v154 (19 features), v155 (16, one shared with v153), v156 (12) have no pages yet.
• ~120 built pages remain legacy-unassessed in the old shape; this run burned down 3.
• v151/xml-parsing-in-rust-for-non-xslt-scenarios documents the same feature id at its earlier milestone claim; flagged in the new page's critique for a future evidenced review (kept per the durable contract).

🤖 Generated with Claude Code

https://claude.ai/code/session_016CAsC4yLd71ywz6WGAD8VB

---

Generated by Claude Code

[Copilot]

🟡 Changes recommended

Unresolved critical report and route-migration issues, along with correctness findings, block approval.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

This PR adds six v153 references and upgrades three v147 pages to the current reference format.

Changes:

• Adds reference pages, child routes, contracts, critiques, and conformance suites.
• Improves three v147 references with updated examples and compatibility data.
• Updates responsive and conformance report artifacts.

File summaries

File	Reviewed change
v153/xml-parsing-in-rust-for-non-xslt-scenarios/conformance.json	XML parser conformance suite; milestone migration remains unresolved.
v153/xml-parsing-in-rust-for-non-xslt-scenarios/_questions.json	XML parser critique and follow-up metadata.
v153/webtransport-headers-and-responseheaders/reference-contract.json	WebTransport implementation contract.
v153/webtransport-headers-and-responseheaders/conformance.json	WebTransport conformance suite.
v153/webtransport-headers-and-responseheaders/_questions.json	WebTransport critique metadata.
v153/support-long-animation-frames-api-in-web-workers/scriptcount/index.html	scriptCount member reference.
v153/support-long-animation-frames-api-in-web-workers/conformance.json	Worker LoAF conformance suite.
v153/support-long-animation-frames-api-in-web-workers/_questions.json	Worker LoAF critique metadata.
v153/spell-check-custom-dictionary-api/reference-contract.json	Dictionary API implementation contract.
v153/spell-check-custom-dictionary-api/conformance.json	Dictionary API conformance suite.
v153/spell-check-custom-dictionary-api/_questions.json	Dictionary API critique metadata.
v153/js-self-profiling-markers/reference-contract.json	Profiling markers implementation contract.
v153/js-self-profiling-markers/conformance.json	Profiling markers conformance suite.
v153/js-self-profiling-markers/_questions.json	Profiling markers critique metadata.
v153/iterator-join/index.html	MDN reference stub.
v153/iterator-join/conformance.json	Stub conformance metadata.
v153/iterator-join/_questions.json	Stub critique metadata.
v147/update-device-memory-api-limits/reference-contract.json	Device Memory implementation contract.
v147/update-device-memory-api-limits/devicememory/index.html	Device Memory API reference and worker example.
v147/update-device-memory-api-limits/_questions.json	Device Memory critique metadata.
v147/js-profiling-in-dedicated-workers/_questions.json	Worker profiling critique metadata.
v147/autofill-event/_questions.json	Autofill critique metadata.
responsive-support.json	Responsive validation records.
reports/conformance/results.json	Conformance results report; currently page-scoped.
reports/conformance/responsive.json	Responsive report; currently incomplete.
reports/conformance/index.html	Human-readable conformance rollup; currently incomplete.

Review details

Suppressed comments (11)

v147/autofill-event/refill/index.html:140

• This process-wide boolean prevents every later autofill event from calling refill() after the first event succeeds. The one-call restriction is per event object, so a page that receives multiple legitimate autofill events will silently skip all but the first; track event objects instead of using a global flag.

<pre><code>let refillRequested = false;
document.addEventListener("autofill", async (event) =&gt; {
  if (event.refill &amp;&amp; !refillRequested) {
    refillRequested = true;      // second call would reject anyway
    await event.refill();

v147/js-profiling-in-dedicated-workers/index.html:230

• This visible citation label has no direct link to the specification, commit, explainer, or MDN artifact listed in the table. Link each original artifact in this citation (or remove the redundant generic citation) so the sources are directly traceable.

    <span class="citation">Source: documents fetched and verified 2026-09-13.</span>

v147/update-device-memory-api-limits/index.html:185

• This citation still names the BCD data only as “BCD files linked above”. The repository's source-link contract requires each cited source label to link directly; link each of the four BCD files again in this citation instead of relying on nearby links.

    <span class="citation">Source: BCD files linked above (fetched 2026-09-13); <a href="https://chromestatus.com/feature/6330376953921536" target="_blank" rel="noopener">ChromeStatus record</a> vendor views; <a href="https://webstatus.dev/features/device-memory" target="_blank" rel="noopener">webstatus.dev &mdash; device-memory</a>.</span>

v153/js-self-profiling-markers/index.html:245

• This visible citation label has no direct link to the documents whose contents it claims to summarize. Link the PR, published specification, marker explainer, conditional-exposure explainer, and TAG review here (or remove the redundant generic citation) rather than relying only on nearby table links.

    <span class="citation">Source: repository and specification contents fetched 2026-09-13 (PR branch fetched via git; merge state checked against <code>main</code>).</span>

v153/spell-check-custom-dictionary-api/index.html:244

• This visible citation label has no direct link to the documents it describes. Link the WHATWG/Igalia/TAG/design-document artifacts listed in the table here (or remove the redundant generic citation) so each source remains directly traceable.
  v153/support-long-animation-frames-api-in-web-workers/index.html:263
• This visible citation label has no direct link to the W3C, explainer, design-doc, or WPT artifacts named around this section. Replace it with direct links to each cited source (or remove the redundant generic citation) instead of leaving only a fetch-status note.
  v153/webtransport-headers-and-responseheaders/headers/index.html:115
• The documented feature-detection expression has the same unguarded WebTransport.prototype access, so it throws before a fallback can run in browsers without WebTransport. Include a typeof WebTransport !== "undefined" guard.
  v153/webtransport-headers-and-responseheaders/headers/index.html:137
• A bearer token in a request header is still visible to the WebTransport server and may be captured by server or intermediary request-header logging; unlike a URL, the header does not guarantee exclusion from logs or telemetry. Limit this claim to URL leakage and document that logging depends on the server/intermediary configuration.
  v153/webtransport-headers-and-responseheaders/index.html:71
• This feature-detection expression throws a ReferenceError in browsers where WebTransport is not defined, so it is not safe cross-browser detection. Guard the constructor before reading its prototype.
  v153/webtransport-headers-and-responseheaders/index.html:226
• This visible citation label only says that the documents were fetched; it does not link the original WebTransport, Fetch, RFC, or draft artifacts listed immediately above. Link each cited primary artifact in the citation itself (or remove this redundant generic citation) so the provenance remains directly traceable.
  v153/webtransport-headers-and-responseheaders/responseheaders/index.html:105
• This feature-detection guidance also dereferences WebTransport.prototype without first checking whether WebTransport exists, so it throws in unsupported browsers. Use a guarded expression before accessing the prototype.

• Files reviewed: 53/53 changed files
• Comments generated: 10
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.