@wowok/agent-mcp 2.3.12 → 2.3.14

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (93) hide show
  1. package/dist/harness/checkpoint.d.ts +8 -0
  2. package/dist/harness/checkpoint.js +129 -0
  3. package/dist/harness/index.d.ts +33 -0
  4. package/dist/harness/index.js +75 -0
  5. package/dist/harness/plan.d.ts +18 -0
  6. package/dist/harness/plan.js +252 -0
  7. package/dist/harness/recover.d.ts +17 -0
  8. package/dist/harness/recover.js +139 -0
  9. package/dist/harness/types.d.ts +137 -0
  10. package/dist/harness/types.js +1 -0
  11. package/dist/harness/verify.d.ts +42 -0
  12. package/dist/harness/verify.js +237 -0
  13. package/dist/index.js +134 -52
  14. package/dist/loop-engineering/aggregate.d.ts +50 -0
  15. package/dist/loop-engineering/aggregate.js +132 -0
  16. package/dist/loop-engineering/diagnose.d.ts +21 -0
  17. package/dist/loop-engineering/diagnose.js +179 -0
  18. package/dist/loop-engineering/improve.d.ts +26 -0
  19. package/dist/loop-engineering/improve.js +178 -0
  20. package/dist/loop-engineering/index.d.ts +4 -0
  21. package/dist/loop-engineering/index.js +4 -0
  22. package/dist/loop-engineering/pipeline.d.ts +17 -0
  23. package/dist/loop-engineering/pipeline.js +56 -0
  24. package/dist/mode-market/index.d.ts +3 -0
  25. package/dist/mode-market/index.js +3 -0
  26. package/dist/mode-market/registry.d.ts +53 -0
  27. package/dist/mode-market/registry.js +124 -0
  28. package/dist/mode-market/review.d.ts +27 -0
  29. package/dist/mode-market/review.js +214 -0
  30. package/dist/mode-market/submission.d.ts +25 -0
  31. package/dist/mode-market/submission.js +85 -0
  32. package/dist/schema/call/allocation.d.ts +40 -40
  33. package/dist/schema/call/arbitration.d.ts +90 -90
  34. package/dist/schema/call/base.d.ts +1054 -0
  35. package/dist/schema/call/base.js +100 -22
  36. package/dist/schema/call/bridge-handler.js +36 -18
  37. package/dist/schema/call/bridge.d.ts +115 -115
  38. package/dist/schema/call/handler.d.ts +2 -1
  39. package/dist/schema/call/handler.js +94 -3
  40. package/dist/schema/call/index.d.ts +1 -0
  41. package/dist/schema/call/index.js +1 -0
  42. package/dist/schema/call/machine.d.ts +144 -144
  43. package/dist/schema/call/order.d.ts +12 -12
  44. package/dist/schema/call/progress.d.ts +6 -6
  45. package/dist/schema/call/proof.js +7 -6
  46. package/dist/schema/call/reward.d.ts +6 -6
  47. package/dist/schema/call/semantic.d.ts +23 -0
  48. package/dist/schema/call/semantic.js +764 -0
  49. package/dist/schema/call/service.d.ts +142 -142
  50. package/dist/schema/call/treasury.d.ts +204 -204
  51. package/dist/schema/local/index.d.ts +113 -2
  52. package/dist/schema/local/index.js +11 -1
  53. package/dist/schema/messenger/index.d.ts +435 -95
  54. package/dist/schema/messenger/index.js +20 -8
  55. package/dist/schema/operations.d.ts +988 -495
  56. package/dist/schema/operations.js +14 -3
  57. package/dist/schema/query/index.d.ts +346 -342
  58. package/dist/schema/query/index.js +4 -1
  59. package/dist/schemas/account_operation.output.json +3 -0
  60. package/dist/schemas/account_operation.schema.json +1 -1
  61. package/dist/schemas/index.json +1 -1
  62. package/dist/schemas/local_info_operation.output.json +3 -0
  63. package/dist/schemas/local_mark_operation.output.json +3 -0
  64. package/dist/schemas/messenger_operation.output.json +21 -0
  65. package/dist/schemas/messenger_operation.schema.json +43 -8
  66. package/dist/schemas/onchain_events.output.json +3 -0
  67. package/dist/schemas/onchain_operations.output.json +464 -21
  68. package/dist/schemas/onchain_operations.schema.json +21 -17
  69. package/dist/schemas/onchain_operations_allocation.schema.json +11 -9
  70. package/dist/schemas/onchain_operations_arbitration.schema.json +11 -9
  71. package/dist/schemas/onchain_operations_contact.schema.json +11 -9
  72. package/dist/schemas/onchain_operations_demand.schema.json +11 -9
  73. package/dist/schemas/onchain_operations_gen_passport.schema.json +21 -17
  74. package/dist/schemas/onchain_operations_guard.schema.json +11 -9
  75. package/dist/schemas/onchain_operations_machine.schema.json +11 -9
  76. package/dist/schemas/onchain_operations_order.schema.json +11 -9
  77. package/dist/schemas/onchain_operations_payment.schema.json +11 -9
  78. package/dist/schemas/onchain_operations_permission.schema.json +11 -9
  79. package/dist/schemas/onchain_operations_personal.schema.json +11 -9
  80. package/dist/schemas/onchain_operations_progress.schema.json +11 -9
  81. package/dist/schemas/onchain_operations_repository.schema.json +11 -9
  82. package/dist/schemas/onchain_operations_reward.schema.json +11 -9
  83. package/dist/schemas/onchain_operations_service.schema.json +11 -9
  84. package/dist/schemas/onchain_operations_treasury.schema.json +11 -9
  85. package/dist/schemas/onchain_table_data.output.json +3 -0
  86. package/dist/schemas/query_toolkit.schema.json +5 -1
  87. package/dist/telemetry/index.d.ts +19 -0
  88. package/dist/telemetry/index.js +112 -0
  89. package/dist/telemetry/redact.d.ts +2 -0
  90. package/dist/telemetry/redact.js +23 -0
  91. package/dist/telemetry/storage.d.ts +8 -0
  92. package/dist/telemetry/storage.js +80 -0
  93. package/package.json +6 -3
