@jsonstudio/rcc 0.90.367 → 0.90.701

package/docs/INSTRUCTION_MARKUP.md

@@ -56,7 +56,34 @@ RouteCodex 支持在用户消息中写入“指令标记”，用于影响 Virtu
 
 > clock servertool 的详细行为与持久化说明见 `docs/SERVERTOOL_CLOCK_DESIGN.md`。
 
-## 4) provider 路由指令
+## 4) heartbeat（tmux 客户端巡检唤醒）
+
+Heartbeat 仅绑定到 tmux session，并且只接受 on/off：
+
+```text
+<**hb:on**>
+<**hb:off**>
+```
+
+语义：
+
+- `hb:on`：立即开启 heartbeat；后续由服务端按 15 分钟周期尝试唤醒对应 tmux 客户端。
+- `hb:off`：关闭该 tmux session 的 heartbeat。
+- 只处理**最新一条 user 消息**中的 heartbeat 指令；历史消息中的 heartbeat 标记不会重复生效。
+- 结束时间不从指令输入，而是从目标工作目录下 `HEARTBEAT.md` 头部标签读取：
+
+```text
+Heartbeat-Until: 2026-03-16T23:00:00+08:00
+```
+
+- 若未写 `Heartbeat-Until`，表示无截止时间。
+- Heartbeat 仅在以下两个条件同时满足时才会真正注入：
+  - 当前 tmux 绑定范围内没有活动中的请求
+  - 客户端已断开或心跳过期
+
+> Heartbeat 的 tmux/持久化/注入设计见 `docs/session-client-daemon-design.md`。
+
+## 5) provider 路由指令
 
 ### 允许列表（whitelist）
 
@@ -86,4 +113,3 @@ RouteCodex 支持在用户消息中写入“指令标记”，用于影响 Virtu
 ```text
 <**!tab.gpt-5.2**>
 ```
-

package/docs/design/heartbeat-session-execution-state.md

