@wowok/agent-mcp 2.6.3 → 2.6.6

package/dist/schemas/index.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "title": "WoWok MCP Schema Index",
   "description": "Index of all available JSON schemas for WoWok MCP tools",
-  "generatedAt": "2026-07-29T00:14:19.691Z",
+  "generatedAt": "2026-08-08T11:43:07.636Z",
   "tools": [
     {
       "name": "onchain_operations",

package/dist/schemas/machineNode2file.schema.json

@@ -22,6 +22,7 @@
             "json",
             "markdown"
           ],
+          "default": "json",
           "description": "Output format: 'json' (default) or 'markdown'"
         },
         "env": {
@@ -77,6 +78,7 @@
             },
             "schema_strict_mode": {
               "type": "boolean",
+              "default": false,
               "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
             },
             "dry_run": {

package/dist/schemas/messenger_operation.schema.json

@@ -1423,7 +1423,7 @@
           "additionalProperties": false
         }
       ],
-      "description": "Messenger operation input schema"
+      "description": "Messenger operation input schema. PREREQUISITE: an account must ENABLE messenger before sending/receiving. There is NO 'enable' operation in this tool — enable via account_operation {messenger: {enabled: true, name_or_account: '<account>'}}, or implicitly via send_message/send_file with options.enable_messenger: true. Use proof_message to anchor a message's WTS proof on-chain (creates a Proof object consumable by Guards via proof.signer/proof.time queries)."
     }
   }
 }

package/dist/schemas/onchain_operations.schema.json

@@ -1026,6 +1026,7 @@
             },
             "schema_strict_mode": {
               "type": "boolean",
+              "default": false,
               "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
             },
             "dry_run": {
@@ -1189,6 +1190,7 @@
             },
             "schema_strict_mode": {
               "type": "boolean",
+              "default": false,
               "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
             },
             "dry_run": {
@@ -1265,6 +1267,7 @@
         },
         "schema_strict_mode": {
           "type": "boolean",
+          "default": false,
           "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
         },
         "dry_run": {
@@ -2075,7 +2078,7 @@
                       },
                       "wip_hash": {
                         "type": "string",
-                        "description": "WIP file hash (hex string). EMPTY string \"\" skips hash comparison (TESTING ONLY). Production: fill with the hash you saw when viewing the product, to prevent merchant replacing the WIP file before order."
+                        "description": "SHA-256 hash (hex string) of the sale's WIP file, committed on-chain by the merchant. BUY RULE: if this is NON-EMPTY, the buyer MUST pass this exact value as wip_hash when creating an order (ServiceBuyItem.wip_hash) — NEVER use \"\". Pinning the on-chain hash prevents the merchant from replacing the WIP file (a legitimate update) between the buyer's view and order placement, ensuring 'what you see is what you get'. EMPTY means no hash was committed (TESTING ONLY, no delivery-integrity guarantee)."
                       }
                     },
                     "required": [
@@ -2223,11 +2226,11 @@
         },
         "rewards": {
           "$ref": "#/definitions/data_service/properties/repositories",
-          "description": "Service Reward object list."
+          "description": "Service Reward object list. May share the Service's Permission (no conflict check — intentional: rewards are the provider's own incentive tool; only Arbitration requires a different Permission for neutrality)."
         },
         "arbitrations": {
           "$ref": "#/definitions/data_service/properties/repositories",
-          "description": "Service Arbitration object list. FORMAT: same as repositories — use the `objects` field name inside the operation data. Example: {arbitrations: [{name: 'my_arb_1'}, {name: 'my_arb_2'}]}. Each item is a NameOrAddress (object ID or local mark name)."
+          "description": "Service Arbitration object list. FORMAT: same as repositories — use the `objects` field name inside the operation data. Example: {arbitrations: [{name: 'my_arb_1'}, {name: 'my_arb_2'}]}. Each item is a NameOrAddress (object ID or local mark name). ⚠️ PERMISSION RULE (contract-enforced, service.move arbitration_add_imp): every Arbitration bound here MUST use a Permission object DIFFERENT from THIS Service's permission — binding an Arbitration that shares the Service's Permission aborts with E_ARBITRATION_PERMISSION_CONFLICT (error 33). Create a dedicated Permission for each Arbitration BEFORE binding. DESIGN RATIONALE (confirmed intentional): dispute resolution requires NEUTRALITY — an Arbitration controlled by the same Permission admins as the Service it judges would be a conflict of interest. ONLY Arbitration has this check: Reward and Treasury objects MAY share the Service's Permission (they are the provider's own tools)."
         },
         "machine": {
           "anyOf": [
@@ -3642,7 +3645,8 @@
                 "unhold",
                 "adminUnhold"
               ],
-              "description": "Operation type on the forward (CANONICAL form — prefer this): 'next' = advance the forward (accomplish); 'hold' = set hold to block the forward; 'unhold' = self-unhold, release own hold (no 224 permission needed); 'adminUnhold' = force-release hold via 224 permission (PROGRESS_UNHOLD). LEGACY ALIAS: `hold: boolean` is auto-converted to `op` — `hold:true`→`op:'hold'`, `hold:false`→`op:'next'`. New code should use `op` directly."
+              "default": "next",
+              "description": "Operation type on the forward (CANONICAL form — prefer this). DEFAULT: 'next' when omitted. 'next' = advance the forward (accomplish); 'hold' = set hold to block the forward; 'unhold' = self-unhold, release own hold (no 224 permission needed); 'adminUnhold' = force-release hold via 224 permission (PROGRESS_UNHOLD). LEGACY ALIAS: `hold: boolean` is auto-converted to `op` — `hold:true`→`op:'hold'`, `hold:false`→`op:'next'`. New code should use `op` directly."
             },
             "message": {
               "type": "string",
@@ -3650,11 +3654,96 @@
             }
           },
           "required": [
-            "operation",
-            "op"
+            "operation"
           ],
           "additionalProperties": false,
           "description": "Advance Progress object. op field selects the operation: next/hold/unhold/adminUnhold."
