dsh-agent-lines 0.3.0 → 0.3.2

package/CHANGELOG.en.md

@@ -2,6 +2,20 @@
 
 English | [中文](CHANGELOG.md)
 
+## 0.3.2 (2026-11-04)
+
+- Zero-config bootstrap: with no plugin config, start one unbound manager line; a root Session can call line_claim_manager to bind itself.
+- Default DB path follows DSH_HOME; without it, still ~/.dsh/agent-lines/lines.db.
+- README now requires a DSH Web restart after install/update; explicit manager/worker config is optional.
+- No schema change; remains v6.
+
+## 0.3.1 (2026-11-04)
+
+- README is now user-first: scenarios and install come first; technical details are later.
+- Added install.sh, which picks the DSH Web profile automatically and verifies agent-lines.
+- The npm 0.3.1 package now carries the same bilingual README and install docs as the public repo.
+- No runtime behavior change; schema remains v6.
+
 ## 0.3.0 (2026-11-04)
 
 - Transport seam (`transport: sqlite` default).

package/CHANGELOG.md

@@ -2,6 +2,20 @@
 
 [English](CHANGELOG.en.md) | 中文
 
+## 0.3.2 (2026-11-04)
+
+- 零配置启动：没有 plugin config 时自动启动一条未绑定 manager，根会话可调用 line_claim_manager 自己绑定。
+- 默认 DB 路径跟随 DSH_HOME；未设置时仍为 ~/.dsh/agent-lines/lines.db。
+- README 明确：安装或更新后必须重启 DSH Web；显式 manager/worker 配置变为可选。
+- 无 schema 变化，仍为 v6。
+
+## 0.3.1 (2026-11-04)
+
+- README 改为用户优先：先场景、安装和首次使用，技术细节后置；安装/快速开始不再要求手填 profile。
+- 新增 install.sh，自动选择 DSH Web profile，并检查 agent-lines 是否可用。
+- 同步最新双语 README、Pages、安装说明；0.3.1 的 npm 包内文档与公开仓库一致。
+- 无运行时行为变更；schema 仍为 v6。
+
 ## 0.3.0 (2026-11-04)
 
 - Transport 接缝（transport: sqlite 默认）。

package/README.en.md

@@ -4,81 +4,42 @@ English | [中文](README.md)
 
 > Community plugin for DeepSeek Harness. Not an official DeepSeek product.
 
-> **100% vibe-coded.** The architecture, code, tests, and docs were produced in AI agent sessions. It is experimental: review the code and run the integration test before production use.
+> **100% Vibe Coding.** The architecture, code, tests, and docs were produced in AI agent sessions. It is experimental: review the code and run an integration test before production use.
 
-A drop-in super-agent alternative for DSH agents. Durable, addressable peer messaging between DSH agent lines. A line is an ordinary DSH Session with a stable label; a DSH process can host one or more lines, and a manager line can create more lines by conversation with `line_create`.
+A drop-in super-agent alternative for DSH.
 
-## When to use it
-
-Use built-in **subagents / Agent Teams** when all workers are children of one session in one DSH process. That is simpler and needs no plugin.
-
-Use **dsh-agent-lines** when you need:
-
-- named lines that are addressable as `agent#line`;
-- lines that can be independent DSH Sessions with their own context and lifetime;
-- a durable inbox that survives a receiver restart;
-- several DSH processes on one machine sharing one line database;
-- a manager line that creates worker lines by natural-language request.
-
-The plugin is a transport + light provisioning layer, not a task orchestrator. Handover (moving a line to a new Session and switching routing) is **not** implemented.
-
-## Transports
-
-`transport` defaults to `sqlite` (local-first) and is the only transport shipped in 0.3. Installing the plugin never requires Postgres or a Python service.
-
-## Architecture
+Stop reopening sessions and copying context by hand. Give one lead agent a long-lived team: each member has a name and a role, messages survive restarts, and the lead collects and reports the results.
 
-~~~mermaid
-flowchart LR
-  U[User] --> M[Manager DSH Session]
-  M -->|line_create / line_send| P[dsh-agent-lines]
-  P --> Q[(SQLite lines.db)]
-  P -->|prompt requestId| W1[Worker line Session A]
-  P -->|prompt requestId| W2[Worker line Session B]
-  W1 -->|line_inbox / line_ack| P
-  W2 -->|line_inbox / line_ack| P
-~~~
+## When to use it
 
-The DSH adapter owns line identity and delivery into a Session; the transport owns durable messages and cross-process storage. The default transport is local SQLite. Public architecture: [English](docs/ARCHITECTURE.en.md) | [中文](docs/ARCHITECTURE.md).
+Use it when:
 
-## Requirements
+- You have a long-running project and do not want to re-explain the background every time.
+- You want several agents to keep stable roles: research, architecture, UI/UX, development, testing, release, and operations.
+- You need a fixed name for each role, so you can assign work directly.
+- Work must survive closing a window or restarting DSH: messages and context should still be there.
+- You want one lead agent to decompose work, create the team, track progress, collect results, and report back.
 
