@turmind/halo 0.1.9 → 0.2.0

package/bundled-docs/plans/issue-session-deep-nesting.md

@@ -1,208 +0,0 @@
-# Deep Session Nesting — Investigation & Fixes
-
-## Current state of session tools
-
-### Tool list
-
-Agent-accessible session tools are defined in `session-manager.ts:437-673`, 9 in total:
-
-| Tool | Purpose |
-|---|---|
-| `start_session` | Create a child session, run asynchronously, auto-report on completion |
-| `query_session` | Send a message to an existing session — run immediately if idle, queue if busy |
-| `stop_session` | Stop a session, set `stoppedAt`; recoverable via `query_session` or a user message |
-| `archive_session` | Cascade soft-delete a subtree, set `archivedAt`; not recoverable |
-| `interrupt_session` | Interrupt and immediately re-run with a new message |
-| `session_list` | List the current session's children and their status |
-| `get_session_output` | Read a child session's output text |
-| `list_agents` | List delegatable agents |
-| `query_agent` | Inspect an agent's config and AGENT.md |
-
-### start_session flow
-
-`session-manager.ts:440-485`
-
-1. Validate `agent_id` exists and isn't default
-2. `createSession(agentId, parentId=currentSessionId)` → write SQLite + memory map + emit `context`
-3. Emit `agent_start` (frontend shows sub-agent starting)
-4. **Async** `runSession(childId, message)` — the tool returns immediately without blocking the parent turn
-5. Attach a one-shot `.then()`: when the child session's first runSession resolves:
-   - emit `agent_done`
-   - `querySession(parentId, childId, result.slice(0, 2000))` forwards the result to the parent
-
-### query_session flow
-
-`session-manager.ts:497-529` (tool) + `1401-1452` (core method)
-
-1. Emit `agent_start` (frontend initialises the sub-session log)
-2. `sm.querySession(targetId, sourceId, message, onComplete)`:
-   - target idle → `runSession` runs immediately
-   - target busy → message goes to `target.messageQueue`, drained by `drainQueue`
-3. `onComplete`: after the target finishes → emit `agent_done` + `querySession` back to source
-
-### stop_session flow
-
-`session-manager.ts:571-588` (tool) + `1377-1399` (core method)
-
-1. `abortController.abort('stop')` cancels the LLM call
-2. Await promise completion
-3. Clear `messageQueue` + `pendingUserMessages`
-4. `repairConversationMessages`
-5. `releaseSession` (persist + drop from memory)
-6. DB write `stoppedAt = Date.now()`
-
-Stop is recoverable: `query_session` or a user message clears `stoppedAt` and returns the session to idle. `listSessions` shows `status: 'stopped'`.
-
-### archive_session flow
-
-`session-manager.ts` (tool) + core method `archiveSessionTree`
-
-1. Recursively walk DB to find every descendant session
-2. For each: DB write `archivedAt`; `archiveSession` (abort → await promise → clear queues → drop from map)
-3. Return count archived
-
-Difference vs stop: archive cascades the whole subtree + sets `archivedAt` (not recoverable); stop only stops one and sets `stoppedAt` (recoverable).
-
-### Event routing
-
-`session-manager.ts:214-222` `emitEvent` does three things:
-1. Append to `.events.jsonl` (persistent audit log)
-2. `reduceIntoUIState` (update in-memory UIState + save `.json`)
-3. Push via `eventListeners` to the frontend (WS)
-
-Event routing uses `findRootSessionId` (`session-manager.ts:178-196`): walk up the parentId chain to the root, then use the root's listener to send.
-
-### Session lifecycle
-
-- **idle**: `promise === null`, waiting for input
-- **running**: `promise !== null`, inside an LLM or tool call
-- **stopped**: `stoppedAt` is set, recoverable via `query_session` or a user message
-- **archived**: `archivedAt` is set, not recoverable
-
-Transitions:
-- idle → running: `sendUserMessage` / `runSession` / `querySession`
-- running → idle: turn finishes + empty queue → finally sets `promise = null`
-- idle → stopped: `stopSession` or `tryReportToParent` (auto-report marks done)
-- stopped → idle: `querySession` / `sendUserMessage` clears `stoppedAt`
-- any → archived: `archiveSessionTree`
-
----
-
-## Deep nesting problems (16-layer scenario)
-
-### Problem 1 (fatal): auto-report chain breaks beyond 2 levels
-
-`start_session`'s `.then()` is bound to the **first** runSession promise of the child — it's one-shot.
-
-Three-layer example:
-```
-L1 start_session → L2    .then() bound to L2's runSession promise
-L2's agent decides to delegate → start_session → L3
-L2's first turn completes → runSession resolves → L1's .then() fires
-  → result = "I have delegated to L3" (garbage intermediate info)
-  → querySession to L1 (user receives useless report)
-
-L3 completes → auto-report to L2 → L2 handles result
-  → but L2 → L1's .then() has already fired
-  → L2's new result has nowhere to go
-```
-
-Result: **the real work result only propagates one level; it never reaches the user.**
-
-### Problem 2: sub-agents can't find their parent
-
-The session tools don't expose the parent session ID. An agent can't proactively `query_session` its parent. System auto-report is the only upward channel — and it fires only once.
-
-### Problem 3: `findRootSessionId` is O(depth) DB lookup
-
-Every `emitEvent` walks the parentId chain up to the root. When intermediate layers have been released from memory by `releaseSession`, each level hits SQLite.
-
-At layer 16, each event (stream, tool_call, tool_result, …) walks 16 levels. Dozens of events per turn × 16 = hundreds of DB lookups.
-
-### Problem 4: stale session references
-
-`start_session` at line 467 captures the parent session object:
-```typescript
-const session = sm.sessions.get(sessionId)
-```
-When the parent session's turn completes, `releaseSession → sessions.delete()`. The new object built by `ensureSession` is a different instance. `.then()`'s `session?.interruptedSessionIds` operates on the now-dead old object.
-
-### Problem 5: no depth limit
-
-No nesting check — pathological agent behaviour can nest infinitely until OOM or rate-limit blowout.
-
-### Problem 6: concurrent rate limits
-
-During the report phase, multiple layers wake up simultaneously via `querySession`, hit Bedrock concurrently, trigger ThrottlingException. Linear backoff + many sessions retrying simultaneously → cascading failure.
-
----
-
-## Fix plan (implemented)
-
-### Hierarchical session_id + level-by-level bubbling
-
-**session_id format**: hierarchy encoded with `>` separators. `createSession` appends a new segment for child ids: `{parentId}>{new_segment}`.
-
-```
-root:    sid_abc
-child:   sid_abc>sid_def
-grand:   sid_abc>sid_def>sid_ghi
-```
-
-- Depth = `id.split('>').length`; exceeding `config.session.maxNestingDepth` (default 16) rejects `start_session`
-- `findRootSessionId` = `id.split('>')[0]`, O(1)
-
-**Auto-report mechanism**: `tryReportToParent(session)` method, called inside `runSession`'s finally after `promise = null`.
-
-Report conditions:
-1. `parentId !== null` (not root)
-2. DB query `WHERE parent_id = session.id AND stopped_at IS NULL AND archived_at IS NULL` finds no active children
-3. `!session.skipRelease` (not in an interrupt flow)
-
-All three → set `stoppedAt` + emit `agent_done` + `querySession(parentId, id, result)`.
-
-**Removed**:
-- Manual `.then()` reports in `start_session` / `interrupt_session` / `query_session`
-- The `interruptedSessionIds` field
-- `onComplete` callbacks (`runSession`, `querySession`, `QueuedMessage`)
-
-### Rate-limit retry (done)
-
-Exponential backoff + jitter: 2s → 4s → 8s → 16s… capped at 60s. `maxRetries` defaults to 5.
-
-### Duplicate child guard (done, mitigation)
-
-In `start_session`'s callback, before `createSession` we query DB: if a non-stopped-non-archived child session with the same parentId + same agentId already exists, reject with a hint.
-
-Mitigates the case where conversation repair makes the LLM re-delegate the same agent. Not a full fix.
-
----
-
-## Still open: conversation repair erases delegation history (likely root cause)
-
-**Status**: suspected issue, needs more verification
-
-**Symptom**: in 16-layer depth tests, some layers branch — one parent session creates multiple same-agent children.
-
-**Analysis**:
-
-`conversation-repair.ts` Phase 2 and Phase 2b can't distinguish "structural damage" from "valid tool-call history" when repairing a damaged message array.
-
-Flow:
-1. `runAgentTurn` hits a Bedrock error (e.g. `unexpected tool_use_id found in tool_result`)
-2. Calls `repairConversationMessages`
-3. Phase 2 (lines 72-119): scan assistant→user pairs, drop entries where tool_use ID and tool_result ID don't match
-4. Phase 2b (lines 122-151): drop user tool_result with no corresponding assistant tool_use
-5. `start_session`'s record (tool_use + tool_result) gets treated as "damage" and swept up
-6. On LLM retry the conversation history has no delegation trace → a new `start_session` call creates a duplicate child
-
-**Impact chain**:
-- Direct: branching child sessions at the same level, abnormal tree structure
-- Indirect: `session_list` shows multiple running same-agent children; `get_session_output` reading different children confuses the LLM
-- Orphaned branches can't complete their lifecycle, stuck in running/idle forever
-
-**Fix direction**: make conversation repair protect session management tool calls (`start_session`, `query_session`, …) from being deleted.
-
-**To verify**:
-- Does this also happen at shallower depths (2-3), or only at deep nesting with high retry rates?
-- Is the duplicate-child guard enough of a mitigation in practice?