+        },
+        "owner_receive": {
+          "anyOf": [
+            {
+              "type": "array",
+              "items": {
+                "type": "object",
+                "properties": {
+                  "id": {
+                    "type": "string",
+                    "minLength": 1,
+                    "description": "Received object ID"
+                  },
+                  "type": {
+                    "type": "string",
+                    "minLength": 1,
+                    "description": "Object type"
+                  },
+                  "content_raw": {
+                    "description": "Raw content data"
+                  }
+                },
+                "required": [
+                  "id",
+                  "type"
+                ],
+                "additionalProperties": false,
+                "description": "Received normal object record"
+              }
+            },
+            {
+              "type": "object",
+              "properties": {
+                "balance": {
+                  "type": [
+                    "number",
+                    "string"
+                  ],
+                  "description": "A coin/balance amount. Accepts three formats: (1) DISPLAY FORMAT with token symbol: \"2.5WOW\", \"10USDC\", \"0.05SUI\" — 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."
+                },
+                "token_type": {
+                  "type": "string",
+                  "description": "Asset type of Coin objects. Supports CoinWrapper<...> format for order receive operations."
+                },
+                "received": {
+                  "type": "array",
+                  "items": {
+                    "type": "object",
+                    "properties": {
+                      "id": {
+                        "type": "string",
+                        "description": "Received CoinWrapper object ID"
+                      },
+                      "balance": {
+                        "$ref": "#/definitions/data_progress/properties/owner_receive/anyOf/1/properties/balance"
+                      },
+                      "payment": {
+                        "type": "string",
+                        "description": "Payment object ID"
+                      }
+                    },
+                    "required": [
+                      "id",
+                      "balance",
+                      "payment"
+                    ],
+                    "additionalProperties": false,
+                    "description": "Received CoinWrapper object record"
+                  },
+                  "description": "Received records of Coin objects"
+                }
+              },
+              "required": [
+                "balance",
+                "token_type",
+                "received"
+              ],
+              "additionalProperties": false,
+              "description": "Received record of Coin objects"
+            },
+            {
+              "type": "string",
+              "const": "recently"
+            }
+          ],
+          "description": "Unwrap CoinWrapper objects and other objects received by this Progress object and send them to the owner of the bound Machine's Permission object.\n\nACCEPTED FORMATS (F-06 unified receive operation block):\n• 'recently' (string literal) — auto-query and receive ALL recently received objects.\n  Use this for the common case: \"withdraw everything the object has received.\"\n  Example: receive: 'recently'\n• ReceivedNormal[] (array) — explicit list of received objects to unwrap.\n  Use this when you want to receive specific objects only (not all).\n  Example: receive: [{id: '0xobj1', type: '0x2::coin::Coin<0x2::sui::SUI>'}]\n• ReceivedBalance ({token_type, balance, received: [{id, balance, payment}]}) —\n  receive a balance record from a specific Payment/payer.\n  Use this for precise balance targeting (advanced — usually after querying\n  the object's received history via query_received).\n  Example: receive: {token_type: '0x2::sui::SUI', balance: 1000000, received: [{id: '0xrec1', balance: 1000000, payment: '0xpay1'}]}\nANTI-PATTERN: do NOT wrap in {result: ...} — pass the value directly."
         }
       },
       "required": [
@@ -4854,7 +4943,7 @@
                   "type": "null"
                 }
               ],
