@wowok/agent-mcp 2.3.13 → 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 (92) 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/reward.d.ts +6 -6
  46. package/dist/schema/call/semantic.d.ts +23 -0
  47. package/dist/schema/call/semantic.js +764 -0
  48. package/dist/schema/call/service.d.ts +142 -142
  49. package/dist/schema/call/treasury.d.ts +204 -204
  50. package/dist/schema/local/index.d.ts +113 -2
  51. package/dist/schema/local/index.js +11 -1
  52. package/dist/schema/messenger/index.d.ts +416 -92
  53. package/dist/schema/messenger/index.js +9 -0
  54. package/dist/schema/operations.d.ts +988 -495
  55. package/dist/schema/operations.js +14 -3
  56. package/dist/schema/query/index.d.ts +346 -342
  57. package/dist/schema/query/index.js +4 -1
  58. package/dist/schemas/account_operation.output.json +3 -0
  59. package/dist/schemas/account_operation.schema.json +1 -1
  60. package/dist/schemas/index.json +1 -1
  61. package/dist/schemas/local_info_operation.output.json +3 -0
  62. package/dist/schemas/local_mark_operation.output.json +3 -0
  63. package/dist/schemas/messenger_operation.output.json +21 -0
  64. package/dist/schemas/messenger_operation.schema.json +21 -0
  65. package/dist/schemas/onchain_events.output.json +3 -0
  66. package/dist/schemas/onchain_operations.output.json +464 -21
  67. package/dist/schemas/onchain_operations.schema.json +21 -17
  68. package/dist/schemas/onchain_operations_allocation.schema.json +11 -9
  69. package/dist/schemas/onchain_operations_arbitration.schema.json +11 -9
  70. package/dist/schemas/onchain_operations_contact.schema.json +11 -9
  71. package/dist/schemas/onchain_operations_demand.schema.json +11 -9
  72. package/dist/schemas/onchain_operations_gen_passport.schema.json +21 -17
  73. package/dist/schemas/onchain_operations_guard.schema.json +11 -9
  74. package/dist/schemas/onchain_operations_machine.schema.json +11 -9
  75. package/dist/schemas/onchain_operations_order.schema.json +11 -9
  76. package/dist/schemas/onchain_operations_payment.schema.json +11 -9
  77. package/dist/schemas/onchain_operations_permission.schema.json +11 -9
  78. package/dist/schemas/onchain_operations_personal.schema.json +11 -9
  79. package/dist/schemas/onchain_operations_progress.schema.json +11 -9
  80. package/dist/schemas/onchain_operations_repository.schema.json +11 -9
  81. package/dist/schemas/onchain_operations_reward.schema.json +11 -9
  82. package/dist/schemas/onchain_operations_service.schema.json +11 -9
  83. package/dist/schemas/onchain_operations_treasury.schema.json +11 -9
  84. package/dist/schemas/onchain_table_data.output.json +3 -0
  85. package/dist/schemas/query_toolkit.schema.json +5 -1
  86. package/dist/telemetry/index.d.ts +19 -0
  87. package/dist/telemetry/index.js +112 -0
  88. package/dist/telemetry/redact.d.ts +2 -0
  89. package/dist/telemetry/redact.js +23 -0
  90. package/dist/telemetry/storage.d.ts +8 -0
  91. package/dist/telemetry/storage.js +80 -0
  92. package/package.json +6 -3
package/dist/schemas/onchain_operations_machine.schema.json CHANGED
@@ -807,7 +807,7 @@
807
807
  "type": {
808
808
  "type": "string",
809
809
  "const": "submission",
810
- "description": "Type of call response: submission"
810
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
811
811
  },
812
812
  "guard": {
813
813
  "type": "array",
@@ -816,11 +816,11 @@
816
816
  "properties": {
817
817
  "object": {
818
818
  "type": "string",
819
- "description": "Guard object name or ID."
819
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
820
820
  },
821
821
  "impack": {
822
822
  "type": "boolean",
823
- "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."
823
+ "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"
824
824
  }
825
825
  },
826
826
  "required": [
@@ -828,7 +828,8 @@
828
828
  "impack"
829
829
  ],
830
830
  "additionalProperties": false
831
- }
831
+ },
832
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
832
833
  },
