@clawos-dev/clawd 0.2.625 → 0.2.627

package/dist/dispatch/mcp-server.cjs

@@ -21533,7 +21533,8 @@ var DeploySecretPresenceSchema = external_exports.object({
 }).strict();
 var DEPLOY_STAGE_STATUSES = ["pending", "running", "done", "failed", "waiting", "skipped"];
 var DeployStageStatusSchema = external_exports.enum(DEPLOY_STAGE_STATUSES);
-var DEPLOY_STAGE_KEYS = ["build", "smoke", "deploy"];
+var DEPLOY_VERIFY_STAGE = "verify";
+var DEPLOY_STAGE_KEYS = ["build", "smoke", "deploy", DEPLOY_VERIFY_STAGE];
 var DeployStageKeySchema = external_exports.enum(DEPLOY_STAGE_KEYS);
 var DeployJobSchema = external_exports.object({
   key: DeployStageKeySchema,

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

@@ -21714,7 +21714,8 @@ var DeploySecretPresenceSchema = external_exports.object({
 }).strict();
 var DEPLOY_STAGE_STATUSES = ["pending", "running", "done", "failed", "waiting", "skipped"];
 var DeployStageStatusSchema = external_exports.enum(DEPLOY_STAGE_STATUSES);
-var DEPLOY_STAGE_KEYS = ["build", "smoke", "deploy"];
+var DEPLOY_VERIFY_STAGE = "verify";
+var DEPLOY_STAGE_KEYS = ["build", "smoke", "deploy", DEPLOY_VERIFY_STAGE];
 var DeployStageKeySchema = external_exports.enum(DEPLOY_STAGE_KEYS);
 var DeployJobSchema = external_exports.object({
   key: DeployStageKeySchema,
@@ -24604,6 +24605,12 @@ var PackageFindingSchema = EnvPackageSchema.omit({ localVersion: true, artifact:
   artifact: external_exports.object({ url: external_exports.string().url(), bin: external_exports.string() }).strict().optional()
 });
 
+// src/feishu-auth/deploy-environments.ts
+var DEPLOY_TARGETS = {
+  integration: { api: "https://api-int.clawos.chat", gateway: "https://persona-int.clawos.chat" },
+  production: { api: "https://api.clawos.chat", gateway: "https://persona.clawos.chat" }
+};
+
 // src/deploy/release-workflow.ts
 function renderDeployWorkflow(config2) {
   const identity = [
@@ -24807,6 +24814,22 @@ function renderDeployWorkflow(config2) {
     ...download("${{ inputs.environment == 'production' && 'persona-candidate' || 'persona-smoked' }}"),
     ...contract,
     ...runtime("register"),
+    ...job(DEPLOY_VERIFY_STAGE),
+    "    needs: deploy",
+    "    if: inputs.environment != 'production'",
+    "    steps:",
+    ...download("persona-smoked"),
+    ...contract,
+    "      - name: Verify ordinary user conversation after deployment",
+    "        env:",
+    `          CLAWD_INT_API_URL: \${{ vars.CLAWD_INT_API_URL || '${DEPLOY_TARGETS.integration.api}' }}`,
+    "          CLAWD_INT_TEST_LOGIN_PASS: ${{ secrets.CLAWD_INT_TEST_LOGIN_PASS }}",
+    "        run: |",
+    "          node clawos/cloud-host/pipeline/persona-verify.mjs \\",
+    "            --file candidate-release.json \\",
+    "            --persona-id '${{ steps.plan.outputs.persona_id }}' \\",
+    "            --engine '${{ steps.plan.outputs.engine }}'",
+    "",
     ...upload("persona-verified-${{ github.run_attempt }}")
   ].join("\n");
 }

package/dist/persona-defaults/persona-clawd-butler/.claude/skills/clawd-introspection/SKILL.md

@@ -11,32 +11,15 @@ description: 老板问本机 clawd 状态时触发——装了哪些 persona/ext
 
 **第一步先走 RPC**（clawd-rpc MCP 的 list / call）——daemon 在跑时它是状态的真源，目录布局只是实现细节。用 list 拉方法表（每条带中文说明），对着老板的问题挑方法调；方法表就是能力清单，别凭印象说 clawd 没有某能力。
 
-**RPC 查不到答案、或 daemon 没在跑，再翻文件。** 先 fetch 一次 `${CLAWOS_API}/api/docs/introspection/file-map.md`——它讲 `~/.clawd/` 下每个文件/目录是干啥的，是文件路线的地图。
+**文档只解释结构，不代表当前状态。** 需要了解字段含义时 fetch `${CLAWOS_API}/api/docs/introspection/file-map.md` 或 `state-schemas.md`；故障表征参考 `common-issues.md`。
 
-然后按具体子问题挑：
+**不直接读凭证或扫目录列状态。** `auth.json`、带凭证的 tunnel / owner identity 文件和含 connectToken 的 `contacts.json` 不读、不贴、不落盘；不调会返回 connectToken 的 `contact:list`。联系人授权通过界面或方法表里不返回凭证的接口查看。
 
-| 老板问的 | fetch |
-|---|---|
-| 具体 state/auth/tunnel/dispatch json 里字段啥意思 | `${CLAWOS_API}/api/docs/introspection/state-schemas.md` |
-| 典型故障表征怎么排（比如 tunnel 挂了、dispatch 卡住、session 报错） | `${CLAWOS_API}/api/docs/introspection/common-issues.md` |
-
-**文件兜底清单（Read / Bash）** —— 仅在 RPC 答不了时用：
-
-- `~/.clawd/state.json` daemon 运行时状态（pid / url / tunnelUrl）
-- `~/.clawd/tunnel.json` 远程接入配置
-- `~/.clawd/dispatch.json` dispatch 台账（正在跑 / 已完成的任务）
-- `~/.clawd/contacts.json` 联系人 + 授权（T-35 后授权数据全在这一份，legacy `capabilities.json` / `received-capabilities.json` 已 retire）
-- `~/.clawd/personas/` 装了哪些 persona
-- `~/.clawd/extensions-published.json` / `~/.clawd/extensions/` 装了哪些 extension
-- `~/.clawd/*.log` 各类 log（`clawd.log` 是 daemon 主 log）
-
-读文件时凭证不外显：`auth.json`（owner token）整份别读，`contacts.json` 里的 `connectToken` 等 token / secret 字段不贴进回答、不落盘。
-
-排障时：先走 RPC 看 daemon 侧状态；daemon 没响应再按 file-map 定位文件 Read，最后按 common-issues 里的表征匹配可能原因。
+RPC 不可用时说明无法确认当前状态。诊断可按用户的时间窗读取 `~/.clawd/log/clawd.log`、`frpc.log` 等日志，禁止把 persona 目录、旧 JSON 或远端不在本机的文件当作实时清单。读会话走 `history:read`，一定加 `slim:true`。
 
 ## fetch 失败了
 
-fetch 不到文档就照本机文件+ 现有认知答。**如果本机文件也答不了、又需要文档知识，直接告诉老板"我需要那份自省文档但拉不到，稍后再问一次或让 David 看一眼"**。别瞎猜字段含义。
+fetch 不到文档时仍先用 RPC 方法表与返回结果回答；需要的结构知识无法核实时，明确说明缺少哪份文档。RPC 也不可用就说明无法确认当前状态，不以目录或旧文件补猜。
 
 ## 回答风格
 

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

@@ -21714,7 +21714,8 @@ var DeploySecretPresenceSchema = external_exports.object({
 }).strict();
 var DEPLOY_STAGE_STATUSES = ["pending", "running", "done", "failed", "waiting", "skipped"];
 var DeployStageStatusSchema = external_exports.enum(DEPLOY_STAGE_STATUSES);
-var DEPLOY_STAGE_KEYS = ["build", "smoke", "deploy"];
+var DEPLOY_VERIFY_STAGE = "verify";
+var DEPLOY_STAGE_KEYS = ["build", "smoke", "deploy", DEPLOY_VERIFY_STAGE];
 var DeployStageKeySchema = external_exports.enum(DEPLOY_STAGE_KEYS);
 var DeployJobSchema = external_exports.object({
   key: DeployStageKeySchema,
@@ -24604,6 +24605,12 @@ var PackageFindingSchema = EnvPackageSchema.omit({ localVersion: true, artifact:
   artifact: external_exports.object({ url: external_exports.string().url(), bin: external_exports.string() }).strict().optional()
 });
 
+// src/feishu-auth/deploy-environments.ts
+var DEPLOY_TARGETS = {
+  integration: { api: "https://api-int.clawos.chat", gateway: "https://persona-int.clawos.chat" },
+  production: { api: "https://api.clawos.chat", gateway: "https://persona.clawos.chat" }
+};
+
 // src/deploy/release-workflow.ts
 function renderDeployWorkflow(config2) {
   const identity = [
@@ -24807,6 +24814,22 @@ function renderDeployWorkflow(config2) {
     ...download("${{ inputs.environment == 'production' && 'persona-candidate' || 'persona-smoked' }}"),
     ...contract,
     ...runtime("register"),
+    ...job(DEPLOY_VERIFY_STAGE),
+    "    needs: deploy",
+    "    if: inputs.environment != 'production'",
+    "    steps:",
+    ...download("persona-smoked"),
+    ...contract,
+    "      - name: Verify ordinary user conversation after deployment",
+    "        env:",
+    `          CLAWD_INT_API_URL: \${{ vars.CLAWD_INT_API_URL || '${DEPLOY_TARGETS.integration.api}' }}`,
+    "          CLAWD_INT_TEST_LOGIN_PASS: ${{ secrets.CLAWD_INT_TEST_LOGIN_PASS }}",
+    "        run: |",
+    "          node clawos/cloud-host/pipeline/persona-verify.mjs \\",
+    "            --file candidate-release.json \\",
+    "            --persona-id '${{ steps.plan.outputs.persona_id }}' \\",
+    "            --engine '${{ steps.plan.outputs.engine }}'",
+    "",
     ...upload("persona-verified-${{ github.run_attempt }}")
   ].join("\n");
 }