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)
111 lines
4.3 KiB
TypeScript
111 lines
4.3 KiB
TypeScript
import { readFile, writeFile } from "node:fs/promises";
|
|
import path from "node:path";
|
|
import process from "node:process";
|
|
|
|
import {
|
|
DEPLOYMENT_TARGETS,
|
|
isDeploymentTarget,
|
|
PUBLIC_TARGETS,
|
|
type DeploymentTarget,
|
|
} from "../src/contracts/deployment-admission.ts";
|
|
import { runtimeConfigV2ArtifactSchema } from "../src/contracts/release-artifacts.ts";
|
|
|
|
/**
|
|
* §6.4. Materializes `dist/config.json` from the profile the build declares.
|
|
*
|
|
* `public/` is copied verbatim into `dist/`, so before this step the runtime
|
|
* document that shipped with every build was the local one — `APP_ENV: local`,
|
|
* `AUTH_MODE: demo`, a loopback API — regardless of what the build was for.
|
|
* The profile is the source of truth instead, and the only values a deployment
|
|
* may inject are the ones it actually owns: its endpoints and its identity.
|
|
*
|
|
* The result is validated against the same V2 schema the browser will apply, so
|
|
* an override cannot produce a document that only fails at boot.
|
|
*/
|
|
|
|
const PROFILE_DIRECTORY = "config/runtime";
|
|
const OUTPUT_PATH = "dist/config.json";
|
|
|
|
/**
|
|
* Deployment-supplied values. Everything else is fixed by the profile so a
|
|
* deployment cannot quietly widen what was reviewed.
|
|
*/
|
|
export const RUNTIME_OVERRIDES = Object.freeze({
|
|
API_BASE_URL: "RUNTIME_API_BASE_URL",
|
|
TELEMETRY_ENDPOINT: "RUNTIME_TELEMETRY_ENDPOINT",
|
|
} as const);
|
|
|
|
export async function generateRuntimeConfig(
|
|
target: DeploymentTarget,
|
|
environment: NodeJS.ProcessEnv = process.env,
|
|
): Promise<Record<string, unknown>> {
|
|
const profilePath = path.join(PROFILE_DIRECTORY, `${target}.json`);
|
|
const source: unknown = JSON.parse(await readFile(profilePath, "utf8"));
|
|
if (source === null || typeof source !== "object" || Array.isArray(source)) {
|
|
throw new TypeError(`${profilePath}: runtime profile must be an object`);
|
|
}
|
|
const draft: Record<string, unknown> = { ...(source as Record<string, unknown>) };
|
|
if (draft["APP_ENV"] !== target) {
|
|
throw new Error(
|
|
`${profilePath}: declares APP_ENV ${String(draft["APP_ENV"])}, expected ${target}`,
|
|
);
|
|
}
|
|
for (const [field, variable] of Object.entries(RUNTIME_OVERRIDES)) {
|
|
const supplied = environment[variable];
|
|
if (supplied !== undefined && supplied !== "") draft[field] = supplied;
|
|
}
|
|
// 13-07. dist, and the release manifest in it, is served under the router
|
|
// base path; a root-relative profile URL is rebased onto it.
|
|
const basePath = environment["VITE_ROUTER_BASE_PATH"] || "/";
|
|
const manifestUrl = draft["RELEASE_MANIFEST_URL"];
|
|
if (
|
|
typeof manifestUrl === "string" &&
|
|
manifestUrl.startsWith("/") &&
|
|
!manifestUrl.startsWith(basePath)
|
|
) {
|
|
draft["RELEASE_MANIFEST_URL"] = `${basePath}${manifestUrl.slice(1)}`;
|
|
}
|
|
// F-6. A public build without its own identity would ship the local
|
|
// placeholder; fail here instead of at admission.
|
|
if (PUBLIC_TARGETS.has(target) && !environment["VITE_BUILD_ID"]) {
|
|
throw new Error(`${profilePath}: a ${target} build requires VITE_BUILD_ID`);
|
|
}
|
|
const buildId = environment["VITE_BUILD_ID"] || "local-build";
|
|
const releaseId = environment["RELEASE_ID"] ?? "local-release";
|
|
draft["BUILD_ID"] = buildId;
|
|
draft["RELEASE_ID"] = releaseId;
|
|
|
|
const parsed = runtimeConfigV2ArtifactSchema.safeParse(draft);
|
|
if (!parsed.success) {
|
|
const issues = parsed.error.issues
|
|
.map((issue) => `${issue.path.join(".") || "(root)"}: ${issue.message}`)
|
|
.join("\n ");
|
|
throw new Error(`${profilePath}: runtime config is invalid\n ${issues}`);
|
|
}
|
|
return draft;
|
|
}
|
|
|
|
function resolveTarget(environment: NodeJS.ProcessEnv): DeploymentTarget {
|
|
const declared = environment["APP_PROFILE"] ?? "local";
|
|
if (!isDeploymentTarget(declared)) {
|
|
throw new Error(
|
|
`APP_PROFILE must be one of ${DEPLOYMENT_TARGETS.join(", ")}; received ${declared}`,
|
|
);
|
|
}
|
|
return declared;
|
|
}
|
|
|
|
async function main(): Promise<void> {
|
|
const target = resolveTarget(process.env);
|
|
const config = await generateRuntimeConfig(target);
|
|
await writeFile(OUTPUT_PATH, `${JSON.stringify(config, null, 2)}\n`, "utf8");
|
|
process.stdout.write(
|
|
`runtime config: ${target} profile written to ${OUTPUT_PATH} ` +
|
|
`(APP_ENV=${String(config["APP_ENV"])}, AUTH_MODE=${String(config["AUTH_MODE"])})\n`,
|
|
);
|
|
}
|
|
|
|
if (process.argv[1] && import.meta.url.endsWith(path.basename(process.argv[1]))) {
|
|
await main();
|
|
}
|