833
834
  "submission": {
834
835
  "type": "array",
@@ -837,7 +838,7 @@
837
838
  "properties": {
838
839
  "guard": {
839
840
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
840
- "description": "Guard object name or ID."
841
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
841
842
  },
842
843
  "submission": {
843
844
  "type": "array",
@@ -1289,7 +1290,7 @@
1289
1290
  "additionalProperties": false,
1290
1291
  "description": "Guard table item"
1291
1292
  },
1292
- "description": "User-submitted data required for Guard verification."
1293
+ "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...'}]"
1293
1294
  }
1294
1295
  },
1295
1296
  "required": [
@@ -1297,8 +1298,9 @@
1297
1298
  "submission"
1298
1299
  ],
1299
1300
  "additionalProperties": false,
1300
- "description": "Permission guard submission data."
1301
- }
1301
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
1302
+ },
1303
+ "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."
1302
1304
  }
1303
1305
  },
1304
1306
  "required": [
@@ -1307,7 +1309,7 @@
1307
1309
  "submission"
1308
1310
  ],
1309
1311
  "additionalProperties": false,
1310
- "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."
1312
+ "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'."
1311
1313
  }
1312
1314
  }
1313
1315
  }
package/dist/schemas/onchain_operations_order.schema.json CHANGED
@@ -325,7 +325,7 @@
325
325
  "type": {
326
326
  "type": "string",
327
327
  "const": "submission",
328
- "description": "Type of call response: submission"
328
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
329
329
  },
330
330
  "guard": {
331
331
  "type": "array",
@@ -334,11 +334,11 @@
334
334
  "properties": {
335
335
  "object": {
336
336
  "type": "string",
337
- "description": "Guard object name or ID."
337
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
338
338
  },
339
339
  "impack": {
340
340
  "type": "boolean",
341
- "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."
341
+ "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"
342
342
  }
343
343
  },
344
344
  "required": [
@@ -346,7 +346,8 @@
346
346
  "impack"
347
347
  ],
348
348
  "additionalProperties": false
349
- }
349
+ },
350
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
350
351
  },
351
352
  "submission": {
352
353
  "type": "array",
@@ -355,7 +356,7 @@
355
356
  "properties": {
356
357
  "guard": {
357
358
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
358
- "description": "Guard object name or ID."
359
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
359
360
  },
360
361
  "submission": {
361
362
  "type": "array",
@@ -807,7 +808,7 @@
807
808
  "additionalProperties": false,
808
809
  "description": "Guard table item"
809
810
  },
810
- "description": "User-submitted data required for Guard verification."
811
+ "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...'}]"
811
812
  }
812
813
  },
813
814
  "required": [
@@ -815,8 +816,9 @@
815
816
  "submission"
816
817
  ],
817
818
  "additionalProperties": false,
818
- "description": "Permission guard submission data."
819
- }
819
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
820
+ },
821
+ "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."
820
822
  }
821
823
  },
822
824
  "required": [
@@ -825,7 +827,7 @@
825
827
  "submission"
826
828
  ],
827
829
  "additionalProperties": false,
828
- "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."
830
+ "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'."
829
831
  }
830
832
  }
831
833
  }
package/dist/schemas/onchain_operations_payment.schema.json CHANGED
@@ -212,7 +212,7 @@
212
212
  "type": {
213
213
  "type": "string",
214
214
  "const": "submission",
215
- "description": "Type of call response: submission"
215
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
216
216
  },
217
217
  "guard": {
218
218
  "type": "array",
@@ -221,11 +221,11 @@
221
221
  "properties": {
222
222
  "object": {
223
223
  "type": "string",
224
- "description": "Guard object name or ID."
224
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
225
225
  },
226
226
  "impack": {
227
227
  "type": "boolean",
228
- "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."
228
+ "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"
229
229
  }
230
230
  },
231
231
  "required": [
@@ -233,7 +233,8 @@
233
233
  "impack"
234
234
  ],
235
235
  "additionalProperties": false
236
- }
236
+ },
237
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
237
238
  },