-- DSH `>=0.2.1-rc.5 <0.3.0`
-- Node.js `^22.19.0 || >=24.0.0`
-- A local filesystem for the SQLite database (NFS/CIFS/SMB/FUSE are refused)
+If you only need temporary child tasks inside one session, use DSH subagents / Agent Teams; you do not need this plugin.
 
 ## Install
 
-```bash
-dsh plugin --profile <profile> add dsh-agent-lines@0.3.0
-```
-
-Until the package is published, install the local tarball:
+One-command install (recommended; no need to find a profile):
 
-```bash
-dsh plugin --profile <profile> add ./dsh-agent-lines-0.3.0.tgz
-```
-
-If you do not know the `<profile>`, use the one-command installer (it picks `web`, or the only profile):
+    curl -fsSL https://raw.githubusercontent.com/Lencen/dsh-agent-lines/main/install.sh -o install.sh
+    bash install.sh
 
-```bash
-curl -fsSL https://raw.githubusercontent.com/Lencen/dsh-agent-lines/main/install.sh -o install.sh
-bash install.sh
-# if npm is not published: bash install.sh ./dsh-agent-lines-0.3.0.tgz
-```
+The script picks the DSH Web profile, installs the plugin, and verifies agent-lines. If it cannot decide, it lists existing profiles and tells you how to specify one.
 
-For a manual install, `<profile>` is the **DSH profile name** (the directory under `~/.dsh/profiles/<profile>`), not a line or agent name.
+**Restart DSH Web after install or update.** A running process does not load new plugin code. With no plugin config the plugin starts in zero-config mode: one unbound manager line, and a root Session can call line_claim_manager to bind itself. The explicit "Manager config" block is optional, for a fixed manager/worker setup.
 
-- Existing profile: run `ls ~/.dsh/profiles` and use the real directory name, such as `web` or `headless`.
-- Isolated install: use a new name such as `agent-lines`; the command initializes it:
+Offline or when npm is unavailable, use the local tarball:
 
-```bash
-dsh plugin --profile agent-lines add dsh-agent-lines@0.3.0
-```
+    bash install.sh ./dsh-agent-lines-0.3.2.tgz
 
-Do not put a line label such as `manager-line` or `research` in `--profile`.
+After install and restart, it works without a config. When you want a fixed manager/worker setup, paste the "Manager config" block below into the file printed by the installer.
 
