@wowok/agent-mcp 2.6.0 → 2.6.3

package/dist/schemas/project_operation.schema.json

@@ -29,13 +29,24 @@
             "get_object_diff",
             "delete_project",
             "assemble_context",
-            "generate_deployment_doc"
+            "get_machine_graph",
+            "get_guard_graph",
+            "generate_deployment_doc",
+            "pre_evaluate_check",
+            "verify_deployment",
+            "clone_project_to_network",
+            "migrate_network",
+            "migrate_to_mainnet",
+            "plan_object_edit",
+            "apply_object_edit",
+            "patch_machine_nodes",
+            "patch_guard_tree"
           ],
-          "description": "Action to perform. Two categories:\n1. Project Entity + Evaluation (15, GLM6): list_projects, create_project, create_project_from_onchain, update_project, get_project_detail, add_object, remove_object, create_version, build_graph, get_graph, evaluate_project, save_evaluation, compare_projects, refresh_objects, get_object_diff. Projects are first-class entities with SQLite persistence, rigid project-object relationships, three-pathway graph construction, and a dual rule-based + LLM-assisted evaluation engine.\n2. Context Assembly (1): assemble_context (query on-chain object states + extract embedded history + optional events, and assemble a structured semantic context for LLM consumption). Required input: context_objects (array of object IDs/names). Optional: include_events (query recent state-transition events)."
+          "description": "Action to perform. Two categories:\n1. Project Entity + Evaluation (15, GLM6): list_projects, create_project, create_project_from_onchain, update_project, get_project_detail, add_object, remove_object, create_version, build_graph, get_graph, evaluate_project, save_evaluation, compare_projects, refresh_objects, get_object_diff. Projects are first-class entities with SQLite persistence, rigid project-object relationships, three-pathway graph construction, and a dual rule-based + LLM-assisted evaluation engine.\n2. Context Assembly (1): assemble_context (query on-chain object states + extract embedded history + optional events, and assemble a structured semantic context for LLM consumption). Required input: context_objects (array of object IDs/names). Optional: include_events (query recent state-transition events).\n3. Cross-Network Migration (FIX-012): clone_project_to_network (or its alias migrate_network) copies a source project's object metadata to a new project bound to target_network. The 5-step migration workflow: 1) call clone_project_to_network (or migrate_network) with target_network to copy metadata, 2) re-run onchain_operations with env.network=target_network to deploy objects on-chain, 3) re-register LocalMark names with the SAME names on the target network (FIX-011 cross-network consistency), 4) update_project to set service_address on the new project, 5) build_graph to construct the new project's relationship graph."
         },
         "project": {
           "type": "string",
-          "description": "Project prefix (human-readable unique identifier). Used by create_version, build_graph, evaluate_project, etc. Takes precedence resolution: project_id > project (prefix)."
+          "description": "Project prefix (human-readable unique identifier). For create_project: OPTIONAL — if omitted, auto-derived from project_name (e.g. 'Twitch Service' → 'twitch_service'). For other actions (build_graph, evaluate_project, etc.): used to identify the project. Takes precedence resolution: project_id > project (prefix)."
         },
         "version": {
           "type": "string",
@@ -104,6 +115,7 @@
           "enum": [
             "general",
             "retail",
+            "retail_d2c",
             "service",
             "rental",
             "freelance",
@@ -112,7 +124,7 @@
             "subscription",
             "custom"
           ],
-          "description": "Industry tag for create_project. Drives template defaults."
+          "description": "Industry tag for create_project. Drives template defaults — when set (and not 'general'), the system auto-applies an industry blueprint with ~10 draft objects (Permission, Service, Machine, Guard, Treasury, Allocation, etc.) + graph edges, ready for deployment. Supported industries: 'general' (no template), 'retail', 'retail_d2c' (Direct-to-Consumer, e.g., Shopify — Allocation escrow + 2 Guards), 'service', 'rental', 'freelance', 'education', 'travel', 'subscription', 'custom'. Each industry preset embeds risk constraints (e.g., 'freelance' does NOT require compensation_fund, while 'rental'/'travel' do). Example: project_industry='freelance' creates a freelance-style blueprint with setting_locked_time ≥ 7d. Set skip_templates=true to bypass template application."
         },
         "project_perspective": {
           "type": "string",
@@ -142,6 +154,10 @@
           ],
           "description": "Network the project is bound to. A Service deployed to different networks are different projects. Defaults to 'testnet'."
         },
