fix(runtime): race/timeout hardening — recall abort, profile backup-swap, sandbox, SQLITE_BUSY

[rainforest888]

fix(offload): Tracing & Token Hardening

拆分自 #391，per YOMXXX review。

修复范围

聚焦 src/offload/ 层：token estimate、local LLM、Opik tracing。不涉及 store、runtime、gateway 层。

具体修复

src/offload/fast-token-estimate.ts — Astral-平面 Token 修正

问题	修复
astral-plane 字符（emoji / CJK extension B，U+10000+）编码为 surrogate pair，原实现把 high surrogate 和 low surrogate 各计为一个 token	high surrogate 检测后跳过低代理（i += 2），修正 ~2× token 高估

src/offload/local-llm/index.ts — L1.5 Fallback 修正

问题	修复
解析失败返回 {taskCompleted: false, ...} — normalizeJudgment 把 false 当有效判断，永远不触发 "LLM 不可用" 重试	改为 {taskCompleted: null, ...}，== null 检查触发重试路径

src/offload/opik-tracer.ts — ESM 兼容 + Trace 截断

问题	修复
ESM 下 require("opik") 为 undefined，tracer 永久静默关闭	改为 createRequire(import.meta.url)
未脱敏 tool 输出（文件内容、环境变量）完整写入 trace，泄露到 Opik backend	统一截断到 2000 字符

验证

• 3 files, +41/-15
• 无 API 变更，无新增依赖
• 与 fix(gateway): harden CORS / Host header / startup host binding #39 / fix(tcvdb): escape session filter literals #232 / fix(offload): keep backend TLS verification enabled #242 / fix(offload): sanitize session storage paths #287 / fix(offload): keep MMD files inside storage dir #288 / fix(offload): sanitize ref and skill paths #289 / fix(offload): invalidate token cache after tool use stripping #347 均不重叠

[Maxwell-Code07]

Thank you for your contribution! We will review your code and get back to you as soon as possible.

[YOMXXX]

Thanks for splitting this runtime hardening work. I verified the PR patch locally by applying it to its base commit and running:

• pnpm test — passed: 4 files, 67 tests
• pnpm build — passed
• git diff --check --cached — passed

However, the recall abort fix is incomplete as a standalone PR. performAutoRecall() now creates an AbortController and passes the signal through searchMemories(), but this PR does not update src/core/store/embedding.ts: EmbeddingCallOptions still has no abortSignal field, and the embedding HTTP request path does not combine or use that signal. Because the object literal uses a conditional spread, TypeScript still builds, but at runtime the extra abortSignal option is ignored by the current embedding services. So the documented behavior — recall timeout aborts the in-flight embedding request — does not actually take effect in this PR by itself.

Please either include the embedding-layer wiring in this PR, or make this PR explicitly depend on/stack after the storage/embedding PR that adds EmbeddingCallOptions.abortSignal and passes it to fetch. Once the abort signal reaches the actual fetch call, the rest of the timeout propagation shape here looks reasonable.