cc-viewer 1.7.22 → 1.8.0

package/src/utils/apiUrl.js

@@ -1,26 +0,0 @@
-// 从 URL 中提取 LAN 访问 token，附加到所有 API 请求 / WebSocket 握手
-const _urlToken = new URLSearchParams(window.location.search).get('token');
-
-// 反向代理子路径部署: 从 <base> 标签或 SSR 注入的全局变量读取 base path，
-// 使 API/WebSocket 等动态请求也能正确路由到代理后端。
-export function getBasePath() {
-  if (typeof window !== 'undefined' && window.__CCV_BASE_PATH__) return window.__CCV_BASE_PATH__;
-  if (typeof document === 'undefined' || !document.querySelector) return '';
-  const base = document.querySelector('base');
-  if (base && base.href) return base.getAttribute('href');
-  return '';
-}
-
-// 把 token 追加到任意 URL（HTTP path 或 ws:// 完整 URL 皆可）。无 token 时原样返回。
-// WS 握手必须也带 token —— 否则启用鉴权后远程「?token=」终端会被 socket.destroy()。
-export function appendToken(url) {
-  if (!_urlToken) return url;
-  const sep = url.includes('?') ? '&' : '?';
-  return `${url}${sep}token=${_urlToken}`;
-}
-
-export function apiUrl(path) {
-  const base = getBasePath();
-  const fullPath = base ? base.replace(/\/$/, '') + path : path;
-  return appendToken(fullPath);
-}

package/src/utils/askFallback.js

@@ -1,21 +0,0 @@
-// Decision helper for ApprovalModal's fallback AskQuestionForm.
-//
-// The Question modal body is normally filled by the transcript tool_use block
-// portaling an AskQuestionForm into the modal's ask slot (see askPortalMatcher.js).
-// When no block portals in — a stale replayed ask whose block is old history, or a
-// fresh ask arriving before transcript ingest — the modal would show an empty body.
-// The fallback renders a form directly from the authoritative pending-ask broadcast.
-//
-// Contract: `slotOccupied` is DOM occupancy of the ask slot (MutationObserver on
-// childList + sync initial read); `graceElapsed` flips true ASK_FALLBACK_GRACE_MS
-// after the ask becomes visible, giving the real portal one commit cycle so fresh
-// asks never flash the fallback before the portaled form mounts.
-
-export const ASK_FALLBACK_GRACE_MS = 120;
-
-export function shouldRenderAskFallback({ isAskActive, slotOccupied, graceElapsed, questions, submitHandler }) {
-  if (!isAskActive || slotOccupied || !graceElapsed) return false;
-  if (!Array.isArray(questions) || questions.length === 0) return false;
-  if (typeof submitHandler !== 'function') return false;
-  return true;
-}

package/src/utils/askOptionDesc.js

