@wowok/agent-mcp 2.7.8 → 3.0.0

package/dist/schemas/onchain_operations_treasury.schema.json

@@ -113,7 +113,7 @@
                       "type": "string"
                     }
                   ],
-                  "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05WOW\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is (loses precision above 2^53). PRECISION RULE: for values exceeding 2^53, ALWAYS use format (1) or (2) — JS numbers lose precision. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer. If multiple tokens share a symbol (ambiguity), specify the full type string in type_parameter. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
+                  "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05WOW\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is only within the safe integer range (±2^53); numbers outside it are REJECTED, use a numeric string instead. PRECISION RULE: for values exceeding 2^53 (9007199254740991), ALWAYS use format (1) or (2) — JS numbers lose integer precision silently and such inputs are blocked. Raw amounts must be plain non-negative integers; a decimal value without a token symbol (e.g. \"2.5\") is rejected — append the symbol (\"2.5WOW\") so the Fund Processing Layer converts it. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer, where the token's FULL type, decimals and raw amount are always visible. MULTIPLE ISSUERS: several on-chain tokens may legally share the same symbol (e.g. multiple \"USDT\" coins). When a bare symbol matches more than one token, the operation is BLOCKED and every candidate is listed with full details (type, name, decimals, verified tag) — present the list to the USER and let them choose (they may answer by number), then re-issue with the chosen token's FULL type string in type_parameter; never guess an issuer from the bare symbol. MISSING TOKEN INFO: when a token's precision cannot be resolved, the operation is REFUSED (raw u64 included — amount magnitude could not be verified). Recovery: provide the token's FULL type in package::module::Name form in type_parameter (a bare symbol like \"USDT\" cannot be resolved), and verify the WOW network is correct. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
                 },
                 "token_type": {
                   "type": "string",
@@ -137,7 +137,7 @@
                             "type": "string"
                           }
                         ],
-                        "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05WOW\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is (loses precision above 2^53). PRECISION RULE: for values exceeding 2^53, ALWAYS use format (1) or (2) — JS numbers lose precision. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer. If multiple tokens share a symbol (ambiguity), specify the full type string in type_parameter. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
+                        "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05WOW\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is only within the safe integer range (±2^53); numbers outside it are REJECTED, use a numeric string instead. PRECISION RULE: for values exceeding 2^53 (9007199254740991), ALWAYS use format (1) or (2) — JS numbers lose integer precision silently and such inputs are blocked. Raw amounts must be plain non-negative integers; a decimal value without a token symbol (e.g. \"2.5\") is rejected — append the symbol (\"2.5WOW\") so the Fund Processing Layer converts it. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer, where the token's FULL type, decimals and raw amount are always visible. MULTIPLE ISSUERS: several on-chain tokens may legally share the same symbol (e.g. multiple \"USDT\" coins). When a bare symbol matches more than one token, the operation is BLOCKED and every candidate is listed with full details (type, name, decimals, verified tag) — present the list to the USER and let them choose (they may answer by number), then re-issue with the chosen token's FULL type string in type_parameter; never guess an issuer from the bare symbol. MISSING TOKEN INFO: when a token's precision cannot be resolved, the operation is REFUSED (raw u64 included — amount magnitude could not be verified). Recovery: provide the token's FULL type in package::module::Name form in type_parameter (a bare symbol like \"USDT\" cannot be resolved), and verify the WOW network is correct. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
                       },
                       "payment": {
                         "type": "string",
@@ -199,7 +199,7 @@
                           "type": "string"
                         }
                       ],
