@wowok/agent-mcp 3.4.0 → 3.4.1

package/dist/schemas/onchain_operations_treasury.schema.json

@@ -353,18 +353,26 @@
               "description": "Withdrawal amount"
             },
             "recipient": {
-              "type": "object",
-              "properties": {
-                "name_or_address": {
-                  "type": "string",
-                  "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
+              "anyOf": [
+                {
+                  "description": "Account name, address (0x...), or mark name. When using string format, local marks are searched first. EXAMPLE: 'alice' - searches local marks first, then global; EXAMPLE: '0x2...' (64 hex chars) - uses address directly; EXAMPLE: '' - uses the default local account"
                 },
-                "local_mark_first": {
-                  "description": "Whether to prioritize local marks, if true, prioritize local marks, otherwise prioritize global marks",
-                  "type": "boolean"
+                {
+                  "type": "object",
+                  "properties": {
+                    "name_or_address": {
+                      "type": "string",
+                      "description": "Account/Object name or ID. If specifying an account, use empty string '' for the default account. If it starts with '0x', it will be treated as an ID. Otherwise, it will be treated as a name (max 64 bcs characters)."
+                    },
+                    "local_mark_first": {
+                      "description": "Whether to prioritize local marks, if true, prioritize local marks, otherwise prioritize global marks",
+                      "type": "boolean"
+                    }
+                  },
+                  "additionalProperties": false,
+                  "description": "Account or address lookup object. Use this to specify which account to use for an operation. EXAMPLE: { name_or_address: 'testor2' } - looks up account by name; EXAMPLE: { name_or_address: '0x1234...' } - uses address directly; If name_or_address is empty string '', uses the default local account. name_or_address is REQUIRED — {} resolves to nothing useful and is rejected."
                 }
-              },
-              "additionalProperties": false,
+              ],
               "description": "ID or account to receive assets. On the by_external_withdraw_guard path this MUST equal the transaction sender — external_withdraw pays only the sender (treasury code 10) because the guard authorizes release but cannot constrain the destination; use amount.fixed (permissioned withdraw) to pay another address"
             },
             "payment_info": {
@@ -475,7 +483,7 @@
                             "type": "integer",
                             "minimum": 0,
                             "maximum": 255,
-                            "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails such as full refunds). SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
+                            "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails whose payee is NOT the order itself, such as settlement releases and incentive/bounty claims). NEVER arm 254 on a refund rail: a refund pays the submitted Order through user slot 0, and a refund leg re-entered in a later renewal period would abort E_ONCE_TRIGGERED (16) forever — refund once-ness comes from the terminal-node topology, never from a once slot. SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
                           },
                           {
                             "type": "null"
@@ -489,7 +497,7 @@
                             "type": "integer",
                             "minimum": 0,
                             "maximum": 255,
-                            "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails such as full refunds). SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
+                            "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails whose payee is NOT the order itself, such as settlement releases and incentive/bounty claims). NEVER arm 254 on a refund rail: a refund pays the submitted Order through user slot 0, and a refund leg re-entered in a later renewal period would abort E_ONCE_TRIGGERED (16) forever — refund once-ness comes from the terminal-node topology, never from a once slot. SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
                           },
                           {
                             "type": "null"
@@ -534,7 +542,7 @@
                             "type": "integer",
                             "minimum": 0,
                             "maximum": 255,
-                            "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails such as full refunds). SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
+                            "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails whose payee is NOT the order itself, such as settlement releases and incentive/bounty claims). NEVER arm 254 on a refund rail: a refund pays the submitted Order through user slot 0, and a refund leg re-entered in a later renewal period would abort E_ONCE_TRIGGERED (16) forever — refund once-ness comes from the terminal-node topology, never from a once slot. SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
                           },
                           {
                             "type": "null"
@@ -548,7 +556,7 @@
                             "type": "integer",
                             "minimum": 0,
                             "maximum": 255,
-                            "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails such as full refunds). SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
+                            "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails whose payee is NOT the order itself, such as settlement releases and incentive/bounty claims). NEVER arm 254 on a refund rail: a refund pays the submitted Order through user slot 0, and a refund leg re-entered in a later renewal period would abort E_ONCE_TRIGGERED (16) forever — refund once-ness comes from the terminal-node topology, never from a once slot. SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
                           },
                           {
                             "type": "null"
@@ -637,7 +645,7 @@
                             "type": "integer",
                             "minimum": 0,
                             "maximum": 255,
-                            "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails such as full refunds). SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
+                            "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails whose payee is NOT the order itself, such as settlement releases and incentive/bounty claims). NEVER arm 254 on a refund rail: a refund pays the submitted Order through user slot 0, and a refund leg re-entered in a later renewal period would abort E_ONCE_TRIGGERED (16) forever — refund once-ness comes from the terminal-node topology, never from a once slot. SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
                           },
                           {
                             "type": "null"
@@ -687,7 +695,7 @@
                             "type": "integer",
                             "minimum": 0,
                             "maximum": 255,
-                            "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails such as full refunds). SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
+                            "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails whose payee is NOT the order itself, such as settlement releases and incentive/bounty claims). NEVER arm 254 on a refund rail: a refund pays the submitted Order through user slot 0, and a refund leg re-entered in a later renewal period would abort E_ONCE_TRIGGERED (16) forever — refund once-ness comes from the terminal-node topology, never from a once slot. SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
                           },
                           {
                             "type": "null"
@@ -889,6 +897,13 @@
       "additionalProperties": false,
       "description": "On-chain Treasury operations. USAGE: (1) CREATE NEW: Set 'object' field with OBJECT format {name, type_parameter, permission, ...} to create a Treasury. NOTE: 'name' goes INSIDE 'object', NOT at the data root level. 'permission' can be a new Permission object or reference an existing one - check 'object' field description for details. (2) OPERATE EXISTING: Set 'object' field with STRING format (object ID or name). The 'object' field is CRITICAL and REQUIRED in both cases. STRING for existing, OBJECT for new creation."
     },
+    "idempotency_key": {
+      "type": "string",
+      "minLength": 8,
+      "maxLength": 128,
+      "pattern": "^[A-Za-z0-9._:-]+$",
+      "description": "F-RQ-13A (prescription ⑨): idempotency key for this business attempt. REPLAY GUARD: if a previous call with the SAME key is still open (dispatched but outcome unresolved, or already committed), this call is HELD — you get a structured state_conflict envelope with the prior attempt's verification data instead of a second on-chain submission (the ghost-order guard: two live mainnet orders, two escrows). Lifecycle: a deterministic failure (nothing submitted / provably reverted) clears the key — fix the cause and retry with the SAME key; an unknown-outcome failure (submission may have landed) keeps the key HELD — verify on-chain state first (result.submission_verification tells you where to look), and only retry with a NEW key once the outcome is resolved. Keep one key per business attempt (e.g. 'ord-20261030-042-buy'); do not reuse across attempts."
+    },
     "env": {
       "type": "object",
       "properties": {
@@ -1027,7 +1042,7 @@
                       "type": "integer",
                       "minimum": 0,
                       "maximum": 255,
-                      "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails such as full refunds). SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
+                      "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails whose payee is NOT the order itself, such as settlement releases and incentive/bounty claims). NEVER arm 254 on a refund rail: a refund pays the submitted Order through user slot 0, and a refund leg re-entered in a later renewal period would abort E_ONCE_TRIGGERED (16) forever — refund once-ness comes from the terminal-node topology, never from a once slot. SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
                     },
                     "b_submission": {
                       "type": "boolean",

package/dist/schemas/onchain_table_data.output.json

@@ -6401,11 +6401,111 @@
                         "additionalProperties": false
                       },
                       "description": "Directed supply-chain edges: each forward's purchased sub-services + required proofs."
+                    },
+                    "rails": {
+                      "type": "array",
+                      "items": {
+                        "type": "object",
+                        "properties": {
+                          "guard": {
+                            "type": "string",
+                            "description": "The allocator-bound Guard that gates this Service's money."
+                          },
+                          "purchased_services": {
+                            "type": "array",
+                            "items": {
+                              "type": "object",
+                              "properties": {
+                                "identifier": {
+                                  "type": "integer",
+                                  "minimum": 0,
+                                  "maximum": 255,
+                                  "description": "Guard table identifier."
+                                },
+                                "name": {
+                                  "type": "string",
+                                  "description": "Guard table item name (the emitter's catalog slot name)."
+                                },
+                                "address": {
+                                  "type": "string",
+                                  "description": "The procured sub-Service address (or LocalMark name if not resolvable)."
+                                }
+                              },
+                              "required": [
+                                "identifier",
+                                "name",
+                                "address"
+                              ],
+                              "additionalProperties": false
+                            },
+                            "description": "Foreign-Service commitments carried as constant Address rows (self-pins and the ledger row excluded)."
+                          },
+                          "required_submissions": {
+                            "type": "array",
+                            "items": {
+                              "type": "object",
+                              "properties": {
+                                "identifier": {
+                                  "type": "integer",
+                                  "minimum": 0,
+                                  "maximum": 255,
+                                  "description": "Guard table identifier."
+                                },
+                                "name": {
+                                  "type": "string",
+                                  "description": "Guard table item name (human-readable field name)."
+                                },
+                                "value_type": {
+                                  "type": "string",
+                                  "description": "Expected value type name (e.g. Address, U64, String)."
+                                }
+                              },
+                              "required": [
+                                "identifier",
+                                "name",
+                                "value_type"
+                              ],
+                              "additionalProperties": false
+                            },
+                            "description": "Order-slot rows the gate expects the caller to submit."
+                          },
+                          "ledger": {
+                            "description": "The rendezvous Repository the gate reads rows from (present when the gate reads a ledger bound to this Service).",
+                            "type": "string"
+                          },
+                          "once_slot": {
+                            "type": "boolean",
+                            "description": "A protocol 255 once row is present — the submission form's single-use key."
+                          },
+                          "axis": {
+                            "description": "Who owns the fulfilment order, as stated by the gate's own description.",
+                            "anyOf": [
+                              {
+                                "type": "string",
+                                "const": "merchant_procured"
+                              },
+                              {
+                                "type": "string",
+                                "const": "user_procured"
+                              }
+                            ]
+                          }
+                        },
+                        "required": [
+                          "guard",
+                          "purchased_services",
+                          "required_submissions",
+                          "once_slot"
+                        ],
+                        "additionalProperties": false
+                      },
+                      "description": "Settlement rails gated on a FOREIGN order (order_allocators binding). Empty when this Service has no composition. The on-chain Guard stores no logic tree, so these facts come from the guard's table slot names and description — the emitter's own vocabulary."
                     }
                   },
                   "required": [
                     "service",
-                    "edges"
+                    "edges",
+                    "rails"
                   ],
                   "additionalProperties": false
                 },