-### Manager config
+### Manager config (optional)
 
 ```yaml
 - id: agent-lines
@@ -102,35 +63,13 @@ Do not put a line label such as `manager-line` or `research` in `--profile`.
 
 Only `createFrom` may call `line_create`. Worker profiles should leave `allowCreate` false.
 
-### Worker profile
-
-```yaml
-- id: agent-lines
-  name: dsh-agent-lines
-  config:
-    agentId: agent-demo
-    dbPath: /home/me/.dsh/agent-lines/lines.db
-    lines:
-      - label: frontend-line
-        sessionId: session-lines-frontend
-        role: 前端
-```
-
-The legacy single-line form `line: frontend-line` + `sessionId: ...` is still accepted.
-
 ## Quick start
 
-1. Install the bundle with <code>dsh plugin --profile &lt;profile&gt; add dsh-agent-lines@0.3.0</code>, or the local tarball (see Install).
-2. Configure one manager line with <code>allowCreate: true</code>, <code>allowClaim: true</code>, and <code>createFrom: manager-line</code>.
-3. Start that profile and open any root Session.
-4. Call <code>line_status</code>. If the current Session is not bound, call <code>line_claim_manager({ confirm: "bind-manager" })</code>; the CLI fallback is:
-   ~~~bash
-   dsh-agent-lines claim --agent agent-demo --line manager-line --session "$DSH_SESSION_ID"
-   ~~~
-5. Tell the manager: "Create frontend-line, backend-line and ops-line, then send each a short hello."
-6. Worker lines can be separate profiles pointing at the same <code>dbPath</code>, or lines created inside the manager process.
-
-The first thing to check on any new Session is <code>line_status</code>: it explains whether the Session is bound, who the manager is, and what to do next.
+1. Run the installer above.
+2. **Restart DSH Web** so the plugin is loaded.
+3. Open any root Session. The zero-config path needs no YAML.
+4. Call line_status; if the Session is not bound, call line_claim_manager({ confirm: "bind-manager" }).
+5. Say "create the first-use team"; wait for the member lines, then send the first task separately.
 
 ## First use: build a development team
 
@@ -164,30 +103,18 @@ After creation, call line_list to confirm.
 
 Actual DSH Web demo profile, generic labels; no internal data.
 
-
 ## Scenario: one manager, several execution lines
 
-A manager profile exists, but the Session does not have to be pre-bound. Open any root Session and say:
+The lead creates the team first; the work comes next.
 
-> You are the manager line. First bind yourself with line_claim_manager, then own task decomposition and scheduling. Create execution lines for frontend, backend, ops, and data; assign work, coordinate them, resolve conflicts, collect results, and summarize.
+1. The lead creates members by role: research, architecture, UI/UX, development, testing, acceptance, release, operations.
+2. You give the lead one concrete task, for example "add CSV export to the reports page, with tests and a one-page runbook."
+3. The lead decomposes it and sends each part to the right member; every message stays local.
+4. Members receive the task, execute it, acknowledge it, and reply to the lead when needed.
+5. The lead collects results, resolves disagreements, and aligns the answer.
+6. You see the lead's summary; each member keeps its own context and message history.
 
-What happens next:
-
-1. The manager calls <code>line_create</code> for each execution line and <code>line_list</code> to confirm them.
-2. The user gives a task, for example: "Add CSV export to the reports page, with tests and a short runbook."
-3. The manager decomposes it and calls <code>line_send</code> to the relevant lines. Each message is persisted in SQLite.
-4. Each worker calls <code>line_inbox</code>, does its part, calls <code>line_ack</code>, and may reply with <code>line_send</code>.
-5. The manager collects results, resolves a disagreement (for example, frontend and backend disagree on the response shape), and writes the summary.
-6. The user sees the manager summary; the worker Sessions keep their own context and message history.
-
-This is a prompt pattern, not a built-in org chart: the manager model decides how to split work. The plugin supplies the durable transport and hard guards:
-
-- <code>maxLines</code> bounds creation;
-- <code>noReply</code>, <code>maxReplyDepth</code>, and self-send blocking stop automatic echo;
-- <code>line_status</code> diagnoses a missing manager binding;
-- one Session has one writer.
-
-If the manager is not bound, <code>line_status</code> returns the repair command; call <code>line_claim_manager</code> (or the CLI) before the scenario.
+This is a prompt-driven team pattern, not a built-in org chart: the lead model decides how to split work. Technical details are in "Use" and "Delivery semantics" below.
 
 ## Use
 
@@ -227,6 +154,31 @@ dsh-agent-lines doctor
 
 Use `--db` or `DSH_AGENT_LINES_DB` to point the CLI at the plugin's database.
 
+## Transports
+
+`transport` defaults to `sqlite` (local-first) and is the only transport shipped in 0.3. Installing the plugin never requires Postgres or a Python service.
+
+## Architecture
+
+~~~mermaid
+flowchart LR
+  U[User] --> M[Manager DSH Session]
+  M -->|line_create / line_send| P[dsh-agent-lines]
+  P --> Q[(SQLite lines.db)]
+  P -->|prompt requestId| W1[Worker line Session A]
+  P -->|prompt requestId| W2[Worker line Session B]
+  W1 -->|line_inbox / line_ack| P
+  W2 -->|line_inbox / line_ack| P
+~~~
+
+The DSH adapter owns line identity and delivery into a Session; the transport owns durable messages and cross-process storage. The default transport is local SQLite. Public architecture: [English](docs/ARCHITECTURE.en.md) | [中文](docs/ARCHITECTURE.md).
+
+## Requirements
+
+- DSH `>=0.2.1-rc.5 <0.3.0`
+- Node.js `^22.19.0 || >=24.0.0`
+- A local filesystem for the SQLite database (NFS/CIFS/SMB/FUSE are refused)
+
 ## Workspaces
 
 DSH groups Sessions by workspace membership, not by cwd. line_create resolves the

package/README.md

@@ -6,79 +6,40 @@
 
 > **100% Vibe Coding。** 架构、代码、测试、文档都在 AI agent 会话中完成。它是实验性项目：生产使用前请审阅代码并跑一遍集成测试。
 
-DSH agent 的 super agent 平替插件。给 DSH agent 线（line）用的、可寻址的持久消息层。一条线是一个普通 DSH Session 加一个稳定 label；一个 DSH 进程可以承载多条线，管理线还可以通过 `line_create` 在对话里创建新线。
+DSH 的 super agent 平替插件。
 
-## 什么时候用
-
-如果所有 worker 都是同一个 DSH 进程里、同一个父 Agent 的子任务，**优先用内置 subagent / Agent Teams**；更简单，不需要插件。
-
-需要下面这些时再用 **dsh-agent-lines**：
-
-- 线要能按 `agent#line` 寻址；
-- 线是独立 DSH Session，有自己的上下文和生命周期；
-- 收件箱要能跨接收方重启存活；
-- 同机多个 DSH 进程共享一个线数据库；
-- 管理线通过自然语言让模型创建 worker 线。
-
-插件只做传输 + 轻量建线，不做任务编排。**交接（handover）没有实现**。
-
-## 传输
-
-`transport` 默认 `sqlite`（local-first），也是 0.3 唯一发布的 transport；安装插件不需要 Postgres 或 Python 服务。
-
-## 架构
+你不用每次新开会话、手动把背景复制给几个 agent。让一个负责人 agent 带一支长期协作的团队：每个成员有名字、各负责一块，任务和消息不会丢，结果由负责人汇总给你。
 
-~~~mermaid
-flowchart LR
-  U[用户] --> M[管理线 DSH Session]
-  M -->|line_create / line_send| P[dsh-agent-lines]
-  P --> Q[(SQLite lines.db)]
-  P -->|prompt requestId| W1[前端线 Session]
-  P -->|prompt requestId| W2[后端线 Session]
-  W1 -->|line_inbox / line_ack| P
-  W2 -->|line_inbox / line_ack| P
-~~~
+## 什么时候用
 