@@ -1,55 +0,0 @@
-import { isPlaceholderAskId } from './askPortalMatcher.js';
-
-// AskUserQuestion options[].description is schema-optional; centralize fallback
-// so AskQuestionForm and ChatMessage recap stay aligned.
-
-export function optionAriaLabel(opt) {
-  if (!opt || opt.label == null) return '';
-  return opt.description
-    ? `${opt.label}: ${opt.description}`
-    : String(opt.label);
-}
-
-export function hasOptionDescription(opt) {
-  return Boolean(opt && opt.description);
-}
-
-// Pick the questions the interactive AskUserQuestion card actually renders.
-//
-// The modal body is filled by the inline tool_use block (reconstructed from the log
-// stream) portaling into the modal's askSlot — it does not read pendingAsk.questions
-// (the authoritative copy broadcast over WS ask-hook-pending / sdk-ask-pending, fully
-// parsed server-side before the hook fires) directly. During streaming of a large
-// payload there is a window where the modal is already open but the reconstructed
-// block's input is still partial JSON. Crucially, partial-JSON parsing materializes
-// the outer questions[] array shape before the element content arrives, so the
-// streamed copy can be HOLLOW AT EQUAL LENGTH (e.g. two question objects with empty
-// text/options while big options[].preview strings are still streaming — the
-// 2026-07-04 blank-popup regression; a strictly-longer length heuristic missed it).
-//
-// So: for the currently pending ask (toolId === lastPendingAskId, id-matched), always
-// prefer the authoritative copy. It is complete by construction, and the submit path
-// (handleAskQuestionSubmit in askFlowController) maps answer indices through the same
-// authoritative _askHookQuestions copy — rendering it keeps rendered indices aligned
-// with the mapping array. Historical blocks never match lastPendingAskId and always
-// keep their own streamed questions (history view unchanged).
-//
-// Legacy/no-id servers use placeholder pendingAsk ids ('__ask__', 'ask_<ts>_<rnd>')
-// that can never equal the real tool_use id. There the authoritative copy is only
-// borrowed when the streamed render would otherwise be completely empty — it can fill
-// a blank popup but never override visible content (a stale legacy pendingAsk must
-// not inject a previous ask's questions over a rendered one).
-export function resolveAskQuestions(streamedQuestions, toolId, lastPendingAskId, pendingAsk) {
-  const streamed = Array.isArray(streamedQuestions) ? streamedQuestions : [];
-  if (!pendingAsk || toolId == null || toolId !== lastPendingAskId) {
-    return streamed;
-  }
-  const idMatches = pendingAsk.id === toolId;
-  if (!idMatches && !(isPlaceholderAskId(pendingAsk.id) && streamed.length === 0)) {
-    return streamed;
-  }
-  const authoritative = Array.isArray(pendingAsk.questions) ? pendingAsk.questions : [];
-  if (authoritative.length === 0) return streamed; // defensive: WS handlers guarantee non-empty
-  if (streamed.length > authoritative.length) return streamed; // never shrink (belt-and-braces)
-  return authoritative;
-}

package/src/utils/askPortalMatcher.js

@@ -1,54 +0,0 @@
-/**
- * Portal 决策：判断 inline AskQuestionForm（在 ChatMessage 里渲染的某条 tool_use）
- * 是否应该 createPortal 到 ApprovalModal 的 askSlot。
- *
- * activeAskId 三种合法形态（与 server 端协议绑定，改一边必须改另一边）：
- *
- *   1. `toolu_xxx` — SDK 模式 / 新版 Claude Code 透传的真实 tool_use_id
- *      → 走 strict 匹配：activeAskId === toolId
- *
- *   2. `__ask__` — LEGACY 老 server（pre-Map 协议）的单槽占位
- *      → 走 owner 通配：仅 owner-idx 锁定的那条 ChatMessage（lastPendingAskId === toolId）命中
- *
- *   3. `ask_${ts}_${rnd}` — 老 Claude Code PreToolUse hook payload 不带 tool_use_id 时
- *      server.js 自生成的 fallback id（修复 modal 标题在但内容空白的根因）
- *      → 走 owner 通配：与 __ask__ 同语义
- *
- * 协议锚点：
- *   - server 端 fallback id 生成：server.js（搜索 `ask_${Date.now()}` 定位）
- *   - server 端 LEGACY 占位推送：server.js 推送 ask-hook-pending 事件时 id 为 '__ask__'
- *   - 前端 setState pendingAsk：src/components/chat/ChatView.jsx
- *
- * 改 server 端 fallback id 格式时，必须同步更新此文件的 isFallbackId 检测。
- */
-
-const FALLBACK_ID_PREFIX = 'ask_';
-const LEGACY_PLACEHOLDER_ID = '__ask__';
-
-/**
- * True when the given pending-ask id is a placeholder that can never equal a real
- * tool_use id: the LEGACY single-slot '__ask__' or a server-generated 'ask_<ts>_<rnd>'
- * fallback id. Consumers (e.g. resolveAskQuestions) use this to apply the same
- * owner-wildcard semantics as shouldPortalAskForm on the legacy paths.
- */
-export function isPlaceholderAskId(id) {
-  return id === LEGACY_PLACEHOLDER_ID
-    || (typeof id === 'string' && id.startsWith(FALLBACK_ID_PREFIX));
-}
-
-/**
- * @param {*} activeAskId   ApprovalPortalContext.Consumer 提供的 activeAskId（modal 当前 active ask 的 id）
- * @param {*} toolId        当前 ChatMessage 里 tool_use 块的 id（toolu_xxx）
- * @param {*} lastPendingAskId  ChatMessage 收到的 owner-idx 派生信号；非 owner 永远为 null
- * @returns {boolean} true 表示当前 ChatMessage 应该 portal 到 askSlot
- */
-export function shouldPortalAskForm(activeAskId, toolId, lastPendingAskId) {
-  if (activeAskId == null) return false;
-  // strict：SDK / 新 Claude Code 真实 tool_use_id
-  if (String(activeAskId) === String(toolId)) return true;
-  // owner 通配：__ask__（LEGACY 老 server）∪ ask_*（server fallback）
-  // 必须同时满足 owner-idx 锁定（lastPendingAskId === toolId），否则会让历史所有真实 toolId
-  // 都被通配命中，重现旧的双份 portal bug
-  if (isPlaceholderAskId(activeAskId) && lastPendingAskId === toolId) return true;
-  return false;
-}

