@xiashe/cli 0.1.18 → 0.1.20

package/README.md

@@ -51,7 +51,8 @@ Production defaults:
 - `xiashe payment bridge-info` checks that the official buyer CLI is available without querying the wallet. `payment doctor` remains a manual diagnostic only.
 - `xiashe payment pay` requests the resource once, saves its exact 402 request in a private local file, and passes that file plus one stable session id to the official buyer CLI. It requires an HTTPS AI-Collect resource URL, a visible purchase-purpose summary, and `--confirm`.
 - `xiashe payment status` resumes the same local attempt with its official query credential and returns a normalized status only. No wallet protocol payload or proof is printed. A QR or confirmation image is exposed only as `officialMedia` when the official wallet emitted that image in the same invocation; the bridge never generates one itself.
+- `xiashe payment diagnose` is read-only. It reports the last stored safe diagnosis for that local attempt, without contacting Alipay, replaying the resource, or exposing its local query credential.
 
 An Agent must never add `--confirm` before the user has explicitly agreed to the displayed purpose. If the wallet is unavailable, obtain permission before running the official `@alipay/agent-payment` setup, then run `payment doctor` again.
 
-For a clean Codex Task, the XiaShe MCP response provides a version-pinned ephemeral command such as `npx -y @xiashe/cli@0.1.18 payment bridge-info`. No global `xiashe` installation is required for that path. The Agent must run the subsequent payment and status commands exactly as supplied, in the foreground: it must inspect the bridge JSON instead of suppressing output or guessing status from shell text. Failed attempts include a redacted `diagnosis` object and `userVisible` next step; do not replace them with a generic payment-failed message.
+For a clean Codex Task, the XiaShe MCP response provides a version-pinned ephemeral command such as `npx -y @xiashe/cli@0.1.20 payment bridge-info`. No global `xiashe` installation is required for that path. The Agent must run the subsequent payment and status commands exactly as supplied, in the foreground: it must inspect the bridge JSON instead of suppressing output or guessing status from shell text. Failed attempts include a redacted `diagnosis` object and `userVisible` next step; do not replace them with a generic payment-failed message.

package/bin/xiashe.mjs

@@ -38,7 +38,8 @@ const {
   checkAlipayWallet,
   getAlipayWalletBridgeInfo,
   payAlipay402Resource,
-  queryAlipay402Resource
+  queryAlipay402Resource,
+  diagnoseAlipay402Resource
 } = sdk;
 
 const EXIT_USAGE = 2;
@@ -99,6 +100,7 @@ Usage:
   ${c} payment bridge-info|doctor
   ${c} payment pay --resource-url <https-url> --intent-summary <text> --confirm [--wallet-timeout-ms <ms>]
   ${c} payment status --resource-url <https-url>
+  ${c} payment diagnose --resource-url <https-url>
 
   ${c} ops doctor
 
@@ -1180,7 +1182,13 @@ async function cmdPayment(sub, args, global) {
     print(result, global);
     return;
   }
-  fail(`Usage: ${COMMAND_NAME} payment bridge-info|doctor|pay|status`, EXIT_USAGE);
+  if (sub === 'diagnose') {
+    const resourceUrl = requireArg(flags['resource-url'] || flags.resourceUrl || flags.r, '--resource-url');
+    const result = await diagnoseAlipay402Resource({ resourceUrl });
+    print(result, global);
+    return;
+  }
+  fail(`Usage: ${COMMAND_NAME} payment bridge-info|doctor|pay|status|diagnose`, EXIT_USAGE);
 }
 
 async function cmdOps(sub, args, global) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@xiashe/cli",
-  "version": "0.1.18",
+  "version": "0.1.20",
   "type": "module",
   "bin": {
     "xiashe": "bin/xiashe.mjs"
@@ -10,7 +10,7 @@
     "README.md"
   ],
   "dependencies": {
-    "@xiashe/sdk": "0.1.18"
+    "@xiashe/sdk": "0.1.20"
   },
   "engines": {
     "node": ">=20"