@@ -9046,8 +9146,12 @@
               "type": "string",
               "const": "service_panorama"
             },
+            "object_address": {
+              "description": "On-chain Service object address (or LocalMark name). Required when query_type='service_panorama'. PREFERRED field name — the panorama family (service/machine/object) is unified on `object_address` (a Service IS an on-chain object); `service_address` remains accepted as a deprecated alias.",
+              "type": "string"
+            },
             "service_address": {
-              "description": "On-chain Service object address (or LocalMark name). Required when query_type='service_panorama'.",
+              "description": "DEPRECATED alias of object_address (accepted for call compatibility). Prefer object_address. Example: {\"query_type\": \"service_panorama\", \"object_address\": \"0xabc...\"}.",
               "type": "string"
             },
             "context_network": {
@@ -9073,9 +9177,13 @@
               "type": "string",
               "const": "service_quote"
             },
+            "object_address": {
+              "description": "On-chain Service object address (or LocalMark name). Required when query_type='service_quote'. PREFERRED field name — unified with the panorama family on `object_address`; `service_address` remains accepted as a deprecated alias.",
+              "type": "string"
+            },
             "service_address": {
-              "type": "string",
-              "description": "On-chain Service object address (or LocalMark name). Required when query_type='service_quote'."
+              "description": "DEPRECATED alias of object_address (accepted for call compatibility). Prefer object_address. Example: {\"query_type\": \"service_quote\", \"object_address\": \"0xabc...\"}.",
+              "type": "string"
             },
             "items": {
               "description": "Basket to quote. Omit to quote EVERY sale with quantity 1 (the floor basket — order quantity is chosen at buy time, so per-unit prices are the authoritative input).",
@@ -9124,8 +9232,7 @@
             }
           },
           "required": [
-            "query_type",
-            "service_address"
+            "query_type"
           ],
           "additionalProperties": false,
           "description": "READ-ONLY pre-purchase quote of a Service (finding 3.6 — order_new total_pay pre-check): per-item unit price × quantity, the basket total that order_new.buy.total_pay.balance must exactly equal (the on-chain buy aborts on any drift), and the order_allocators fee-split preview (sharing rows of the FIRST allocator — the normal payout path; guards select per-case allocators such as refund/damage, so the live split depends on which guard passes). Also previews the reward terms of every Reward hung on the Service (pool balance, per-claim amount, claim window) so a buyer never budgets on an expired or unfunded reward. Mirrors the on-chain price×quantity semantics WITHOUT calling quote on-chain and NEVER submits a transaction. Amounts are payment-token smallest units plus a human display when the token precision resolves."
