@xirang-ai/dsh-teamflow 0.1.2 → 0.1.3

package/README.en.md

@@ -4,12 +4,12 @@
 
 Teamflow (`@xirang-ai/dsh-teamflow`) is a [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness) (DSH) plugin that turns **requirements → high-level design → detailed design → stories → development runs → bug fixes** into a persistent, resumable pipeline. It also adds a team workbench called **Xirang Workbench** to the DSH Web UI.
 
-Version: **`0.1.2`** (documents move into the plugin directory; stories and bugs gain discussion sessions; see [CHANGELOG.md](CHANGELOG.md)).
+Version: **`0.1.3`** (detailed-design documents can be deleted individually; the workbench header shows the plugin version; see [CHANGELOG.md](CHANGELOG.md)).
 
 - Data lives in SQLite; documents live in the plugin directory (default `<dataDir>/docs`), so closing a session does not lose progress.
 - Five agent presets cover requirements, stories, bugs, development, and detailed design. Each preset controls its own tool boundary.
 - The workbench provides lists, detail pages, a flow chart, a create page, a read-only session tab, and guarded deletion.
-- Twenty `teamflow_*` tools write interview and development results back to the database and plugin documents.
+- Twenty-one `teamflow_*` tools write interview and development results back to the database and plugin documents.
 
 ## Requirements
 

package/README.md

