refactor: 프론트 템플릿 리펙토링

README.md

@@ -47,21 +47,28 @@ authoritative.
 
 ## Architecture
 
+This repository is a **Frontend Application Foundation**: a starter/composition
+skeleton plus a reusable capability platform. Platform capabilities stay
+horizontal while product business features use vertical slices.
+
 Dependencies point inward:
 
 ```text
 presentation -> application -> domain
 adapters -----^
 bootstrap composes concrete adapters
-contracts own cross-cutting registries
+feature use case -> feature port <- feature-owned capability binding
 ```
 
-See `docs/architecture/overview.md`, `docs/architecture/layers.md`, and
+See
+`docs/architecture/frontend-application-foundation.md`,
+`docs/architecture/overview.md`, `docs/architecture/layers.md`, and
 `docs/architecture/starter-experience.md`. The removable vertical slice is
 under `src/features/reference-feature`; its domain, application input, HTTP
-adapter, contracts, route runtime, and presentation are installed through the
-feature contribution files in `src/features`. The generic starter routes
-continue to typecheck, test, and build after that contribution is removed.
+binding, contracts, route runtime, and presentation own their contributions.
+The central installed catalogs only aggregate selected contributions. The
+generic starter routes continue to typecheck, test, and build after that
+feature is removed.
 
 ### Platform capability review
 
@@ -103,6 +110,7 @@ corepack pnpm check:types:node
 corepack pnpm check:types:test
 corepack pnpm check:architecture
 corepack pnpm test:all
+corepack pnpm test:contract
 corepack pnpm test:e2e
 corepack pnpm test:a11y
 corepack pnpm build
@@ -115,6 +123,11 @@ corepack pnpm drill:runbooks
 corepack pnpm check:ci
 ```
 
+`test:all` is the ordinary product-development loop and intentionally excludes
+host-level CI-runner assurance. Run `corepack pnpm test:system` only on the
+compatible Linux assurance host described in
+[`docs/testing/taxonomy.md`](docs/testing/taxonomy.md).
+
 `check:types`는 source, Node scripts/config와 tests를 분리된 TypeScript
 project로 모두 검사한다. type/architecture/security/registry의 invalid
 fixture는 `config/ci/gates.json`에서 “실패해야 통과”하는 negative gate로
@@ -153,7 +166,7 @@ Live release verification additionally requires `HOSTING_BASE_URL`.
 
 ## CI and evidence
 
-The 26-gate registry is `config/ci/gates.json`; the Gitea workflow is
+The 27-gate registry is `config/ci/gates.json`; the Gitea workflow is
 `.gitea/workflows/quality-gates.yml`. It follows:
 
 ```text