package/dist/schemas/onchain_operations.schema.json CHANGED
@@ -602,7 +602,7 @@
602
602
  "type": {
603
603
  "type": "string",
604
604
  "const": "submission",
605
- "description": "Type of call response: submission"
605
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
606
606
  },
607
607
  "guard": {
608
608
  "type": "array",
@@ -611,11 +611,11 @@
611
611
  "properties": {
612
612
  "object": {
613
613
  "type": "string",
614
- "description": "Guard object name or ID."
614
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
615
615
  },
616
616
  "impack": {
617
617
  "type": "boolean",
618
- "description": "Whether the verification result of this Guard participates in the final verification logic. If true, the verification result of this Guard will be included in the final verification result; if false, the verification result of this Guard will not be included."
618
+ "description": "Whether this Guard's verification result participates in the final logic. Constraint: if false, the Guard is checked but does not block the operation. Example: true"
619
619
  }
620
620
  },
621
621
  "required": [
@@ -623,7 +623,8 @@
623
623
  "impack"
624
624
  ],
625
625
  "additionalProperties": false
626
- }
626
+ },
627
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
627
628
  },
628
629
  "submission": {
629
630
  "type": "array",
@@ -632,7 +633,7 @@
632
633
  "properties": {
633
634
  "guard": {
634
635
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
635
- "description": "Guard object name or ID."
636
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
636
637
  },
637
638
  "submission": {
638
639
  "type": "array",
@@ -1084,7 +1085,7 @@
1084
1085
  "additionalProperties": false,
1085
1086
  "description": "Guard table item"
1086
1087
  },
1087
- "description": "User-submitted data required for Guard verification."
1088
+ "description": "User-submitted data matching the Guard's required fields. Relation: structure must match the Guard table's column definitions. Example: [{field:'delivery_proof', value:'Qm...'}]"
1088
1089
  }
1089
1090
  },
