@vellumai/assistant 0.10.12 → 0.11.0-staging.2

package/src/daemon/message-types/contacts.ts

@@ -1,13 +0,0 @@
-// Contact events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`. Contact list/get/delete are served by the HTTP
-// `contacts` routes, not by a client message.
-
-import type { ContactRequestEvent } from "../../api/events/contact-request.js";
-import type { ContactsChangedEvent } from "../../api/events/contacts-changed.js";
-
-export type _ContactsServerMessages =
-  | ContactsChangedEvent
-  | ContactRequestEvent;

package/src/daemon/message-types/document-comments.ts

@@ -1,14 +0,0 @@
-// Document comment event types (Server → Client).
-
-import type { DocumentCommentCreatedEvent } from "../../api/events/document-comment-created.js";
-import type { DocumentCommentDeletedEvent } from "../../api/events/document-comment-deleted.js";
-import type { DocumentCommentReopenedEvent } from "../../api/events/document-comment-reopened.js";
-import type { DocumentCommentResolvedEvent } from "../../api/events/document-comment-resolved.js";
-
-// --- Domain-level union alias (consumed by the barrel file) ---
-
-export type _DocumentCommentsServerMessages =
-  | DocumentCommentCreatedEvent
-  | DocumentCommentResolvedEvent
-  | DocumentCommentReopenedEvent
-  | DocumentCommentDeletedEvent;

package/src/daemon/message-types/documents.ts

@@ -1,13 +0,0 @@
-// Document editor events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`. Document save/load/list are served by the document
-// tools and HTTP document routes, not by client messages.
-
-import type { DocumentEditorShowEvent } from "../../api/events/document-editor-show.js";
-import type { DocumentEditorUpdateEvent } from "../../api/events/document-editor-update.js";
-
-export type _DocumentsServerMessages =
-  | DocumentEditorShowEvent
-  | DocumentEditorUpdateEvent;

package/src/daemon/message-types/home.ts

@@ -1,15 +0,0 @@
-/**
- * Home — server → client push messages for the macOS Home page.
- *
- * These messages are fire-and-forget notifications; the client reacts
- * by refetching the authoritative state from the HTTP route
- * (`GET /v1/home/state`). Payloads stay deliberately tiny — they carry
- * just enough metadata to invalidate a cache and trigger a refetch.
- */
-
-import type { HomeFeedUpdatedEvent } from "../../api/events/home-feed-updated.js";
-import type { RelationshipStateUpdatedEvent } from "../../api/events/relationship-state-updated.js";
-
-export type _HomeServerMessages =
-  | RelationshipStateUpdatedEvent
-  | HomeFeedUpdatedEvent;

package/src/daemon/message-types/host-bash.ts

@@ -1,12 +0,0 @@
-// Host bash proxy events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { HostBashCancelEvent } from "../../api/events/host-bash.js";
-import type { HostBashRequestEvent } from "../../api/events/host-bash.js";
-
-export type _HostBashServerMessages =
-  | HostBashRequestEvent
-  | HostBashCancelEvent;

package/src/daemon/message-types/host-cu.ts

@@ -1,10 +0,0 @@
-// Host computer-use proxy events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { HostCuCancelEvent } from "../../api/events/host-cu.js";
-import type { HostCuRequestEvent } from "../../api/events/host-cu.js";
-
-export type _HostCuServerMessages = HostCuRequestEvent | HostCuCancelEvent;

package/src/daemon/message-types/host-file.ts

@@ -1,12 +0,0 @@
-// Host file proxy events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { HostFileCancelEvent } from "../../api/events/host-file.js";
-import type { HostFileRequestEvent } from "../../api/events/host-file.js";
-
-export type _HostFileServerMessages =
-  | HostFileRequestEvent
-  | HostFileCancelEvent;

package/src/daemon/message-types/host-transfer.ts

@@ -1,12 +0,0 @@
-// Host transfer proxy events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { HostTransferCancelEvent } from "../../api/events/host-transfer.js";
-import type { HostTransferRequestEvent } from "../../api/events/host-transfer.js";
-
-export type _HostTransferServerMessages =
-  | HostTransferRequestEvent
-  | HostTransferCancelEvent;

package/src/daemon/message-types/integrations.ts