package/src/utils/autoApproveOptions.js

@@ -1,27 +0,0 @@
-// 自动审批档位唯一事实源 —— 全部消费点共用同一组档位,防止各处字面量发散:
-//   1. TerminalPanel 终端工具栏四芒星快捷菜单（权限/Plan 两行级联档位）
-//   2. ChatInputBar 对话输入框四芒星快捷菜单（隐藏终端时,同款两行）
-//   3. AppHeader 设置抽屉的权限/Plan 两个 Select
-//   4. Mobile 设置面板的权限/Plan 两个 Select
-// 三态语义(持久化于 preferences.autoApproveSeconds / approvalModal.planAutoApproveSeconds):
-//   0   = 关闭(手动审批)
-//   > 0 = 倒计时该秒数后自动批准
-//   -1  = 免审批(AUTO_APPROVE_INSTANT):请求到达即放行,从源头绕过审批面板
-// 本模块不依赖 helpers.js(它带 .svg?raw 等 Vite 专属 import),保持 node --test 可直接引用。
-export const AUTO_APPROVE_INSTANT = -1;
-
-export const PERM_AUTO_APPROVE_OPTIONS = [0, 3, 5, 10, AUTO_APPROVE_INSTANT];
-export const PLAN_AUTO_APPROVE_OPTIONS = [0, 10, 30, 60, AUTO_APPROVE_INSTANT];
-
-// 单个档位值 -> 显示文案;t 由调用方注入,避免本模块依赖前端 i18n。
-// 档位之外的历史值(如 Plan 旧 3/5)同样落在 `${v}s` 分支正常显示。
-export function autoApproveValueLabel(v, t) {
-  if (v === AUTO_APPROVE_INSTANT) return t('ui.permission.autoApprove.instant');
-  if (!v) return t('ui.permission.autoApprove.off');
-  return `${v}s`;
-}
-
-// 档位数组 -> antd Select options
-export function autoApproveSelectOptions(values, t) {
-  return values.map(v => ({ value: v, label: autoApproveValueLabel(v, t) }));
-}

package/src/utils/avatarAnimationPostPass.js