-                      "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05WOW\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is (loses precision above 2^53). PRECISION RULE: for values exceeding 2^53, ALWAYS use format (1) or (2) — JS numbers lose precision. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer. If multiple tokens share a symbol (ambiguity), specify the full type string in type_parameter. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
+                      "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05WOW\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is only within the safe integer range (±2^53); numbers outside it are REJECTED, use a numeric string instead. PRECISION RULE: for values exceeding 2^53 (9007199254740991), ALWAYS use format (1) or (2) — JS numbers lose integer precision silently and such inputs are blocked. Raw amounts must be plain non-negative integers; a decimal value without a token symbol (e.g. \"2.5\") is rejected — append the symbol (\"2.5WOW\") so the Fund Processing Layer converts it. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer, where the token's FULL type, decimals and raw amount are always visible. MULTIPLE ISSUERS: several on-chain tokens may legally share the same symbol (e.g. multiple \"USDT\" coins). When a bare symbol matches more than one token, the operation is BLOCKED and every candidate is listed with full details (type, name, decimals, verified tag) — present the list to the USER and let them choose (they may answer by number), then re-issue with the chosen token's FULL type string in type_parameter; never guess an issuer from the bare symbol. MISSING TOKEN INFO: when a token's precision cannot be resolved, the operation is REFUSED (raw u64 included — amount magnitude could not be verified). Recovery: provide the token's FULL type in package::module::Name form in type_parameter (a bare symbol like \"USDT\" cannot be resolved), and verify the WOW network is correct. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
                     }
                   },
                   "required": [
@@ -327,7 +327,7 @@
                           "type": "string"
                         }
                       ],
-                      "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05WOW\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is (loses precision above 2^53). PRECISION RULE: for values exceeding 2^53, ALWAYS use format (1) or (2) — JS numbers lose precision. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer. If multiple tokens share a symbol (ambiguity), specify the full type string in type_parameter. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
+                      "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05WOW\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is only within the safe integer range (±2^53); numbers outside it are REJECTED, use a numeric string instead. PRECISION RULE: for values exceeding 2^53 (9007199254740991), ALWAYS use format (1) or (2) — JS numbers lose integer precision silently and such inputs are blocked. Raw amounts must be plain non-negative integers; a decimal value without a token symbol (e.g. \"2.5\") is rejected — append the symbol (\"2.5WOW\") so the Fund Processing Layer converts it. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer, where the token's FULL type, decimals and raw amount are always visible. MULTIPLE ISSUERS: several on-chain tokens may legally share the same symbol (e.g. multiple \"USDT\" coins). When a bare symbol matches more than one token, the operation is BLOCKED and every candidate is listed with full details (type, name, decimals, verified tag) — present the list to the USER and let them choose (they may answer by number), then re-issue with the chosen token's FULL type string in type_parameter; never guess an issuer from the bare symbol. MISSING TOKEN INFO: when a token's precision cannot be resolved, the operation is REFUSED (raw u64 included — amount magnitude could not be verified). Recovery: provide the token's FULL type in package::module::Name form in type_parameter (a bare symbol like \"USDT\" cannot be resolved), and verify the WOW network is correct. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
                     }
                   },
                   "required": [
@@ -797,7 +797,7 @@
                       "type": "string"
                     }
                   ],
-                  "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05WOW\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is (loses precision above 2^53). PRECISION RULE: for values exceeding 2^53, ALWAYS use format (1) or (2) — JS numbers lose precision. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer. If multiple tokens share a symbol (ambiguity), specify the full type string in type_parameter. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
+                  "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05WOW\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is only within the safe integer range (±2^53); numbers outside it are REJECTED, use a numeric string instead. PRECISION RULE: for values exceeding 2^53 (9007199254740991), ALWAYS use format (1) or (2) — JS numbers lose integer precision silently and such inputs are blocked. Raw amounts must be plain non-negative integers; a decimal value without a token symbol (e.g. \"2.5\") is rejected — append the symbol (\"2.5WOW\") so the Fund Processing Layer converts it. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer, where the token's FULL type, decimals and raw amount are always visible. MULTIPLE ISSUERS: several on-chain tokens may legally share the same symbol (e.g. multiple \"USDT\" coins). When a bare symbol matches more than one token, the operation is BLOCKED and every candidate is listed with full details (type, name, decimals, verified tag) — present the list to the USER and let them choose (they may answer by number), then re-issue with the chosen token's FULL type string in type_parameter; never guess an issuer from the bare symbol. MISSING TOKEN INFO: when a token's precision cannot be resolved, the operation is REFUSED (raw u64 included — amount magnitude could not be verified). Recovery: provide the token's FULL type in package::module::Name form in type_parameter (a bare symbol like \"USDT\" cannot be resolved), and verify the WOW network is correct. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
                 },
                 "token_type": {
                   "type": "string",
@@ -821,7 +821,7 @@
                             "type": "string"
                           }
                         ],