+        "skip_templates": {
+          "type": "boolean",
+          "description": "When true, create_project skips applying the industry template (no draft:* blueprint objects). Use this when you want a clean project with no pre-filled blueprint objects — useful for custom architectures that do not match any industry mode, or to avoid draft objects appearing in build_graph / evaluate_project before deployment. Defaults to false (templates applied)."
+        },
         "project_id": {
           "type": "string",
           "description": "Project UUID for update_project / get_project_detail / add_object / remove_object / create_version / build_graph / evaluate_project / refresh_objects. Takes precedence over 'project' (prefix) when both are given."
@@ -156,9 +172,17 @@
           ],
           "description": "New status for update_project. 'active' projects are live, 'archived' are read-only."
         },
+        "target_network": {
+          "type": "string",
+          "enum": [
+            "testnet",
+            "mainnet"
+          ],
+          "description": "Target network for clone_project_to_network (or its alias migrate_network). The source project's objects are copied to a new project bound to this network. The new project's prefix is '<source_prefix>_<target_network>' to avoid collision. See the action description for the full 5-step migration workflow (FIX-012)."
+        },
         "object_address": {
           "type": "string",
-          "description": "On-chain object address (0x...) for add_object / remove_object. For add_object, alternatively use object_name to resolve via LocalMark."
+          "description": "On-chain object address (0x followed by 32-64 hex chars) for add_object / remove_object. Also accepts the internal 'draft:<name>' sentinel used by create_project for blueprint objects not yet on-chain. For add_object, alternatively use object_name_add to resolve via LocalMark. H-06 fix: invalid formats are rejected at the handler level with a descriptive error."
         },
         "object_name_add": {
           "type": "string",
@@ -249,6 +273,12 @@
           "maximum": 5,
           "description": "Max recursion depth for Pathway 1 (internal reference derivation) in build_graph. Default 3."
         },
+        "depth": {
+          "type": "integer",
+          "minimum": 1,
+          "maximum": 5,
+          "description": "Alias for max_depth (build_graph). When both are set, max_depth takes precedence. Default 3."
+        },
         "enable_registrar": {
           "type": "boolean",
           "description": "Enable Pathway 2 (Registrar inbound query) in build_graph. Default true."
@@ -257,6 +287,10 @@
           "type": "boolean",
           "description": "Enable Pathway 3 (potential relationship detection) in build_graph. Default false."
         },