@@ -1,90 +0,0 @@
-// External service integrations: Slack, Telegram, Vercel, ingress, platform.
-//
-// Server→client events that are live hub broadcasts are single-sourced from
-// their canonical `api/events` wire schemas; this file only composes them into
-// the domain union consumed by `message-protocol.ts`. Config get/set flows
-// (Slack webhook, ingress, platform, Vercel, Telegram, integration listing and
-// connect) are served by the HTTP settings routes, not by client messages.
-
-import type { NavigateSettingsEvent } from "../../api/events/navigate-settings.js";
-import type { OAuthConnectResultEvent } from "../../api/events/oauth-connect-result.js";
-import type { OpenPanelEvent } from "../../api/events/open-panel.js";
-import type { OpenUrlEvent } from "../../api/events/open-url.js";
-import type { PlatformDisconnectedEvent } from "../../api/events/platform-disconnected.js";
-import type { ShowPlatformLoginEvent } from "../../api/events/show-platform-login.js";
-import type { ChannelId } from "../../channels/types.js";
-
-// === Client → Server ===
-
-export interface ChannelVerificationSessionRequest {
-  type: "channel_verification_session";
-  action:
-    | "create_session"
-    | "status"
-    | "cancel_session"
-    | "revoke"
-    | "resend_session";
-  channel?: ChannelId; // Defaults to 'telegram'
-  conversationId?: string;
-  rebind?: boolean; // When true, allows creating a challenge even if a binding already exists
-  /** E.164 phone number for phone, Telegram handle/chat-id. Used by outbound actions. */
-  destination?: string;
-  /** Origin conversation ID so completion/failure pointers can route back. */
-  originConversationId?: string;
-  /** Distinguishes guardian vs trusted-contact verification flows in the unified create endpoint. */
-  purpose?: "guardian" | "trusted_contact";
-  /** Contact-channel ID for the absorbed contact-channel verify flow. */
-  contactChannelId?: string;
-}
-
-// === Server → Client ===
-
-export interface ChannelVerificationSessionResponse {
-  type: "channel_verification_session_response";
-  success: boolean;
-  secret?: string;
-  instruction?: string;
-  /** Present when action is 'status'. */
-  bound?: boolean;
-  guardianExternalUserId?: string;
-  /** The channel this status pertains to (e.g. "telegram", "phone"). Present when action is 'status'. */
-  channel?: ChannelId;
-  /** The assistant ID scoped to this status. Present when action is 'status'. */
-  assistantId?: string;
-  /** The delivery chat ID for the guardian (e.g. Telegram chat ID). Present when action is 'status' and bound is true. */
-  guardianDeliveryChatId?: string;
-  /** Optional channel username/handle for the bound guardian (for UI display). */
-  guardianUsername?: string;
-  /** Optional display name for the bound guardian (for UI display). */
-  guardianDisplayName?: string;
-  /** Whether a pending verification challenge exists for this (assistantId, channel). Used by relay setup to detect active voice verification sessions. */
-  hasPendingChallenge?: boolean;
-  error?: string;
-  /** Human-readable error detail (e.g. for already_bound failures). */
-  message?: string;
-  /** Conversation ID for outbound verification flows. */
-  verificationSessionId?: string;
-  /** Epoch ms when the verification session expires. */
-  expiresAt?: number;
-  /** Epoch ms after which a resend is allowed. */
-  nextResendAt?: number;
-  /** Number of sends for this session. */
-  sendCount?: number;
-  /** Telegram deep-link URL for bootstrap (M3 placeholder). */
-  telegramBootstrapUrl?: string;
-  /** True when the outbound session is still in pending_bootstrap state (Telegram handle flow). Prevents the client from clearing the bootstrap URL during status polling. */
-  pendingBootstrap?: boolean;
-}
-
-// --- Domain-level union aliases (consumed by the barrel file) ---
-
-export type _IntegrationsClientMessages = ChannelVerificationSessionRequest;
-
-export type _IntegrationsServerMessages =
-  | ChannelVerificationSessionResponse
-  | OAuthConnectResultEvent
-  | OpenUrlEvent
-  | OpenPanelEvent
-  | NavigateSettingsEvent
-  | ShowPlatformLoginEvent
-  | PlatformDisconnectedEvent;

package/src/daemon/message-types/memory.ts

