@wowok/agent-mcp 3.3.2 → 3.3.5

package/dist/schemas/onchain_events.output.json

@@ -121,6 +121,10 @@
                             "type": "string",
                             "const": "OrderAllocatorsAppendedEvent"
                           },
+                          {
+                            "type": "string",
+                            "const": "DiscountRedeemedEvent"
+                          },
                           {
                             "type": "string",
                             "const": "ArbStatementEvent"
@@ -141,7 +145,7 @@
                             "type": "string"
                           }
                         ],
-                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
+                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, DiscountRedeemedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
                       },
                       "type_raw": {
                         "type": "string",
@@ -279,6 +283,10 @@
                             "type": "string",
                             "const": "OrderAllocatorsAppendedEvent"
                           },
+                          {
+                            "type": "string",
+                            "const": "DiscountRedeemedEvent"
+                          },
                           {
                             "type": "string",
                             "const": "ArbStatementEvent"
@@ -299,7 +307,7 @@
                             "type": "string"
                           }
                         ],
-                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
+                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, DiscountRedeemedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
                       },
                       "type_raw": {
                         "type": "string",
@@ -494,6 +502,10 @@
                             "type": "string",
                             "const": "OrderAllocatorsAppendedEvent"
                           },
+                          {
+                            "type": "string",
+                            "const": "DiscountRedeemedEvent"
+                          },
                           {
                             "type": "string",
                             "const": "ArbStatementEvent"
@@ -514,7 +526,7 @@
                             "type": "string"
                           }
                         ],
-                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
+                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, DiscountRedeemedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
                       },
                       "type_raw": {
                         "type": "string",
@@ -707,6 +719,10 @@
                             "type": "string",
                             "const": "OrderAllocatorsAppendedEvent"
                           },
+                          {
+                            "type": "string",
+                            "const": "DiscountRedeemedEvent"
+                          },
                           {
                             "type": "string",
                             "const": "ArbStatementEvent"
@@ -727,7 +743,7 @@
                             "type": "string"
                           }
                         ],
-                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
+                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, DiscountRedeemedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
                       },
                       "type_raw": {
                         "type": "string",
@@ -913,6 +929,10 @@
                             "type": "string",
                             "const": "OrderAllocatorsAppendedEvent"
                           },
+                          {
+                            "type": "string",
+                            "const": "DiscountRedeemedEvent"
+                          },
                           {
                             "type": "string",
                             "const": "ArbStatementEvent"
@@ -933,7 +953,7 @@
                             "type": "string"
                           }
                         ],
-                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
+                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, DiscountRedeemedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
                       },
                       "type_raw": {
                         "type": "string",
@@ -1092,6 +1112,10 @@
                             "type": "string",
                             "const": "OrderAllocatorsAppendedEvent"
                           },
+                          {
+                            "type": "string",
+                            "const": "DiscountRedeemedEvent"
+                          },
                           {
                             "type": "string",
                             "const": "ArbStatementEvent"
@@ -1112,7 +1136,7 @@
                             "type": "string"
                           }
                         ],
-                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
+                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, DiscountRedeemedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
                       },
                       "type_raw": {
                         "type": "string",
@@ -1282,6 +1306,10 @@
                             "type": "string",
                             "const": "OrderAllocatorsAppendedEvent"
                           },
+                          {
+                            "type": "string",
+                            "const": "DiscountRedeemedEvent"
+                          },
                           {
                             "type": "string",
                             "const": "ArbStatementEvent"
@@ -1302,7 +1330,7 @@
                             "type": "string"
                           }
                         ],
-                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
+                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, DiscountRedeemedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
                       },
                       "type_raw": {
                         "type": "string",
@@ -1461,6 +1489,10 @@
                             "type": "string",
                             "const": "OrderAllocatorsAppendedEvent"
                           },
+                          {
+                            "type": "string",
+                            "const": "DiscountRedeemedEvent"
+                          },
                           {
                             "type": "string",
                             "const": "ArbStatementEvent"
@@ -1481,7 +1513,7 @@
                             "type": "string"
                           }
                         ],
-                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
+                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, DiscountRedeemedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
                       },
                       "type_raw": {
                         "type": "string",
@@ -1634,6 +1666,10 @@
                             "type": "string",
                             "const": "OrderAllocatorsAppendedEvent"
                           },
+                          {
+                            "type": "string",
+                            "const": "DiscountRedeemedEvent"
+                          },
                           {
                             "type": "string",
                             "const": "ArbStatementEvent"
@@ -1654,7 +1690,7 @@
                             "type": "string"
                           }
                         ],
-                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
+                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, DiscountRedeemedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
                       },
                       "type_raw": {
                         "type": "string",
@@ -1815,6 +1851,10 @@
                             "type": "string",
                             "const": "OrderAllocatorsAppendedEvent"
                           },
