fix(advisor): resolve the factory for the Claude replay config

docs-site/src/content/docs/fr/reference/configuration/advisor.md

@@ -43,7 +43,7 @@ Sur la page **Advisor**, choisissez le modèle dans le catalogue. Le sélecteur
 Gérez-le via la page **Advisor** du tableau de bord ou
 `ocx advisor status|on|off|set --model <model> --effort <effort> --policy <manual|preflight|adaptive>`.
 
-Sans consentement courant, `ocx advisor on` n'active pas le partage inter-fournisseurs : il affiche cette divulgation et s'arrête. `ocx advisor on --ack-context-sharing` et `ocx advisor consent` enregistrent `v1`. `ocx advisor consent --revoke` retire le consentement et arrête immédiatement l'envoi. `ocx advisor set` n'accorde pas le consentement. La case du tableau de bord n'est pas précochée.
+Sans consentement courant, `ocx advisor on` n'active pas le partage inter-fournisseurs : il affiche cette divulgation et s'arrête. `ocx advisor on --ack-context-sharing` et `ocx advisor consent` enregistrent `v1`. `ocx advisor consent --revoke` retire le consentement. Les consultations qui n'ont pas encore été envoyées sont bloquées, mais une consultation déjà envoyée ne peut pas être annulée, et le contexte déjà transmis hors du proxy ne peut pas être retiré. `ocx advisor set` n'accorde pas le consentement. La case du tableau de bord n'est pas précochée.
 
 ## Politiques
 

docs-site/src/content/docs/ja/reference/configuration/advisor.md

@@ -35,7 +35,7 @@ description: manual、preflight、証拠に基づく adaptive ポリシーによ
 
 ダッシュボードの **Advisor** ページまたは `ocx advisor status|on|off|set --model <model> --effort <effort> --policy <manual|preflight|adaptive>` で管理します。
 
-現在の同意がないとき、`ocx advisor on` はプロバイダー間送信を有効にしません。開示を表示して停止します。`ocx advisor on --ack-context-sharing` と `ocx advisor consent` が `v1` を記録します。`ocx advisor consent --revoke` は同意を消し、送信を直ちに止めます。`ocx advisor set` は同意を与えません。ダッシュボードの同意チェックは初期状態でオフです。
+現在の同意がないとき、`ocx advisor on` はプロバイダー間送信を有効にしません。開示を表示して停止します。`ocx advisor on --ack-context-sharing` と `ocx advisor consent` が `v1` を記録します。`ocx advisor consent --revoke` は同意を消します。まだディスパッチされていない相談はブロックされますが、すでにディスパッチされた相談は取り消せず、すでにプロキシを離れた文脈も取り戻せません。`ocx advisor set` は同意を与えません。ダッシュボードの同意チェックは初期状態でオフです。
 
 ## ポリシー
 

docs-site/src/content/docs/ko/reference/configuration/advisor.md

@@ -35,7 +35,7 @@ description: manual, preflight 및 증거 기반 adaptive 정책을 제공하는
 
 대시보드 **Advisor** 페이지 또는 `ocx advisor status|on|off|set --model <model> --effort <effort> --policy <manual|preflight|adaptive>`로 관리합니다.
 
-현재 동의가 없으면 `ocx advisor on`은 프로바이더 간 전송을 켜지 않습니다. 고지를 출력하고 멈춥니다. `ocx advisor on --ack-context-sharing`와 `ocx advisor consent`가 `v1`을 기록합니다. `ocx advisor consent --revoke`는 동의를 지우고 전송을 즉시 멈춥니다. `ocx advisor set`은 동의를 부여하지 않습니다. 대시보드의 동의 확인란은 미리 선택되지 않습니다.
+현재 동의가 없으면 `ocx advisor on`은 프로바이더 간 전송을 켜지 않습니다. 고지를 출력하고 멈춥니다. `ocx advisor on --ack-context-sharing`와 `ocx advisor consent`가 `v1`을 기록합니다. `ocx advisor consent --revoke`는 동의를 지웁니다. 아직 디스패치되지 않은 상담은 차단되지만, 이미 디스패치된 상담은 취소할 수 없고 이미 프록시를 떠난 맥락도 되돌릴 수 없습니다. `ocx advisor set`은 동의를 부여하지 않습니다. 대시보드의 동의 확인란은 미리 선택되지 않습니다.
 
 ## 정책
 

docs-site/src/content/docs/reference/configuration/advisor.md

@@ -206,6 +206,12 @@ consultation never switches the session's main model.
 - Native OpenAI passthrough turns (ChatGPT-pool workers) do not get the synthetic tool; advisor
   support covers routed (translated) providers. Preflight consultation applies to run-turn
   adapters; the tool does not.
