@wowok/agent-mcp 3.3.3 → 3.3.5

package/dist/schemas/account_operation.output.json

@@ -2386,6 +2386,7 @@
                 "submission_unknown",
                 "move_abort_unmapped",
                 "missing_data",
+                "state_not_visible",
                 "unknown"
               ]
             },
@@ -3699,7 +3700,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",

package/dist/schemas/bridge_operation.output.json

@@ -70,6 +70,7 @@
                 "submission_unknown",
                 "move_abort_unmapped",
                 "missing_data",
+                "state_not_visible",
                 "unknown"
               ]
             },
@@ -1378,7 +1379,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",

package/dist/schemas/index.json

@@ -2,7 +2,7 @@
   "$schema": "http://json-schema.org/draft-07/schema#",
   "title": "WoWok MCP Schema Index",
   "description": "Index of all available JSON schemas for WoWok MCP tools",
-  "generatedAt": "2026-10-23T20:22:02.598Z",
+  "generatedAt": "2026-10-23T22:51:17.328Z",
   "tools": [
     {
       "name": "onchain_operations",

package/dist/schemas/keeper_operation.output.json

@@ -1282,7 +1282,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",

package/dist/schemas/local_cache_operation.output.json

@@ -264,6 +264,7 @@
                 "submission_unknown",
                 "move_abort_unmapped",
                 "missing_data",
+                "state_not_visible",
                 "unknown"
               ]
             },
@@ -1548,7 +1549,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",

package/dist/schemas/local_history_operation.output.json

@@ -190,6 +190,7 @@
                 "submission_unknown",
                 "move_abort_unmapped",
                 "missing_data",
+                "state_not_visible",
                 "unknown"
               ]
             },
@@ -1474,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",

package/dist/schemas/local_info_operation.output.json

@@ -76,6 +76,7 @@
                 "submission_unknown",
                 "move_abort_unmapped",
                 "missing_data",
+                "state_not_visible",
                 "unknown"
               ]
             },
@@ -1360,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",

package/dist/schemas/local_mark_operation.output.json

@@ -168,6 +168,7 @@
                 "submission_unknown",
                 "move_abort_unmapped",
                 "missing_data",
+                "state_not_visible",
                 "unknown"
               ]
             },
@@ -1452,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",

package/dist/schemas/messenger_operation.output.json

@@ -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",

package/dist/schemas/monitor_events.output.json

@@ -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",

package/dist/schemas/monitor_subscription.output.json

@@ -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",

package/dist/schemas/onchain_events.output.json

@@ -3432,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",

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'",
@@ -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",
@@ -5667,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",
@@ -5827,6 +5857,7 @@
                 "submission_unknown",
                 "move_abort_unmapped",
                 "missing_data",
+                "state_not_visible",
                 "unknown"
               ]
             },
@@ -7158,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",

package/dist/schemas/onchain_operations.schema.json

