# Static asset and runtime-config delivery

> **정본 안내 (non-authoritative for runtime capability decisions)**
>
> Runtime Config/boot, Fetch HTTP client, Router, Query/Mutation, realtime 공통 경계, Web Worker,
> Service Worker, offline command와 Background Sync의 구현 결정은
> [프론트엔드 런타임 Capability 저장소 정합형 구현 결정 폐쇄 상세 설계](./2026-07-30-frontend-runtime-capability-repository-aligned-implementation-closed-deep-design.md)가 정본이다.
> 본 문서의 해당 서술이 정본과 충돌하면 정본을 따른다.


This Mermaid view is a repository-local implementation projection. The
`PASS_SCOPED` reviewer evidence applies only to the canonical static-delivery
draw.io scope recorded in `review-ledger.json`.

```mermaid
sequenceDiagram
  participant CI
  participant ImmutableRelease
  participant ActivePointer
  participant Browser
  CI->>ImmutableRelease: upload hashed assets
  CI->>ImmutableRelease: upload release manifest
  CI->>ImmutableRelease: upload runtime config
  CI->>ImmutableRelease: probe asset reachability
  CI->>ActivePointer: atomically switch HTML
  Browser->>ActivePointer: fetch revalidated HTML
  Browser->>ImmutableRelease: fetch no-store config and manifest
  Browser->>ImmutableRelease: fetch immutable hashed assets
  CI->>Browser: boot, route, API, and reload-loop smoke
```

Rollback changes the active pointer only after confirming that the prior
immutable release has a coherent HTML/assets/config/API/manifest tuple.