@@ -0,0 +1,227 @@
+# Heartbeat Session Execution State 设计
+
+## 目标
+
+为 heartbeat 注入建立一个 **tmux-scoped 执行状态真源**，在注入前判断目标 tmux 当前是否仍在执行任务；若仍在执行，则跳过本次 heartbeat，避免打扰。
+
+本设计重点解决两个问题：
+
+1. 不能再把 `client alive` 误判为 `session busy`。
+2. 不能只看 executor 生命周期；流式 SSE 仍在输出时，必须视为仍在执行。
+
+---
+
+## 已确认可用的现有信号
+
+### 1. tmux / session 绑定
+
+来源：
+
+- `src/server/runtime/http-server/executor-metadata.ts`
+- `src/server/runtime/http-server/session-scope-resolution.ts`
+
+当前可解析：
+
+- `tmuxSessionId`
+- `sessionId`
+- `conversationId`
+- `workdir`
+- `clientType`
+
+### 2. request 开始/结束
+
+来源：
+
+- `src/server/runtime/http-server/request-executor.ts`
+- `src/server/runtime/http-server/request-activity-tracker.ts`
+
+可用作“请求已发出”的信号，但 **不能单独作为流式执行态真源**，因为 `onRequestEnd` 发生在 executor `finally`，早于 SSE 真正结束。
+
+### 3. SSE 生命周期与 finish_reason
+
+来源：
+
+- `src/server/handlers/handler-response-utils.ts`
+- `src/server/utils/finish-reason.ts`
+
+当前已经能识别：
+
+- SSE stream start
+- SSE end
+- client close
+- finish / terminal event
+- `finish_reason`
+
+这些信号目前主要停留在响应层日志，没有形成 tmux-scoped 共享运行态。
+
+### 4. daemon alive / registry
+
+来源：
+
+- `src/server/runtime/http-server/session-client-registry.ts`
+
+当前能说明：
+
+- client daemon 是否仍在线
+- 最近 heartbeat / inject 时间
+
+但这 **不能说明 pane 当前是否 busy**。
+
+---
+
+## 核心判断原则
+
+### A. 流式请求优先
+
+若目标 tmux 当前存在 **未关闭的 SSE**，则直接判定为 **正在执行**，heartbeat 必须跳过。
+
+### B. 非流式请求看最近 request/response 时间线
+
+若最近一条事件是 request，且还未观察到对应 response：
+
+- 在 timeout 窗口内：视为仍在等待响应，应跳过 heartbeat
+- 超过 timeout：视为大概率已超时/断连，不应无限跳过 heartbeat
+
+### C. 最近一条事件是 response 时，看 finish_reason
+
+- `finish_reason=stop` 且之后没有新 request：视为空闲
+- `finish_reason!=stop`：进入短暂 grace 窗口，避免刚结束 tool_calls / length 时立刻误判为空闲
+
+---
+
+## 建议新增的真源模块
+
+建议新增：
+
+- `src/server/runtime/http-server/session-execution-state.ts`
+
+按 `tmuxSessionId` 维护最近执行态，至少记录：
+
+- `state`
+- `lastRequestId`
+- `lastRequestAtMs`
+- `lastRequestWasStream`
+- `openSseCount`
+- `lastSseOpenAtMs`
+- `lastSseCloseAtMs`
+- `lastResponseAtMs`
+- `lastFinishReason`
+- `lastTerminalAtMs`
+- `lastClientCloseBeforeTerminal`
+
+---
+
+## 状态机
+
+### 状态
+
+- `IDLE`
+- `WAITING_RESPONSE`
+- `STREAMING_OPEN`
+- `POST_RESPONSE_GRACE`
+- `STALED`
+- `UNKNOWN`
+
+### 含义
+
+#### `IDLE`
+
+当前可注入 heartbeat。
+
+#### `WAITING_RESPONSE`
+
+已收到 request，但尚未观察到 response 完成；在 timeout 窗口内应跳过 heartbeat。
+
+#### `STREAMING_OPEN`
+
+流式请求的 SSE 仍未关闭；这是“仍在执行”的最高优先级判定。
+
+#### `POST_RESPONSE_GRACE`
+
+刚结束一个非 `stop` 的响应，例如 `tool_calls` / `length`，短时间内仍可能紧接下一轮请求。
+
+#### `STALED`
+
+最近一条是 request，但超过 timeout 仍无 response，视为超时或断连，不应再无限跳过 heartbeat。
+
+#### `UNKNOWN`
+
+当前没有足够的新执行态数据；只允许降级到 tmux pane heuristic，不允许把 daemon alive 直接当作 busy。
+
+---
+
+## 事件与转移
+
+建议统一记录这些事件：
+
+- `REQUEST_STARTED`
+- `SSE_OPENED`
+- `SSE_CLOSED`
+- `RESPONSE_COMPLETED`
+- `RESPONSE_CLIENT_CLOSED`
+- `RESPONSE_ERROR`
+- `TIMEOUT_EXPIRED`
+
+主要转移：
+
+- `IDLE -> WAITING_RESPONSE`：收到 request
+- `WAITING_RESPONSE -> STREAMING_OPEN`：流式响应开始
+- `WAITING_RESPONSE -> IDLE`：收到非流式终态且 `finish_reason=stop`
+- `WAITING_RESPONSE -> POST_RESPONSE_GRACE`：收到非流式终态且 `finish_reason!=stop`
+- `WAITING_RESPONSE -> STALED`：超时无响应
+- `STREAMING_OPEN -> IDLE`：SSE 正常结束且 `finish_reason=stop`
+- `STREAMING_OPEN -> POST_RESPONSE_GRACE`：SSE 正常结束且 `finish_reason!=stop`
+- `STREAMING_OPEN -> STALED`：client close / 异常结束且没有正常终态
+- `POST_RESPONSE_GRACE -> WAITING_RESPONSE`：grace 期间来了新 request
+- `POST_RESPONSE_GRACE -> IDLE`：grace 到期且没有新 request
+- `STALED -> WAITING_RESPONSE`：之后出现新的 request
+
+---
+
+## Heartbeat skip 决策顺序
+
+推荐优先级：
+
+1. **存在未关闭 SSE** → `skip`
+2. **最新是 request，且仍在 timeout 窗口内** → `skip`
+3. **最新是 response，`finish_reason=stop`，且之后无新 request** → `allow`
+4. **最新是 request，但已超时无响应** → `allow`
+5. **状态不足** → fallback 到 tmux pane heuristic
+
+明确禁止：
+
+- 仅因为 `registry.hasAliveTmuxSession()` 为真，就直接判定 busy
+
+---
+
+## 与现有 heartbeat 的关系
+
+当前 heartbeat skip 逻辑里已有：
+
+- tmux 存活检查
+- request inflight 检查
+- client daemon alive 检查
+- tmux pane heuristic fallback
+
+新方案应调整为：
+
+1. execution-state tracker 为主真源
+2. tmux pane heuristic 仅作 fallback
+3. daemon alive 只表示“在线”，不表示“忙”
+
+---
+
+## 落地顺序建议
+
+1. 新增 `session-execution-state.ts`
+2. 在 request start 路径写入 `REQUEST_STARTED`
+3. 在 JSON response 完成路径写入 `RESPONSE_COMPLETED`
+4. 在 SSE 路径写入 `SSE_OPENED / SSE_CLOSED / RESPONSE_COMPLETED / RESPONSE_CLIENT_CLOSED`
+5. heartbeat 决策改为优先读取 execution-state tracker
+6. 在缺少状态时再回退到 tmux pane heuristic
+
+---
+
+## 备注
+
+该设计上线后，只能对 **上线后的新请求** 逐步建立准确执行态。对上线前已在跑的老 session，短期内仍需依赖 tmux pane heuristic 兜底。

