@y9931666/dsh-plugin-roundtable 1.0.0-rc.2

package/lib/types/client/slot-boundary.d.ts

@@ -0,0 +1,49 @@
+/**
+ * Render-failure boundary for the two RoundTable slot entries.
+ *
+ * WHY THIS EXISTS (v0.2.36): DSH retires a slot entry that throws during render
+ * (`onEntryError` + abdication) — correct isolation, but for the user the 圆桌
+ * 会议 tab simply is not there, with no message anywhere. That silent
+ * disappearance is exactly the shape the "界面调不出来" reports arrived in, and
+ * it is undiagnosable from the outside.
+ *
+ * Wrapping each entry in a boundary turns a crash into a readable panel naming
+ * the error, and mirrors it to the browser console with the component stack.
+ * The boundary deliberately renders NO data of its own, so it cannot become a
+ * second failure source; the panel is swapped out as soon as React re-renders
+ * a healthy tree after a reload.
+ *
+ * @module dsh-plugin-roundtable/client/slot-boundary
+ */
+import { Component, type ComponentType, type ErrorInfo, type ReactNode } from 'react';
+/** The inject face every RoundTable slot entry receives (see client/index.ts). */
+export interface SlotEntryFace {
+    /** Locale-bound translator for the `roundtable` namespace. */
+    t?: (key: string) => string;
+}
+interface SlotBoundaryProps {
+    title: string;
+    hint: string;
+    children?: ReactNode;
+}
+interface SlotBoundaryState {
+    error: Error | null;
+}
+/** Class-component boundary (React only catches render errors in class components). */
+export declare class SlotBoundary extends Component<SlotBoundaryProps, SlotBoundaryState> {
+    state: SlotBoundaryState;
+    static getDerivedStateFromError(error: Error): SlotBoundaryState;
+    componentDidCatch(error: Error, info: ErrorInfo): void;
+    render(): ReactNode;
+}
+/**
+ * Wrap one slot component so a render crash renders a report instead of
+ * vanishing. The inner component keeps receiving every prop it got before
+ * (owner share + standard seats + the inject face), so this is transparent on
+ * the happy path.
+ *
+ * @param Inner - the registered slot component.
+ * @returns a component with the same props contract.
+ */
+export declare function withSlotBoundary<P extends object>(Inner: ComponentType<P>): ComponentType<P>;
+export {};

package/lib/types/client/tool-views-model.d.ts

@@ -0,0 +1,65 @@
+/**
+ * `roundtable_status` tool view 的纯逻辑（第 4 批）。
+ *
+ * 与渲染分离的原因很实际：Node 的类型剥离**不支持 JSX**，所以放在 `.tsx` 里的
+ * 解析函数无法被零依赖单测直接 import。这里只留可测的判定，组件（tool-views.tsx）
+ * 只负责画。
+ *
+ * @module @y9931666/dsh-plugin-roundtable/client/tool-views-model
+ */
+/** Structural view of the owner block this view needs (no host type import). */
+export interface ToolBlockLike {
+    kind?: string;
+    isError?: boolean;
+    call?: {
+        name?: string;
+        argsRaw?: string;
+    } | null;
+    content?: readonly {
+        type?: string;
+        text?: string;
+    }[];
+}
+/** Parsed subset of one `roundtable_status` payload. */
+export interface StatusPayload {
+    meeting_name?: unknown;
+    mode?: unknown;
+    status?: unknown;
+    round?: unknown;
+    budget?: {
+        used_tokens?: unknown;
+        max_tokens?: unknown;
+        max_rounds?: unknown;
+    } | null;
+    nodes?: readonly {
+        key?: unknown;
+        status?: unknown;
+        activity?: unknown;
+        last_error?: unknown;
+    }[] | null;
+    pending_decisions?: readonly unknown[] | null;
+    pending_actions?: readonly unknown[] | null;
+}
+/** Flatten the text blocks of a settled tool result. */
+export declare function blockTextOf(block: unknown): string;
+/**
+ * Parse a `roundtable_status` result; `null` when it is anything else.
+ *
+ * Deliberately claims only this tool's own shape: a payload without a string
+ * `meeting_name` falls back to the generic rendering rather than being forced
+ * into a card that would show blanks.
+ */
+export declare function parseStatusPayload(text: string): StatusPayload | null;
+/** Display a payload field without ever printing `undefined`. */
+export declare function fieldText(value: unknown): string;
+/**
+ * One expert node line: `key status/activity`, plus the failure note the node
+ * left behind (`last_error` is what makes "这位专家到底跑起来了没有" answerable,
+ * and `missing` means the host no longer knows that subagent at all).
+ */
+export declare function nodeLine(node: {
+    key?: unknown;
+    status?: unknown;
+    activity?: unknown;
+    last_error?: unknown;
+}): string;

