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)
81 lines
4.4 KiB
Markdown
81 lines
4.4 KiB
Markdown
# Architecture overview
|
|
|
|
This Mermaid view is a repository-local implementation projection. The
|
|
`PASS_SCOPED` reviewer evidence applies to the canonical draw.io diagram named
|
|
in `review-ledger.json`, not automatically to edits in this file.
|
|
|
|
```mermaid
|
|
flowchart LR
|
|
Bootstrap[bootstrap / composition root] --> Presentation[presentation]
|
|
Bootstrap --> Adapters[adapters]
|
|
Presentation --> Shell[app shell and route surfaces]
|
|
Shell --> Providers[session and theme providers]
|
|
Presentation --> Application[application]
|
|
Adapters --> Application
|
|
Application --> Domain[domain]
|
|
Contracts[contract registries] --> Bootstrap
|
|
Contracts --> Adapters
|
|
Contracts --> Presentation
|
|
```
|
|
|
|
The enforced dependency rule points inward: presentation calls application use
|
|
cases, adapters implement application ports, and only the composition root
|
|
selects concrete adapters. Contract registries are the named source for routes,
|
|
API operations, environment values, storage keys, errors, queries, telemetry,
|
|
and release tokens. Installed feature contributions extend those registries
|
|
without making the generic application or router import a concrete feature
|
|
implementation.
|
|
|
|
In ports-and-adapters terms, `presentation` is the current inbound adapter and
|
|
`adapters` contains the current outbound implementations. The production
|
|
composition exposes an application input API to React while keeping concrete
|
|
output ports inside application closures:
|
|
|
|
```mermaid
|
|
flowchart LR
|
|
Driver[User, route, browser event] --> Inbound[React inbound adapter]
|
|
Inbound --> Input[Application input API]
|
|
Input --> UseCase[Use cases]
|
|
UseCase --> Output[Application output ports]
|
|
Output --> Outbound[HTTP, auth, storage, query, telemetry adapters]
|
|
Bootstrap2[Composition root] -. selects and injects .-> Input
|
|
Bootstrap2 -. selects and injects .-> Outbound
|
|
```
|
|
|
|
The executable route tree is mounted only after runtime configuration and
|
|
release-manifest coherence pass. `ApplicationProvider` receives the composed
|
|
application API; concrete session, storage, telemetry, diagnostics, and release
|
|
ports are not returned to feature pages. TanStack Query is isolated behind the
|
|
presentation query adapter, while its provider remains React infrastructure.
|
|
The module-augmented feature registry gives each installed feature a closed ID
|
|
and exact input type.
|
|
|
|
Route contracts/codecs, the route-input provider, and lazy runtime modules are
|
|
separate modules so feature pages do not import the router that loads them.
|
|
Expected application failures use the shared `Result`/`AppFailure` contract.
|
|
The architecture gate analyzes TS/TSX imports with its own graph (the rules
|
|
live in `.dependency-cruiser.json`; dependency-cruiser itself cannot parse
|
|
TypeScript 7 and does not run), rejects local JavaScript-family specifiers and executable
|
|
JavaScript-family files, and fails on unresolved imports, parse failures,
|
|
forbidden layer edges, or cycles. The remaining project-owned work includes
|
|
selecting and verifying real hosting, identity, telemetry, vulnerability and
|
|
signing providers, plus backend/provider/browser/operations evidence for each
|
|
selected optional capability; the repository does not fabricate that evidence.
|
|
Use the following
|
|
documents for implementation details and project integration work:
|
|
|
|
- [Frontend platform capability review](./frontend-platform-capability-review.md)
|
|
- [Frontend ports, adapters, and boundaries](./frontend-ports-adapters-and-boundaries.md)
|
|
- [API contract, Schema, Mapper, and Server State](./api-contract-schema-mapper-and-server-state.md)
|
|
- [Protobuf browser transports and REST Gateway](./protobuf-browser-transport-and-rest-gateway.md)
|
|
- [Backend API and Server State handoff contract](./backend-api-and-server-state-contract.md)
|
|
- [TypeScript, state, and data flow](./typescript-state-and-data-flow.md)
|
|
- [Routing, pages, and patterns](./routing-pages-and-patterns.md)
|
|
- [Browser data capability completion ledger](./browser-data-capability-completion-ledger.md)
|
|
- [Browser file and origin storage](./browser-file-and-origin-storage.md)
|
|
- [Client cache and storage](./client-cache-and-storage.md)
|
|
- [Realtime events, Web Push, and bounded polling](./realtime-events-web-push-and-bounded-polling.md)
|
|
- [Presigned transfer and Image CDN](./presigned-transfer-and-image-cdn.md)
|
|
- [Server file capability infrastructure](./server-file-capability-infrastructure.md)
|
|
- [Frontend platform implementation roadmap](./frontend-platform-implementation-roadmap.md)
|