@@ -1,49 +0,0 @@
-import React from 'react';
-import { shouldAnimateTeammateAvatar, pickAvatarAnimationTargets } from './teammateAvatars';
-
-/**
- * Avatar animation loading strategy — post-pass applied at the end of
- * ChatView.buildAllItems, once every item (and the out-of-band Last Response
- * timestamp) is known. Teammate rows animate their one-shot draw-in only when
- * within the 60s window of the newest item's timestamp; the single newest
- * teammate row always animates ("welcome flourish" on historic logs). Losers
- * get cloneElement({ animateAvatar: false }) — winners keep their original
- * element reference so cached elements skip reconciliation entirely.
- *
- * The flags are frozen per build: the window is measured against the newest
- * item's timestamp, NOT wall clock (do not "fix" with Date.now()); they
- * refresh whenever new data rebuilds the list.
- *
- * @param {Array} items - freshly built ChatMessage element array; mutated in place
- * @param {string|null} lastResponseTs - session.entryTimestamp of the Last
- *   Response block, which lives OUTSIDE items but must count toward "newest"
- * @returns {Array} the same array, with stale teammate rows cloned to static
- */
-export function applyAvatarAnimationTargets(items, lastResponseTs = null) {
-  const scanEntries = items.map((item) => ({
-    ts: item?.props?.timestamp,
-    isTeammateAvatar: isTeammateAvatarItem(item?.props),
-  }));
-  if (lastResponseTs) scanEntries.push({ ts: lastResponseTs, isTeammateAvatar: false });
-  const { latestMs, newestTeammateIdx } = pickAvatarAnimationTargets(scanEntries);
-  if (newestTeammateIdx === -1) return items;
-  for (let i = 0; i < items.length; i++) {
-    if (!scanEntries[i].isTeammateAvatar) continue;
-    const animate = i === newestTeammateIdx ||
-      shouldAnimateTeammateAvatar(items[i].props.timestamp, latestMs);
-    if (!animate) items[i] = React.cloneElement(items[i], { animateAvatar: false });
-  }
-  return items;
-}
-
-// Mirrors ChatMessage.render()'s THREE teammate-avatar branches:
-// renderSubAgentChatMessage (role 'sub-agent-chat'), renderSubAgentMessage
-// (role 'sub-agent' — currently never constructed, covered defensively), and
-// renderTeammateMessage (role 'teammate-message'). If ChatMessage gains a new
-// teammate-avatar branch, add it here — rows missed by this predicate default
-// to animated forever.
-export function isTeammateAvatarItem(props) {
-  if (!props) return false;
-  return ((props.role === 'sub-agent-chat' || props.role === 'sub-agent') && props.isTeammate)
-    || props.role === 'teammate-message';
-}

package/src/utils/builtinPresets.js

@@ -1,18 +0,0 @@
-/**
- * 内置预置快捷方式。
- *
- * builtinId 跨版本不变，用于追踪用户的删除/编辑。
- * teamName / description 是 i18n key，渲染时通过 t() 解析。
- */
-export const BUILTIN_PRESETS = [
-  {
-    builtinId: 'codereview-5',
-    teamName: 'ui.preset.codeReview5.name',
-    description: 'ui.preset.codeReview5.desc',
-  },
-  // 历史遗留 builtinId 已连同 i18n key 一并删除（用户反馈不常用）：
-  //   - 'scout-regiment'  / ui.preset.scoutRegiment.*
-  //   - 'codereview-2'    / ui.preset.codeReview2.*
-  // 若老用户的 preset 列表里已保存这些条目，i18n key 缺失时 t() 会回显原始 key，
-  // 视觉上难看但不崩；用户可在管理弹窗里手动删除。
-];

package/src/utils/clearCheckpoint.js

@@ -1,7 +0,0 @@
-// Re-export shell — the implementations moved VERBATIM to the shared client-safe
-// module server/lib/session-boundary.js in wire-v2 step S1 so the server-side
-// conversation router (S2+) and the client use ONE source of truth for session
-// boundaries (docs/refactor/WIRE_FORMAT_V2_PLAN.md). Existing client imports of
-// './clearCheckpoint.js' keep working through this shell; new code should import
-// from server/lib/session-boundary.js directly.
-export { isPostClearCheckpoint, isCompactContinuation, isSessionBoundary } from '../../server/lib/session-boundary.js';

package/src/utils/commandValidator.js

