@wowok/agent-mcp 3.3.2 → 3.3.5

package/dist/schemas/local_cache_operation.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://wowok.net/schemas/local_cache_operation.json",
   "title": "SDK Read Cache Operations",
-  "description": "LOCAL ONLY, NEVER ON-CHAIN: inspect and clear this device's WoWok SDK read cache. Use {status: {op:'status'}} to diagnose a stale cache, {refresh_chain_scope: {op:'refresh_chain_scope'}} after the chain node was reset or restarted (this alone fixes 'object 0x… version 0x… is unavailable'), {clear_prefix: {...}} to drop one cache family such as on-chain objects, or {clear: {op:'clear'}} to drop everything. Does NOT touch accounts, marks, info or history — those hold user data and have their own tools.",
+  "description": "LOCAL ONLY, NEVER ON-CHAIN: inspect and clear this device's WoWok SDK read cache. Use {status: {op:'status'}} to diagnose a stale cache, {refresh_chain_scope: {op:'refresh_chain_scope'}} after the chain node was reset or restarted (this alone fixes 'object 0x… version 0x… is unavailable'), {clear_prefix: {...}} to drop one cache family such as on-chain objects, {clear: {op:'clear'}} to drop everything, or {clear_inflight: {op:'clear_inflight'}} to release parked in-flight operation markers. Does NOT touch accounts, marks, info or history — those hold user data and have their own tools.",
   "type": "object",
   "properties": {
     "status": {
@@ -95,6 +95,21 @@
         "op"
       ],
       "additionalProperties": false
+    },
+    "clear_inflight": {
+      "description": "F-M10 (gfm F-25): drop EVERY in-flight operation marker and landed tombstone held by this process. In-flight markers park the signature of a fund-moving call whose outcome was never observed (transport drop after submit) and hold an identical resend for a 120s verify-first window; if a stale marker is blocking a deliberate re-run past on-chain verification, this clears it immediately instead of waiting out the window. Device-local only — never on-chain.",
+      "type": "object",
+      "properties": {
+        "op": {
+          "type": "string",
+          "const": "clear_inflight",
+          "description": "Operation type: clear in-flight operation markers"
+        }
+      },
+      "required": [
+        "op"
+      ],
+      "additionalProperties": false
     }
   },
   "additionalProperties": false

package/dist/schemas/local_history_operation.output.json

@@ -168,6 +168,7 @@
                 "guard_rejected",
                 "state_conflict",
                 "insufficient_balance",
+                "pool_shortage",
                 "transaction_expired",
                 "stock_exhausted",
                 "sale_suspended",
@@ -189,6 +190,7 @@
                 "submission_unknown",
                 "move_abort_unmapped",
                 "missing_data",
+                "state_not_visible",
                 "unknown"
               ]
             },
@@ -893,7 +895,7 @@
               }
             },
             "available_queries": {
-              "description": "Available query instructions for the current context (subset of 375 GUARDQUERY entries)",
+              "description": "Available query instructions for the current context (subset of the GUARDQUERY catalog)",
               "type": "array",
               "items": {
                 "type": "object",
@@ -928,7 +930,7 @@
                   "returnType"
                 ],
                 "additionalProperties": false,
-                "description": "A Guard query instruction available for the current context (subset of GUARDQUERY 375 entries)."
+                "description": "A Guard query instruction available for the current context (subset of the GUARDQUERY catalog)."
               }
             },
             "risk_warnings": {
@@ -1473,7 +1475,7 @@
           "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).",
+          "description": "Composite review submission report (F01 ordering): the structured-reputation repository write runs BEFORE the progress forward (its review-edge guard anchors the PRE node), the optional reward claim runs AFTER — one passport submission, fail-isolated steps. A failed step never rolled back the forward. Relay failed/unknown steps to the user with next_action (probe before retry; dedicated repository/reward tools).",
           "type": "array",
           "items": {
             "type": "object",
@@ -1490,20 +1492,25 @@
                 "type": "string",
                 "enum": [
                   "success",
-                  "failed"
+                  "failed",
+                  "unknown"
                 ],
-                "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback)."
+                "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback). 'unknown' (esln-261023 E-6) = the submission outcome could NOT be observed (transport drop after submit) — the step MAY have landed; this is NOT a confirmed failure. Follow next_action (probe) before any retry; a blind retry double-writes."
               },
               "detail": {
                 "type": "string",
-                "description": "On success: what was written/claimed (payload summary). On failure: what the step attempted."
+                "description": "On success: what was written/claimed (payload summary). On failure or unknown: what the step attempted."
               },
               "digest": {
-                "description": "Transaction digest when the step succeeded.",
+                "description": "Transaction digest: on success the landing digest; on an unknown outcome the transport-reported pre-submit digest — verify it via onchain_transaction (executed → landed, adopt; failure → final; unresolvable → nothing landed).",
                 "type": "string"
               },
               "error": {
-                "description": "Error message when the step failed. Retry via the dedicated repository/reward tools with the same submission values.",
+                "description": "Error message when the step failed or stayed unknown. Retry via the dedicated repository/reward tools with the same submission values — only after a probe confirms nothing landed.",
+                "type": "string"
+              },
+              "next_action": {
+                "description": "Present on failed/unknown steps: the concrete recovery move (the probe to run, the safe-retry condition, or the two-phase split).",
                 "type": "string"
               }
             },

