fix(codegen-ts): named package separator in the requirement walk, and hermetic strict-switch tests

The qualified address was built with a literal separator where PACKAGE_SEPARATOR exists. The verify end-to-end tests read the ambient META_REQUIRE_IMPLEMENTERS and failed with it exported; each test now starts with it unset and restores it after.

Refs docs/superpowers/plans/2026-10-05-requirements-slice-1-checks-and-test-generators.md and ADR-0057.

Author: dmealing

server/typescript/packages/cli/test/verify-requirements-e2e.test.ts

@@ -10,7 +10,7 @@
 // Each case drives the real command dispatcher, so a regression in the wiring —
 // requirements silently unhooked from the exit-code max, say — fails here.
 
-import { test, expect, describe, spyOn } from "bun:test";
+import { test, expect, describe, spyOn, beforeEach, afterEach } from "bun:test";
 import { mkdtempSync, mkdirSync, writeFileSync } from "node:fs";
 import { tmpdir } from "node:os";
 import { join } from "node:path";
@@ -93,6 +93,19 @@ const L4 = {
 };
 
 describe("meta verify — requirements exit-code contract", () => {
+  // The strict switch is also an environment variable, and these tests assert the DEFAULT
+  // severity. Whatever the shell that runs them has exported must not decide the outcome:
+  // each test starts with the variable unset, and the shell's value is put back after.
+  let ambientRequireImplementers: string | undefined;
+  beforeEach(() => {
+    ambientRequireImplementers = process.env.META_REQUIRE_IMPLEMENTERS;
+    delete process.env.META_REQUIRE_IMPLEMENTERS;
+  });
+  afterEach(() => {
+    if (ambientRequireImplementers === undefined) delete process.env.META_REQUIRE_IMPLEMENTERS;
+    else process.env.META_REQUIRE_IMPLEMENTERS = ambientRequireImplementers;
+  });
+
   test("a clean requirement tree exits 0", async () => {
     const dir = project(req({ ...L4, "@implementedBy": ["Order"] }));
     expect(await run(["verify", "--cwd", dir])).toBe(0);

server/typescript/packages/codegen-ts/src/requirement-walk.ts

@@ -14,6 +14,7 @@
 
 import { createHash } from "node:crypto";
 import {
+  PACKAGE_SEPARATOR,
   TYPE_REQUIREMENT,
   REQUIREMENT_SUBTYPE_FUNCTIONAL,
   REQUIREMENT_LINK_FLOOR_LEVEL,
@@ -292,7 +293,7 @@ export function requirementTestIdentity(
 ): RequirementTestIdentity {
   const { path, status } = w.view;
   const pkg = w.view.package;
-  const address = pkg === "" ? path : `${pkg}::${path}`;
+  const address = pkg === "" ? path : `${pkg}${PACKAGE_SEPARATOR}${path}`;
   // Derived from the loader's status list rather than naming the two skipped statuses:
   // a status that does not claim the capability works right now is skipped by
   // construction, so a status added later cannot be left failing by omission.