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)
79 lines
3.4 KiB
TypeScript
79 lines
3.4 KiB
TypeScript
import { copyFile, mkdir, readdir, readFile, stat, symlink, writeFile } from "node:fs/promises";
|
|
import path from "node:path";
|
|
|
|
/**
|
|
* Links the repository's installed dependencies into a throwaway fixture root.
|
|
*
|
|
* The obvious form — one directory symlink at `<fixture>/node_modules` — is
|
|
* destructive. A fixture runs `pnpm` inside itself, pnpm does not recognise the
|
|
* modules directory it finds there, and its purge follows the symlink and
|
|
* deletes the *repository's* real dependencies mid-run. With `CI=true` that
|
|
* happens without a prompt, so a test suite silently uninstalls the workspace
|
|
* it is running in.
|
|
*
|
|
* `node_modules` is therefore a real directory here, and every entry inside it
|
|
* is an individual symlink. Package resolution is unchanged, but a recursive
|
|
* delete unlinks the fixture's own symlinks instead of walking through one link
|
|
* into the shared tree.
|
|
*
|
|
* Top-level files are pnpm's install state (`.modules.yaml`,
|
|
* `.pnpm-workspace-state-v1.json`, ...). pnpm rewrites them in place when it
|
|
* runs inside the fixture, so they are copied: a link would carry the fixture's
|
|
* path into the repository's own state and make its next pnpm command
|
|
* re-verify the install.
|
|
*
|
|
* The copied workspace state still names the repository as its validated
|
|
* project, so pnpm in the fixture would re-verify and start an install through
|
|
* the linked directories. It is rewritten to name the fixture root instead:
|
|
* the packages are the repository's own, already validated.
|
|
*/
|
|
/**
|
|
* F-4. The environment for every `pnpm` a linked fixture runs. pnpm verifies
|
|
* the install before a script and, when the fixture's copied state disagrees
|
|
* with its own settings (for example `CI=true` against an install made
|
|
* without it), installs. `.pnpm` and `.bin` are links into the repository's
|
|
* node_modules, so that install rewrote the shared `.pnpm/lock.yaml` and bin
|
|
* shims. A fixture started through `pnpm <script>` inherits this setting from
|
|
* pnpm; one started directly (`node scripts/run-vitest.ts run <file>`) did not.
|
|
* The fixture uses the repository's packages as they are; it never installs.
|
|
*/
|
|
export const FIXTURE_PNPM_ENVIRONMENT = Object.freeze({
|
|
pnpm_config_verify_deps_before_run: "false",
|
|
});
|
|
|
|
export async function linkFixtureNodeModules(
|
|
fixtureRoot: string,
|
|
sourceRoot: string = process.cwd(),
|
|
): Promise<void> {
|
|
const source = path.join(sourceRoot, "node_modules");
|
|
const target = path.join(fixtureRoot, "node_modules");
|
|
await mkdir(target, { recursive: true });
|
|
for (const entry of await readdir(source)) {
|
|
const from = path.join(source, entry);
|
|
const to = path.join(target, entry);
|
|
if ((await stat(from)).isDirectory()) await symlink(from, to, "dir");
|
|
else await copyFile(from, to);
|
|
}
|
|
await retargetWorkspaceState(
|
|
path.join(target, ".pnpm-workspace-state-v1.json"),
|
|
fixtureRoot,
|
|
);
|
|
}
|
|
|
|
async function retargetWorkspaceState(
|
|
statePath: string,
|
|
fixtureRoot: string,
|
|
): Promise<void> {
|
|
let state: { projects?: Record<string, unknown>; lastValidatedTimestamp?: number };
|
|
try {
|
|
state = JSON.parse(await readFile(statePath, "utf8"));
|
|
} catch {
|
|
return; // no state file, or not pnpm's JSON: nothing to retarget
|
|
}
|
|
const [project] = Object.values(state.projects ?? {});
|
|
if (project === undefined) return;
|
|
state.projects = { [fixtureRoot]: project };
|
|
state.lastValidatedTimestamp = Date.now();
|
|
await writeFile(statePath, `${JSON.stringify(state, null, 2)}\n`);
|
|
}
|