@itpay/cli 2.1.46 → 2.1.48

package/dist/src/state/config.js

@@ -1,144 +1,6 @@
-import { sellerSessionToken } from "./account_auth.js";
-// CLI configuration loader. Production defaults to app.itpay.ai; supported public overrides
-// are the official sandbox and dev Backends. Checkout
-// display-token persistence belongs to the cart session file, protected with
-// owner-only permissions. Provider secrets are explicitly out of scope here.
-import { createHash } from "node:crypto";
-import { homedir } from "node:os";
-import { mkdirSync } from "node:fs";
-import { resolve } from "node:path";
-import { HttpClient } from "../client/http.js";
-import { BackendClient } from "../client/backend.js";
-import { declaredAgentType } from "./agent_type.js";
-import { DeviceAuthority } from "./device_authority.js";
-import { OperationJournal } from "./operation_journal.js";
-export const DEFAULT_BASE_URL = "https://app.itpay.ai";
-export const DEV_BASE_URL = "https://dev.itpay.ai";
-export const SANDBOX_BASE_URL = "https://sandbox.itpay.ai";
-export const CLI_VERSION = "2.1.46";
-export const API_CONTRACT_REVISION = "sha256:c1e1f459c1d3844f6eeae21535b532abb2e48c3e320173c4faccd62992890dcd";
-const CART_SESSION_DEFAULT_DIR = ".itpay-v3";
-const CART_SESSION_FILENAME = "cart.json";
-const OPERATION_JOURNAL_FILENAME = "operations.json";
-const TASK_JOURNAL_FILENAME = "tasks.json";
-export function cliDistribution(env = process.env) {
-    if (env.ITPAY_DISTRIBUTION === "openclaw-skill-bundle")
-        return "openclaw-skill-bundle";
-    if (env.ITPAY_DISTRIBUTION === "kimi-plugin-bundle")
-        return "kimi-plugin-bundle";
-    return "npm";
-}
-export class BackendOverrideError extends Error {
-    code = "backend_override_forbidden";
-    constructor() {
-        super(`ITPAY_BACKEND_URL only supports ${DEFAULT_BASE_URL}, ${SANDBOX_BASE_URL}, or ${DEV_BASE_URL}`);
-        this.name = "BackendOverrideError";
-    }
-}
-export function resolveBackendURL(env = process.env) {
-    const requested = env.ITPAY_BACKEND_URL?.trim();
-    if (!requested || requested === DEFAULT_BASE_URL || requested === `${DEFAULT_BASE_URL}/`)
-        return DEFAULT_BASE_URL;
-    if (requested === SANDBOX_BASE_URL || requested === `${SANDBOX_BASE_URL}/`)
-        return SANDBOX_BASE_URL;
-    if (requested === DEV_BASE_URL || requested === `${DEV_BASE_URL}/`)
-        return DEV_BASE_URL;
-    if (env.ITPAY_CLI_DEV === "1" && /^http:\/\/(localhost|127\.0\.0\.1):\d+\/?$/.test(requested))
-        return requested.replace(/\/$/, "");
-    throw new BackendOverrideError();
-}
-export function qualifyBackendCommand(command, env = process.env) {
-    const requested = env.ITPAY_BACKEND_URL?.trim();
-    if (!requested)
-        return command;
-    const target = resolveBackendURL(env);
-    if (target === DEFAULT_BASE_URL)
-        return command;
-    if (!command.startsWith("itpay ") || command.startsWith(`ITPAY_BACKEND_URL=${target} `))
-        return command;
-    return `ITPAY_BACKEND_URL=${target} ${command}`;
-}
-function stateFilename(filename, baseURL) {
-    if (baseURL === DEFAULT_BASE_URL)
-        return filename;
-    const suffix = baseURL === SANDBOX_BASE_URL ? "sandbox" : baseURL === DEV_BASE_URL ? "dev" : `local-${createHash("sha256").update(baseURL).digest("hex").slice(0, 16)}`;
-    const dot = filename.lastIndexOf(".");
-    return dot < 0 ? `${filename}.${suffix}` : `${filename.slice(0, dot)}.${suffix}${filename.slice(dot)}`;
-}
-export function stateDir(env = process.env) {
-    return env.ITPAY_STATE_DIR ? resolve(env.ITPAY_STATE_DIR) : resolve(env.HOME || homedir(), CART_SESSION_DEFAULT_DIR);
-}
-export function cartSessionPath(env = process.env) {
-    if (env.ITPAY_CART_SESSION_PATH) {
-        return resolve(env.ITPAY_CART_SESSION_PATH);
-    }
-    const dir = stateDir(env);
-    mkdirSync(dir, { recursive: true });
-    return resolve(dir, stateFilename(CART_SESSION_FILENAME, resolveBackendURL(env)));
-}
-// Task journal (AUTH04): paused Service Executions per backend, so a login
-// completion can resume the SAME task instead of guessing from the latest order.
-export function taskJournalPath(env = process.env) {
-    if (env.ITPAY_TASK_JOURNAL_PATH) {
-        return resolve(env.ITPAY_TASK_JOURNAL_PATH);
-    }
-    const dir = stateDir(env);
-    mkdirSync(dir, { recursive: true });
-    return resolve(dir, stateFilename(TASK_JOURNAL_FILENAME, resolveBackendURL(env)));
-}
-export function loadConfig(env = process.env) {
-    const baseURL = resolveBackendURL(env);
-    const bearerToken = env.ITPAY_BEARER_TOKEN || undefined;
-    const agentType = declaredAgentType(env);
-    const checkoutCurrency = env.ITPAY_CURRENCY || "CNY";
-    const idempotencyKey = env.ITPAY_IDEMPOTENCY_KEY || `cli_${shortRandom()}`;
-    const ideImageAttach = env.ITPAY_IDE_IMAGE_ATTACH !== "0";
-    const ideImageDirOverride = env.ITPAY_IDE_IMAGE_DIR_OVERRIDE;
-    return {
-        baseURL,
-        environment: baseURL === DEFAULT_BASE_URL ? "production" : "development",
-        ...(agentType ? { agentType } : {}),
-        checkoutCurrency,
-        idempotencyKey,
-        ...(!env.ITPAY_IDEMPOTENCY_KEY ? { operationJournal: new OperationJournal(resolve(stateDir(env), stateFilename(OPERATION_JOURNAL_FILENAME, baseURL))) } : {}),
-        ideImageAttach,
-        ...(ideImageDirOverride ? { ideImageDirOverride } : {}),
-        ...(bearerToken ? { bearerToken } : {}),
-    };
-}
-export function operationID(config, operationKey) {
-    if (config.operationJournal)
-        return config.operationJournal.getOrCreate(operationKey);
-    return Promise.resolve(config.idempotencyKey);
-}
-export function newBackendClient(config) {
-    const authority = new DeviceAuthority({
-        baseURL: config.baseURL,
-        ...(config.agentType ? { requestedAgentType: config.agentType } : {}),
-        compatibilityHeaders: {
-            "X-ItPay-CLI-Version": CLI_VERSION,
-            "X-ItPay-Contract-Revision": API_CONTRACT_REVISION,
-        },
-    });
-    const http = new HttpClient({
-        baseURL: config.baseURL,
-        defaultHeaders: {
-            "X-ItPay-CLI-Version": CLI_VERSION,
-            "X-ItPay-Contract-Revision": API_CONTRACT_REVISION,
-        },
-        requestAuthorizer: (input) => {
-            if (/^\/v1\/(seller\/organizations(?:\/|\?|$)|library\/)/.test(input.path)) {
-                const token = config.bearerToken ?? sellerSessionToken(config.baseURL);
-                if (!token)
-                    throw new Error("Seller login required; run itpay sell auth login");
-                return Promise.resolve({ Authorization: `Bearer ${token}` });
-            }
-            return authority.authorizationHeaders(input);
-        },
-        recoverAuthorization: () => authority.recoverAuthorization(),
-    });
-    return new BackendClient(http);
-}
-function shortRandom() {
-    return Math.random().toString(36).slice(2, 10) + Math.random().toString(36).slice(2, 6);
-}
+const CLI_VERSION = "2.1.48";
+const API_CONTRACT_REVISION = "sha256:e61bd9998bddfaeee498d2306854f29a4e50c50a372acc26746b6c251c1b70f6";
+export {
+  API_CONTRACT_REVISION,
+  CLI_VERSION
+};