1090
1091
  "required": [
@@ -1092,8 +1093,9 @@
1092
1093
  "submission"
1093
1094
  ],
1094
1095
  "additionalProperties": false,
1095
- "description": "Permission guard submission data."
1096
- }
1096
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
1097
+ },
1098
+ "description": "User-submitted data for each Guard. Relation: one entry per Guard in the guard array; fill submission fields and resubmit via call_with_submission."
1097
1099
  }
1098
1100
  },
1099
1101
  "required": [
@@ -1102,7 +1104,7 @@
1102
1104
  "submission"
1103
1105
  ],
1104
1106
  "additionalProperties": false,
1105
- "description": "Guard verification submission data required to complete an operation. Contains: (1) 'guard' - array of Guard objects to verify, each with an object ID and an 'impack' flag indicating if its result affects the final outcome; (2) 'submission' - array of user data submissions matching the Guard's requirements. The operation proceeds only after all Guards with impack=true are successfully verified."
1107
+ "description": "Guard verification required. The operation was blocked because one or more Guards require user-submitted data. Fill the submission array and resubmit. Semantic status is 'pending_input'."
1106
1108
  },
1107
1109
  "data_service": {
1108
1110
  "type": "object",
@@ -8102,7 +8104,7 @@
8102
8104
  "type": {
8103
8105
  "type": "string",
8104
8106
  "const": "submission",
8105
- "description": "Type of call response: submission"
8107
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
8106
8108
  },
8107
8109
  "guard": {
8108
8110
  "type": "array",
@@ -8111,11 +8113,11 @@
8111
8113
  "properties": {
8112
8114
  "object": {
8113
8115
  "$ref": "#/definitions/data_gen_passport/properties/guard/anyOf/0",
8114
- "description": "Guard object name or ID."
8116
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
8115
8117
  },
8116
8118
  "impack": {
8117
8119
  "type": "boolean",
8118
- "description": "Whether the verification result of this Guard participates in the final verification logic. If true, the verification result of this Guard will be included in the final verification result; if false, the verification result of this Guard will not be included."
8120
+ "description": "Whether this Guard's verification result participates in the final logic. Constraint: if false, the Guard is checked but does not block the operation. Example: true"
8119
8121
  }
8120
8122
  },
8121
8123
  "required": [
@@ -8123,7 +8125,8 @@
8123
8125
  "impack"
8124
8126
  ],
8125
8127
  "additionalProperties": false
8126
- }
8128
+ },
8129
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
8127
8130
  },
8128
8131
  "submission": {
8129
8132
  "type": "array",
@@ -8132,7 +8135,7 @@
8132
8135
  "properties": {
8133
8136
  "guard": {
8134
8137
  "$ref": "#/definitions/data_gen_passport/properties/guard/anyOf/0",
8135
- "description": "Guard object name or ID."
8138
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
8136
8139
  },
8137
8140
  "submission": {
8138
8141
  "type": "array",
@@ -8584,7 +8587,7 @@
8584
8587
  "additionalProperties": false,
8585
8588
  "description": "Guard table item"
8586
8589
  },
8587
- "description": "User-submitted data required for Guard verification."
8590
+ "description": "User-submitted data matching the Guard's required fields. Relation: structure must match the Guard table's column definitions. Example: [{field:'delivery_proof', value:'Qm...'}]"
8588
8591
  }
8589
8592
  },
8590
8593
  "required": [
@@ -8592,8 +8595,9 @@
8592
8595
  "submission"
8593
8596
  ],
8594
8597
  "additionalProperties": false,
8595
- "description": "Permission guard submission data."
8596
- }
8598
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
8599
+ },
8600
+ "description": "User-submitted data for each Guard. Relation: one entry per Guard in the guard array; fill submission fields and resubmit via call_with_submission."
8597
8601
  }
8598
8602
  },