@@ -1,10 +0,0 @@
-// Memory recall and status events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`. Memory has no client messages.
-
-import type { MemoryRecalledEvent } from "../../api/events/memory-recalled.js";
-import type { MemoryStatusEvent } from "../../api/events/memory-status.js";
-
-export type _MemoryServerMessages = MemoryRecalledEvent | MemoryStatusEvent;

package/src/daemon/message-types/schedules.ts

@@ -1,14 +0,0 @@
-// Heartbeat events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`. Schedule / heartbeat / filing management (list,
-// config, run-now, checklist) is served by the HTTP heartbeat and filing
-// routes, not by client messages.
-
-import type { HeartbeatAlertEvent } from "../../api/events/heartbeat-alert.js";
-import type { HeartbeatConversationCreatedEvent } from "../../api/events/heartbeat-conversation-created.js";
-
-export type _SchedulesServerMessages =
-  | HeartbeatAlertEvent
-  | HeartbeatConversationCreatedEvent;

package/src/daemon/message-types/settings.ts

@@ -1,17 +0,0 @@
-// Client settings: daemon-pushed configuration updates to connected clients.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`. Settings mutations (voice config, avatar generation)
-// are served by the HTTP settings/avatar routes, not by client messages.
-
-import type { AvatarUpdatedEvent } from "../../api/events/avatar-updated.js";
-import type { ClientSettingsUpdateEvent } from "../../api/events/client-settings-update.js";
-import type { ConfigChangedEvent } from "../../api/events/config-changed.js";
-import type { SoundsConfigUpdatedEvent } from "../../api/events/sounds-config-updated.js";
-
-export type _SettingsServerMessages =
-  | ClientSettingsUpdateEvent
-  | AvatarUpdatedEvent
-  | ConfigChangedEvent
-  | SoundsConfigUpdatedEvent;

package/src/daemon/message-types/subagents.ts

@@ -1,63 +0,0 @@
-// Subagent lifecycle and communication types.
-//
-// The `subagent_spawned` and `subagent_status_changed` server events are
-// single-sourced from their canonical `api/events` wire schemas; this file
-// composes them into the domain union consumed by `message-protocol.ts`.
-
-import type { SubagentSpawnedEvent } from "../../api/events/subagent-spawned.js";
-import type { SubagentStatusChangedEvent } from "../../api/events/subagent-status-changed.js";
-import type { UsageStats } from "./shared.js";
-
-// === Server → Client ===
-
-export interface SubagentDetailResponse {
-  type: "subagent_detail_response";
-  subagentId: string;
-  objective?: string;
-  usage?: UsageStats;
-  events: Array<{
-    type: string;
-    content: string;
-    toolName?: string;
-    isError?: boolean;
-    messageId?: string;
-  }>;
-}
-
-// === Client → Server ===
-
-export interface SubagentAbortRequest {
-  type: "subagent_abort";
-  subagentId: string;
-}
-
-export interface SubagentStatusRequest {
-  type: "subagent_status";
-  /** If omitted, returns all subagents for the conversation. */
-  subagentId?: string;
-}
-
-export interface SubagentMessageRequest {
-  type: "subagent_message";
-  subagentId: string;
-  content: string;
-}
-
-export interface SubagentDetailRequest {
-  type: "subagent_detail_request";
-  subagentId: string;
-  conversationId: string;
-}
-
-// --- Domain-level union aliases (consumed by the barrel file) ---
-
-export type _SubagentsClientMessages =
-  | SubagentAbortRequest
-  | SubagentStatusRequest
-  | SubagentMessageRequest
-  | SubagentDetailRequest;
-
-export type _SubagentsServerMessages =
-  | SubagentSpawnedEvent
-  | SubagentStatusChangedEvent
-  | SubagentDetailResponse;

package/src/daemon/message-types/upgrades.ts

@@ -1,14 +0,0 @@
-// Service-group upgrade lifecycle events.
-//
-// Server→client events are single-sourced from their canonical `api/events`
-// wire schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { ServiceGroupUpdateCompleteEvent } from "../../api/events/service-group-update-complete.js";
-import type { ServiceGroupUpdateProgressEvent } from "../../api/events/service-group-update-progress.js";
-import type { ServiceGroupUpdateStartingEvent } from "../../api/events/service-group-update-starting.js";
-
-export type _UpgradesServerMessages =
-  | ServiceGroupUpdateStartingEvent
-  | ServiceGroupUpdateProgressEvent
-  | ServiceGroupUpdateCompleteEvent;