package/lib/types/client/tool-views.d.ts

@@ -0,0 +1,31 @@
+/**
+ * `roundtable_status` 的专属渲染（第 4 批）。
+ *
+ * 注册在 `tool.call.toolview` 上，key 是本插件自己的工具名。宿主的 key 域是
+ * 开放的（"any wire tool name, **including a tool your own package registered**"），
+ * 且"registering is **additive** for your own tool" —— 未认领的 key 才回退到
+ * 通用 tool 行。owner 传入的是**已冻结的运行中/已结算节点**，所以这个视图是
+ * turn 已知内容的纯函数，无状态。
+ *
+ * 取数：settled 调用是 `ToolResultNode`（`content: ContentBlock[]`），running 时
+ * 只有 `argsRaw`。解析失败**一律回退为纯文本**——绝不显示空白卡片，那会比通用
+ * tool 行更糟。纯逻辑在 tool-views-model.ts（JSX 无法被零依赖测试直接加载）。
+ *
+ * @module @y9931666/dsh-plugin-roundtable/client/tool-views
+ */
+import { type StatusPayload } from './tool-views-model.ts';
+/** Card body for a parsed status payload. */
+export declare function StatusCard({ data }: {
+    data: StatusPayload;
+}): JSX.Element;
+/**
+ * Tool view for `roundtable_status`.
+ *
+ * Renders the card when the result parses, otherwise falls back to the raw
+ * text (and to `null` when there is nothing at all — the host's own call row
+ * still shows the running call).
+ */
+export declare function RoundTableStatusView(props: {
+    block?: unknown;
+    toolName?: string;
+}): JSX.Element | null;

package/lib/types/client/wire.d.ts