package/docs/agent/buyer/cart-checkout.json

@@ -1,13 +1,13 @@
 {
   "schema_version": "itp.agent_doc.v1",
   "role": "buyer",
-  "product_scope": "itpay is the single public CLI entry point for Buyer services and the existing itpay sell Seller workflow; $itpay is its user-facing Skill invocation.",
+  "product_scope": "itpay is the single public Buyer CLI entry point, and $itpay is its user-facing Skill invocation. It covers services, railway planning and booking, orders, authorized purchased content and refunds.",
   "topic": "cart-checkout",
-  "title": "Canonical Cart And Checkout Routing",
-  "purpose": "Use the canonical server Cart and route service-backed lines through Service Execution without hardcoded service logic.",
+  "title": "Advanced Multi-Service Cart And Historical Checkout Recovery",
+  "purpose": "Use only for an explicitly requested multi-service cart or a historical pinned flow. Normal selected services use the Skill purchase route.",
   "when_to_use": [
-    "A catalog item or variant is ready to add.",
-    "An interrupted Cart or Checkout needs recovery."
+    "The human explicitly requests combining several services in one Cart.",
+    "An existing Cart or historical Checkout needs recovery."
   ],
   "commands": [
     {
@@ -21,12 +21,12 @@
       "success_signal": "service-backed lines route to services next; ordinary lines route to buy"
     },
     {
-      "intent": "create an ordinary Checkout",
+      "intent": "prepare an ordinary official Checkout; no payment request",
       "command": "itpay --agent-type <agent_type> buy --cart <cart_id> --json",
       "success_signal": "status is human_checkout_required and handoff contains only fields usable by the current Host"
     },
     {
-      "intent": "create or resume a service Checkout",
+      "intent": "historical pinned service Checkout compatibility",
       "command": "itpay --agent-type <agent_type> services checkout <service_execution_id> --capability <capability_id> [--input key=value] [--email <email>] --json",
       "success_signal": "one Checkout handoff is returned; rerun with --resume after output or token loss"
     }
@@ -37,7 +37,7 @@
     "Railway query and booking use distinct Service Executions for one purchase journey. Start another execution for an independent intent.",
     "Only non-rail capabilities explicitly requiring delivery email may ask its purpose and value. Railway notification contact belongs to the protected checkout page with verified account email reuse; the Agent must not guess or collect it in chat.",
     "A lost Checkout response is retried with the same Cart and persisted idempotency operation.",
-    "A single railway service checkout normally follows its booking execution; Cart is used only when the returned flow calls for it."
+    "A normal selected service follows services purchase on its original execution. Do not introduce Cart as an extra tutorial or recovery fallback."
   ],
   "forbidden": [
     "Do not call ordinary buy for a service-backed Cart line.",
@@ -61,5 +61,5 @@
     "resume",
     "contact"
   ],
-  "purchase_consent": "Candidate selection is not price approval. Service-backed quote/cart/checkout requires a current scoped approve_purchase record; use the complete server template, default false. Only genuine matching approval allows true; material price/subject/terms changes invalidate it. Restore an existing Checkout before creating anything."
+  "purchase_consent": "Advanced and historical quote/cart flows retain the current quote-bound approve_purchase template and genuine matching consent. Do not bypass its exact quote or expiry. Normal new services use the Skill purchase preparation rule instead."
 }