package/src/daemon/message-types/workflows.ts

@@ -1,25 +0,0 @@
-// Workflow orchestration run lifecycle events.
-//
-// Emitted by the `WorkflowRunManager` (run-manager.ts) as a workflow run
-// progresses and completes. These are server → client push events only — the
-// run is launched via the workflow tool / scheduler / routes (later PRs), not
-// via a client message in this union.
-//
-// The events are single-sourced from their canonical `api/events` wire
-// schemas; this file only composes them into the domain union consumed by
-// `message-protocol.ts`.
-
-import type { WorkflowCompletedEvent } from "../../api/events/workflow-completed.js";
-import type { WorkflowLeafFinishedEvent } from "../../api/events/workflow-leaf-finished.js";
-import type { WorkflowLeafStartedEvent } from "../../api/events/workflow-leaf-started.js";
-import type { WorkflowProgressEvent } from "../../api/events/workflow-progress.js";
-import type { WorkflowStartedEvent } from "../../api/events/workflow-started.js";
-
-// --- Domain-level union aliases (consumed by the barrel file) ---
-
-export type _WorkflowsServerMessages =
-  | WorkflowProgressEvent
-  | WorkflowCompletedEvent
-  | WorkflowStartedEvent
-  | WorkflowLeafStartedEvent
-  | WorkflowLeafFinishedEvent;

package/src/daemon/message-types/workspace.ts

@@ -1,137 +0,0 @@
-// Workspace file, identity, and tool permission types.
-
-import type { IdentityChangedEvent } from "../../api/events/identity-changed.js";
-
-// === Client → Server ===
-
-export interface WorkspaceFilesListRequest {
-  type: "workspace_files_list";
-}
-
-export interface WorkspaceFileReadRequest {
-  type: "workspace_file_read";
-  /** Relative path within the workspace directory (e.g. "IDENTITY.md"). */
-  path: string;
-}
-
-export interface IdentityGetRequest {
-  type: "identity_get";
-}
-
-export interface ToolPermissionSimulateRequest {
-  type: "tool_permission_simulate";
-  /** Tool name to simulate (e.g. 'bash', 'file_write'). */
-  toolName: string;
-  /** Tool input record to simulate. */
-  input: Record<string, unknown>;
-  /** Working directory context; defaults to daemon cwd when omitted. */
-  workingDir?: string;
-  /** Whether the simulated context is interactive (default true). */
-  isInteractive?: boolean;
-}
-
-export interface ToolNamesListRequest {
-  type: "tool_names_list";
-}
-
-// === Server → Client ===
-
-export interface WorkspaceFilesListResponse {
-  type: "workspace_files_list_response";
-  files: Array<{
-    /** Relative path within the workspace (e.g. "IDENTITY.md", "skills/my-skill"). */
-    path: string;
-    /** Display name (e.g. "IDENTITY.md"). */
-    name: string;
-    /** Whether the file/directory exists. */
-    exists: boolean;
-  }>;
-}
-
-export interface WorkspaceFileReadResponse {
-  type: "workspace_file_read_response";
-  path: string;
-  content: string | null;
-  error?: string;
-}
-
-export interface IdentityGetResponse {
-  type: "identity_get_response";
-  /** Whether an IDENTITY.md file was found. When false, all fields are empty defaults. */
-  found: boolean;
-  name: string;
-  role: string;
-  personality: string;
-  emoji: string;
-  home: string;
-  version?: string;
-  assistantId?: string;
-  createdAt?: string;
-  originSystem?: string;
-}
-
-export interface ToolPermissionSimulateResponse {
-  type: "tool_permission_simulate_response";
-  success: boolean;
-  /** The simulated permission decision. */
-  decision?: "allow" | "deny" | "prompt";
-  /** Risk level of the simulated tool invocation. */
-  riskLevel?: string;
-  /** Human-readable reason for the decision. */
-  reason?: string;
-  /** When decision is 'prompt', the data needed to render a ToolConfirmationBubble. */
-  promptPayload?: {
-    allowlistOptions: Array<{
-      label: string;
-      description: string;
-      pattern: string;
-    }>;
-    scopeOptions: Array<{ label: string; scope: string }>;
-    persistentDecisionsAllowed: boolean;
-  };
-  /** Resolved execution target for the tool. */
-  executionTarget?: "host" | "sandbox";
-  /** ID of the trust rule that matched (if any). */
-  matchedTrustRuleId?: string;
-  /** Error message when success is false. */
-  error?: string;
-}
-
-export interface ToolInputSchema {
-  type: "object";
-  properties?: Record<
-    string,
-    {
-      type?: string;
-      description?: string;
-      enum?: string[];
-      [key: string]: unknown;
-    }
-  >;
-  required?: string[];
-}
-
-export interface ToolNamesListResponse {
-  type: "tool_names_list_response";
-  /** Sorted list of all registered tool names. */
-  names: string[];
-  /** Input schemas keyed by tool name. */
-  schemas?: Record<string, ToolInputSchema>;
-}
-
-// --- Domain-level union aliases (consumed by the barrel file) ---
-
-export type _WorkspaceClientMessages =
-  | WorkspaceFilesListRequest
-  | WorkspaceFileReadRequest
-  | IdentityGetRequest
-  | ToolPermissionSimulateRequest
-  | ToolNamesListRequest;
-
-export type _WorkspaceServerMessages =
-  | WorkspaceFilesListResponse
-  | WorkspaceFileReadResponse
-  | IdentityGetResponse
-  | ToolPermissionSimulateResponse
-  | ToolNamesListResponse
-  | IdentityChangedEvent;