@@ -0,0 +1,238 @@
+/**
+ * Wire types shared by the browser topology tab: the meeting snapshot served
+ * by `/plugins/dsh-plugin-roundtable/state` and the RPC result envelope.
+ * @module dsh-plugin-roundtable/client/wire
+ */
+/** One RPC response envelope (structurally compatible with the host's RpcResult). */
+export type RpcEnvelope<T> = {
+    ok: true;
+    value: T;
+    error?: never;
+} | {
+    ok: false;
+    error: {
+        code: string;
+        message: string;
+        details?: unknown;
+    };
+    value?: never;
+};
+/** A tiny typed RPC caller over the plugin's own web route. */
+export type RpcCaller = <T>(endpoint: string, payload: unknown) => Promise<RpcEnvelope<T>>;
+/**
+ * POST one RPC call to the plugin's OWN web route.
+ *
+ * That route is mounted through the same `webServer` registration as the
+ * snapshot route, so the browser reaches it even when the host's generic
+ * connection channel is not mounted — which is what made the settings page
+ * report 「读取设置失败」. An unreachable or malformed answer is reported as a
+ * failure envelope instead of a rejected promise.
+ */
+export declare function callRpc<T>(endpoint: string, payload: unknown, signal?: AbortSignal): Promise<RpcEnvelope<T>>;
+export interface WireNode {
+    id: string;
+    key: string;
+    role: string;
+    provider: string;
+    model: string;
+    status: string;
+    activity: string;
+}
+export interface WireEdge {
+    id: string;
+    from: string;
+    to: string;
+    direction: string;
+}
+export interface WireBudget {
+    maxRounds: number;
+    maxTokens: number;
+    usedRounds: number;
+    usedTokens: number;
+    /** 第 3 批：provider 上报的真实用量（0 = 此刻不可测）。 */
+    usedTokensReal?: number;
+}
+export interface WirePendingDecision {
+    id: string;
+    question: string;
+    options: string[];
+}
+/** One pending user action recorded by the Web UI, awaiting the captain. */
+export interface WirePendingAction {
+    id: string;
+    kind: string;
+    nodeKey: string;
+    role: string;
+    provider: string;
+    model: string;
+    text: string;
+}
+/** Model entry for the expert-management dropdown (from host llm catalog). */
+export interface WireModelOption {
+    id: string;
+    name: string;
+}
+/** Provider entry with its advertised models for the expert-management dropdown. */
+export interface WireProviderOption {
+    id: string;
+    name: string;
+    models: WireModelOption[];
+}
+export interface WireMessage {
+    id: string;
+    from: string;
+    to: string;
+    ts: number;
+}
+/** One knowledge-base directory entry (阅览版: name/kind/format/size only). */
+export interface WireKbEntry {
+    name: string;
+    kind: 'file' | 'dir';
+    ext: string;
+    size: number;
+    mtimeMs: number;
+}
+/** Knowledge-base listing returned by `roundtable/kb.list`. */
+export interface WireKbListing {
+    path: string;
+    configured: boolean;
+    error: string;
+    files: WireKbEntry[];
+}
+/** 观点证据分级（C1）：repro=可复现步骤；argument=论证链。 */
+export interface WireReviewEvidence {
+    kind: 'repro' | 'argument';
+    text: string;
+}
+/** 针锋相对评审：一个观点（V0.2.2 三态 + 拆分）。 */
+export interface WireReviewViewpoint {
+    id: string;
+    utteranceId: string;
+    nodeKey: string;
+    content: string;
+    /** 三态：pending/endorsed/rejected。 */
+    status: 'pending' | 'endorsed' | 'rejected';
+    /** 兼容派生（旧视图仍可读）：status === 'endorsed'。 */
+    endorsed: boolean;
+    /** 派生：status === 'rejected'。 */
+    rejected: boolean;
+    /** 驳回理由（C2：驳回必填；前端在 rejected 状态下展示）。 */
+    rejectReason?: string;
+    /** 证据分级（C1）。 */
+    evidence?: WireReviewEvidence;
+    /** 原文引用子串（拆分观点可能有）。 */
+    quote?: string;
+    /** 维度标签（默认"其他"）。 */
+    dimension: string;
+    /** 发言内序号：0=整条未拆分。 */
+    seq: number;
+}
+/** 针锋相对评审记录（快照携带，前端弹窗数据源）。 */
+export interface WireReview {
+    status: string;
+    reviewPass: number;
+    maxReviewPass: number;
+    question: string;
+    plan: string;
+    viewpoints: WireReviewViewpoint[];
+}
+/** 一条匿名反馈（E1/E3：设置页列表展示）。 */
+export interface WireFeedbackEntry {
+    id: string;
+    ts: number;
+    meetingId: string;
+    mode: string;
+    providers: string[];
+    models: string[];
+    usedRounds: number;
+    usedTokens: number;
+    rating: 'good' | 'meh' | 'bad';
+    note?: string;
+}
+export interface WireUtterance {
+    id: string;
+    from: string;
+    to: string;
+    text: string;
+    ts: number;
+    round: number;
+}
+export interface WireMeeting {
+    id: string;
+    name: string;
+    goal: string;
+    mode: string;
+    status: string;
+    round: number;
+    workspace: string;
+    captainSessionId: string;
+    /** 知识库目录（阅览版）；空 = 未设置。 */
+    kbPath: string;
+    /** R2：本次会议选中的 skill 名称清单；空 = 未选。 */
+    skills: string[];
+    /** R2.2/D5：skill 传递方式（relay / direct）。 */
+    skillDelivery: string;
+    budget: WireBudget;
+    nodes: WireNode[];
+    edges: WireEdge[];
+    pendingDecisions: WirePendingDecision[];
+    pendingActions: WirePendingAction[];
+    review: WireReview | null;
+    digest: string;
+    messages: WireMessage[];
+    recent: WireUtterance[];
+}
+/** B3 用户自建角色预设（设置页维护；专家管理面板一键填充）。
+ *  与 host `types.ts` 的 `RolePreset` 逐字对应。 */
+export interface WireRolePreset {
+    id: string;
+    name: string;
+    role: string;
+    /** 可选 provider 路由；必须与 model 同时存在才生效。 */
+    provider?: string;
+    /** 可选模型名；空 = 继承主持人。 */
+    model?: string;
+}
+/** B3+ 阵容预设的一位成员（与 host `types.ts` 的 `RoleSquadMember` 对应）。
+ *  阵容只回答"请哪几位专家"，不描述会议怎么开。 */
+export interface WireRoleSquadMember {
+    key: string;
+    role: string;
+    provider?: string;
+    model?: string;
+}
+/** B3+ 阵容预设（一次套用多位专家）。 */
+export interface WireRoleSquad {
+    id: string;
+    name: string;
+    members: WireRoleSquadMember[];
+}
+export interface RoundTablePrefs {
+    defaultMode: 'orchestrated' | 'egalitarian' | 'redteam';
+    maxRounds: number;
+    maxTokens: number;
+    /** 互通开关：true=显示所有圆桌会议；false=仅显示当前对话开启的会议。 */
+    showAllMeetings: boolean;
+    /** 专家每轮输出 token 上限（模型请求 max_tokens），0 = 不限制。 */
+    expertMaxTokens: number;
+    /** 专家每轮最多提几条意见，0 = 不限制。 */
+    expertMaxOpinions: number;
+    /** E1/E4 反馈：会议结束后是否询问轻量反馈；false = 永久关闭。 */
+    feedbackEnabled: boolean;
+    /** R2.2/D5：skill 传递方式（relay=主持人中转；direct=专家自行调用）。 */
+    skillDelivery: 'relay' | 'direct';
+    /** R3：右栏隐藏的面板 id 清单；空 = 全部显示。 */
+    hiddenPanels: string[];
+    /** A1：画布图例已被用户关闭（true = 不显示）。默认 false。 */
+    legendHidden: boolean;
+    /** B3：用户自建角色预设（全局；不预置内置角色）。 */
+    rolePresets: WireRolePreset[];
+    /** B3+：用户自建阵容预设（全局；不预置内置阵容）。 */
+    squads: WireRoleSquad[];
+}
+/**
+ * Poll the meeting snapshot. Without a session id the host lists every
+ * meeting under every workspace (互通开); with one it filters by captain
+ * session (互通关 — only meetings started by the current conversation).
+ */
+export declare function fetchMeetings(sessionId?: string): Promise<WireMeeting[]>;