+- Translated `/v1/messages` requests (for example Claude Code routed to a translated provider)
+  get the synthetic tool and preflight like `/v1/responses` and `/v1/chat/completions`. The
+  same `policy` and context-sharing consent rules apply, and the settings are read from the live
+  config, so a consent revocation blocks consultations for requests already in flight that have
+  not yet been dispatched. It does not cancel a dispatched consultation or retract context that
+  already left the proxy.
 - No semantic stuck detection, completion review, escalation tiers, multiple advisors or voting.
   Adaptive consultation requires the structured validation/edit/retry evidence described above.
 - The preflight dedup ledger is process-local; after a proxy restart, a task in progress may

docs-site/src/content/docs/ru/reference/configuration/advisor.md

@@ -35,7 +35,7 @@ description: Независимые консультации с политика
 
 Управляйте через страницу **Advisor** на дашборде или `ocx advisor status|on|off|set --model <model> --effort <effort> --policy <manual|preflight|adaptive>`.
 
-Без текущего согласия `ocx advisor on` не включает межпровайдерную отправку: команда печатает раскрытие и останавливается. `ocx advisor on --ack-context-sharing` и `ocx advisor consent` записывают `v1`. `ocx advisor consent --revoke` снимает согласие и сразу прекращает отправку. `ocx advisor set` согласие не выдаёт. Флажок на дашборде изначально снят.
+Без текущего согласия `ocx advisor on` не включает межпровайдерную отправку: команда печатает раскрытие и останавливается. `ocx advisor on --ack-context-sharing` и `ocx advisor consent` записывают `v1`. `ocx advisor consent --revoke` снимает согласие. Ещё не отправленные консультации блокируются, но уже отправленную консультацию нельзя отменить, а ушедший из прокси контекст нельзя отозвать. `ocx advisor set` согласие не выдаёт. Флажок на дашборде изначально снят.
 
 ## Политики
 

docs-site/src/content/docs/tr/reference/configuration/advisor.md

@@ -35,7 +35,7 @@ Kontrol panelindeki **Advisor** sayfasında katalogdan model seçin. Yerel, sağ
 
 Panodaki **Advisor** sayfası veya `ocx advisor status|on|off|set --model <model> --effort <effort> --policy <manual|preflight|adaptive>` ile yönetin.
 
-Güncel onay yokken `ocx advisor on` sağlayıcılar arası gönderimi açmaz: açıklamayı basar ve durur. `ocx advisor on --ack-context-sharing` ile `ocx advisor consent` `v1` kaydeder. `ocx advisor consent --revoke` onayı kaldırır ve gönderimi hemen durdurur. `ocx advisor set` onay vermez. Panodaki onay kutusu önceden işaretli değildir.
+Güncel onay yokken `ocx advisor on` sağlayıcılar arası gönderimi açmaz: açıklamayı basar ve durur. `ocx advisor on --ack-context-sharing` ile `ocx advisor consent` `v1` kaydeder. `ocx advisor consent --revoke` onayı kaldırır. Henüz gönderilmemiş danışmalar engellenir, ancak gönderilmiş bir danışma iptal edilemez ve proxy'den ayrılmış bağlam geri alınamaz. `ocx advisor set` onay vermez. Panodaki onay kutusu önceden işaretli değildir.
 
 ## Politikalar
 

docs-site/src/content/docs/zh-cn/reference/configuration/advisor.md

@@ -35,7 +35,7 @@ description: 独立专家咨询，支持 manual、preflight 与基于证据的 a
 
 通过仪表盘的 **Advisor** 页面或 `ocx advisor status|on|off|set --model <model> --effort <effort> --policy <manual|preflight|adaptive>` 管理。
 
-`ocx advisor on` 在没有当前同意时不会开启跨 provider 发送：它会打印披露并停止。`ocx advisor on --ack-context-sharing` 与 `ocx advisor consent` 记录 `v1`。`ocx advisor consent --revoke` 会移除同意并立即停止发送。`ocx advisor set` 不授予同意。仪表盘上的同意复选框默认不勾选。
+`ocx advisor on` 在没有当前同意时不会开启跨 provider 发送：它会打印披露并停止。`ocx advisor on --ack-context-sharing` 与 `ocx advisor consent` 记录 `v1`。`ocx advisor consent --revoke` 会移除同意。尚未发出的咨询会被阻断，但已经发出的咨询无法取消，已经离开代理的上下文也无法收回。`ocx advisor set` 不授予同意。仪表盘上的同意复选框默认不勾选。
 
 ## 策略
 

docs-site/src/content/docs/zh-tw/reference/configuration/advisor.md

@@ -35,7 +35,7 @@ description: 獨立專家諮詢，支援 manual、preflight 與依據證據的 a
 
 透過儀表板的 **Advisor** 頁面或 `ocx advisor status|on|off|set --model <model> --effort <effort> --policy <manual|preflight|adaptive>` 管理。
 