8599
8603
  "required": [
package/dist/schemas/onchain_operations_allocation.schema.json CHANGED
@@ -409,7 +409,7 @@
409
409
  "type": {
410
410
  "type": "string",
411
411
  "const": "submission",
412
- "description": "Type of call response: submission"
412
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
413
413
  },
414
414
  "guard": {
415
415
  "type": "array",
@@ -418,11 +418,11 @@
418
418
  "properties": {
419
419
  "object": {
420
420
  "type": "string",
421
- "description": "Guard object name or ID."
421
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
422
422
  },
423
423
  "impack": {
424
424
  "type": "boolean",
425
- "description": "Whether the verification result of this Guard participates in the final verification logic. If true, the verification result of this Guard will be included in the final verification result; if false, the verification result of this Guard will not be included."
425
+ "description": "Whether this Guard's verification result participates in the final logic. Constraint: if false, the Guard is checked but does not block the operation. Example: true"
426
426
  }
427
427
  },
428
428
  "required": [
@@ -430,7 +430,8 @@
430
430
  "impack"
431
431
  ],
432
432
  "additionalProperties": false
433
- }
433
+ },
434
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
434
435
  },
435
436
  "submission": {
436
437
  "type": "array",
@@ -439,7 +440,7 @@
439
440
  "properties": {
440
441
  "guard": {
441
442
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
442
- "description": "Guard object name or ID."
443
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
443
444
  },
444
445
  "submission": {
445
446
  "type": "array",
@@ -891,7 +892,7 @@
891
892
  "additionalProperties": false,
892
893
  "description": "Guard table item"
893
894
  },
894
- "description": "User-submitted data required for Guard verification."
895
+ "description": "User-submitted data matching the Guard's required fields. Relation: structure must match the Guard table's column definitions. Example: [{field:'delivery_proof', value:'Qm...'}]"
895
896
  }
896
897
  },
897
898
  "required": [
@@ -899,8 +900,9 @@
899
900
  "submission"
900
901
  ],
901
902
  "additionalProperties": false,
902
- "description": "Permission guard submission data."
903
- }
903
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
904
+ },
905
+ "description": "User-submitted data for each Guard. Relation: one entry per Guard in the guard array; fill submission fields and resubmit via call_with_submission."
904
906
  }
905
907
  },
906
908
  "required": [
@@ -909,7 +911,7 @@
909
911
  "submission"
910
912
  ],
911
913
  "additionalProperties": false,
912
- "description": "Guard verification submission data required to complete an operation. Contains: (1) 'guard' - array of Guard objects to verify, each with an object ID and an 'impack' flag indicating if its result affects the final outcome; (2) 'submission' - array of user data submissions matching the Guard's requirements. The operation proceeds only after all Guards with impack=true are successfully verified."
914
+ "description": "Guard verification required. The operation was blocked because one or more Guards require user-submitted data. Fill the submission array and resubmit. Semantic status is 'pending_input'."
913
915
  }
914
916
  }
915
917
  }
package/dist/schemas/onchain_operations_arbitration.schema.json CHANGED
@@ -661,7 +661,7 @@
661
661
  "type": {
662
662
  "type": "string",
663
663
  "const": "submission",
664
- "description": "Type of call response: submission"
664
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
665
665
  },
666
666
  "guard": {
667
667
  "type": "array",
@@ -670,11 +670,11 @@
670
670
  "properties": {
671
671
  "object": {
672
672
  "type": "string",
673
- "description": "Guard object name or ID."
673
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
674
674
  },
675
675
  "impack": {
676
676
  "type": "boolean",
677
- "description": "Whether the verification result of this Guard participates in the final verification logic. If true, the verification result of this Guard will be included in the final verification result; if false, the verification result of this Guard will not be included."
677
+ "description": "Whether this Guard's verification result participates in the final logic. Constraint: if false, the Guard is checked but does not block the operation. Example: true"
678
678
  }
679
679
  },
680
680
  "required": [
@@ -682,7 +682,8 @@
682
682
  "impack"
683
683
  ],
684
684
  "additionalProperties": false
685
- }
685
+ },
686
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
686
687
  },