package/docs/agent/buyer/catalog-list.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "itp.agent_doc.v1",
   "role": "buyer",
-  "product_scope": "itpay is the single public CLI entry point for Buyer services and the existing itpay sell Seller workflow; $itpay is its user-facing Skill invocation.",
+  "product_scope": "itpay is the single public Buyer CLI entry point, and $itpay is its user-facing Skill invocation. It covers services, railway planning and booking, orders, authorized purchased content and refunds.",
   "topic": "catalog-list",
   "title": "Browse ItPay V3 Service Catalog",
   "purpose": "Explain available services, outcomes, conditions, and prices in human language without exposing catalog identifiers.",
@@ -56,8 +56,7 @@
     },
     {
       "condition": "Non-rail Buyer selected a service and wants to purchase",
-      "topic": "cart-checkout",
-      "file": "docs/agent/buyer/cart-checkout.json"
+      "topic": "quickstart"
     }
   ],
   "search_terms": [
@@ -69,6 +68,5 @@
     "what to buy",
     "有哪些",
     "服务列表"
-  ],
-  "purchase_consent": "Candidate selection is not price approval. Service-backed quote/cart/checkout requires a current scoped approve_purchase record; use the complete server template, default false. Only genuine matching approval allows true; material price/subject/terms changes invalidate it. Restore an existing Checkout before creating anything."
+  ]
 }

package/docs/agent/buyer/identity-and-sessions.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "itp.agent_doc.v1",
   "role": "buyer",
-  "product_scope": "itpay is the single public CLI entry point for Buyer services and the existing itpay sell Seller workflow; $itpay is its user-facing Skill invocation.",
+  "product_scope": "itpay is the single public Buyer CLI entry point, and $itpay is its user-facing Skill invocation. It covers services, railway planning and booking, orders, authorized purchased content and refunds.",
   "topic": "identity-and-sessions",
   "title": "Device Identity And Session Recovery",
   "purpose": "Explain stable local identity, official Backend-scoped registrations, Agent Type instances, and bounded automatic session recovery.",

package/docs/agent/buyer/install-and-setup.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "itp.agent_doc.v1",
   "role": "buyer",
-  "product_scope": "itpay is the public CLI entry point for Buyer services and existing itpay sell Seller workflows.",
+  "product_scope": "itpay is the single public Buyer CLI entry point, and $itpay is its user-facing Skill invocation. It covers services, railway planning and booking, orders, authorized purchased content and refunds.",
   "topic": "install-and-setup",
   "title": "Install And Identify The ItPay Agent Runtime",
   "purpose": "Install in one host-permitted persistent npm location, prepare the real Agent once, and enable the same-package Skill.",

package/docs/agent/buyer/orders-refunds.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "itp.agent_doc.v1",
   "role": "buyer",
-  "product_scope": "itpay is the single public CLI entry point for Buyer services and the existing itpay sell Seller workflow; $itpay is its user-facing Skill invocation.",
+  "product_scope": "itpay is the single public Buyer CLI entry point, and $itpay is its user-facing Skill invocation. It covers services, railway planning and booking, orders, authorized purchased content and refunds.",
   "topic": "orders-refunds",
   "title": "Order, Delivery, Customer Care And Refund Recovery",
   "purpose": "Explain paid-order and delivery problems to the human, then read or manage the same owned Order without guessing payment, consumption, or refund state.",

package/docs/agent/buyer/payment-flow.json