package/bundled-docs/plans/launch-plan.md

@@ -1,111 +0,0 @@
-# Halo 对外推广计划 (Go-to-Market)
-
-> 起草人:halo仔 · 状态:草案,待咚咚总拍板方向
-> 一句话:**先把"门面 + 弹药"修好,再开渠道。子弹没上膛之前别扣扳机。**
-
----
-
-## 0. 先认清现状 —— 你的底气比你以为的足
-
-**底气(别人砸钱都买不到的):**
-- 作者自用一个半月**无暗伤**,另有 2-3 人**持续留存几个月** → 这是 PMF(产品-市场契合)的雏形,已被真实验证了一小块。多少项目 Show HN 几百 star、三天 DAU 归零,你刚好反过来:没声量,但有留存。
-- **独门视觉牌**:粒子脸(Express Self)+ 像素城市(Halo City)。绝大多数 agent 工具就是个丑终端,你有天生适合短视频传播的东西。像素城市那张图质量已经够发。
-
-**短板(要么修、要么坦诚):**
-- 无声量、单人维护、无自动化测试 → README 的 "Status & Limitations" 已经很诚实,**保留**,这反而是加分项(海外开发者吃这套)。
-- **门面有空截图硬伤**(见第 3 节 P0)。
-
----
-
-## 1. 定位:先解决"一句话"
-
-2025 年 agent 工具卷到飞起(Cursor / Claude Code / Devin / Manus…),路人第一反应一定是"又一个?凭啥用你"。必须一句话把差异点砸进去。
-
-**Halo 真正的差异点(按稀缺度排序):**
-1. **多渠道指挥** —— 微信/TG/飞书/Slack 都能直接指挥,不绑死在 IDE 里。**这个位几乎没人占。**
-2. **自托管 + 多模型 + 自己的密钥边界** —— 数据不出你的机器。
-3. **一切皆文件、无隐藏记忆** —— 对控制欲强的开发者是真卖点。
-4. **视觉化的 agent 运行时** —— 看得见每个 agent 在干啥。
-
-**英文定位候选(待选):**
-- A. *"Your AI dev team — command it from any chat app, running entirely on your own machine."*
-- B. *"A self-hosted AI agent team you command from Slack, Telegram, or WeChat — not locked inside an IDE."*
-- C. *"The multi-agent dev workspace that lives in your terminal and your chat apps — not someone else's cloud."*
-
-> ⚠️ 最终选哪句,**取决于那 2-3 个留存用户最离不开的功能**。他们用脚投票留下的那个点,大概率就是对外该喊的话。所以这句先别急着定死。
-
----
-
-## 2. 公用弹药库 —— 所有渠道都要用,先做这个
-
-不管最后走哪条渠道,这三样是公用子弹,先做绝不亏:
-
-| 弹药 | 说明 | 负责 |
-|---|---|---|
-| **① 一句话定位** | 见上,等留存用户反馈后敲定 | 咚咚总拍板 |
-| **② 60 秒 demo 视频/GIF** | 押视觉牌:粒子脸说话 + 像素城市里 agent 跑动 + 多渠道手机指挥。**这是 Show HN / PH 的钩子,比任何文字都强** | halo仔出脚本,咚咚总录 |
-| **③ README 改版** | 换掉空截图 hero(见 P0),把"多渠道 + 视觉"提到最前 | halo仔 |
-| ④ landing page(可选) | 一个能在线瞄一眼的页面,降低门槛 | 二期 |
-
----
-
-## 3. 门面急救清单
-
-### 🔴 P0 —— 推广前必须修
-
-- **README 首图(`assets/workspace.jpg`)是一个空工作区!** Canvas 写着 "Open a file to start editing",Chat 写着 "Start a conversation" —— 整个项目最重要的第一张图,却展示了一个**什么都没发生的空壳**。这是第一印象的致命伤。
-  - **改法**:换成"火力全开"的截图 —— agent 正在思考、sub-agent 在跑、文件树有改动标记、代码在 Canvas 里、对话有来有回。让人一眼看到"这玩意儿在干活"。
-
-### 🟡 P1 —— 强烈建议
-- 体检报告(deep-executor 正在跑)回来后补充。
-
----
-
-## 4. 渠道排期 —— 别贪多,挑水塘蹲
-
-### 主线:海外开发者(自托管多 agent 的人群密度最高)
-
-| 顺序 | 渠道 | 说明 | 你要做的 |
-|---|---|---|---|
-| 首发 | **Show HN**(Hacker News) | 全球科技圈最猛的水塘。"Show HN: 给大家看看我做了个啥"。一旦上首页,几小时几万开发者刷到,免费 | 发帖后头 1-2 小时回评论 |
-| 跟进 | **Reddit** r/LocalLLaMA · r/selfhosted | 自托管 AI 的高浓度人群,正好是你的目标用户 | 同上 |
-| 持续 | **Twitter/X** build-in-public | 持续发 demo 短视频,养长期关注 | 每周 1-2 条 |
-| 拿牌 | **Product Hunt** | 等有点声量后冲,拿个 badge | 单独排期 |
-
-### 第二梯队:AWS(不是拉用户,是背书 + 省钱)
-
-> 咚咚总的直觉对一半:**写软文夸 Halo 发 AWS 博客确实戆居**(读者来学技术不是来找产品,转化≈0)。但 AWS 渠道的真实价值在别处:
-
-- **`AWS Activate` / startup credits** —— 跟推广无关,纯省钱。**今天就该申请,顺手的事,无脑做。**
-- **`community.aws` 技术稿**(自助发布、门槛低)—— 写"如何解决一个通用难题",Halo 只当案例出场。你真有干货:Bedrock 上做 prompt caching、用 Nova grounding 取代传统 web search、多 provider 的 agent runtime 抽象、自托管多 agent 协作系统怎么搭。立技术口碑 + SEO 长尾 + 以后见客户/投资人的背书。
-- ⚠️ 注意:你的产品命脉之一**就是 Bedrock**(默认引擎 Claude on Bedrock、GPT 走 bedrock-mantle、联网搜索用 Nova)。所以"我做的东西不用 AWS"这个前提不成立 —— AWS 内容有得写,只是别放第一发。
-
-### 可选:国内
-即刻 · V2EX · 掘金(长文讲架构)· 小红书/B站(发视觉 demo)· 公众号。
-
----
-
-## 5. 两周执行排期(建议)
-
-**第一周 —— 上膛**
-- [ ] 敲定一句话定位(等留存用户反馈)
-- [ ] 修 P0:换 README hero 图
-- [ ] 录 60 秒 demo 视频(halo仔出脚本)
-- [ ] README 改版(多渠道 + 视觉提前)
-- [ ] 顺手申请 AWS Activate credits
-- [ ] 处理体检报告里的 P0/P1
-
-**第二周 —— 开火**
-- [ ] Show HN 首发(配 demo 视频)
-- [ ] 同步 Reddit r/LocalLLaMA + r/selfhosted
-- [ ] 启动 Twitter build-in-public
-- [ ] community.aws 技术稿(可延后)
-
----
-
-## 6. 待咚咚总拍板
-
-1. **主线方向**:开源涨 star(build in public)还是商业化接客户?→ 建议先走开源,默认采纳。
-2. **主战场**:海外为主?→ 建议海外(人群密度),国内顺带。
-3. **那 2-3 个留存用户是啥人、最离不开哪个功能?** → 这个直接决定定位语怎么写。
-4. demo 视频你想自己录,还是要 halo仔先把素材/分镜全做好?

