docs(features): 기능 실행부 설명 네 곳을 V2 삭제 뒤 모양으로 고친다 (1103/09-10)

문제
FeatureRuntime은 featureId·schemas·adapters·contractContributions인데, 네 곳이
지워진 V2 모양을 적었다. feature-module.ts 머리 주석("API contracts with their
runtime schemas and mappers"), installed-feature-contracts.ts("The V2 API
registries"), frontend-application-foundation.md("composes the V2 API
registries"), starter-experience.md 기능 추가 2단계("the API contract
(operations, schema metadata, runtime schemas, mappers)"). 기능 작성자가 없는
칸을 찾게 된다. 07-05(starter-experience 같은 문장)를 함께 닫는다.

고른 방법
네 문장을 지금 모양으로 고친다: schemas는 FE-REG-SCHEMA 행, 어댑터 기여는
application input, 계약 기여는 HTTP operation이고 FE-REG-API 행은 거기서
투영한다(installed-feature-runtime-registries.ts와 같다).

위험·한계
verify:documentation은 문장 내용을 보지 않으므로 다시 낡아도 게이트가 모른다.

검증
- git grep "V2 API registr|runtime schemas, mappers|runtime schemas and
  mappers" -- src docs/architecture → 0건.
- verify:documentation PASS_SCOPED.

Refs: docs/reviews/2026-11-03-maturity-review/09-app-core.md 09-10
Refs: docs/reviews/2026-11-03-maturity-review/07-contracts.md 07-05
This commit is contained in:
DongHyeonka
2026-11-04 20:19:59 +09:00
parent 9edc8307b0
commit bf9df9a5c2
4 changed files with 13 additions and 9 deletions
@@ -118,8 +118,9 @@ Central installed catalogs are aggregation points only:
- `installed-contract-contributions.ts`: declared contract packages and the
registry the HTTP executor resolves against, filled as features load
- `installed-feature-runtime-registries.ts`: loads every runtime half and
composes the V2 API registries and contract contributions; the platform
overview route calls it before it renders, the boot never does
composes the contract contributions, the FE-REG-API rows projected from
them and the FE-REG-SCHEMA registry; the platform overview route calls it
before it renders, the boot never does
- `loaded-feature-runtimes.ts`: the same registries as module constants (top-
level await) for Node scripts, tests and registry governance; nothing under
`src` may import it (`boot-does-not-load-every-feature-runtime`)
+4 -3
View File
@@ -133,10 +133,11 @@ selected app. Every build and check script runs it first; run it yourself with
`loadRuntime`, which imports `feature-runtime.ts` dynamically.
`src/features/reference-feature/feature-module.ts` is the complete example.
2. Create `src/features/<feature>/feature-runtime.ts` with
`defineFeatureRuntime`: the API contract (operations, schema metadata,
runtime schemas, mappers), the adapter contributions
`defineFeatureRuntime`: the `schemas` (FE-REG-SCHEMA rows for the
feature's route and API schemas), the adapter contributions
(`defineFeatureAdapterContribution`, with `needs` naming the platform
capabilities it receives) and the contract contributions. The router loads
capabilities it receives) and the contract contributions (the HTTP
operations). The router loads
it (`application.features.load`) when one of the feature's routes is
entered. Do not import it statically from anywhere: each feature would add
its whole executable code to the initial chunk again, about 3.9 KB gzip
+3 -2
View File
@@ -9,8 +9,9 @@ type EmptyRecord = Readonly<Record<never, never>>;
* contract packages the release manifest is checked against at boot. It is
* imported statically and lands in the initial chunk, so it stays data.
*
* Everything executable (API contracts with their runtime schemas and mappers,
* the application input factory, the HTTP contract contributions) is the
* Everything executable (the FE-REG-SCHEMA schema definitions, the adapter
* contributions that build the application input, and the HTTP contract
* contributions whose descriptors FE-REG-API rows are projected from) is the
* runtime half (`FeatureRuntime`). `loadRuntime` imports it dynamically when
* one of the feature's routes is entered. Before 15-01 both halves loaded at
* boot and each feature added about 3.9 KB gzip to the initial chunk.
+3 -2
View File
@@ -9,8 +9,9 @@ import { INSTALLED_PRODUCT_FEATURES } from "./installed-product-manifest.ts";
/**
* 15-01. Boot-time registries composed from the features' declarations: the
* route table, route runtime contracts, cache invalidation and navigation.
* The V2 API registries need the executable half of every feature and live in
* `loaded-feature-runtimes.ts`, which the app boot never imports.
* FE-REG-API and FE-REG-SCHEMA come from the executable half of every feature
* (rows projected from the contract contributions, and the runtime `schemas`)
* and live in `loaded-feature-runtimes.ts`, which the app boot never imports.
*/
export const INSTALLED_FEATURE_CONTRACTS = INSTALLED_PRODUCT_FEATURES;