@clawos-dev/clawd 0.2.720 → 0.2.722

package/dist/owner-ui/owner.html

@@ -5,7 +5,7 @@
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
     <meta name="referrer" content="no-referrer" />
     <title>Clawd</title>
-    <script type="module" crossorigin src="/app/assets/owner-Dpx2FHaL.js"></script>
+    <script type="module" crossorigin src="/app/assets/owner-B8KkpCFg.js"></script>
     <link rel="stylesheet" crossorigin href="/app/assets/owner-BcG1zRor.css">
   </head>
   <body style="margin: 0">

package/dist/persona-defaults/persona-app-builder/mcp/clawd-app-builder/mcp-server.cjs

@@ -32211,7 +32211,7 @@ var DispatchRunArgsSchema = external_exports.object({
 }).refine((v) => v.targetPersona !== void 0 || v.dispatchId !== void 0, {
   message: "either targetPersona (new dispatch) or dispatchId (follow-up) is required"
 }).refine((v) => !(v.dispatchId !== void 0 && v.targetDeviceId !== void 0), {
-  message: "cross-device dispatch cannot be continued (dispatchId + targetDeviceId are mutually exclusive)"
+  message: "follow-ups take only dispatchId; the target device comes from the ledger row (dispatchId + targetDeviceId are mutually exclusive)"
 }).refine((v) => !(v.tool !== void 0 && v.targetDeviceId !== void 0), {
   message: "engine override is not supported for cross-device dispatch (tool + targetDeviceId are mutually exclusive)"
 }).refine((v) => !(v.dispatchId !== void 0 && (v.tool !== void 0 || v.model !== void 0)), {
@@ -32230,6 +32230,10 @@ var DispatchRecordSchema = external_exports.object({
   targetPersonaId: external_exports.string().min(1),
   /** A-side target device attribution; absence means local for existing records. Forwarding strips it from the B-side local ledger. */
   targetDeviceId: external_exports.string().min(1).optional(),
+  /** A-side cross-device rows: the B-side ledger id, used for follow-ups and for resuming polls after an A restart. */
+  remoteDispatchId: external_exports.string().min(1).optional(),
+  /** The A-side round B last accepted; a follow-up reopened but not yet accepted has remoteRound < round, so a restart must not resume polling it. */
+  remoteRound: external_exports.number().int().positive().optional(),
   /** B 的 sessionId；registerBSession 后回填 */
   workerSessionId: external_exports.string().min(1).optional(),
   taskText: external_exports.string(),
@@ -34315,7 +34319,7 @@ var METHOD_DOCS = {
     args: PersonaIdArgsSchema
   },
   "personaDispatch:run": {
-    summary: "\u628A\u4EFB\u52A1\u59D4\u6D3E\u7ED9\u53E6\u4E00\u4E2A persona\uFF08\u53EF\u8DE8\u8BBE\u5907\uFF09\uFF0C\u5F02\u6B65\u79D2\u56DE { dispatchId }\u3002targetPersona \u4E0E dispatchId **\u81F3\u5C11\u7ED9\u4E00\u4E2A**\uFF08\u524D\u8005\u65B0\u5F00\u3001\u540E\u8005\u7EED\u6D3E\uFF09\uFF1BdispatchId \u4E0E targetDeviceId **\u4E92\u65A5**",
+    summary: "\u628A\u4EFB\u52A1\u59D4\u6D3E\u7ED9\u53E6\u4E00\u4E2A persona\uFF08\u53EF\u8DE8\u8BBE\u5907\uFF09\uFF0C\u5F02\u6B65\u79D2\u56DE { dispatchId }\u3002targetPersona \u4E0E dispatchId **\u81F3\u5C11\u7ED9\u4E00\u4E2A**\uFF08\u524D\u8005\u65B0\u5F00\u3001\u540E\u8005\u7EED\u6D3E\uFF09\uFF1BdispatchId \u4E0E targetDeviceId **\u4E92\u65A5**\uFF08\u8DE8\u8BBE\u5907\u7EED\u6D3E\u4E5F\u53EA\u4F20 dispatchId\uFF0C\u8BBE\u5907\u4ECE\u53F0\u8D26\u53D6\uFF09",
     args: DispatchRunArgsSchema,
     argsConstraints: {
       anyOf: [{ required: ["targetPersona"] }, { required: ["dispatchId"] }],

package/dist/persona-defaults/persona-dataclaw-builder/mcp/clawd-app-builder/mcp-server.cjs

@@ -32211,7 +32211,7 @@ var DispatchRunArgsSchema = external_exports.object({
 }).refine((v) => v.targetPersona !== void 0 || v.dispatchId !== void 0, {
   message: "either targetPersona (new dispatch) or dispatchId (follow-up) is required"
 }).refine((v) => !(v.dispatchId !== void 0 && v.targetDeviceId !== void 0), {
-  message: "cross-device dispatch cannot be continued (dispatchId + targetDeviceId are mutually exclusive)"
+  message: "follow-ups take only dispatchId; the target device comes from the ledger row (dispatchId + targetDeviceId are mutually exclusive)"
 }).refine((v) => !(v.tool !== void 0 && v.targetDeviceId !== void 0), {
   message: "engine override is not supported for cross-device dispatch (tool + targetDeviceId are mutually exclusive)"
 }).refine((v) => !(v.dispatchId !== void 0 && (v.tool !== void 0 || v.model !== void 0)), {
@@ -32230,6 +32230,10 @@ var DispatchRecordSchema = external_exports.object({
   targetPersonaId: external_exports.string().min(1),
   /** A-side target device attribution; absence means local for existing records. Forwarding strips it from the B-side local ledger. */
   targetDeviceId: external_exports.string().min(1).optional(),
+  /** A-side cross-device rows: the B-side ledger id, used for follow-ups and for resuming polls after an A restart. */
+  remoteDispatchId: external_exports.string().min(1).optional(),
+  /** The A-side round B last accepted; a follow-up reopened but not yet accepted has remoteRound < round, so a restart must not resume polling it. */
+  remoteRound: external_exports.number().int().positive().optional(),
   /** B 的 sessionId；registerBSession 后回填 */
   workerSessionId: external_exports.string().min(1).optional(),
   taskText: external_exports.string(),
@@ -34315,7 +34319,7 @@ var METHOD_DOCS = {
     args: PersonaIdArgsSchema
   },
   "personaDispatch:run": {
-    summary: "\u628A\u4EFB\u52A1\u59D4\u6D3E\u7ED9\u53E6\u4E00\u4E2A persona\uFF08\u53EF\u8DE8\u8BBE\u5907\uFF09\uFF0C\u5F02\u6B65\u79D2\u56DE { dispatchId }\u3002targetPersona \u4E0E dispatchId **\u81F3\u5C11\u7ED9\u4E00\u4E2A**\uFF08\u524D\u8005\u65B0\u5F00\u3001\u540E\u8005\u7EED\u6D3E\uFF09\uFF1BdispatchId \u4E0E targetDeviceId **\u4E92\u65A5**",
+    summary: "\u628A\u4EFB\u52A1\u59D4\u6D3E\u7ED9\u53E6\u4E00\u4E2A persona\uFF08\u53EF\u8DE8\u8BBE\u5907\uFF09\uFF0C\u5F02\u6B65\u79D2\u56DE { dispatchId }\u3002targetPersona \u4E0E dispatchId **\u81F3\u5C11\u7ED9\u4E00\u4E2A**\uFF08\u524D\u8005\u65B0\u5F00\u3001\u540E\u8005\u7EED\u6D3E\uFF09\uFF1BdispatchId \u4E0E targetDeviceId **\u4E92\u65A5**\uFF08\u8DE8\u8BBE\u5907\u7EED\u6D3E\u4E5F\u53EA\u4F20 dispatchId\uFF0C\u8BBE\u5907\u4ECE\u53F0\u8D26\u53D6\uFF09",
     args: DispatchRunArgsSchema,
     argsConstraints: {
       anyOf: [{ required: ["targetPersona"] }, { required: ["dispatchId"] }],

package/dist/persona-defaults/persona-master/CLAUDE.md

@@ -143,8 +143,8 @@ daemon 数打回次数、同时把理由写进流水（一次调用两件事，
 返回 `{ rejectCount, needsOwnerAttention }`。**`needsOwnerAttention` 为 true
 （同一条线累计两次打回）→ 停下上报老板，不要再自行打回。**
 
-> 跨设备派出去的线（`targetDeviceId`）**不能续派**，协议层就禁止 `dispatchId + targetDeviceId` 同传。
-> 这类线目前无法打回，只能重新派一条新的——M1 只跑本机 worker，遇到跨设备先上报老板。
+> 跨设备派出去的线（`targetDeviceId`）续派 / 打回与本机线一样：只传 `dispatchId`，**不要**再带
+> `targetDeviceId`（协议层禁止两者同传，设备从台账取）。
 
 ### 6. 线中途上报问题