chore: sync the frontend template from a0fbafb to 5434760

Carries eight template commits: the provider sandbox actually running, release
admission to a named environment, the product feature manifest with its runtime
kill switch, architecture and documentation rules that match what is enforced,
the removability fixtures, and the browser, visual and performance evidence.

Product identity is unchanged. `package.json` keeps `tech-log-frontend` and the
catalog keeps the Tech Log naming; the home page was not in the delta. The
visual baselines are this product's own — the template's were excluded from the
transplant and these were regenerated here, where the only difference is the
platform overview's new product-feature section.

What this repository gains operationally: `config/runtime/{local,development,
staging,production}.json` with `FE-GATE-027` refusing an artifact whose runtime
document does not match the environment it is being admitted to, and
`FEATURE_OVERRIDES` for taking an installed feature out of service without a
rebuild.

Verified here: eight gates green, build green, visual 5/5, and 1,858 of 1,859
tests in the suites that do not need a sandbox — the one failure passes in
isolation and is a jsdom lazy-chunk timeout under parallel load. The provider
suites cannot run on this machine at all: `kernel.apparmor_restrict_unprivileged
_userns=1` makes `bwrap --unshare-net` fail, reproducible without any code from
either repository.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

src/application/ports/in/application-api.ts

@@ -1,8 +1,10 @@
 import type { SessionState } from "../auth-session-port.ts";
+import type { ProductFeatureStatus } from "../product-features-port.ts";
 import type { RuntimeCapabilitySnapshot } from "../runtime-capabilities-port.ts";
 import type { StoragePort } from "../storage-port.ts";
 
 export type { SessionState } from "../auth-session-port.ts";
+export type { ProductFeatureStatus };
 export type { RuntimeCapabilitySnapshot };
 
 /**
@@ -64,6 +66,13 @@ export type ApplicationApi = Readonly<{
      * reads capability state here instead of importing the composition root.
      */
     getCapabilitySnapshot(): RuntimeCapabilitySnapshot;
+    /**
+     * §3.5. Which product features this build contains and which of them the
+     * runtime document switched off. Presentation reads state here; it never
+     * learns how to reach a feature the build left out.
+     */
+    getFeatureSnapshot(): readonly ProductFeatureStatus[];
+    isFeatureActive(featureId: string): boolean;
   }>;
   recovery: Readonly<{
     recoverChunk(input: Readonly<{

src/application/ports/out/application-output-ports.ts

@@ -1,5 +1,6 @@
 import type { AuthSessionPort } from "../auth-session-port.ts";
 import type { ReleaseInfoPort } from "../release-info-port.ts";
+import type { ProductFeaturesPort } from "../product-features-port.ts";
 import type { RuntimeCapabilitiesPort } from "../runtime-capabilities-port.ts";
 import type { StoragePort } from "../storage-port.ts";
 import type { TelemetryPort } from "../telemetry-port.ts";
@@ -19,5 +20,6 @@ export type ApplicationOutputPorts = Readonly<{
   telemetry: TelemetryPort;
   releaseInfo: ReleaseInfoPort;
   runtimeCapabilities: RuntimeCapabilitiesPort;
+  productFeatures: ProductFeaturesPort;
   navigation: Readonly<{ reload(): void }>;
 }>;

src/application/ports/product-features-port.ts

@@ -0,0 +1,16 @@
+import type { ProductFeatureStatus } from "../../contracts/product-features.ts";
+
+export type { ProductFeatureStatus };
+
+/**
+ * §3.5. The application reads feature state; it never resolves it.
+ *
+ * Only the composition root knows both halves of the answer — what the build
+ * compiled in and what the runtime document disabled — so the snapshot arrives
+ * here already reduced to ids and states. It carries no feature module, so
+ * reading it cannot become a way to reach code the build left out.
+ */
+export type ProductFeaturesPort = Readonly<{
+  getSnapshot(): readonly ProductFeatureStatus[];
+  isActive(featureId: string): boolean;
+}>;