@@ -1,45 +0,0 @@
-/**
- * File and command validation utilities.
- */
-
-const IMAGE_EXTS = new Set(['png', 'jpg', 'jpeg', 'gif', 'svg', 'bmp', 'ico', 'icns', 'webp', 'avif']);
-
-export function isImageFile(path) {
-  const ext = (path || '').split('.').pop().toLowerCase();
-  return IMAGE_EXTS.has(ext);
-}
-
-/**
- * Regex matching Bash commands that may mutate filesystem or git state.
- * 命中任一即触发文件浏览器与 git 面板自动刷新（ToolFileChangeController 的 Bash 路径依赖）。
- *
- * 覆盖类别：
- * - delete：rm（含 rm -rf）、rmdir（删空目录）、unlink（POSIX 单文件删除）、find ... -delete
- * - create/move：mkdir、mv、cp、touch、ln
- * - metadata：chmod、chown
- * - package/archive：npm/yarn/pnpm install/uninstall、pip install、tar、unzip、curl -o、wget
- * - redirect write：> 与 >>（排除 2>、>= 等由 [^>]>(?!>)/>> 处理）
- * - git mutating：checkout/reset/stash/merge/rebase/cherry-pick/restore/clean/rm
- *
- * 设计取舍（trade-off）：
- *   \b 单词边界不能区分"作为命令"还是"作为参数/字面量"，因此 `echo unlink` 之类
- *   会被命中。文件浏览器额外刷新成本极低（一次 GET），宁可多刷不漏刷。
- *
- * find -delete 子表达式 `\bfind\b[^|;&\n]*-delete\b` 限定单条命令内，
- * 避免 `grep find . | echo "-delete"` 之类的跨管道/分号误匹配。
- *
- * @example
- *   isMutatingCommand('rm -rf node_modules')           // true
- *   isMutatingCommand('find . -name "*.log" -delete')  // true
- *   isMutatingCommand('git status')                    // false
- *   isMutatingCommand('echo hello')                    // false
- */
-const MUTATING_CMD_RE = /\b(rm|rmdir|unlink|mkdir|mv|cp|touch|chmod|chown|ln|git\s+(checkout|reset|stash|merge|rebase|cherry-pick|restore|clean|rm)|npm\s+(install|uninstall|ci)|yarn\s+(add|remove)|pnpm\s+(add|remove|install)|pip\s+install|tar|unzip|curl\s+-[^\s]*o|wget)\b|\bfind\b[^|;&\n]*-delete\b|[^>]>(?!>)|>>/;
-
-/**
- * @param {string} cmd  Bash 命令字符串
- * @returns {boolean}   true 表示命令可能修改文件树或 git 状态
- */
-export function isMutatingCommand(cmd) {
-  return MUTATING_CMD_RE.test(cmd);
-}

package/src/utils/contextRaw.js

@@ -1,18 +0,0 @@
-import { stripPrivateKeys } from './helpers';
-
-// Context 标签页「原文」视图的文本组装（唯一实现，ContextTab 不内联第二份）。
-// 口径与 DetailPanel Request/Response 标签 text 模式一致：stripPrivateKeys 剥掉
-// 前端注入的 _ 前缀键（如 _timestamp）→ 字符串原样输出（不加引号包裹）、其余
-// JSON.stringify 两空格缩进。
-// turn 节点输出 [userMsg, ...systemMsgs, assistantMsg] 原始消息切片（rawSystem 为
-// 折叠进本 turn 的 mid-conversation system 消息，按会话顺序位于 user 与 assistant 之间）；
-// 当前轮次 assistant 若由 response 覆盖（见 ContextTab turns useMemo），rawAssistant 即完整 response body。
-export function buildContextItemRawText(item) {
-  if (!item) return '';
-  const raw = item.isTurn
-    ? [item.rawUser, ...(Array.isArray(item.rawSystem) ? item.rawSystem : []), item.rawAssistant].filter(Boolean)
-    : item.raw;
-  if (raw == null) return '';
-  const clean = typeof raw === 'object' ? stripPrivateKeys(raw) : raw;
-  return typeof clean === 'string' ? clean : JSON.stringify(clean, null, 2);
-}

package/src/utils/contextSidebarNavigation.js

@@ -1,16 +0,0 @@
-export function getContextSidebarArrowNavigation({
-  currentId,
-  visibleIds = [],
-  key,
-}) {
-  if (key !== 'ArrowUp' && key !== 'ArrowDown') return null;
-
-  const currentIndex = visibleIds.findIndex((id) => id === currentId);
-  const delta = key === 'ArrowUp' ? -1 : 1;
-
-  if (currentIndex >= 0) {
-    return visibleIds[currentIndex + delta] ?? null;
-  }
-
-  return null;
-}