+                          {
+                            "type": "string",
+                            "const": "DiscountRedeemedEvent"
+                          },
                           {
                             "type": "string",
                             "const": "ArbStatementEvent"
@@ -1835,7 +1875,7 @@
                             "type": "string"
                           }
                         ],
-                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
+                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, DiscountRedeemedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
                       },
                       "type_raw": {
                         "type": "string",
@@ -1996,6 +2036,10 @@
                             "type": "string",
                             "const": "OrderAllocatorsAppendedEvent"
                           },
+                          {
+                            "type": "string",
+                            "const": "DiscountRedeemedEvent"
+                          },
                           {
                             "type": "string",
                             "const": "ArbStatementEvent"
@@ -2016,7 +2060,7 @@
                             "type": "string"
                           }
                         ],
-                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
+                        "description": "Event type. Supports Wowok built-in types (ArbEvent, NewOrderEvent, ProgressEvent, DemandPresentEvent, DemandFeedbackEvent, NewEntityEvent, ServiceEvent, ArbitrationEvent, DemandChangedEvent, VoteEvent, FeedbackEvent, AllocationEvent, TreasuryEvent, RewardClaimEvent, RewardFundEvent, RewardWithdrawEvent, NewPaymentEvent, OrderAllocatorsAppendedEvent, DiscountRedeemedEvent, ArbStatementEvent, PermissionChangedEvent, RepositoryDataOverwriteEvent, VoteEvictedEvent) or any string for generic MoveEventType (e.g., '0x2::coin::CoinEvent'). See the Event Semantics Registry (knowledge/event-semantics.ts) for every event's trigger logic, parameter meanings, and business semantics — especially NewPaymentEvent (the universal fund-flow receipt: from_object is the internal-only funding-source object — Treasury/Allocation/Service — set by the framework, never by user code)."
                       },
                       "type_raw": {
                         "type": "string",
@@ -2808,7 +2852,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",
@@ -2843,7 +2887,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": {
@@ -3388,7 +3432,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",
@@ -3405,20 +3449,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/onchain_events.schema.json

@@ -79,6 +79,10 @@
           "type": "string",
           "const": "OrderAllocatorsAppendedEvent"
         },
+        {
+          "type": "string",
+          "const": "DiscountRedeemedEvent"
+        },
         {
           "type": "string",
           "const": "ArbStatementEvent"

package/dist/schemas/onchain_operations.output.json

@@ -2362,9 +2362,39 @@
                 "type"
               ],
               "additionalProperties": false
+            },
+            {
+              "type": "object",
+              "properties": {
+                "type": {
+                  "type": "string",
+                  "const": "receive_auto_claimed",
+                  "description": "Discriminator for this result variant. Constraint: always 'receive_auto_claimed'. Example: 'receive_auto_claimed'"
+                },
+                "receive_state": {
+                  "type": "string",
+                  "const": "auto_claimed",
+                  "description": "The receive goal was already met before this call: settlement auto-claimed the CoinWrapper into the wallet."
+                },
+                "receiver": {
+                  "type": "string",
+                  "description": "Wallet address that already holds the claimed funds."
+                },
+                "message": {
+                  "type": "string",
+                  "description": "Human-readable satisfied-state explanation, including how to verify arrival."
+                }
+              },
+              "required": [
+                "type",
+                "receive_state",
+                "receiver",
+                "message"
+              ],
+              "additionalProperties": false
             }
           ],
-          "description": "Discriminated result payload. 'transaction' (raw Wow response), 'data' (query result array), 'null' (no-op completed)."
+          "description": "Discriminated result payload. 'transaction' (raw Wow response), 'data' (query result array), 'null' (no-op completed), 'receive_auto_claimed' (OF2-15: payment receive already satisfied by the settlement auto-claim — no transaction exists, funds are already in the wallet)."
         },
         "message": {
           "description": "Human-readable summary or hint. Constraint: always present for transaction results; may be omitted for data/null. Example: 'Transaction completed successfully'",
@@ -3053,7 +3083,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",
@@ -3088,7 +3118,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": {
@@ -3633,7 +3663,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",
@@ -3650,20 +3680,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"
                   }
                 },
@@ -3797,7 +3832,7 @@
                               "type": "integer",
                               "minimum": 0,
                               "maximum": 255,
-                              "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails such as full refunds). SLOT 0 SEMANTICS (protocol 154): slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
+                              "description": "Identifier (0-255) for data lookup in Guard table. Slot consensus (enforced on-chain at guard table construction): 0-220 = user slots (free for business guards); 221-253 = PROTOCOL-RESERVED (rejected on-chain — reserved so future protocol features get fixed slots without colliding with published guards); 255 = ONCE replay-protection slot on Allocation (byte-keyed, the submitted bytes are the once-key — use for per-period keys like period-<N>); 254 = ONCE-FOR-OBJECT slot on Allocation (chain-derived key = bcs(the Allocation's payment_info.for_object); the submitted bytes are ignored and the submission only arms the slot — use for one-shot per-order rails such as full refunds). SLOT 0 SEMANTICS: slot 0 carries the transacted Order address by convention. As a submission slot it is legal on order/allocation/machine rails (the order exists when those verify), but FORBIDDEN on a Service buy_guard — the order does not exist when the buy-time passport is verified, so the mount is refused (service abort 43)."
                             },
                             "b_submission": {
                               "type": "boolean",
@@ -5082,7 +5117,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",
@@ -5117,7 +5152,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": {
@@ -5662,7 +5697,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",
@@ -5679,20 +5714,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"
                   }
                 },