687
688
  "submission": {
688
689
  "type": "array",
@@ -691,7 +692,7 @@
691
692
  "properties": {
692
693
  "guard": {
693
694
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
694
- "description": "Guard object name or ID."
695
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
695
696
  },
696
697
  "submission": {
697
698
  "type": "array",
@@ -1143,7 +1144,7 @@
1143
1144
  "additionalProperties": false,
1144
1145
  "description": "Guard table item"
1145
1146
  },
1146
- "description": "User-submitted data required for Guard verification."
1147
+ "description": "User-submitted data matching the Guard's required fields. Relation: structure must match the Guard table's column definitions. Example: [{field:'delivery_proof', value:'Qm...'}]"
1147
1148
  }
1148
1149
  },
1149
1150
  "required": [
@@ -1151,8 +1152,9 @@
1151
1152
  "submission"
1152
1153
  ],
1153
1154
  "additionalProperties": false,
1154
- "description": "Permission guard submission data."
1155
- }
1155
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
1156
+ },
1157
+ "description": "User-submitted data for each Guard. Relation: one entry per Guard in the guard array; fill submission fields and resubmit via call_with_submission."
1156
1158
  }
1157
1159
  },
1158
1160
  "required": [
@@ -1161,7 +1163,7 @@
1161
1163
  "submission"
1162
1164
  ],
1163
1165
  "additionalProperties": false,
1164
- "description": "Guard verification submission data required to complete an operation. Contains: (1) 'guard' - array of Guard objects to verify, each with an object ID and an 'impack' flag indicating if its result affects the final outcome; (2) 'submission' - array of user data submissions matching the Guard's requirements. The operation proceeds only after all Guards with impack=true are successfully verified."
1166
+ "description": "Guard verification required. The operation was blocked because one or more Guards require user-submitted data. Fill the submission array and resubmit. Semantic status is 'pending_input'."
1165
1167
  }
1166
1168
  }
1167
1169
  }
package/dist/schemas/onchain_operations_contact.schema.json CHANGED
@@ -348,7 +348,7 @@
348
348
  "type": {
349
349
  "type": "string",
350
350
  "const": "submission",
351
- "description": "Type of call response: submission"
351
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
352
352
  },
353
353
  "guard": {
354
354
  "type": "array",
@@ -357,11 +357,11 @@
357
357
  "properties": {
358
358
  "object": {
359
359
  "type": "string",
360
- "description": "Guard object name or ID."
360
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
361
361
  },
362
362
  "impack": {
363
363
  "type": "boolean",
364
- "description": "Whether the verification result of this Guard participates in the final verification logic. If true, the verification result of this Guard will be included in the final verification result; if false, the verification result of this Guard will not be included."
364
+ "description": "Whether this Guard's verification result participates in the final logic. Constraint: if false, the Guard is checked but does not block the operation. Example: true"
365
365
  }
366
366
  },
367
367
  "required": [
@@ -369,7 +369,8 @@
369
369
  "impack"
370
370
  ],
371
371
  "additionalProperties": false
372
- }
372
+ },
373
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
373
374
  },
374
375
  "submission": {
375
376
  "type": "array",
@@ -378,7 +379,7 @@
378
379
  "properties": {
379
380
  "guard": {
380
381
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
381
- "description": "Guard object name or ID."
382
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
382
383
  },
383
384
  "submission": {
384
385
  "type": "array",
@@ -830,7 +831,7 @@
830
831
  "additionalProperties": false,
831
832
  "description": "Guard table item"
832
833
  },
833
- "description": "User-submitted data required for Guard verification."
834
+ "description": "User-submitted data matching the Guard's required fields. Relation: structure must match the Guard table's column definitions. Example: [{field:'delivery_proof', value:'Qm...'}]"
834
835
  }
835
836
  },
836
837
  "required": [
@@ -838,8 +839,9 @@
838
839
  "submission"
839
840
  ],
840
841
  "additionalProperties": false,
841
- "description": "Permission guard submission data."
842
- }
842
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
843
+ },
844
+ "description": "User-submitted data for each Guard. Relation: one entry per Guard in the guard array; fill submission fields and resubmit via call_with_submission."
843
845
  }