-                        "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05WOW\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is (loses precision above 2^53). PRECISION RULE: for values exceeding 2^53, ALWAYS use format (1) or (2) — JS numbers lose precision. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer. If multiple tokens share a symbol (ambiguity), specify the full type string in type_parameter. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
+                        "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05WOW\" — auto-converted to smallest units via the Fund Processing Layer (token precision resolved from official registry → cache → on-chain). The symbol MUST match the token's type_parameter. (2) SMALLEST UNIT (numeric string): \"10000000000\" — used as-is, no conversion. (3) SMALLEST UNIT (number): 10000000000 — used as-is only within the safe integer range (±2^53); numbers outside it are REJECTED, use a numeric string instead. PRECISION RULE: for values exceeding 2^53 (9007199254740991), ALWAYS use format (1) or (2) — JS numbers lose integer precision silently and such inputs are blocked. Raw amounts must be plain non-negative integers; a decimal value without a token symbol (e.g. \"2.5\") is rejected — append the symbol (\"2.5WOW\") so the Fund Processing Layer converts it. Default token: WOW (9 decimals, 1 WOW = 10^9 MIST). For custom tokens: use display format with the token's symbol, or pass smallest units directly. MONEY CONFIRMATION: all monetary fields trigger user confirmation via the Fund Processing Layer, where the token's FULL type, decimals and raw amount are always visible. MULTIPLE ISSUERS: several on-chain tokens may legally share the same symbol (e.g. multiple \"USDT\" coins). When a bare symbol matches more than one token, the operation is BLOCKED and every candidate is listed with full details (type, name, decimals, verified tag) — present the list to the USER and let them choose (they may answer by number), then re-issue with the chosen token's FULL type string in type_parameter; never guess an issuer from the bare symbol. MISSING TOKEN INFO: when a token's precision cannot be resolved, the operation is REFUSED (raw u64 included — amount magnitude could not be verified). Recovery: provide the token's FULL type in package::module::Name form in type_parameter (a bare symbol like \"USDT\" cannot be resolved), and verify the WOW network is correct. Examples: \"2.5WOW\" (display → 2500000000), 10000000000 (number, smallest unit), \"50000000000\" (string, smallest unit). Used for: Service.sale.price, Service.compensation_fund_add balance, Treasury.deposit, Arbitration.fee, Reward.amount, stock quantities."
                       },
                       "payment": {
                         "type": "string",
@@ -910,7 +910,7 @@
             "testnet",
             "mainnet"
           ],
-          "description": "Network entrypoint: Specifies which network the operation occurs on. FIX-010 cross-network note: LocalMark names are scoped per network (testnet marks are invisible on mainnet and vice versa). When migrating from testnet to mainnet, recreate all objects on mainnet and re-register LocalMark names with the SAME names to keep name-based references working across networks. Use project_operation action='clone_project_to_network' to clone the project blueprint to the target network, then re-run onchain_operations with env.network=target_network to deploy."
+          "description": "Network entrypoint: Specifies which network the operation occurs on. FIX-010 cross-network note: LocalMark names are scoped per network (testnet marks are invisible on mainnet and vice versa). When migrating from testnet to mainnet, recreate all objects on mainnet and re-register LocalMark names with the SAME names to keep name-based references working across networks. Recreate all objects on the target network via onchain_operations with env.network=target_network, then re-register the LocalMark names."
         },
         "referrer": {
           "description": "Referrer ID. If the user is using the network for the first time, the referrer ID will be recorded (also applied when the SDK auto-registers the sender in the global Entity table).",
@@ -931,8 +931,8 @@
             "type": "string"
           }
         },
