Merge branch 'main' into feature/techlog-ui-migration

Integrates the frontend template sync (a0fbafb → 5434760) into the TechLog UI
migration. Merged in this direction so every conflict is resolved and proved in
the worktree; main is only fast-forwarded afterwards and never holds a state
that was not verified here.

15 conflicts. The rule throughout: keep the template's mechanism, keep the
product's content, and never invent a third state neither branch would accept.

The template's product manifest and its runtime feature kill switch are adopted.
The route registry is deliberately not composed from contract.routes: the
reference feature still declares screens this product deleted, and reducing over
them would register paths with no component behind them. ROUTE_FEATURE_OWNER is
narrowed to registered routes for the same reason. The first resolution did
compose from contract.routes and was rejected by product-features.test.ts.

Three files pinned counts and a digest describing the gate contract. Neither
side's numbers describe the merged config/ci/gates.json, so they were recomputed
from it rather than chosen: 27 gates, 82 commands, 94 command references, 107
evidence references, 128 artifacts, shape sha256 5063586d.

README.md and docs/accessibility/manual-checklist.md now enumerate this
product's 27 routes, which the template's own verify:documentation requires.

product-feature-switch.test.tsx was rewritten around the invariant that still
applies here — no registered route without a component — rather than deleted
with the screens it used to exercise.

docs/operations/template-merge-2026-08-17.md records every decision, the gate
results, and the three follow-ups this merge deliberately did not decide.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

tests/features/reference-feature/reference-installed-executor.test.ts

@@ -0,0 +1,43 @@
+import { describe, expect, it } from "vitest";
+
+import { createReferenceFeatureInstalledInput } from "../../../src/features/reference-feature/adapters/create-reference-feature-input.ts";
+
+/**
+ * This assertion is about the reference feature, not about HTTP observability:
+ * it names the feature's own route ids. It used to live in
+ * `tests/integration/http-execution-v3-observability.test.ts`, which meant a
+ * platform integration file imported the removable feature's installed input.
+ * Removing the feature then left that file importing a deleted module, and the
+ * removability fixture failed on typecheck, the unit/integration run, coverage
+ * and residue at once — four symptoms of one misplaced test.
+ */
+describe("reference feature installed operation executor", () => {
+  it("preserves the feature route id through the installed operation executor", async () => {
+    const seen: Array<Readonly<Record<string, unknown>>> = [];
+    const installed = createReferenceFeatureInstalledInput({
+      contractOperations: Object.freeze({
+        async execute(
+          _operationId: string,
+          _input: unknown,
+          context?: Readonly<Record<string, unknown>>,
+        ) {
+          seen.push(Object.freeze({ ...(context ?? {}) }));
+          return Object.freeze({
+            kind: "SUCCESS" as const,
+            value: [],
+            metadata: Object.freeze({ status: 200 }),
+            effect: "NOT_APPLICABLE" as const,
+          });
+        },
+      }),
+    });
+
+    await installed.input.listResources({ limit: 20 });
+    await installed.input.getResource("resource-1");
+
+    expect(seen.map((context) => context.routeId)).toEqual([
+      "REFERENCE_RESOURCE_LIST",
+      "REFERENCE_RESOURCE_DETAIL",
+    ]);
+  });
+});

tests/features/reference-feature/reference-runtime-composition.test.ts

@@ -28,6 +28,7 @@ const runtime: Runtime = {
       SERVICE_WORKER: "DEFAULT",
       OFFLINE_COMMANDS: "DEFAULT",
     },
+    FEATURE_OVERRIDES: {},
   },
   configSchema: "V2",
   build: {
@@ -83,6 +84,23 @@ function referenceBoundQueryKey() {
   ).queryKey;
 }
 
+/**
+ * The installed feature inputs are partial by design: a feature the product
+ * manifest did not select supplies none. This suite is about the reference
+ * feature being composed, so it asserts that first and narrows once.
+ */
+function referenceInput<
+  Inputs extends Readonly<Partial<Record<typeof REFERENCE_FEATURE_ID, unknown>>>,
+>(adapters: Readonly<{ featureInputs: Inputs }>) {
+  const input = adapters.featureInputs[REFERENCE_FEATURE_ID];
+  if (!input) {
+    throw new Error(
+      `${REFERENCE_FEATURE_ID} is not installed; the manifest did not select it`,
+    );
+  }
+  return input as NonNullable<Inputs[typeof REFERENCE_FEATURE_ID]>;
+}
+
 describe("reference feature runtime composition", () => {
   it("invalidates a real bound query through the installed production graph", async () => {
     const adapters = await createRuntimeAdapters({ runtime, release, host: {} });
@@ -117,7 +135,7 @@ describe("reference feature runtime composition", () => {
     );
 
     await expect(
-      adapters.featureInputs[REFERENCE_FEATURE_ID].listResources({ limit: 20 }),
+      referenceInput(adapters).listResources({ limit: 20 }),
     ).resolves.toEqual({
       ok: true,
       value: [
@@ -170,7 +188,7 @@ describe("reference feature runtime composition", () => {
     });
 
     await expect(
-      adapters.featureInputs[REFERENCE_FEATURE_ID].createResource(
+      referenceInput(adapters).createResource(
         { name: "Created resource" },
         { intent },
       ),