@itpay/cli 0.2.16 → 2.0.0-rc.1

package/skills/itpay-buyer/SKILL.md

@@ -1,281 +1,150 @@
 ---
 name: itpay-buyer
 description: >
-  Use this skill when an AI agent helps a human discover, choose, buy, pay for,
-  or receive an ItPay service through the `itp` CLI. This is a quick-start
-  directory and safety boundary for buyer agents; detailed flow guidance lives
-  in `itp docs ... --role buyer --json`.
+  Use the ItPay V3 CLI when a human asks an AI agent to discover services,
+  use a free capability, buy a paid result, show an ItPay checkout QR, recover
+  an interrupted purchase, or read a result covered by a temporary human grant.
 ---
 
-# ItPay Buyer Agent Skill
+# ItPay V3 Buyer
 
-You are acting as an ItPay buyer agent. Your job is to help the human discover
-services, choose a purchase option, add the selected purchase option to cart, create checkout,
-show first-purchase account authorization when required, show the returned
-payment QR, wait for verified payment, and report redacted secure delivery
-status.
+Use the CLI as the control surface. Do not recreate ItPay API calls or invent a
+service-specific workflow. The backend returns the next valid actions for each
+catalog item and Service Execution.
 
-This skill is intentionally short. Do not try to memorize the entire ItPay
-protocol from this file. Use the CLI docs graph whenever you need details.
+## Bootstrap
 
-## Start Here
+```bash
+npm install -g @itpay/cli
+itpay readyz
+itpay docs show quickstart
+```
+
+This prerelease defaults to `https://test.itpay.ai`. Set `ITPAY_BACKEND_URL`
+only for an intentional override.
 
-Every non-doc ItPay command must include the current client context. `--host`
-means the human-visible client/surface, not where the shell command runs. In
-Codex desktop chat use `--host codex` even when calling `itp` through shell;
-use `--host terminal` only when the human is directly reading a terminal. The
-CLI will stop with `client_context_required` or `client_target_required`
-rather than guess.
+Every commerce flow must identify the real runtime. Pass the global option
+immediately after `itpay`, or set `ITPAY_AGENT_TYPE` once:
 
-```text
-Codex app:        --host codex
-Claude Code app:  --host claude-code
-Terminal:         --host terminal
-Plain chat:       --host plain-chat
-OpenClaw Telegram private/group chat: --host telegram --target <inbound_meta.chat_id>
+```bash
+itpay --agent-type codex-desktop catalog list --json
 ```
 
-For Telegram groups or @mention flows, use the same OpenClaw inbound
-`chat_id` as the target, for example `--target telegram:-1001234567890`.
-OpenClaw owns group allowlists and mention policy; ItPay only echoes the target
-into the returned `agent_action`.
+Examples include `codex-desktop`, `codex-cli`, `claude-code-desktop`,
+`claude-code-cli`, and the actual WorkBuddy/OpenClaw runtime name. Never rotate
+the type or local device files to obtain more free quota. The CLI enrolls one
+signed device under `~/.itpay-v3/device` and registers each runtime on it.
 
-If a response contains `agent_action`, execute that action before writing any
-normal reply or running wait/status. For Telegram/terminal this may be
-`agent_action.command` or `agent_action.argv`; for Codex/Claude Code this may
-be `agent_action.markdown`, which must be sent exactly to the current chat.
-If the action cannot be made visible to the human, stop and say why.
+## Golden Flow
 
-Run these commands before buying:
+1. Discover, then use IDs returned by the CLI:
 
 ```bash
-itp status --refresh --host <client> --json
-itp docs show quickstart --role buyer --json
-itp docs list --role buyer --json
+itpay --agent-type <agent_type> catalog list --json
+itpay --agent-type <agent_type> services start <service_id>
 ```
 
-If you are confused, search the agent docs instead of guessing:
+2. Ask the server for the next step:
 
 ```bash
