fix: restore V3 HTTP observability

Project one typed HttpExecutionObservation per logical V3 execution through a
closed composition-root projector: only registered diagnostic context keys and
bucketed values reach the sinks, and terminal non-abort failures now emit
exactly one api.request.failed telemetry event. Caller cancellation and scope
fencing record a diagnostic but never a failure event.

routeId becomes a required input at the installed operation-executor boundary
so the feature gateway's low-cardinality route identity survives to the sink.

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

docs/architecture/decisions/VD-07-diagnostics-and-telemetry-exporter.md

@@ -37,6 +37,21 @@ vendor 결정 전에는 안전한 기본값이 아니다.
    abort마다 `http.request.completed` diagnostics를 정확히 한 번 남긴다.
    `api.request.failed` telemetry는 retry가 끝난 terminal non-abort failure에만
    정확히 한 번 발행한다.
+5-1. V2 client와 V3 contract executor는 각각 자신의 logical execution에 대해
+   이 규칙을 만족한다. V3에서는 execution site가 `HttpExecutionObservation`
+   typed record 하나만 만들고, composition root의
+   `createHttpObservationProjector`가 유일한 projection authority다. observation은
+   arbitrary context map이 아니며 projector는 `route_id`, `operation_id`,
+   `operation`, `outcome`, `error_kind`, `http_status_group`,
+   `attempt_count_bucket`, `duration_bucket`만 사용한다. raw attempt count,
+   duration, status, URL, intent, key, input identity와 내부 `terminalReason`은
+   sink로 나가지 않는다. effect certainty가 운영상 필요해지면 `effect_certainty`
+   key와 닫힌 value policy를 contract·fixture·이 ADR에 동시에 추가한 뒤에만
+   전달한다.
+5-2. caller cancellation과 scope fence는 API failure가 아니다. diagnostics는 한
+   번 남기고 `api.request.failed`는 발행하지 않는다.
+5-3. `routeId`는 installed operation-executor 경계의 필수 입력이다. feature
+   gateway가 소유한 low-cardinality route identity를 URL에서 재구성하지 않는다.
 6. `app.boot.failed`, `ui.render.failed`, `release.mismatch.detected`,
    `telemetry.delivery.dropped`를 production path에 연결한다. cache와 storage
    실패는 diagnostics로 기록하되 raw key/value를 기록하지 않는다.
@@ -79,6 +94,11 @@ route/application/HTTP/cache/storage/bootstrap
   queue full, sink/observer failure와 pre-mount boot evidence를 검증한다.
 - HTTP integration은 success, retry recovery, terminal failure와 abort의 producer
   횟수, route/operation/correlation context와 요청 값 비노출을 검증한다.
+- `tests/integration/http-execution-v3-observability.test.ts`는 V3 terminal
+  outcome이 실제로 closed allowlist를 통과하는지, terminal non-abort failure가
+  `api.request.failed`를 정확히 한 번 발행하는지, cancellation/scope fence가
+  발행하지 않는지, feature route ID가 executor 경계까지 보존되는지, sink 예외가
+  HTTP 결과를 바꾸지 못하는지를 검증한다.
 - cache/storage/release/application/runtime test는 각 production wiring과
   diagnostics failure isolation을 검증한다.
 

docs/operations/adapter-remediation-ledger.md

@@ -72,7 +72,7 @@ Rollout state starts at `NOT_STARTED`; documented-unimplemented items start at
 
 | ID | Activation | Red test command | Fix commit/PR | Rollout state | Rollback trigger | Evidence |
 | --- | --- | --- | --- | --- | --- | --- |
-| N-01 | Live V3 path | `corepack pnpm exec vitest run tests/integration/http-execution-v3-observability.test.ts` | — | `NOT_STARTED` | diagnostics/telemetry producer gate regression | — |
+| N-01 | Live V3 path | `corepack pnpm exec vitest run tests/integration/http-execution-v3-observability.test.ts` | `fix: restore V3 HTTP observability` | `FIXED_NOT_RELEASED` | diagnostics/telemetry producer gate regression | Red 5/5 failed → green 5/5; `check:diagnostics` PASS (8 diagnostics, 5 telemetry producers); `check:types` PASS; `check:architecture` PASS |
 | N-02 | Live V3 path | `corepack pnpm exec vitest run tests/integration/http-execution-v3-auth-profile.test.ts` | — | `NOT_STARTED` | authenticated request 4xx spike after profile enforcement | — |
 | N-03 | Live V3 path | `corepack pnpm exec vitest run tests/unit/http-execution-v3.test.ts` | — | `NOT_STARTED` | command effect verdict regression | — |
 | N-04 | Live composition teardown | `corepack pnpm exec vitest run tests/unit/telemetry.test.ts` | — | `NOT_STARTED` | telemetry delivery loss after teardown change | — |