844
846
  },
845
847
  "required": [
@@ -848,7 +850,7 @@
848
850
  "submission"
849
851
  ],
850
852
  "additionalProperties": false,
851
- "description": "Guard verification submission data required to complete an operation. Contains: (1) 'guard' - array of Guard objects to verify, each with an object ID and an 'impack' flag indicating if its result affects the final outcome; (2) 'submission' - array of user data submissions matching the Guard's requirements. The operation proceeds only after all Guards with impack=true are successfully verified."
853
+ "description": "Guard verification required. The operation was blocked because one or more Guards require user-submitted data. Fill the submission array and resubmit. Semantic status is 'pending_input'."
852
854
  }
853
855
  }
854
856
  }
package/dist/schemas/onchain_operations_demand.schema.json CHANGED
@@ -479,7 +479,7 @@
479
479
  "type": {
480
480
  "type": "string",
481
481
  "const": "submission",
482
- "description": "Type of call response: submission"
482
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
483
483
  },
484
484
  "guard": {
485
485
  "type": "array",
@@ -488,11 +488,11 @@
488
488
  "properties": {
489
489
  "object": {
490
490
  "type": "string",
491
- "description": "Guard object name or ID."
491
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
492
492
  },
493
493
  "impack": {
494
494
  "type": "boolean",
495
- "description": "Whether the verification result of this Guard participates in the final verification logic. If true, the verification result of this Guard will be included in the final verification result; if false, the verification result of this Guard will not be included."
495
+ "description": "Whether this Guard's verification result participates in the final logic. Constraint: if false, the Guard is checked but does not block the operation. Example: true"
496
496
  }
497
497
  },
498
498
  "required": [
@@ -500,7 +500,8 @@
500
500
  "impack"
501
501
  ],
502
502
  "additionalProperties": false
503
- }
503
+ },
504
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
504
505
  },
505
506
  "submission": {
506
507
  "type": "array",
@@ -509,7 +510,7 @@
509
510
  "properties": {
510
511
  "guard": {
511
512
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
512
- "description": "Guard object name or ID."
513
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
513
514
  },
514
515
  "submission": {
515
516
  "type": "array",
@@ -961,7 +962,7 @@
961
962
  "additionalProperties": false,
962
963
  "description": "Guard table item"
963
964
  },
964
- "description": "User-submitted data required for Guard verification."
965
+ "description": "User-submitted data matching the Guard's required fields. Relation: structure must match the Guard table's column definitions. Example: [{field:'delivery_proof', value:'Qm...'}]"
965
966
  }
966
967
  },
967
968
  "required": [
@@ -969,8 +970,9 @@
969
970
  "submission"
970
971
  ],
971
972
  "additionalProperties": false,
972
- "description": "Permission guard submission data."
973
- }
973
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
974
+ },
975
+ "description": "User-submitted data for each Guard. Relation: one entry per Guard in the guard array; fill submission fields and resubmit via call_with_submission."
974
976
  }
975
977
  },
976
978
  "required": [
@@ -979,7 +981,7 @@
979
981
  "submission"
980
982
  ],
981
983
  "additionalProperties": false,
982
- "description": "Guard verification submission data required to complete an operation. Contains: (1) 'guard' - array of Guard objects to verify, each with an object ID and an 'impack' flag indicating if its result affects the final outcome; (2) 'submission' - array of user data submissions matching the Guard's requirements. The operation proceeds only after all Guards with impack=true are successfully verified."
984
+ "description": "Guard verification required. The operation was blocked because one or more Guards require user-submitted data. Fill the submission array and resubmit. Semantic status is 'pending_input'."
983
985
  }
984
986
  }
985
987
  }
package/dist/schemas/onchain_operations_gen_passport.schema.json CHANGED
@@ -50,7 +50,7 @@
50
50
  "type": {
51
51
  "type": "string",
52
52
  "const": "submission",
53
- "description": "Type of call response: submission"
53
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
54
54
  },