@@ -1,18 +1,18 @@
 {
   "schema_version": "itp.agent_doc.v1",
   "role": "buyer",
-  "product_scope": "itpay is the single public CLI entry point for Buyer services and the existing itpay sell Seller workflow; $itpay is its user-facing Skill invocation.",
+  "product_scope": "itpay is the single public Buyer CLI entry point, and $itpay is its user-facing Skill invocation. It covers services, railway planning and booking, orders, authorized purchased content and refunds.",
   "topic": "payment-flow",
   "title": "Human Checkout Handoff And Payment Verification",
   "purpose": "Show the ItPay Checkout to the human and recover authoritative payment state without creating duplicate payment resources.",
   "when_to_use": [
-    "buy or services checkout returned human_checkout_required.",
+    "services purchase, buy or historical services checkout returned an official human handoff.",
     "The agent restarted or lost the Checkout output before payment was confirmed."
   ],
   "commands": [
     {
       "intent": "present the Checkout handoff",
-      "command": "<execute the exact command returned by buy or services checkout>",
+      "command": "<show the already-returned official handoff on the current Host>",
       "success_signal": "the returned official URL and/or QR supported by the actual Host is visible to the human"
     },
     {
@@ -22,12 +22,12 @@
     },
     {
       "intent": "recover a service Checkout handoff",
-      "command": "itpay services checkout <service_execution_id> --resume --json",
+      "command": "itpay services purchase <service_execution_id> --resume --json",
       "success_signal": "the same unpaid Checkout is reused with a fresh short-lived handoff"
     }
   ],
   "agent_rules": [
-    "Normal buyer flow opens the ItPay Checkout page; itpay pay and buy --pay are operator escape hatches.",
+    "Normal preparation generates an official filling/payment page; it does not call payment or charge. The human completes actual payment on that page.",
     "Use only handoff fields returned for the current Host and make them actually visible to the human.",
     "Obtain only missing required agreement or material price/term changes. Reuse a valid explicit confirmation for unchanged terms; never invent it.",
     "For a railway journey, show one official checkout for all legs: one total/payment, separate issuance. The page shares its authoritative payment_deadline_at/server_now/payment_remaining_seconds; reaching zero requires reading current status, not declaring cancellation.",
@@ -66,6 +66,5 @@
     "付款后",
     "不要重复付款",
     "支付确认"
-  ],
-  "purchase_consent": "Candidate selection is not price approval. Service-backed quote/cart/checkout requires a current scoped approve_purchase record; use the complete server template, default false. Only genuine matching approval allows true; material price/subject/terms changes invalidate it. Restore an existing Checkout before creating anything."
+  ]
 }

package/docs/agent/buyer/purchased-content.json

@@ -1,6 +1,6 @@
 {
   "schema_version": "1.0",
-  "product_scope": "buyer",
+  "product_scope": "itpay is the single public Buyer CLI entry point, and $itpay is its user-facing Skill invocation. It covers services, railway planning and booking, orders, authorized purchased content and refunds.",
   "topic": "purchased-content",
   "title": "Previously Purchased Content And Account History",
   "purpose": "Distinguish a previous purchase from a new service request, obtain one time-limited read authorization, and resume the original list, orders, or read command.",

package/docs/agent/buyer/quickstart.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "itp.agent_doc.v1",
   "role": "buyer",
-  "product_scope": "itpay is the single public CLI entry point for Buyer services and the existing itpay sell Seller workflow; $itpay is its user-facing Skill invocation.",
+  "product_scope": "itpay is the single public Buyer CLI entry point, and $itpay is its user-facing Skill invocation. It covers services, railway planning and booking, orders, authorized purchased content and refunds.",
   "topic": "quickstart",
   "title": "Route One Human Intent Through ItPay",
   "purpose": "Choose the correct first action from the human's words and continue through one authoritative CLI envelope at a time.",
@@ -45,7 +45,7 @@
     "Use --target only for a Host presentation destination. Use --input key=value only for simple scalars; nested objects use a small JSON file with the existing --input-json command.",
     "For non-rail delivery that explicitly requires email, ask only that missing value and explain its purpose. Railway identity and notification contact are handled on the protected official checkout page; never guess them.",
     "Explain useful service facts in ordinary language; never ask the human to run commands or learn internal IDs.",
-    "Normal payment uses the returned ItPay Checkout handoff.",
+    "Normal selected service purchase uses its complete services purchase confirmation template, then the returned official handoff; no manual quote/cart/buy chain.",
     "A railway query execution and its separate booking execution may serve one purchase intent; keep both references."
   ],
   "forbidden": [
@@ -67,7 +67,7 @@
       "topic": "purchased-content"
     },
     {
-      "condition": "Need Cart and Checkout routing",
+      "condition": "Explicit multi-service Cart or historical Cart recovery",
       "topic": "cart-checkout"
     },
     {
@@ -108,5 +108,5 @@
     "input"
   ],
   "reading_results": "Read normal CLI text directly, or parse the complete --json envelope with the host file reader. If saving stdout to a file, first check the command exit code, then read the whole file with cat or the existing file tool. Keep stderr separate; do not use head, tail, regex or a custom script to recover truncated results. Write complex input as a small JSON file and use --input-json.",
-  "purchase_consent": "Candidate selection is not price approval. Service-backed quote/cart/checkout requires a current scoped approve_purchase record; use the complete server template, default false. Only genuine matching approval allows true; material price/subject/terms changes invalidate it. Restore an existing Checkout before creating anything."
+  "purchase_consent": "Follow the same-package Skill purchase preparation rule: current complete review → reuse matching real consent or ask only what is missing → write flat file_content → services purchase → show the official entry. This step does not request payment."
 }