package/src/utils/contextTurns.js

@@ -1,117 +0,0 @@
-// Context tab message parsing + turn grouping (extracted from ContextTab.jsx so the
-// pairing logic is unit-testable — JSX modules cannot be imported by the test harness).
-
-export function parseContentBlocks(content) {
-  if (content == null) return [];
-
-  if (typeof content === 'string') {
-    const trimmed = content.trim();
-    return trimmed ? [{ type: 'markdown', text: trimmed }] : [];
-  }
-
-  if (Array.isArray(content)) {
-    const blocks = [];
-    for (const block of content) {
-      if (!block) continue;
-      if (block.type === 'text') {
-        const trimmed = (block.text || '').trim();
-        if (trimmed) blocks.push({ type: 'markdown', text: trimmed });
-      } else if (block.type === 'tool_use') {
-        blocks.push({
-          type: 'tool_use',
-          name: block.name || 'unknown',
-          id: block.id || '',
-          input: block.input ?? {},
-        });
-      } else if (block.type === 'tool_result') {
-        const inner = parseResultContent(block.content);
-        blocks.push({
-          type: 'tool_result',
-          tool_use_id: block.tool_use_id || '',
-          is_error: block.is_error,
-          content: inner,
-        });
-      } else if (block.type === 'thinking') {
-        const text = block.thinking || '';
-        if (text.trim()) blocks.push({ type: 'thinking', text });
-      } else if (block.type === 'image') {
-        blocks.push({ type: 'json', label: 'image', data: block });
-      } else {
-        blocks.push({ type: 'json', label: block.type || 'block', data: block });
-      }
-    }
-    return blocks;
-  }
-
-  return [{ type: 'json', label: 'content', data: content }];
-}
-
-export function parseResultContent(content) {
-  if (content == null) return [];
-  if (typeof content === 'string') {
-    const trimmed = content.trim();
-    return trimmed ? [{ type: 'markdown', text: trimmed }] : [];
-  }
-  if (Array.isArray(content)) {
-    return content.flatMap((c) => {
-      if (!c) return [];
-      if (c.type === 'text') {
-        const trimmed = (c.text || '').trim();
-        return trimmed ? [{ type: 'markdown', text: trimmed }] : [];
-      }
-      return [{ type: 'json', label: c.type || 'block', data: c }];
-    });
-  }
-  return [{ type: 'json', label: 'content', data: content }];
-}
-
-export function extractPreviewText(content) {
-  if (typeof content === 'string') return content.slice(0, 60).replace(/\n/g, ' ');
-  if (Array.isArray(content)) {
-    for (const block of content) {
-      if (block?.type === 'text' && block.text?.trim()) {
-        return block.text.trim().slice(0, 60).replace(/\n/g, ' ');
-      }
-    }
-  }
-  return '';
-}
-
-// 注意：非 user 开头的消息（首条 assistant、连续 assistant 等）不进任何 turn，
-// 「原文」视图与解析视图同口径，同样不展示这些消息。
-// Mid-conversation `role:"system"` messages (mid-conversation-system beta) may sit
-// between the user message and its assistant reply; they are folded into the turn
-// (systemBlocks/rawSystem) so the assistant pairing is not broken. Only messages
-// with role === 'system' are skipped when locating the paired assistant — any
-// other unknown role still ends the turn, matching the old strict-adjacency rule.
-export function groupMessagesIntoTurns(messages) {
-  const turns = [];
-  let i = 0;
-  while (i < messages.length) {
-    const userMsg = messages[i];
-    if (userMsg?.role !== 'user') { i++; continue; }
-    let j = i + 1;
-    const systemMsgs = [];
-    while (messages[j]?.role === 'system') { systemMsgs.push(messages[j]); j++; }
-    const assistantMsg = messages[j]?.role === 'assistant' ? messages[j] : null;
-    turns.push({
-      id: `turn__${i}`,
-      isTurn: true,
-      turnIndex: turns.length,
-      timestamp: userMsg._timestamp || null,
-      assistantTimestamp: assistantMsg?._timestamp || null,
-      userBlocks: parseContentBlocks(userMsg?.content),
-      systemBlocks: systemMsgs.length
-        ? systemMsgs.map((m) => ({ blocks: parseContentBlocks(m.content), timestamp: m._timestamp || null }))
-        : null,
-      assistantBlocks: assistantMsg ? parseContentBlocks(assistantMsg.content) : null,
-      // 原始消息引用：供「原文」视图无损输出（解析 blocks 是单向的，不可逆）
-      rawUser: userMsg,
-      rawSystem: systemMsgs.length ? systemMsgs : null,
-      rawAssistant: assistantMsg,
-      preview: extractPreviewText(userMsg?.content),
-    });
-    i = assistantMsg ? j + 1 : i + 1;
-  }
-  return turns;
-}

