Files
clean-architecture-frontend…/docs/architecture/static-delivery.md
T
DongHyeonka 2f2426a670 docs: 샘플과 함께 지워지는 경로를 백틱 없이 적는다
문제
ac52a93이 backend-api-and-server-state-contract.md를 docs/README.md 1절에서
링크해 이 문서도 경로 검사를 받는다. 이 문서는 참조 기능 파일 둘을 백틱
경로로 적는다. static-delivery.md는 config/scale/feature-shape-ceilings.json
(15-02, 샘플 제거 때 함께 지워짐)을 백틱 경로로 적는다. 그래서 참조 기능을
지운 제거 fixture에서 verify:documentation이 "names paths that do not exist"로
실패하고, 그 fixture의 documentation-readiness 테스트 36건이 떨어진다
(FE-GATE-020). 14-04가 정한 규칙(지울 수 있는 샘플 경로는 백틱 없이)을
어겼다.

고른 방법
- 세 경로를 백틱 없이 적고, static-delivery에는 샘플과 함께 지워진다고
  적는다.

검증
- verify:documentation PASS_SCOPED. 제거 fixture 확인은 X4 재실행에서 한다.

Refs: docs/reviews/2026-11-03-maturity-review/14-template-product-docs.md 14-04, 14-03
2026-11-05 00:13:49 +09:00

3.2 KiB

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 저장소 정합형 구현 결정 폐쇄 상세 설계가 정본이다. 본 문서의 해당 서술이 정본과 충돌하면 정본을 따른다.

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.

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

In this repository the workflow deploys nothing. The upload, pointer switch and smoke steps above belong to the project's provider adapter, which fills the deployment job between promotion and production_gate. After it has deployed the promoted release, FE-GATE-019 probes the live headers and checks that the host serves that release; while the slot is empty FE-GATE-019 is UNVERIFIED (reviews 13-05, 1101/13-01, release-cache-rollback.md).

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

Serve the app over HTTP/2 or later. The entry preloads every initial JavaScript file in parallel (initialJsFiles in config/performance/budgets.json bounds how many; the current count is initialJavascript.files in config/scale/feature-shape-ceilings.json, which goes with the sample feature). Over HTTP/1.1 they queue for six connections per host, and the first screen on Fast 3G came about one second later than with the initial chunks grouped (2026-11-03). Over HTTP/2 the difference was under 100 ms, so the template keeps the chunks split. A product that can only serve HTTP/1.1 groups its initial chunks in vite.config.ts and measures again whenever the shell changes ("초기 청크 수와 HTTP/1.1" in performance-evidence.md, review 1101/14.4).

Serve JavaScript compressed (gzip, brotli or zstd). The bundle budget counts gzip bytes; uncompressed, the initial JavaScript is about three times larger. Both premises are declared in config/hosting/cache-policy.json (transport.alpnProtocols, hashedAsset.contentEncodings), and the live probe of FE-GATE-019 fails a host that does not meet them (review 1103/13-02). The nginx example in release-cache-rollback.md turns both on.