-itp docs search "<what you need to know>" --role buyer --json
+itpay --agent-type <agent_type> services next <service_execution_id> --json
 ```
 
-## Standard Buyer Flow
-
-```text
-read this skill
--> read quickstart doc
--> run status --refresh; follow next.command if unauthenticated, and if recoverable_context.found=true decide whether the old task matches the current user intent
--> read catalog-search doc and shelf when the service catalog is unclear
--> search catalog with structured query/category/facets
--> explain/recommend a purchase option
--> collect required service input and buyer delivery email
--> create cart with selected UCP Variant.id
--> show the full cart contents and get human confirmation
--> create checkout from cart_id
--> if auth_qr is returned, show it for Alipay login/registration consent
--> poll/resume checkout until payment_intent_id appears
--> show returned payment QR exactly
--> wait for payment_intent.verified
--> check redacted delivery status
--> tell the human to check email / ItPay secure claim UI
--> if the human grants agent-readable access with Passkey, discover and read only the approved vault fields
-```
+3. Execute the first applicable command from `next_actions` unchanged. Typical
+commands are `services invoke`, `services action`, or `services checkout`.
+Do not infer a capability ID or hardcode one service's sequence.
 
-The high-level command can wrap this flow:
+4. For a paid result, collect only contact fields requested by the CLI. Create
+the checkout with the exact server-selected capability:
 
 ```bash
-itp buy <variant_id> --email <buyer_email> --phone <buyer_phone> --display agent --no-wait-payment --host <client> --json
+itpay --agent-type <agent_type> services checkout <service_execution_id> \
+  --capability <capability_id> --email <human_email> --host <host> --json
 ```
 
-For step-by-step testing:
+5. Show both handoff forms to the human:
 
-```bash
-itp buyer catalog search --query "<user request>" --host <client> --json
-itp buyer catalog search --query "企业工商信息 查询" --category business_data_api --provider itpay_enterprise_data --service-type ai_api --host <client> --json
-itp buyer catalog get --variant <variant_id> --host <client> --json
-itp buyer cart create --variant <variant_id> --host <client> --json
-itp buyer cart create --variants <variant_id_1>,<variant_id_2> --quantities 1,1 --host <client> --json
-itp buyer cart show <cart_id> --host <client> --json
-itp buyer cart add <cart_id> --variant <variant_id> --input key=value --quantity 1 --host <client> --json
-itp buyer cart remove <cart_id> --line <cart_line_item_id> --host <client> --json
-itp buyer checkout create --cart <cart_id> --email <buyer_email> --phone <buyer_phone> --host <client> --json
-itp buyer checkout resume <checkout_id> --host <client> --json
-itp buyer payment wait <payment_intent_id> --timeout 1 --host <client> --json
-itp buyer checkout status <checkout_id> --host <client> --json
-itp buyer refund create --order <order_id> --amount-minor <minor_units> --currency CNY --reason buyer_requested --host <client> --json
-itp buyer refund list --order <order_id> --host <client> --json
-itp buyer refund show <refund_id> --host <client> --json
-itp buyer refund cancel <refund_id> --reason buyer_changed_mind --host <client> --json
-itp buyer vault grants list --checkout <checkout_id> --host <client> --json
-itp buyer vault read --order <order_id> --artifact <vault_artifact_id> --host <client> --json
-```
+- Attach `brand_qr_local_path` when `brand_qr_status` is `downloaded`.
+- Print `checkout_url` as a clickable link.
+- Keep `checkout_id`, `display_token`, and `service_execution_id` for recovery.
+- Do not substitute a provider QR or call `itpay pay` in the normal buyer flow.
 
-For API products, read the product metadata input schema before cart creation.
-Enterprise data products require query input at cart time:
+6. After the human pays, claims, or grants access, re-read server state:
 
 ```bash