package/dist/schemas/local_info_operation.output.json

@@ -54,6 +54,7 @@
                 "guard_rejected",
                 "state_conflict",
                 "insufficient_balance",
+                "pool_shortage",
                 "transaction_expired",
                 "stock_exhausted",
                 "sale_suspended",
@@ -75,6 +76,7 @@
                 "submission_unknown",
                 "move_abort_unmapped",
                 "missing_data",
+                "state_not_visible",
                 "unknown"
               ]
             },
@@ -779,7 +781,7 @@
               }
             },
             "available_queries": {
-              "description": "Available query instructions for the current context (subset of 375 GUARDQUERY entries)",
+              "description": "Available query instructions for the current context (subset of the GUARDQUERY catalog)",
               "type": "array",
               "items": {
                 "type": "object",
@@ -814,7 +816,7 @@
                   "returnType"
                 ],
                 "additionalProperties": false,
-                "description": "A Guard query instruction available for the current context (subset of GUARDQUERY 375 entries)."
+                "description": "A Guard query instruction available for the current context (subset of the GUARDQUERY catalog)."
               }
             },
             "risk_warnings": {
@@ -1359,7 +1361,7 @@
           "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).",
+          "description": "Composite review submission report (F01 ordering): the structured-reputation repository write runs BEFORE the progress forward (its review-edge guard anchors the PRE node), the optional reward claim runs AFTER — one passport submission, fail-isolated steps. A failed step never rolled back the forward. Relay failed/unknown steps to the user with next_action (probe before retry; dedicated repository/reward tools).",
           "type": "array",
           "items": {
             "type": "object",
@@ -1376,20 +1378,25 @@
                 "type": "string",
                 "enum": [
                   "success",
-                  "failed"
+                  "failed",
+                  "unknown"
                 ],
-                "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback)."
+                "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback). 'unknown' (esln-261023 E-6) = the submission outcome could NOT be observed (transport drop after submit) — the step MAY have landed; this is NOT a confirmed failure. Follow next_action (probe) before any retry; a blind retry double-writes."
               },
               "detail": {
                 "type": "string",
-                "description": "On success: what was written/claimed (payload summary). On failure: what the step attempted."
+                "description": "On success: what was written/claimed (payload summary). On failure or unknown: what the step attempted."
               },
               "digest": {
-                "description": "Transaction digest when the step succeeded.",
+                "description": "Transaction digest: on success the landing digest; on an unknown outcome the transport-reported pre-submit digest — verify it via onchain_transaction (executed → landed, adopt; failure → final; unresolvable → nothing landed).",
                 "type": "string"
               },
               "error": {
-                "description": "Error message when the step failed. Retry via the dedicated repository/reward tools with the same submission values.",
+                "description": "Error message when the step failed or stayed unknown. Retry via the dedicated repository/reward tools with the same submission values — only after a probe confirms nothing landed.",
+                "type": "string"
+              },
+              "next_action": {
+                "description": "Present on failed/unknown steps: the concrete recovery move (the probe to run, the safe-retry condition, or the two-phase split).",
                 "type": "string"
               }
             },