238
239
  "submission": {
239
240
  "type": "array",
@@ -242,7 +243,7 @@
242
243
  "properties": {
243
244
  "guard": {
244
245
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
245
- "description": "Guard object name or ID."
246
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
246
247
  },
247
248
  "submission": {
248
249
  "type": "array",
@@ -694,7 +695,7 @@
694
695
  "additionalProperties": false,
695
696
  "description": "Guard table item"
696
697
  },
697
- "description": "User-submitted data required for Guard verification."
698
+ "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...'}]"
698
699
  }
699
700
  },
700
701
  "required": [
@@ -702,8 +703,9 @@
702
703
  "submission"
703
704
  ],
704
705
  "additionalProperties": false,
705
- "description": "Permission guard submission data."
706
- }
706
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
707
+ },
708
+ "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."
707
709
  }
708
710
  },
709
711
  "required": [
@@ -712,7 +714,7 @@
712
714
  "submission"
713
715
  ],
714
716
  "additionalProperties": false,
715
- "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."
717
+ "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'."
716
718
  }
717
719
  }
718
720
  }
package/dist/schemas/onchain_operations_permission.schema.json CHANGED
@@ -583,7 +583,7 @@
583
583
  "type": {
584
584
  "type": "string",
585
585
  "const": "submission",
586
- "description": "Type of call response: submission"
586
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
587
587
  },
588
588
  "guard": {
589
589
  "type": "array",
@@ -592,11 +592,11 @@
592
592
  "properties": {
593
593
  "object": {
594
594
  "type": "string",
595
- "description": "Guard object name or ID."
595
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
596
596
  },
597
597
  "impack": {
598
598
  "type": "boolean",
599
- "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."
599
+ "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"
600
600
  }
601
601
  },
602
602
  "required": [
@@ -604,7 +604,8 @@
604
604
  "impack"
605
605
  ],
606
606
  "additionalProperties": false
607
- }
607
+ },
608
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
608
609
  },
609
610
  "submission": {
610
611
  "type": "array",
@@ -613,7 +614,7 @@
613
614
  "properties": {
614
615
  "guard": {
615
616
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
616
- "description": "Guard object name or ID."
617
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
617
618
  },
618
619
  "submission": {
619
620
  "type": "array",
@@ -1065,7 +1066,7 @@
1065
1066
  "additionalProperties": false,
1066
1067
  "description": "Guard table item"
1067
1068
  },
1068
- "description": "User-submitted data required for Guard verification."
1069
+ "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...'}]"
1069
1070
  }
1070
1071
  },
1071
1072
  "required": [
@@ -1073,8 +1074,9 @@
1073
1074
  "submission"
1074
1075
  ],
1075
1076
  "additionalProperties": false,
1076
- "description": "Permission guard submission data."
1077
- }
1077
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
1078
+ },
1079
+ "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."
1078
1080
  }
1079
1081
  },
1080
1082
  "required": [
@@ -1083,7 +1085,7 @@
1083
1085
  "submission"
1084
1086
  ],
1085
1087
  "additionalProperties": false,
1086
- "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."
1088
+ "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'."
1087
1089
  }
1088
1090
  }
1089
1091
  }
package/dist/schemas/onchain_operations_personal.schema.json CHANGED
@@ -777,7 +777,7 @@
777
777
  "type": {
778
778
  "type": "string",
779
779
  "const": "submission",
780
- "description": "Type of call response: submission"
780
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
781
781
  },
782
782
  "guard": {
783
783
  "type": "array",
@@ -786,11 +786,11 @@
786
786
  "properties": {
787
787
  "object": {
788
788
  "type": "string",
789
- "description": "Guard object name or ID."
789
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
790
790
  },
791
791
  "impack": {
792
792
  "type": "boolean",
793
- "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."
793
+ "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"
794
794
  }
795
795
  },
796
796
  "required": [
@@ -798,7 +798,8 @@
798
798
  "impack"
799
799
  ],
800
800
  "additionalProperties": false
801
- }
801
+ },
802
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
802
803
  },
