@seasonkoh/webaz 0.1.12 → 0.1.14

package/dist/layer0-foundation/L0-2-state-machine/engine.js

@@ -49,7 +49,10 @@ export function transition(db, orderId, toStatus, actorId, evidenceIds = [], not
     if (rule.requiresEvidence && evidenceIds.length === 0) {
         return {
             success: false,
-            error: `此操作需要上传证据。提示：${rule.evidenceHint ?? '请上传相关证明文件'}`
+            error: `此操作需要证据。可任选一种方式提供:\n` +
+                `(A) 传 evidence_description(文字描述,如 "物流单号: SF1234567 / 顺丰" / "已揽收 GPS:31.2,121.5") — agent 最方便\n` +
+                `(B) 上传文件作为证据 — 提示:${rule.evidenceHint ?? '相关证明文件'}\n` +
+                `两种都会写入 evidence 表,效力等同。`
         };
     }
     // 5. 执行转移（数据库事务，保证原子性）
@@ -351,7 +354,7 @@ function getActiveDeadline(order, db) {
     // QA 轮 7 P1：旧表 picked_up 状态没 deadline → agent 不知道下一步多久前要做完
     // 修：picked_up 状态视为"已揽收，等运输/投递"，下一个 deadline 是 delivery_deadline
     // QA 轮 7 P1（另一条）：disputed 状态下没读 dispute_cases 的 arbitrate_deadline → agent 不知道仲裁还有多久
-    const deadlineMap = {
+    const deadlineMapMarket = {
         created: 'pay_deadline',
         paid: 'accept_deadline',
         accepted: 'ship_deadline',
@@ -360,6 +363,18 @@ function getActiveDeadline(order, db) {
         in_transit: 'delivery_deadline',
         delivered: 'confirm_deadline',
     };
+    // 2026-05-31 修：self-fulfill(logistics_id 空)无三方揽收环节,shipped/picked_up/in_transit
+    // 全部直接走 delivery_deadline,跟 CURRENT_RESPONSIBLE_SELF_FULFILL 对齐(都归 seller)。
+    // 之前 deadlineMap 单表导致 self-fulfill shipped 显示 pickup_deadline + responsible=seller,
+    // agent 看到矛盾不知道下一步(pickup 是物流的事,seller 又没物流可揽收)。
+    const deadlineMapSelfFulfill = {
+        ...deadlineMapMarket,
+        shipped: 'delivery_deadline',
+        picked_up: 'delivery_deadline',
+        in_transit: 'delivery_deadline',
+    };
+    const isSelfFulfill = !order.logistics_id;
+    const deadlineMap = isSelfFulfill ? deadlineMapSelfFulfill : deadlineMapMarket;
     // disputed 状态：从 `disputes` 表（active dispute, not the `dispute_cases` archive）查 deadline
     // 优先返 arbitrate_deadline（仲裁总截止）；如果还在 respond 窗口（被诉方未回应）返 respond_deadline
     if (order.status === 'disputed' && db) {

package/dist/layer1-agent/L1-1-mcp-server/server.js

@@ -214,9 +214,15 @@ Roles:
         name: 'webaz_search',
         description: `Search WebAZ marketplace + cross-platform anchor lookup. No auth required.
 
-USE THIS when the user:
-- gives KEYWORDS / filters (typical product discovery), OR
-- pastes ANY external product URL/share-text from Taobao / Tmall / JD / PDD / 1688 / Douyin / Xiaohongshu
+⚠️ **STRICT MATCH ONLY** — query 永远是精准匹配(等于 title / 等于 external_title / 包含 ≥6 字符 alias)。
+不做 fuzzy LIKE 模糊降级。短查询(如 "钱包" "iphone")很大概率 0 命中,这是设计如此,不是 bug。
+0 命中时,**不要**自己拼短词 retry,也**不要**调别的工具假装搜索;应**引导用户访问 https://webaz.xyz/#discover**
+在搜索框输入关键词浏览(那里有 fuzzy LIKE)。模糊搜索是用户主动行为,不是 agent 代办。
+
+USE THIS when:
+- 用户给出 **完整商品标题 / SKU / 精准描述**(典型 strict match,如 "AirPods Pro 2 USB-C 港行"), OR
+- 用户给出 **筛选条件**(category / max_price / min_return_days / max_handling_hours / sort), OR
+- 用户粘贴 ANY external product URL/share-text from Taobao / Tmall / JD / PDD / 1688 / Douyin / Xiaohongshu
   → WebAZ exact-matches against its anchor registry (canonical product fingerprints across
     platforms). matched_by='none' means truly not indexed — do NOT silently fall back to keyword,
     and do NOT guess similar products.
@@ -225,7 +231,8 @@ USE THIS when the user:
 NOT a separate browser-fetch capability. Returns structured specs + logistics + after-sales +
 agent_summary (one-line decision hint).
 
-【Keyword search】Pass query / category / max_price / min_return_days / max_handling_hours.
+【Keyword search — STRICT】Pass query / category / max_price / min_return_days / max_handling_hours.
+query 命中 = (1) 完全等于 product.title OR (2) 完全等于任一 external_title OR (3) 用户文本包含任一卖家声明 alias_value (≥6 字符)。模糊关键词请引导用户去 PWA #discover。
 
 【External-link paste search】When user pastes share text from Taobao/Tmall/JD/Pinduoduo/1688/Douyin/Xiaohongshu
 (e.g. '【淘宝】「Product Name」 https://e.tb.cn/xxx ...'), do:
@@ -279,10 +286,15 @@ Note: paste-link matching hits webaz.xyz production data, not your local webaz.d
     },
     {
         name: 'webaz_verify_price',
-        description: `Lock product price before placing order — returns session_token.
-Recommended flow for agents: call this first to verify & lock price, then call webaz_place_order with session_token.
-Benefits: (1) order price matches displayed; (2) caller is alerted if price changed; (3) platform only liable for T0 price.
-session_token: 10-minute TTL, single-use.
+        description: `Lock product price + reserve stock window BEFORE webaz_place_order — returns session_token.
+
+USE THIS for EVERY purchase, not just price-sensitive ones. Reasons:
+(1) order price matches displayed (defeats flash-sale / hidden-fee races)
+(2) caller is alerted if price changed between view and order
+(3) protocol only liable for T0 price
+(4) reduces stock-depletion race on hot items (session_token is single-use within 10min)
+
+Skipping this is allowed but the agent then carries the price/stock-race risk itself. session_token: 10-minute TTL, single-use, pass it to webaz_place_order.
 
 ──
 中文：下单前锁价 — 10 分钟一次性 session_token；agent 应先调此再调 place_order。`,
@@ -298,8 +310,14 @@ session_token: 10-minute TTL, single-use.
     },
     {
         name: 'webaz_list_product',
-        description: `Seller product catalog management (create / update / shelf / archive / query own listings).
-Requires seller-role api_key. On create, system auto-suggests stake (~15% of price) to secure buyer protection.
+        description: `⚠️ "list" = PUBLISH (verb), NOT "list out" (noun). Seller-only product catalog publishing & management.
+
+USE THIS when SELLER wants to:
+- publish a NEW product to their catalog, OR
+- update / delist / relist / trash / delete an existing product they own, OR
+- view their OWN listings (action=mine)
+
+NOT for browsing the marketplace — for that use webaz_search (anyone, no auth). Requires seller-role api_key. On create, system auto-suggests stake (~15% of price) to secure buyer protection.
 
 Fill fields completely — better agent_summary helps buyer agents make comparison decisions (brand / return / handling / warranty).
 Note: for "exclusive price vs external link" listing, use PWA Web only — link claim needs crowd-verification.
@@ -429,7 +447,9 @@ Missing any deadline auto-judges fault against the responsible party and trigger
     },
     {
         name: 'webaz_update_order',
-        description: `Update order status (each role can only perform their own actions).
+        description: `STATUS TRANSITIONS on an order (accept / ship / pickup / deliver / confirm / dispute) — NOT for editing order content (price/quantity/address are immutable after creation).
+
+USE THIS to advance an order through its lifecycle. Each role can only perform their own actions (see action list).
 
 Seller actions:
 - accept:  accept order (within 24h of payment)
@@ -486,7 +506,9 @@ Returns: current status, status history (who did what when), next responsible ac
     },
     {
         name: 'webaz_wallet',
-        description: `Wallet query (balance + earnings stats + deposit/withdrawal/income history).
+        description: `Wallet READ-ONLY query (balance + earnings stats + deposit/withdrawal/income history).
+
+⚠️ Iron-Rule (must read before use): actual withdrawals / deposits / whitelist management require Passkey + email OTP via PWA Web only. This tool CANNOT move money — only query state. If user asks "send/withdraw/deposit WAZ", do NOT promise it via MCP; instead direct them to PWA Web.
 
 Actions:
 - view         available balance + staked + in-escrow + total earnings + reputation tier (default)
@@ -494,9 +516,6 @@ Actions:
 - withdrawals  last 10 withdrawal requests (with status / tx_hash)
 - income       income breakdown: referral L1/L2/L3 + binary PV matching + sales net
 
-NOTE: actual withdrawals / deposits / whitelist management require Passkey + email OTP via PWA Web only.
-This is a security boundary — agents CANNOT bypass it. Use this tool for read-only queries only.
-
 ──
 中文：钱包查询（余额/收益/充提历史）。仅查询用，实际充提需 PWA Web + Passkey + 邮件 OTP，agent 不可绕过。`,
         inputSchema: {
@@ -532,7 +551,12 @@ Every status change (new order / ship / dispute / etc.) notifies relevant partic
     },
     {
         name: 'webaz_dispute',
-        description: `Manage dispute lifecycle (L3 dispute system).
+        description: `Manage ORDER-DELIVERY dispute lifecycle (L3 dispute system, central arbitrator).
+
+⚠️ Different from webaz_claim_verify:
+- webaz_dispute = order delivery problem (didn't arrive / wrong / damaged in transit / seller fraud) → central arbitrator + 120h ruling
+- webaz_claim_verify = challenge a product CLAIM (brand / spec / ship time) → 3 crowd verifiers vote
+Pick based on the actual problem: delivery/receiving = dispute; marketing-claim accuracy = claim_verify.
 
 When buyer claims item-not-as-described / damaged / seller fraud, first raise dispute via webaz_update_order action=dispute,
 then use this tool for follow-ups.
@@ -601,7 +625,12 @@ view / list_open / respond / add_evidence can be agent-proxied; only arbitrate n
     },
     {
         name: 'webaz_claim_verify',
-        description: `Crowd-sourced claim verification — no central arbitrator, 3 eligible verifiers reach consensus by vote.
+        description: `Crowd-sourced PRODUCT-CLAIM verification — challenge seller's marketing claims (brand / spec / ship time / authenticity); 3 eligible verifiers reach consensus by vote.
+
+⚠️ Different from webaz_dispute:
+- webaz_claim_verify = challenge a CLAIM about the product itself ("seller said 24h ship but didn't" / "said brand new but used")
+- webaz_dispute = order-delivery problem (didn't arrive / arrived broken / wrong item) → central arbitrator
+If unsure: did the buyer GET the item? If yes + problem with item itself → claim_verify. If no/damaged in transit → dispute.
 
 When to use:
 - Buyer:   suspects a seller's product claim (e.g. "brand new sealed", "ships within 24h") → wants decentralized verification
@@ -670,12 +699,14 @@ Other actions (create / view / mine / available / eligibility / apply / appeal e
     },
     {
         name: 'webaz_skill',
-        description: `L4-4 Skill marketplace — sellers publish reusable seller-side behaviour configs; buyer Agents subscribe with one click.
+        description: `L4-4 Skill marketplace — sellers publish reusable seller-side BEHAVIOUR configs; buyer Agents subscribe with one click.
 
 USE THIS when:
 - seller wants to install reusable selling behavior (auto-accept / catalog-sync / price-haggling / etc.), OR
 - buyer agent wants to subscribe to seller's behaviour to enable priority discovery / auto-deal flows.
-This is NOT a product search — for "find me X" use webaz_search.
+
+NOT a product search — for "find me X" use webaz_search.
+NOT a KNOWLEDGE-content marketplace — for buying/selling templates / prompts / guides / checklists use webaz_skill_market (totally separate system, independent revenue flow).
 
 ⚠️ Important — Skill is NOT executable code distribution. There are exactly 5 typed Skill kinds (below), each accepts only **structured config parameters** (numbers / enums / amounts). There is NO path for an Agent to download and run arbitrary third-party code via this marketplace. Subscribing = setting a flag + data binding, not installing a plugin. (Common Web2 "plugin marketplace" risk model does NOT apply here.)
 
@@ -731,7 +762,9 @@ Actions:
     },
     {
         name: 'webaz_mykey',
-        description: `Confirm account existence by handle + permanent_code. Returns redacted api_key hint only — full api_key disclosure requires PWA + Passkey verification (Iron-Rule).
+        description: `Account RECOVERY check — confirm account existence by handle + permanent_code when user has lost their api_key but still remembers handle + 6-char recovery code from registration. Returns redacted api_key hint only — full api_key disclosure requires PWA + Passkey verification (Iron-Rule).
+
+USE THIS ONLY when user has lost api_key and provides handle + permanent_code. NOT for "show me my api_key" (you already have it if you're authenticated). NOT for looking up other users (use webaz_profile).
 
 Rate-limited: 5 attempts per handle per hour. Excessive failures lock the handle for 1 hour.
 
@@ -798,13 +831,15 @@ Public-profile actions:
     },
     {
         name: 'webaz_revoke_key',
-        description: `Initiate api_key revocation. Iron-Rule: actual revocation requires PWA + Passkey confirmation — MCP only registers the intent and returns the PWA URL where you finish the action.
+        description: `Initiate api_key revocation (NO REPLACEMENT — old key dies, no new one issued). Iron-Rule: actual revocation requires PWA + Passkey confirmation — MCP only registers the intent and returns the PWA URL where you finish the action.
 
-Use when:
-- Your api_key was leaked or you suspect unauthorized access
-- You are decommissioning an agent / device
+⚠️ STRONG RECOMMENDATION: use webaz_rotate_key instead unless you intentionally want zero replacement (e.g. fully decommissioning the agent / device). Rotate = atomic swap (no access gap). Revoke = death + you re-register from scratch.
 
-After PWA confirmation, the old api_key returns 401 on all tools. Plan ahead: have a new key (via webaz_rotate_key) before revoking, or you lose access.
+Use revoke (not rotate) when:
+- You are PERMANENTLY decommissioning this agent / device, OR
+- You want all access to die NOW with no fallback
+
+After PWA confirmation, the old api_key returns 401 on all tools.
 
 ──
 中文：发起 api_key 吊销。Iron-Rule：真正吊销必须 PWA + Passkey 二次确认（agent 不能单方面执行不可逆操作）。MCP 仅登记意图，返回 PWA 确认 URL。`,
@@ -943,7 +978,16 @@ to my address" — use webaz_search ship_to filter.`,
     },
     {
         name: 'webaz_shareables',
-        description: 'Manage your external content "shareables" (YouTube / TikTok / 小红书 / B 站 / IG / Twitter links bound to a product or anchor). WebAZ indexes only the URL, never the content bytes. Or query by product_id / anchor.',
+        description: `Bind your EXTERNAL content (YouTube / TikTok / 小红书 / B站 / IG / Twitter posts) to a WebAZ product — turns your content into a referral-earning channel. WebAZ indexes only the URL, never the content bytes.
+
+USE THIS when:
+- creator/user wants to "anchor" their existing review/unboxing/recommendation video/post to a WebAZ product (or anchor) so future buyers clicking that content → registration / purchase counts toward THEIR referral commission, OR
+- agent wants to look up "what external content is associated with this product / this anchor"
+
+Differs from webaz_share_link (which generates a NEW short link for sharing) — shareables register your EXISTING content as the discovery surface.
+
+──
+中文：把你在 YouTube/TikTok/小红书/B站/IG/Twitter 已发的内容(测评/开箱/推荐)锚定到 WebAZ 商品 —— 让你的外部内容变成赚 referral 佣金的入口。WebAZ 只锚 URL,不取内容。区别于 webaz_share_link(那个是生成新短链)。`,
         inputSchema: {
             type: 'object',
             properties: {
@@ -1016,7 +1060,10 @@ Shipping address: if omitted, falls back to webaz_default_address (set via that
     },
     {
         name: 'webaz_bid',
-        description: `Bid on RFQs (seller-side).
+        description: `Bid on RFQs (seller-side, Request-for-Quotation).
+
+USE THIS ONLY for RFQ bidding (when a buyer posted demand via webaz_rfq and you want to quote). For AUCTION bidding (English forward auction on a listed item) use webaz_auction action=bid — they are separate systems with different economics (RFQ has bid stake; auction has min_increment + sniper extension).
+
 Actions:
 - submit:    new bid; needs rfq_id + price + qty_offered + fulfillment_type; optional eta_hours/note
 - patch:     edit price/ETA/fulfillment/note (only active; stake delta auto-settled)
@@ -1044,7 +1091,9 @@ Actions:
     },
     {
         name: 'webaz_chat',
-        description: `Context-bound DM (no open DM — only order / rfq / listing_qa contexts allowed).
+        description: `Relay buyer↔seller (or RFQ partner) MESSAGES — context-bound DM, no open DM. Only order / rfq / listing_qa contexts allowed.
+
+USE THIS when the user wants to communicate with the OTHER PARTY of a trade (e.g. "ask seller about return", "tell buyer about shipping delay", "answer Q&A on my listing"). NOT a general LLM chat — every message attaches to an order/rfq/listing_qa context. If the user just wants to chat with YOU (the agent), don't call this tool.
 Actions:
 - start:     open conversation — needs kind + context_id (for rfq, also recipient_id)
 - list:      my conversation list
@@ -1108,7 +1157,14 @@ Returns insufficient_data:true when data sparse.
     },
     {
         name: 'webaz_charity',
-        description: `Charity wish pool + repayment + community fund — double-anonymous + dual-signed anchoring + isolated prestige.
+        description: `Charity WISH POOL + repayment + community FUND — double-anonymous + dual-signed anchoring + isolated prestige.
+
+USE THIS when:
+- user wants to publish a "wish" (need help with money/service) for community fulfillment, OR
+- user wants to claim/fulfill someone else's wish, OR
+- user wants to donate to / browse the community charity fund (separate from per-order donation).
+
+NOT for per-order charity donation — that's handled by webaz_place_order's donation_pct param (0.5% / 1% / 2% / 5% sent to charity_fund at order time). This tool is for the standalone wish-fulfillment economy.
 Actions:
 - list:        browse public wishes (filter by category/target_kind; anonymous accessible)
 - detail:      single wish details (commit_hash + fulfillment + repayments)
@@ -1273,6 +1329,8 @@ Actions:
     {
         name: 'webaz_auto_bid',
         description: `Seller auto_bid Skill config — auto-quote on RFQ creation instantly.
+
+USE THIS as a shortcut equivalent to webaz_skill install kind=auto_bid + ongoing config edits. Dedicated tool because auto_bid is the most-used Skill and needs frequent param tuning (max_eta_h / undercut_pct / daily_cap). For other Skill kinds use webaz_skill directly.
 Actions:
 - get:     read current Skill config
 - set:     create/update Skill (needs categories[] / regions[] / max_eta_h / bid_strategy etc.)
@@ -1738,7 +1796,12 @@ async function handleSearch(args) {
     params.push(Math.min(limit * 3, 500)); // 取更多候选，便于 trending 排序
     const products = db.prepare(sql).all(...params);
     if (products.length === 0) {
-        return { found: 0, message: '没有找到匹配的商品', products: [] };
+        // query 模式 0 命中 = strict 精准匹配未命中。**不做 fuzzy fallback**(协议精准承诺)。
+        // 引导用户去 PWA 发现页做模糊搜索;agent 不应自己 LIKE 降级,那会污染精准 trust。
+        const hint = query
+            ? `精准匹配 0 命中(query='${String(query).slice(0, 40)}')。webaz_search 是协议精准接口,不做模糊降级。要做模糊搜索请引导用户访问 https://webaz.xyz/#discover ,在搜索框输入关键词浏览 — 这是用户主动操作,不是 agent 代办。`
+            : '没有找到匹配的商品';
+        return { found: 0, message: hint, products: [], matched_by: 'strict_no_match' };
     }
     const enriched = products.map((p) => {
         const boost = getSearchBoost(db, p.seller_id);

package/dist/pwa/public/app.js

@@ -420,6 +420,10 @@ async function apiWithStatus(method, path, body) {
   const opts = {
     method,
     headers: { 'Content-Type': 'application/json', ...(state.apiKey ? { Authorization: `Bearer ${state.apiKey}` } : {}) },
+    // 2026-05-31 修:boot 阶段 fetch 必须有 timeout,否则服务挂时 render 永远 await,
+    // skeleton "正在恢复登录..." 永不替换 = PWA 刷新卡死。10s 后强制 abort → catch → status=0 →
+    // 命中已有的"无法连接+重试"兜底 UI(render 530-548)。
+    signal: AbortSignal.timeout(10000),
   }
   if (body) opts.body = JSON.stringify(body)
   try {
@@ -427,7 +431,7 @@ async function apiWithStatus(method, path, body) {
     const json = await res.json().catch(() => ({}))
     return { status: res.status, body: json }
   } catch {
-    return { status: 0, body: { error: 'network' } }  // 0 = 网络不可达，保留 key 等下次
+    return { status: 0, body: { error: 'network' } }  // 0 = 网络不可达或超时,保留 key 等下次
   }
 }
 
@@ -10600,22 +10604,25 @@ async function initShareCtx() {
   }
 
   // Enrich：并发 fetch sponsor 公开卡 + target 预览（阻塞返回，确保 banner 渲染时数据齐）
+  // 2026-05-31 修:每个 fetch 加 AbortSignal.timeout(5000),防 boot 阶段任一 fetch hang
+  // 把 render 卡死在"正在恢复登录..."
+  const sig = () => ({ signal: AbortSignal.timeout(5000) })
   const fetches = []
   if (ctx.sponsor_id && !ctx.sponsor_name) {
-    fetches.push(fetch(`/api/users/${ctx.sponsor_id}/public-card`).then(r => r.json()).then(card => {
+    fetches.push(fetch(`/api/users/${ctx.sponsor_id}/public-card`, sig()).then(r => r.json()).then(card => {
       if (card?.name) writeShareCtx({ sponsor_name: card.name, sponsor_bio: card.bio, sponsor_joined_days_ago: card.joined_days_ago })
     }).catch(() => {}))
   }
   if (ctx.target_hash && !ctx.target_preview) {
     const m = ctx.target_hash.match(/^#order-product\/(.+)$/)
     if (m) {
-      fetches.push(fetch(`/api/products/${m[1]}/preview`).then(r => r.json()).then(p => {
+      fetches.push(fetch(`/api/products/${m[1]}/preview`, sig()).then(r => r.json()).then(p => {
         if (p?.id) writeShareCtx({ target_kind: 'product', target_preview: p })
       }).catch(() => {}))
     } else if (ctx.target_hash.startsWith('#u/')) {
       const uid = ctx.target_hash.slice(3)
       if (/^usr_[A-Za-z0-9_]+$/.test(uid)) {
-        fetches.push(fetch(`/api/users/${uid}/public-card`).then(r => r.json()).then(p => {
+        fetches.push(fetch(`/api/users/${uid}/public-card`, sig()).then(r => r.json()).then(p => {
           if (p?.id) writeShareCtx({ target_kind: 'user', target_preview: p })
         }).catch(() => {}))
       }

package/dist/pwa/public/sw.js

@@ -1,5 +1,5 @@
 // Service Worker — 网络优先，离线降级缓存；API 请求不缓存
-const CACHE = 'webaz-v480'
+const CACHE = 'webaz-v481'
 
 self.addEventListener('install', e => {
   self.skipWaiting()

package/dist/pwa/server.js

@@ -126,6 +126,8 @@ import { registerExternalAnchorsRoutes } from './routes/external-anchors.js';
 import { registerAnchorsRoutes } from './routes/anchors.js';
 // 仲裁员申请 (#1013 Phase 44) — 4 user + 3 admin endpoints
 import { registerArbitratorRoutes } from './routes/arbitrator.js';
+// 卖家配额 + 数据中心 (#1013 Phase 45) — 4 user + 3 admin
+import { registerSellerQuotaRoutes } from './routes/seller-quota.js';
 // 验证员用户侧 (#1013 Phase 46) — 5 endpoints
 import { registerVerifierUserRoutes } from './routes/verifier-user.js';
 // 公开用户主页 (#1013 Phase 47) — 6 endpoints
@@ -7257,6 +7259,13 @@ registerOrdersCreateRoutes(app, {
     signPassport: (message) => privateKeyToAccount(derivePrivKey('platform-hot-wallet')).signMessage({ message }),
     issuerAddress: () => privateKeyToAddress(derivePrivKey('platform-hot-wallet')),
 });
+// #1013 Phase 45: 卖家配额 + 数据中心 7 endpoints — 2026-05-31 修补:之前 import 了但忘了 register,
+// 导致 /api/seller/quota-status + /api/seller/insights 落入 SPA fallback 返回 HTML,前端 JSON.parse 死循环
+registerSellerQuotaRoutes(app, {
+    db, generateId, auth,
+    requireUsersAdmin: (req, res) => requireAdminPermission(req, res, 'users'),
+    safeRoles, checkSellerCanList, adminCanOperateOn, logAdminAction, QUOTA_TIERS,
+});
 // #1013 Phase 86: 5 disputes 读端点已迁出
 registerDisputesReadRoutes(app, {
     db, auth, errorRes,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@seasonkoh/webaz",
-  "version": "0.1.12",
+  "version": "0.1.14",
   "description": "Agent-native decentralized commerce protocol. Humans and AI agents trade on the same protocol via MCP tools.",
   "main": "dist/mcp.js",
   "bin": {