package/dist/schemas/local_info_operation.schema.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "$id": "https://wowok.net/schemas/local_info_operation.json",
   "title": "Local Info Operations",
-  "description": "Local info operations. Exactly one operation type (add/remove/reset/clear) must be specified as a NESTED field. Example: {add: {op:'add', data:[...]}} — NOT flat {op:'add', data:[...]}.",
+  "description": "Local info operations. Exactly one operation type (add/remove/reset/clear) must be specified as a NESTED field. Example: {add: {op:'add', data:[...]}} — NOT flat {op:'add', data:[...]}. Optional top-level 'account' scopes the operation to one account's info partition (ESD-A5).",
   "type": "object",
   "properties": {
     "add": {
@@ -130,6 +130,10 @@
         "op"
       ],
       "additionalProperties": false
+    },
+    "account": {
+      "description": "Account partition for this operation. Local info is isolated per account; omit it to target the process default account's partition. Accepts an account name or address; a ref that does not resolve to a registered account FAILS the call (no silent fallback to the default partition).",
+      "type": "string"
     }
   },
   "additionalProperties": false

package/dist/schemas/local_mark_operation.output.json

@@ -146,6 +146,7 @@
                 "guard_rejected",
                 "state_conflict",
                 "insufficient_balance",
+                "pool_shortage",
                 "transaction_expired",
                 "stock_exhausted",
                 "sale_suspended",
@@ -167,6 +168,7 @@
                 "submission_unknown",
                 "move_abort_unmapped",
                 "missing_data",
+                "state_not_visible",
                 "unknown"
               ]
             },
@@ -871,7 +873,7 @@
               }
             },
             "available_queries": {
-              "description": "Available query instructions for the current context (subset of 375 GUARDQUERY entries)",
+              "description": "Available query instructions for the current context (subset of the GUARDQUERY catalog)",
               "type": "array",
               "items": {
                 "type": "object",
@@ -906,7 +908,7 @@
                   "returnType"
                 ],
                 "additionalProperties": false,
-                "description": "A Guard query instruction available for the current context (subset of GUARDQUERY 375 entries)."
+                "description": "A Guard query instruction available for the current context (subset of the GUARDQUERY catalog)."
               }
             },
             "risk_warnings": {
@@ -1451,7 +1453,7 @@
           "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).",
+          "description": "Composite review submission report (F01 ordering): the structured-reputation repository write runs BEFORE the progress forward (its review-edge guard anchors the PRE node), the optional reward claim runs AFTER — one passport submission, fail-isolated steps. A failed step never rolled back the forward. Relay failed/unknown steps to the user with next_action (probe before retry; dedicated repository/reward tools).",
           "type": "array",
           "items": {
             "type": "object",
@@ -1468,20 +1470,25 @@
                 "type": "string",
                 "enum": [
                   "success",
-                  "failed"
+                  "failed",
+                  "unknown"
                 ],
-                "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback)."
+                "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback). 'unknown' (esln-261023 E-6) = the submission outcome could NOT be observed (transport drop after submit) — the step MAY have landed; this is NOT a confirmed failure. Follow next_action (probe) before any retry; a blind retry double-writes."
               },
               "detail": {
                 "type": "string",
-                "description": "On success: what was written/claimed (payload summary). On failure: what the step attempted."
+                "description": "On success: what was written/claimed (payload summary). On failure or unknown: what the step attempted."
               },
               "digest": {
-                "description": "Transaction digest when the step succeeded.",
+                "description": "Transaction digest: on success the landing digest; on an unknown outcome the transport-reported pre-submit digest — verify it via onchain_transaction (executed → landed, adopt; failure → final; unresolvable → nothing landed).",
                 "type": "string"
               },
               "error": {
-                "description": "Error message when the step failed. Retry via the dedicated repository/reward tools with the same submission values.",
+                "description": "Error message when the step failed or stayed unknown. Retry via the dedicated repository/reward tools with the same submission values — only after a probe confirms nothing landed.",
+                "type": "string"
+              },
+              "next_action": {
+                "description": "Present on failed/unknown steps: the concrete recovery move (the probe to run, the safe-retry condition, or the two-phase split).",
                 "type": "string"
               }
             },