package/docs/agent/buyer/rail-booking.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "itp.agent_doc.v1",
   "role": "buyer",
-  "product_scope": "itpay is the single public CLI entry point, and $itpay is its user-facing Skill invocation. Under that one product entry point, the two top-level commerce actions are buy and sell: Buyer workflows are available now; Seller workflows use the same entry point via itpay sell.",
+  "product_scope": "itpay is the single public Buyer CLI entry point, and $itpay is its user-facing Skill invocation. It covers services, railway planning and booking, orders, authorized purchased content and refunds.",
   "topic": "rail-booking",
   "title": "Railway Query, Planning, and Ticket Booking",
   "purpose": "One railway route from understanding the request to saved results, booking, protected checkout, order status and refunds.",
@@ -13,7 +13,7 @@
     "query_vs_booking": "Exact/Smart returns a query execution and saved evidence. Booking creates a separate execution from a server-issued selection; it is not a repeated search.",
     "comparison": "If the human only asked to compare, answer within the searched scope and stop without a buy-or-not question. Reuse already-read unchanged Skill/docs in this context; do not repeat install/readyz/docs at each step. A clear purchase delegation permits selection under their rules, subject to required human terms.",
     "public_entry": "One public service itpay-rail declares query_exact, query_smart and prepare_purchase. Query, booking, Checkout and order remain separate identities. Legacy IDs are only for recovering their pinned historical executions.",