-沒有目前同意時，`ocx advisor on` 不會開啟跨 provider 傳送：它會印出揭露並停止。`ocx advisor on --ack-context-sharing` 與 `ocx advisor consent` 記錄 `v1`。`ocx advisor consent --revoke` 會移除同意並立即停止傳送。`ocx advisor set` 不授予同意。儀表板上的同意核取方塊預設不勾選。
+沒有目前同意時，`ocx advisor on` 不會開啟跨 provider 傳送：它會印出揭露並停止。`ocx advisor on --ack-context-sharing` 與 `ocx advisor consent` 記錄 `v1`。`ocx advisor consent --revoke` 會移除同意。尚未發出的諮詢會被阻擋，但已經發出的諮詢無法取消，已經離開代理的上下文也無法收回。`ocx advisor set` 不授予同意。儀表板上的同意核取方塊預設不勾選。
 
 ## 策略
 

scripts/test-layout/layout-agent-assertion.json

@@ -10,6 +10,7 @@
   "advisor-caller-policy-routing.test.ts": "advisor",
   "advisor-caller-policy-host-key.test.ts": "advisor",
   "advisor-caller-policy-self-fetch.test.ts": "advisor",
+  "advisor-messages-replay-config.test.ts": "advisor",
   "windows-native-principal.test.ts": "windows",
   "fixture-windows-runtime-preload.test.ts": "ci-workflows",
   "agent-assertion-auth.test.ts": "server",

src/advisor/runtime.ts

@@ -36,6 +36,7 @@ import {
 } from "./state";
 import { formatAdvisorAdvice, advisorPreflightMessages, formatAdvisorUnavailable } from "./context";
 import { advisorActivityStore, type AdvisorActivityStore, type AdvisorTrigger } from "./activity";
+import { advisorPlanRootConfig } from "../server/responses/advisor-plan-slot";
 import { createAdvisorTaskBudget, type AdvisorTaskBudget } from "./budget";
 import { collectAdvisorRepairEvidence, type AdvisorRepairEvidence } from "./evidence";
 import type { AdmissionModelScope } from "../server/admission-model-scope";
@@ -95,7 +96,10 @@ export function createAdvisorRuntimePlan(deps: AdvisorRuntimeDeps): AdvisorRunti
   const ledger = deps.ledger ?? sharedPreflightLedger;
   const now = deps.now ?? (() => Date.now());
   const budget = deps.budget ?? createAdvisorTaskBudget();
-  const activities = deps.activities ?? advisorActivityStore(deps.config);
+  // Identity-scoped state must key on the LIVE config: `GET /api/advisor/activity` reads the store
+  // of the management context's own config, so a request-scoped view (the Claude replay config)
+  // would record consultations the dashboard and CLI never see.
+  const activities = deps.activities ?? advisorActivityStore(advisorPlanRootConfig(deps.config));
   // Management PUT mutates this same config object (`config.advisor = ...`). Re-resolving
   // at dispatch is what makes a mid-request consent revocation stop outbound transfer.
   const liveSettings = () => resolveAdvisorSettings(deps.config);

src/server/claude-messages.ts

@@ -46,6 +46,7 @@ import { captureAdmissionPolicy } from "./capture-admission-policy";
 import type { CapturedAdmissionPolicy } from "../types/admission-policy";
 import { captureClaudeInbound } from "../claude/inbound-debug";
 import { declaredAnthropicServerTools, replayedAnthropicServerBlocks, systemCachePrefix } from "../claude/inbound-content-options";
+import { linkAdvisorPlanConfig } from "./responses/advisor-plan-slot";
 import { claudeCodeForIngress } from "../claude/intercept/model-bindings";
 import { classifyInterceptClient } from "../claude/intercept/client-class";
 import { analyzeClaudeCompatibility, isClaudeCompatibilityMode } from "../claude/compatibility";