package/lib/types/edge-helper.d.ts

@@ -0,0 +1,7 @@
+/**
+ * Locate the workspace directory owning a meeting directory (used by the RPC
+ * edge.set path, which arrives without a session context).
+ * @module dsh-plugin-roundtable/edge-helper
+ */
+/** Find the first workspace whose state root contains the given meeting. */
+export declare function workspaceOfMeeting(stateDir: string, meetingId: string): Promise<string | undefined>;

package/lib/types/harness-compat.d.ts

@@ -0,0 +1,204 @@
+/**
+ * 宿主兼容与能力边界（Host compatibility boundary）。
+ *
+ * **所有与 DSH 版本相关的形状都集中在这个文件里。**
+ * 理由与做法直接借鉴社区项目 dsh-agent-teams 的 `src/harness-compat.ts`：
+ *
+ * > Keep version-specific shapes here: **API presence alone is not a promise of
+ * > support for future versions.**
+ *
+ * 我们的宿主是 **rc 线**（0.1.5-rc.2 → rc.3 → **0.2.0-rc.2**；`0.1.6-alpha.*`
+ * 是另一条未纳入的线），API 尚未冻结，破坏性变更属于常态 —— 0.2.0-rc.2 一轮
+ * 就动了两处真正破坏兼容的地方。所以在写任何 `ctx.get(...)` / `ctx.on(...)` /
+ * 服务方法调用之前，先问一句：**这个形状在别的 rc 上还成立吗？** 如果答案需要翻
+ * 源码，那它就应该写进本文件，而不是散进业务代码。
+ *
+ * 每轮升级的实测结论记在文末「6. 宿主契约变更实录」—— 那是本文件最值钱的部分。
+ *
+ * 两条铁律：
+ *   1. **探测绝不成为新的加载门禁**。这里没有 `inject`、没有静态导入宿主包，
+ *      缺失的能力一律降级（记录进审计表）——v0.2.36 的「整个界面消失」事故
+ *      就是可选能力被当成必需能力造成的。
+ *   2. **降级要留痕**。每个能力第一次被探测时记一条审计，`roundtable_status`
+ *      与 `scripts/doctor.mjs` 都能把它打出来，让"为什么某个功能没生效"
+ *      有一个能查的答案，而不是靠猜。
+ *
+ * @module dsh-plugin-roundtable/harness-compat
+ */
+import type { Context } from '@deepseek-ai/cordis';
+/**
+ * 插件**要求**宿主提供的服务能力：少一个就装不起来。
+ *
+ * 这个数组必须与 `src/index.ts` 的 `inject`、`compatibility.json` 的
+ * `capabilities` 三者逐字一致 —— `scripts/compatibility.mjs` 会校验，
+ * 不一致直接失败。这样"支持哪些宿主"只有一处真话。
+ */
+export declare const REQUIRED_CAPABILITIES: readonly ["tools", "subagents", "agents", "systemPrompt"];
+/** 可选能力：缺失只降级，绝不阻断加载。 */
+export declare const OPTIONAL_CAPABILITIES: readonly ["connection", "llm", "skills", "userQuestions", "sessionProjections", "webServer", "workspaceRegistry"];
+/** 一个能力探测点的静态描述。 */
+export interface CapabilitySpec {
+    id: string;
+    kind: 'required' | 'optional';
+    /** 用来做什么。 */
+    purpose: string;
+    /** 缺失（或形状不符）时发生什么 —— 这一栏是运维价值的核心。 */
+    whenMissing: string;
+    /** 版本相关的证据说明。 */
+    evidence: string;
+}
+/**
+ * 本插件触碰过的**每一个**宿主能力探测点。
+ *
+ * 加新的探测点时同时更新这里：`scripts/doctor.mjs` 与
+ * `test/compatibility.test.mjs` 都以本表为准，漏登记会被测试拦下。
+ */
+export declare const CAPABILITY_SPECS: readonly CapabilitySpec[];
+/** 一次能力探测的结果。 */
+export type CapabilityState = 'not_probed' | 'available' | 'missing' | 'degraded';
+/** 审计表里的一条。 */
+export interface CapabilityAudit {
+    state: CapabilityState;
+    /** 人类可读的一句话，说明探测到了什么或为什么降级。 */
+    note: string;
+    ts: number;
+}
+/** 当前审计快照（给 roundtable_status / doctor 用）。 */
+export declare function capabilityAudit(): ReadonlyMap<string, CapabilityAudit>;
+/** 渲染成紧凑的一行行文本（诊断输出用）。 */
+export declare function formatCapabilityAudit(): string;
+/**
+ * 记录一次探测结果（**每个能力只保留第一条**）。
+ *
+ * 只记第一条是刻意的：探测点常在 tick / 轮询路径上，每次都记会把内存和日志
+ * 都吃掉；而"第一次看到它是什么状态"已经足够定位问题。
+ */
+export declare function noteCapability(id: string, state: CapabilityState, note: string): CapabilityState;
+/** 测试用：清空审计表。 */
+export declare function resetCapabilityAudit(): void;
+/**
+ * 读一个**可选**宿主服务。
+ *
+ * 统一走 `ctx.get`（cordis 核心、非严格：缺失返回 `undefined`）而不是属性访问
+ * —— 后者在没有 `inject` 时会**直接抛错**：
+ * `cannot get property "connection" without inject`。
+ */
+export declare function optionalService<T>(ctx: Context, name: string): T | undefined;
+/** 可选服务键的结构式候选（宿主可能改名；按序取第一个可用的）。 */
+export declare const WEB_SERVER_KEYS: readonly ["webServer", "httpServer"];
+export declare const WORKSPACE_KEYS: readonly ["workspaceRegistry", "workspace"];
+/** webServer 服务面（只声明我们真正调用的部分）。
+ *
+ *  `register` 的返回值刻意只声明为 `() => void`：宿主不同 rc 上返回过
+ *  disposer 与 `unknown`，而调用处一律以 `ctx.effect(() => webServer.register(…))`
+ *  的形式**忽略返回值**——effect 自带卸载。声明成 `unknown` 会让
+ *  `ctx.effect` 的重载解析失败（它要求回调返回具体 Effect，不接受 unknown），
+ *  所以这里保留"当它是清理函数"的写法。 */
+export interface WebRouteHost {
+    register(route: {
+        kind: 'exact';
+        path: string;
+        handler: (req: import('node:http').IncomingMessage, res: import('node:http').ServerResponse) => Promise<void> | void;
+    }): () => void;
+}
+/** workspace 注册表面。 */
+export interface WorkspaceListHost {
+    list(): {
+        title: string;
+        path: string;
+    }[];
+}
+/**
+ * 解析 webServer 服务面。
+ *
+ * 服务键是**结构式候选**而非固定名：宿主可能把 `webServer` 换成别的名字，
+ * 所以按 `WEB_SERVER_KEYS` 顺序探测。headless profile 下取不到属预期，
+ * 只降级不报错。
+ */
+export declare function webRouteHostOf(ctx: Context): WebRouteHost | undefined;
+/** 解析 workspace 注册表面（同上，结构式候选 + 降级留痕）。 */
+export declare function workspaceRegistryOf(ctx: Context): WorkspaceListHost | undefined;
+/**
+ * 判定一个 `rpc.handle(...)` 返回值能不能当清理函数用。
+ *
+ * 宿主签名在 rc 线上变过：0.1.1 时代第三参 `{ authority }` 被移除，返回值在
+ * 不同版本里出现过 `disposer` / `undefined` / Promise。这里只做**形状判定**，
+ * 不 import 宿主类型：合法就交出去，不合法就交给调用方记一条降级。
+ */
+export declare function asDisposer(value: unknown): (() => void) | undefined;
+/**
+ * 在可选的清理函数存在时注册一个 effect。
+ *
+ * `connection.rpc.handle` 的返回值形状随版本变化，直接 `ctx.effect(() => () =>
+ * release())` 会在返回值不是函数时静默留下一个永远不执行的清理器（通道泄漏）。
+ */
+export declare function effectWithOptionalDisposer(ctx: {
+    effect(callback: () => () => void, label?: string): unknown;
+}, disposer: unknown, label: string): boolean;
+/** 投影读取面：宿主只暴露 `snapshot(session, keys)`。 */
+export interface ProjectionReadFace {
+    snapshot(session: unknown, keys: string[]): {
+        values?: Record<string, unknown>;
+    } | undefined;
+}
+/**
+ * 读一个 live session 的投影值。
+ *
+ * **返回 `undefined`，绝不抛错**：测量用量是观察行为，不能因为宿主投影形状
+ * 变化就把 `roundtable_status` 弄崩 —— 与 `token-usage.ts` 的既有契约一致。
+ */
+export declare function projectionValuesOf(ctx: Context, session: unknown): Record<string, unknown> | undefined;
+/**
+ * ## 0.2.0-rc.2 —— 两处真破坏（核对日期 2026-09-30）
+ *
+ * 从 0.1.5-rc.3 抬到 0.2.0-rc.2 后，**宿主侧 `tsc` 只有 4 个错误**，浏览器侧 0 个。
+ * 4 个错误归为两类，两类都不是「改一行签名」能解决的。
+ *
+ * ### ① `settings` 服务被重构成 `SettingsForms`
+ *
+ * | | 0.1.5-rc.3 | 0.2.0-rc.2 |
+ * | --- | --- | --- |
+ * | 形状 | `SettingsScope`：插件注册自己的命名空间 | `SettingsForms`：把 profile 配置投影成表单 |
+ * | API | `settings.register(ns, schema, { base })` | `configure` / `describe` / `update` / `replace` / `mutate` |
+ * | 插件自管偏好 | `scope.get` / `update` / `watch` | **没有对应物** |
+ *
+ * 编译期症状：
+ *   `Property 'register' does not exist on type 'SettingsForms'`
+ *   `Module '"@deepseek-ai/dsh-settings"' has no exported member 'SettingsScope'`
+ *
+ * **应对**：偏好改为自持久化（`src/preferences.ts` →
+ * `<DSH_HOME>/roundtable/preferences.json`），并同步从 `OPTIONAL_CAPABILITIES`、
+ * `CAPABILITY_SPECS`、`compatibility.json` 三处移除 `settings`。
+ *
+ * ⚠️ **不要再试图用 `ctx.inject(['settings'])` 注册命名空间** —— 那个能力在新模型
+ * 里不存在。插件现在的可配置面是它自己的 Cordis `Config`（Loader YAML 提供、宿主
+ * 自动生成配置页），而写 `Config` 会触发 entry 重载，不适合承载"改一个偏好"。
+ *
+ * ### ② `MessageSourceMap` 不再有 catch-all 的 `plugin` kind
+ *
+ * 基础表只剩 `user` / `model` / `tool` / `system-prompt`，其余由**生产者在自己
+ * 的模块里** `declare module '@deepseek-ai/dsh-llm'` 补上 —— 宿主内部插件
+ * （`tool-registry`、`ptc-mode`、`agent-message`、`subagent-settled` …）都是这么做的。
+ * 原文注释写得很直白：**"there is no shared catch-all `plugin` kind"**。
+ *
+ * 编译期症状：
+ *   `Type '"plugin"' is not assignable to type '"user" | "model" | "tool" | …'`
+ *
+ * **应对**：`src/members.ts` 自声明 `roundtable` kind（`{ kind: 'roundtable'; plugin: string }`），
+ * 而不是退化成匿名的 `user` —— 转录消费者需要把"插件注入的提示"与"用户说的话"分开。
+ *
+ * ### 保持不变的（本轮逐项复核确认）
+ *
+ * `inject` 的四个必需服务、`ctx.subagents` 的派发与 `interruptByParent`、
+ * `ctx.agents.get`、`subagent/end` 与 `agent/request-error` 事件、
+ * `webServer.register` 的形状、`connection.rpc.handle` 的两参签名与 disposer
+ * 返回值、`ctx.skills` / `ctx.userQuestions` / `sessionProjections.snapshot(session, keys)`、
+ * 以及全部浏览器侧槽位（`conversation.view` / `settings.section` /
+ * `tool.call.toolview`）—— 一律原样可用。
+ *
+ * ### 环境侧的老教训仍然有效
+ *
+ * 升级后**先跑 `node scripts/doctor.mjs`**：cordis 必须是同一物理副本，否则
+ * `declare module` 合并失效，会出现几十处「Context 上不存在某属性」的假故障，
+ * 看起来像 API 全崩。本轮 doctor 一次通过（混装 ✓ / cordis 同一性 ✓）。
+ */