-itp buyer cart create --variant var_itpay_enterprise_fuzzy_search_cny01 --input company_name=京东 --host <client> --json
-itp buyer cart show <cart_id> --host <client> --json
-itp buyer cart add <cart_id> --variant var_itpay_enterprise_fuzzy_search_cny01 --input company_name=美团 --host <client> --json
-itp buyer cart create --variant var_itpay_enterprise_precise_lookup_cny05 --input company_name_or_credit_no=北京京东世纪贸易有限公司 --host <client> --json
-itp buy var_itpay_enterprise_fuzzy_search_cny01 --email <buyer_email> --input company_name=京东 --display agent --no-wait-payment --host <client> --json
+itpay --agent-type <agent_type> services next <service_execution_id> --json
+itpay --agent-type <agent_type> services get <service_execution_id> --json
 ```
 
-For cart edits, always read the server cart first with `buyer cart show`.
-Cart line identity includes the variant, offer, price, provider product, and
-normalized input. A fully identical line increments quantity; a different
-company name, exact name, page number, setting, or other input must stay as a
-separate line.
-
-Use fuzzy search when the user gives a short name, brand, keyword, or uncertain
-entity. Use precise lookup only after you have the exact China mainland
-registered company name or unified social credit code. If the user says
-"京东" or "那个京东商城", do not buy precise lookup until you resolve the exact
-registered name or run fuzzy search first.
-
-Refund commands use ItPay shared order state. If `itp buyer refund create`
-returns `policy_risk_confirmation_required`, explain the returned
-`refund_eligibility.policy` and `agent_guidance` to the human first. Only retry
-with `--confirm-policy-risk true` after explicit human confirmation.
-Do not guess `order_id`; if missing, run `buyer checkout status <checkout_id> --host <client> --json`.
-Refund amounts use minor units: CNY 1000 means CNY 10.00.
-Refund commands require a server-verified buyer session, not a vault grant. If
-the CLI says the buyer session is required or expired, run
-`itp status --refresh --host <client> --json` and follow the returned `next.command`.
-Current buyer refunds are whole-order only; do not use line-item refund scope.
-If the human cancels a refund before provider or money movement starts, use
-`buyer refund cancel <refund_id> --host <client> --json`; after cancel, the delivery claim can
-be unlocked again by the ItPay backend.
-
-## Non-Negotiable Rules
-
-1. Use `--json` and current client context for every non-doc ItPay command. Use `--host codex`, `--host claude-code`, `--host terminal`, `--host plain-chat`, or for OpenClaw Telegram use `--host telegram --target <inbound_meta.chat_id>`. `--host` is the human-visible client, not the shell execution environment.
-2. Do not invent service IDs, variant IDs, checkout IDs, payment URLs, QR URLs,
-   payment intent IDs, delivery IDs, or claim links.
-3. When the user asks for several compatible services, use one cart and one
-   checkout. Prefer `buyer cart create` for the first line, then `buyer cart
-   show` and `buyer cart add` for each additional query line so each service
-   input is locked to the correct cart line. Split only when ItPay rejects the
-   cart or explicitly says split checkout is required.
-4. Before checkout, make sure a buyer delivery email is available. If the CLI
-   has no known buyer email, ask the human for the email; do not invent one,
-   do not use placeholders, and do not proceed to checkout without it. The
-   email is used for human-first secure delivery and account/order access.
-5. Do not rewrite, shorten, re-encode, translate, or replace QR URLs. For
-   payment QR display, you must show `local_qr_path` when the CLI provides it;
-   remote QR images may not render in every agent client. If no local file is
-   present, use `qr_png_url` / `preferred_qr_url`, and use `qr_image_url` only
-   as fallback. These are ItPay-hosted human QR images; they may render a
-   native provider payment code for scanner reliability, but you must not
-   request, decode, or expose the raw provider payload.
-6. If `human_action.kind=auth_qr`, it is account login/registration consent,
-   not payment. Show the ItPay auth entry (`url`, `web_url`, or local/PNG QR)
-   as the primary human action, then poll/resume checkout until payment QR
-   appears. `oauth_start_url` is provider fallback/debug, not the primary agent
-   handoff.
-7. Do not treat QR display, page open, or user text like "I paid" as payment
-   proof. Payment proof for the agent is `payment_intent.verified`.
-8. Do not ask the human to paste raw keys, redeem codes, claim links, claim
-   tokens, session tokens, provider payloads, or secrets into chat.
-9. Do not call ops commands, worker routes, provider query recovery, or fixture
-   evidence routes from the buyer flow.
-10. Secure delivery is human-first. The agent may report
-   `delivery_claimable`, `check_email`, and `claim_link_sent`, but must not
-   fetch or reveal protected content.
-11. If the human uses Passkey to authorize agent-readable vault access, do not
-    ask them to paste content, portal text, claim links, session tokens, auth
-    session IDs, display tokens, or grant IDs. Run
-    `itp buyer vault grants list ...` and then `itp buyer vault read ...`.
-    The CLI automatically restores the buyer agent session from the checkout
-    auth handoff when possible. If the JSON includes
-    `buyer_session.status=buyer_session_saved`, continue with the returned
-    grants; the session token is intentionally stored locally and not printed.
-    Use only the fields returned by that command.
-12. If the user asks you to analyze, compare, summarize, install, or otherwise
-    use a delivered result, you may ask them to open the ItPay claim/account
-    page, click "Give to Agent / 一键给 Agent", choose fields, and confirm with
-    Passkey. After they approve, probe with `itp buyer vault grants list ...`;
-    do not ask them to copy a grant id.
-13. Prefer resume/wait over creating duplicate checkouts.
-14. Do not create a cart for an API service until all required service input
-    fields are known. For enterprise fuzzy search, `company_name` can be a
-    broad keyword. For enterprise precise lookup, `company_name_or_credit_no`
-    must be exact; otherwise warn the user that the query may waste the paid
-    lookup.
-15. Do not operate ItPay by opening the human web UI yourself. Use the CLI for
-    catalog, cart, checkout, payment wait, delivery status, grant discovery,
-    and vault reads. Browser/UI pages are for the human to scan, pay, claim,
-    reveal, and approve.
-
-## Docs Directory
-
-Use these docs pages as needed:
+7. Read protected output only when `next_actions` says the human grant is
+active:
 
 ```bash