@@ -9421,6 +9528,57 @@
           "additionalProperties": false,
           "description": "In-flight order participation analysis for ONE account (GLM6/94): customer / operator / observer perspective derived from on-chain permission matching (never caller-asserted) — per-order operable forwards (branch choices), waiting_on roles, pending claims (reward/discount/compensation/rating), perspective-specific interest hints, aggregated account dashboard. Read-only."
         },
+        {
+          "type": "object",
+          "properties": {
+            "query_type": {
+              "type": "string",
+              "const": "order_aggregate"
+            },
+            "group": {
+              "description": "Grouping dimension, read from each Order's own fields: 'service' (default — the crowd/group-buy pool per service), 'machine' (per workflow) or 'owner' (per ordering account).",
+              "type": "string",
+              "enum": [
+                "service",
+                "machine",
+                "owner"
+              ]
+            },
+            "group_id": {
+              "description": "Restrict the aggregation to ONE group value (exact address match — e.g. the Service address running a crowd-funding campaign). The funding-target verdict then reads a single row.",
+              "type": "string"
+            },
+            "metric": {
+              "description": "Numeric field to sum (default 'amount' — the Order's escrowed payment in smallest units).",
+              "type": "string",
+              "const": "amount"
+            },
+            "exclude_claimed": {
+              "description": "Exclude orders whose compensation has been claimed (claimed_by set). Default false — pass true so refund/compensation payouts are not double-counted toward a target.",
+              "type": "boolean"
+            },
+            "limit": {
+              "description": "Max group rows returned (default 50, max 1000). truncated flags rows beyond the limit; totals ALWAYS cover the full set regardless of the limit.",
+              "type": "integer",
+              "minimum": 1,
+              "maximum": 1000
+            },
+            "context_network": {
+              "type": "string",
+              "enum": [
+                "testnet",
+                "mainnet",
+                "localnet"
+              ],
+              "description": "Network for the query — THIS field is `context_network` (the query tools accept no separate `network` key). Defaults to the user's CURRENT network (client UI selection / authority config) when omitted. 'localnet' is for internal test use against a local fullnode."
+            }
+          },
+          "required": [
+            "query_type"
+          ],
+          "additionalProperties": false,
+          "description": "CROSS-ORDER aggregate over Order objects from the MCP index projection (S17-C / F-RQD2-06): count + exact amount sums per group, with the projection's reconciliation coverage attached. Read-side stand-in for the missing on-chain cross-order primitive — crowd/group-buy targets like '3 x 6 WOW >= 18 WOW before funding' are checked HERE until the protocol grows a native aggregate. A STALE projection refuses to answer loudly (INDEX_STALE_PROJECTION — no legacy fallback can aggregate) instead of serving a funding verdict on old data. Read-only."
+        },
         {
           "type": "object",
           "properties": {
@@ -10664,6 +10822,92 @@
                 "top_risks"
               ],
               "additionalProperties": false
+            },
+            "blueprint_verdict": {
+              "description": "Creation-time blueprint verdict: business intent + host rich semantics + logic tree composed and run through the full per-host verification battery BEFORE the guard create tx. Present when binding_hint maps to a catalog host; absent when no host is known (add binding_hint to enable).",
+              "type": "object",
+              "properties": {
+                "host": {
+                  "type": "string",
+                  "description": "Catalog host id this guard was verified against (guard-host-context)."
+                },
+                "status": {
+                  "type": "string",
+                  "enum": [
+                    "blocked",
+                    "proceed_with_warnings",
+                    "proceed"
+                  ],
+                  "description": "Single authority over create readiness. blocked = structural defect, fix BEFORE create (guards are immutable after create)."
+                },
+                "statement": {
+                  "type": "string",
+                  "description": "One authoritative verdict statement naming the finding codes."
+                },
+                "findings": {
+                  "type": "array",
+                  "items": {
+                    "type": "object",
+                    "properties": {
+                      "source": {
+                        "type": "string",
+                        "description": "Which verifier produced the finding (verifyGuardBinding / auditGuardRelies / auditQuoteGuardCandidate / blueprint)."
+                      },
+                      "code": {
+                        "type": "string",
+                        "description": "Stable finding id (e.g. MF_SLOT_IDENTITY_ANCHOR, RC_NO_ORDER_ANCHOR)."
+                      },
+                      "level": {
+                        "type": "string",
+                        "enum": [
+                          "critical",
+                          "warning",
+                          "info"
+                        ]
+                      },
+                      "detail": {
+                        "type": "string"
+                      }
+                    },
+                    "required": [
+                      "source",
+                      "code",
+                      "level",
+                      "detail"
+                    ],
+                    "additionalProperties": false
+                  },
+                  "description": "All findings from the composed verification battery."
+                },
+                "host_context": {
+                  "description": "The host rich semantics this guard inherits — inlined so the design dialogue argues from facts, not memory.",
+                  "type": "object",
+                  "properties": {
+                    "signer_subject": {
+                      "type": "string"
+                    },
+                    "order_anchor": {
+                      "type": "string"
+                    },
+                    "identity_obligation": {
+                      "type": "string"
+                    }
+                  },
+                  "required": [
+                    "signer_subject",
+                    "order_anchor",
+                    "identity_obligation"
+                  ],
+                  "additionalProperties": false
+                }
+              },
+              "required": [
+                "host",
+                "status",
+                "statement",
+                "findings"
+              ],
+              "additionalProperties": false
             }
           },
           "additionalProperties": false
@@ -11059,6 +11303,14 @@
             "note": {
               "description": "Additional note.",
               "type": "string"
+            },
+            "digest": {
+              "description": "REAL transaction digest of this operation (ddmc4 B-37) — paste into onchain_transaction or a block explorer to audit. Absent under dry-run/simulation.",
+              "type": "string"
+            },
+            "signer": {
+              "description": "Signing account's on-chain address — a SEPARATE field from digest ({signer, digest}), never occupying the digest slot.",
+              "type": "string"
             }
           },
           "required": [