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)
71 lines
2.7 KiB
TypeScript
71 lines
2.7 KiB
TypeScript
import { readFileSync } from "node:fs";
|
|
|
|
import { expect, test, type Page } from "../support/browser/strict-browser-test.ts";
|
|
|
|
// 13-08. The Content-Security-Policy in config/hosting/security-headers.json was
|
|
// declared but never applied in a browser: `vite preview` sends no security
|
|
// headers. This smoke serves the build with the production headers attached
|
|
// and fails on any securitypolicyviolation event or console error.
|
|
const { headers: declaredHeaders } = JSON.parse(
|
|
readFileSync("config/hosting/security-headers.json", "utf8"),
|
|
) as { headers: Record<string, string> };
|
|
// The preview server is plain HTTP on loopback. `upgrade-insecure-requests` is a
|
|
// no-op for an HTTPS origin, but WebKit applies it to loopback and rewrites
|
|
// every same-origin request to https, which this server cannot answer. Every
|
|
// other directive is served exactly as declared.
|
|
const securityHeaders = {
|
|
...declaredHeaders,
|
|
"Content-Security-Policy": declaredHeaders["Content-Security-Policy"]!
|
|
.split(";")
|
|
.map((directive) => directive.trim())
|
|
.filter((directive) => directive !== "upgrade-insecure-requests")
|
|
.join("; "),
|
|
};
|
|
|
|
// F-7. No zod setup here: the app sets `jitless` in src/contracts/zod.ts before
|
|
// any schema is built, so zod's `Function("")` probe never reaches the policy.
|
|
test.beforeEach(async ({ page, baseURL }) => {
|
|
const origin = new URL(baseURL ?? "http://127.0.0.1:4173").origin;
|
|
await page.route(
|
|
(url) => url.origin === origin,
|
|
async (route) => {
|
|
const response = await route.fetch();
|
|
await route.fulfill({
|
|
response,
|
|
headers: { ...response.headers(), ...securityHeaders },
|
|
});
|
|
},
|
|
);
|
|
await page.addInitScript(() => {
|
|
const violations: string[] = [];
|
|
Object.defineProperty(window, "__cspViolations", { value: violations });
|
|
document.addEventListener("securitypolicyviolation", (event) => {
|
|
violations.push(`${event.effectiveDirective} ${event.blockedURI}`);
|
|
});
|
|
});
|
|
});
|
|
|
|
async function cspViolations(page: Page): Promise<string[]> {
|
|
return page.evaluate(() => (window as unknown as { __cspViolations: string[] }).__cspViolations);
|
|
}
|
|
|
|
test("boots and changes route under the production security headers", async ({ page }) => {
|
|
const response = await page.goto("/");
|
|
expect(response?.headers()["content-security-policy"]).toBe(
|
|
securityHeaders["Content-Security-Policy"],
|
|
);
|
|
await expect(page.getByRole("heading", { level: 1 })).toHaveText(
|
|
"Clean Architecture Frontend",
|
|
);
|
|
|
|
await page
|
|
.getByRole("navigation", { name: "주요 탐색" })
|
|
.getByRole("link", { name: "화면 상태" })
|
|
.click();
|
|
await expect(
|
|
page.getByRole("heading", { level: 1, name: "화면 상태" }),
|
|
).toBeFocused();
|
|
|
|
expect(await cspViolations(page)).toEqual([]);
|
|
});
|