-itp docs show catalog-search --role buyer --json
-itp docs show product-recommendation --role buyer --json
-itp docs show cart-checkout --role buyer --json
-itp docs show payment-qr --role buyer --json
-itp docs show payment-wait --role buyer --json
-itp docs show qr-refresh --role buyer --json
-itp docs show secure-delivery --role buyer --json
-itp docs show human-claim-ui --role buyer --json
-itp docs show account-portal --role buyer --json
-itp docs show vault-agent-read --role buyer --json
-itp docs show recovery --role buyer --json
-itp docs show safety-policy --role buyer --json
+itpay --agent-type <agent_type> services read-result <service_execution_id>
 ```
 
-Each docs page includes `next_docs`. Follow those links as the state changes.
+The grant is scoped to one Service Execution and expires after 15 minutes. It
+does not expose the buyer's other Vault artifacts, orders, or executions.
+
+## Recovery
 
-For payment creation in an agent/chat client, prefer:
+Use server-backed recovery before creating anything again:
 
 ```bash
-itp buy <variant_id> --email <buyer_email> --phone <buyer_phone> --display agent --no-wait-payment --host <client> --json
+itpay --agent-type <agent_type> next --json
+itpay --agent-type <agent_type> services list --json
+itpay --agent-type <agent_type> services next <service_execution_id> --json
+itpay --agent-type <agent_type> services checkout <service_execution_id> --resume --json
+itpay checkout --id <checkout_id> --token <display_token>
 ```
 
-This keeps JSON output machine-readable while allowing the CLI to prepare a
-local QR image path for clients that cannot render remote SVG reliably. In
-agent/chat clients, prefer `--no-wait-payment`. If `agent_action` is present,
-execute it exactly before normal prose. In OpenClaw Telegram it contains
-`openclaw message send`, the chat target, QR media, exact human text, and
-`presentation.blocks[].type="buttons"` for Telegram native inline buttons. In
-Codex or Claude Code app clients, send `agent_action.markdown` exactly to the
-current chat. In terminal, run `agent_action.command` only when the human is
-directly watching that terminal.
-
-If a response has `status=payment_handoff_required`, follow `next.type`.
-For Codex/Claude Code app clients, send `agent_action.markdown` first; once it
-is visible in the current chat, run `after_visible_action.command` once by
-default. Do not run payment wait before the human-visible QR/link is sent. If
-visibility is uncertain, stop and wait for the human.
-
-For first-purchase auth, treat the returned ItPay authorization entry as a
-single human orchestration entry. It may open Alipay login/registration first
-and then payment after ItPay receives the OAuth callback. Do not call
-`oauth_start_url` directly unless the ItPay auth page asks for fallback.
-If the payment page says provider entry is stabilizing/preparing,
-or if the payment provider says "order not found", tell the human to wait 30-60
-seconds and use the same page/QR again. Do not ask them to refresh repeatedly,
-and do not create another checkout or payment intent. Use
-`itp buyer payment refresh-qr ... --reason order-not-found` only after the
-same QR/page has been retried and still fails; ItPay may safely return the same
-valid QR rather than creating a new provider order.
-
-## Safe User Message Pattern
-
-When reporting progress, keep it short:
-
-```text
-I found the service and selected the matching variant.
-I created the cart and checkout.
-Please open the returned ItPay authorization link and approve Alipay login.
-I am waiting for ItPay account authorization.
-Please scan the returned ItPay-hosted QR image with the payment provider.
-I am waiting for ItPay payment verification.
-Payment is verified.
-Delivery is claimable by the human buyer. Please check your email.
-```
+`--resume` reissues the handoff for the existing unpaid checkout. It must not
+create a second order. Local files cache recovery handles; canonical cart,
+quota, execution, checkout, delivery, and grant state comes from the backend.
+
+## Host Selection
 
-Do not include raw protected content in the message.
+`--agent-type` identifies the agent runtime. `--host` identifies where the
+human sees the output. They are separate.
+
+| Human surface | CLI options |
+| --- | --- |
+| Codex | `--host codex` |
+| Claude Code | `--host claude-code` |
+| Terminal | `--host terminal` |
+| Telegram | `--host telegram --target <chat_id>` |
+| Feishu/Lark | `--host feishu --target <id>` or `--host lark --target <id>` |
+
+Run `itpay install <host>` for host-specific setup.
+
+## Progressive Disclosure
+
+- Run one state-changing command at a time.
+- Return the useful result, a short explanation, and the next executable step.
+- Ask the human only for a missing required field such as delivery email.
+- When checkout is ready, visibly attach the QR and print the payment link.
+- Prefer CLI `next_actions`; do not dump internal timelines unless diagnosing.
+- Use `--json` for agent parsing and normal rendering for the human handoff.
+
+## Safety Rules
+
+1. Never invent catalog, service, capability, result-item, checkout, or order IDs.
+2. Never expose provider credentials, raw provider metadata, bearer tokens, or device private keys.
+3. Do not treat QR rendering or a human statement as payment confirmation.
+4. Do not call `itpay pay` or use `buy --pay` for a normal checkout; those are operator escape hatches.
+5. Do not create a new execution or checkout until recovery confirms the prior one is unusable.
+6. Do not claim protected access before `services read-result` succeeds.
+7. Do not invent admin, account, grant-creation, or provider-specific CLI commands.
+
+## Built-in Docs
+
+```bash
+itpay docs list
+itpay docs search <term>
+itpay docs show catalog-list
+itpay docs show cart-checkout
+itpay docs show payment-flow
+itpay docs show orders-refunds
+itpay docs show render-hosts
+itpay docs show install-and-setup
+```

package/docs/agent/buyer/account-portal.json

@@ -1,81 +0,0 @@
-{
-  "schema_version": "itp.agent_doc.v1",
-  "role": "buyer",
-  "topic": "account-portal",
-  "title": "Human Account Portal",
-  "purpose": "Teach the agent how to help a human open the ItPay account/order portal without reading protected content.",
-  "when_to_use": [
-    "The human asks to see their ItPay account or previous orders.",
-    "The original claim email link expired or was already used.",
-    "The agent needs to explain that human UI and agent status share the same redacted order state."
-  ],
-  "required_state": {
-    "needs": [
-      "authenticated buyer account session"
-    ],
-    "must_not_need": [
-      "claim token",
-      "raw content",
-      "portal page contents"
-    ]
-  },
-  "commands": [
-    {
-      "intent": "create a one-time human account portal link",
-      "command": "itp account login-link --host <client> --json",
-      "success_signal": "response.status == account_portal_login_link_created and response.portal_login_link.one_time == true"
-    },
-    {
-      "intent": "same command under buyer namespace",
-      "command": "itp buyer account login-link --host <client> --json",
-      "success_signal": "response.login_url is present"
-    },
-    {
-      "intent": "agent-side state check without opening the human portal",
-      "command": "itp buyer checkout status <checkout_id> --host <client> --json",
-      "success_signal": "response contains redacted order/delivery state only"
-    }
-  ],
-  "agent_rules": [
-    "Give the one-time account portal link to the human buyer.",
-    "Do not open the account portal link yourself.",
-    "The human portal and agent APIs read the same redacted order/vault state.",
-    "If the human chooses one-key agent authorization after Passkey reveal, use `itp buyer vault grants list ...` to discover the active grant; do not ask the human to copy the grant id.",
-    "If the human reports an order status, verify it through buyer status/order commands instead of scraping the portal.",
-    "Protected artifact reveal still requires a later Passkey/WebAuthn human reveal flow."
-  ],
-  "forbidden": [
-    "Do not fetch, screenshot, scrape, cache, or summarize the account portal page.",
-    "Do not ask the human to paste portal contents, claim links, keys, or raw results into chat.",
-    "Do not claim the portal link is a raw content reveal link.",
-    "Do not reuse a portal link after it has been opened."
-  ],
-  "next_docs": [
-    {
-      "condition": "The user asks where a delivered item is",
-      "topic": "secure-delivery",
-      "command": "itp docs show secure-delivery --role buyer --json"
-    },
-    {
-      "condition": "The human approved agent access to selected fields",
-      "topic": "vault-agent-read",
-      "command": "itp docs show vault-agent-read --role buyer --json"
-    },
-    {
-      "condition": "The user asks why the agent cannot open the portal",
-      "topic": "safety-policy",
-      "command": "itp docs show safety-policy --role buyer --json"
-    }
-  ],
-  "search_terms": [
-    "account portal",
-    "orders",
-    "login link",
-    "one time link",
-    "portal",
-    "账号",
-    "订单",
-    "登录链接",
-    "一次性链接"
-  ]
-}

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

@@ -1,106 +0,0 @@
-{
-  "schema_version": "itp.agent_doc.v1",
-  "role": "buyer",
-  "topic": "catalog-search",
-  "title": "Catalog Search For Buyer Agents",
-  "purpose": "Help the agent read the service shelf, search the public ItPay service catalog, and choose a purchase option without guessing.",
-  "when_to_use": [
-    "The user describes a need but has not chosen a service.",
-    "The agent needs service and purchase option details before recommendation.",
-    "The agent needs to search standardized API products such as ItPay enterprise data APIs."
-  ],
-  "required_state": {
-    "needs": [
-      "search query or service intent"
-    ],
-    "must_not_need": [
-      "buyer login",
-      "payment intent",
-      "ops token"
-    ]
-  },
-  "commands": [
-    {
-      "intent": "inspect the service shelf before guessing keywords or facets",
-      "command": "itp buyer shelf manifest --host <client> --json",
-      "success_signal": "response.snapshot_version and response.snapshot_url are present; use snapshot/delta when the agent needs a shopping-list view of available services"
-    },
-    {
-      "intent": "search public catalog by natural language query",
-      "command": "itp buyer catalog search --query \"企业工商信息 查询\" --host <client> --json",
-      "success_signal": "response.products contains services with purchase options, id, title, price, metadata, and response.catalog_guidance explains how to choose safely"
-    },
-    {
-      "intent": "search API services by stable category and safe facets",
-      "command": "itp buyer catalog search --query \"企业工商信息 查询\" --category business_data_api --provider itpay_enterprise_data --service-type ai_api --delivery-mode managed_capability --use-case company_lookup --input-facet company_name --host <client> --json",
-      "success_signal": "response.products only contains products matching the requested category/facets"
-    },
-    {
-      "intent": "search fuzzy company lookup when the user only provides a partial company name",
-      "command": "itp buyer catalog search --query \"企业 模糊 查询 公司简称\" --category business_data_api --provider itpay_enterprise_data --service-type ai_api --use-case company_disambiguation --input-facet company_name --host <client> --json",
-      "success_signal": "response.products includes the fuzzy enterprise search product before precise lookup"
-    },
-    {
-      "intent": "get exact service details for a selected purchase option",
-      "command": "itp buyer catalog get --variant <variant_id> --host <client> --json",
-      "success_signal": "response.selection.catalog_variant_id matches the selected purchase option and response.catalog_guidance says to explain before cart creation"
-    }
-  ],
-  "agent_rules": [
-    "Terminology: product means 服务, variant means 购买选项, variant_id means 购买选项 ID, catalog means 服务目录, shelf means 目录清单.",
-    "Before searching, remember the local agent does not know the current service catalog. Use this doc and the shelf manifest/snapshot as the shopping-list view when keywords or facets are unclear.",
-    "Catalog search is structured ItPay catalog search, not general web search. Convert the user's request into query plus category/provider/use-case/input-facet filters.",
-    "Full search is allowed for explicit user search, not as a polling loop.",
-    "For repeated discovery, prefer shelf manifest/snapshot/delta.",
-    "For API services, map user intent to category/facet filters before relying on keyword ranking.",
-    "Use stable categories: business_data_api, business_verification_api, identity_verification_api, phone_verification_api, risk_compliance_api, location_weather_api, finance_data_api.",
-    "Use safe facets such as --use-case, --input-facet, --output-facet, --sensitivity-level, --delivery-mode, and --provider.",
-    "Use service and purchase option metadata to explain options in user language.",
-    "If search returns zero products, do not invent a service or conclude too early. Loosen filters, change query terms, or go back to the shelf.",
-    "If search returns many products, narrow with category/provider/use-case/input-facet before recommending.",
-    "If search returns a small set, compare service description, price, required input, sensitivity level, and delivery mode.",
-    "Money values from catalog JSON use minor units. For CNY, amount=10 means CNY 0.10, not CNY 10. Prefer display_amount when present, or divide amount/amount_minor by 100 before telling the user.",
-    "For products with requires_human_input=true, do not ask for identity numbers or phone numbers in chat; rely on ItPay human authorization/input.",
-    "Selecting a service is not buying. Explain the selected service and purchase option to the human, then ask for confirmation before cart creation.",
-    "Do not create checkout until the user intent maps to one selected purchase option and the user confirms the purchase."
-  ],
-  "forbidden": [
-    "Do not require login for discovery.",
-    "Do not invent catalog items, services, purchase options, or variant IDs.",
-    "Do not assume search result order means the user has approved purchase."
-  ],
-  "next_docs": [
-    {
-      "condition": "Need to recommend among services or purchase options",
-      "topic": "product-recommendation",
-      "command": "itp docs show product-recommendation --role buyer --json"
-    },
-    {
-      "condition": "The user has chosen and confirmed a purchase option",
-      "topic": "cart-checkout",
-      "command": "itp docs show cart-checkout --role buyer --json"
-    }
-  ],
-  "search_terms": [
-    "catalog",
-    "search",
-    "shelf",
-    "product",
-    "variant",
-    "purchase option",
-    "api",
-    "enterprise_data",
-    "category",
-    "facet",
-    "business_data_api",
-    "企业查询",
-    "工商信息",
-    "企业工商数据精准查询",
-    "企业工商数据模糊查询",
-    "搜索",
-    "商品",
-    "服务目录",
-    "目录清单",
-    "购买选项"
-  ]
-}