package/src/utils/displayScaleHelper.js

@@ -1,47 +0,0 @@
-/**
- * Display-scale (整体显示大小 / Chrome 式缩放) 的纯计算工具。
- * 无 DOM / React 依赖,便于单测。比例以「整数百分比」表示(100 = 原始大小)。
- */
-
-// 预设档位,贴近 Chrome 的缩放档位。
-export const DISPLAY_SCALE_PRESETS = [50, 67, 75, 80, 90, 100, 110, 125, 150, 175, 200];
-
-const MIN_SCALE = DISPLAY_SCALE_PRESETS[0];
-const MAX_SCALE = DISPLAY_SCALE_PRESETS[DISPLAY_SCALE_PRESETS.length - 1];
-
-/**
- * 把任意输入(可能来自手改 preferences.json / 旧数据)夹到 [50,200] 并吸附到最近的预设档位。
- * 平局时取较大档位。非法输入回退到 100。
- * @param {number|string} pct
- * @returns {number} 一个合法的预设值
- */
-export function snapToPreset(pct) {
-  const n = Number(pct);
-  if (!Number.isFinite(n)) return 100;
-  const clamped = Math.max(MIN_SCALE, Math.min(MAX_SCALE, n));
-  let best = DISPLAY_SCALE_PRESETS[0];
-  let bestDist = Infinity;
-  for (const p of DISPLAY_SCALE_PRESETS) {
-    const d = Math.abs(p - clamped);
-    // `<=` 让平局时取后出现(更大)的档位
-    if (d <= bestDist) {
-      bestDist = d;
-      best = p;
-    }
-  }
-  return best;
-}
-
-/**
- * 在预设档位上前进/后退一格(用于 Cmd/Ctrl +/- 快捷键)。
- * 先把当前值吸附到档位,再按方向移动一格,两端夹紧。
- * @param {number|string} current 当前比例
- * @param {number} dir +1 放大 / -1 缩小
- * @returns {number} 新的预设值
- */
-export function stepPreset(current, dir) {
-  const snapped = snapToPreset(current);
-  const idx = DISPLAY_SCALE_PRESETS.indexOf(snapped);
-  const nextIdx = Math.max(0, Math.min(DISPLAY_SCALE_PRESETS.length - 1, idx + Math.sign(dir)));
-  return DISPLAY_SCALE_PRESETS[nextIdx];
-}

package/src/utils/effectiveModel.js

@@ -1,17 +0,0 @@
-// Extracted from helpers.js so pure session modules (sessionMerge/sessionManager) and node:test
-// can import it without pulling helpers' Vite-only svg imports; helpers.js re-exports it to keep
-// existing import paths unchanged (same pattern as autoApproveOptions.js).
-
-/**
- * Resolve the effective model name for a log request entry, preferring the
- * server-reported model in `response.body.model` (authoritative under proxy
- * hot-switch) over the client-supplied `body.model`. Returns null when both
- * are missing — callers should fall back to a sensible default.
- *
- * KEEP IN SYNC: server/lib/context-watcher.js getContextSizeForModel reuses
- * this precedence for its entry path — changing the priority here must be
- * mirrored there (and vice versa).
- */
-export function getEffectiveModel(request) {
-  return request?.response?.body?.model || request?.body?.model || null;
-}