package/dist/schemas/messenger_operation.output.json

@@ -3334,7 +3334,7 @@
               }
             },
             "available_queries": {
-              "description": "Available query instructions for the current context (subset of 375 GUARDQUERY entries)",
+              "description": "Available query instructions for the current context (subset of the GUARDQUERY catalog)",
               "type": "array",
               "items": {
                 "type": "object",
@@ -3369,7 +3369,7 @@
                   "returnType"
                 ],
                 "additionalProperties": false,
-                "description": "A Guard query instruction available for the current context (subset of GUARDQUERY 375 entries)."
+                "description": "A Guard query instruction available for the current context (subset of the GUARDQUERY catalog)."
               }
             },
             "risk_warnings": {
@@ -3914,7 +3914,7 @@
           "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).",
+          "description": "Composite review submission report (F01 ordering): the structured-reputation repository write runs BEFORE the progress forward (its review-edge guard anchors the PRE node), the optional reward claim runs AFTER — one passport submission, fail-isolated steps. A failed step never rolled back the forward. Relay failed/unknown steps to the user with next_action (probe before retry; dedicated repository/reward tools).",
           "type": "array",
           "items": {
             "type": "object",
@@ -3931,20 +3931,25 @@
                 "type": "string",
                 "enum": [
                   "success",
-                  "failed"
+                  "failed",
+                  "unknown"
                 ],
-                "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback)."
+                "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback). 'unknown' (esln-261023 E-6) = the submission outcome could NOT be observed (transport drop after submit) — the step MAY have landed; this is NOT a confirmed failure. Follow next_action (probe) before any retry; a blind retry double-writes."
               },
               "detail": {
                 "type": "string",
-                "description": "On success: what was written/claimed (payload summary). On failure: what the step attempted."
+                "description": "On success: what was written/claimed (payload summary). On failure or unknown: what the step attempted."
               },
               "digest": {
-                "description": "Transaction digest when the step succeeded.",
+                "description": "Transaction digest: on success the landing digest; on an unknown outcome the transport-reported pre-submit digest — verify it via onchain_transaction (executed → landed, adopt; failure → final; unresolvable → nothing landed).",
                 "type": "string"
               },
               "error": {
-                "description": "Error message when the step failed. Retry via the dedicated repository/reward tools with the same submission values.",
+                "description": "Error message when the step failed or stayed unknown. Retry via the dedicated repository/reward tools with the same submission values — only after a probe confirms nothing landed.",
+                "type": "string"
+              },
+              "next_action": {
+                "description": "Present on failed/unknown steps: the concrete recovery move (the probe to run, the safe-retry condition, or the two-phase split).",
                 "type": "string"
               }
             },

package/dist/schemas/monitor_events.output.json

