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)
1.7 KiB
Browser security boundary
The browser bundle is public. Secrets, token lifecycle, raw HTML injection, dynamic code execution, untrusted script URLs, and public production source maps are prohibited defaults.
config/hosting/security-headers.json is the declared header set. Hosting
verification compares that declaration with live responses. CSP deliberately
omits unsafe-inline and unsafe-eval; production code and built assets must
remain compatible with that baseline. tests/e2e/production-csp.spec.ts (part of
test:e2e, FE-GATE-008) serves the build with these headers and fails on a
securitypolicyviolation event or console error (review 13-08). zod probes
Function("") on its first object schema, which the policy would report on
every boot. src/contracts/zod.ts sets jitless to skip that probe, and every
module that builds a schema imports z from there, so the setting is applied
before the first schema whatever order the bundler evaluates chunks in.
z.config in the entry module would be too late. Import z from
src/contracts/zod.ts, not from zod, in new schema code. Features that are off by
default need CSP additions when a project selects them; see step 9 in
optional adapter recipes.
connect-src 'self' https: lets script reach any HTTPS origin. Narrowing it to
the runtime config's API_BASE_URL and TELEMETRY_ENDPOINT origins needs a
header generated per environment at deploy time, because those values are set
per deployment (scripts/generate-runtime-config.ts). That generator does not
exist yet; a project that deploys should add it with its provider adapter.
Route guards are UX hints and client validation does not replace backend authorization or validation.