@@ -4664,12 +4664,12 @@
               ]
             },
             "review": {
-              "description": "Structured review composite (REVIEW component): after this forward succeeds, write the structured reputation record into a Repository (+ optional reward claim), reusing this call's passport submission. Requires operate (the chain fires only after a successful forward).",
+              "description": "Structured review composite (REVIEW component): with a passport submission the structured-record write runs BEFORE this forward (the review-edge credential anchors the PRE node — F01), then the forward, then the optional reward claim. Requires operate. Steps are reported in semantic.review_steps.",
               "type": "object",
               "properties": {
                 "repository": {
                   "type": "string",
-                  "description": "Repository object ID or name that stores the structured reputation record. The matching policy key must accept a JSON payload {rating, tags?, orderRef?}. id_from options (C30): Signer = one record per BUYER (rewrite = own-record overwrite); None + a write_guard with id_from_submission = one record per bound OBJECT/ORDER (the row id is the raw bound Order address — the verified once-per-order review shape); Clock = append-only log. PREFERRED: the service's review repository EMITTED BY THE BUILD PLAN when review_mode was set (AR-1) — resolve it from the service's repositories list (service_panorama / onchain_objects, name suffix '_review') — never guess an address."
+                  "description": "Repository object ID or name that stores the structured reputation record. The matching policy key must accept a JSON payload {rating, tags?, orderRef?}. id_from options (C30): None = one record per bound OBJECT/ORDER with a write_guard (row id = the order address — the compile-emitted default AND the verified once-per-order review shape, F09); Signer = one record per BUYER (rewrite = own-record overwrite; a repeat buyer can only ever hold ONE row across all their orders — do not use for per-order reviews); Clock = append-only log. PREFERRED: the service's review repository EMITTED BY THE BUILD PLAN when review_mode was set (AR-1) — resolve it from the service's repositories list (service_panorama / onchain_objects, name suffix '_review') — never guess an address."
                 },
                 "policy": {
                   "description": "Policy RULE NAME to write under (the repository's PolicyRule whose value_type is String — the chain writes the structured record as a JSON string row). MUST match an existing policy of the target repository. Default 'review' (the compile-emitted review policy name). A mismatch aborts the write AFTER the forward — the review-edge credential is single-use, so the row can never be re-written; resolve the exact name from the build plan / service_panorama before calling.",
@@ -20480,7 +20480,25 @@
               "additionalProperties": false
             },
             "arb_claim_compensation": {
-              "description": "Specify the adjudicated Arb object to obtain order compensation. ZERO-INDEMNITY GATE (BF-14, chain abort 11): when the ruling's indemnity is 0 (a dismissal) the claim is REFUSED on-chain — the case stays open, the dispute fee stays escrowed (withdrawable by the arbitrator only after the 30-day window closes with no objection, or blocked while an objection is pending), and `order.claimed_by` is NOT written. A claim that DOES pay (indemnity > 0) closes the case (state 5), pays the claimant, writes `order.claimed_by`, and releases the fee path. DIRECTION CAUTION: because only paying claims write `claimed_by`, a dismissal leaves it `none` — refund-style rails gated on `claimed_by == none` stay LIVE after a dismissal, while merchant-recovery rails gated on `claimed_by != none` can never fire (F-BS-54). Read ruling DIRECTION from `arb.indemnity.amount` (query 1641), never from `claimed_by`.",
+              "description": "Specify the adjudicated Arb object to obtain order compensation. ZERO-INDEMNITY GATE (BF-14, chain abort 11): when the ruling's indemnity is 0 (a dismissal) the claim is REFUSED on-chain — the case stays open, the dispute fee stays escrowed (withdrawable by the arbitrator only after the 30-day window closes with no objection, or blocked while an objection is pending), and `order.claimed_by` is NOT written. A claim that DOES pay (indemnity > 0) closes the case (state 5), pays the claimant, writes `order.claimed_by`, and releases the fee path. DIRECTION CAUTION: because only paying claims write `claimed_by`, a dismissal leaves it `none` — refund-style rails gated on `claimed_by == none` stay LIVE after a dismissal, while merchant-recovery rails gated on `claimed_by != none` can never fire (F-BS-54). Read ruling DIRECTION from `arb.indemnity.amount` (query 1641), never from `claimed_by`. F05 REVERSE GATE (yfd-ln-261024): when this order's escrow is ALREADY fully released (allocation balance 0 of a positive order amount), the claim is REFUSED unless acknowledge_dual_payout is true — pairing a paid compensation with a completed escrow track is a netting decision the operator must state (see acknowledge_dual_payout).",
+              "type": "object",
+              "properties": {
+                "arb": {
+                  "type": "string",
+                  "description": "Arb object ID or name."
+                }
+              },
+              "required": [
+                "arb"
+              ],
+              "additionalProperties": false
+            },
+            "acknowledge_dual_payout": {
+              "description": "Explicit opt-in for a KNOWN double payout on the compensation-claim direction: when this order's escrow is already FULLY released (allocation balance 0 of a positive order amount) and this call claims the arbitration compensation on top, the call is REFUSED unless this flag is true. The escrow track and the compensation track are independent by design — the chain will not stop the second payout, so the operator must state the netting decision deliberately. Leave unset for claims on orders whose escrow is intact or partially released.",
+              "type": "boolean"
+            },
+            "arb_case_conclude": {
+              "description": "DISMISSAL CONVERGER (F-BS-54/56, F-OF2-01): stamp a CONCLUDED, DEFENDANT-FAVORED ruling onto this order through the service's case-conclusion entry so the `claimed_by == none` refund rails close AT RULING TIME instead of staying live forever. PERMISSIONLESS: any keeper (merchant agent, watchdog, even the buyer) may drive it; it writes the claimed_by=case flag and MOVES NO FUNDS. The chain refuses anything but a concluded (Arbitrated/Withdrawn) case leaving NO indemnity (E_CASE_NOT_DISMISSAL_CONCLUSION, abort 48). TYPICAL KEEPER LOOP after a 0-indemnity ruling: arb_claim_compensation aborts 11 (BF-14 zero-indemnity gate) → call THIS to close the refund rails → the escrow can then only exit through the merchant-recovery rails.",
               "type": "object",
               "properties": {
                 "arb": {

package/dist/schemas/onchain_operations_order.schema.json

@@ -161,7 +161,25 @@
           "additionalProperties": false
         },
         "arb_claim_compensation": {
-          "description": "Specify the adjudicated Arb object to obtain order compensation. ZERO-INDEMNITY GATE (BF-14, chain abort 11): when the ruling's indemnity is 0 (a dismissal) the claim is REFUSED on-chain — the case stays open, the dispute fee stays escrowed (withdrawable by the arbitrator only after the 30-day window closes with no objection, or blocked while an objection is pending), and `order.claimed_by` is NOT written. A claim that DOES pay (indemnity > 0) closes the case (state 5), pays the claimant, writes `order.claimed_by`, and releases the fee path. DIRECTION CAUTION: because only paying claims write `claimed_by`, a dismissal leaves it `none` — refund-style rails gated on `claimed_by == none` stay LIVE after a dismissal, while merchant-recovery rails gated on `claimed_by != none` can never fire (F-BS-54). Read ruling DIRECTION from `arb.indemnity.amount` (query 1641), never from `claimed_by`.",
+          "description": "Specify the adjudicated Arb object to obtain order compensation. ZERO-INDEMNITY GATE (BF-14, chain abort 11): when the ruling's indemnity is 0 (a dismissal) the claim is REFUSED on-chain — the case stays open, the dispute fee stays escrowed (withdrawable by the arbitrator only after the 30-day window closes with no objection, or blocked while an objection is pending), and `order.claimed_by` is NOT written. A claim that DOES pay (indemnity > 0) closes the case (state 5), pays the claimant, writes `order.claimed_by`, and releases the fee path. DIRECTION CAUTION: because only paying claims write `claimed_by`, a dismissal leaves it `none` — refund-style rails gated on `claimed_by == none` stay LIVE after a dismissal, while merchant-recovery rails gated on `claimed_by != none` can never fire (F-BS-54). Read ruling DIRECTION from `arb.indemnity.amount` (query 1641), never from `claimed_by`. F05 REVERSE GATE (yfd-ln-261024): when this order's escrow is ALREADY fully released (allocation balance 0 of a positive order amount), the claim is REFUSED unless acknowledge_dual_payout is true — pairing a paid compensation with a completed escrow track is a netting decision the operator must state (see acknowledge_dual_payout).",
+          "type": "object",
+          "properties": {
+            "arb": {
+              "type": "string",
+              "description": "Arb object ID or name."
+            }
+          },
+          "required": [
+            "arb"
+          ],
+          "additionalProperties": false
+        },
+        "acknowledge_dual_payout": {
+          "description": "Explicit opt-in for a KNOWN double payout on the compensation-claim direction: when this order's escrow is already FULLY released (allocation balance 0 of a positive order amount) and this call claims the arbitration compensation on top, the call is REFUSED unless this flag is true. The escrow track and the compensation track are independent by design — the chain will not stop the second payout, so the operator must state the netting decision deliberately. Leave unset for claims on orders whose escrow is intact or partially released.",
+          "type": "boolean"
+        },
+        "arb_case_conclude": {
+          "description": "DISMISSAL CONVERGER (F-BS-54/56, F-OF2-01): stamp a CONCLUDED, DEFENDANT-FAVORED ruling onto this order through the service's case-conclusion entry so the `claimed_by == none` refund rails close AT RULING TIME instead of staying live forever. PERMISSIONLESS: any keeper (merchant agent, watchdog, even the buyer) may drive it; it writes the claimed_by=case flag and MOVES NO FUNDS. The chain refuses anything but a concluded (Arbitrated/Withdrawn) case leaving NO indemnity (E_CASE_NOT_DISMISSAL_CONCLUSION, abort 48). TYPICAL KEEPER LOOP after a 0-indemnity ruling: arb_claim_compensation aborts 11 (BF-14 zero-indemnity gate) → call THIS to close the refund rails → the escrow can then only exit through the merchant-recovery rails.",
           "type": "object",
           "properties": {
             "arb": {

package/dist/schemas/onchain_operations_progress.schema.json

@@ -325,12 +325,12 @@
           ]
         },
         "review": {
-          "description": "Structured review composite (REVIEW component): after this forward succeeds, write the structured reputation record into a Repository (+ optional reward claim), reusing this call's passport submission. Requires operate (the chain fires only after a successful forward).",
+          "description": "Structured review composite (REVIEW component): with a passport submission the structured-record write runs BEFORE this forward (the review-edge credential anchors the PRE node — F01), then the forward, then the optional reward claim. Requires operate. Steps are reported in semantic.review_steps.",
           "type": "object",
           "properties": {
             "repository": {
               "type": "string",
-              "description": "Repository object ID or name that stores the structured reputation record. The matching policy key must accept a JSON payload {rating, tags?, orderRef?}. id_from options (C30): Signer = one record per BUYER (rewrite = own-record overwrite); None + a write_guard with id_from_submission = one record per bound OBJECT/ORDER (the row id is the raw bound Order address — the verified once-per-order review shape); Clock = append-only log. PREFERRED: the service's review repository EMITTED BY THE BUILD PLAN when review_mode was set (AR-1) — resolve it from the service's repositories list (service_panorama / onchain_objects, name suffix '_review') — never guess an address."
+              "description": "Repository object ID or name that stores the structured reputation record. The matching policy key must accept a JSON payload {rating, tags?, orderRef?}. id_from options (C30): None = one record per bound OBJECT/ORDER with a write_guard (row id = the order address — the compile-emitted default AND the verified once-per-order review shape, F09); Signer = one record per BUYER (rewrite = own-record overwrite; a repeat buyer can only ever hold ONE row across all their orders — do not use for per-order reviews); Clock = append-only log. PREFERRED: the service's review repository EMITTED BY THE BUILD PLAN when review_mode was set (AR-1) — resolve it from the service's repositories list (service_panorama / onchain_objects, name suffix '_review') — never guess an address."
             },
             "policy": {
               "description": "Policy RULE NAME to write under (the repository's PolicyRule whose value_type is String — the chain writes the structured record as a JSON string row). MUST match an existing policy of the target repository. Default 'review' (the compile-emitted review policy name). A mismatch aborts the write AFTER the forward — the review-edge credential is single-use, so the row can never be re-written; resolve the exact name from the build plan / service_panorama before calling.",

package/dist/schemas/onchain_table_data.output.json

@@ -9339,7 +9339,7 @@
               "type": "boolean"
             },
             "radar_review_summary": {
-              "description": "Merchant-side review coverage summary (REVIEW-COMPONENT-PLAN batch 4): completed orders vs orders with a structured review record. Review rows live in a caller-named Repository — gather both counts via onchain_table_data (repository rows under the 'review' key, id_from=Signer → one row per buyer) and pass them in; the radar derives the merchant-side review-rate hint (high missing rate with a reward attached → reward lapsed or window too short). Omit when no review repository is bound.",
+              "description": "Merchant-side review coverage summary (REVIEW-COMPONENT-PLAN batch 4): completed orders vs orders with a structured review record. Review rows live in a caller-named Repository — gather both counts via onchain_table_data (repository rows under the 'review' key, order-keyed → one row per order, F09) and pass them in; the radar derives the merchant-side review-rate hint (high missing rate with a reward attached → reward lapsed or window too short). Omit when no review repository is bound.",
               "type": "object",
               "properties": {
                 "orders_completed": {
@@ -11068,7 +11068,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",

package/dist/schemas/query_toolkit.output.json

@@ -16496,6 +16496,20 @@
                             }
                           ]
                         },
+                        "max_coverable_order": {
+                          "type": "string",
+                          "description": "Raw smallest units: fund / 3 — the LARGEST single order this fund can still cover (F-OF2-06). Orders above this ceiling are refused at buy (compensation_fund_below_order_ceiling), so this is the storefront's effective price cap; check it before promising a bigger basket."
+                        },
+                        "max_coverable_order_display": {
+                          "anyOf": [
+                            {
+                              "type": "string"
+                            },
+                            {
+                              "type": "null"
+                            }
+                          ]
+                        },
                         "required_for_this_basket": {
                           "type": "string",
                           "description": "Raw smallest units: 3 x total_pay — the per-order payout requirement this basket must meet at order creation."
@@ -16521,6 +16535,8 @@
                       "required": [
                         "fund_balance",
                         "fund_balance_display",
+                        "max_coverable_order",
+                        "max_coverable_order_display",
                         "required_for_this_basket",
                         "required_display",
                         "covered",
@@ -22625,7 +22641,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",

package/dist/schemas/query_toolkit.schema.json

@@ -1255,7 +1255,7 @@
           "type": "boolean"
         },
         "radar_review_summary": {
-          "description": "Merchant-side review coverage summary (REVIEW-COMPONENT-PLAN batch 4): completed orders vs orders with a structured review record. Review rows live in a caller-named Repository — gather both counts via onchain_table_data (repository rows under the 'review' key, id_from=Signer → one row per buyer) and pass them in; the radar derives the merchant-side review-rate hint (high missing rate with a reward attached → reward lapsed or window too short). Omit when no review repository is bound.",
+          "description": "Merchant-side review coverage summary (REVIEW-COMPONENT-PLAN batch 4): completed orders vs orders with a structured review record. Review rows live in a caller-named Repository — gather both counts via onchain_table_data (repository rows under the 'review' key, order-keyed → one row per order, F09) and pass them in; the radar derives the merchant-side review-rate hint (high missing rate with a reward attached → reward lapsed or window too short). Omit when no review repository is bound.",
           "type": "object",
           "properties": {
             "orders_completed": {