FE-GATE-021..025 rebuilt from source and drilled that build, so the drilled
bytes were not the promoted release. production_gate now downloads the
promoted-release artifact, extracts it against immutable_build's digest and
runs each drill with --release-root; the CI contract rejects a rebuild.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
check-ci-contract only caught test files outside the gates; check:* scripts
such as check:request-fanout and check:remediation-ledger ran nowhere. The
new check reads config/ci/ungated-scripts.json; three checks are now wired
into FE-GATE-010 and FE-GATE-012 and the rest carry a reason.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The growth test read docs/reviews/, which the removal fixtures do not copy and
README lets a project delete, so three removal checks failed with ENOENT. The
rationale now lives in config/scale/feature-shape-ceilings.json and a guard
test keeps code from reading the deletable history documents.
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. file-transfer 55582 -> 55623 gzip bytes: 01-07 moves
the vault release into one finally around put() and open(). Same
rounding rule: 55700.
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>
The detail path /examples/reference-resources/:resourceId lost to the static
new and status routes, so an item with one of those ids opened the wrong
screen. The breaking route change carries registry evidence.
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>
ENV_REGISTRY called VITE_BUILD_ID required with no default while every reader
fell back to local-build. Staging and production builds now fail without it;
local builds keep the placeholder, and the registry records that default.
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>
The gate only matched one diagnostic string, so widening the telemetry event
name or the diagnostic level still counted as the expected failure. Each
violation now has its own directive and the fixture must compile cleanly.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Nothing read severity, telemetryEvent or redaction, yet FE-REG-ERROR guarded
them as policy. They are removed and the registry baseline is re-approved.
A new test fails if createFailure stops clearing retryable for MAYBE_APPLIED (M1).
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>
The budgets are size ratchets set about 100 bytes above the measured
reference bundle. Measured on 926f448 and after the wave-1 lanes:
file-transfer 54468 -> 55517 gzip bytes (01-01..01-11 add capability
reissue, size-aware timeouts, probe limiting) and offline-indexeddb
35856 -> 36822 (05-01..05-14 add per-transaction locks, purge sweep and
corrupt-row skipping). Same rounding rule: 55600 and 36900.
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>
config/architecture/layers.json was read by nothing and contradicted the
enforced adapter rule. It is deleted; .dependency-cruiser.json is the one rule
source, and the ESLint layer patterns are marked as an editor aid.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
No CI job ran any scale tier, and every tier past pr compares timings only on
the baseline CPU. The pr tier checks counts, bounds and growth shape; it now
includes S2 composition, since S0/S1 stay under the noise floor and let a
quadratic accumulation through. The ungated-test check reads tier paths.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Drills held constant true verdicts and read public/ placeholders, so they
passed with no build or with JS assets deleted. They now check the local dist,
mark boot, live traffic and provider steps UNVERIFIED (exit 3), and FE-GATE-016
is retired because it repeated FE-GATE-025's FE-RB-005 drill.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The signed review is per release candidate, so the merge gate could never pass.
FE-GATE-009 now checks only the record format; the checked-in records are
source-controlled evidence, not command output.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tests/architecture, tests/release, tests/scripts, the top-level
tests/features files and the browser-soak contract now run in
test:coverage (FE-GATE-005); check:adapter-inventory joins FE-GATE-010
and the image resolve-signal type fixture joins FE-GATE-003 (baseline
updated). check:ci fails on a test file no gate command reaches unless
config/ci/ungated-tests.json gives a reason; only the tests/scale suite
is listed, pending 11-03. defineFeatureModule's id mismatch is tested.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Gate/command/artifact counts and the gate-shape SHA-256 were code
constants, so any real removal or addition failed check:ci and removal
fixtures passed only in a relaxed mode. They now live in
config/ci/contract-baseline.json (owner, reason) with
update:ci-contract-baseline; update:registry-baseline wraps the existing
registry script. Removal fixtures re-baseline and run canonical check:ci
and check:registries; CI_CONTRACT_MODE, --reduced-removal-fixture and
check:registries:structure are gone. ci-quality-gates.md lists the
baselines a new project resets.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
verify-hosting-headers.ts passed the serviceWorker probe only when
cache-policy.json said `enabled: false` AND dist had no worker script, so no
configuration let a supported ACTIVE build through the hosting gate. The
probe now follows the static selection: ACTIVE requires exactly the selected
`service-worker.js` at the dist root; null / REMOVE_REGISTRATION /
PURGE_OWNED_RESOURCES still reject any worker script. The now-unused
`serviceWorker.enabled` policy flag is removed; the artifact keeps the same
`serviceWorker`/`enabled` probe key.
RED (ACTIVE build from the previous commit, `node scripts/verify-hosting-headers.ts`):
Hosting cache/content-type/security header verification failed. exit=1
{ surface: serviceWorker, header: enabled, expected: false, observed: true, passed: false }
GREEN: same ACTIVE build -> PASS exit=0 (expected: true, observed: true);
default build -> PASS; default build + stray dist/service-worker.js -> exit=1
(reason "dist worker scripts: service-worker.js");
tests/unit/hosting-probe.test.ts 13 passed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Delete src/features/reference-feature/presentation/reference-feature-runtime.tsx:
it only re-exported the same-named .ts and nothing imported it by the
.tsx path.
- Move promotion-readiness.ts and performance-budgets.ts from
src/application/policies to scripts/lib: only scripts and their unit
tests import them. Imports updated in 5 scripts and 2 tests.
config/testing/risk-coverage.json lists only src modules, so their two
criticalModules/highRiskPaths entries are removed; the synthetic
14-file summary fixture now names two other existing src modules.
- installed-feature-messages.ts composes one catalog per locale the
installed features declare (composeInstalledMessageCatalogs) instead
of a fixed ko-KR/en-US list that silently dropped other catalogs. The
exported type still maps each declared locale to its exact key set.
Verified: tests/unit/installed-feature-messages.test.ts (ko-KR/en-US
content pinned first; derived-locale and duplicate-key cases RED before);
app typecheck also passes with a zero-feature generated index; all gates
PASS; check:ci PASS; check-bundle resolves the moved module (stops later
on the absent artifacts/performance/bundle.json).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>