-    "price_approval": "Choosing a candidate or confirming seat/whole-journey terms is not approving price. Read the current scoped approve_purchase template after quote; record true only for genuine matching exact-price or capped-budget approval, or an explicitly authorized official-page confirmation. Reuse matching approval; never fabricate it."
+    "price_approval": "Use the complete purchase review and price policy under the formal Skill consent rule; one confirmation covers the actual itinerary, party, price policy and terms. Selection alone is not consent. The coordinator compares the real supplier quote; changed material conditions cannot reuse narrower approval."
   },
   "flow_at_a_glance": [
     {
@@ -49,13 +49,13 @@
     {
       "step": "review",
       "command": "itpay services next <booking_execution_id> --json",
-      "returns": "current review revision, material terms and a non-executable confirm_booking input_template",
-      "next": "submit the returned actor-type agent template only after genuine consent; reuse an unchanged explicit consent for code-only correction"
+      "returns": "complete purchase summary, current server reference and flat purchase confirmation file",
+      "next": "reuse genuine matching consent, ask only missing conditions, then execute the returned services purchase input template"
     },
     {
       "step": "checkout",
-      "command": "use the returned next or handoff for the same booking execution",
-      "returns": "an official protected payment entry",
+      "command": "itpay services purchase <booking_execution_id> --input-json <purchase-confirmation.json> --json",
+      "returns": "one original official page, or original progress with a bounded purchase --resume action; no payment requested",
       "next": "show the official entry using the current host immediately before optional memory/log writing, then stop; retain necessary safety/permissions, do not infer paid or issued"
     },
     {
@@ -125,21 +125,22 @@
     "whole_journey": "Use the returned complete ticket plan booking_template: ordered selections (2–3 legs) from one owner/snapshot/revision/plan, or selection for one leg. One booking, one refreshed whole quote, one checkout, one order and one payment; each leg issues separately without connection or joint-seat guarantees. Raw legs are single-leg compatibility only; never hand-compose multi-leg legs when complete selections are missing or expired. Do not combine different plans or choose per-leg payment by default. Historical details without a whole-journey template do not prove whole-journey support."
   },
   "review_and_checkout": {
-    "review": "Copy the returned complete interaction.input_template.input, current revision and notice. For a whole journey, each ordered leg has its own seat_type and an object preference per passenger; default auto, never null/string arrays. Use known choices and confirm only missing genuine terms consent or material changes. Set accept_non_guaranteed=true only after real consent; delegation or choosing a train alone is not terms consent. The false default is protection, not a broken template; if consent is missing, ask the returned review.consent_question once. Seat/berth placement requests differ from the whole-journey separate-issuance and partial-outcome terms; use the current notice.",
+    "review": "Read every ordered leg, seat class, party size, whole-journey terms and current price policy in the purchase summary. Copy the complete flat file_content, preserving server review_ref/request_key. Use the formal Skill rule to reuse genuine unchanged consent or ask only missing conditions. The coordinator applies the original railway review template and checks the real supplier quote; do not separately assemble confirm_booking, approve_purchase, cart or buy.",
     "equivalent_correction": "If only seat code spelling changes while train, actual seat class, party, price and terms are identical, reuse an existing explicit human approval. Material draft changes or missing approval require human confirmation. Reuse accepted original endpoints, no-seat, overnight and incomplete-coverage facts when unchanged; never silently substitute the destination.",
     "checkout": "Present the complete itinerary, total and single official handoff: one payment, separate issuance. The human enters one passenger set on that page; verified account notification email is reused there and can be changed for this order. Do not ask or guess traveler identity/email in chat. Use the returned checkout payment deadline, not an estimated duration. Handoff is not payment, and payment is not all legs issued."
   },
   "continue_and_aftercare": {
     "same_execution": "Read the same booking/checkout/order. Report issued only when every leg is confirmed issued; partial or unknown outcomes keep the same order and successful tickets, reconcile before retry, and explain the affected leg. No automatic rebuy or full-refund promise.",
     "saved_vs_live": "A saved snapshot remains historical evidence after expiry. Real-time booking or quote credentials may expire and require the documented fresh validation path; rereading an old token does not renew it.",
-    "refund": "For railway refund/change use itpay aftercare list --order <order_id> --json. Select returned leg/passenger targets from the user’s request, explain scope and manual processing, submit the complete current template. Request acceptance is not supplier success or money returned. Read the same case; concrete change proposals need current-revision consent and actual fee facts. No automatic change payment or replacement purchase."
+    "refund": "For railway refund/change use itpay aftercare list --order <order_id> --json. Select returned leg/passenger targets from the user’s request, explain scope and manual processing, submit the complete current template. Request acceptance is not supplier success or money returned. Read the same case; concrete change proposals need current-revision consent and actual fee facts. No automatic change payment or replacement purchase.",
+    "waiting": "Use the returned bounded same-task next command: up to 60 seconds per continuation, 120 seconds cumulative automatic waiting. Collect the same host session output before continuing. Budget expiry means still processing, not no trains or failed. Human terms, unresolved payment and terminal outcomes stop automatic polling."
   },
   "exceptional_branches": {
     "login_required": "Use itpay auth login --json, complete the official handoff, then execute the returned recovery command for the same paused query. Login returning a command does not execute it.",
     "rate_limited": "Respect returned retry_after and continue the same execution.",
     "booking_review_invalid": "Read the same booking review and use the returned seat code; reuse real consent only under the strict equivalent-correction rule.",
     "booking_review_changed": "Read the current revision and compare material terms; confirm new terms only when changed.",
-    "selection_stale": "Saved result stays readable, but follow the current owner action for new live inventory and quote evidence; do not assume reread refreshes the token.",
+    "selection_stale": "Saved details never refresh inventory or renew credentials. Only when the current server response proves safe_new_query and no existing purchase, write the complete original public query file, without reuse_from, and refresh once. Match the full itinerary, trains, seat classes and price to the original choice rather than selecting the new rank 1. Reuse genuine unchanged consent; explain and confirm material changes. Existing booking or unknown payment restores only the same purchase. Failed purchase-history evidence stops automatic refresh; do not loop on historical details.",
     "unknown_paid_outcome": "Read the same checkout/order before any mutation. Never repeat payment or create a new order on an unknown outcome.",
     "lock": "Normal device authorization uses no legacy lock. Preserve identity and old lock files; follow the actual error stage, not a generic lock-repair command.",
     "empty": "Report verified scope, failures and missing evidence separately. Do not guess a new date or station as a generic repair. Explain checked scope first, then propose at most two evidence-backed directions. Ask consent before changing a locked endpoint; after consent copy the complete original input and change only the accepted side in a new query.",
@@ -169,8 +170,9 @@
   "saved_followup": "Use returned refine_preferences with expected_query_revision for arrival/departure times, passengers, seat preference or priority; rerank uses existing facts. Only endpoints/date/new scope require a new query. Profiles compare within one journey, not the whole catalog. Fares and service fees are whole-journey totals for the stated people; observed available is not proof of ample inventory. Page limit is 1-20; follow next_offset exactly, never infer full-catalog optimality from the visible page. Byte-limited pages may contain fewer rows than limit. Area station candidates are not guaranteed nearest; transfer wait/minimum are facts, not a low-risk guarantee.",
   "actor_conventions": {
     "location_confirmation": "Use the returned human template only for the user's real place choice; no delegated human action.",
-    "journey_terms": "workflow:confirm_booking and booking_review_invalid recovery accept agent-reported genuine consent; default false, never infer from purchase delegation.",
+    "journey_terms": "Normal preparation uses the purchase confirmation file and real user_answer. Historical workflow:confirm_booking recovery retains its original agent-reported genuine consent rule; default false.",
     "ordinary_human_action": "Use its published actor rule; do not generalize railway permission.",
-    "price_approval": "approve_purchase uses actor-type agent with the unchanged server-scoped approval template and genuine matching approval; candidate choice is not price approval."
-  }
+    "price_approval": "Historical approve_purchase keeps its exact server-scoped quote binding and actor-type agent; it is not the new default route."
+  },
+  "consent_template_semantics": "Template false means approval is not recorded, not that the human must answer again. When user_answer_required is absent, check explicit chat or recorded consent for the current scope, party, price and terms; reuse it unchanged, ask only for missing consent or material differences, and never invent approval."
 }

package/docs/agent/buyer/rail-fast-checkout.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "itp.agent_doc.v1",
   "role": "buyer_agent",
-  "product_scope": "itpay_rail",
+  "product_scope": "itpay is the single public Buyer CLI entry point, and $itpay is its user-facing Skill invocation. It covers services, railway planning and booking, orders, authorized purchased content and refunds.",
   "topic": "rail-fast-checkout",
   "title": "Rail Fast Checkout — Delegated Purchase Supplement",
   "purpose": "Short delegated-purchase supplement to rail-booking; host presentation differences only.",
@@ -22,7 +22,7 @@
       "command": "Use the current result’s booking_template and returned next action",
       "notes": [
         "Select under the buyer’s unchanged rules. Required human terms still require real consent. Continue the same booking execution.",
-        "Copy the complete plan template into one booking; raw legs are single-leg compatibility only, multi-leg purchases require the complete selections template; one whole quote and official payment entry, separate issuance. Use the returned full review JSON; only missing real agreement requires asking."
+        "Copy the complete ordered plan template into one booking. Its complete purchase review leads to one services purchase confirmation and official entry; reuse genuine unchanged consent. Separate leg issuance remains, not separate payments."
       ]
     },
     {

package/docs/agent/buyer/render-hosts.json

@@ -1,12 +1,12 @@
 {
   "schema_version": "itp.agent_doc.v1",
   "role": "buyer",
-  "product_scope": "itpay is the single public CLI entry point for Buyer services and the existing itpay sell Seller workflow; $itpay is its user-facing Skill invocation.",
+  "product_scope": "itpay is the single public Buyer CLI entry point, and $itpay is its user-facing Skill invocation. It covers services, railway planning and booking, orders, authorized purchased content and refunds.",
   "topic": "render-hosts",
   "title": "Agent Type And Human Handoff Rendering",
   "purpose": "Use only the handoff fields returned for the current Agent Type and make Checkout or read authorization genuinely visible on that surface.",
   "when_to_use": [
-    "buy, services checkout, checkout, pay, or vault access returned a human handoff.",
+    "services purchase or an existing Checkout/authorization reader returned a human handoff.",
     "The human cannot see a Checkout or authorization QR image or link."
   ],
   "host_contracts": [
@@ -33,7 +33,7 @@
     {
       "agent_type": "workbuddy",
       "default_host": "plain-chat",
-      "responsibility": "execute handoff.agent_action exactly once to open the fully rendered handoff.url with present_files, then send handoff.mobile_url as a clickable link that jumps straight into Alipay or WeChat Pay on a phone; show the amount and stop"
+      "responsibility": "If present_files is already available, execute the returned agent_action once; otherwise show the original official URL in this turn. Show mobile_url when present and the amount, then stop."
     },
     {
       "agent_type": "zcode",
@@ -57,7 +57,7 @@
       "native_hosts": [
         "telegram"
       ],
-      "responsibility": "pass the native OpenClaw entry target explicitly; for Telegram execute handoff.agent_action unchanged, then treat itp:grant_confirmed callbacks only as permission to query the same Checkout and follow Backend grant state; otherwise show the returned HTTPS QR image and Checkout URL"
+      "responsibility": "Preserve the trusted native Host/target. Use the returned message action only if its tool is available now; otherwise show the official URL in this turn. Callbacks only permit reading the same state, never prove payment."
     }
   ],
   "commands": [
@@ -75,7 +75,7 @@
   "agent_rules": [
     "Agent Type is stable identity; Host is presentation and may be explicitly overridden. Once the official handoff is available, show it on this host before optional memory/log work; retain necessary safety and permissions.",
     "A local QR path is not visible until a desktop Agent attaches or renders that file on the human-facing surface; WorkBuddy Checkout handoff uses its returned Card Link and mobile URL; auth login may separately return a local QR path.",
-    "For workbuddy with plain-chat, execute handoff.agent_action exactly once; it calls present_files with handoff.url as the only files element and opens the rendered Card Link in the right-side browser, then send handoff.mobile_url so phone users can tap straight into Alipay or WeChat Pay.",
+    "For WorkBuddy, use present_files once only if already available; otherwise show the original handoff.url immediately. Send mobile_url when present. Do not research or install a tool before delivering the entry.",
     "For zcode with plain-chat, open handoff.url in the built-in browser and also send handoff.mobile_url as the phone entry; do not only paste text, download or rebuild a QR, or invent a private browser-tool payload; when the built-in browser is unavailable show both clickable links.",
     "For doubao-work with plain-chat, show two labeled official links: handoff.mobile_url for direct same-phone opening and handoff.qr_image_url for saving or scanning on another device; do not parse credentials, download or rebuild the QR, or create an alternative resource.",
     "If the WorkBuddy action fails, send the original handoff.url and handoff.mobile_url, report that it did not auto-open, and stop without creating another payment resource.",
@@ -83,7 +83,8 @@
     "Do not claim a handoff was shown until the official entry supported by this Host is genuinely visible. A link-only Host does not require a QR.",
     "IM Hosts that require a target must receive --target before Checkout creation. OpenClaw has no default Host; Kimi Code uses terminal.",
     "OpenClaw Telegram uses flat url/value buttons for deployed-version compatibility. A grant_confirmed callback carries only the Checkout ID, never a display token, and never proves payment or an active grant.",
-    "Business flow is the same across hosts. Vault grants apply only to protected purchased-content access, not every railway step."
+    "Business flow is the same across hosts. Vault grants apply only to protected purchased-content access, not every railway step.",
+    "Image preparation has a short budget. A failed or slow image does not invalidate an already verified, currently payable official URL; show that URL in the same turn, without creating another Checkout."
   ],
   "forbidden": [
     "Do not expose display tokens separately from the tokenized Checkout handoff.",

package/docs/agent/buyer/service-feedback.json

@@ -1,7 +1,7 @@
 {
   "schema_version": "itp.agent_doc.v1",
   "role": "buyer",
-  "product_scope": "itpay is the single public CLI entry point. Service feedback records one safe Agent postmortem for an existing order item; a human rating and comment are optional and it never replaces delivery recovery, refund policy, or customer care.",
+  "product_scope": "itpay is the single public Buyer CLI entry point, and $itpay is its user-facing Skill invocation. It covers services, railway planning and booking, orders, authorized purchased content and refunds.",
   "topic": "service-feedback",
   "title": "Record A Completed Service Postmortem",
   "purpose": "Finish the original order outcome first, then persist safe process context and any explicit human rating or comment without exposing commands or internal identifiers.",

package/docs/cli-reference/agent-types.md

@@ -1,6 +1,6 @@
 # Agent Type And Host Contract
 
-> **Product boundary:** `itpay` is the single public CLI entry point, and `$itpay` is its user-facing Skill invocation. The same entry point supports Buyer workflows and the existing `itpay sell` Seller workflow.
+> **Product boundary:** `itpay` is the single public CLI entry point, and `$itpay` is its user-facing Skill invocation. The public package provides Buyer workflows; Seller authoring source is maintained separately.
 
 `--agent-type` 表示哪类运行时在运行 CLI，用于 Agent 实例归属和定制 instruction。`--host` 表示输出展示在哪里；`--target` 只是在某些 Host 中指定 chat/channel/open ID。三者不可混用，窗口、任务和对话也不是身份。
 

package/docs/cli-reference/commands/auth.md

@@ -93,4 +93,3 @@ Terminal and error states:
 - Login never grants Vault content, passenger history, or another Agent's authority. Other devices/platforms enroll and authorize separately.
 - After `authenticated`, server-side identity is re-read; an anonymous execution blocked at the quota step resumes with `services run <service> --execution <id> --json` — no new execution, no re-asked itinerary.
 - Refusing or cancelling login deletes nothing: saved results and purchase options remain usable.
-- Seller authoring uses `itpay sell auth` separately.

package/docs/cli-reference/commands/buy.md

@@ -1,6 +1,6 @@
 # `itpay buy`
 
-> **Product boundary:** `itpay` is the single public CLI entry point, and `$itpay` is its user-facing Skill invocation. The same entry point supports Buyer workflows and the existing `itpay sell` Seller workflow.
+> **Product boundary:** `itpay` is the single public CLI entry point, and `$itpay` is its user-facing Skill invocation. The public package provides Buyer workflows; Seller authoring source is maintained separately.
 
 ## 范围与意义
 

package/docs/cli-reference/commands/cart/add.md

@@ -1,6 +1,6 @@
 # `itpay cart add`
 
-> **Product boundary:** `itpay` is the single public CLI entry point, and `$itpay` is its user-facing Skill invocation. The same entry point supports Buyer workflows and the existing `itpay sell` Seller workflow.
+> **Product boundary:** `itpay` is the single public CLI entry point, and `$itpay` is its user-facing Skill invocation. The public package provides Buyer workflows; Seller authoring source is maintained separately.
 
 ## 服务报价的批准边界
 

package/docs/cli-reference/commands/cart/clear.md

@@ -1,6 +1,6 @@
 # `itpay cart clear`
 
-> **Product boundary:** `itpay` is the single public CLI entry point, and `$itpay` is its user-facing Skill invocation. The same entry point supports Buyer workflows and the existing `itpay sell` Seller workflow.
+> **Product boundary:** `itpay` is the single public CLI entry point, and `$itpay` is its user-facing Skill invocation. The public package provides Buyer workflows; Seller authoring source is maintained separately.
 
 ## 范围与意义
 

package/docs/cli-reference/commands/cart/index.md

@@ -1,6 +1,6 @@
 # `itpay cart`
 
-> **Product boundary:** `itpay` is the single public CLI entry point, and `$itpay` is its user-facing Skill invocation. The same entry point supports Buyer workflows and the existing `itpay sell` Seller workflow.
+> **Product boundary:** `itpay` is the single public CLI entry point, and `$itpay` is its user-facing Skill invocation. The public package provides Buyer workflows; Seller authoring source is maintained separately.
 
 ## 命令范围
 

package/docs/cli-reference/commands/cart/next.md

@@ -1,6 +1,6 @@
 # `itpay cart next`
 
-> **Product boundary:** `itpay` is the single public CLI entry point, and `$itpay` is its user-facing Skill invocation. The same entry point supports Buyer workflows and the existing `itpay sell` Seller workflow.
+> **Product boundary:** `itpay` is the single public CLI entry point, and `$itpay` is its user-facing Skill invocation. The public package provides Buyer workflows; Seller authoring source is maintained separately.
 
 ## 服务报价的批准边界