@@ -1265,12 +1266,13 @@ async function handleClaudeMessagesWithBudget(
   // BEFORE translation (the translated Anthropic stream has no response.completed
   // frame, so tapping it records a bogus 502 with no usage/cache detail).
   const finalizeNativeLog = createFinalRequestLog(logIds, logCtx).finish;
-  const upstream = await handleResponses(internalReq, {
+  // The replay view is a new object; link it so the Advisor factory registered on `config` applies.
+  const upstream = await handleResponses(internalReq, linkAdvisorPlanConfig(config, {
     ...buildClaudeReplayConfig(config),
     // Operator config wins; otherwise the caller's explicit TTLs (all 1h, or a pinned 5m) carry
     // over, and TTL-less breakpoints take the destination default.
     cacheRetention: config.cacheRetention ?? callerCacheRetention(anthropicBody),
-  }, logCtx, {
+  }), logCtx, {
     ...(nativeComboSource && envelope && settledRoute?.combo ? {
       protocolSource: (await import("./messages-native")).createNativeMessagesComboSource({
         req, config, logCtx, envelope, requestedModel, translatorBudget, selector: nativeSelector,

src/server/responses/advisor-plan-slot.ts

@@ -29,6 +29,38 @@ export function setAdvisorPlanFactory(config: OcxConfig, factory: AdvisorPlanFac
   else factories.delete(config);
 }
 
+/** Request-scoped config views (e.g. the Claude replay config) -> the live config they were built from. */
+type AdvisorLinkedConfig = Pick<OcxConfig, "advisor">;
+const views = new WeakMap<AdvisorLinkedConfig, OcxConfig>();
+
+/**
+ * Record that `view` is a request-scoped copy of `live`. A view resolves the live config's
+ * factory at lookup time, so a later disable or re-activation of the live config still applies.
+ * The view's `advisor` reads through to the live config: management writes replace that object
+ * (`config.advisor = ...`), so a copied reference would keep a revoked consent alive for the
+ * plan. Every other request-scoped override on the view is kept. Nothing is stored on the live
+ * config, and an accessor is still cloneable (#7974).
+ */
+export function linkAdvisorPlanConfig<T extends OcxConfig>(live: OcxConfig, view: T): T {
+  const root = views.get(live) ?? live;
+  views.set(view, root);
+  if (view !== root) {
+    Object.defineProperty(view, "advisor", { get: () => root.advisor, enumerable: true, configurable: true });
+  }
+  return view;
+}
+
+/**
+ * The live config a request-scoped view was linked to, or the config itself when it was not
+ * linked. Identity-scoped state that must outlive one request (the activity feed the management
+ * route reads from its own config object) resolves through the same link as the factory.
+ */
+export function advisorPlanRootConfig<T extends AdvisorLinkedConfig>(config: T): T | OcxConfig {
+  return views.get(config) ?? config;
+}
+
+/** Create the plan from the factory registered for this config, or for the live config it was linked to. */
 export function createRegisteredAdvisorPlan(input: AdvisorPlanInput): Promise<RegisteredAdvisorPlan | null> | null {
-  return factories.get(input.config)?.(input) ?? null;
+  const live = views.get(input.config);
+  return (factories.get(input.config) ?? (live && factories.get(live)))?.(input) ?? null;
 }

structure/advisor.md

@@ -19,6 +19,13 @@ The server composition root registers it synchronously at startup; a successful
 updates activation, including enable after startup and disable/reset. The runtime is loaded only
 when an active factory is used, so its process-local ledger is not constructed by an inactive
 install. `sidecar-execution.ts` reads the core-owned slot, not Advisor settings or runtime.
+Request-scoped copies of the live config, such as the Claude replay config `/v1/messages` passes to
+the Responses pipeline, are linked with `linkAdvisorPlanConfig` so they resolve the live config's
+factory at lookup time. The view's `advisor` reads through to the live config, so a consent
+revocation after the copy still blocks outbound transfer up to dispatch: the runtime rechecks
+consent immediately before the loopback call, and a revocation after that call has been dispatched
+neither cancels it nor retracts context already sent
+(`tests/advisor/advisor-messages-replay-config.test.ts`).
 Advisor settings admit the complete synchronous candidate/read/patch/save/activation phase through the [config admission contract](config.md). Production uses the current disk candidate when present, preserving unrelated disk edits during admission. Successful saves adopt the committed Advisor subtree and its field-scoped live baseline together, including known absence after reset, without advancing unrelated pending live edits. Fallback or error-bearing diagnostics are refused before mutation. Deadline refusal leaves live and durable settings untouched and retains the existing `write_failed` response. Successful receipts are serialized in that callback before another settings mutation can run.
 Management loads `advisor-routes.ts` only for the Advisor namespace. The guard is attached through
 `_advisorGuard`. `tests/advisor/advisor-core-boundary.test.ts` enforces the transitive load-time
@@ -332,7 +339,9 @@ request under the advisor model. Consultation usage is never merged into the wor
 usage; intercepted worker legs are, via the same usage-merge rule the terminal guard applies.
 
 `src/advisor/activity.ts` holds config-scoped process memory: at most 100 records, at most 24
-hours old, with pruning on access and no timer. `GET /api/advisor/activity` and `ocx advisor
+hours old, with pruning on access and no timer. The store is keyed by the LIVE config object, so a
+request that runs on a linked view (the Claude replay config) records into the feed the management
+route reads. `GET /api/advisor/activity` and `ocx advisor
 activity` expose trigger, status, models, requested/mapped effort, duration and reported tokens.
 There are no task bodies, commands, advice, conversation identifiers or provider error bodies
 in these records. Dashboard polling runs only while its page is visible. Restart clears activity,