package/src/live-voice/ack-phrases.ts

@@ -1,58 +0,0 @@
-import type { LiveVoiceSpokenAckKind } from "./live-voice-metrics.js";
-
-// Short, persona-neutral phrases spoken to hold the floor when the model is
-// slow to produce its first delta. Pure floor-holders:
-// they must never carry content or require domain knowledge, and they stay
-// short (≤ 6 words) so they finish before the real reply's audio arrives.
-const ACK_PHRASES: readonly string[] = [
-  "One sec — let me think.",
-  "Let me look into that.",
-  "Give me a moment.",
-  "Hmm, let me check.",
-  "Just a moment.",
-];
-
-// Tool-flavored variant spoken the moment a turn starts tool use (a
-// guaranteed-slow turn). Same rules as ACK_PHRASES: persona-neutral, no
-// domain content, ≤ 6 words.
-const TOOL_ACK_PHRASES: readonly string[] = [
-  "Let me check that.",
-  "Looking that up now.",
-  "Let me pull that up.",
-  "One moment, checking.",
-  "Give me a second here.",
-];
-
-const PHRASES_BY_KIND: Record<LiveVoiceSpokenAckKind, readonly string[]> = {
-  first_delta: ACK_PHRASES,
-  tool_use: TOOL_ACK_PHRASES,
-};
-
-// Static fallbacks for an idle-triggered progress narration whose LLM
-// phrasing failed — the one case where prolonged silence is actively harmful.
-// The idle trigger can fire on a slow turn with zero tool activity, so every
-// phrase stays strictly neutral: no claims about running tools or tasks.
-// Same rules as the ack lists: persona-neutral, no domain content, ≤ 8 words.
-// Exported so tests can assert the neutrality invariant against the list.
-export const PROGRESS_FALLBACK_PHRASES: readonly string[] = [
-  "Still on it — one moment.",
-  "Still thinking this through.",
-  "Almost there — thanks for waiting.",
-];
-
-// Deterministic rotation through a phrase list: callers hold a nonnegative
-// monotonic counter, so consecutive picks vary while tests stay reproducible.
-function pickPhrase(phrases: readonly string[], counter: number): string {
-  return phrases[counter % phrases.length];
-}
-
-export function pickAckPhrase(
-  kind: LiveVoiceSpokenAckKind,
-  counter: number,
-): string {
-  return pickPhrase(PHRASES_BY_KIND[kind], counter);
-}
-
-export function pickProgressPhrase(counter: number): string {
-  return pickPhrase(PROGRESS_FALLBACK_PHRASES, counter);
-}

package/src/plugins/defaults/memory/retrieval-budget.ts