package/docs/reports/apply-patch-errorsamples-classification.md

@@ -0,0 +1,144 @@
+# apply_patch 错误样本分类表（2026-03-18）
+
+## 范围
+
+本表基于两个样本集合：
+
+1. **近期主样本集**
+   - `~/.rcc/errorsamples/client-tool-error/chat_process.req.stage2.semantic_map.apply_patch-*.json`
+   - 按最近 **200** 条与最近 **500** 条做统计
+2. **历史回归样本集**
+   - `~/.rcc/errorsamples/apply-patch-regression/*.json`
+
+## 结论摘要
+
+- 近期高频错误几乎全部是 `apply_patch_verification_failed`，而且高度集中在 **4 类**。
+- 当前主因不是执行器随机失效，而是 **模型 patch 心智错误**：
+  1. 把 GNU diff 头混进 `*** Begin Patch` 块；
+  2. 把 merge/conflict 标记直接塞进 patch；
+  3. 继续硬写 GNU 行号上下文（`@@ -51,7 +51,9 @@`）；
+  4. 少量真实的 `expected lines not found`。
+- 历史回归样本还保留两类基础错误：
+  - `unsupported_patch_format`
+  - `empty_add_file_block`
+
+---
+
+## 近期样本统计
+
+### 最近 200 条 apply_patch 专属样本
+
+来源：
+
+- `~/.rcc/errorsamples/client-tool-error/chat_process.req.stage2.semantic_map.apply_patch-*.json`
+
+统计结果：
+
+| 分类 | 数量 |
+|---|---:|
+| conflict_markers_or_merge_chunks | 72 |
+| gnu_line_number_context_not_found | 55 |
+| mixed_gnu_diff_inside_begin_patch | 55 |
+| expected_lines_not_found | 18 |
+
+### 最近 500 条 JSON 错误样本中的 apply_patch 相关分类
+
+来源：
+
+- `~/.rcc/errorsamples/**/*.json`
+
+统计结果：
+
+| 分类 | 数量 |
+|---|---:|
+| conflict_markers_or_merge_chunks | 75 |
+| gnu_line_number_context_not_found | 57 |
+| mixed_gnu_diff_inside_begin_patch | 49 |
+| expected_lines_not_found | 19 |
+
+备注：
+
+- 最近 500 条 JSON 样本里，**未看到**新的 `exec_command_nested_apply_patch_warning` 成为主流；说明这轮主要问题已从“工具选错”转向“patch 形状错误”。
+
+---
+
+## 历史回归样本统计
+
+来源：
+
+- `~/.rcc/errorsamples/apply-patch-regression/*.json`
+
+统计结果：
+
+| 分类 | 数量 |
+|---|---:|
+| unsupported_patch_format | 2 |
+| empty_add_file_block | 1 |
+
+---
+
+## 分类表
+
+| 分类 | 典型 matchedText / 症状 | 当前数量 | 更可能的根因 | 建议修复层 | 优先级 | 建议动作 |
+|---|---|---:|---|---|---|---|
+| `conflict_markers_or_merge_chunks` | `Expected update hunk to start with a @@ context marker, got: '======='` | 72 / 75 | 模型把 merge/conflict chunk 或非 patch 文本直接塞进 `Update File` | **prompt/guidance** + request-path guard | P0 | 强化“禁止 `=======/<<<<<<</>>>>>>>`”与“`Update File` 必须有 `@@` hunk”；必要时在 request-path 直接拦截冲突标记并回写 guard reason |
+| `gnu_line_number_context_not_found` | `Failed to find context '-114,6 +114,7 @@'` | 55 / 57 | 模型误以为必须精确写 GNU 行号上下文；或基于旧内容生成 patch | **prompt/guidance** + post-failure retry policy | P0 | 明确“可以用 `@@` + 上下文，不必强写 GNU 行号”；失败后要求重读文件并缩小唯一上下文 |
+| `mixed_gnu_diff_inside_begin_patch` | `invalid hunk at line 2, '--- a/src/server/index.ts' is not a valid hunk header` | 55 / 49 | 模型把 internal `*** Begin Patch` 与 GNU diff 头混用 | **prompt/guidance** + validator normalization（可选） | P0 | 明确“二选一，严禁混用”；可评估是否把 `*** Begin Patch` 包裹的 GNU diff 头再做一层自动剥离修复 |
+| `expected_lines_not_found` | `Failed to find expected lines in ...` | 18 / 19 | 真正的上下文不匹配：文件已变化、上下文过大、不够唯一 | **runtime retry guidance** | P1 | 出错后强制重读最新文件，再用更小且唯一的上下文；必要时把单次 patch 拆小 |
+| `unsupported_patch_format` | `Update File` 后直接跟 frontmatter / 正文，没有 hunk | 2（历史） | 模型不理解 internal grammar；把 `Update File` 当“全文替换” | **tool guidance** + validator reason hint | P1 | 强化最小合法模板，显式提示“没有 `@@` hunk 的 `Update File` 会被拒绝” |
+| `empty_add_file_block` | `*** Add File: ...` 后没有任何 `+` 行 | 1（历史） | 模型误以为空文件 Add File 合法 | **tool guidance** + validator reason hint | P2 | 明确 Add File 必须至少包含一行 `+内容`；若真要空文件，应改为 shell `touch` 之类的受控策略或专门工具，而不是空 patch |
+| `exec_command_nested_apply_patch_warning` | `Warning: apply_patch was requested via exec_command` | 非近期主流，历史存在 | 工具选错：模型把 `apply_patch` 当 shell 命令 | **rewrite/guard** | P2 | 维持现有 rewrite/guard；后续做样本分类时单独追踪是否再次升高 |
+
+---
+
+## 已完成的前置收敛
+
+本轮已先修正工具引导文案，避免继续制造同类错误：
+
+- `src/config/system-prompts/codex-cli.txt`
+  - 去掉“apply_patch 不好用就换 Node/Python 脚本”的弱引导
+- `sharedmodule/llmswitch-core/src/guidance/index.ts`
+  - 明确 **Begin Patch / GNU diff 二选一，禁止混用**
+  - 增加最小合法模板
+  - 禁止 conflict markers / 裸 frontmatter 作为 `Update File` body
+- `sharedmodule/llmswitch-core/src/guidance/CCR_TOOL_GUIDE.md`
+  - 同步补齐以上规则
+- `sharedmodule/llmswitch-core/src/conversion/hub/process/chat-process-clock-tool-schemas.ts`
+  - 工具描述补齐 FREEFORM 与“不混用”要求
+
+---
+
+## 建议修复顺序
+
+### 第一步：先修 prompt / guidance
+
+优先原因：
+
+- 当前占比最高的三类错误都属于**模型生成 patch 形状错误**
+- 不先收紧提示词，后面即使增强 validator，也只是在被动收垃圾输入
+
+### 第二步：补 request-path / validator 的 reason 编码与 guard
+
+优先看两点：
+
+1. 对 conflict markers 的 request-path 早拦截
+2. 对“mixed GNU diff inside Begin Patch”评估是否做自动修复，还是继续 fail-fast
+
+### 第三步：为 `expected_lines_not_found` 设计统一 retry 策略
+
+这是最像“正常 patch 失败”的一类，应通过：
+
+- 重读文件
+- 缩小上下文
+- 拆小 patch
+
+来恢复，而不是继续堆更宽松的语法容错。
+
+---
+
+## 下一步实施建议
+
+1. 在 `apply_patch` 工具引导里增加**可复制模板**的实际注入验证
+2. 给 `tool-governor` / request-path 增加 **conflict-marker 明确分类 reason**
+3. 决定是否为“`*** Begin Patch` + GNU diff 头混用”加一层**自动正规化**
+4. 把本表对应到测试矩阵，新增每类错误至少 1 条回归用例