+        "async_mode": {
+          "type": "boolean",
+          "description": "When true, build_graph / evaluate_project runs in the background and returns { task_id } immediately. Poll query_task_status(task_id) to check progress and retrieve the result. Default false (synchronous). Use async_mode=true for large projects with enable_potential=true where build may take >10s."
+        },
         "evaluation_type": {
           "type": "string",
           "enum": [
@@ -270,7 +304,7 @@
         },
         "refresh_before_eval": {
           "type": "boolean",
-          "description": "When true, evaluate_project refreshes object cache from chain before evaluating. Default false."
+          "description": "When true (DEFAULT), evaluate_project refreshes object cache from chain before evaluating. Set to false ONLY for read-only checks where staleness is acceptable (e.g., quick comparisons). BUG-P0-2 fix: previously defaulted to false, causing stale Machine node_count and other dynamic-field-derived fields to produce false findings (e.g., 'Machine has no nodes'). Now defaults to true — set refresh_before_eval=false explicitly to skip refresh."
         },
         "eval_score": {
           "type": "number",
@@ -319,6 +353,50 @@
         "save": {
           "type": "boolean",
           "description": "When true (default), persist the generated MD to SQLite project_documents table for generate_deployment_doc."
+        },
+        "detail_level": {
+          "type": "string",
+          "enum": [
+            "summary",
+            "detailed",
+            "full"
+          ],
+          "description": "P2-03: Deployment document detail level (only for generate_deployment_doc). 'summary' (default): object name + type + key bindings (machine, permission, buy_guard, order_allocators). 'detailed': adds sale list, arbitration list, reward list. 'full': complete fields including stock, price, wip_hash, all config. Use 'summary' for quick review; request 'detailed' or 'full' only when deeper inspection is needed."
+        },
+        "object_kind": {
+          "type": "string",
+          "enum": [
+            "machine",
+            "guard"
+          ],
+          "description": "Object kind for plan_object_edit. 'machine' = Machine workflow directed graph (cycles allowed), 'guard' = Guard computation tree. Required when action='plan_object_edit'. Inferred from action for patch_machine_nodes (always 'machine') and patch_guard_tree (always 'guard')."
+        },
+        "edit_format": {
+          "type": "string",
+          "enum": [
+            "tree_outline",
+            "json"
+          ],
+          "description": "Format of the edited content for plan_object_edit. 'tree_outline' (default): the indented Markdown outline produced by get_machine_graph / get_guard_graph (human-editable). 'json': raw JSON (machine-readable, for programmatic edits). Both formats are bidirectional with the parse functions in knowledge/machine-render.ts / guard-render.ts."
+        },
+        "edited_content": {
+          "type": "string",
+          "description": "Edited content for plan_object_edit. Must be in the format specified by edit_format. For 'tree_outline': the full tree_outline string from get_machine_graph/get_guard_graph with user edits. For 'json': a JSON string matching the Machine/Guard schema. The content is parsed + validated + diffed against the current on-chain state."
+        },
+        "plan_id": {
+          "type": "string",
+          "description": "Plan ID returned by plan_object_edit. Required for apply_object_edit. The plan is short-lived (10-minute TTL) and stored in-memory."
+        },
+        "expected_hash": {
+          "type": "string",
+          "description": "Expected hash returned by plan_object_edit. Required for apply_object_edit. Used for optimistic concurrency control: if the on-chain state changed between plan and apply, the hash will mismatch and apply will refuse to proceed (stale edit protection)."
+        },
+        "patch_operations": {
+          "type": "array",
+          "items": {
+            "type": "string"
+          },
+          "description": "Patch operations for patch_machine_nodes / patch_guard_tree. Each string is a single patch operation.\nMachine operations (13 total):\n  'add node <name>' | 'remove node <name>' | 'set description <node_name> <text...>'\n  'add edge <from> <to>' | 'remove edge <from> <to>' | 'set threshold <edge_from> <edge_to> <value>'\n  'add forward <edge_from> <edge_to> <forward_name>' | 'remove forward <edge_from> <edge_to> <forward_name>'\n  'set guard <edge_from> <edge_to> <forward_name> <guard_addr_or_name|none>'\n  'set permission <edge_from> <edge_to> <forward_name> <perm_index>'\n  'set operator <edge_from> <edge_to> <forward_name> <named_operator|none>'\n  'set weight <edge_from> <edge_to> <forward_name> <weight>'\n  'set retained_submission <edge_from> <edge_to> <forward_name> <comma_separated_indices|none>'\nGuard operations (8 total — see patch_guard_tree):\n  'add table <identifier> <name|none> <value_type> <b_submission> [json_value]'\n  'remove table <identifier>' | 'set table_value <identifier> [json_value|none]'\n  'set table_name <identifier> <name|none>' | 'set table_submission <identifier> <true|false>'\n  'set root <json_node>' | 'set rely <comma_separated_guard_addresses|none>'\nOperations are applied in order. Both patches are validated (validateMachine/validateGuard) before execution."
         }
       },
       "required": [