803
804
  "submission": {
804
805
  "type": "array",
@@ -807,7 +808,7 @@
807
808
  "properties": {
808
809
  "guard": {
809
810
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
810
- "description": "Guard object name or ID."
811
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
811
812
  },
812
813
  "submission": {
813
814
  "type": "array",
@@ -1259,7 +1260,7 @@
1259
1260
  "additionalProperties": false,
1260
1261
  "description": "Guard table item"
1261
1262
  },
1262
- "description": "User-submitted data required for Guard verification."
1263
+ "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...'}]"
1263
1264
  }
1264
1265
  },
1265
1266
  "required": [
@@ -1267,8 +1268,9 @@
1267
1268
  "submission"
1268
1269
  ],
1269
1270
  "additionalProperties": false,
1270
- "description": "Permission guard submission data."
1271
- }
1271
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
1272
+ },
1273
+ "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."
1272
1274
  }
1273
1275
  },
1274
1276
  "required": [
@@ -1277,7 +1279,7 @@
1277
1279
  "submission"
1278
1280
  ],
1279
1281
  "additionalProperties": false,
1280
- "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."
1282
+ "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'."
1281
1283
  }
1282
1284
  }
1283
1285
  }
package/dist/schemas/onchain_operations_progress.schema.json CHANGED
@@ -246,7 +246,7 @@
246
246
  "type": {
247
247
  "type": "string",
248
248
  "const": "submission",
249
- "description": "Type of call response: submission"
249
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
250
250
  },
251
251
  "guard": {
252
252
  "type": "array",
@@ -255,11 +255,11 @@
255
255
  "properties": {
256
256
  "object": {
257
257
  "type": "string",
258
- "description": "Guard object name or ID."
258
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
259
259
  },
260
260
  "impack": {
261
261
  "type": "boolean",
262
- "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."
262
+ "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"
263
263
  }
264
264
  },
265
265
  "required": [
@@ -267,7 +267,8 @@
267
267
  "impack"
268
268
  ],
269
269
  "additionalProperties": false
270
- }
270
+ },
271
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
271
272
  },
272
273
  "submission": {
273
274
  "type": "array",
@@ -276,7 +277,7 @@
276
277
  "properties": {
277
278
  "guard": {
278
279
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
279
- "description": "Guard object name or ID."
280
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
280
281
  },
281
282
  "submission": {
282
283
  "type": "array",
@@ -728,7 +729,7 @@
728
729
  "additionalProperties": false,
729
730
  "description": "Guard table item"
730
731
  },
731
- "description": "User-submitted data required for Guard verification."
732
+ "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...'}]"
732
733
  }
733
734
  },
734
735
  "required": [
@@ -736,8 +737,9 @@
736
737
  "submission"
737
738
  ],
738
739
  "additionalProperties": false,
739
- "description": "Permission guard submission data."
740
- }
740
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
741
+ },
742
+ "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."
741
743
  }
742
744
  },
743
745
  "required": [
@@ -746,7 +748,7 @@
746
748
  "submission"
747
749
  ],
748
750
  "additionalProperties": false,
749
- "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."
751
+ "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'."
750
752
  }
751
753
  }
752
754
  }
package/dist/schemas/onchain_operations_repository.schema.json CHANGED
@@ -1070,7 +1070,7 @@
1070
1070
  "type": {
1071
1071
  "type": "string",
1072
1072
  "const": "submission",
1073
- "description": "Type of call response: submission"
1073
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
1074
1074
  },
1075
1075
  "guard": {
1076
1076
  "type": "array",
@@ -1079,11 +1079,11 @@
1079
1079
  "properties": {
1080
1080
  "object": {
1081
1081
  "type": "string",
1082
- "description": "Guard object name or ID."
1082
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
1083
1083
  },
1084
1084
  "impack": {
1085
1085
  "type": "boolean",
1086
- "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."
1086
+ "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"
1087
1087
  }
1088
1088
  },
1089
1089
  "required": [
@@ -1091,7 +1091,8 @@
1091
1091
  "impack"
1092
1092
  ],
1093
1093
  "additionalProperties": false
1094
- }
1094
+ },
1095
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
1095
1096
  },