-              "description": "Voting deadline as Unix timestamp in MILLISECONDS (ms). MUST be in the future (recommended: now + at least 86400000 ms = 24 hours). Set to null to remove the deadline. COMMON MISTAKE: using seconds instead of milliseconds (multiply by 1000). Example: Date.now() + 259200000 for 3 days from now."
+              "description": "Voting deadline as Unix timestamp in MILLISECONDS (ms). SEMANTICS OF SPECIAL VALUES: 0 = deadline already passed → voting is IMPOSSIBLE and the arbitrator may deliver the verdict immediately (direct-verdict flow); null = open-ended voting with no deadline (verdict allowed anytime); a future timestamp = normal voting window (recommended: now + at least 86400000 ms = 24 hours). COMMON MISTAKE: using seconds instead of milliseconds (multiply by 1000). Example: Date.now() + 259200000 for 3 days from now."
             }
           },
           "required": [
@@ -4875,7 +4964,7 @@
                 "number",
                 "null"
               ],
-              "description": "New voting deadline as Unix timestamp in MILLISECONDS (ms). MUST be in the future (recommended: now + at least 86400000 ms = 24 hours). Set to null to remove the deadline. COMMON MISTAKE: using seconds instead of milliseconds (multiply by 1000). Example: Date.now() + 259200000 for 3 days from now."
+              "description": "New voting deadline as Unix timestamp in MILLISECONDS (ms). SEMANTICS OF SPECIAL VALUES: 0 = deadline already passed → voting is IMPOSSIBLE and the arbitrator may deliver the verdict immediately; null = open-ended voting with no deadline (verdict allowed anytime); a future timestamp = normal voting window (recommended: now + at least 86400000 ms = 24 hours). COMMON MISTAKE: using seconds instead of milliseconds (multiply by 1000). Example: Date.now() + 259200000 for 3 days from now."
             }
           },
           "required": [
@@ -4897,11 +4986,12 @@
                 "type": "integer",
                 "minimum": 0,
                 "maximum": 255
-              }
+              },
+              "description": "Proposition INDICES (0-based, u8) the voter agrees with — e.g. [0] votes for the first proposition. Re-voting REPLACES the voter's previous vote (old weight removed, new applied). Out-of-range index aborts with E_PROPOSITION_NOT_FOUND."
             },
             "voting_guard": {
               "$ref": "#/definitions/data_arbitration/properties/confirm/properties/arb",
-              "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)."
+              "description": "Optional Voting Guard for weighted voting. THREE PATHS are supported by the SDK and Move contract: (1) voting_guard PROVIDED → vote_with_voting_guard (Guard verifies voter + determines vote weight via VoteWeight config); (2) voting_guard OMITTED but other guards trigger passport creation (e.g. env.permission_guard or usage_guard) → vote_with_passport (permission-only via passport); (3) voting_guard OMITTED and no passport context → vote (plain permission-only vote, no Guard). The Guard (when provided) must be in the Arbitration's voting_guard list."
             }
           },
           "required": [
@@ -5258,7 +5348,7 @@
         "object"
       ],
       "additionalProperties": false,