-DSH 适配层负责线身份和“把消息送进 Session”；transport 负责持久消息和跨进程存储。默认是本地 SQLite。公开架构说明：[English](docs/ARCHITECTURE.en.md) | [中文](docs/ARCHITECTURE.md)。
+如果你遇到这些情况，再考虑安装：
 
-## 要求
+- 你有一个长期项目，不想每次都从头解释背景；
+- 你希望几个 agent 长期分工，比如调研、架构、开发、测试、发布、运维；
+- 你需要给每个角色一个固定名字，能直接点名派任务；
+- 任务做到一半关掉窗口、重启 DSH，消息和上下文还要在；
+- 你希望一个负责人 agent 自己拆任务、建团队、追进度、收结果，最后向你汇报。
 
-- DSH `>=0.2.1-rc.5 <0.3.0`
-- Node.js `^22.19.0 || >=24.0.0`
-- 本地文件系统（NFS/CIFS/SMB/FUSE 会被拒绝）
+如果只是同一次会话里的临时子任务，直接用 DSH 内置的 subagent / Agent Teams，不需要这个插件。
 
 ## 安装
 
-```bash
-dsh plugin --profile <profile> add dsh-agent-lines@0.3.0
-```
-
-包尚未发布时，用本地 tarball 安装：
+一条命令安装（推荐，不需要自己找 profile）：
 
-```bash
-dsh plugin --profile <profile> add ./dsh-agent-lines-0.3.0.tgz
-```
-
-不知道 `<profile>` 是什么，可以直接用一键脚本（自动选 `web`，没有 web 时选唯一 profile）：
+    curl -fsSL https://raw.githubusercontent.com/Lencen/dsh-agent-lines/main/install.sh -o install.sh
+    bash install.sh
 
-```bash
-curl -fsSL https://raw.githubusercontent.com/Lencen/dsh-agent-lines/main/install.sh -o install.sh
-bash install.sh
-# npm 未发布时：bash install.sh ./dsh-agent-lines-0.3.0.tgz
-```
+脚本会自动选择 DSH Web 使用的 profile，安装后检查 agent-lines 是否可用；如果判断不了，会列出已有配置并提示你怎么指定。
 
-手动安装时，`<profile>` 是 **DSH profile 名**（对应 `~/.dsh/profiles/<profile>`），不是线名，也不是 agent 名。
+**安装或更新后必须重启 DSH Web。** 运行中的进程不会加载新插件代码。插件没有 config 时走零配置：启动一条未绑定 manager，根会话可以调用 line_claim_manager 自己绑定。显式“管理线配置”是可选的，用于固定 manager/worker。
 
-- 已有 profile：先 `ls ~/.dsh/profiles`，填实际目录名，例如 `web`、`headless`；
-- 想隔离安装：用新名字，例如 `agent-lines`，命令会自动初始化：
+离线或 npm 不可用时，用本地 tarball：
 
-```bash
-dsh plugin --profile agent-lines add dsh-agent-lines@0.3.0
-```
+    bash install.sh ./dsh-agent-lines-0.3.2.tgz
 
-不要把 `manager-line`、`research` 这类线名填进 `--profile`。
+安装并重启后，不写配置也可以直接使用；需要固定管理线/worker 时，再把下面“管理线配置”粘贴到脚本打印的配置文件。
 
