feat: 기능 추가 과정중

README.md

@@ -6,8 +6,15 @@ operations are executable contracts rather than conventions.
 
 ## Start locally
 
-Requirements: Node 24.11 or newer and Corepack. The repository pins pnpm in
-`package.json`.
+Requirements: the exact Node.js version in `.nvmrc` (currently 24.14.0) and
+Corepack. The repository pins pnpm in `package.json`.
+
+Product source, tests, build/quality scripts, and supported tool configuration
+are TypeScript/TSX. `allowJs` is disabled. Node-side `.ts` scripts run directly
+on the pinned Node 24 runtime and are checked with NodeNext resolution plus
+erasable-syntax enforcement. Project-owned executable source contains no
+JavaScript-family files; negative architecture, security, and type-compatibility
+fixtures are TypeScript/TSX as well.
 
 ```bash
 corepack pnpm install --frozen-lockfile
@@ -29,7 +36,7 @@ persistent `system` / `light` / `dark` theme selector.
 | `/examples/ui` | buttons, fields, cards, alerts, badges, modal, and tokens |
 | `/examples/states` | loading, refresh, empty, error, auth, forbidden, and not-found states |
 | `/examples/auth` | reactive external-auth integration seam |
-| `/sample/resources` | protected, domain-neutral integration route |
+| `/examples/reference-resources` | removable, integration-defined reference feature |
 
 `AUTH_MODE=demo` is credential-free and accepted only in local/development
 environments. Deployments use `AUTH_MODE=external` and provide the opaque auth
@@ -50,10 +57,11 @@ contracts own cross-cutting registries
 ```
 
 See `docs/architecture/overview.md`, `docs/architecture/layers.md`, and
-`docs/architecture/starter-experience.md`. The removable sample slice is under
-`src/sample/contract-fixture`; product code is not allowed to import it. The
-visible starter routes do not depend on that fixture and continue to build
-after it is removed.
+`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.
 
 ### Platform capability review
 
@@ -63,8 +71,17 @@ through one end-to-end application path:
 
 - [platform capability review](docs/architecture/frontend-platform-capability-review.md)
 - [ports, adapters, and feature boundaries](docs/architecture/frontend-ports-adapters-and-boundaries.md)
+- [REST, GraphQL, Connect/gRPC-Web, Schema, Mapper, and Server State](docs/architecture/api-contract-schema-mapper-and-server-state.md)
+- [Protobuf browser transports and REST Gateway](docs/architecture/protobuf-browser-transport-and-rest-gateway.md)
+- [backend API and Server State handoff contract](docs/architecture/backend-api-and-server-state-contract.md)
 - [TypeScript, state ownership, and data flow](docs/architecture/typescript-state-and-data-flow.md)
 - [routing, page templates, and reusable patterns](docs/architecture/routing-pages-and-patterns.md)
+- [browser data capability completion ledger](docs/architecture/browser-data-capability-completion-ledger.md)
+- [browser file and origin-storage platform](docs/architecture/browser-file-and-origin-storage.md)
+- [client cache and storage](docs/architecture/client-cache-and-storage.md)
+- [realtime events, Web Push, and bounded polling](docs/architecture/realtime-events-web-push-and-bounded-polling.md)
+- [presigned transfer, resumable upload, streaming download, and Image CDN](docs/architecture/presigned-transfer-and-image-cdn.md)
+- [server file capability infrastructure](docs/architecture/server-file-capability-infrastructure.md)
 - [design-system platform](docs/styling/design-system-platform.md)
 - [frontend platform testing strategy](docs/testing/frontend-platform-testing-strategy.md)
 - [implementation roadmap](docs/architecture/frontend-platform-implementation-roadmap.md)
@@ -105,6 +122,14 @@ fixture는 `config/ci/gates.json`에서 “실패해야 통과”하는 negative
 [VD-01](docs/architecture/decisions/VD-01-typescript-lint-tooling.md)에 기록돼
 있다.
 
+Application feature input은 module augmentation으로 닫힌 ID와 정확한 input
+shape를 제공하며, 공통 `Result<Value, Failure = AppFailure>`는 error registry의
+failure kind만 application/presentation 경계를 통과시킨다. Architecture gate는
+TypeScript/TSX의 static, dynamic, type import를 별도 정적 그래프로 분석하고
+runtime/source 영역의 JavaScript 재유입도 거절한다. 해석되지 않은 import,
+parse failure, 금지 계층 edge와 순환 의존은 모두 fail-closed이며 전용
+TypeScript/TSX negative fixture로도 검증된다.
+
 Install the pinned Playwright browser engines before the first cross-browser
 run: