dsh-session-messaging 0.0.0-stage → 0.1.2

package/CHANGELOG.md

@@ -0,0 +1,45 @@
+# Changelog
+
+All notable changes to this project are documented here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project uses
+[Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.2] - 2026-10-18
+
+### Fixed
+
+- Enforce the top-level boundary symmetrically. `session_send`, `session_peers`,
+  and `session_reception` now reject subagent callers with
+  `caller-not-top-level`; previously a subagent could send one-way messages to
+  top-level sessions while top-level sessions could not reply. Subagents keep
+  using the existing parent/child `send_message` channel.
+- Targeting a subagent from a top-level session remains explicitly refused with
+  `target-not-top-level`.
+
+### Changed
+
+- README (English and Chinese) now states that the envelope `from` field is the
+  trusted identity; any identity claim in the message body is data only.
+
+### Tests
+
+- Added integration coverage: a subagent caller is rejected without waking the
+  target, a top-level session cannot target a subagent, and all previous
+  refusals (self-send, cross-directory, non-live target, paused reception)
+  still pass.
+
+## [0.1.1] - 2026-10-18
+
+### Added
+
+- Bilingual plugin-manager metadata (English / 简体中文) for the bundle and its
+  tools row, plus SVG icons.
+- Desktop demo screenshot in the README.
+
+## [0.1.0] - 2026-10-18
+
+### Added
+
+- Initial release: `session_peers`, `session_send`, and `session_reception`
+  tools; peer delivery through `Agent.steer` as a durable `user/message` with a
+  `session-message` source; advisory write-scope conflict warnings.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 XBXyftx
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,188 @@
-# Temporary Holding Version
+# dsh-session-messaging
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+Cross-session messaging for [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (dsh): let **user-launched sessions in the same workspace message each other** to coordinate tasks, declared file-write scopes, and conflicts — without turning them into parent/child subagents.
+
+[![CI](https://github.com/XBXyftx/dsh-session-messaging/actions/workflows/ci.yml/badge.svg)](https://github.com/XBXyftx/dsh-session-messaging/actions/workflows/ci.yml)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+
+**English** | [简体中文](README.zh-CN.md)
+
+> Status: early preview (`0.1.0`). Targets dsh `0.2.1-rc.2`. dsh plugin APIs are pre-stable, so expect breaking changes on upstream upgrades.
+
+## Why
+
+dsh already has strong delegation (subagents, Agent Teams), but those are hierarchical and lifecycle-bound to a parent. When you open several conversations yourself — frontend, backend, docs — they work in one workspace with no way to say "I'm editing `src/ui.ts`, please avoid it" or "the API field is frozen".
+
+This plugin adds a **peer channel** between those top-level sessions:
+
+- Sessions discover each other in the same working directory.
+- A model can send a message to a peer session; the message is inserted into the target conversation as a normal user message.
+- Reception can be paused per session; write scopes are declared advice, and overlaps are reported to both sides.
+
+## Demo
+
+![A peer session's message arriving in the desktop app](docs/assets/cross-session-demo.webp)
+
+A real run in the macOS desktop app (`0.2.1-rc.2`): another user-launched session sent a test message. It arrived inline as a `session-message` envelope — sender id, timestamp, and the "peer is not an authority" note — and this session replied through `session_send`. Both sessions work in the same directory; no subagent hierarchy is involved.
+
+### Case study: peer-reported bug to verified fix
+
+Two user-launched sessions used the plugin to coordinate a real fix. One session sent a reproducible defect report with a code-level root cause; the fix shipped as `v0.1.2`, and the reporting session independently re-ran the regression on the desktop build.
+
+![Bug report received from a peer session](docs/assets/defect-report-demo.webp)
+
+*The reporting session's message as seen here: reproducible steps, root-cause pointers, and the fix request — all delivered through `session_send`.*
+
+![Regression verification after the fix](docs/assets/regression-verification.webp)
+
+*Independent regression verification: static checks plus a desktop runtime probe that returns `caller-not-top-level`, proving `v0.1.2` is active. The same message also proves the top-level → top-level path still works.*
+
+See [CHANGELOG.md](CHANGELOG.md) for the `0.1.2` entry.
+
+## Features
+
+- `session_peers` — list live, same-directory, top-level sessions and their reception state.
+- `session_send` — relay a coordination message, optionally declaring `writeScopes` and replying to a message.
+- `session_reception` — pause/resume receiving peer messages for the current session and declare its write scopes.
+- Messages appear inline in the target conversation, attributed to the sending session — no separate inbox UI.
+- Advisory **write-scope conflict detection**: if a peer declared an overlapping path, the receipt and the message envelope carry a `conflict-warning`.
+- No new Session event types and no `SESSION_FORMAT_VERSION` change: the relay is a durable `user/message` with a declared `session-message` source.
+- Bilingual plugin-card metadata and icons (English / 简体中文) for the dsh plugin manager.
+- Bounded: message size, per-sender→target rate limit, same-directory scope, top-level-only, live-only, self-send rejected.
+
+## How it works
+
+```text
+Session A (model) calls session_send
+  → tools.ts uses exec.agent as the only identity source
+  → service.send validates target, body, scopes, reception, rate limit
+  → createUserMessage({ content: envelope + body, source: session-message/relay })
+  → target.steer(message)          # next step boundary, or wake an idle agent
+  → await ctx.sessions.flush(target.session)
+Session B's log gains a user/message with source.kind = 'session-message'
+  → deriveMessages() rebuilds it → B's next model request sees it → B can reply
+```
+
+The envelope always states that the message comes from another session, not the current user, and repeats that a peer is not an authority. Peer text is treated as data, never as higher-priority instructions.
+
+## Requirements
+
+- DeepSeek Harness `0.2.1-rc.2` (desktop app or source checkout).
+- Node.js `>= 22.19.0`.
+- The plugin needs the host's copies of `@deepseek-ai/{cordis,schemastery,dsh-agent,dsh-llm,dsh-session,dsh-tools}`. They are declared as peer dependencies and resolved from the running dsh installation.
+
+## Install
+
+### From GitHub
+
+```sh
+dsh plugin --profile <profile> add github:XBXyftx/dsh-session-messaging
+```
+
+The repository ships the built `lib/` output, so installing from git does **not** run a build. If you prefer a registry, `npm publish` from this repository produces the same package (`dsh-session-messaging`).
+
+### From a local checkout
+
+```sh
+dsh plugin --profile <profile> add /absolute/path/to/dsh-session-messaging
+```
+
+### Desktop app
+
+The macOS/Windows desktop app uses its own profiles (for example `desktop`). Install with the bundled CLI or the agent's `plugin_manager` tool, targeting that profile. In dsh `0.2.1-rc.2` the configuration reloads through HMR, so the two plugin rows usually activate without restarting the app.
+
+Verify the plugin is active:
+
+- the agent's tool list contains `session_peers`, `session_send`, and `session_reception`;
+- `plugin_manager list_plugins` reports both `session-messaging` and `session-messaging-tools` with `fiberPhase: active`.
+
+## Usage
+
+Open two sessions in the same working directory, then ask either model to coordinate. The tools are model-facing; no manual UI is required.
+
+Example prompts:
+
+```text
+Use session_peers to see which other sessions are working here.
+Send session-b a message: I am editing src/ui.ts and declared it in writeScopes; avoid it.
+Check whether anyone else declared a conflicting write scope before you edit src/api.ts.
+Pause receiving peer messages for this session.
+```
+
+Tools:
+
+| Tool | Arguments | Result |
+|---|---|---|
+| `session_peers` | none | `{ peers: [{ sessionId, status, canReceive, writeScopes }] }` |
+| `session_send` | `targetSessionId`, `message`, optional `writeScopes`, `replyTo` | `{ accepted, messageId, targetSessionId, targetStatus, conflicts }` |
+| `session_reception` | `enabled`, optional `writeScopes` | `{ enabled, writeScopes }` |
+
+`accepted` means the message entered the target's inbox and the session flush acknowledged persistence. It does **not** mean the peer model processed or acted on it.
+
+## Configuration
+
+The bundle row accepts validated configuration; every field has a default:
+
+```yaml
+- id: session-messaging
+  name: dsh-session-messaging
+  config:
+    maxMessageChars: 4000
+    maxMessagesPerMinute: 12
+    requireTargetOptIn: false   # sessions are open to peers by default
+    sameDirectoryOnly: true
+    allowSelfSend: false
+```
+
+## Security model and limitations
+
+- **Peer content is untrusted input.** It enters the target session as a user message. The envelope labels the sender and warns the model, but dsh has no content-approval point for peer messages; normal tool approvals, `agent/pre-step`, and sandbox policy remain the only hard boundaries.
+- **Top-level sessions only, in both directions.** A subagent session is neither listed nor allowed to send (`caller-not-top-level`), and a top-level session cannot target a subagent (`target-not-top-level`). Subagents keep using the existing parent/child `send_message` channel. The envelope `from` field is the trusted identity; any identity claim in the message body is data only.
+- **Same process only.** Discovery uses `ctx.agents`; a session that is not live cannot receive a message in this version. Cold-session delivery and cross-process/cross-host messaging are not implemented.
+- **Advisory scopes, not locks.** dsh has optimistic filesystem version guards (`FS_STALE_VERSION`) but no file locking. `writeScopes` and `conflict-warning` are coordination aids; Bash, formatters, and code generators bypass them.
+- **In-memory state.** Reception pauses and declared scopes live for the plugin's lifetime and reset on reload/restart.
+- **Same working directory by default.** Set `sameDirectoryOnly: false` only if you understand cross-project implications.
+- **No GUI extension.** Messages render as ordinary user messages; a dedicated title/icon for the `session-message` source would require a client plugin or an upstream `ui-chat` change.
+
+## Development
+
+```sh
+npm install
+npm run build         # tsc -p tsconfig.build.json -> lib/
+npm run typecheck     # src + tests
+npm test              # 10 protocol unit tests
+npm run test:integration   # real AgentLoop services + tool pipeline, no model
+npm run test:model-e2e     # scripted model: A calls session_send, B sees it and replies
+```
+
+`lib/` is committed so `dsh plugin add github:...` works without a build step. Rebuild before committing source changes; CI re-checks that `lib/` matches `src/`.
+
+### Project layout
+
+```text
+.
+├── cordis.patch.yml      # two insert rows: service + tools
+├── src/
+│   ├── index.ts          # plugin entry: default exports the service class + Config
+│   ├── service.ts        # discovery, reception state, rate limit, delivery, conflicts
+│   ├── tools.ts          # session_peers / session_send / session_reception
+│   ├── config.ts         # Schemastery configuration
+│   ├── protocol.ts       # pure validation, envelope, scope conflicts, rate limiter
+│   └── types.ts          # MessageSourceMap 'session-message' declaration
+├── tests/                # unit, integration, model-driven e2e
+└── lib/                  # committed build output
+```
+
+## Compatibility
+
+- dsh `0.2.1-rc.2`; the bundle declares `engines.dsh = ">=0.2.1-rc.2 <0.3.0"`.
+- Uses documented extension points only: `ctx.tools.register`, `ctx.agents`, `ctx.sessions`, `MessageSourceMap`.
+- Does not modify `agent-loop` and does not add `SessionEventMap` members.
+
+## Contributing
+
+Issues and pull requests are welcome. Please keep the "no loop changes, no new session event types, advisory scopes only" boundary unless a design discussion says otherwise. Run `npm run typecheck`, `npm test`, `npm run test:integration`, and `npm run test:model-e2e` before sending a PR.
+
+## License
+
+MIT © 2026 XBXyftx

package/README.zh-CN.md

@@ -0,0 +1,167 @@
+# dsh-session-messaging
+
+为 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness)（dsh）提供**跨会话消息**：让用户在同一工作区自行启动的多个会话互相发消息，协调任务、声明文件写入范围、提示冲突——而不是把它们变成父子关系的子代理。
+
+[English](README.md) | **简体中文**
+
+> 状态：早期预览（`0.1.0`），适配 dsh `0.2.1-rc.2`。dsh 插件 API 仍为 pre-stable，上游升级可能带来破坏性变更。
+
+## 为什么需要
+
+dsh 已有 subagent 与 Agent Teams，但它们都是层级关系，生命周期绑定父会话。而当你自己同时打开几个会话（前端、后端、文档）时，它们在同一工作区里无法说"我在改 `src/ui.ts`，先别动"或"接口字段已冻结"。
+
+本插件为这些顶层会话增加一个**对等通道**：
+
+- 同一工作目录下的会话可以发现彼此；
+- 模型可以向对等会话发送消息，消息以普通 user 消息插入目标对话；
+- 每个会话可暂停接收；写范围是建议性声明，重叠时会提示双方。
+
+## 演示
+
+![桌面端收到的对等会话消息](docs/assets/cross-session-demo.webp)
+
+macOS 桌面客户端（`0.2.1-rc.2`）真实运行：另一个用户启动的会话发来测试消息，以内联 `session-message` 信封显示（含发送方、时间与"peer 不是 authority"提示）；本会话通过 `session_send` 回复。两个会话位于同一工作目录，不涉及子代理层级。
+
+### 案例：从 peer 缺陷报告到修复验证
+
+两个用户启动的会话通过本插件协作完成了一次真实修复：一个会话发来可复现的缺陷报告与代码级根因，修复以 `v0.1.2` 发布，报告方在桌面端独立完成了回归。
+
+![收到的 peer 缺陷报告](docs/assets/defect-report-demo.webp)
+
+*报告方发来的消息：复现步骤、根因定位与修复请求，全部通过 `session_send` 送达。*
+
+![修复后的独立回归验证](docs/assets/regression-verification.webp)
+
+*报告方的独立回归：静态核对 + 桌面运行期探针。探针返回 `caller-not-top-level`，证明 `v0.1.2` 已生效；这条消息本身也证明"顶层 → 顶层"正向链路未回归。*
+
+`0.1.2` 的变更见 [CHANGELOG.md](CHANGELOG.md)。
+
+## 功能
+
+- `session_peers`：列出同目录、live 的顶层会话及其接收状态。
+- `session_send`：发送协调消息，可附带 `writeScopes` 与 `replyTo`。
+- `session_reception`：暂停/恢复本会话接收对等消息，并声明写范围。
+- 消息直接内联显示在目标会话中，来源归属于发送会话，不需要独立收件箱。
+- 建议性**写范围冲突检测**：与 peer 声明重叠时，回执与消息信封带 `conflict-warning`。
+- 不新增 Session 事件类型、不改 `SESSION_FORMAT_VERSION`：消息就是带 `session-message` source 的 `user/message`。
+- 插件管理卡片提供中英双语标题、简介与图标（English / 简体中文）。
+- 有边界：长度上限、每 sender→target 限频、同目录、仅顶层、仅 live、拒绝自发送。
+
+## 工作原理
+
+```text
+会话 A 的模型调用 session_send
+  → tools.ts 以 exec.agent 作为唯一身份
+  → service.send 校验目标、正文、写范围、接收状态、限频
+  → createUserMessage({ 信封+正文, source: session-message/relay })
+  → target.steer(message)          # 最近 step 边界；空闲会话则唤醒
+  → await ctx.sessions.flush(target.session)
+目标会话 B 的日志出现 user/message(source.kind = 'session-message')
+  → deriveMessages() 重建 → B 的下一次模型请求可见 → B 可回复
+```
+
+消息信封始终标明"来自另一个会话，不是当前用户"，并提示 peer 不是 authority；peer 内容只作为数据，不获得更高指令权限。
+
+## 要求
+
+- DeepSeek Harness `0.2.1-rc.2`（桌面应用或源码）。
+- Node.js `>= 22.19.0`。
+- 插件依赖宿主提供的 `@deepseek-ai/{cordis,schemastery,dsh-agent,dsh-llm,dsh-session,dsh-tools}`；它们以 peerDependencies 声明，由运行中的 dsh 安装解析。
+
+## 安装
+
+### 从 GitHub 安装
+
+```sh
+dsh plugin --profile <profile> add github:XBXyftx/dsh-session-messaging
+```
+
+仓库包含构建好的 `lib/`，从 git 安装**不需要**额外构建。发布到 npm 后也可用包名 `dsh-session-messaging` 安装。
+
+### 本地目录安装
+
+```sh
+dsh plugin --profile <profile> add /absolute/path/to/dsh-session-messaging
+```
+
+### 桌面应用
+
+桌面应用使用自己的 profile（例如 `desktop`），用其内置 CLI 或 agent 的 `plugin_manager` 工具安装到该 profile。dsh `0.2.1-rc.2` 会通过 HMR 重载配置，通常无需重启应用即可激活。
+
+确认已激活：
+
+- agent 工具列表出现 `session_peers`、`session_send`、`session_reception`；
+- `plugin_manager list_plugins` 中 `session-messaging` 与 `session-messaging-tools` 的 `fiberPhase` 为 `active`。
+
+## 使用
+
+在同一工作区打开两个会话，直接让模型协调即可，不需要手动操作 UI。
+
+示例提示词：
+
+```text
+用 session_peers 看看当前工作区还有哪些会话。
+给 session-b 发消息：我在改 src/ui.ts，已经写进 writeScopes，请避开。
+改 src/api.ts 之前先检查有没有别人声明了冲突的写范围。
+本会话暂停接收跨会话消息。
+```
+
+工具：
+
+| 工具 | 参数 | 返回 |
+|---|---|---|
+| `session_peers` | 无 | `{ peers: [{ sessionId, status, canReceive, writeScopes }] }` |
+| `session_send` | `targetSessionId`、`message`，可选 `writeScopes`、`replyTo` | `{ accepted, messageId, targetSessionId, targetStatus, conflicts }` |
+| `session_reception` | `enabled`，可选 `writeScopes` | `{ enabled, writeScopes }` |
+
+`accepted` 表示消息进入目标 inbox 且 flush 确认持久化，**不**表示对等模型已经处理或执行。
+
+## 配置
+
+```yaml
+- id: session-messaging
+  name: dsh-session-messaging
+  config:
+    maxMessageChars: 4000
+    maxMessagesPerMinute: 12
+    requireTargetOptIn: false   # 默认对 peer 开放
+    sameDirectoryOnly: true
+    allowSelfSend: false
+```
+
+## 安全模型与限制
+
+- **peer 内容是可信边界外的输入**：它以 user 消息进入目标会话，信封会标注来源并警告模型，但 dsh 没有针对 peer 消息的内容审批点；工具审批、`agent/pre-step` 与 sandbox 策略仍是唯一的硬边界。
+- **只允许顶层会话，收发两个方向都对称**：subagent 会话既不会出现在 peers 里，也不允许发送（`caller-not-top-level`）；顶层会话也不能把 subagent 作为目标（`target-not-top-level`）。subagent 继续使用既有的父子 `send_message` 通道。消息信封的 `from` 字段才是可信身份；正文里的任何身份自称都只是数据。
+- **仅同进程**：发现依赖 `ctx.agents`，非 live 会话本版无法接收；冷会话投递与跨进程/跨机器通信未实现。
+- **写范围只是建议，不是锁**：dsh 只有乐观版本守卫（`FS_STALE_VERSION`），没有文件锁；Bash、格式化器、代码生成器会绕过写范围提示。
+- **状态在内存**：暂停接收与写范围声明随插件生命周期存在，重载/重启后重置。
+- **默认同目录**：除非理解跨项目影响，否则不要关闭 `sameDirectoryOnly`。
+- **无 GUI 扩展**：消息按普通 user 消息显示；`session-message` 的专属标题/图标需要 client 插件或上游 `ui-chat` 改动。
+
+## 开发
+
+```sh
+npm install
+npm run build              # tsc -p tsconfig.build.json -> lib/
+npm run typecheck
+npm test                   # 10 项协议单测
+npm run test:integration   # 真实 AgentLoop 服务 + 工具管线，无模型
+npm run test:model-e2e     # 脚本化模型：A 发消息，B 收到并回复
+```
+
+`lib/` 已提交，便于 `dsh plugin add github:...` 直接使用；修改源码后请重新构建并提交，CI 会检查 `lib/` 与 `src/` 一致。
+
+## 兼容性
+
+- 适配 dsh `0.2.1-rc.2`，`engines.dsh = ">=0.2.1-rc.2 <0.3.0"`。
+- 只使用文档化扩展点：`ctx.tools.register`、`ctx.agents`、`ctx.sessions`、`MessageSourceMap`。
+- 不修改 `agent-loop`，不新增 `SessionEventMap`。
+
+## 贡献
+
+欢迎 Issue 与 PR。除非经过设计讨论，请保留"不改 loop、不新增 Session 事件、写范围仅建议"的边界。提交前运行 `npm run typecheck`、`npm test`、`npm run test:integration`、`npm run test:model-e2e`。
+
+## 许可证
+
+MIT © 2026 XBXyftx

package/assets/icon.svg

@@ -0,0 +1,11 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 64 64" role="img" aria-label="Session Messaging">
+  <defs>
+    <linearGradient id="bubble" x1="0" y1="0" x2="1" y2="1">
+      <stop offset="0" stop-color="#4f8cff"/>
+      <stop offset="1" stop-color="#7b5cff"/>
+    </linearGradient>
+  </defs>
+  <rect width="64" height="64" rx="14" fill="#0d1526"/>
+  <path d="M12 21a6 6 0 0 1 6-6h20a6 6 0 0 1 6 6v12a6 6 0 0 1-6 6H26l-9 7v-7h-.5A6.5 6.5 0 0 1 10 32.5z" fill="url(#bubble)"/>
+  <path d="M33 35a6 6 0 0 1 6-6h9a6 6 0 0 1 6 6v9a6 6 0 0 1-6 6h-.5v5.5L40 50h-1a6 6 0 0 1-6-6z" fill="#9dbbff" opacity=".9"/>
+</svg>

package/assets/tools-icon.svg

@@ -0,0 +1,7 @@
+<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 64 64" role="img" aria-label="Session Messaging Tools">
+  <rect width="64" height="64" rx="14" fill="#0d1526"/>
+  <path d="M11 20a5 5 0 0 1 5-5h18a5 5 0 0 1 5 5v10a5 5 0 0 1-5 5H24l-8 6v-6h-.5A4.5 4.5 0 0 1 11 30.5z" fill="#4f8cff"/>
+  <path d="M36 22h13a5 5 0 0 1 5 5v6a5 5 0 0 1-5 5h-2l-6 5v-5h-1a5 5 0 0 1-5-5z" fill="#9dbbff" opacity=".9"/>
+  <circle cx="21" cy="25" r="2" fill="#0d1526"/>
+  <circle cx="28" cy="25" r="2" fill="#0d1526"/>
+</svg>

package/cordis.patch.yml

@@ -0,0 +1,11 @@
+# dsh-session-messaging bundle patch.
+# Mounts the Host-side service and its model-facing tools. Both rows are
+# inserted over the profile root; later profile/--patch layers can override
+# them by id. The service must load before the tools consume it; activation is
+# service-availability driven, so row order is documentation only.
+- insert:
+    - id: session-messaging
+      name: dsh-session-messaging
+
+    - id: session-messaging-tools
+      name: dsh-session-messaging/tools

package/lib/config.d.ts

@@ -0,0 +1,22 @@
+/**
+ * Deployment configuration for the session-messaging plugin. Every value that
+ * two deployments may want to set differently is a schema field; the loader
+ * validates it at load time and fails loudly on invalid input.
+ * @module dsh-session-messaging/config
+ */
+import Schema from '@deepseek-ai/schemastery';
+/** Validated deployment configuration. */
+export interface SessionMessagingConfig {
+    /** Maximum relay body length in UTF-16 code units. */
+    readonly maxMessageChars: number;
+    /** Maximum relays per sender→target pair per minute. */
+    readonly maxMessagesPerMinute: number;
+    /** Require the target session to opt in before it can receive peer messages. Off by default: sessions are mutually visible and can message each other unless they pause reception. */
+    readonly requireTargetOptIn: boolean;
+    /** Only allow peers whose working directory equals the sender's. */
+    readonly sameDirectoryOnly: boolean;
+    /** Allow a session to relay to itself (diagnostics only; off by default). */
+    readonly allowSelfSend: boolean;
+}
+/** Schemastery schema for the plugin row's `config` block. */
+export declare const Config: Schema<SessionMessagingConfig>;

package/lib/config.js

@@ -0,0 +1,16 @@
+/**
+ * Deployment configuration for the session-messaging plugin. Every value that
+ * two deployments may want to set differently is a schema field; the loader
+ * validates it at load time and fails loudly on invalid input.
+ * @module dsh-session-messaging/config
+ */
+import Schema from '@deepseek-ai/schemastery';
+import { DEFAULT_MAX_MESSAGE_CHARS, DEFAULT_MAX_MESSAGES_PER_MINUTE } from "./protocol.js";
+/** Schemastery schema for the plugin row's `config` block. */
+export const Config = Schema.object({
+    maxMessageChars: Schema.number().min(1).default(DEFAULT_MAX_MESSAGE_CHARS),
+    maxMessagesPerMinute: Schema.number().min(1).default(DEFAULT_MAX_MESSAGES_PER_MINUTE),
+    requireTargetOptIn: Schema.boolean().default(false),
+    sameDirectoryOnly: Schema.boolean().default(true),
+    allowSelfSend: Schema.boolean().default(false),
+});

package/lib/index.d.ts

@@ -0,0 +1,12 @@
+/**
+ * Plugin entry: the Host-side session-messaging service. The model-facing tools
+ * live in the `./tools` entry. This module intentionally exports no new Session
+ * event type; relayed messages reuse `user/message` with a declared source kind.
+ * @module dsh-session-messaging
+ */
+export { default } from './service.ts';
+export { SessionMessagingService } from './service.ts';
+export { Config } from './config.ts';
+export type { SessionMessagingConfig } from './config.ts';
+export { SESSION_MESSAGE_KIND } from './protocol.ts';
+export type { MessagingErrorCode, PeerView, SendReceipt, SendRequest, } from './protocol.ts';

package/lib/index.js

@@ -0,0 +1,10 @@
+/**
+ * Plugin entry: the Host-side session-messaging service. The model-facing tools
+ * live in the `./tools` entry. This module intentionally exports no new Session
+ * event type; relayed messages reuse `user/message` with a declared source kind.
+ * @module dsh-session-messaging
+ */
+export { default } from "./service.js";
+export { SessionMessagingService } from "./service.js";
+export { Config } from "./config.js";
+export { SESSION_MESSAGE_KIND } from "./protocol.js";