package/docs/session-client-daemon-design.md

@@ -289,6 +289,98 @@ Examples:
 
 Validation rule: if recurrence is present but invalid/missing required fields, marker scheduling is skipped (marker text remains unchanged).
 
+## 16. Heartbeat (tmux client re-activation)
+
+Heartbeat is a specialized tmux-only wake-up loop, separate from normal clock tasks.
+
+### 16.1 Contract
+
+- Marker protocol:
+  - `<**hb:on**>`
+  - `<**hb:off**>`
+- Binding scope: **tmux session only**
+- Enable semantics: `hb:on` takes effect immediately; no start time input is supported.
+- End time source: target workdir `HEARTBEAT.md` header tag
+
+```text
+Heartbeat-Until: 2026-03-16T23:00:00+08:00
+```
+
+- If `Heartbeat-Until` is absent, heartbeat has no deadline.
+- If tmux scope is unavailable when parsing `hb:on/off`, directive is stripped from the latest user message but no state is written.
+
+### 16.2 Delivery loop
+
+- Persistence root: `<sessions-root>/heartbeat/*.json`
+  - If `ROUTECODEX_SESSION_DIR` points to a port-scoped bucket like `~/.rcc/sessions/127.0.0.1_5520`, heartbeat state must still resolve to the parent sessions root (`~/.rcc/sessions/heartbeat/*.json`).
+  - This keeps heartbeat persistence bound to the **tmux session domain**, not to one server port bucket.
+- Daemon tick: every **15 minutes**
+- Each due heartbeat attempts tmux injection only when both are true:
+  1. no active in-flight request is bound to that tmux scope
+  2. session-client daemon is disconnected / heartbeat stale
+
+- If either condition is false:
+  - skip this tick
+  - record skip reason
+  - never fail the main system path
+
+### 16.3 Injected fixed prompt
+
+Heartbeat injection is tmux-only and uses one fixed prompt generated from the heartbeat module:
+
+1. read `HEARTBEAT.md` in the current workdir
+2. inspect whether previous delivery is complete and whether more fixes are needed
+3. update `DELIVERY.md`
+4. call `review`
+5. continue execution instead of stop-only reporting
+
+### 16.4 Workdir and cleanup rules
+
+- Workdir truth source for heartbeat is the **current tmux pane path**.
+- If tmux workdir cannot be resolved, heartbeat skips without fallback to server cwd.
+- If tmux session is dead, persisted heartbeat state is removed during startup cleanup / runtime scan.
+- If `Heartbeat-Until` is expired, heartbeat state is auto-disabled.
+- Current cleanup risk review:
+  - startup/reaper cleanup may remove **heartbeat state / registry records / conversation bindings / tool-state metadata** when a tmux session is judged dead or stale;
+  - current runtime path does **not** directly kill tmux sessions during stale-heartbeat cleanup;
+  - therefore the main risk today is **metadata false-positive cleanup** (functional amnesia), not tmux process termination.
+
+### 16.4.1 Cleanup entrypoint matrix (single source of truth)
+
+| Entrypoint | Trigger | Removes daemon record | Removes tmux-scoped mappings / stop-message / task metadata | Kills tmux |
+|---|---|---:|---:|---:|
+| `cleanupSessionStorageOnStartup()` | server start | Yes, for dead or stale records | Yes, **only** for tmux judged dead; stale-but-alive tmux now keeps mappings/tool-state | No |
+| `SessionReaper.cleanupDeadTmuxSessions()` | periodic reaper | Yes, when tmux probe says dead | Yes | Not in current runtime wiring |
+| `SessionReaper.cleanupStaleHeartbeats()` | periodic reaper | Yes, stale daemon record only | **No** for tmux that is still alive; stale-but-live tmux scope is preserved | No |
+| `POST /daemon/session/cleanup mode=dead_tmux` | admin/manual | Yes | Yes | No (`allowManagedTermination=false`) |
+| `POST /daemon/session/cleanup mode=stale_heartbeat` | admin/manual | Yes, stale daemon record only | **No** for tmux that is still alive | No |
+| `clock-runtime-hooks` cleanup | tmux inject path confirms dead/missing tmux | N/A | Yes, clears routing/stop-message scope for dead tmux | No |
+| `executor-metadata` / `client-injection-flow` unbind | request-time dead tmux / inject failure cleanup | N/A | Yes, scoped unbind only | No |
+| `heartbeat/session-store.removeHeartbeatState()` | heartbeat daemon confirms dead tmux or legacy migration cleanup | N/A | heartbeat state only | No |
+
+Rules:
+
+- **Dead tmux** can clear tmux-scoped metadata.
+- **Stale daemon heartbeat alone** must only remove daemon registration, and must not clear the still-alive tmux scope.
+- Any path that wants to terminate tmux must be explicitly wired and separately reviewed; current runtime path does not do this.
+- Host-side cleanup判定唯一真源：`src/server/runtime/http-server/tmux-scope-cleanup-policy.ts`
+
+### 16.5 Failure policy
+
+- Heartbeat failure is **non-fatal**:
+  - record state / log
+  - do not fail request handling
+  - do not affect provider correctness or servertool followup correctness
+
+### 16.6 Review invariants
+
+- Heartbeat must not auto-chain server-side review flows.
+- It only injects prompt text telling the model to call `review`.
+- Existing `review_flow` semantics remain unchanged:
+  - `clientInjectOnly: true`
+  - same flow id / followup contract
+  - no hidden service-side review reenter
+
 ### 15.3 Cleanup policy (tmux vs conversation session)
 
 Two session domains are intentionally separated:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jsonstudio/rcc",
-  "version": "0.90.367",
+  "version": "0.90.701",
   "description": "Multi-provider OpenAI proxy server with anthropic/responses/chat support (release)",
   "type": "module",
   "main": "dist/index.js",
@@ -22,8 +22,7 @@
     "README.md",
     "LICENSE",
     "docs/",
-    "configsamples/",
-    "vendor/"
+    "configsamples/"
   ],
   "bundledDependencies": [],
   "engines": {
@@ -81,7 +80,7 @@
     "verify:e2e-gemini-followup-sample": "node scripts/verify-e2e-gemini-followup-sample.mjs",
     "install:global": "./scripts/install-global.sh",
     "install:release": "./scripts/install-release.sh",
-    "release:rcc": "npm run publish:rcc",
+    "release:rcc": "npm run pack:rcc",
     "audit:tool-text": "node scripts/audit-tool-text.mjs",
     "start:bg": "bash scripts/run-bg.sh -- 'node dist/index.js'",
     "start:fg": "bash scripts/run-fg-gtimeout.sh 12 -- 'node dist/index.js'",
@@ -103,6 +102,9 @@
     "debug:responses:lmstudio:tool": "tsx scripts/tools-dev/responses-debug-client/src/index.ts --file scripts/tools-dev/responses-debug-client/payloads/tool.json --baseURL ${LMSTUDIO_BASEURL:-http://127.0.0.1:1234/v1}",
     "capture:responses:lmstudio": "node scripts/capture-responses-sse.mjs --file scripts/tools-dev/responses-debug-client/payloads/tool.json",
     "llmswitch:ensure": "node scripts/ensure-llmswitch-mode.mjs",
+    "llmswitch:link": "node scripts/link-llmswitch.mjs",
+    "llmswitch:unlink": "node scripts/link-llmswitch.mjs unlink",
+    "llmswitch:link:global": "node scripts/link-global-llms-local.mjs --require-target",
     "dry-run:responses-provider": "node scripts/tests/responses-provider-dry-run.mjs",
     "start:verify:fg": "node scripts/start-verify.mjs --mode fg --timeout 90",
     "rc-config": "node scripts/rc-config.mjs",
@@ -158,6 +160,7 @@
     "@ai-sdk/anthropic": "^3.0.58",
     "@ai-sdk/openai": "^3.0.41",
     "@anthropic-ai/sdk": "^0.65.0",
+    "@jsonstudio/llms": "0.6.4291",
     "@lmstudio/sdk": "^1.5.0",
     "@radix-ui/react-switch": "^1.2.6",
     "@types/socket.io": "^3.0.1",
@@ -173,15 +176,14 @@
     "helmet": "^7.0.0",
     "lmstudio": "^0.0.32",
     "open": "^9.1.0",
-    "openai": "^6.9.1",
+    "openai": "^5.23.0",
     "ora": "^9.0.0",
     "playwright-core": "^1.49.0",
     "rcc-basemodule": "^0.2.7",
     "rcc-debugcenter": "^0.1.6",
     "rcc-errorhandling": "^1.0.10",
     "socket.io": "^4.8.1",
-    "zod": "^3.23.8",
-    "tiktoken": "^1.0.22"
+    "zod": "^3.23.8"
   },
   "optionalDependencies": {
     "@jsonstudio/llms-engine": "^0.3.0"

package/scripts/analyze-thinking-keywords.mjs

@@ -10,7 +10,7 @@
 import fs from 'fs/promises';
 import os from 'os';
 import path from 'path';
-import { DEFAULT_THINKING_KEYWORDS } from '../sharedmodule/llmswitch-core/dist/router/virtual-router/default-thinking-keywords.js';
+import { DEFAULT_THINKING_KEYWORDS } from '@jsonstudio/llms';
 
 const HOME = os.homedir();
 const CHAT_DIR = path.join(HOME, '.routecodex', 'codex-samples', 'openai-chat');

package/scripts/ci/repo-sanity.mjs

@@ -27,7 +27,7 @@ function listRootEntries() {
 
 function isForbiddenRootFile(p) {
   const base = path.posix.basename(p);
-  const allow = new Set(['AGENTS.md', 'README.md', 'MEMORY.md', 'task.md']);
+  const allow = new Set(['AGENTS.md', 'README.md', 'MEMORY.md', 'HEARTBEAT.md', 'DELIVERY.md', 'task.md']);
   if (allow.has(base)) return false;
   if (/^test-.*\.(mjs|js|ts|py)$/i.test(base)) return true;
   if (/^debug-.*\.(mjs|js|ts)$/i.test(base)) return true;
@@ -66,37 +66,43 @@ function isForbiddenTrackedPath(p) {
 
 function checkRootLayout() {
   // Fixed top-level layout. Adding new root entries requires an explicit policy change.
-  const allowed = new Set([
-    'eslint.config.js',
-    '.beads',
-    '.github',
-    '.gitattributes',
-    '.gitignore',
-    'AGENTS.md',
-    'README.md',
-    'MEMORY.md',
-    'config',
-    'configsamples',
-    'dist',
-    'docs',
-    'jest.config.js',
-    'memory',
-    'node_modules',
-    'package',
-    'package-lock.json',
-    'package.json',
-    'rcc',
-    'samples',
-    'scripts',
-    'sharedmodule',
-    'src',
-    'task.md',
-    'tests',
-    'tmp',
-    'tsconfig.jest.json',
-    'tsconfig.json',
-    'vendor',
-  ]);
+ const allowed = new Set([
+   'eslint.config.js',
+   '.beads',
+   '.github',
+   '.gitattributes',
+   '.gitignore',
+   'AGENTS.md',
+   'HEARTBEAT.md',
+   'DELIVERY.md',
+   'README.md',
+   'MEMORY.md',
+   'config',
+   'configsamples',
+   'dist',
+   'docs',
+   'jest.config.js',
+   'memory',
+   'node_modules',
+   'package',
+   'package-lock.json',
+   'package.json',
+   'rcc',
+   'samples',
+   'scripts',
+   'sharedmodule',
+   'src',
+   'task.md',
+   'tests',
+   'tmp',
+   'tsconfig.jest.json',
+   'tsconfig.json',
+   'vendor',
+   'CACHE.md',
+   'botpy.log',
+   'clock.md',
+   'models',
+ ]);
 
   const rootEntries = listRootEntries();
   const unexpected = rootEntries.filter((name) => !allowed.has(name));