-### 管理线配置
+### 管理线配置（可选）
 
 ```yaml
 - id: agent-lines
@@ -102,35 +63,13 @@ dsh plugin --profile agent-lines add dsh-agent-lines@0.3.0
 
 只有 `createFrom` 指定的线能调用 `line_create`。worker profile 不要开 `allowCreate`。
 
-### Worker profile
-
-```yaml
-- id: agent-lines
-  name: dsh-agent-lines
-  config:
-    agentId: agent-demo
-    dbPath: /home/me/.dsh/agent-lines/lines.db
-    lines:
-      - label: frontend-line
-        sessionId: session-lines-frontend
-        role: 前端
-```
-
-旧的单线写法 `line: frontend-line` + `sessionId: ...` 仍然兼容。
-
 ## 快速开始
 
-1. 安装：<code>dsh plugin --profile &lt;profile&gt; add dsh-agent-lines@0.3.0</code>，或用本地 tarball（见“安装”）。
-2. 配置一条管理线：<code>allowCreate: true</code>、<code>allowClaim: true</code>、<code>createFrom: manager-line</code>。
-3. 启动 profile，打开任意根 Session。
-4. 先调用 <code>line_status</code>。如果当前会话未绑定，调用 <code>line_claim_manager({ confirm: "bind-manager" })</code>；CLI 兜底：
-   ~~~bash
-   dsh-agent-lines claim --agent agent-demo --line manager-line --session "$DSH_SESSION_ID"
-   ~~~
-5. 对管理线说：“创建 frontend-line、backend-line、ops-line，然后分别发一条 hello。”
-6. worker 可以是独立 profile（共享同一个 <code>dbPath</code>），也可以是管理线进程内创建的线。
-
-任何新会话先看 <code>line_status</code>：它会告诉你是否绑定、manager 是谁、下一步怎么修。
+1. 运行上面的安装脚本。
+2. **重启 DSH Web**，让插件加载。
+3. 打开任意根会话。零配置路径不需要改 YAML。
+4. 先调用 line_status；如果当前会话未绑定，调用 line_claim_manager({ confirm: "bind-manager" })。
+5. 直接说“按首次使用创建团队”，然后等它建好成员线；第一个任务再单独发。
 
 ## 首次使用：组建开发团队
 
@@ -165,30 +104,18 @@ line_create({ label: "ops", role: "运维" })
 
 真实 DSH Web 演示 profile、通用 label；不含内部数据。
 
-
 ## 场景：一个管理线 + 多条执行线
 
-只要 profile 里有管理线配置，Session 不必预先绑定。打开任意根 Session，直接说：
+负责人先建好团队，后面才是具体任务。
 
-> 你是管理线。先用 line_claim_manager 把自己绑定为管理线，然后负责任务拆分与调度。需要建几个任务执行线，由你安排分配任务；你负责协调执行线中的工作内容、裁决纠纷、回收任务结果、汇总、总结、汇报。
+1. 负责人按角色建立成员：调研、架构、UIUX、开发、测试、验收、发布、运维。
+2. 你给负责人一个具体任务，例如“给报表页加 CSV 导出，带测试和一页 runbook”。
+3. 负责人把任务拆开，派给对应的成员；每条消息都会留在本地。
+4. 成员收到任务、执行、确认收到，需要时回复负责人。
+5. 负责人收集结果，处理成员之间的分歧，统一口径。
+6. 你看到负责人的汇总；每个成员保留自己的上下文和消息记录。
 
-接下来会发生：
-
-1. 管理线调用 <code>line_create</code> 创建前端线、后端线、运维线、数据线，再用 <code>line_list</code> 确认。
-2. 用户给一个具体任务，例如：“给报表页加 CSV 导出，带测试和一页 runbook。”
-3. 管理线拆解后，用 <code>line_send</code> 发给对应执行线；消息落 SQLite。
-4. 执行线用 <code>line_inbox</code> 收任务、执行、<code>line_ack</code> 确认，需要时用 <code>line_send</code> 回复。
-5. 管理线收集结果；如果前端和后端对接口结构有分歧，管理线裁决并统一口径。
-6. 管理线汇总、总结、汇报；各执行线保留自己的上下文和消息历史。
-
-这是一个“提示词组织模式”，不是插件内置的组织架构：怎么拆任务由管理线模型决定。插件提供的是持久传输和硬约束：
-
-- <code>maxLines</code> 限制建线数量；
-- <code>noReply</code>、<code>maxReplyDepth</code> 和默认 self-send 禁止，防止自动回声；
-- <code>line_status</code> 诊断 manager 绑定；
-- 一个 Session 只能有一个 writer。
-
-如果管理线没绑定，<code>line_status</code> 会给出修复命令；先调用 <code>line_claim_manager</code>（或 CLI）再跑这个场景。
+这只是“用提示词组织团队”的方式，不是插件内置的组织架构；怎么拆任务由负责人模型决定。技术细节（消息、状态、工具）在下面的“使用”和“投递语义”。
 
 ## 使用
 
@@ -228,6 +155,31 @@ dsh-agent-lines doctor
 
 用 `--db` 或 `DSH_AGENT_LINES_DB` 指向插件同一个数据库。
 
+## 传输
+
+`transport` 默认 `sqlite`（local-first），也是 0.3 唯一发布的 transport；安装插件不需要 Postgres 或 Python 服务。
+
+## 架构
+
+~~~mermaid
+flowchart LR
+  U[用户] --> M[管理线 DSH Session]
+  M -->|line_create / line_send| P[dsh-agent-lines]
+  P --> Q[(SQLite lines.db)]
+  P -->|prompt requestId| W1[前端线 Session]
+  P -->|prompt requestId| W2[后端线 Session]
+  W1 -->|line_inbox / line_ack| P
+  W2 -->|line_inbox / line_ack| P
+~~~
+
+DSH 适配层负责线身份和“把消息送进 Session”；transport 负责持久消息和跨进程存储。默认是本地 SQLite。公开架构说明：[English](docs/ARCHITECTURE.en.md) | [中文](docs/ARCHITECTURE.md)。
+
+## 要求
+
+- DSH `>=0.2.1-rc.5 <0.3.0`
+- Node.js `^22.19.0 || >=24.0.0`
+- 本地文件系统（NFS/CIFS/SMB/FUSE 会被拒绝）
+
 ## 工作区
 
 DSH 侧边栏按 workspace 的 sessionIds 成员表分组，不是按 cwd。line_create 通过 workspaceRegistry.resolveByPath 找到管理线所属工作区，传 workspaceId，DSH 会在创建时 attachSession，新线就不会落到“未分组”。如果管理线没有 workspace，插件回退 cwd，线仍未分组。

package/docs/SECURITY.en.md

@@ -13,13 +13,13 @@ Only install packages whose source you have reviewed. This is a community plugin
 - Default transport is a local SQLite file.
 - The parent directory is created with mode `0700`; the database is chmod `0600`.
 - The DB contains message bodies, line names, Session ids, and delivery metadata. Treat it as sensitive operational data.
-- No encryption at rest in 0.3.0; use full-disk encryption if needed.
+- No encryption at rest in 0.3.x; use full-disk encryption if needed.
 
 ## Network
 
-0.3.0 has no network listener and makes no outbound network calls. It only reads/writes the local DB and calls DSH's in-process `sessionController`.
+0.3.x has no network listener and makes no outbound network calls. It only reads/writes the local DB and calls DSH's in-process `sessionController`.
 
-External transports are not part of 0.3.0; SQLite is local.
+External transports are not part of 0.3.x; SQLite is local.
 
 ## Peer content
 
@@ -33,7 +33,7 @@ The model is told to evaluate peer messages before acting. This is a prompt-leve
 
 - The sender identity is the line registered in the local DB, not a field supplied by the model.
 - The tool layer rejects calls from a Session this process does not serve (`LINE_WRONG_SESSION`).
-- In 0.3.0 the DB is local and trusted; there is no cryptographic sender signature. A local user who can write the DB can forge messages.
+- In 0.3.x the DB is local and trusted; there is no cryptographic sender signature. A local user who can write the DB can forge messages.
 
 ## Line creation
 

package/docs/SECURITY.md

@@ -13,13 +13,13 @@ dsh-agent-lines 是 DSH Host 插件，运行在 DSH 进程内，拥有该进程
 - 默认传输是本地 SQLite 文件。
 - 父目录权限 0700；数据库权限 0600。
 - 数据库包含消息正文、线名、Session id 和投递元数据，按敏感运维数据处理。
-- 0.3.0 不做静态加密；需要时使用全盘加密。
+- 0.3.x 不做静态加密；需要时使用全盘加密。
 
 ## 网络
 
-0.3.0 没有网络监听，也不发起外部网络请求。它只读写本地 DB，并调用 DSH 进程内的 sessionController。
+0.3.x 没有网络监听，也不发起外部网络请求。它只读写本地 DB，并调用 DSH 进程内的 sessionController。
 
-外部 transport 不属于 0.3.0；SQLite 是本地实现。
+外部 transport 不属于 0.3.x；SQLite 是本地实现。
 
 ## 对端内容
 
@@ -33,7 +33,7 @@ dsh-agent-lines 是 DSH Host 插件，运行在 DSH 进程内，拥有该进程
 
 - 发送方身份来自本地 DB 注册的线，不是模型自己填的字段。
 - 工具层会拒绝当前进程不服务的 Session 调用（LINE_WRONG_SESSION）。
-- 0.3.0 的 DB 是本地且受信任的；没有密码学发送方签名。能写 DB 的本地用户可以伪造消息。
+- 0.3.x 的 DB 是本地且受信任的；没有密码学发送方签名。能写 DB 的本地用户可以伪造消息。
 
 ## 建线
 

package/docs/en/index.html

@@ -43,7 +43,7 @@ footer{padding:34px 0 48px;color:var(--muted);font-size:12px}
 <div class="wrap">
 <header>
   <a class="brand" href="../"><span class="mark"></span>dsh-agent-lines</a>
-  <nav><a href="../">中文</a><a href="https://github.com/Lencen/dsh-agent-lines">GitHub</a><a href="https://github.com/Lencen/dsh-agent-lines/releases/tag/v0.3.0">Release</a></nav>
+  <nav><a href="../">中文</a><a href="https://github.com/Lencen/dsh-agent-lines">GitHub</a><a href="https://github.com/Lencen/dsh-agent-lines/releases/tag/v0.3.2">Release</a></nav>
 </header>
 <main>
 <section class="hero" style="border:0;padding-bottom:22px">
@@ -51,10 +51,10 @@ footer{padding:34px 0 48px;color:var(--muted);font-size:12px}
     <div class="kicker">Community plugin · Apache-2.0</div>
     <h1>Durable lines<br><span>for DSH agents</span></h1>
     <p class="lead">One manager, several execution lines. Each line is an ordinary DSH Session with its own context and durable inbox. Messages live in local SQLite, shared across processes, with no network service.</p>
-    <div class="install">dsh plugin --profile &lt;profile&gt; add dsh-agent-lines@0.3.0</div>
+    <div class="install">curl -fsSL https://raw.githubusercontent.com/Lencen/dsh-agent-lines/main/install.sh -o install.sh &amp;&amp; bash install.sh</div>
     <div class="actions">
       <a class="btn primary" href="https://github.com/Lencen/dsh-agent-lines">GitHub repository</a>
-      <a class="btn" href="https://github.com/Lencen/dsh-agent-lines/releases/tag/v0.3.0">Download 0.3.0</a>
+      <a class="btn" href="https://github.com/Lencen/dsh-agent-lines/releases/tag/v0.3.2">Download 0.3.2</a>
     </div>
   </div>
   <div class="shot">
@@ -78,7 +78,7 @@ research / architecture / uiux / dev / test / acceptance / release / ops
 Then call line_list and wait for my first task.</pre>
   <p style="color:var(--muted);font-size:14px">Full docs, protocol, and limits: <a href="https://github.com/Lencen/dsh-agent-lines">README</a>. Community plugin, not an official DeepSeek product.</p>
 </section>
-<footer>dsh-agent-lines 0.3.0 · Apache-2.0 · Community plugin for DeepSeek Harness. Not an official DeepSeek product.</footer>
+<footer>dsh-agent-lines 0.3.2 · Apache-2.0 · Community plugin for DeepSeek Harness. Not an official DeepSeek product.</footer>
 </main>
 </div>
 </body>

package/docs/index.html

@@ -43,7 +43,7 @@ footer{padding:34px 0 48px;color:var(--muted);font-size:12px}
 <div class="wrap">
 <header>
   <a class="brand" href="./"><span class="mark"></span>dsh-agent-lines</a>
-  <nav><a href="en/index.html">English</a><a href="https://github.com/Lencen/dsh-agent-lines">GitHub</a><a href="https://github.com/Lencen/dsh-agent-lines/releases/tag/v0.3.0">Release</a></nav>
+  <nav><a href="en/index.html">English</a><a href="https://github.com/Lencen/dsh-agent-lines">GitHub</a><a href="https://github.com/Lencen/dsh-agent-lines/releases/tag/v0.3.2">Release</a></nav>
 </header>
 <main>
 <section class="hero" style="border:0;padding-bottom:22px">
@@ -51,10 +51,10 @@ footer{padding:34px 0 48px;color:var(--muted);font-size:12px}
     <div class="kicker">Community plugin · Apache-2.0</div>
     <h1>给 DSH Agent 的<br><span>持久消息线</span></h1>
     <p class="lead">一个管理线，多条执行线。每条线是普通 DSH Session，有独立上下文和持久收件箱；消息落本地 SQLite，跨进程共享，不依赖网络服务。</p>
-    <div class="install">dsh plugin --profile &lt;profile&gt; add dsh-agent-lines@0.3.0</div>
+    <div class="install">curl -fsSL https://raw.githubusercontent.com/Lencen/dsh-agent-lines/main/install.sh -o install.sh &amp;&amp; bash install.sh</div>
     <div class="actions">
       <a class="btn primary" href="https://github.com/Lencen/dsh-agent-lines">GitHub 仓库</a>
-      <a class="btn" href="https://github.com/Lencen/dsh-agent-lines/releases/tag/v0.3.0">下载 0.3.0</a>
+      <a class="btn" href="https://github.com/Lencen/dsh-agent-lines/releases/tag/v0.3.2">下载 0.3.2</a>
     </div>
   </div>
   <div class="shot">
@@ -78,7 +78,7 @@ research / architecture / uiux / dev / test / acceptance / release / ops
 创建后用 line_list 确认，然后待命。</pre>
   <p style="color:var(--muted);font-size:14px">完整说明、协议和限制见 <a href="https://github.com/Lencen/dsh-agent-lines">README</a>。社区插件，不是 DeepSeek 官方产品。</p>
 </section>
-<footer>dsh-agent-lines 0.3.0 · Apache-2.0 · Community plugin for DeepSeek Harness. Not an official DeepSeek product.</footer>
+<footer>dsh-agent-lines 0.3.2 · Apache-2.0 · Community plugin for DeepSeek Harness. Not an official DeepSeek product.</footer>
 </main>
 </div>
 </body>

package/docs/market-index.json

@@ -50,11 +50,11 @@
         ]
       },
       "dist-tags": {
-        "latest": "0.3.0"
+        "latest": "0.3.2"
       },
       "versions": [
         {
-          "version": "0.3.0",
+          "version": "0.3.2",
           "publishTimestamp": 1793771000,
           "source": {
             "type": "npm"

package/examples/market-index.json

@@ -50,11 +50,11 @@
         ]
       },
       "dist-tags": {
-        "latest": "0.3.0"
+        "latest": "0.3.2"
       },
       "versions": [
         {
-          "version": "0.3.0",
+          "version": "0.3.2",
           "publishTimestamp": 1793771000,
           "source": {
             "type": "npm"

package/lib/index.js

@@ -40,20 +40,25 @@ function normalizeLine(entry, agentId, index) {
 /** Validate and normalize plugin config. Exported for tests and the CLI. */
 export function normalizeConfig(raw = {}) {
   if (raw === null || typeof raw !== 'object') throw new LineError('LINE_INVALID_CONFIG', 'Plugin config must be an object')
-  const agentId = validateAgentId(raw.agentId)
   const legacy = raw.line !== undefined && raw.sessionId !== undefined
     ? [{ label: raw.line, sessionId: raw.sessionId }]
     : []
   const rawLines = Array.isArray(raw.lines) ? raw.lines : legacy
-  if (rawLines.length === 0) throw new LineError('LINE_INVALID_CONFIG', 'At least one line is required (lines[] or line/sessionId)')
-  const lines = rawLines.map((entry, index) => normalizeLine(entry, agentId, index))
+  const zeroConfig = rawLines.length === 0 && raw.lines === undefined && raw.line === undefined
+  const agentId = raw.agentId === undefined && zeroConfig
+    ? 'agent-lines'
+    : validateAgentId(raw.agentId)
+  if (rawLines.length === 0 && !zeroConfig) throw new LineError('LINE_INVALID_CONFIG', 'At least one line is required (lines[] or line/sessionId)')
+  const lines = zeroConfig
+    ? [{ agentId, label: 'manager', sessionId: '', lineId: lineId(agentId, 'manager'), role: null }]
+    : rawLines.map((entry, index) => normalizeLine(entry, agentId, index))
   const labels = new Set()
   const sessions = new Set()
   for (const line of lines) {
     if (labels.has(line.label)) throw new LineError('LINE_INVALID_CONFIG', `Duplicate line label: ${line.label}`)
-    if (sessions.has(line.sessionId)) throw new LineError('LINE_INVALID_CONFIG', `Duplicate sessionId: ${line.sessionId}`)
+    if (line.sessionId !== '' && sessions.has(line.sessionId)) throw new LineError('LINE_INVALID_CONFIG', `Duplicate sessionId: ${line.sessionId}`)
     labels.add(line.label)
-    sessions.add(line.sessionId)
+    if (line.sessionId !== '') sessions.add(line.sessionId)
   }
   const createFrom = raw.createFrom === undefined ? lines[0].label : validateLineLabel(raw.createFrom)
   if (!labels.has(createFrom)) throw new LineError('LINE_INVALID_CONFIG', `createFrom must name a configured line: ${createFrom}`)
@@ -66,9 +71,9 @@ export function normalizeConfig(raw = {}) {
     transport,
     lines,
     createFrom,
-    maxLines: integer(raw.maxLines, 16, { min: lines.length, max: 256 }),
-    allowCreate: raw.allowCreate === true,
-    allowClaim: raw.allowClaim === true,
+    maxLines: integer(raw.maxLines, 16, { min: Math.max(1, lines.length), max: 256 }),
+    allowCreate: raw.allowCreate === undefined ? zeroConfig : raw.allowCreate === true,
+    allowClaim: raw.allowClaim === undefined ? zeroConfig : raw.allowClaim === true,
     allowSelfSend: raw.allowSelfSend === true,
     dedupeWindowMs: integer(raw.dedupeWindowMs, 5_000, { min: 0, max: 3_600_000 }),
     maxReplyDepth: integer(raw.maxReplyDepth, 8, { min: 1, max: 100 }),
@@ -344,6 +349,10 @@ export async function apply(ctx, rawConfig) {
       startupLines.push(effective)
     }
     for (const def of startupLines) {
+      if (def.sessionId === '') {
+        ctx.logger?.info?.('agent-lines: manager %s is unbound; waiting for claim', def.label)
+        continue
+      }
       if (!(await sessionExists(def.sessionId))) {
         ctx.logger?.warn?.('agent-lines: Session %s for line %s is missing; line stays unbound until claimed', def.sessionId, def.label)
         lineDefs.set(def.sessionId, { ...def, missing: true })

package/lib/store.js

@@ -101,7 +101,10 @@ PRAGMA user_version = 6;
 `
 
 export function defaultDbPath() {
-  return resolve(homedir(), '.dsh', 'agent-lines', 'lines.db')
+  const home = process.env.DSH_HOME === undefined || process.env.DSH_HOME.trim() === ''
+    ? resolve(homedir(), '.dsh')
+    : resolve(process.env.DSH_HOME)
+  return resolve(home, 'agent-lines', 'lines.db')
 }
 
 function expandHome(path) {

package/lib/tools.js

@@ -59,6 +59,7 @@ export function registerStatusTool(ctx, { config, store, lineDefs }) {
       const managerConfig = config.lines.find(line => line.label === config.createFrom)
       const managerDef = [...lineDefs.values()].find(line => line.label === config.createFrom)
       const managerSessionId = (managerDef ?? managerConfig)?.sessionId
+      const effectiveManagerSessionId = managerSessionId === undefined || managerSessionId === '' ? undefined : managerSessionId
       const persistence = ctx.get?.('sessionPersistence')
 
       const sessionState = async (sessionId) => {
@@ -71,12 +72,12 @@ export function registerStatusTool(ctx, { config, store, lineDefs }) {
         return { live, persisted }
       }
 
-      const manager = managerSessionId === undefined
+      const manager = effectiveManagerSessionId === undefined
         ? null
         : {
             label: config.createFrom,
-            sessionId: managerSessionId,
-            ...(await sessionState(managerSessionId)),
+            sessionId: effectiveManagerSessionId,
+            ...(await sessionState(effectiveManagerSessionId)),
             lease: store.listLines().find(line => line.label === config.createFrom)?.lease ?? null,
           }
       const lines = store.listLines().map(line => ({

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dsh-agent-lines",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "DSH Agent 的持久、可寻址消息线（社区插件）。",
   "type": "module",
   "license": "Apache-2.0",