-        "project": {
-          "description": "Project prefix to assign this object to (e.g. 'myshop'). When set: 1) the object is tagged with 'project:<prefix>' on-chain automatically via ProjectService, 2) the newly created object is auto-associated to the SQLite project for local management, evaluation, and graph tracking. The project MUST exist (create via project_operation action='create_project' first). Use project_operation to manage projects.",
+        "plan_approval": {
+          "description": "K3 24 PlanApproval: id of a goal whose plan was approved via goal_operation action='approve'. When set: 1) the ConfirmGate treats fail-open rules (standard/none levels) as pre-approved for operations under this goal's plan; 2) after successful CREATION operations, the created objects are auto-registered into the goal (GoalRecord.objects + its TaskProcess manifest — ACT station 'execution registers'). Fail-closed levels (irreversible/publish/amount) still require per-operation confirmation with env.confirmed=true.",
           "type": "string"
         },
         "client_schema_version": {

package/dist/schemas/onchain_table_data.output.json

@@ -9064,6 +9064,403 @@
             "result"
           ],
           "additionalProperties": false
+        },
+        {
+          "type": "object",
+          "properties": {
+            "query_type": {
+              "type": "string",
+              "const": "service_panorama"
+            },
+            "service_address": {
+              "description": "On-chain Service object address (or LocalMark name). Required when query_type='service_panorama'.",
+              "type": "string"
+            },
+            "context_network": {
+              "type": "string",
+              "enum": [
+                "testnet",
+                "mainnet",
+                "localnet"
+              ],
+              "description": "Network for the query. Defaults to 'testnet' if omitted. 'localnet' is for internal test use against a local fullnode."
+            }
+          },
+          "required": [
+            "query_type"
+          ],
+          "additionalProperties": false,
+          "description": "ONE-CALL full business-intelligence context of an on-chain Service (K3 22 / Business Service tab): base data + machine workflow graph + buy_guard/permission/allocator guards + related objects + supply chain + trust summary + deterministic BusinessReport + recent orders. Every section degrades gracefully — failures are reported in `data_gaps`. Read-only."
+        },
+        {
+          "type": "object",
+          "properties": {
+            "query_type": {
+              "type": "string",
+              "const": "machine_panorama"
+            },
+            "object_address": {
+              "description": "On-chain object address (0x followed by 32-64 hex chars). Also accepts a LocalMark NAME (resolved automatically). H-06 fix: invalid formats are rejected at the handler level with a descriptive error.",
+              "type": "string"
+            },
+            "context_network": {
+              "type": "string",
+              "enum": [
+                "testnet",
+                "mainnet",
+                "localnet"
+              ],
+              "description": "Network for the query. Defaults to 'testnet' if omitted. 'localnet' is for internal test use against a local fullnode."
+            }
+          },
+          "required": [
+            "query_type"
+          ],
+          "additionalProperties": false,
+          "description": "ONE-CALL panorama of an on-chain Machine (Business Machine tab; Machine counterpart of service_panorama): head (name/tags/description/published/paused) + the Machine's own fields (permission/um/node_count/consensus repositories) + workflow graph (nodes/edges/forwards) + Progress list from the GLOBAL tx table (0xaaf, Machine address as KEY). Read-only."
+        },
+        {
+          "type": "object",
+          "properties": {
+            "query_type": {
+              "type": "string",
+              "const": "object_panorama"
+            },
+            "object_address": {
+              "description": "On-chain object address (0x followed by 32-64 hex chars) for object_panorama. Also accepts a LocalMark NAME (resolved automatically). H-06 fix: invalid formats are rejected at the handler level with a descriptive error.",
+              "type": "string"
+            },
+            "context_network": {
+              "type": "string",
+              "enum": [
+                "testnet",
+                "mainnet",
+                "localnet"
+              ],
+              "description": "Network for the query. Defaults to 'testnet' if omitted. 'localnet' is for internal test use against a local fullnode."
+            }
+          },
+          "required": [
+            "query_type"
+          ],
+          "additionalProperties": false,
+          "description": "ONE-CALL detail-page panorama for Progress / Demand / Order / Arb / Repository objects (client panorama family): discriminated `object_type` + head (name/tags/description) + the object's own typed fields + type-specific extras (Demand presenters from the GLOBAL tx table, Progress session/forwards, Arb votes & propositions, Repository policies). Read-only."
+        },
+        {
+          "type": "object",
+          "properties": {
+            "query_type": {
+              "type": "string",
+              "const": "review_pack"
+            },
+            "object_address": {
+              "description": "On-chain object address (0x followed by 32-64 hex chars) for review_pack. Also accepts a LocalMark NAME (resolved automatically). H-06 fix: invalid formats are rejected at the handler level with a descriptive error.",
+              "type": "string"
+            },
+            "context_network": {
+              "type": "string",
+              "enum": [
+                "testnet",
+                "mainnet",
+                "localnet"
+              ],
+              "description": "Network for the query. Defaults to 'testnet' if omitted. 'localnet' is for internal test use against a local fullnode."
+            }
+          },
+          "required": [
+            "query_type"
+          ],
+          "additionalProperties": false,
+          "description": "ONE-CALL typed ReviewPack for the client's generic ReviewPackRenderer (K3 24 §5.2 / G3) — section list + typed field values; the UI-convention defaults live in the renderer, the section composition lives in the MCP assembler. Runs the matching panorama (one chain-query pass) and reshapes it. Supported types: Order, Service, Arb, Demand, Repository, Progress, Machine. Read-only."
+        },
+        {
+          "type": "object",
+          "properties": {
+            "query_type": {
+              "type": "string",
+              "const": "assemble_context"
+            },
+            "context_objects": {
+              "description": "Object IDs (0x...) or LocalMark names to assemble context for. Required when query_type='assemble_context'. The current on-chain state of each object will be queried and enriched with semantic annotations.",
+              "type": "array",
+              "items": {
+                "type": "string"
+              }
+            },
+            "include_events": {
+              "description": "When true, assemble_context also queries recent state-transition events (NewOrderEvent, ProgressEvent, ArbEvent, etc.). Events are the real-time transition log — convergent and bounded. Defaults to false. Note: object-embedded history (ProgressSession.forwards, Order.disputes) is ALWAYS extracted automatically — no flag needed.",
+              "type": "boolean"
+            },
+            "context_network": {
+              "type": "string",
+              "enum": [
+                "testnet",
+                "mainnet",
+                "localnet"
+              ],
+              "description": "Network for the query. Defaults to 'testnet' if omitted. 'localnet' is for internal test use against a local fullnode."
+            },
+            "context_depth": {
+              "description": "BFS recursion depth for dependency expansion in assemble_context (default 0 = no expansion). When >0, the assembly recursively queries objects referenced by the center objects (permission, guard, machine, service, repositories, etc.) up to the given depth, using the same address-field extraction rules as extractAddressFields. Each level issues one batched query_objects call (≤50 IDs per batch). Cycles are detected and skipped via a visited set. Discovered dependencies are returned in `dependencies` (edge metadata) and `dependency_objects` (full object states). Recommended: 1–2 for most use cases; 3+ may pull large subgraphs (use context_include to constrain).",
+              "type": "integer",
+              "minimum": 0,
+              "maximum": 5
+            },
+            "context_include": {
+              "description": "Optional filter for dependency expansion edge types. When omitted, ALL outbound references are followed. When provided, only edges whose `field` matches one of the listed names are followed. Recognized field names (from extractAddressFields): 'permission', 'machine', 'service', 'progress', 'buy_guard', 'um', 'repositories', 'arbitrations', 'rewards', 'consensus_repositories', 'context_repositories', 'dispute', 'allocation', 'external_deposit_guard', 'external_withdraw_guard', 'allocator_guard', 'for_object', 'for_guard', 'payment', 'voting_guard', 'usage_guard', 'guard', 'write_guard', 'quote_guard', 'recipient_entity', 'order_allocators'. Example: ['permission','guard'] expands only permission/guard dependencies.",
+              "type": "array",
+              "items": {
+                "type": "string"
+              }
+            }
+          },
+          "required": [
+            "query_type"
+          ],
+          "additionalProperties": false,
+          "description": "Semantic context assembly (GLM5 §6, Layer 3): query on-chain object states + extract embedded history + optional events + optional BFS dependency expansion, and assemble a structured context for LLM consumption. Required: context_objects (array of object IDs/names). Read-only."
+        },
+        {
+          "type": "object",
+          "properties": {
+            "query_type": {
+              "type": "string",
+              "const": "reverse_map"
+            },
+            "context_objects": {
+              "description": "Object IDs (0x...) or LocalMark names to feed into the report. Required when query_type='reverse_map' (include the Service; add Machine/Allocation for refund-path detection).",
+              "type": "array",
+              "items": {
+                "type": "string"
+              }
+            },
+            "context_network": {
+              "type": "string",
+              "enum": [
+                "testnet",
+                "mainnet",
+                "localnet"
+              ],
+              "description": "Network for the query. Defaults to 'testnet' if omitted. 'localnet' is for internal test use against a local fullnode."
+            },
+            "reverse_order_amount": {
+              "description": "Escrowed order amount (smallest-unit string) for reverse_map — included in the report summary as the concrete escrow mention.",
+              "type": "string"
+            }
+          },
+          "required": [
+            "query_type"
+          ],
+          "additionalProperties": false,
+          "description": "Deterministic L4→L1 business report (K3 03 reverse lane; no LLM): queries the objects, classifies into business semantics, emits merchant profile + user risk assessment + game-theory analysis. Same objects ALWAYS yield the same report. Required: context_objects (include the Service; add Machine/Allocation for refund-path detection). Read-only."
+        },
+        {
+          "type": "object",
+          "properties": {
+            "query_type": {
+              "type": "string",
+              "const": "participation_radar"
+            },
+            "radar_account": {
+              "description": "Account to analyze — address (0x...) or LocalMark name (resolved to an address). Required when query_type='participation_radar'. The perspective (customer/operator/observer) is DERIVED from on-chain data (Order.builder + PermissionPerm grants) — never asserted by this field.",
+              "type": "string"
+            },
+            "radar_targets": {
+              "description": "In-flight orders to analyze (1-20). Required when query_type='participation_radar'. Each target is analyzed independently; results are aggregated into one account dashboard.",
+              "minItems": 1,
+              "maxItems": 20,
+              "type": "array",
+              "items": {
+                "type": "object",
+                "properties": {
+                  "progress": {
+                    "type": "string",
+                    "description": "Progress object address (0x...) or LocalMark name. The Progress carries the current node + bound Machine."
+                  },
+                  "order": {
+                    "description": "Order object address or LocalMark name (optional but recommended — enables order-holder detection, service-level compensation/reward claims, and dispute context).",
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "progress"
+                ],
+                "additionalProperties": false
+              }
+            },
+            "radar_include_alerts": {
+              "description": "Attach order-monitor alerts (progress stall / compensation fund / review & arbitration windows) to each per-order result. Default true.",
+              "type": "boolean"
+            },
+            "radar_monitor_thresholds": {
+              "description": "Optional per-call overrides for order-monitor alert thresholds (only used when radar_include_alerts is on). All fields optional; omitted fields keep defaults. Units: hours/days as marked per field.",
+              "type": "object",
+              "properties": {
+                "progress_stall_hours": {
+                  "description": "Progress stall alert threshold in HOURS. Default 0 = auto (expected_node_duration × 2).",
+                  "type": "number",
+                  "exclusiveMinimum": 0
+                },
+                "compensation_drop_ratio": {
+                  "description": "Compensation fund drop alert ratio (0-1). Default 0.3 = alert on ≥30% drop.",
+                  "type": "number",
+                  "minimum": 0,
+                  "maximum": 1
+                },
+                "compensation_coverage_min": {
+                  "description": "Minimum compensation coverage ratio vs order amount (0-1). Default 1.0 = must fully cover.",
+                  "type": "number",
+                  "minimum": 0,
+                  "maximum": 1
+                },
+                "messenger_timeout_hours": {
+                  "description": "Messenger no-reply timeout in HOURS. Default 24.",
+                  "type": "number",
+                  "exclusiveMinimum": 0
+                },
+                "review_window_closing_days": {
+                  "description": "Review window near-closing alert threshold in DAYS. Default 3.",
+                  "type": "number",
+                  "exclusiveMinimum": 0
+                },
+                "arb_window_closing_days": {
+                  "description": "Arbitration window near-closing alert threshold in DAYS. Default 3.",
+                  "type": "number",
+                  "exclusiveMinimum": 0
+                }
+              },
+              "additionalProperties": false
+            },
+            "context_network": {
+              "type": "string",
+              "enum": [
+                "testnet",
+                "mainnet",
+                "localnet"
+              ],
+              "description": "Network for the query. Defaults to 'testnet' if omitted. 'localnet' is for internal test use against a local fullnode."
+            }
+          },
+          "required": [
+            "query_type"
+          ],
+          "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": "relationship_profile"
+            },
+            "radar_account": {
+              "description": "Anchor account to analyze — address (0x...) or LocalMark name. Required when query_type='relationship_profile'. ANY distributed account works (not only local accounts): the anchor is just an address; all relationships derive from on-chain power carriers.",
+              "type": "string"
+            },
+            "relation_kinds": {
+              "description": "Filter to specific relationship kinds (default: all). employment = merchant × staff (principal-agent); process_operation = machine node operators; agency = order owner × agents; transaction = customer × merchant; supply = demander × presenters; arbitration_delegation = service owner × arbitrators; dispute_resolution = arbitrator × disputants; value_distribution = payer × allocation recipients; contact_membership = communication channel members.",
+              "type": "array",
+              "items": {
+                "type": "string",
+                "enum": [
+                  "employment",
+                  "process_operation",
+                  "agency",
+                  "transaction",
+                  "supply",
+                  "arbitration_delegation",
+                  "dispute_resolution",
+                  "value_distribution",
+                  "contact_membership"
+                ]
+              }
+            },
+            "context_network": {
+              "type": "string",
+              "enum": [
+                "testnet",
+                "mainnet",
+                "localnet"
+              ],
+              "description": "Network for the query. Defaults to 'testnet' if omitted. 'localnet' is for internal test use against a local fullnode."
+            }
+          },
+          "required": [
+            "query_type"
+          ],
+          "additionalProperties": false,
+          "description": "Business Relationship Graph (K3/19): derive ONE account's full relationship web from on-chain power carriers (Permission memberships, Machine forwards, Orders, Demand presenters, Allocation sharing, Arbitration bindings, Contact ims). Each edge carries the three dimensions — 权属 power (what each side CAN do, and where that power lives on-chain), 利益 interest (gains/exposures, with registry-declared goal tensions like principal-agent divergence), and 价值交互 value flows (escrow → allocation → payment chains). Read-only; roles are DERIVED from chain data, never asserted."
+        },
+        {
+          "type": "object",
+          "properties": {
+            "query_type": {
+              "type": "string",
+              "const": "workspace_lists"
+            },
+            "no_cache": {
+              "description": "Set to true to bypass both the aggregation cache and the SDK chain-read cache.",
+              "type": "boolean"
+            },
+            "context_network": {
+              "type": "string",
+              "enum": [
+                "testnet",
+                "mainnet",
+                "localnet"
+              ],
+              "description": "Network for the query. Defaults to 'testnet' if omitted. 'localnet' is for internal test use against a local fullnode."
+            },
+            "account": {
+              "description": "Scope the aggregation to ONE account address (the client's current account). Omit to aggregate across ALL local accounts.",
+              "type": "string"
+            },
+            "light": {
+              "description": "Set to true for the fast first-paint phase: rows carry address / type / name / time only, skipping the per-object enrichment (dead-object probe, registrar votes, per-family extras). Used for progressive list loading; the client merges the full result afterwards.",
+              "type": "boolean"
+            }
+          },
+          "required": [
+            "query_type"
+          ],
+          "additionalProperties": false,
+          "description": "ONE-CALL workspace object lists for ONE account (client Quick Access workspace buckets) — pass `account` to scope to the current account; omit to aggregate across ALL local accounts: treasuries / repositories / contacts / machines / rewards come from the unified permission reverse chain (account → EntityPermission @0xaad → permission-keyed ObjectLinkerCore @0xaae, the ONE source every permission-bearing object family writes to) plus account-keyed EntityContact memberships (@0xaa9) for contacts; others = account-keyed ObjectLinkerTx (@0xaaf) touches, deduplicated, minus all classified business types. Each item: object address + type + local name + time. Aggregation result is TTL-cached (120s, keyed by network + account). Read-only."
+        },
+        {
+          "type": "object",
+          "properties": {
+            "query_type": {
+              "type": "string",
+              "const": "marks_of_account"
+            },
+            "no_cache": {
+              "description": "Set to true to bypass both the aggregation cache and the SDK chain-read cache.",
+              "type": "boolean"
+            },
+            "context_network": {
+              "type": "string",
+              "enum": [
+                "testnet",
+                "mainnet",
+                "localnet"
+              ],
+              "description": "Network for the query. Defaults to 'testnet' if omitted. 'localnet' is for internal test use against a local fullnode."
+            },
+            "account": {
+              "description": "Scope to ONE account address (the client's current account). Omit to merge across ALL local accounts.",
+              "type": "string"
+            },
+            "light": {
+              "description": "Set to true for the fast first-paint phase: rows carry address / type only (vote_kinds is empty until the full result), skipping the per-target registrar-vote reads + object enrichment. Used for progressive list loading; the client merges the full result afterwards.",
+              "type": "boolean"
+            }
+          },
+          "required": [
+            "query_type"
+          ],
+          "additionalProperties": false,
+          "description": "Like / Favor list for ONE account (client Quick Access 'Like / Favor' tab) — every address (object OR plain user) the account has EVER liked / disliked / favored, deduplicated, with the CURRENT active vote kinds per target. Deterministic source: the voter's own Resource mark table (registrar.move handle_vote → resource::tag_set), cross-read with the target's EntityLinker votes for the 'marked at' clock. Fully-toggled-off targets are dropped. Each row: address + tags (like/dislike/favor) + time + object_type (null = plain user) + local name / description / tags. Aggregation result is TTL-cached (120s, keyed by network + account). Read-only."
         }
       ]
     },
@@ -9467,10 +9864,10 @@
               "items": {
                 "type": "string"
               },
-              "description": "Phase 2 services currently active (enabled). Example: ['confirm_gate','project_service','experience_layer']"
+              "description": "Phase 2 services currently active (enabled). Example: ['confirm_gate','experience_layer']"
             },
             "inactive": {
-              "description": "Phase 2 services currently inactive (can be toggled via config_operation). Example: ['harness','graph_persist']",
+              "description": "Phase 2 services currently inactive (can be toggled via config_operation). Example: ['harness']",
               "type": "array",
               "items": {
                 "type": "string"