package/lib/types/index.d.ts

@@ -0,0 +1,53 @@
+/**
+ * RoundTable for DeepSeek Harness — host plugin entry.
+ *
+ * A host-plane plugin that registers the `roundtable_*` tools and one usage
+ * section into the global system prompt. After installation any session can
+ * run a visualized round-table meeting through natural language: the model
+ * creates a meeting (it becomes the captain), adds expert nodes as durable
+ * continuable subagents, wires directed edges, collects contributions through
+ * the aggregation gateway, and asks the human when a decision is needed.
+ * The Web GUI shows the meeting as a topology tab via the `conversation.view`
+ * slot, fed by the `/plugins/dsh-plugin-roundtable/state` snapshot route.
+ *
+ * @module dsh-plugin-roundtable
+ */
+import type { Context } from '@deepseek-ai/cordis';
+import z from '@deepseek-ai/schemastery';
+export declare const name = "roundtable";
+/**
+ * REQUIRED services only — and the list is load-gating, which is why it is
+ * short. cordis has no "optional inject" form (`Inject` is `string[] | Record`
+ * and the record form is only intercept config), so every name listed here
+ * keeps the whole plugin fiber PENDING until that service exists: no
+ * `roundtable_*` tools, no `/plugins/dsh-plugin-roundtable/*` routes and no GUI
+ * tab. A missing OPTIONAL capability listed here therefore presents to the user
+ * as "圆桌会议整个不见了 / 无法调用界面" with no error anywhere.
+ *
+ * `userQuestions` and `skills` are deliberately NOT listed: both are optional
+ * capabilities that the plugin reads live through `ctx.get(...)`:
+ *   - skills.ts hard constraint #1 — the plugin MUST load in a profile without
+ *     the skill service and degrade to an empty catalog;
+ *   - tools.ts falls back to `decision: 'unavailable'` when the userQuestions
+ *     service is absent (the captain then states the draft in words).
+ * v0.2.36 removed both from this list; v0.2.21 had already fixed the mirrored
+ * over-constraint on the browser half (`connection`).
+ */
+export declare const inject: string[];
+/** Plugin configuration. */
+export interface Config {
+    /** State directory name under the captain's workspace (default `.roundtable`). */
+    stateDir?: string;
+    /** `ctx.subagents` provider used to spawn nodes (default `spawn`). */
+    memberProvider?: string;
+    /** Meeting size cap in nodes (default `8`). */
+    maxNodes?: number;
+    /** Default collaboration mode (default `orchestrated`; `redteam` = 针锋相对评审). */
+    defaultMode?: 'orchestrated' | 'egalitarian' | 'redteam';
+    /** Node delegation depth cap (default `1`). */
+    memberMaxDepth?: number;
+    /** Prompt-section order for the usage policy (default `116`). */
+    promptSectionOrder?: number;
+}
+export declare const Config: z<Config>;
+export declare function apply(ctx: Context, config: Config): void;