55
55
  "guard": {
56
56
  "type": "array",
@@ -59,11 +59,11 @@
59
59
  "properties": {
60
60
  "object": {
61
61
  "$ref": "#/definitions/data/properties/guard/anyOf/0",
62
- "description": "Guard object name or ID."
62
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
63
63
  },
64
64
  "impack": {
65
65
  "type": "boolean",
66
- "description": "Whether the verification result of this Guard participates in the final verification logic. If true, the verification result of this Guard will be included in the final verification result; if false, the verification result of this Guard will not be included."
66
+ "description": "Whether this Guard's verification result participates in the final logic. Constraint: if false, the Guard is checked but does not block the operation. Example: true"
67
67
  }
68
68
  },
69
69
  "required": [
@@ -71,7 +71,8 @@
71
71
  "impack"
72
72
  ],
73
73
  "additionalProperties": false
74
- }
74
+ },
75
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
75
76
  },
76
77
  "submission": {
77
78
  "type": "array",
@@ -80,7 +81,7 @@
80
81
  "properties": {
81
82
  "guard": {
82
83
  "$ref": "#/definitions/data/properties/guard/anyOf/0",
83
- "description": "Guard object name or ID."
84
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
84
85
  },
85
86
  "submission": {
86
87
  "type": "array",
@@ -532,7 +533,7 @@
532
533
  "additionalProperties": false,
533
534
  "description": "Guard table item"
534
535
  },
535
- "description": "User-submitted data required for Guard verification."
536
+ "description": "User-submitted data matching the Guard's required fields. Relation: structure must match the Guard table's column definitions. Example: [{field:'delivery_proof', value:'Qm...'}]"
536
537
  }
537
538
  },
538
539
  "required": [
@@ -540,8 +541,9 @@
540
541
  "submission"
541
542
  ],
542
543
  "additionalProperties": false,
543
- "description": "Permission guard submission data."
544
- }
544
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
545
+ },
546
+ "description": "User-submitted data for each Guard. Relation: one entry per Guard in the guard array; fill submission fields and resubmit via call_with_submission."
545
547
  }
546
548
  },
547
549
  "required": [
@@ -637,7 +639,7 @@
637
639
  "type": {
638
640
  "type": "string",
639
641
  "const": "submission",
640
- "description": "Type of call response: submission"
642
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
641
643
  },
642
644
  "guard": {
643
645
  "type": "array",
@@ -646,11 +648,11 @@
646
648
  "properties": {
647
649
  "object": {
648
650
  "type": "string",
649
- "description": "Guard object name or ID."
651
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
650
652
  },
651
653
  "impack": {
652
654
  "type": "boolean",
653
- "description": "Whether the verification result of this Guard participates in the final verification logic. If true, the verification result of this Guard will be included in the final verification result; if false, the verification result of this Guard will not be included."
655
+ "description": "Whether this Guard's verification result participates in the final logic. Constraint: if false, the Guard is checked but does not block the operation. Example: true"
654
656
  }
655
657
  },
656
658
  "required": [
@@ -658,7 +660,8 @@
658
660
  "impack"
659
661
  ],
660
662
  "additionalProperties": false
661
- }
663
+ },
664
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
662
665
  },
663
666
  "submission": {
664
667
  "type": "array",
@@ -667,7 +670,7 @@
667
670
  "properties": {
668
671
  "guard": {
669
672
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
670
- "description": "Guard object name or ID."
673
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
671
674
  },
672
675
  "submission": {
673
676
  "type": "array",
@@ -1119,7 +1122,7 @@
1119
1122
  "additionalProperties": false,
1120
1123
  "description": "Guard table item"
1121
1124
  },
1122
- "description": "User-submitted data required for Guard verification."
1125
+ "description": "User-submitted data matching the Guard's required fields. Relation: structure must match the Guard table's column definitions. Example: [{field:'delivery_proof', value:'Qm...'}]"
1123
1126
  }
1124
1127
  },
1125
1128
  "required": [
@@ -1127,8 +1130,9 @@
1127
1130
  "submission"
1128
1131
  ],
