@wowok/agent-mcp 3.2.6 → 3.2.9

package/dist/schemas/onchain_operations.output.json

@@ -3592,6 +3592,50 @@
                 "current_node"
               ],
               "additionalProperties": false
+            },
+            "review_steps": {
+              "description": "Composite review submission report: the structured-reputation repository write (+ optional reward claim) chained after a successful progress forward via the data.review block, each reusing the forward's passport submission. Fail-isolated — a failed step never rolled back the forward. Relay failed steps to the user with the retry path (dedicated repository/reward tools).",
+              "type": "array",
+              "items": {
+                "type": "object",
+                "properties": {
+                  "step": {
+                    "type": "string",
+                    "enum": [
+                      "repository_write",
+                      "reward_claim"
+                    ],
+                    "description": "Which chained review step this report describes. repository_write = structured reputation record (rating/tags) into the caller-named Repository; reward_claim = incentive claim on the caller-named Reward."
+                  },
+                  "status": {
+                    "type": "string",
+                    "enum": [
+                      "success",
+                      "failed"
+                    ],
+                    "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback)."
+                  },
+                  "detail": {
+                    "type": "string",
+                    "description": "On success: what was written/claimed (payload summary). On failure: what the step attempted."
+                  },
+                  "digest": {
+                    "description": "Transaction digest when the step succeeded.",
+                    "type": "string"
+                  },
+                  "error": {
+                    "description": "Error message when the step failed. Retry via the dedicated repository/reward tools with the same submission values.",
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "step",
+                  "status",
+                  "detail"
+                ],
+                "additionalProperties": false,
+                "description": "One fail-isolated chained step of the progress composite review submission (REVIEW component, data.review block)."
+              }
             }
           },
           "required": [
@@ -3721,6 +3765,7 @@
                               "description": "Whether this table item's value is submitted dynamically at Guard trigger time (alloc_by_guard call). \n\ntrue = value is submitted by the caller when triggering the Guard. Use for runtime-context-dependent values like order address, user address. The 'value' field is ignored when b_submission=true; the caller must provide it via submissions[]. \n\nfalse = value is static, set at Guard creation time. Use for values known when the Guard is created: expected node names, expected merchant address, expected service address. The 'value' field must be populated and will be stored on-chain permanently. \n\nRule of thumb: if the value is the SAME for all future Guard triggers, use false. If the value DIFFERS per trigger (e.g., which order to release funds for), use true."
                             },
                             "value_type": {
+                              "description": "Type of the value stored in `value`. One of: Bool(0), Address(1), String(2), U8(3), U16(4), U32(5), U64(6), U128(7), U256(8), VecBool(9), VecAddress(10), VecString(11), VecU8(12), VecU16(13), VecU32(14), VecU64(15), VecU128(16), VecU256(17), VecVecU8(18). When value_type=Address (1), the `value` field accepts a hex address string, a LocalMark name, or an AccountOrMark_Address object — see `value` field description for details.",
                               "anyOf": [
                                 {
                                   "type": "number",
@@ -4007,11 +4052,10 @@
                                   "const": "vecvecu8",
                                   "description": "vecvecu8"
                                 }
-                              ],
-                              "description": "Type of the value stored in `value`. One of: Bool(0), Address(1), String(2), U8(3), U16(4), U32(5), U64(6), U128(7), U256(8), VecBool(9), VecAddress(10), VecString(11), VecU8(12), VecU16(13), VecU32(14), VecU64(15), VecU128(16), VecU256(17), VecVecU8(18). When value_type=Address (1), the `value` field accepts a hex address string, a LocalMark name, or an AccountOrMark_Address object — see `value` field description for details."
+                              ]
                             },
                             "value": {
-                              "description": "The actual value data. Format depends on `value_type`:\n• Bool: true/false (boolean)\n• Address (CRITICAL — string 'Address' is NOT a placeholder): a hex address (e.g. '0x1234...'), a LocalMark name (e.g. 'my-service' — resolved to address at evaluation time), an AccountOrMark_Address object (e.g. {name_or_address:'my-service'}), or system shorthand ('0xaaa' = EntityLinker, '0xaab' = EntityRegistrar). The literal string 'Address' itself is INVALID — it would be treated as a non-existent LocalMark name and fail. Example: value='0x2::wow::WOW<address>' or value='my-permission'.\n• String: any string\n• U8/U16/U32/U64/U128/U256: number or numeric string (e.g. 42 or '42')\n• Vec* types: arrays of the corresponding element type\nREQUIRED when b_submission=false. OPTIONAL when b_submission=true (value is supplied at evaluation time by user submission).",
+                              "description": "The actual value data. Format depends on `value_type`:\nTYPE-CLASS SPLIT (F03): scalar value_types (Bool/Address/String/U8..U256) take ONE scalar value (boolean/address string/name/string/number); Vec* value_types (VecBool/VecAddress/VecString/VecU8..VecU256) take a REAL JSON ARRAY of elements — a string (even a Python-repr-looking \"[a, b]\") fails serialization with 'value_type=10 (array) requires a array value'. The historical 'static values must be strings' rule applied to SCALARS only.\n• Bool: true/false (boolean)\n• Address (CRITICAL — string 'Address' is NOT a placeholder): a hex address (e.g. '0x1234...'), a LocalMark name (e.g. 'my-service' — resolved to address at evaluation time), an AccountOrMark_Address object (e.g. {name_or_address:'my-service'}), or system shorthand ('0xaaa' = EntityLinker, '0xaab' = EntityRegistrar). The literal string 'Address' itself is INVALID — it would be treated as a non-existent LocalMark name and fail. Example: value='0x2::wow::WOW<address>' or value='my-permission'.\n• String: any string\n• U8/U16/U32/U64/U128/U256: number or numeric string (e.g. 42 or '42')\n• Vec* types: arrays of the corresponding element type\nPROTOCOL SLOT 254 (once, b_submission Address): the submitted value MUST be the ORDER address bound to the operation (payment_info.for_object) — NEVER the Progress/Machine/Arb object the call is advancing. The chain asserts submission(254) == the order address; a Progress address fails the task binding and the forward aborts.\nREQUIRED when b_submission=false. OPTIONAL when b_submission=true (value is supplied at evaluation time by user submission).",
                               "anyOf": [
                                 {
                                   "type": "boolean"
@@ -4170,7 +4214,7 @@
                           "additionalProperties": false,
                           "description": "Guard table item (QUERY/OUTPUT form — includes auto-derived object_type field)"
                         },
-                        "description": "User-submitted data matching the Guard's required fields. Relation: structure must match the Guard table's column definitions. Example: [{field:'delivery_proof', value:'Qm...'}]"
+                        "description": "User-submitted data matching the Guard's required fields. Relation: structure must match the Guard table's column definitions. Example: [{field:'delivery_proof', value:'Qm...'}] PROTOCOL SLOT 254: when the Guard table has identifier 254, submit the ORDER address bound to the operation (payment_info.for_object) — never the Progress/Machine object being advanced."
                       }
                     },
                     "required": [
@@ -4180,7 +4224,7 @@
                     "additionalProperties": false,
                     "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
                   },
