The gate count and the reference-feature LOC table were hand-typed and
drifted from the code, so they are removed; the LOC table now names the
files and the command that measures them. .env.example pointed to
layers.md for runtime profiles, which never described them; it now points
to the README section that does. ci-quality-gates.md lists the three
things DOCUMENTATION_READY checks, so the gate name is not read as a
general documentation-accuracy guarantee. The route list (③) and the
README config location (④) were already fixed by 14-03 and 13-15.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The budget is a size ratchet set about 100 bytes above the measured
reference bundle. Measured after merging lanes B, D, F, G, H and J:
realtime 39903 -> 40886 gzip bytes (04-01..04-08 add reconnect rules and
SSE handling; 06-01, 06-02, 06-06, 06-09 add web-push fences and click
handling, and src/adapters/web-push is a realtime recipe source root).
Same rounding rule: 40900.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
One run decided the release gate, the interaction included Playwright round
trips, and a server already on 4173 was measured instead of the build. Runs
now repeat with every sample kept, time the interaction in the page, use
--strictPort and check the served build, and stop the whole preview group.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Save failures outside sign-in, permission and retry still went into
ErrorSummary under "review the entered information". They now reach
FormFailureStatus with their own copy and action; the unused copy is gone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Old-tab chunk recovery in the default configuration only had jsdom tests, and
the old-asset test checked its own hosting fixture. A spec now serves two real
builds: the old tab reloads once into the new one and not a second time. The
fixture test and the acceptance row now say what they cover.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The scale evidence came from stub features, so the cost of one app growing
towards its declared ceiling was never measured. Copies of the reference
feature at 25 and 100 are now the baseline, and the acceptance matrix says
what the ceilings rest on and which axes stay unverified.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
AsyncSurface drew auth-required, forbidden and not-found query failures with
its own copy while the gallery used AccessSurface. Both now use one set, and
a state surface without a handler shows no dead button.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
zod probed Function("") on its first object schema, which the production CSP
(no unsafe-eval) reported on every boot. Schema code now imports z from
src/contracts/zod.ts, enforced by a dependency-cruiser rule, and the CSP smoke
drops its init-script workaround.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The fallback opened `${origin}/`, outside the app under a router base path.
The scope host now passes registration.scope and the click adapter opens it,
refusing any app root outside the origin.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A direct link to /page#target stayed at the top: the target renders with the
lazy page, after the router scrolled up. PageHeader now scrolls to it below
the sticky header, focus never scrolls, and POP no longer scrolls to top.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The documents said rate/provider failures retry only with a server hint and
that either a stable open or a valid signal resets attempts. The code lets
the transport's retryable decide and needs both signals. Also records the
offline budget pause and refreshes line references shifted by 04-07.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The doc still called the registry pulse key, the storageArea check and the
per-scope QueryClient unimplemented and gave the old release.<id> epoch. Only
session/account epoch and the durable ledger remain missing.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Design 14.1 connect and bounded_poll events had no place to come from, and
an exhausted budget looked the same as a terminal failure. Both coordinators
now emit a closed observation vocabulary through a best-effort sink.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
After an account switch without logout the new session could not name the
stored authority, so enable and reconcile stayed STALE_AUTHORITY. The port
gains revokeForeign: it rotates a fence another fence generation holds and
revokes its association, and leaves the caller's own fence alone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Route render, unrecovered chunk and query failure screens now show the id
a user quotes to support, and the render diagnostic records the same id as
correlation_id. The route failure page also offers a reload.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The strategy doc promised clock/random/scheduler helpers that no test used
(the helper's clearTimeout did nothing), listed three scenario IDs the
catalog does not have, and the taxonomy described an older test:all and a
child-process rule tests/unit does not follow. Removes the unused helper.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The policy guarded legacy retry-policy.ts but not the live V3 retry and
contract path rules, and the strategy doc claimed 19 modules at 90% targets.
The doc now states the enforced ratchet. The below-threshold fixture used the
pre-counter summary shape and failed with a TypeError instead of the
'Risk coverage failed:' diagnostic the negative gate expects.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
An ACTIVE worker whose install failed left a trace only in health(), which
nothing reads. The optional host now emits service-worker.start.failed on the
application telemetry port, and the recipe doc lists what else to wire.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
axe ran as soon as `main` showed, which is the app shell's loading surface,
and protected routes were scanned on the sign-in prompt. The specs now wait
for the route's h1, sign in first, and scan the reference list, detail, form
and status states. The state-surfaces baseline was the loading surface.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A bare vitest run collected 26 Playwright specs and the host-bound system
suite. The documented one-file command goes through run-vitest.ts, which
renders the gitignored product index a fresh clone lacks.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A worker that stops the page from booting had no exit: every off switch was
page code. A REMOVE_REGISTRATION release now writes a service-worker.js that
skips waiting and unregisters itself (D-5), checked end to end in the browser.
The runbook and rollback doc now name only paths that exist in code.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The registry validates hiddenPolicy, killSwitchId and fallback, but the
reference runtime reads none of them, and isCurrent is checked only at loop
boundaries. The comments and design 5.4-5.6 now say close() is the caller's.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A type added by a newer backend ended the connection as MALFORMED_EVENT and
left the stream CURRENT. It is now PROTOCOL_MISMATCH/REGISTRY, and any decode
failure after the stream lookup marks that stream UNKNOWN (design 13.1).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The reference feature and home page rendered Korean literals, so en-US
still showed Korean. check:i18n now scans pages and every feature
presentation folder, and its fixture fails unless every fixture is rejected.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Preview and download share one lease registry and download leases stay for a
30 s grace, so running out of slots clears on its own. Only a Blob above the
single-lease ceiling stays LIMIT_EXCEEDED without retry.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Current contracts, target designs and work history shared one tree with no
index. docs/README.md sorts them, names the files gates read, and marks the
history folders; README lists what a copy can delete. SPEC.md and tasks/ stay
in place because this round still uses them (D-16).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tabs share one native subscription and one origin fence. enable, reconcile
and revoke now run under the `web-push-control` Web Lock (D-4), and a
compensation unsubscribes only a subscription its own call created.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The classifier called type, enum and nullable changes "none" and treated new
keys under strict readers as additive; FE-GATE-014 only checked hand-written
fixtures. It now fails closed and compares the committed baseline with the
schema the build emits. The doc lists per-boundary reader rules.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The runtime does not know the session, so File refs, preview leases and
downloads of the previous user outlived a logout. Section 3.5 and the recipe
lifecycle now say to dispose it, via a scope reset participant if needed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
check:test-evidence requires every e2e spec to use the strict fixture, which
fails on the zod eval console error. The smoke now sets zod's global config
jitless before page scripts run and requires zero violations; without that
init script it fails on the known probe.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The consumer-experience probe ran and scanned a fixture copy of local-draft
that had drifted from src. The copy is gone; the probe runs the src store and
scans every local-draft source file, and the measured table now describes it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The template's default screens use 96% of the initial JS budget, and nothing
said so, nor that CSS is excluded, which gzip level applies, or that the lab
interaction is one run including the Playwright round trip.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Promotion needs two offline signing providers and a bwrap/systemd/cgroup v2
runner that this repository never ran end to end, and no document said what a
project without them gets or how to rotate or revoke a provider key.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The module inventory named dependency modules external:<file>, so no artifact
said which package versions reach the public bundle. It now records
npm:<name>@<version> ids and a packages list. supply-chain.md states what the
SBOM, bundle list and provenance prove, and one SBOM scope mismatch (scheduler).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The barrel rule and layers.md said storage/indexeddb and storage/opfs are each
removable on their own. The removal drill deletes the whole browser-file-storage
bundle together; the sub-barrels exist so the Web Storage barrel survives it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The declared CSP was never applied in a browser. A Playwright spec now serves
the build with config/hosting/security-headers.json and fails on any
securitypolicyviolation. It found one: zod's Function('') probe, listed in the
spec as a known violation until zod is configured jitless before first use.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A feature directory without feature-module.ts vanished silently, registry
consumers listed only the sample's directories, and the removal gate only knew
the sample. The generator now fails unless a NOT_INSTALLED marker says so
(D-10), consumer directories are globs over every feature, and the removal
script takes --feature=<id>. starter-experience.md documents the current
ownership declarations and the files a new feature touches.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
FE-GATE-019 ran before the release existed and passed by comparing the declared
headers with a copy of themselves. The fixture result is now UNVERIFIED, the
gate runs in the production stage after deployment, and the live probe
requests the entry script the served index.html names (D-14).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Provider evidence expires two hours after issue, so no repo tool could
re-verify a release before deploying it later or rolling back to it.
verify:promotion --archived keeps every signature, digest and member check and
judges freshness at the recorded promotion time; the FE-RB-005 drill takes the
extracted release with --release-root.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>