tower-studio 0.2.44 → 0.2.46

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tower-studio",
-  "version": "0.2.44",
+  "version": "0.2.46",
   "description": "AI Task Orchestration Platform — Kanban + Terminal + Code Editor + MCP",
   "bin": {
     "tower": "bin/tower.mjs"
@@ -20,17 +20,16 @@
     "scripts/migrate-data.ts",
     "scripts/run-migrations.ts",
     "scripts/migrations/",
-    "scripts/post-tool-hook.js",
-    "scripts/session-start-hook.js",
-    "scripts/stop-hook.js",
+    "scripts/tower-post-tool-hook.js",
+    "scripts/tower-session-start-hook.js",
+    "scripts/tower-stop-hook.js",
     "dist/mcp-server.cjs",
     "skills/",
-    "next.config.ts",
     "tsconfig.json"
   ],
   "scripts": {
     "predev": "TOWER_DATA_DIR=\"$HOME/.tower-dev\" DATABASE_URL=\"file:$HOME/.tower-dev/database/tower.db\" node scripts/ensure-dev-db.js && pnpm db:migrate && pnpm mcp:build",
-    "dev": "NEXT_DISTDIR=.next-dev TOWER_DATA_DIR=\"$HOME/.tower-dev\" DATABASE_URL=\"file:$HOME/.tower-dev/database/tower.db\" next dev --webpack -p 9022",
+    "dev": "NEXT_DISTDIR=.next-dev TOWER_DATA_DIR=\"$HOME/.tower-dev\" DATABASE_URL=\"file:$HOME/.tower-dev/database/tower.db\" env -u TURBOPACK next dev --webpack -p 9022",
     "build": "pnpm mcp:build && rm -rf .next && next build && find .next -name '*.map' -delete && cp -R .next/static .next/standalone/.next/ && cp -R public .next/standalone/ && node scripts/prune-standalone-natives.js",
     "release": "pnpm build && npm pack",
     "release:smoke": "node scripts/release-smoke.js",

package/prisma/schema.prisma

@@ -15,10 +15,11 @@ model Workspace {
   createdAt   DateTime @default(now())
   updatedAt   DateTime @updatedAt
 
-  projects     Project[]
-  labels       Label[]
-  prompts      AgentPrompt[]
-  versionTypes VersionType[]
+  projects      Project[]
+  labels        Label[]
+  prompts       AgentPrompt[]
+  versionTypes  VersionType[]
+  productGroups ProductGroup[]
 }
 
 model Project {
@@ -34,18 +35,58 @@ model Project {
   previewPort    Int?
   previewPreset  String?
   previewInstallCommand String?
+  // 知识库：groupId 把同一产品的多个仓库（前后端/trace/需求）归入一个 ProductGroup，
+  // 问答时自动把同组兄弟项目一起纳入检索。knowledgeDir 是 repo 内知识库目录（相对 localPath），
+  // 留空则用约定默认（见 src/lib/knowledge.ts DEFAULT_KNOWLEDGE_DIR）。
+  groupId        String?
+  knowledgeDir   String?
   workspaceId    String
   createdAt   DateTime    @default(now())
   updatedAt   DateTime    @updatedAt
 
-  workspace    Workspace    @relation(fields: [workspaceId], references: [id], onDelete: Cascade)
+  workspace    Workspace     @relation(fields: [workspaceId], references: [id], onDelete: Cascade)
+  group        ProductGroup? @relation(fields: [groupId], references: [id], onDelete: SetNull)
   tasks        Task[]
   repositories Repository[]
   notes        ProjectNote[]
   assets       ProjectAsset[]
   versions     Version[]
+  facts        ProjectFact[]
 
   @@index([workspaceId])
+  @@index([groupId])
+}
+
+/// 产品组：把同一产品的多个仓库（前后端 / trace 静态知识库 / 需求）归为一组。
+/// 组内成员的知识（repo 知识目录 + 事实卡 + 版本/commit + 笔记）在问答时一起检索。
+model ProductGroup {
+  id          String   @id @default(cuid())
+  name        String
+  description String?
+  workspaceId String
+  createdAt   DateTime @default(now())
+  updatedAt   DateTime @updatedAt
+
+  workspace Workspace @relation(fields: [workspaceId], references: [id], onDelete: Cascade)
+  projects  Project[]
+
+  @@unique([workspaceId, name])
+  @@index([workspaceId])
+}
+
+// 结构化「事实卡」：机器拿不到、需人工/AI 填的项目级 key-value（生产环境路径、
+// CICD 路径、域名等）。知识库问答的精确命中源之一。key 在项目内唯一（upsert）。
+model ProjectFact {
+  id        String   @id @default(cuid())
+  projectId String
+  key       String
+  value     String
+  updatedAt DateTime @updatedAt
+
+  project Project @relation(fields: [projectId], references: [id], onDelete: Cascade)
+
+  @@unique([projectId, key])
+  @@index([projectId])
 }
 
 model Label {
@@ -83,6 +124,7 @@ model Task {
   promptId    String?
   baseBranch  String?
   subPath     String?
+  parentTaskId String?   // 派生来源：派生此任务的父任务 id（父任务终端注入的 TOWER_TASK_ID）。裸字符串无 relation，与 promptId 同惯例
   previewCommandOverride String?
   previewPortOverride    Int?
   projectId   String
@@ -91,17 +133,23 @@ model Task {
   updatedAt   DateTime   @updatedAt
   doneAt      DateTime?  // 进入 DONE 的时间戳，用于「归档期限」判定（离开 DONE 时清空）
 
+  // 无人值守：开启后 agent 遇阻塞主动 ask_human/notify_human（经 tower-ask 技能用平台 MCP 外推）；
+  // 关闭则只在 /harness 面板内显示等待。Tower 只记录+park/resume，不发消息、不存平台绑定。
+  unattended    Boolean   @default(false)
+
   project    Project         @relation(fields: [projectId], references: [id], onDelete: Cascade)
   executions TaskExecution[]
   messages   TaskMessage[]
   labels     TaskLabel[]
   notes      ProjectNote[]
   assets     ProjectAsset[]
+  harnessMessages HarnessMessage[]
   version    Version?        @relation(fields: [versionId], references: [id], onDelete: SetNull)
 
   @@index([projectId])
   @@index([status])
   @@index([versionId])
+  @@index([parentTaskId])
 }
 
 model TaskExecution {
@@ -137,6 +185,36 @@ model TaskExecution {
   @@index([insightNoteId])
 }
 
+// 无人值守：一张表记所有 harness→人 的消息（ask/notify/done/failed）—— 纯记录/日志，Tower 不发送。
+// - kind='ask' 是 park/resume 闭环载体，带生命周期 state：OPEN→ANSWERED|CANCELLED|IGNORED|EXPIRED。
+// - notify/done/failed 是日志行，出生即 CLOSED，不参与「待回复」过滤。
+// - 不变量：待回复 = kind='ask' AND state='OPEN'。回复内容记在 replyText（reply_to_ask 写入）。
+model HarnessMessage {
+  id           String   @id @default(cuid())
+  taskId       String
+  executionId  String?
+  kind         String   // "ask" | "notify" | "done" | "failed"（映射 OutboundKind）
+  content      String
+  replyText    String?
+  repliedAt    DateTime?
+  state        HarnessState @default(OPEN)
+  createdAt    DateTime @default(now())
+
+  task Task @relation(fields: [taskId], references: [id], onDelete: Cascade)
+
+  @@index([taskId, kind, state])
+  @@index([state])
+}
+
+enum HarnessState {
+  OPEN
+  ANSWERED
+  CANCELLED
+  IGNORED
+  EXPIRED
+  CLOSED
+}
+
 model TaskMessage {
   id          String      @id @default(cuid())
   role        MessageRole

package/scripts/migrations/0005-add-parent-task-id.ts

@@ -0,0 +1,29 @@
+/**
+ * Add Task.parentTaskId — 派生中枢的父任务链。
+ *
+ * 子任务由父任务终端的 claude 调 create_task 创建时，写入派生它的父任务 id
+ * （父任务 PTY 注入的 TOWER_TASK_ID）。用于完成回推（子任务 stop → 通知父任务
+ * review）及将来的派生子任务展示。裸字符串列、无 FK relation（与 promptId 同惯例）。
+ *
+ * 加性 raw SQL —— 绝不碰 notes_fts 虚表（prisma db push 会卡死）。
+ * 幂等：SQLite 无 ADD COLUMN IF NOT EXISTS，先 PRAGMA 检查列是否存在。
+ *
+ * Table/column names hardcoded on purpose — a migration is a point-in-time
+ * snapshot and must keep doing exactly what it did the day it shipped.
+ */
+
+import type { PrismaClient } from "@prisma/client";
+
+export async function up(prisma: PrismaClient): Promise<void> {
+  const cols = await prisma.$queryRawUnsafe<Array<{ name: string }>>(
+    `PRAGMA table_info("Task")`
+  );
+  const hasCol = Array.isArray(cols) && cols.some((c) => c.name === "parentTaskId");
+  if (!hasCol) {
+    await prisma.$executeRawUnsafe(`ALTER TABLE "Task" ADD COLUMN "parentTaskId" TEXT`);
+    console.log("  added Task.parentTaskId");
+  }
+  await prisma.$executeRawUnsafe(
+    `CREATE INDEX IF NOT EXISTS "Task_parentTaskId_idx" ON "Task"("parentTaskId")`
+  );
+}

package/scripts/migrations/0006-project-knowledge.ts

@@ -0,0 +1,58 @@
+/**
+ * 项目知识库地基：Project.productKey / Project.knowledgeDir + ProjectFact 表。
+ *
+ * - productKey: 产品组归一（前后端 a/b 填同值即成组），问答时兄弟项目一起检索。
+ * - knowledgeDir: repo 内知识库目录（相对 localPath），留空走约定默认。
+ * - ProjectFact: 机器拿不到的项目级事实卡（生产/CICD 路径等），key 项目内唯一。
+ *
+ * 加性 raw SQL —— 绝不碰 notes_fts 虚表（prisma db push 会卡死）。
+ * 幂等：SQLite 无 ADD COLUMN IF NOT EXISTS，先 PRAGMA 检查列是否存在。
+ *
+ * Table/column names hardcoded on purpose — a migration is a point-in-time
+ * snapshot and must keep doing exactly what it did the day it shipped.
+ */
+
+import type { PrismaClient } from "@prisma/client";
+
+async function addColumnIfMissing(
+  prisma: PrismaClient,
+  table: string,
+  column: string,
+  ddlType: string
+): Promise<void> {
+  const cols = await prisma.$queryRawUnsafe<Array<{ name: string }>>(
+    `PRAGMA table_info("${table}")`
+  );
+  const hasCol = Array.isArray(cols) && cols.some((c) => c.name === column);
+  if (!hasCol) {
+    await prisma.$executeRawUnsafe(
+      `ALTER TABLE "${table}" ADD COLUMN "${column}" ${ddlType}`
+    );
+    console.log(`  added ${table}.${column}`);
+  }
+}
+
+export async function up(prisma: PrismaClient): Promise<void> {
+  await addColumnIfMissing(prisma, "Project", "productKey", "TEXT");
+  await addColumnIfMissing(prisma, "Project", "knowledgeDir", "TEXT");
+  await prisma.$executeRawUnsafe(
+    `CREATE INDEX IF NOT EXISTS "Project_productKey_idx" ON "Project"("productKey")`
+  );
+
+  await prisma.$executeRawUnsafe(
+    `CREATE TABLE IF NOT EXISTS "ProjectFact" (` +
+      `"id" TEXT NOT NULL PRIMARY KEY, ` +
+      `"projectId" TEXT NOT NULL, ` +
+      `"key" TEXT NOT NULL, ` +
+      `"value" TEXT NOT NULL, ` +
+      `"updatedAt" DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP, ` +
+      `CONSTRAINT "ProjectFact_projectId_fkey" FOREIGN KEY ("projectId") ` +
+      `REFERENCES "Project"("id") ON DELETE CASCADE ON UPDATE CASCADE)`
+  );
+  await prisma.$executeRawUnsafe(
+    `CREATE UNIQUE INDEX IF NOT EXISTS "ProjectFact_projectId_key_key" ON "ProjectFact"("projectId", "key")`
+  );
+  await prisma.$executeRawUnsafe(
+    `CREATE INDEX IF NOT EXISTS "ProjectFact_projectId_idx" ON "ProjectFact"("projectId")`
+  );
+}

package/scripts/migrations/0007-product-group.ts

@@ -0,0 +1,67 @@
+/**
+ * 产品组一等实体：ProductGroup 表 + Project.groupId，取代平级字符串 Project.productKey。
+ *
+ * 加性 raw SQL —— 绝不碰 notes_fts 虚表。幂等：建表/建索引用 IF NOT EXISTS，加列先 PRAGMA 查。
+ *
+ * 为什么没有 productKey→组的数据回填：
+ *   1. productKey 从未发布（无真实数据）。
+ *   2. Tower 升级生命周期（bin/tower.mjs preStart）**先** `db push --accept-data-loss`
+ *      按新 schema 同步、**再**跑本迁移。新 schema 已删 productKey，故 db push 会先
+ *      把该列连数据一起丢掉——等本迁移执行时 productKey 早已不存在，回填必成死代码。
+ *   迁移只负责把 groupId/ProductGroup 幂等建出来（供不走 db push 的 dev/迁移路径），
+ *   并清掉遗留的 productKey 列。删组时的「成员解绑」由 group-actions 在应用层做
+ *   （ADD COLUMN 不带外键，不能靠 DB 级 onDelete: SetNull）。
+ *
+ * Table/column names hardcoded on purpose — a migration is a point-in-time snapshot.
+ */
+
+import type { PrismaClient } from "@prisma/client";
+
+async function hasColumn(prisma: PrismaClient, table: string, column: string): Promise<boolean> {
+  const cols = await prisma.$queryRawUnsafe<Array<{ name: string }>>(
+    `PRAGMA table_info("${table}")`
+  );
+  return Array.isArray(cols) && cols.some((c) => c.name === column);
+}
+
+export async function up(prisma: PrismaClient): Promise<void> {
+  // 1. ProductGroup 表
+  await prisma.$executeRawUnsafe(
+    `CREATE TABLE IF NOT EXISTS "ProductGroup" (` +
+      `"id" TEXT NOT NULL PRIMARY KEY, ` +
+      `"name" TEXT NOT NULL, ` +
+      `"description" TEXT, ` +
+      `"workspaceId" TEXT NOT NULL, ` +
+      `"createdAt" DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP, ` +
+      `"updatedAt" DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP, ` +
+      `CONSTRAINT "ProductGroup_workspaceId_fkey" FOREIGN KEY ("workspaceId") ` +
+      `REFERENCES "Workspace"("id") ON DELETE CASCADE ON UPDATE CASCADE)`
+  );
+  await prisma.$executeRawUnsafe(
+    `CREATE UNIQUE INDEX IF NOT EXISTS "ProductGroup_workspaceId_name_key" ON "ProductGroup"("workspaceId", "name")`
+  );
+  await prisma.$executeRawUnsafe(
+    `CREATE INDEX IF NOT EXISTS "ProductGroup_workspaceId_idx" ON "ProductGroup"("workspaceId")`
+  );
+
+  // 2. Project.groupId 列 + 索引
+  if (!(await hasColumn(prisma, "Project", "groupId"))) {
+    await prisma.$executeRawUnsafe(`ALTER TABLE "Project" ADD COLUMN "groupId" TEXT`);
+    console.log("  added Project.groupId");
+  }
+  await prisma.$executeRawUnsafe(
+    `CREATE INDEX IF NOT EXISTS "Project_groupId_idx" ON "Project"("groupId")`
+  );
+
+  // 3. 清掉遗留 productKey 列（先删其索引）。无回填——见文件头说明。
+  //    SQLite <3.35 不支持 DROP COLUMN → 留孤儿列，Prisma 忽略，无害。
+  await prisma.$executeRawUnsafe(`DROP INDEX IF EXISTS "Project_productKey_idx"`);
+  if (await hasColumn(prisma, "Project", "productKey")) {
+    try {
+      await prisma.$executeRawUnsafe(`ALTER TABLE "Project" DROP COLUMN "productKey"`);
+      console.log("  dropped Project.productKey");
+    } catch {
+      console.log("  DROP COLUMN productKey unsupported (old SQLite) — left orphaned, harmless");
+    }
+  }
+}

package/scripts/{stop-hook.js → tower-stop-hook.js}

@@ -3,13 +3,14 @@
  * Tower Stop Hook
  *
  * Claude Code Stop hook that fires when Claude finishes responding.
- * Notifies Tower so the UI can show a "response complete" indicator.
+ * Notifies Tower so the UI can show a "response complete" indicator, and so a
+ * derived child task can hand its turn back to the parent task for review.
  *
  * Environment:
  *   TOWER_TASK_ID  - Required. Skip if absent (not a Tower session).
  *   TOWER_API_URL  - Required. Base URL of the Tower server.
  *
- * Stdin: JSON object from Claude Code with { session_id, cwd, ... }
+ * Stdin: JSON object from Claude Code with { session_id, transcript_path, cwd, ... }
  */
 
 "use strict";
@@ -17,6 +18,43 @@
 const http = require("http");
 const https = require("https");
 
+/**
+ * 从 Claude Code 的 transcript 提取最后一条 assistant 回复（截断 2000 字）。
+ * 用于完成回推：父任务据此 review，不必读整个终端缓冲。best-effort，失败返回空串。
+ * transcript 是 jsonl，行格式随 CC 版本略有差异，这里兼容 obj.message.content / obj.content。
+ */
+function extractLastAssistantText(transcriptPath) {
+  if (!transcriptPath) return "";
+  try {
+    const fs = require("fs");
+    const raw = fs.readFileSync(transcriptPath, "utf8");
+    const lines = raw.split("\n");
+    for (let i = lines.length - 1; i >= 0; i--) {
+      const line = lines[i].trim();
+      if (!line) continue;
+      let obj;
+      try { obj = JSON.parse(line); } catch { continue; }
+      const msg = obj.message || obj;
+      const role = msg.role || obj.type;
+      if (role !== "assistant" || !msg.content) continue;
+      let text = "";
+      if (Array.isArray(msg.content)) {
+        text = msg.content
+          .filter((c) => c && c.type === "text" && typeof c.text === "string")
+          .map((c) => c.text)
+          .join("\n")
+          .trim();
+      } else if (typeof msg.content === "string") {
+        text = msg.content.trim();
+      }
+      if (text) return text.slice(0, 2000);
+    }
+  } catch {
+    /* best effort — transcript unreadable */
+  }
+  return "";
+}
+
 function main() {
   // Always drain stdin first — Claude Code writes the hook payload there
   // and if we exit before reading it, Windows libuv can crash the parent
@@ -52,10 +90,11 @@ function main() {
     try { data = JSON.parse(input); } catch { process.exit(0); }
 
     const sessionId = data.session_id || "";
+    const lastReply = extractLastAssistantText(data.transcript_path);
 
     // POST to Tower
     const url = new URL("/api/internal/hooks/stop", apiUrl);
-    const payload = JSON.stringify({ taskId, sessionId });
+    const payload = JSON.stringify({ taskId, sessionId, lastReply });
     const mod = url.protocol === "https:" ? https : http;
 
     const req = mod.request({

package/skills/tower/SKILL.md

@@ -39,6 +39,7 @@ Use Tower tools when the user wants to:
 - Organize tasks with labels or status changes
 - Get daily work summary or pending todo list
 - Check what was done today or what's left to do
+- **Run or relay unattended tasks** — when `TOWER_UNATTENDED=1`, or you need to push an `ask_human` / `notify_human` to a person, or relay a human's reply back into a parked task (`reply_to_ask`): read [`references/unattended-messaging.md`](references/unattended-messaging.md) for the send/receive contract.
 
 ---
 
@@ -51,6 +52,16 @@ to keep asking. If information is missing, ask a **specific** question instead o
 vaguely promising to act. If the user prods you ("did you create it?", "创建了吗"),
 it means your previous turn produced no tool call — issue the tool call now.
 
+## Session default scope
+
+If a turn opens with `[当前会话默认范围：…]`, the user has bound this chat to a
+workspace/project. Treat it as the **default scope**: for scope-needing actions
+(create/list/search within a project, label, version…) use those ids directly
+and skip resolving with `identify_project`/`search`. No binding present → resolve
+scope the usual way. It's a soft default, **not a hard filter** — global requests
+(daily summary, cross-workspace search, list all workspaces) ignore it. The user
+switching workspace/project mid-chat overrides it; the latest prefix always wins.
+
 ## Scenarios
 
 ### "Show me my workspaces" / "List projects"
@@ -78,7 +89,7 @@ it means your previous turn produced no tool call — issue the tool call now.
    - **Pasted images with known paths**: if the platform provides file paths for pasted media (e.g. OpenClaw's `{{MediaPaths}}`, Claude Code temp files), pass those paths directly — they are local files
    - **Base64 only (no file path)**: if you only have base64 data with no local path, upload first via `manage_assets` with `action: "upload"`, `projectId`, `base64`, `mimeType`. Get back `{ id: assetId, path }`. Then pass the returned `path` in `references` — `create_task` will automatically copy and link the asset, no separate `link_task` needed
    - **`link_task` only for retroactive linking**: use `manage_assets` with `action: "link_task"` only when you need to associate existing assets with an already-created task (e.g. user wants to add references after task creation)
-8. **Source (`## 来源`)** — ALWAYS append a `## 来源` section to the task `description` (see **Task Source** below for the full spec). If the incoming prompt carries no source info, it is literally `## 来源\n无`. If it does (especially a `<task-source>` block injected by a bridge like Feishu), standardize it into a detailed, traceable record.
+8. **Source (`## 来源`)** — ALWAYS end the `description` with a `## 来源` section (it's the last section of the description format — see **Task Description Format** for the rule and [references/task-source.md](references/task-source.md) for the full rendering). No source info → literally `## 来源\n无`. Source present (a `<task-source>` bridge block or `TOWER_TASK_ID`) → standardize into a detailed, traceable record.
 9. Call `create_task` with projectId, title, and optional description/priority/labelIds/subPath/versionId/useWorktree/baseBranch/references
 10. After creating: if `autoStart` resolved to true the task starts immediately (check the response's `execution` field — `autoStart` intent does not guarantee it actually started); otherwise the task stays TODO.
 
@@ -184,6 +195,9 @@ The `description` field supports Markdown. **Never copy the user's raw message a
 
 ## 备注
 - <constraints, edge cases, things to watch out for>
+
+## 来源
+无
 ```
 
 Rules:
@@ -192,6 +206,14 @@ Rules:
 - Extract actionable requirements from the user's natural language
 - Omit sections that have no content (e.g. skip 备注 if nothing to note)
 - If user provides file paths, put them in 参考 section AND in `references` parameter
+- **`## 来源` is mandatory and always the LAST section** — it traces *why* the task
+  exists and *who* asked. Every creation path (助手 / 飞书 / 父子派生 / 终端) ends here:
+  - **No source info** → write exactly `## 来源` + `无` (as shown above).
+  - **Source present** → standardize into a human-readable record, then read
+    [references/task-source.md](references/task-source.md) for the exact rendering.
+    Two triggers: `TOWER_TASK_ID` set (parent-derived child) or a `<task-source>`
+    block (bridge like Feishu). Keep hard locators (chat/msg id, link) verbatim; if
+    a `<task-source>` block is present, DROP the raw block from the description.
 
 ---
 
@@ -239,80 +261,6 @@ Note: the response does not include workspace name. Use the workspace name from
 | {id (first 8 chars)} | {title} | {status} | {priority} | {labels} |
 ```
 
-### Task Source (`## 来源`)
-
-Every task created through this skill MUST end its `description` with a `## 来源`
-section so we can always trace **why** a task exists and **who** asked for it.
-
-**No source info in the prompt** → write exactly:
-
-```
-## 来源
-无
-```
-
-**Source info present** → standardize it into a human-readable record. Keep the
-hard locators (chat id / message id / link) verbatim — they are what makes the
-task traceable later.
-
-#### Bridge metadata contract (`<task-source>` block)
-
-External bridges (Feishu/Lark, etc.) inject a machine-readable block into the
-message. When you see it, parse it, render the standardized `## 来源`, and then
-DROP the raw block from the description (don't store the tags):
-
-```
-<task-source>
-channel: feishu                      # 渠道 (feishu | openclaw | manual | ...)
-chat_name: 南京招生报名讨论群          # 群显示名
-chat_id: oc_xxxxxxxx                 # 群 ID（硬定位符，必带）
-occurred_at: 2026-06-16 17:49 +08:00 # 讨论/触发时间，带时区（用于进群后定位到具体那条）
-chat_link: https://applink.feishu.cn/client/chat/open?openChatId=oc_xxxxxxxx  # 打开「群」的链接（群级，飞书无法精确到单条消息）
-trigger_message_id: om_xxxxxxxx      # 触发那条消息的 ID（不可点，但唯一绑定该消息，必带；用于程序回读/去重/兜底）
-thread_root_id: om_yyyyyyyy          # （可选）话题根消息 ID
-participants:                        # 参与者：显示名 + open_id + 角色
-  - name: 张斯佳, open_id: ou_aaa, role: 讨论
-  - name: 张瑶,   open_id: ou_bbb, role: 讨论
-  - name: 刘俊平, open_id: ou_ccc, role: 确认
-transcript: |                        # 相关消息原文（按时间）—— 人真正要看的内容，必带
-  17:49 张斯佳：有线下核验点，但无可预约时间，这里需要加提示么？
-  17:5x 张瑶：建议合并提示语「目前暂无线下审核点或没有可预约的时间…」
-  17:5x 刘俊平：可以处理
-summary: 线下核验点无可预约时间，确认合并提示语后处理   # （可选）一句话结论；缺省时由模型从 transcript 推
-</task-source>
-```
-
-Roles are not required to be pre-computed by the bridge — if `role` is missing,
-infer it from the `transcript` (谁提出 / 谁讨论 / 谁拍板"可以处理"). If a
-`summary` is absent, derive it from the `transcript`.
-
-**Feishu reality** — `chat_link` only opens the **group**, not a single message.
-So the practical "go back and find it" combo is **群链接 + occurred_at + transcript**:
-open the group, jump to that time, the transcript is the actual content. Label the
-link line **打开群** (never "原始消息") so nobody expects a one-click jump to the
-exact message. `trigger_message_id` is kept as the only hard anchor to that
-message (not clickable — for programmatic re-read / dedup / fallback).
-
-#### Rendered `## 来源` format
-
-```
-## 来源
-
-- 渠道：飞书群「{chat_name}」
-- 时间：{occurred_at}
-- 参与者：{讨论者们}（讨论），{确认者}（确认可处理）
-- 讨论要点：{summary}
-- 打开群：{chat_link}
-- 溯源 ID：chat={chat_id} · msg={trigger_message_id}{ thread_root_id 时追加 · thread={thread_root_id}}
-
-讨论摘录（按时间）：
-{transcript}
-```
-
-Only render lines whose data is present (e.g. omit `打开群` if there is no
-`chat_link`). Always keep `chat_id` + `trigger_message_id` (hard anchors) and the
-`讨论摘录`/`transcript` (the content humans actually read).
-
 ### Task Creation Confirmation
 
 After `create_task` succeeds, render based on the **response** (not the input
@@ -468,6 +416,19 @@ Categories: `task`, `project`, `repository`, `note`, `asset`, `all`. Result coun
 
 ---
 
+## 无人值守收发消息（Unattended messaging）
+
+When operating in unattended mode (`TOWER_UNATTENDED=1`) or acting as the bridge that relays a
+human's reply back to a parked task, follow the send/receive contract in
+[`references/unattended-messaging.md`](references/unattended-messaging.md). Key points:
+
+- Tower **only records + parks/resumes** — it never sends platform messages. You (the agent/bridge)
+  send via the platform's own MCP (Feishu/WeChat/OpenClaw…).
+- Every outbound ask/notify **must** carry the correlation token `[[tower:task=<taskId>]]`.
+- Relay a human's reply with the **`reply_to_ask(taskId, text)`** MCP tool (not raw
+  `send_task_terminal_input`) so Tower records the reply. If it returns `{ no_pending: true }`,
+  handle the message as an ordinary request.
+
 ## Important Rules
 
 - **Scope boundary**: You are a **task management operator only**. If the user asks you to write code, explain code, debug, search the web, read/write files, or anything outside Tower task management, reply: "抱歉，我只能帮你管理工作区、项目和任务。编码、调试等操作请在任务终端中完成。" Do NOT attempt to answer out-of-scope questions.

package/skills/tower/references/task-source.md

@@ -0,0 +1,80 @@
+# Task Source (`## 来源`) — detailed rendering
+
+Read this when the incoming prompt carries real source info — a parent-task
+derivation (`TOWER_TASK_ID` set) or a `<task-source>` bridge block. For the
+common "no source" case you don't need this file: just write `## 来源\n无`.
+
+## Parent task derivation (派生子任务)
+
+If `TOWER_TASK_ID` is set in your environment (run `echo $TOWER_TASK_ID` to check),
+you are operating **inside a Tower task terminal** — so any task you create here is
+a **child task derived from the current (parent) task**. Render its source as:
+
+```
+## 来源
+
+- 渠道：父任务派生
+- 父任务：{当前任务标题，知道就填}（id: $TOWER_TASK_ID）
+```
+
+Tower also records this link structurally on the new task's `parentTaskId`
+automatically (used for parent→child completion notifications) — this `## 来源`
+is just the human-readable mirror. The id alone is enough if you don't know the title.
+
+## Bridge metadata contract (`<task-source>` block)
+
+External bridges (Feishu/Lark, etc.) inject a machine-readable block into the
+message. When you see it, parse it, render the standardized `## 来源`, and then
+DROP the raw block from the description (don't store the tags):
+
+```
+<task-source>
+channel: feishu                      # 渠道 (feishu | openclaw | manual | ...)
+chat_name: 南京招生报名讨论群          # 群显示名
+chat_id: oc_xxxxxxxx                 # 群 ID（硬定位符，必带）
+occurred_at: 2026-06-16 17:49 +08:00 # 讨论/触发时间，带时区（用于进群后定位到具体那条）
+chat_link: https://applink.feishu.cn/client/chat/open?openChatId=oc_xxxxxxxx  # 打开「群」的链接（群级，飞书无法精确到单条消息）
+trigger_message_id: om_xxxxxxxx      # 触发那条消息的 ID（不可点，但唯一绑定该消息，必带；用于程序回读/去重/兜底）
+thread_root_id: om_yyyyyyyy          # （可选）话题根消息 ID
+participants:                        # 参与者：显示名 + open_id + 角色
+  - name: 张斯佳, open_id: ou_aaa, role: 讨论
+  - name: 张瑶,   open_id: ou_bbb, role: 讨论
+  - name: 刘俊平, open_id: ou_ccc, role: 确认
+transcript: |                        # 相关消息原文（按时间）—— 人真正要看的内容，必带
+  17:49 张斯佳：有线下核验点，但无可预约时间，这里需要加提示么？
+  17:5x 张瑶：建议合并提示语「目前暂无线下审核点或没有可预约的时间…」
+  17:5x 刘俊平：可以处理
+summary: 线下核验点无可预约时间，确认合并提示语后处理   # （可选）一句话结论；缺省时由模型从 transcript 推
+</task-source>
+```
+
+Roles are not required to be pre-computed by the bridge — if `role` is missing,
+infer it from the `transcript` (谁提出 / 谁讨论 / 谁拍板"可以处理"). If a
+`summary` is absent, derive it from the `transcript`.
+
+**Feishu reality** — `chat_link` only opens the **group**, not a single message.
+So the practical "go back and find it" combo is **群链接 + occurred_at + transcript**:
+open the group, jump to that time, the transcript is the actual content. Label the
+link line **打开群** (never "原始消息") so nobody expects a one-click jump to the
+exact message. `trigger_message_id` is kept as the only hard anchor to that
+message (not clickable — for programmatic re-read / dedup / fallback).
+
+## Rendered `## 来源` format
+
+```
+## 来源
+
+- 渠道：飞书群「{chat_name}」
+- 时间：{occurred_at}
+- 参与者：{讨论者们}（讨论），{确认者}（确认可处理）
+- 讨论要点：{summary}
+- 打开群：{chat_link}
+- 溯源 ID：chat={chat_id} · msg={trigger_message_id}{ thread_root_id 时追加 · thread={thread_root_id}}
+
+讨论摘录（按时间）：
+{transcript}
+```
+
+Only render lines whose data is present (e.g. omit `打开群` if there is no
+`chat_link`). Always keep `chat_id` + `trigger_message_id` (hard anchors) and the
+`讨论摘录`/`transcript` (the content humans actually read).