-      "description": "On-chain Arbitration operations. USAGE: (1) CREATE NEW: Set 'object' field with OBJECT format {name, type_parameter, permission, ...} to create an Arbitration. 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."
+      "description": "On-chain Arbitration operations. USAGE: (1) CREATE NEW: Set 'object' field with OBJECT format {name, type_parameter, permission, ...} to create an Arbitration. 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. ⚠️ PERMISSION RULE (contract-enforced, service.move arbitration_add_imp): the Arbitration's permission MUST be DIFFERENT from the permission of any Service it will be bound to — binding an Arbitration that SHARES the Service's Permission aborts with E_ARBITRATION_PERMISSION_CONFLICT (error 33). Always create a DEDICATED Permission object for each Arbitration. (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."
     },
     "data_contact": {
       "type": "object",
@@ -6839,7 +6929,7 @@
             },
             "alloc_by_guard": {
               "$ref": "#/definitions/data_allocation/anyOf/0/properties/allocators/properties/allocators/items/properties/sharing/items/properties/who/anyOf/1/properties/Entity/properties/name_or_address",
-              "description": "Verify the specified Guard and execute the corresponding fund allocation"
+              "description": "Verify the specified Guard and execute the corresponding fund allocation. POST-ALLOCATION CLAIM (required step): each recipient receives a CoinWrapper object (NOT spendable coins). Recipient address resolution (allocation.move): Entity recipients receive it at the Entity's address; Signer recipients receive it at the transaction sender's address; GuardIdentifier n recipients receive it at the ADDRESS SUBMITTED for identifier n in this call's submission (resolved via passport::submission_get) — conventionally the Order OBJECT address (escrow pattern), in which case the order owner claims it via operation_type='order' {object:'<order_id>', receive:'recently'}. Claim paths by holder: EOA wallet → operation_type='payment' RECEIVE mode {object:'<coinwrapper_id>', receive:true, type_parameter:'0x2::wow::WOW'}; Order object → order receive; Treasury object → treasury receive. Find pending CoinWrappers via query_toolkit query_type='onchain_received'. Verify the distribution via the immutable Payment object created by this call (allocation.payment array)."
             }
           },
           "required": [
@@ -8595,6 +8685,42 @@
               "additionalProperties": false,
               "description": "PUBLIC: Clear ALL tags from specified on-chain identity marks."
             },
+            {
+              "type": "object",
+              "properties": {
+                "op": {
+                  "type": "string",
+                  "const": "like"
+                },
+                "address": {
+                  "$ref": "#/definitions/data_personal/properties/mark/anyOf/0/properties/data/items/properties/address"
+                }
+              },
+              "required": [
+                "op",
+                "address"
+              ],
+              "additionalProperties": false,
+              "description": "PUBLIC REPUTATION VOTE: Like an address (0x...) or LocalMark name. Goes through registrar::like — toggles off if already liked, auto-flips an existing dislike, and increments the target's PUBLIC aggregate like count (queryable via query personal / Guard entity_voted_record). Do NOT emulate with mark.add tags:['like'] — manual tags stay private in your Resource and never affect the aggregate count."
+            },
+            {
+              "type": "object",
+              "properties": {
+                "op": {
+                  "type": "string",
+                  "const": "dislike"
+                },
+                "address": {
+                  "$ref": "#/definitions/data_personal/properties/mark/anyOf/0/properties/data/items/properties/address"
+                }
+              },
+              "required": [
+                "op",
+                "address"
+              ],
+              "additionalProperties": false,
+              "description": "PUBLIC REPUTATION VOTE: Dislike an address (0x...) or LocalMark name. Goes through registrar::dislike — toggles off if already disliked, auto-flips an existing like, and increments the target's PUBLIC aggregate dislike count. Same manual-tag caveat as 'like'."
+            },
             {
               "type": "object",
               "properties": {
@@ -9317,7 +9443,8 @@
                 "unhold",
                 "adminUnhold"
               ],
-              "description": "Operation type on the forward (CANONICAL form — prefer this): 'next' = advance the forward (accomplish); 'hold' = set hold to block the forward; 'unhold' = self-unhold, release own hold (no 224 permission needed); 'adminUnhold' = force-release hold via 224 permission (PROGRESS_UNHOLD). LEGACY ALIAS: `hold: boolean` is auto-converted to `op` — `hold:true`→`op:'hold'`, `hold:false`→`op:'next'`. New code should use `op` directly."
+              "default": "next",
+              "description": "Operation type on the forward (CANONICAL form — prefer this). DEFAULT: 'next' when omitted. 'next' = advance the forward (accomplish); 'hold' = set hold to block the forward; 'unhold' = self-unhold, release own hold (no 224 permission needed); 'adminUnhold' = force-release hold via 224 permission (PROGRESS_UNHOLD). LEGACY ALIAS: `hold: boolean` is auto-converted to `op` — `hold:true`→`op:'hold'`, `hold:false`→`op:'next'`. New code should use `op` directly."
             },
             "message": {
               "type": "string",
@@ -9325,8 +9452,7 @@
             }
           },
           "required": [
-            "operation",
-            "op"
+            "operation"
           ],
           "additionalProperties": false,
           "description": "Advance order process"
