# Release, cache, and rollback contract Each deployment is an immutable `releases//` artifact set. The provider adapter must upload assets, release manifest, runtime config, and verify asset reachability before atomically switching the active HTML pointer. The post-switch boot, route, API, telemetry, and reload-loop smoke checks close the deployment. Rollback selects a prior release tuple, confirms its assets and runtime/API compatibility, atomically switches the complete set, performs the provider cache action, and repeats the smoke checks. Rebuilding an old commit, replacing HTML alone, or declaring recovery from cache-purge completion is prohibited. Recovery is established by old/new reachability probes. Before deploying a promoted release later, or rolling back to one, re-verify its promoted bundle (the five files uploaded by the `promotion` job) with the archived mode (review 13-04). Provider evidence expires two hours after issue, so the normal mode refuses any release promoted before that. The archived mode still checks signatures, digests and the exact five members, and judges freshness at the release's recorded promotion time (`promotion-verification.json` `verifiedAt`, which may not lie in the future). New promotion never uses it (`scripts/lib/exact-promotion-bundle.ts`). ```bash VULNERABILITY_PUBLIC_KEY_PATH=... VULNERABILITY_KEY_ID=... \ PROVENANCE_PUBLIC_KEY_PATH=... PROVENANCE_KEY_ID=... \ EXPECTED_PROMOTION_RUN_ID= EXPECTED_PROMOTION_RUN_ATTEMPT= \ EXPECTED_PROMOTION_SOURCE_REVISION= \ EXPECTED_PROMOTION_ARCHIVE_SHA256= \ corepack pnpm verify:promotion -- --root --archived mkdir && tar -xzf /release-candidate.tar.gz -C corepack pnpm drill:runbook -- FE-RB-005 --release-root ``` The expected values come from the release record, not from the bundle. The drill then checks that release's build/config/manifest tuple and its assets, not the local build. It ends `UNVERIFIED` until the provider switch and smoke are recorded, because those happen outside this repository. The provider-independent cache defaults are: - hashed assets: `public, max-age=31536000, immutable` - HTML: `no-cache` - runtime config and release manifest: `no-store` - public source maps: disabled - service worker/offline cache: disabled, unless the static selection in `src/features/installed-runtime-capabilities.ts` is `ACTIVE` or `REMOVE_REGISTRATION`; then `dist` holds exactly the selected `service-worker.js`, served `no-cache` so the browser's update check sees each release's worker HTML, JSON config/manifest, and hashed JavaScript MIME types are also compared to the declared allowlist; a cache-correct response with a mismatched `Content-Type` still fails the hosting gate. `corepack pnpm verify:hosting-headers` compares the declared headers with a deterministic fixture when `HOSTING_BASE_URL` is unset. That only shows the declarations agree with each other, so its result is `UNVERIFIED` (exit 3), not `PASS` (review 13-05, `scripts/lib/hosting-probe.ts` `hostingVerdict`). Only `mode: "live"` can pass. The live target must be its canonical, non-loopback HTTPS root URL. Each required surface must return HTTP 200 without leaving that origin before its cache, content-type, and security headers can count as deployment evidence. The hashed asset it requests is the entry script named by the served `index.html`, so it checks the release that is actually deployed. FE-GATE-019 is therefore a production-stage gate (`production_gate` job, `PROD_PROMOTION_READY`). It runs after `promotion` and after the project has deployed the promoted release. This repository's workflow stops at promotion: uploading the release, switching the active pointer, and the post-switch smoke are the project's provider adapter, chosen with the hosting provider. Keep a retired release's hashed assets reachable while any open tab may still request them. The minimum is the previous release while the next one is active (the rolling window modeled in `tests/release/release-fixture.ts`). Size it to the longest session the product supports; a tab older than that depends on the reload-once recovery (FE-RB-002). ## Service Worker steps (only when the static selection is not `null`) The worker is part of the release tuple: `service-worker.js` comes from the same build as the HTML and assets it caches. 1. **Rollback N+1 โ†’ N.** Switching the tuple serves N's `service-worker.js`. The browser's update check installs it; the worker never calls `skipWaiting()` on install (`src/adapters/service-worker/service-worker-entry.ts`), so it waits until every tab of the scope closes or a page calls `requestActivation()`. The template has no page that calls it. The cache name is the asset-set digest, so if N's cache is still there as the retained previous cache, the install reuses it and never deletes it on failure (`service-worker-static-assets.ts` `installStaticAssets`). Tabs still on N+1 keep worker N+1, so N+1's assets stay reachable for the rolling window above. 2. **Turn the worker off without a rebuild.** Set `CAPABILITY_OVERRIDES.SERVICE_WORKER: "DISABLED"` in the runtime config. The next boot unregisters the owned registration and registers nothing; owned caches stay (`src/contracts/runtime-capabilities.ts` `resolveRuntimeCapabilities`, `service-worker-page-controller.ts` `start()`). This needs a page that boots. 3. **A worker stops the page from booting.** Deploy a release whose static selection is `REMOVE_REGISTRATION`. It ships a self-unregistering `service-worker.js` (`scripts/build-frontend.ts`, `scripts/lib/self-unregistering-service-worker.ts`): the update check installs it over the broken worker, it skips waiting, unregisters on activation and answers no fetch. The next load is uncontrolled (`tests/e2e/service-worker-recovery.spec.ts`). Runbook: `docs/operations/browser-file-storage-recovery.md` ยง8. 4. **Removing the worker** takes three releases: `REMOVE_REGISTRATION` โ†’ `PURGE_OWNED_RESOURCES` (deletes owned caches) โ†’ `null` (`src/contracts/service-worker.ts` `InstalledServiceWorkerSelection`).