문제
FE-GATE-012의 check:app-build-input:bundle은 production 번들에 든
`src/features/<dir>/` 모듈이 모두 앱의 context가 소유한(생성기로 설치한)
기능이어야 한다고 본다. TechLog는 조립부가 직접 붙이는 기능이라
(`src/features/tech-log/NOT_INSTALLED`) 어떤 context도 소유하지 않는다.
그래서 이 검사는 TechLog의 모든 production 번들을 거절한다. 9-29 템플릿
동기화(af3d8e6)로 들어온 뒤, 같은 게이트의 번들 예산 검사가 먼저 실패해
한 번도 이 단계까지 가지 않았다. 예산을 맞추자 드러났다.
고른 방법
- DIRECTLY_COMPOSED_FEATURE_DIRECTORIES(["tech-log"])를 두고, 번들 쪽
검사에서만 이름으로 허용한다.
- 생성 인덱스 쪽 검사는 그대로다. 생성기가 TechLog를 import하면 여전히
실패한다.
버린 대안
- NOT_INSTALLED 표시가 있는 디렉터리를 모두 허용: reference-feature와
local-draft-feature도 NOT_INSTALLED다. 그 샘플이 번들에 새면 이 검사가
잡아야 한다.
위험·한계
- 템플릿 소유 스크립트를 고친다. TechLog를 feature-module.ts로 옮기는
후속 작업(docs/operations/template-sync-2026-09-29.md)을 하면 이 목록을
지운다.
검증
- tests/architecture/app-build-input.test.ts: TechLog 모듈은 받아들이고,
같은 번들의 reference-feature는 거절한다.
- desktop CI env에서 이 커밋 전 head로 돌린 FE-GATE-012: 번들 예산은 PASS
(229,223 / 230,400 B), check:app-build-input:bundle이 "production bundle
contains feature \"tech-log\" not owned by app template-app"으로 실패.
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 at 8210d48.
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 at
8210d48 first 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)