@@ -10073,6 +10199,7 @@
             },
             "schema_strict_mode": {
               "type": "boolean",
+              "default": false,
               "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
             },
             "dry_run": {
@@ -10304,6 +10431,7 @@
             },
             "schema_strict_mode": {
               "type": "boolean",
+              "default": false,
               "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
             },
             "dry_run": {

package/dist/schemas/onchain_operations_allocation.schema.json

@@ -361,7 +361,7 @@
             },
             "alloc_by_guard": {
               "$ref": "#/definitions/data/anyOf/0/properties/allocators/properties/allocators/items/properties/sharing/items/properties/who/anyOf/1/properties/Entity/properties/name_or_address",
-              "description": "Verify the specified Guard and execute the corresponding fund allocation"
+              "description": "Verify the specified Guard and execute the corresponding fund allocation. POST-ALLOCATION CLAIM (required step): each recipient receives a CoinWrapper object (NOT spendable coins). Recipient address resolution (allocation.move): Entity recipients receive it at the Entity's address; Signer recipients receive it at the transaction sender's address; GuardIdentifier n recipients receive it at the ADDRESS SUBMITTED for identifier n in this call's submission (resolved via passport::submission_get) — conventionally the Order OBJECT address (escrow pattern), in which case the order owner claims it via operation_type='order' {object:'<order_id>', receive:'recently'}. Claim paths by holder: EOA wallet → operation_type='payment' RECEIVE mode {object:'<coinwrapper_id>', receive:true, type_parameter:'0x2::wow::WOW'}; Order object → order receive; Treasury object → treasury receive. Find pending CoinWrappers via query_toolkit query_type='onchain_received'. Verify the distribution via the immutable Payment object created by this call (allocation.payment array)."
             }
           },
           "required": [
@@ -426,6 +426,7 @@
         },
         "schema_strict_mode": {
           "type": "boolean",
+          "default": false,
           "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
         },
         "dry_run": {

package/dist/schemas/onchain_operations_arbitration.schema.json

@@ -215,7 +215,7 @@
                   "type": "null"
                 }
               ],
-              "description": "Voting deadline as Unix timestamp in MILLISECONDS (ms). MUST be in the future (recommended: now + at least 86400000 ms = 24 hours). Set to null to remove the deadline. COMMON MISTAKE: using seconds instead of milliseconds (multiply by 1000). Example: Date.now() + 259200000 for 3 days from now."
+              "description": "Voting deadline as Unix timestamp in MILLISECONDS (ms). SEMANTICS OF SPECIAL VALUES: 0 = deadline already passed → voting is IMPOSSIBLE and the arbitrator may deliver the verdict immediately (direct-verdict flow); null = open-ended voting with no deadline (verdict allowed anytime); a future timestamp = normal voting window (recommended: now + at least 86400000 ms = 24 hours). COMMON MISTAKE: using seconds instead of milliseconds (multiply by 1000). Example: Date.now() + 259200000 for 3 days from now."
             }
           },
           "required": [
@@ -236,7 +236,7 @@
                 "number",
                 "null"
               ],
