fix: invalidate the TechLog CSRF token on 403 and harden the bootstrap profile wiring

Item 1 (real bug): contractOperations.execute only invalidated the cached
CSRF token on UNAUTHENTICATED (401). A CSRF-specific rejection normally
arrives as FORBIDDEN (403) -- the platform classifies any 403 response as
FORBIDDEN unconditionally -- so a token rejected during an ordinary document
save left the stale token cached and every subsequent Studio mutation kept
failing until reload. Extracted invalidateTechLogCsrfOnOutcome() so
production and the composition test call the identical function; it now
invalidates on both UNAUTHENTICATED and FORBIDDEN.

Item 2: the upload transport's uncontracted-status fallback hardcoded status
503, so an uncontracted 401/403 body never reached the gateway's
error.status === 401 || 403 invalidation check. Passes the real
response.status through.

Item 3: safeOperation()'s auth-profile parameter is now typed as a union of
the two valid profile constants instead of a bare string, and
assertExactlyOneTechLogStudioBootstrapOperation() fails composition closed
if getStudioSession stops being the sole caller of the credential-free
bootstrap profile.

Item 4: corrected two stale operation counts in the adapter review doc.

Both new tests for items 1 and 2 were run and shown failing before their
fix, per this task's TDD standard for error-path changes.

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

tests/features/tech-log/studio-csrf-composition.test.ts

@@ -9,7 +9,10 @@ import { INSTALLED_REST_AUTH_PROFILES } from "../../../src/contracts/rest-profil
 import { createAssetUploadTransport } from "../../../src/features/tech-log/adapters/http/asset-upload-transport.ts";
 import { createHttpStudioAssetGateway } from "../../../src/features/tech-log/adapters/http/http-studio-asset-gateway.ts";
 import { createCsrfTokenProvider } from "../../../src/features/tech-log/adapters/http/studio-session-csrf.ts";
-import { attachStudioSessionCredentials } from "../../../src/features/tech-log/adapters/http/studio-session-credentials.ts";
+import {
+  attachStudioSessionCredentials,
+  invalidateTechLogCsrfOnOutcome,
+} from "../../../src/features/tech-log/adapters/http/studio-session-credentials.ts";
 import type { StudioOperationExecutor } from "../../../src/features/tech-log/adapters/http/http-studio-gateway.ts";
 import { TECH_LOG_STUDIO_CONTRIBUTION } from "../../../src/features/tech-log/contracts/tech-log-studio-contract-contribution.ts";
 
@@ -102,12 +105,17 @@ function composeStudioRuntime() {
     async execute(operationId, input, executionContext) {
       const operation = composed.httpByOperationId.get(operationId);
       if (!operation) throw new Error(`no such operation: ${operationId}`);
-      return contractHttp.execute(operation, input, {
+      const outcome = await contractHttp.execute(operation, input, {
         routeId: executionContext.routeId,
         scope: scopeSnapshot(),
         ...(executionContext.signal ? { signal: executionContext.signal } : {}),
         ...(executionContext.intent ? { intent: executionContext.intent } : {}),
       });
+      // Fix round 2, item 1. Same production call as
+      // `bootstrap/runtime-adapters.ts`'s `contractOperations.execute` — not
+      // a reimplementation of it.
+      invalidateTechLogCsrfOnOutcome(outcome.kind, techLogCsrf);
+      return outcome;
     },
   });
 
@@ -182,3 +190,67 @@ test(
     assert.equal(sessionCalls, 1);
   },
 );
+
+/**
+ * Fix round 2, item 1. `contractOperations.execute` previously invalidated
+ * `techLogCsrf` only on `UNAUTHENTICATED` (HTTP 401). A CSRF-specific
+ * rejection normally arrives as `FORBIDDEN` (HTTP 403) instead — the
+ * platform classifies any 403 response as `FORBIDDEN` regardless of body
+ * (`http-execution-v3.ts:1050`) — so a token rejected during an ordinary
+ * document save left the stale token cached, and every subsequent Studio
+ * mutation kept failing until the page reloaded. The multipart upload path
+ * already invalidated on both 401 and 403; this proves the JSON path now
+ * agrees.
+ */
+test(
+  "a 403 on a JSON operation invalidates the cached token so the next operation re-fetches the session",
+  async () => {
+    let sessionCalls = 0;
+    server.use(
+      http.get(`${BASE}/api/v1/studio/session`, () => {
+        sessionCalls += 1;
+        return HttpResponse.json({
+          authenticated: true,
+          displayName: "테스터",
+          roles: ["editor"],
+          csrfToken: `csrf-token-${sessionCalls}`,
+          csrfHeaderName: "X-CSRF-TOKEN",
+        });
+      }),
+    );
+
+    const dashboardHeaders: (string | null)[] = [];
+    server.use(
+      http.get(`${BASE}/api/v1/studio/dashboard`, ({ request }) => {
+        dashboardHeaders.push(request.headers.get("x-csrf-token"));
+        // First call: the server rejects the (now-stale) token with 403.
+        // Second call: succeeds with whatever token is presented.
+        return dashboardHeaders.length === 1
+          ? new HttpResponse(null, { status: 403 })
+          : HttpResponse.json({ documentTotals: {}, workflowSections: [] });
+      }),
+    );
+
+    const { contractOperations } = composeStudioRuntime();
+
+    const first = await contractOperations.execute(
+      "getStudioDashboard",
+      {},
+      { routeId: "TECH_LOG_STUDIO" },
+    );
+    assert.equal(first.kind, "FORBIDDEN");
+    assert.equal(dashboardHeaders[0], "csrf-token-1");
+
+    const second = await contractOperations.execute(
+      "getStudioDashboard",
+      {},
+      { routeId: "TECH_LOG_STUDIO" },
+    );
+    assert.equal(second.kind, "SUCCESS");
+    assert.equal(dashboardHeaders[1], "csrf-token-2");
+
+    // Two fresh session fetches: the cache was discarded after the 403, not
+    // replayed on the retry.
+    assert.equal(sessionCalls, 2);
+  },
+);