@@ -4,12 +4,12 @@
 
 Teamflow（`@xirang-ai/dsh-teamflow`）是 [DeepSeek Harness](https://github.com/deepseek-ai/deepseek-harness)（下称 DSH）的插件：把**需求 → 概要设计 → 详细设计 → 故事拆分 → 研发执行 → 缺陷修复**做成一条可持久化、可断点续跑的流水线，并在 Web 端提供团队工作台「息壤工作台」。
 
-当前版本：**`0.1.2`**（文档迁入插件目录，故事与缺陷支持讨论会话，变更记录见 [CHANGELOG.md](CHANGELOG.md)）。
+当前版本：**`0.1.3`**（详细设计文档可单独删除，工作台首页显示版本号，变更记录见 [CHANGELOG.md](CHANGELOG.md)）。
 
 - 数据落在 SQLite，文档落在插件目录（默认 `<dataDir>/docs`），关掉会话不丢进度。
 - 五个 Agent 预设分别负责需求、故事、缺陷、研发和详细设计，工具边界由预设控制。
 - 工作台提供列表、详情、流程图、创建页、会话内只读页签，以及受控的删除入口。
-- 二十个 `teamflow_*` 工具把访谈与研发结果写回数据库和插件文档。
+- 二十一个 `teamflow_*` 工具把访谈与研发结果写回数据库和插件文档。
 
 ## 环境要求
 

package/RELEASE.md

@@ -9,7 +9,7 @@
 
 | 项 | 值 |
 | --- | --- |
-| 目标版本号 | **0.1.2**（用户已确认） |
+| 目标版本号 | **0.1.3**（用户已确认） |
 | 发布分支 / commit | 发布时填写 |
 | 发布日期 | 发布时填写 |
 | 发布人 | 发布时填写 |
@@ -125,7 +125,7 @@ sqlite3 "$DSH_HOME/xirang-ai/dsh-teamflow/teamflow.sqlite" \
 - [ ] 开发端口统一为 `3091`（与本文件、AGENTS.md §5.1 一致）。
 - [ ] README 中的链接均可访问；仓库根的 `docs/` 仅作为提示词一致性报告、快照、Demo 走查结论与历次发版检查留痕保留，不进入 npm 包。
 - [ ] 配置说明指向 **profile 配置层** 的 `id: teamflow` 覆盖，而不是让用户改 `node_modules` 里的包内文件。
-- [ ] 版本号、schema 版本、工具数量（当前 20 个）、预设数量（当前 5 个）与实际一致。
+- [ ] 版本号、schema 版本、工具数量（当前 21 个）、预设数量（当前 5 个）与实际一致。
 - [ ] 本文件已按本次发版更新；AGENTS.md 的阅读路径与文档索引没有死链。
 
 ## 5. 代码、敏感信息与数据卫生

package/cordis.patch.yml

@@ -867,7 +867,7 @@
                 3. 需要确认某份详设该挂哪些故事时，用 teamflow_get_requirement 返回的故事列表核对标题与编号。你读不到故事正文，所以不要评论故事的验收标准细节。
                 4. 读完后先用两三句话概括：现有详设的结构、覆盖范围、与概要设计的对应关系。然后只问真正缺失或互相冲突的信息。
                 5. 讨论要围绕：接口、数据、状态机、异常与边界、权限、验收方式，以及文档之间的边界和一致性。
-                6. 文档粒度按 kind 自动划分：流程用 flow、数据用 data、接口用 interface、页面用 page、规则用 rule。一份文档只讲一件事；同一 kind 同一主题已有文档时更新既有文档，不要新建副本。这套分类由你按内容自动判定，不设确认闸口。
+                6. 文档粒度按 kind 自动划分：流程用 flow、数据用 data、接口用 interface、页面用 page、规则用 rule。一份文档只讲一件事；同一 kind 同一主题已有文档时更新既有文档，不要新建副本；用户明确要求「删旧建新」时，先删除旧文档再新建。这套分类由你按内容自动判定，不设确认闸口。
                 7. 一次最多问 3 个问题；能选择就给选项；不重复询问用户已经说过的内容。
 
                 ## 不做
@@ -884,7 +884,7 @@
 
                 遇到下列情况先停下说明并等用户回答，不要自行处置：
 
-                1. 写回前：先按「结论 / 理由 / 影响 / 待办」给出摘要，并明确问用户是否写回；用户确认后才调用 teamflow_create_design_doc 或 teamflow_update_design_doc。
+                1. 写回前：先按「结论 / 理由 / 影响 / 待办」给出摘要，并明确问用户是否写回；用户确认后才调用 teamflow_create_design_doc 或 teamflow_update_design_doc。删除文档前必须单独说明「正文文件与故事覆盖关系会一并删除、不可恢复」，得到明确同意后才调用 teamflow_delete_design_doc，一次只删一份。
                 2. 概要设计自相矛盾、或与用户新说法冲突时：指出冲突的具体两处，问以哪个为准，不要静默按一方写。
                 3. 需求已完成、已归档或已取消时：说明当前状态，问是否仍要在其上继续设计。
                 4. 用户要求改概设正文或拆故事时：说明不在你的职责内，并指出该走哪个入口。
@@ -903,7 +903,7 @@
 
                 1. 按职责内第 5 条的七个维度推进讨论，一次最多 3 个问题。
                 2. 形成结论时给出「结论 / 理由 / 影响 / 待办」摘要，并明确问是否写回。
-                3. 修改已有文档 → teamflow_update_design_doc（传文档 id）；新增文档 → teamflow_create_design_doc（定 kind、sortOrder、storyIds）。
+                3. 修改已有文档 → teamflow_update_design_doc（传文档 id）；新增文档 → teamflow_create_design_doc（定 kind、sortOrder、storyIds）；删除旧文档 → teamflow_delete_design_doc（传文档 id，先说明不可恢复）。
                 4. 写回后说明写了哪几份、各自路径，以及仍然未决的事项。
 
                 # 输入输出约定
@@ -920,6 +920,7 @@
                 2. 不要求用户手工粘贴文档内容。
                 3. 不在同一份文档里塞进多件互不相关的事。
                 4. 不用占位式 TODO 当作讨论结论。
+                5. 不一次删除多份文档，不用删除代替改写。
           - id: teamflow-tools
             name: '@xirang-ai/dsh-teamflow/tools'
             config:

package/lib/client.js

@@ -1,4 +1,4 @@
-/* @xirang-ai/dsh-teamflow 0.1.2 — generated by scripts/build.mjs, do not edit. */
+/* @xirang-ai/dsh-teamflow 0.1.3 — generated by scripts/build.mjs, do not edit. */
 window.__ModuleLoader__.load({
 	id: "@xirang-ai/dsh-teamflow",
 	factory: (require) => {
@@ -426,6 +426,7 @@ window.__ModuleLoader__.load({
 		  "page.retry": "Retry",
 		  "page.subtitle": "Defects come first, then running work, work waiting to start, and requirements still in discussion.",
 		  "page.title": "Xirang Workbench",
+		  "page.version": "v{version}",
 		  panel: "Xirang Workbench",
 		  "remote.bugId.empty": "A bug id is required.",
 		  "remote.doc.notFound": "Detailed-design document {id} does not exist.",
@@ -766,6 +767,7 @@ window.__ModuleLoader__.load({
 		  "page.retry": "重试",
 		  "page.subtitle": "缺陷优先；其下依次是执行中的需求与故事、待开始的工作，以及仍在讨论的需求。",
 		  "page.title": "息壤工作台",
+		  "page.version": "v{version}",
 		  panel: "息壤工作台",
 		  "remote.bugId.empty": "缺少缺陷编号。",
 		  "remote.doc.notFound": "详细设计 {id} 不存在。",
@@ -1242,6 +1244,14 @@ window.__ModuleLoader__.load({
 		.tf-head { display: flex; align-items: flex-start; gap: 16px; padding: 20px 0 14px; }
 		.tf-head-main { min-width: 0; flex: 1 1 auto; }
 		.tf-title { margin: 0; font-size: 18px; font-weight: 650; letter-spacing: -0.01em; }
+		.tf-version {
+		  margin-left: 7px;
+		  font-size: 11px;
+		  font-weight: 500;
+		  color: var(--dsw-alias-label-tertiary, inherit);
+		  font-variant-numeric: tabular-nums;
+		  white-space: nowrap;
+		}
 		.tf-sub { margin: 3px 0 0; font-size: 12px; color: var(--dsw-alias-label-tertiary, inherit); }
 		.tf-head-actions { display: flex; align-items: center; gap: 8px; flex: 0 0 auto; padding-top: 2px; }
 		.tf-error {
@@ -3240,6 +3250,9 @@ window.__ModuleLoader__.load({
 		  return title !== void 0 && title.trim() !== "" ? title : sessionId;
 		}
 
+		// src/client/version.ts
+		var PLUGIN_VERSION = "0.1.3";
+
 		// src/dev.ts
 		var DEV_PRESET = "xirang-dev";
 		function buildDevPrompt(story, requirement) {
@@ -15074,7 +15087,10 @@ window.__ModuleLoader__.load({
 		      view.kind === "list" ? /* @__PURE__ */ (0, import_jsx_runtime10.jsxs)(import_jsx_runtime10.Fragment, { children: [
 		        /* @__PURE__ */ (0, import_jsx_runtime10.jsxs)("header", { className: "tf-head", children: [
 		          /* @__PURE__ */ (0, import_jsx_runtime10.jsxs)("div", { className: "tf-head-main", children: [
-		            /* @__PURE__ */ (0, import_jsx_runtime10.jsx)("h1", { className: "tf-title", children: t("page.title") }),
+		            /* @__PURE__ */ (0, import_jsx_runtime10.jsxs)("h1", { className: "tf-title", children: [
+		              t("page.title"),
+		              /* @__PURE__ */ (0, import_jsx_runtime10.jsx)("span", { className: "tf-version", children: t("page.version", { version: PLUGIN_VERSION }) })
+		            ] }),
 		            /* @__PURE__ */ (0, import_jsx_runtime10.jsx)("p", { className: "tf-sub", children: t("page.subtitle") })
 		          ] }),
 		          /* @__PURE__ */ (0, import_jsx_runtime10.jsxs)("div", { className: "tf-head-actions", children: [

package/lib/store/model.d.ts

@@ -371,18 +371,19 @@ export interface RunFilter {
 /**
  * Record types the workbench can physically delete.
  *
- * Detailed-design documents (`design_docs`) are not a target of their own: they
- * are records *of* a requirement and are removed with it, because a document
- * has no meaning once the requirement that explains it is gone.
+ * A detailed-design document (`design_doc`) is deletable on its own as well as
+ * through its requirement: rewriting a document from scratch starts by removing
+ * the old one, and only then does a fresh document make sense. Deleting one
+ * removes its `design_doc_stories` coverage links with it.
  */
-export declare const DELETABLE_KINDS: readonly ["bug", "story", "requirement"];
+export declare const DELETABLE_KINDS: readonly ["bug", "story", "requirement", "design_doc"];
 export type DeletableKind = (typeof DELETABLE_KINDS)[number];
 /** One record the user asked to delete. */
 export interface DeleteTarget {
     readonly kind: DeletableKind;
     readonly id: string;
 }
-/** A detailed-design document that will be deleted together with its requirement. */
+/** A detailed-design document that will be deleted with its requirement. */
 export interface DeleteDocRef {
     readonly id: string;
     readonly title: string;
@@ -406,6 +407,7 @@ export interface DeletePreviewItem {
     readonly id: string;
     readonly found: boolean;
     readonly title: string;
+    /** Record status; a detailed design reports the status of its requirement. */
     readonly status: string;
     readonly workspaceId: string;
     readonly deletable: boolean;
@@ -439,6 +441,8 @@ export interface DeleteOutcome {
     readonly title: string;
     readonly ok: boolean;
     readonly removedDocs: number;
+    /** `design_doc_stories` links removed with a detailed design; 0 otherwise. */
+    readonly removedLinks: number;
     readonly removedRuns: number;
     readonly error: {
         readonly code: string;

package/lib/store/model.js

@@ -63,8 +63,9 @@ export class WorkflowError extends Error {
 /**
  * Record types the workbench can physically delete.
  *
- * Detailed-design documents (`design_docs`) are not a target of their own: they
- * are records *of* a requirement and are removed with it, because a document
- * has no meaning once the requirement that explains it is gone.
+ * A detailed-design document (`design_doc`) is deletable on its own as well as
+ * through its requirement: rewriting a document from scratch starts by removing
+ * the old one, and only then does a fresh document make sense. Deleting one
+ * removes its `design_doc_stories` coverage links with it.
  */
-export const DELETABLE_KINDS = ['bug', 'story', 'requirement'];
+export const DELETABLE_KINDS = ['bug', 'story', 'requirement', 'design_doc'];

package/lib/store/workflow.js

@@ -1278,6 +1278,7 @@ export class WorkflowStore {
     #deleteOne(target, preview) {
         const staged = [];
         let committed = false;
+        let removedLinks = 0;
         try {
             const outcome = withTransaction(this.#db, () => {
                 // Re-check inside the write transaction: a run may have started between
@@ -1305,12 +1306,28 @@ export class WorkflowStore {
                 else if (target.kind === 'bug') {
                     this.#db.prepare('DELETE FROM runs WHERE bug_id = ?').run(target.id);
                 }
+                else if (target.kind === 'design_doc') {
+                    // Coverage links cascade from `design_docs`, but delete them
+                    // explicitly so the removed count is known and does not depend on
+                    // the connection's foreign-keys pragma.
+                    const links = this.#db
+                        .prepare('SELECT COUNT(*) AS n FROM design_doc_stories WHERE doc_id = ?')
+                        .get(target.id);
+                    removedLinks = Number(links?.['n'] ?? 0);
+                    this.#db.prepare('DELETE FROM design_doc_stories WHERE doc_id = ?').run(target.id);
+                }
                 else {
                     // `design_doc_stories` is ON DELETE CASCADE from this table, and
                     // `requirement_sessions` cascades from `requirements`.
                     this.#db.prepare('DELETE FROM design_docs WHERE requirement_id = ?').run(target.id);
                 }
-                const table = target.kind === 'story' ? 'stories' : target.kind === 'bug' ? 'bugs' : 'requirements';
+                const table = target.kind === 'story'
+                    ? 'stories'
+                    : target.kind === 'bug'
+                        ? 'bugs'
+                        : target.kind === 'design_doc'
+                            ? 'design_docs'
+                            : 'requirements';
                 const changes = Number(this.#db.prepare(`DELETE FROM ${table} WHERE id = ?`).run(target.id).changes);
                 if (changes === 0) {
                     throw new WorkflowError('not_found', `${target.kind} ${target.id} does not exist`);
@@ -1320,7 +1337,8 @@ export class WorkflowStore {
                     id: target.id,
                     title: current.title,
                     ok: true,
-                    removedDocs: current.docs.length,
+                    removedDocs: target.kind === 'design_doc' ? 1 : current.docs.length,
+                    removedLinks,
                     removedRuns: current.runCount,
                     error: null,
                 };
@@ -1344,6 +1362,7 @@ export class WorkflowStore {
                 title: preview.title,
                 ok: false,
                 removedDocs: 0,
+                removedLinks: 0,
                 removedRuns: 0,
                 error: {
                     code: error instanceof WorkflowError ? error.code : 'delete_failed',
@@ -1363,7 +1382,7 @@ export class WorkflowStore {
         }
     }
     #summary(items) {
-        const counts = { bug: 0, story: 0, requirement: 0 };
+        const counts = { bug: 0, story: 0, requirement: 0, design_doc: 0 };
         for (const item of items)
             counts[item.kind] += 1;
         return {
@@ -1414,6 +1433,47 @@ export class WorkflowStore {
                 runCount: 0,
             };
         }
+        if (target.kind === 'design_doc') {
+            const doc = this.getDesignDoc(target.id);
+            if (doc === null)
+                return this.#missingPreview(target);
+            const requirement = this.getRequirement(doc.requirementId);
+            if (requirement === null)
+                return this.#missingPreview(target);
+            // A document has no lifecycle of its own, so only the stories it covers
+            // can make its deletion unsafe: an executing story still reads it.
+            const coveredStoryIds = this.listDocStoryIds(doc.id);
+            const activeRun = this.#activeRunForStories(coveredStoryIds);
+            const busyStory = coveredStoryIds
+                .map((storyId) => this.getStory(storyId))
+                .find((story) => story !== null && (story.status === 'developing' || story.status === 'self_testing'));
+            const blocked = activeRun !== null
+                ? {
+                    code: 'has_active_run',
+                    message: `design document ${doc.id} is covered by a story whose run ${activeRun} is still running; cancel the run before deleting`,
+                }
+                : busyStory === null || busyStory === undefined
+                    ? null
+                    : {
+                        code: 'invalid_transition',
+                        message: `design document ${doc.id} is covered by story ${busyStory.id}, which is ${busyStory.status}; only documents covered by idle stories can be deleted`,
+                    };
+            return {
+                kind: 'design_doc',
+                id: doc.id,
+                found: true,
+                title: doc.title,
+                status: requirement.status,
+                workspaceId: requirement.workspaceId,
+                deletable: blocked === null,
+                reasonCode: blocked?.code ?? null,
+                reason: blocked?.message ?? null,
+                activeRunId: activeRun,
+                docs: [],
+                stories: [],
+                runCount: 0,
+            };
+        }
         if (target.kind === 'story') {
             const story = this.getStory(target.id);
             if (story === null)
@@ -1519,6 +1579,8 @@ export class WorkflowStore {
             return [this.#requireStory(target.id).contentPath];
         if (target.kind === 'bug')
             return [this.#requireBug(target.id).contentPath];
+        if (target.kind === 'design_doc')
+            return [this.#requireDesignDoc(target.id).contentPath];
         const requirement = this.#requireRequirement(target.id);
         return [
             requirement.contentPath,

package/lib/tools/delete-design-doc.d.ts

@@ -0,0 +1,24 @@
+import type { WorkflowStore } from '../store/workflow.ts';
+import type { ToolEnvironment } from './shared.ts';
+/** What one successful detailed-design deletion removed, as the model sees it. */
+export interface DeletedDesignDoc {
+    readonly id: string;
+    readonly requirementId: string;
+    readonly title: string;
+    readonly kind: string;
+    /** Coverage links removed from `design_doc_stories`. */
+    readonly removedLinks: number;
+}
+/**
+ * Preview and then delete one detailed-design document.
+ *
+ * The preview is where a refusal becomes an actionable sentence instead of a
+ * bare `ok: false`, because `deleteRecords` reports per-record failures instead
+ * of throwing.
+ * @param workflow - the open workbench store.
+ * @param rawId - document id, trimmed before lookup.
+ * @returns the removed document's identity and how many coverage links went with it.
+ */
+export declare function deleteDesignDoc(workflow: WorkflowStore, rawId: string): DeletedDesignDoc;
+/** Build the detailed-design deletion tool bound to one Host context. */
+export declare function deleteDesignDocTool(environment: ToolEnvironment): import("@deepseek-ai/dsh-tools").ToolDefinition;

package/lib/tools/delete-design-doc.js

@@ -0,0 +1,109 @@
+/**
+ * `teamflow_delete_design_doc` — permanently remove one detailed-design document.
+ *
+ * This is the "delete the old document, then write a new one" path the detail
+ * Agent needs when a rewrite is not an in-place revision. Deletion goes through
+ * the workbench's preview-then-delete path, so the Agent and the Web UI share
+ * the same refusal rules: a document covered by an executing story is refused
+ * with a sentence the user can act on. The body file and every
+ * `design_doc_stories` coverage link are removed with the row; there is no undo.
+ *
+ * @module
+ */
+import { defineTool } from '@deepseek-ai/dsh-tools';
+/** Turn a deletion preview into the refusal the Agent should relay. */
+function refusal(item) {
+    const head = `teamflow: 不能删除详细设计 ${item.id}《${item.title}》`;
+    if (item.reasonCode === 'has_active_run') {
+        const run = item.activeRunId === null ? '' : ` ${item.activeRunId}`;
+        return `${head}：覆盖它的故事仍有研发运行${run} 尚未结束；请先取消该运行再删除。`;
+    }
+    if (item.reasonCode === 'invalid_transition') {
+        return `${head}：覆盖它的故事正在执行（developing / self_testing）；只有覆盖故事都空闲时才能删除详设。`;
+    }
+    return `${head}：${item.reason ?? '当前状态不允许删除'}。`;
+}
+/**
+ * Preview and then delete one detailed-design document.
+ *
+ * The preview is where a refusal becomes an actionable sentence instead of a
+ * bare `ok: false`, because `deleteRecords` reports per-record failures instead
+ * of throwing.
+ * @param workflow - the open workbench store.
+ * @param rawId - document id, trimmed before lookup.
+ * @returns the removed document's identity and how many coverage links went with it.
+ */
+export function deleteDesignDoc(workflow, rawId) {
+    const id = rawId.trim();
+    if (id.length === 0)
+        throw new Error('teamflow: 详细设计 id 不能为空。');
+    // Read the row before it is gone: the requirement id and kind are not part
+    // of the deletion outcome.
+    const doc = workflow.getDesignDoc(id);
+    if (doc === null)
+        throw new Error(`teamflow: 详细设计 ${id} 不存在。`);
+    const preview = workflow.previewDeletions([{ kind: 'design_doc', id }]);
+    const item = preview.items[0];
+    if (item === undefined)
+        throw new Error(`teamflow: 无法预览详细设计 ${id} 的删除。`);
+    if (!item.found)
+        throw new Error(`teamflow: 详细设计 ${id} 不存在。`);
+    if (!item.deletable)
+        throw new Error(refusal(item));
+    const report = workflow.deleteRecords([{ kind: 'design_doc', id }]);
+    const outcome = report.results[0];
+    if (outcome === undefined)
+        throw new Error(`teamflow: 删除详细设计 ${id} 没有返回结果。`);
+    if (!outcome.ok) {
+        throw new Error(`teamflow: 删除详细设计 ${id} 失败：${outcome.error?.message ?? '未知错误'}。`);
+    }
+    return {
+        id: outcome.id,
+        requirementId: doc.requirementId,
+        title: outcome.title,
+        kind: doc.kind,
+        removedLinks: outcome.removedLinks,
+    };
+}
+/** Build the detailed-design deletion tool bound to one Host context. */
+export function deleteDesignDocTool(environment) {
+    return defineTool({
+        name: 'teamflow_delete_design_doc',
+        description: 'Permanently delete one detailed-design document together with its Markdown body and every story-coverage link. Use this when the user asks to remove the old document and write a new one, or to drop a document that no longer belongs. A document covered by a story that is developing or self-testing is refused. Ask the user to confirm the title first: this cannot be undone.',
+        parameters: {
+            id: {
+                type: 'string',
+                required: true,
+                description: 'Document id from teamflow_get_requirement or teamflow_get_design_doc.',
+            },
+        },
+        output: {
+            schema: {
+                type: 'object',
+                additionalProperties: false,
+                properties: {
+                    id: { type: 'string', required: true },
+                    requirementId: { type: 'string', required: true },
+                    title: { type: 'string', required: true },
+                    kind: { type: 'string', required: true },
+                    removedLinks: { type: 'number', required: true },
+                },
+            },
+            render: (_args, value) => [
+                {
+                    type: 'text',
+                    text: [
+                        `已删除详细设计 ${value.id}《${value.title}》（${value.kind}），所属需求 ${value.requirementId}。`,
+                        value.removedLinks === 0
+                            ? '正文文件已一并删除；此操作不可恢复。'
+                            : `正文文件与 ${value.removedLinks} 条故事覆盖关系已一并删除；此操作不可恢复。`,
+                    ].join('\n'),
+                },
+            ],
+        },
+        async execute(args, exec) {
+            exec.signal.throwIfAborted();
+            return deleteDesignDoc(environment.database.workflow, args.id);
+        },
+    });
+}

package/lib/tools/index.d.ts

@@ -26,7 +26,7 @@ export type ToolProfile = (typeof TOOL_PROFILES)[number];
  * Tool names per profile.
  *
  * `requirement` collects the requirement and its outline design;
- * `detail` writes detailed designs while reading the outline;
+ * `detail` writes and deletes detailed designs while reading the outline;
  * `split` writes stories while reading detailed designs;
  * `dev` executes a story with every document read-only;
  * `bug` collects and merges defects.

package/lib/tools/index.js

@@ -5,6 +5,7 @@ import { createBugTool } from "./create-bug.js";
 import { createDesignDocTool } from "./create-design-doc.js";
 import { createRequirementTool } from "./create-requirement.js";
 import { createStoryTool } from "./create-story.js";
+import { deleteDesignDocTool } from "./delete-design-doc.js";
 import { deleteStoryTool } from "./delete-story.js";
 import { finishRunTool } from "./finish-run.js";
 import { getBugTool } from "./get-bug.js";
@@ -37,7 +38,7 @@ export const TOOL_PROFILES = [
  * Tool names per profile.
  *
  * `requirement` collects the requirement and its outline design;
- * `detail` writes detailed designs while reading the outline;
+ * `detail` writes and deletes detailed designs while reading the outline;
  * `split` writes stories while reading detailed designs;
  * `dev` executes a story with every document read-only;
  * `bug` collects and merges defects.
@@ -59,6 +60,7 @@ export const PROFILE_TOOL_NAMES = {
         'teamflow_get_design_doc',
         'teamflow_create_design_doc',
         'teamflow_update_design_doc',
+        'teamflow_delete_design_doc',
         'teamflow_list_records',
         'teamflow_list_workspaces',
     ],
@@ -97,6 +99,7 @@ export const PROFILE_TOOL_NAMES = {
         'teamflow_get_requirement',
         'teamflow_create_design_doc',
         'teamflow_update_design_doc',
+        'teamflow_delete_design_doc',
         'teamflow_get_design_doc',
         'teamflow_link_requirement_session',
         'teamflow_link_session',
@@ -142,6 +145,7 @@ export function apply(ctx, config) {
         getRequirementTool(environment),
         createDesignDocTool(environment),
         updateDesignDocTool(environment),
+        deleteDesignDocTool(environment),
         getDesignDocTool(environment),
         linkRequirementSessionTool(environment),
         linkSessionTool(environment),

package/locale/en.json

@@ -218,6 +218,7 @@
   "page.retry": "Retry",
   "page.subtitle": "Defects come first, then running work, work waiting to start, and requirements still in discussion.",
   "page.title": "Xirang Workbench",
+  "page.version": "v{version}",
   "panel": "Xirang Workbench",
   "remote.bugId.empty": "A bug id is required.",
   "remote.doc.notFound": "Detailed-design document {id} does not exist.",

package/locale/zh.json

@@ -218,6 +218,7 @@
   "page.retry": "重试",
   "page.subtitle": "缺陷优先；其下依次是执行中的需求与故事、待开始的工作，以及仍在讨论的需求。",
   "page.title": "息壤工作台",
+  "page.version": "v{version}",
   "panel": "息壤工作台",
   "remote.bugId.empty": "缺少缺陷编号。",
   "remote.doc.notFound": "详细设计 {id} 不存在。",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xirang-ai/dsh-teamflow",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "DeepSeek Harness plugin: Xirang workbench for the requirement → development → defect pipeline.",
   "license": "MIT",
   "repository": {