-              "description": "New voting deadline as Unix timestamp in MILLISECONDS (ms). MUST be in the future (recommended: now + at least 86400000 ms = 24 hours). Set to null to remove the deadline. COMMON MISTAKE: using seconds instead of milliseconds (multiply by 1000). Example: Date.now() + 259200000 for 3 days from now."
+              "description": "New voting deadline as Unix timestamp in MILLISECONDS (ms). SEMANTICS OF SPECIAL VALUES: 0 = deadline already passed → voting is IMPOSSIBLE and the arbitrator may deliver the verdict immediately; null = open-ended voting with no deadline (verdict allowed anytime); a future timestamp = normal voting window (recommended: now + at least 86400000 ms = 24 hours). COMMON MISTAKE: using seconds instead of milliseconds (multiply by 1000). Example: Date.now() + 259200000 for 3 days from now."
             }
           },
           "required": [
@@ -258,11 +258,12 @@
                 "type": "integer",
                 "minimum": 0,
                 "maximum": 255
-              }
+              },
+              "description": "Proposition INDICES (0-based, u8) the voter agrees with — e.g. [0] votes for the first proposition. Re-voting REPLACES the voter's previous vote (old weight removed, new applied). Out-of-range index aborts with E_PROPOSITION_NOT_FOUND."
             },
             "voting_guard": {
               "$ref": "#/definitions/data/properties/confirm/properties/arb",
-              "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)."
+              "description": "Optional Voting Guard for weighted voting. THREE PATHS are supported by the SDK and Move contract: (1) voting_guard PROVIDED → vote_with_voting_guard (Guard verifies voter + determines vote weight via VoteWeight config); (2) voting_guard OMITTED but other guards trigger passport creation (e.g. env.permission_guard or usage_guard) → vote_with_passport (permission-only via passport); (3) voting_guard OMITTED and no passport context → vote (plain permission-only vote, no Guard). The Guard (when provided) must be in the Arbitration's voting_guard list."
             }
           },
           "required": [
@@ -619,7 +620,7 @@
         "object"
       ],
       "additionalProperties": false,
-      "description": "On-chain Arbitration operations. USAGE: (1) CREATE NEW: Set 'object' field with OBJECT format {name, type_parameter, permission, ...} to create an Arbitration. 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."
+      "description": "On-chain Arbitration operations. USAGE: (1) CREATE NEW: Set 'object' field with OBJECT format {name, type_parameter, permission, ...} to create an Arbitration. 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. ⚠️ PERMISSION RULE (contract-enforced, service.move arbitration_add_imp): the Arbitration's permission MUST be DIFFERENT from the permission of any Service it will be bound to — binding an Arbitration that SHARES the Service's Permission aborts with E_ARBITRATION_PERMISSION_CONFLICT (error 33). Always create a DEDICATED Permission object for each Arbitration. (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."
     },
     "env": {
       "type": "object",
@@ -674,6 +675,7 @@
         },
         "schema_strict_mode": {
           "type": "boolean",
+          "default": false,
           "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
         },
         "dry_run": {

package/dist/schemas/onchain_operations_contact.schema.json

@@ -359,6 +359,7 @@
         },
         "schema_strict_mode": {
           "type": "boolean",
+          "default": false,
           "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
         },
         "dry_run": {

package/dist/schemas/onchain_operations_demand.schema.json

@@ -490,6 +490,7 @@
         },
         "schema_strict_mode": {
           "type": "boolean",
+          "default": false,
           "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
         },
         "dry_run": {

package/dist/schemas/onchain_operations_gen_passport.schema.json

@@ -587,6 +587,7 @@
         },
         "schema_strict_mode": {
           "type": "boolean",
+          "default": false,
           "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
         },
         "dry_run": {
@@ -1186,6 +1187,7 @@
             },
             "schema_strict_mode": {
               "type": "boolean",
+              "default": false,
               "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
             },
             "dry_run": {

package/dist/schemas/onchain_operations_gen_proof.schema.json

@@ -120,6 +120,7 @@
         },
         "schema_strict_mode": {
           "type": "boolean",
+          "default": false,
           "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
         },
         "dry_run": {
@@ -256,6 +257,7 @@
             },
             "schema_strict_mode": {
               "type": "boolean",
+              "default": false,
               "description": "When true, schema incompatibility returns an error instead of a warning. Default: false (warn mode)."
             },
             "dry_run": {