1096
1097
  "submission": {
1097
1098
  "type": "array",
@@ -1100,7 +1101,7 @@
1100
1101
  "properties": {
1101
1102
  "guard": {
1102
1103
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
1103
- "description": "Guard object name or ID."
1104
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
1104
1105
  },
1105
1106
  "submission": {
1106
1107
  "type": "array",
@@ -1552,7 +1553,7 @@
1552
1553
  "additionalProperties": false,
1553
1554
  "description": "Guard table item"
1554
1555
  },
1555
- "description": "User-submitted data required for Guard verification."
1556
+ "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...'}]"
1556
1557
  }
1557
1558
  },
1558
1559
  "required": [
@@ -1560,8 +1561,9 @@
1560
1561
  "submission"
1561
1562
  ],
1562
1563
  "additionalProperties": false,
1563
- "description": "Permission guard submission data."
1564
- }
1564
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
1565
+ },
1566
+ "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."
1565
1567
  }
1566
1568
  },
1567
1569
  "required": [
@@ -1570,7 +1572,7 @@
1570
1572
  "submission"
1571
1573
  ],
1572
1574
  "additionalProperties": false,
1573
- "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."
1575
+ "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'."
1574
1576
  }
1575
1577
  }
1576
1578
  }
package/dist/schemas/onchain_operations_reward.schema.json CHANGED
@@ -450,7 +450,7 @@
450
450
  "type": {
451
451
  "type": "string",
452
452
  "const": "submission",
453
- "description": "Type of call response: submission"
453
+ "description": "Discriminator for this result variant. Constraint: always 'submission'. Example: 'submission'"
454
454
  },
455
455
  "guard": {
456
456
  "type": "array",
@@ -459,11 +459,11 @@
459
459
  "properties": {
460
460
  "object": {
461
461
  "type": "string",
462
- "description": "Guard object name or ID."
462
+ "description": "Guard object name or ID to verify against. Example: 'my-delivery-guard' or '0x123...'"
463
463
  },
464
464
  "impack": {
465
465
  "type": "boolean",
466
- "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."
466
+ "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"
467
467
  }
468
468
  },
469
469
  "required": [
@@ -471,7 +471,8 @@
471
471
  "impack"
472
472
  ],
473
473
  "additionalProperties": false
474
- }
474
+ },
475
+ "description": "Array of Guard objects to verify. Relation: each entry corresponds to a Guard bound to the operation."
475
476
  },
476
477
  "submission": {
477
478
  "type": "array",
@@ -480,7 +481,7 @@
480
481
  "properties": {
481
482
  "guard": {
482
483
  "$ref": "#/definitions/submission/properties/guard/items/properties/object",
483
- "description": "Guard object name or ID."
484
+ "description": "Guard object name or ID that requires submission data. Example: 'my-delivery-guard'"
484
485
  },
485
486
  "submission": {
486
487
  "type": "array",
@@ -932,7 +933,7 @@
932
933
  "additionalProperties": false,
933
934
  "description": "Guard table item"
934
935
  },
935
- "description": "User-submitted data required for Guard verification."
936
+ "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...'}]"
936
937
  }
937
938
  },
938
939
  "required": [
@@ -940,8 +941,9 @@
940
941
  "submission"
941
942
  ],
942
943
  "additionalProperties": false,
943
- "description": "Permission guard submission data."
944
- }
944
+ "description": "One Guard's submission data: the Guard to verify plus the user-provided data that satisfies its requirements."
945
+ },
946
+ "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."
945
947
  }
946
948
  },
947
949
  "required": [
@@ -950,7 +952,7 @@
950
952
  "submission"
951
953
  ],
952
954
  "additionalProperties": false,
953
- "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."
955
+ "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'."
954
956
  }
955
957
  }
956
958
  }