chore: sync the frontend template from ebea300 to af3d8e6
Carries 359 template commits, tag v0.2.0 plus one documentation commit: the generator-built feature index with its app, bounded-context and feature declarations, the src/platform kernel and scale tooling, the 2026-09-24 src review fixes, and the 2026-09-25 maturity review round with its CHANGELOG [보안]/[계약] rows. 691 of the 824 template paths are applied, 85 of them merged with product changes; 127 are not carried. Product identity is unchanged: name, version 0.1.0, routes, design and the TechLog domain. Three decisions worth naming. TechLog stays composed directly, as the last two syncs recorded; its directory carries a NOT_INSTALLED marker that says so, and every installed-* composer takes the template's projection with TechLog added on top. The reference sample is no longer installed: the template now installs a feature only through feature-module.ts and context-routes.ts, which load the screens this product deleted, so its three operations, six schemas and one topic leave the registries, recorded as registry change evidence. And AppRouter mounts the platform and TechLog routes only; the template's bounded-context route gateway waits for a generator-installed feature. Required fixes: readSubject on the BFF session owner (without it every HTTP Studio session would close as integration-failed), zod through the facade in nine TechLog files, noUnusedLocals, and public/config.json written out to match the local profile. Derived baselines were recomputed after reproducing both sides' values: CI contract 101 commands / 106 references / 141 artifacts, gate shape c9adcf85; registry approval 2dc6c3a3; the runtime config schema baseline equals the schema at8210d48. Verified here: types, lint, architecture, adapter inventory, CI contract, i18n, design system, diagnostics, browser security, dev release manifest, TechLog contract and build pass; 220 component, 155 integration, 15 contract, 418 TechLog, 43 reference-feature, 18 recipe and 46 release-coherence tests pass, and 2381 of 2383 unit tests. Reproduced at8210d48first and unchanged: check:registries (byte-identical), test:runtime-schema, verify:documentation. Brought by the template and escalated rather than suppressed: check:request-fanout on TechLog's cursor pagination, check:remediation-ledger (fails upstream too), the shared-chunk hash test, and the registry-dependent sample removal and second-feature tests. Playwright suites were not run. Full record, the five open questions and the follow-ups in docs/operations/template-sync-2026-09-29.md. (cherry picked from commit b2170cf265dea45dc9cc05d3c61e627e97f31cdb)
This commit is contained in:
@@ -142,8 +142,12 @@ rasterization과 실제 device farm은 프로젝트가 요구할 때 연결한
|
||||
|
||||
operation별 success/empty/slow/network/timeout/content/envelope/schema/auth/
|
||||
403/404/409/422/429/retry/terminal을 포함한 19개 scenario catalog와 strict
|
||||
unhandled-request server를 공유한다. clock/random/scheduler/storage helper와
|
||||
browser console/page/network failure 정책으로 비결정적 우회를 차단한다.
|
||||
unhandled-request server(`tests/mocks/server.ts`의
|
||||
`onUnhandledRequest: "error"`)를 공유한다. browser test는 공용 fixture
|
||||
(`tests/support/browser/strict-browser-test.ts`)가 console error/warning,
|
||||
page error, 실패한 request를 test 실패로 만든다. 시간은 각 test가
|
||||
`vi.useFakeTimers()`로 통제하고, 전역 `afterEach`가 실제 timer로 되돌린다
|
||||
(`tests/setup.ts`). 공용 clock/random/scheduler helper는 두지 않는다.
|
||||
|
||||
#### Built-dist와 compact E2E
|
||||
|
||||
@@ -153,11 +157,25 @@ Chromium, Firefox, WebKit과 compact project로 실행한다. 빠른 Vite 개발
|
||||
|
||||
#### 위험 기반 coverage
|
||||
|
||||
V8 text/JSON/LCOV를 생성하고 전체 기준과 retry/storage/telemetry/application
|
||||
composition/compatibility/performance/promotion/chunk/diagnostics/reference HTTP
|
||||
operation/query-mutation/registry compatibility 19개 high-risk module에 80개
|
||||
scoped threshold를 적용한다. critical module 누락 또는 threshold 미달 fixture는
|
||||
merge gate를 실패시킨다.
|
||||
V8 text/JSON/LCOV를 생성하고 `config/testing/risk-coverage.json`의 하한을
|
||||
적용한다. 하한은 전체 평균 4개(`summary`: lines 75, statements 73, functions 80,
|
||||
branches 68)와 `criticalModules` 20개의 모듈별 하한 80개(모듈마다 4개)다.
|
||||
`check-risk-coverage.ts`는 두 종류를 합쳐 "84 thresholds"로 보고한다. 모듈은
|
||||
HTTP 실행(`http-execution-v3.ts`, live 재시도 규칙 `http-retry-lifecycle.ts`,
|
||||
계약 경로 규칙 `http-contract-bridge.ts`, legacy V2 `retry-policy.ts`, 요청 조립,
|
||||
bounded body/JSON), server-state scope, Service Worker lifecycle, 저장소
|
||||
(`browser-storage-adapter.ts`, `indexeddb-runtime.ts`), telemetry, application
|
||||
조립, compatibility, chunk recovery, release manifest, boot JSON, diagnostics,
|
||||
reference HTTP gateway, application query다. 모듈별 하한은 목표치가 아니라
|
||||
등록할 때 측정값 근처로 둔 ratchet이다(되돌아가지 못하게 막는 하한). 새로
|
||||
넣은 세 모듈은 2026-09-26 측정값을 내림한 값이다.
|
||||
critical module 누락 또는 threshold 미달 fixture는 merge gate를 실패시킨다.
|
||||
|
||||
realtime(`src/adapters/realtime/`)과 Web Push(`src/adapters/web-push/`)는
|
||||
`test:realtime-removal`이 통째로 지우는 선택 runtime이라
|
||||
(`scripts/test-realtime-runtime-removal.ts`의 `runtimePaths`) 모듈별 하한에 넣지
|
||||
않는다. 넣으면 그 runtime을 지운 다운스트림의 coverage gate가 없는 파일 때문에
|
||||
실패한다. 두 영역은 전체 평균 하한만 받는다.
|
||||
|
||||
Repository inventory의 정적 provenance는 runtime 실행 가능 여부가 아니라 현재
|
||||
Vitest/V8 producer가 file counter를 생성하는 문장의 존재 여부를 나타낸다. 따라서
|
||||
@@ -724,15 +742,19 @@ tests/factories/
|
||||
| `malformed-json` | 파싱 불가능한 JSON |
|
||||
| `envelope-mismatch` | top-level contract 위반 |
|
||||
| `schema-mismatch` | data payload contract 위반 |
|
||||
| `auth-recover-once` | 첫 401 후 복구 성공 |
|
||||
| `auth-persistent-401` | 복구 뒤에도 401 |
|
||||
| `response-too-large` | 응답 본문이 크기 상한을 넘어 읽기를 멈춤 |
|
||||
| `unauthenticated-401` | 401. 명령은 적용되지 않음(`NOT_APPLIED`) |
|
||||
| `forbidden-403` | 권한 없음 |
|
||||
| `not-found-404` | 리소스 없음 |
|
||||
| `conflict-409` | mutation conflict |
|
||||
| `validation-422` | 승인된 field/global error |
|
||||
| `rate-limited-429` | Retry-After 포함 |
|
||||
| `server-retry-success` | bounded retry 뒤 성공 |
|
||||
| `server-terminal-500` | retry 소진 |
|
||||
| `server-terminal-503` | 503. 조회는 retry 2회 뒤 소진, 명령은 retry 없이 결과 불명(`MAYBE_APPLIED`) |
|
||||
|
||||
이 표는 `tests/mocks/scenarios/catalog.ts`의 `HTTP_SCENARIO_IDS`와 같은 순서다.
|
||||
401 뒤 인증 복구 흐름은 catalog가 아니라 `tests/integration/auth-recovery.test.ts`가
|
||||
다룬다.
|
||||
|
||||
### 11.3 Catalog 규칙
|
||||
|
||||
@@ -951,6 +973,13 @@ fixture로 확인한다.
|
||||
|
||||
### 14.2 위험별 목표
|
||||
|
||||
아래 표는 올려 갈 **목표**다. 지금 gate가 막는 값은 이 표가 아니라
|
||||
`config/testing/risk-coverage.json`의 현재값 ratchet이다(2.3절 "위험 기반
|
||||
coverage"). 예를 들어 `service-worker-lifecycle.ts`의 branch 하한은 43,
|
||||
`http-execution-v3.ts`는 52로 표의 목표보다 낮다. 테스트를 보강해 측정값이
|
||||
오르면 그 모듈의 하한을 새 측정값으로 올린다. 하한을 내리는 변경은 이유를
|
||||
커밋 메시지에 적는다.
|
||||
|
||||
| 영역 | Line/statement 참고 | Branch 우선 목표 |
|
||||
| --- | --- | --- |
|
||||
| registry/codec/schema | 95~100% | 100%에 가깝게 |
|
||||
@@ -1103,8 +1132,11 @@ validate한다.
|
||||
|
||||
외부 배포 주소나 28일 field evidence가 없는 skeleton 개발 단계에서는 해당 gate가
|
||||
실제 프로젝트가 채울 계약으로 남는다. 이를 fake data로 통과시키지 않는다.
|
||||
현재 `FE-GATE-009`의 signed manual accessibility review는 merge gate다. 이
|
||||
문서는 이를 production/field gate로 이동시키지 않는다.
|
||||
signed manual accessibility review는 release gate `FE-GATE-028`이다
|
||||
(`config/ci/gates.json`, 리뷰 08-06). 사람의 서명은 릴리스 후보 하나에 대해
|
||||
하므로 merge마다 요구할 수 없다. merge gate `FE-GATE-009`는 자동 axe 검사와
|
||||
기록 형식 검사(`review:a11y-manual -- --format-only`,
|
||||
`scripts/lib/manual-a11y-evidence.ts`의 `validateManualA11yRecordFormat`)만 한다.
|
||||
|
||||
### 16.4 병렬화와 shard
|
||||
|
||||
|
||||
@@ -16,9 +16,11 @@ Each gate is blocking in its declared scope. Failures are not downgraded with
|
||||
| end-to-end | `pnpm test:e2e` | pinned browser engines | `artifacts/tests/e2e/` |
|
||||
| accessibility | `pnpm test:a11y` | pinned browser engines | `artifacts/tests/a11y.json` |
|
||||
|
||||
`test:all` is the normal product-development loop. It intentionally includes
|
||||
runtime-schema, unit, capability-contract, component, integration, reference
|
||||
feature and recipe suites, but does not include `test:system`. CI-runner and
|
||||
`test:all` is the normal product-development loop. It runs, in order,
|
||||
`test:runtime-schema`, `test:unit`, `test:contract`, `test:component`,
|
||||
`test:integration`, `test:reference-feature`, `test:platform` (`tests/platform`
|
||||
and `tests/architecture`), `check:release-coherence` and `test:recipes`
|
||||
(`package.json` `test:all`). It does not include `test:system`. CI-runner and
|
||||
supply-chain assurance has different host prerequisites and is invoked
|
||||
explicitly in the assurance path.
|
||||
|
||||
@@ -37,6 +39,24 @@ That runner:
|
||||
`vitest.config.ts` also fixes `NODE_ENV=test` so a direct Vitest invocation
|
||||
cannot accidentally select React's production behavior.
|
||||
|
||||
To run one test file, use the same runner:
|
||||
|
||||
```sh
|
||||
node scripts/run-vitest.ts run tests/component/router.test.tsx
|
||||
```
|
||||
|
||||
The runner renders the gitignored `src/.generated/` product index first
|
||||
(`scripts/run-vitest.ts`), so this works in a fresh clone. A direct
|
||||
`pnpm exec vitest run <file>` skips that step and fails there with
|
||||
`Failed to resolve import "../.generated/product-feature-index.ts"`.
|
||||
`pnpm test:unit -- <file>` does not narrow the run, because the script already
|
||||
passes the whole `tests/unit` directory.
|
||||
|
||||
`vitest.config.ts` collects only `tests/**/*.test.{ts,tsx}`; Playwright
|
||||
`*.spec.ts` files are not Vitest tests. `tests/system/` is collected only when
|
||||
the command names it, as `test:system` does, so a bare `vitest` run does not
|
||||
start the CI-runner suite.
|
||||
|
||||
The system suite additionally runs
|
||||
`scripts/check-system-test-prerequisites.ts` and fails with one prerequisite
|
||||
report when the CI-runner host does not provide its required Linux facilities.
|
||||
@@ -64,11 +84,19 @@ CI / release assurance:
|
||||
|
||||
A host-level process/sandbox test must not be placed in `tests/unit` merely
|
||||
because it uses Vitest. The classification follows the system boundary and
|
||||
prerequisites, not the test framework. Process-heavy tests that spawn child
|
||||
processes but do not require privileged host facilities belong in
|
||||
`tests/integration`; for example the provider guardian transaction protocol
|
||||
lives at `tests/integration/provider-guardian-transaction.test.ts`. Its
|
||||
handshake timeout is a test watchdog, not a production protocol deadline.
|
||||
prerequisites, not the test framework:
|
||||
|
||||
- Tests that need systemd, bubblewrap, cgroup v2 or CI-provider process
|
||||
controls belong in `tests/system`.
|
||||
- Tests of a long-lived child-process protocol belong in `tests/integration`;
|
||||
for example the provider guardian transaction protocol lives at
|
||||
`tests/integration/provider-guardian-transaction.test.ts`. Its handshake
|
||||
timeout is a test watchdog, not a production protocol deadline.
|
||||
- A script's own tests may start that script, Node or Vitest as a short-lived
|
||||
child process to check its command-line contract, and stay in `tests/unit`
|
||||
next to the script's other tests. Such a suite declares its own longer
|
||||
timeout instead of raising the global one; for example
|
||||
`tests/unit/risk-coverage.test.ts` uses `PROCESS_HEAVY_TIMEOUT_MS`.
|
||||
|
||||
End-to-end and automated accessibility scenarios run on the pinned Chromium,
|
||||
Firefox, and WebKit engines. The responsive contract explicitly exercises
|
||||
|
||||
Reference in New Issue
Block a user