-                  "description": "User-submitted data for each Guard. Relation: one entry per Guard in the guard array; fill submission fields and resubmit via call_with_submission. PLACEMENT: this `submission` field is at the SAME level as `data` and `env` in the operation input — NOT inside `data.data`. Example structure: {tool:'onchain_operations', data:{operation_type:'order', data:{object:'my_order', progress:{...}}}, submission:{type:'submission', guard:[...], submission:[...]}}"
+                  "description": "User-submitted data for each Guard. Relation: one entry per Guard in the guard array; fill submission fields and resubmit via call_with_submission. SLOT COMPLETENESS (T8 az3-mn-261013): the submission array must cover EVERY b_submission slot in the Guard's table, not just one — a Guard whose table has multiple b_submission entries (e.g. slot 0 + slot 254) aborts on-chain with 'Submission ID not found' (abort 11) when any b_submission slot has no matching entry. Check the Guard's table (each entry with b_submission needs its identifier filled) and include ALL of them. PLACEMENT: this `submission` field is at the SAME level as `data` and `env` in the operation input — NOT inside `data.data`. Example structure: {tool:'onchain_operations', data:{operation_type:'order', data:{object:'my_order', progress:{...}}}, submission:{type:'submission', guard:[...], submission:[...]}}"
                 }
               },
               "required": [
@@ -5577,6 +5621,50 @@
                 "current_node"
               ],
               "additionalProperties": false