1129
1132
  "additionalProperties": false,
1130
- "description": "Permission guard submission data."
1131
- }
1133
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
1134
+ },
1135
+ "description": "User-submitted data for each Guard. Relation: one entry per Guard in the guard array; fill submission fields and resubmit via call_with_submission."
1132
1136
  }
1133
1137
  },
1134
1138
  "required": [
@@ -1137,7 +1141,7 @@
1137
1141
  "submission"
1138
1142
  ],
1139
1143
  "additionalProperties": false,
1140
- "description": "Guard verification submission data required to complete an operation. Contains: (1) 'guard' - array of Guard objects to verify, each with an object ID and an 'impack' flag indicating if its result affects the final outcome; (2) 'submission' - array of user data submissions matching the Guard's requirements. The operation proceeds only after all Guards with impack=true are successfully verified."
1144
+ "description": "Guard verification required. The operation was blocked because one or more Guards require user-submitted data. Fill the submission array and resubmit. Semantic status is 'pending_input'."
1141
1145
  }
1142
1146
  }
1143
1147
  }
package/dist/schemas/onchain_operations_guard.schema.json CHANGED
@@ -206,7 +206,7 @@
206
206
  "type": {
207
207
  "type": "string",
208
208
  "const": "submission",
209
- "description": "Type of call response: submission"
209
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
210
210
  },
211
211
  "guard": {
212
212
  "type": "array",
@@ -215,11 +215,11 @@
215
215
  "properties": {
216
216
  "object": {
217
217
  "type": "string",
218
- "description": "Guard object name or ID."
218
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
219
219
  },
220
220
  "impack": {
221
221
  "type": "boolean",
222
- "description": "Whether the verification result of this Guard participates in the final verification logic. If true, the verification result of this Guard will be included in the final verification result; if false, the verification result of this Guard will not be included."
222
+ "description": "Whether this Guard's verification result participates in the final logic. Constraint: if false, the Guard is checked but does not block the operation. Example: true"
223
223
  }
224
224
  },
225
225
  "required": [
@@ -227,7 +227,8 @@
227
227
  "impack"
228
228
  ],
229
229
  "additionalProperties": false
230
- }
230
+ },
231
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
231
232
  },
232
233
  "submission": {
233
234
  "type": "array",
@@ -236,7 +237,7 @@
236
237
  "properties": {
237
238
  "guard": {
238
239
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
239
- "description": "Guard object name or ID."
240
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
240
241
  },
241
242
  "submission": {
242
243
  "type": "array",
@@ -688,7 +689,7 @@
688
689
  "additionalProperties": false,
689
690
  "description": "Guard table item"
690
691
  },
691
- "description": "User-submitted data required for Guard verification."
692
+ "description": "User-submitted data matching the Guard's required fields. Relation: structure must match the Guard table's column definitions. Example: [{field:'delivery_proof', value:'Qm...'}]"
692
693
  }
693
694
  },
694
695
  "required": [
@@ -696,8 +697,9 @@
696
697
  "submission"
697
698
  ],
698
699
  "additionalProperties": false,
699
- "description": "Permission guard submission data."
700
- }
700
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
701
+ },
702
+ "description": "User-submitted data for each Guard. Relation: one entry per Guard in the guard array; fill submission fields and resubmit via call_with_submission."
701
703
  }
702
704
  },
703
705
  "required": [
@@ -706,7 +708,7 @@
706
708
  "submission"
707
709
  ],
708
710
  "additionalProperties": false,
709
- "description": "Guard verification submission data required to complete an operation. Contains: (1) 'guard' - array of Guard objects to verify, each with an object ID and an 'impack' flag indicating if its result affects the final outcome; (2) 'submission' - array of user data submissions matching the Guard's requirements. The operation proceeds only after all Guards with impack=true are successfully verified."
711
+ "description": "Guard verification required. The operation was blocked because one or more Guards require user-submitted data. Fill the submission array and resubmit. Semantic status is 'pending_input'."
710
712
  }
711
713
  }
712
714
  }