package/bundled-docs/plans/md-and-agent-refactor.md

@@ -1,197 +0,0 @@
-# Refactor plan: drop is_default + working_dir + MD-load simplification + externalise system prompts
-
-**Status**: shipped (2026-04 / 2026-05). All phases A–F landed: `priority` field replaced `is_default`, `agent_sessions.working_dir` column added, MD-loader simplified (INDEX.md root-only, INSTRUCTIONS.md stacks per directory level), system prompts externalised under `prompts/{bootstrap,all,root}/`. This doc is kept as a design log — see the reference state in [design/prompt-system.md](../design/prompt-system.md).
-**Filed**: 2026-04-27
-
-This doc preserves every design decision, rationale, and trade-off so we can rapidly recover context if it's lost.
-
----
-
-## Background
-
-Halo uses `is_default` as a synonym for "root agent", which has bad knock-on effects:
-- Prompt injection logic, tool behaviour, and UI default selection all bind to this field
-- User-defined "direct-chat agents" can't receive USER.md, PLATFORM_KNOWLEDGE, or other root-only prompts
-- Hard-coded system prompts (BOOTSTRAP / TOOL_GUIDELINES / PLATFORM_KNOWLEDGE / ORCHESTRATOR_GUIDELINES) live in source — users wanting to customise must edit source
-- INDEX.md reserves a subdirectory-loading interface but never calls it (dead code)
-- INSTRUCTIONS.md only supports two layers (global + project); no subdirectory granularity
-
----
-
-## Core decisions
-
-### 1. Drop `is_default`
-
-- The `is_default` field is deprecated. YAML uses `priority: number` instead — default 0, higher first.
-- The `default` agent seed stays, `priority: 99` (remains the initial default selection).
-- All `isDefault`-semantic branches become `!parentId` ("root agent") checks.
-- `list_agents` no longer filters `default`; agents can spawn themselves (same agent_id, independent session instances).
-- Delete protection: at least 1 agent in the global scope; workspace scope can be emptied.
-- UI default selection: sort by `priority desc, name asc`, pick the first.
-- Remove the "default" badge.
-
-### 2. Add `working_dir`
-
-- New `working_dir` argument on `start_session`
-- Accepts absolute or workspace-relative paths
-- Default: `workspaceRoot` (project root)
-- Enforce resolved path within workspace (reject traversal)
-- Non-existent directory → reject spawn
-- `agent_sessions` gets a `workingDir TEXT` column (null = project root)
-- On resume, DB → `buildAgentInstance`
-
-### 3. INDEX.md — project-root-only
-
-- `<ws>/.halo/INDEX.md` is the sole source, injected for every agent
-- Sub-directory `INDEX.md` files are **not auto-loaded**; user / agent uses `file_read` on demand
-- Drop `subDirIndex` logic in `resolveMdPaths` (dead code)
-- Rationale: multi-level INDEX is an untested requirement; users reference sub-INDEX from the root INDEX and the agent reads on demand (progressive disclosure)
-
-### 4. INSTRUCTIONS.md — stacked by level
-
-- From global → workspaceRoot → every level of the workingDir path, load `.halo/INSTRUCTIONS.md`
-- Injection order: outer → inner (global first, workingDir last)
-- Each block labelled with its path relative to workspaceRoot (root itself uses `.`)
-- Rationale: INSTRUCTIONS encode "how to work here"; directory depth is a natural scope, more specific wins
-
-### 5. Externalise system prompts
-
-The four hard-coded constants (BOOTSTRAP / TOOL_GUIDELINES / PLATFORM_KNOWLEDGE / ORCHESTRATOR_GUIDELINES) move to:
-
-```
-~/.halo/global/prompts/
-├── bootstrap/   ← only injected for root agent + needsBootstrap
-├── all/         ← injected for every agent
-└── root/        ← only injected for root agent
-```
-
-- Subdirectory categorisation decides injection scope
-- Inside each subdirectory, every `.md` is concatenated by filename ascending
-- User extends by dropping MDs in the relevant directory (e.g. `prompts/all/my-style-guide.md`)
-- Startup seed: first run writes four defaults; existing files preserved
-- Live-read (every `buildAgentInstance`)
-- Missing: warn + skip (don't break the server)
-- `tool-guidelines.ts` remains the seed source + hard-coded fallback
-- **Global only**; workspace doesn't override
-- **Language**: seed content stays English (already is); UI copy stays English; section headers stay English; Chinese only in developer docs
-
----
-
-## Target directory layout
-
-### Global
-
-```
-~/.halo/global/
-├── USER.md                    ← bootstrap-generated
-├── INSTRUCTIONS.md            ← user-global preferences
-├── prompts/
-│   ├── bootstrap/BOOTSTRAP.md
-│   ├── all/TOOL_GUIDELINES.md
-│   └── root/PLATFORM_KNOWLEDGE.md, ORCHESTRATOR_GUIDELINES.md
-├── agents/<id>/{agent.yaml, AGENT.md}
-└── skills/<id>/SKILL.md
-```
-
-### Workspace
-
-```
-<ws>/.halo/
-├── USER.md                       ← optional, overrides global
-├── INSTRUCTIONS.md               ← project-root preferences
-├── INDEX.md                      ← sole project index
-├── <subdir>/.halo/INSTRUCTIONS.md  ← per-subdir preferences, stacked
-├── agents/<id>/{agent.yaml, AGENT.md}
-└── skills/<id>/SKILL.md
-```
-
----
-
-## Root vs sub-agent behaviour matrix
-
-| Injected content | Root (`!parentId`) | Sub-agent |
-|---|---|---|
-| USER.md | ✓ | ✗ |
-| AGENT.md | ✓ | ✓ |
-| INSTRUCTIONS.md (global + stacked) | ✓ | ✓ |
-| INDEX.md (project root) | ✓ | ✓ |
-| `prompts/all/` | ✓ | ✓ |
-| `prompts/root/` | ✓ | ✗ |
-| `prompts/bootstrap/` | ✓ (only when no USER.md) | ✗ |
-| `"workspace at..."` | ✓ | ✓ |
-| `"Working directory: ..."` | only when workingDir != root | always |
-
----
-
-## Execution phases
-
-Grouped into 6 todo buckets:
-
-### A. is_default → priority (backend + frontend)
-- session-manager.ts: drop isDefault; replace prompt branches with `!parentId`; merge tool order; drop `list_agents` filter
-- agent-loader.ts: YAML gains priority; `scanAvailableAgents` returns priority
-- agent-configs.ts: `parseAgentYaml` reads priority; sort by priority desc + name asc; seed template gains `priority: 99`; DELETE adds last-global guard
-- frontend types.ts + api-client.ts: rename fields
-- chat-panel.tsx: default-selection logic; remove "default" badge
-- agent-management-main.tsx + agent-form.tsx: delete isDefault UI
-
-### B. working_dir feature
-- `start_session` schema adds `working_dir`
-- `createSession` / `buildAgentInstance` pass it through
-- DB migration: `agent_sessions` adds `workingDir` column
-- Resume restores from DB
-
-### C. md-loader simplification
-- INDEX.md reads only `<ws>/.halo/INDEX.md`; drop `subDirIndex`
-- INSTRUCTIONS.md becomes `workspaceInstructionsChain: Array<{rel, content}>`
-- `composeMdPrompt` expands the chain as multiple sections, each header labelled with relative path (root = `.`)
-- Implement `collectInstructionsChain(workspaceRoot, workingDir)`
-
-### D. Externalise system prompts
-- Create `~/.halo/global/prompts/{bootstrap,all,root}/`
-- `init.ts` startup seeds four MD files (content from `tool-guidelines.ts`)
-- New `loadSystemPrompts()` reads live per subdir, filename-ascending concat
-- Replace `import { ... } from './tool-guidelines'` with `loadSystemPrompts()` calls
-- Missing: warn + fall back to the hard-coded value (keep `tool-guidelines.ts`)
-
-### E. Doc sync
-- CLAUDE.md: describe the MD load flow, agent model
-- `.halo/docs/backend/md-loading-flow.md` (already in target state)
-- `.halo/docs/knowledge-system.md`: directory layout, injection rules
-- `.halo/docs/data-storage-protocol.md`: agent YAML fields + new agent_sessions column
-- `.halo/docs/session-tools-reference.md`: `start_session` schema
-- `.halo/docs/test-case.md`: updated test cases
-
-### F. Deployment smoke test
-- `pnpm --filter core/server/web build`
-- Kill 9527, restart with Node 22 (PATH=$HOME/.nvm/versions/node/v22.21.1/bin:$PATH)
-- Smoke: /api/health, WS connect, send one message end-to-end
-- Verify: root agent receives prompts/root, sub-agent doesn't; INSTRUCTIONS stacking works; working_dir wires through; deletion guard fires
-
----
-
-## Key constraints and risks
-
-- **Node version**: must be v22+ (better-sqlite3 native binding bound to v22). Scripts must load nvm.
-- **Compatibility**: legacy YAML's `is_default: true` stays readable but ignored; DB's `is_default` column stays untouched, just unread.
-- **Backwards-compat seed**: `default` agent still auto-seeds with id `default`, but YAML uses `priority: 99`.
-- **Path safety**: `working_dir` must be verified inside workspace (block `../` escapes).
-- **Cache key**: with merged tool list, `cache_control` still goes on the last tool — stability unaffected.
-- **Bootstrap idempotence**: once USER.md exists, `needsBootstrap` is false forever, `prompts/bootstrap/` no longer injects.
-- **Self-spawn allowed**: `session_id` depth limit (`maxNestingDepth`) already guards against infinite recursion.
-
----
-
-## Rollback plan
-
-If something breaks in production:
-- Git revert to pre-refactor commit
-- `~/.halo/global/prompts/` directory is harmless to older versions (they don't read it)
-- `agent_sessions.workingDir` column harmless (old code reads null → falls back to workspaceRoot)
-- YAML `priority` harmless to older code (unknown field = default 0); `is_default: true` can be seeded back into the default agent's YAML
-
----
-
-## Todo index
-
-See the todo list. All 12 pending items run A → F; the last one is the smoke test.