+            },
+            "review_steps": {
+              "description": "Composite review submission report: the structured-reputation repository write (+ optional reward claim) chained after a successful progress forward via the data.review block, each reusing the forward's passport submission. Fail-isolated — a failed step never rolled back the forward. Relay failed steps to the user with the retry path (dedicated repository/reward tools).",
+              "type": "array",
+              "items": {
+                "type": "object",
+                "properties": {
+                  "step": {
+                    "type": "string",
+                    "enum": [
+                      "repository_write",
+                      "reward_claim"
+                    ],
+                    "description": "Which chained review step this report describes. repository_write = structured reputation record (rating/tags) into the caller-named Repository; reward_claim = incentive claim on the caller-named Reward."
+                  },
+                  "status": {
+                    "type": "string",
+                    "enum": [
+                      "success",
+                      "failed"
+                    ],
+                    "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback)."
+                  },
+                  "detail": {
+                    "type": "string",
+                    "description": "On success: what was written/claimed (payload summary). On failure: what the step attempted."
+                  },
+                  "digest": {
+                    "description": "Transaction digest when the step succeeded.",
+                    "type": "string"
+                  },
+                  "error": {
+                    "description": "Error message when the step failed. Retry via the dedicated repository/reward tools with the same submission values.",
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "step",
+                  "status",
+                  "detail"
+                ],
+                "additionalProperties": false,
+                "description": "One fail-isolated chained step of the progress composite review submission (REVIEW component, data.review block)."
+              }
             }
           },
           "required": [
@@ -5679,12 +5767,15 @@
                 "network_error",
                 "rate_limit",
                 "gas_exceeded",
+                "insufficient_gas",
                 "bcs_error",
                 "signature_error",
                 "config_error",
                 "wip_verification_failed",
                 "wip_storage_unavailable",
                 "submission_unknown",
+                "move_abort_unmapped",
+                "missing_data",
                 "unknown"
               ]
             },
@@ -6973,6 +7064,50 @@
                 "current_node"
               ],
               "additionalProperties": false
+            },
+            "review_steps": {
+              "description": "Composite review submission report: the structured-reputation repository write (+ optional reward claim) chained after a successful progress forward via the data.review block, each reusing the forward's passport submission. Fail-isolated — a failed step never rolled back the forward. Relay failed steps to the user with the retry path (dedicated repository/reward tools).",
+              "type": "array",
+              "items": {
+                "type": "object",
+                "properties": {
+                  "step": {
+                    "type": "string",
+                    "enum": [
+                      "repository_write",
+                      "reward_claim"
+                    ],
+                    "description": "Which chained review step this report describes. repository_write = structured reputation record (rating/tags) into the caller-named Repository; reward_claim = incentive claim on the caller-named Reward."
+                  },
+                  "status": {
+                    "type": "string",
+                    "enum": [
+                      "success",
+                      "failed"
+                    ],
+                    "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback)."
+                  },
+                  "detail": {
+                    "type": "string",
+                    "description": "On success: what was written/claimed (payload summary). On failure: what the step attempted."
+                  },
+                  "digest": {
+                    "description": "Transaction digest when the step succeeded.",
+                    "type": "string"
+                  },
+                  "error": {
+                    "description": "Error message when the step failed. Retry via the dedicated repository/reward tools with the same submission values.",
+                    "type": "string"
+                  }
+                },
+                "required": [
+                  "step",
+                  "status",
+                  "detail"
+                ],
+                "additionalProperties": false,
+                "description": "One fail-isolated chained step of the progress composite review submission (REVIEW component, data.review block)."
+              }
             }
           },
           "required": [