@@ -863,7 +863,7 @@
               }
             },
             "available_queries": {
-              "description": "Available query instructions for the current context (subset of 375 GUARDQUERY entries)",
+              "description": "Available query instructions for the current context (subset of the GUARDQUERY catalog)",
               "type": "array",
               "items": {
                 "type": "object",
@@ -898,7 +898,7 @@
                   "returnType"
                 ],
                 "additionalProperties": false,
-                "description": "A Guard query instruction available for the current context (subset of GUARDQUERY 375 entries)."
+                "description": "A Guard query instruction available for the current context (subset of the GUARDQUERY catalog)."
               }
             },
             "risk_warnings": {
@@ -1443,7 +1443,7 @@
           "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).",
+          "description": "Composite review submission report (F01 ordering): the structured-reputation repository write runs BEFORE the progress forward (its review-edge guard anchors the PRE node), the optional reward claim runs AFTER — one passport submission, fail-isolated steps. A failed step never rolled back the forward. Relay failed/unknown steps to the user with next_action (probe before retry; dedicated repository/reward tools).",
           "type": "array",
           "items": {
             "type": "object",
@@ -1460,20 +1460,25 @@
                 "type": "string",
                 "enum": [
                   "success",
-                  "failed"
+                  "failed",
+                  "unknown"
                 ],
-                "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback)."
+                "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback). 'unknown' (esln-261023 E-6) = the submission outcome could NOT be observed (transport drop after submit) — the step MAY have landed; this is NOT a confirmed failure. Follow next_action (probe) before any retry; a blind retry double-writes."
               },
               "detail": {
                 "type": "string",
-                "description": "On success: what was written/claimed (payload summary). On failure: what the step attempted."
+                "description": "On success: what was written/claimed (payload summary). On failure or unknown: what the step attempted."
               },
               "digest": {
-                "description": "Transaction digest when the step succeeded.",
+                "description": "Transaction digest: on success the landing digest; on an unknown outcome the transport-reported pre-submit digest — verify it via onchain_transaction (executed → landed, adopt; failure → final; unresolvable → nothing landed).",
                 "type": "string"
               },
               "error": {
-                "description": "Error message when the step failed. Retry via the dedicated repository/reward tools with the same submission values.",
+                "description": "Error message when the step failed or stayed unknown. Retry via the dedicated repository/reward tools with the same submission values — only after a probe confirms nothing landed.",
+                "type": "string"
+              },
+              "next_action": {
+                "description": "Present on failed/unknown steps: the concrete recovery move (the probe to run, the safe-retry condition, or the two-phase split).",
                 "type": "string"
               }
             },

package/dist/schemas/monitor_subscription.output.json

@@ -890,7 +890,7 @@
               }
             },
             "available_queries": {
-              "description": "Available query instructions for the current context (subset of 375 GUARDQUERY entries)",
+              "description": "Available query instructions for the current context (subset of the GUARDQUERY catalog)",
               "type": "array",
               "items": {
                 "type": "object",
@@ -925,7 +925,7 @@
                   "returnType"
                 ],
                 "additionalProperties": false,
-                "description": "A Guard query instruction available for the current context (subset of GUARDQUERY 375 entries)."
+                "description": "A Guard query instruction available for the current context (subset of the GUARDQUERY catalog)."
               }
             },
             "risk_warnings": {
@@ -1470,7 +1470,7 @@
           "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).",
+          "description": "Composite review submission report (F01 ordering): the structured-reputation repository write runs BEFORE the progress forward (its review-edge guard anchors the PRE node), the optional reward claim runs AFTER — one passport submission, fail-isolated steps. A failed step never rolled back the forward. Relay failed/unknown steps to the user with next_action (probe before retry; dedicated repository/reward tools).",
           "type": "array",
           "items": {
             "type": "object",
@@ -1487,20 +1487,25 @@
                 "type": "string",
                 "enum": [
                   "success",
-                  "failed"
+                  "failed",
+                  "unknown"
                 ],
-                "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback)."
+                "description": "Step outcome. Steps are fail-isolated: a failed step never affects the forward or the other step (on-chain has no rollback). 'unknown' (esln-261023 E-6) = the submission outcome could NOT be observed (transport drop after submit) — the step MAY have landed; this is NOT a confirmed failure. Follow next_action (probe) before any retry; a blind retry double-writes."
               },
               "detail": {
                 "type": "string",
-                "description": "On success: what was written/claimed (payload summary). On failure: what the step attempted."
+                "description": "On success: what was written/claimed (payload summary). On failure or unknown: what the step attempted."
               },
               "digest": {
-                "description": "Transaction digest when the step succeeded.",
+                "description": "Transaction digest: on success the landing digest; on an unknown outcome the transport-reported pre-submit digest — verify it via onchain_transaction (executed → landed, adopt; failure → final; unresolvable → nothing landed).",
                 "type": "string"
               },
               "error": {
-                "description": "Error message when the step failed. Retry via the dedicated repository/reward tools with the same submission values.",
+                "description": "Error message when the step failed or stayed unknown. Retry via the dedicated repository/reward tools with the same submission values — only after a probe confirms nothing landed.",
+                "type": "string"
+              },
+              "next_action": {
+                "description": "Present on failed/unknown steps: the concrete recovery move (the probe to run, the safe-retry condition, or the two-phase split).",
                 "type": "string"
               }
             },