@@ -1,29 +0,0 @@
-export interface RecallBudgetInput {
-  estimatedPromptTokens: number;
-  maxInputTokens: number;
-  targetHeadroomTokens: number;
-  minInjectTokens: number;
-  maxInjectTokens: number;
-}
-
-/**
- * Compute per-turn memory recall injection budget from context headroom.
- *
- * The result is always clamped into [minInjectTokens, maxInjectTokens].
- */
-export function computeRecallBudget(input: RecallBudgetInput): number {
-  const maxInput = Math.max(0, Math.floor(input.maxInputTokens));
-  const estimatedPrompt = Math.max(0, Math.floor(input.estimatedPromptTokens));
-  const headroomTarget = Math.max(0, Math.floor(input.targetHeadroomTokens));
-  const minInject = Math.max(1, Math.floor(input.minInjectTokens));
-  const maxInject = Math.max(minInject, Math.floor(input.maxInjectTokens));
-
-  const available = maxInput - estimatedPrompt - headroomTarget;
-  return clamp(Math.floor(available), minInject, maxInject);
-}
-
-function clamp(value: number, min: number, max: number): number {
-  if (value < min) return min;
-  if (value > max) return max;
-  return value;
-}

package/src/plugins/defaults/memory/v3/__tests__/gate-flag.test.ts

@@ -1,69 +0,0 @@
-/**
- * Tests for `gate-flag.ts` — the on/off predicate gating the memory-v3
- * per-turn injection gate. The assistant flag resolver is mocked so the test
- * asserts the composition: the predicate forwards `MEMORY_V3_INJECTION_GATE_FLAG`
- * and the config to `isAssistantFeatureFlagEnabled` and ANDs its boolean with
- * the `memory.v3.gate.enabled` config kill-switch.
- */
-import { beforeEach, describe, expect, mock, test } from "bun:test";
-
-import type { AssistantConfig } from "../../../../../config/schema.js";
-
-// The resolver is mocked BEFORE importing the module under test so the import
-// observes the spy at load time. The specifier is resolved relative to THIS
-// test file (one level deeper than gate-flag.ts's own import path).
-const isAssistantFeatureFlagEnabled = mock(
-  (_flag: string, _config: AssistantConfig): boolean => false,
-);
-
-mock.module("../../../../../config/assistant-feature-flags.js", () => ({
-  isAssistantFeatureFlagEnabled,
-}));
-
-const { isMemoryV3InjectionGateEnabled, MEMORY_V3_INJECTION_GATE_FLAG } =
-  await import("../gate-flag.js");
-
-// The predicate reads only `memory.v3.gate.enabled` from the config.
-const cfgWithGateEnabled = (enabled: boolean): AssistantConfig =>
-  ({ memory: { v3: { gate: { enabled } } } }) as AssistantConfig;
-
-describe("gate-flag", () => {
-  beforeEach(() => {
-    isAssistantFeatureFlagEnabled.mockReset();
-  });
-
-  test("constant is the kebab-case flag id", () => {
-    expect(MEMORY_V3_INJECTION_GATE_FLAG).toBe("memory-v3-injection-gate");
-  });
-
-  test("flag on + config enabled → true, resolver called with the flag id + config", () => {
-    isAssistantFeatureFlagEnabled.mockReturnValue(true);
-
-    const cfg = cfgWithGateEnabled(true);
-    expect(isMemoryV3InjectionGateEnabled(cfg)).toBe(true);
-    expect(isAssistantFeatureFlagEnabled).toHaveBeenCalledTimes(1);
-    expect(isAssistantFeatureFlagEnabled).toHaveBeenCalledWith(
-      MEMORY_V3_INJECTION_GATE_FLAG,
-      cfg,
-    );
-  });
-
-  test("returns false when the resolver returns false", () => {
-    isAssistantFeatureFlagEnabled.mockReturnValue(false);
-
-    const cfg = cfgWithGateEnabled(true);
-    expect(isMemoryV3InjectionGateEnabled(cfg)).toBe(false);
-    expect(isAssistantFeatureFlagEnabled).toHaveBeenCalledWith(
-      MEMORY_V3_INJECTION_GATE_FLAG,
-      cfg,
-    );
-  });
-
-  test("config kill-switch: flag on + gate.enabled false → false", () => {
-    isAssistantFeatureFlagEnabled.mockReturnValue(true);
-
-    expect(isMemoryV3InjectionGateEnabled(cfgWithGateEnabled(false))).toBe(
-      false,
-    );
-  });
-});