@@ -5795,6 +5835,7 @@
                 "guard_rejected",
                 "state_conflict",
                 "insufficient_balance",
+                "pool_shortage",
                 "transaction_expired",
                 "stock_exhausted",
                 "sale_suspended",
@@ -5816,6 +5857,7 @@
                 "submission_unknown",
                 "move_abort_unmapped",
                 "missing_data",
+                "state_not_visible",
                 "unknown"
               ]
             },
@@ -5828,8 +5870,49 @@
               "type": "string"
             },
             "related_object": {
-              "description": "Object ID related to the error, if any. Example: '0x123...'",
+              "description": "Object ID related to the error, if any. Example: '0x123...",
+              "type": "string"
+            },
+            "committed_digest": {
+              "description": "C-1 (rex-mn-261021 §2.4): present ONLY when the failed execution is a COMMITTED transaction — the aborting tx's own digest. The tx is final and gas-charged; a MoveAbort reverts its effects atomically, so the digest changed no on-chain state. Verify via onchain_transaction with this digest; never blind-resubmit. Example: '5fJgk…'",
               "type": "string"
+            },
+            "submission_state": {
+              "description": "F-BS-14/39/63 (bs-mn-261022): present ONLY when error_code is 'submission_unknown' — the request failed at transport level AFTER the request left the client, so the transaction MAY have committed and the response was lost. This is NOT a deterministic failure: verify commit state (onchain_events for the sender / query the expected object) before any retry; a blind retry double-purchases (live mainnet ghost orders).",
+              "type": "string",
+              "const": "unknown"
+            },
+            "submission_verification": {
+              "description": "F-BS-14/39/63 (harness batch-31, idempotency-key support, structured half): present ONLY when error_code is 'submission_unknown' — the machine-readable verification kit for the unknown outcome. Carries the sender, the time window to query, and any known digests, so verification needs no re-derivation from the call's arguments. Prose guidance lives in result.recovery_hint; this block is the structured counterpart.",
+              "type": "object",
+              "properties": {
+                "sender": {
+                  "type": "string",
+                  "description": "The account that signed the possibly-landed transaction. Query onchain_events / onchain_objects for THIS address to resolve the unknown outcome. Example: '0xa1…'"
+                },
+                "failed_at": {
+                  "type": "string",
+                  "description": "ISO timestamp of the observed transport failure. The transaction (if it landed) committed between dispatch and this moment. Example: '2026-10-22T12:00:00.000Z'"
+                },
+                "verify_events_since": {
+                  "type": "string",
+                  "description": "ISO timestamp — the START of the suggested verification window (backdated to cover the dispatch-to-failure interval). Query the sender's onchain_events from this moment; anything matching this call's intent inside the window is the landed result — adopt it, do not resubmit. Example: '2026-10-22T11:59:00.000Z'"
+                },
+                "digests": {
+                  "type": "array",
+                  "items": {
+                    "type": "string"
+                  },
+                  "description": "Transport-reported transaction digests, when the error carried one (e.g. TransactionCommitUnknownError). Verify THESE FIRST via onchain_transaction — a direct digest lookup is cheaper and more decisive than any object hunt: executed → adopt; failure status → final (bytes consumed, fix the cause); unresolvable → nothing landed, resubmit is safe. Example: ['5fJgk…']"
+                }
+              },
+              "required": [
+                "sender",
+                "failed_at",
+                "verify_events_since",
+                "digests"
+              ],
+              "additionalProperties": false
             }
           },
           "required": [
@@ -6526,7 +6609,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",
@@ -6561,7 +6644,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": {
@@ -7106,7 +7189,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",
@@ -7123,20 +7206,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"
                   }
                 },
@@ -7352,7 +7440,7 @@
         "recovery"
       ],
       "additionalProperties": false,
-      "description": "Failed outcome: the operation did NOT complete. recovery is guaranteed — check recovery.strategy first, then result.error_code/retryable for retry guidance; diagnosis (when present) explains the gap between expectation and outcome."
+      "description": "Failed outcome: the operation did NOT complete — OR the submission state is unknown (result.submission_state 'unknown': the transaction may have committed despite the error; verify on-chain state before any retry). recovery is guaranteed — check recovery.strategy first, then result.error_code/retryable for retry guidance; diagnosis (when present) explains the gap between expectation and outcome."
     }
   ]
 }