@wowok/agent-mcp 2.5.3 → 2.5.5

package/dist/tools/index.js

@@ -32,7 +32,7 @@ export const TOOL_REGISTRY = [
         handler: handleOnchainOperations,
         config: {
             title: "⛓️ On-chain Operations",
-            description: "On-chain operations for WoWok object: service (marketplace listings), machine (workflow templates), progress (order tracking), repository (on-chain database), arbitration (dispute resolution), contact (IM management), treasury (team funds), reward (incentive pools), allocation (auto-distribution), permission (access control), guard (programmable trust rules), personal (public profile), payment (direct coin transfers), demand (service requests), order (order management), gen_passport (verified credentials), proof (on-chain proof objects), gen_proof (generate proof shortcut).\n\n💡 Schema hint: Use schema_query with action='get' and name='onchain_operations' to retrieve the complete parameter schema. For individual operation schemas (e.g., 'onchain_operations_permission'), use schema_query with action='list_operations' to see all available operation schemas.",
+            description: "On-chain operations for WoWok object: service (marketplace listings), machine (workflow templates), progress (order tracking), repository (on-chain database), arbitration (dispute resolution), contact (IM management), treasury (team funds), reward (incentive pools), allocation (auto-distribution), permission (access control), guard (programmable trust rules), personal (public profile), payment (direct coin transfers), demand (service requests), order (order management), gen_passport (verified credentials), proof (on-chain proof objects), gen_proof (generate proof shortcut).\n\n📌 Project association: Pass env.project='<prefix>' to auto-tag the object on-chain AND auto-associate it to the SQLite project (created objects are automatically added). For complex builds, create a project first (project_operation action='create_project'). For single objects, just pass env.project. See PROJECT ASSOCIATION POLICY in system prompt.\n\n💡 Schema hint: Use schema_query with action='get' and name='onchain_operations' to retrieve the complete parameter schema. For individual operation schemas (e.g., 'onchain_operations_permission'), use schema_query with action='list_operations' to see all available operation schemas.",
             inputSchema: OnchainOperationsSchema,
             outputSchema: CallOutputSchema,
             annotations: { readOnlyHint: false, destructiveHint: true, idempotentHint: false, openWorldHint: true },
@@ -259,57 +259,43 @@ export const TOOL_REGISTRY = [
         name: "project_operation",
         handler: handleProjectOperation,
         config: {
-            title: "🗂️ Project - 5-Stage Deployment & Object Graph",
-            description: "Project-based deployment service — manage the local object dependency graph (DAG) AND guide users " +
-                "through the 5-stage project deployment workflow. All data comes from local marks tagged " +
-                "`project:<prefix>` (auto-injected by the ProjectService when enabled, default ON).\n\n" +
+            title: "🗂️ Project - Entity Management & Evaluation",
+            description: "Project management service — manage projects as first-class entities with SQLite persistence, " +
+                "rigid project-object relationships, three-pathway graph construction, and a dual rule-based + " +
+                "LLM-assisted evaluation engine.\n\n" +
+                "📌 Project policy: Complex builds → auto-create project first + check for similar projects. " +
+                "Single object → remind user to add to a project. " +
+                "Consumer → create_project_from_onchain + evaluate before buying.\n\n" +
                 "═══════════════════════════════════════════════════════════════\n" +
-                "  PROJECT-BASED DEPLOYMENT — 5-STAGE WORKFLOW (C1-C4)\n" +
+                "  PROJECT ENTITY + EVALUATION (15 actions, GLM6)\n" +
                 "═══════════════════════════════════════════════════════════════\n" +
-                "When a user wants to build/deploy a service, follow these 5 stages IN ORDER. " +
-                "Each stage's output tells you the next action to call:\n\n" +
-                "  Stage 1: Project Naming\n" +
-                "    → Use `project` + `version` params to name the project (e.g. myshop_v1).\n" +
-                "  Stage 2: Business Puzzle (action='analyze_intent')\n" +
-                "    → Input: user_intent (natural language), industry hint.\n" +
-                "    → Output: ODG (object dependency graph), puzzles, missing fields, next_step.\n" +
-                "    → Guide user to fill missing fields, then proceed to Stage 3.\n" +
-                "  Stage 3: Risk Calibration (action='aggregate_risks')\n" +
-                "    → Input: puzzles from Stage 2.\n" +
-                "    → Output: risk findings, can_proceed flag.\n" +
-                "    → CRITICAL risks block; HIGH/MEDIUM/LOW only warn. Fix CRITICAL before proceeding.\n" +
-                "  Stage 4: Deployment Doc (action='generate_deployment_doc')\n" +
-                "    → Input: objects, edges, steps (topological plan from Stage 2-3).\n" +
-                "    → Output: markdown deployment doc, D-01..D-18 scanner checks, can_proceed.\n" +
-                "    → 0 D-errors required before Stage 5.\n" +
-                "  Stage 5: Substep Trace (action='trace_substeps')\n" +
-                "    → Input: substeps (from deployment doc), network (testnet/mainnet).\n" +
-                "    → Output: coherence check, D-10 substep linkage, can_proceed.\n" +
-                "    → Execute each substep via onchain_operations, record outcomes.\n\n" +
-                "  Status Query (action='get_project_status')\n" +
-                "    → Input: project, version.\n" +
-                "    → Output: current stage (1-5), stage_name, next_action, can_proceed.\n" +
-                "    → Call anytime to check which stage the project is in and what to do next.\n\n" +
-                "Correct object creation order (topological): Permission → Allocation → Guard → Machine → Service.\n" +
-                "All objects created as draft (publish=false) first; publish Machine before Service (last).\n\n" +
+                "  • list_projects — List all projects (with object count + types). Supports filter_status, filter_perspective, filter_network.\n" +
+                "  • create_project — Create a new project (producer/consumer/both, bound to a network).\n" +
+                "  • create_project_from_onchain — Create a consumer project from an on-chain Service address (auto-discovers objects + graph).\n" +
+                "  • update_project — Update project metadata, status, labels, service address, etc.\n" +
+                "  • get_project_detail — Get full project detail (objects, graph edges, evaluations, versions).\n" +
+                "  • add_object — Add an on-chain object to a project (by address or LocalMark name).\n" +
+                "  • remove_object — Remove an object from a project.\n" +
+                "  • create_version — Create a project version (e.g. 'v2') with optional fork from a source version.\n" +
+                "  • build_graph — Build relationship graph via 3 pathways (internal refs, Registrar, potential). Configurable depth.\n" +
+                "  • get_graph — Get persisted graph edges.\n" +
+                "  • evaluate_project — Evaluate project (risk/trust/completeness = rule-based; value/worth_buying = LLM-assisted with prompt).\n" +
+                "  • save_evaluation — Save an LLM-produced evaluation result.\n" +
+                "  • compare_projects — Compare multiple projects by evaluation type.\n" +
+                "  • refresh_objects — Refresh object cache from chain (batch query, rate-limited).\n" +
+                "  • get_object_diff — Get field-level diff of an object between two timestamps.\n\n" +
                 "═══════════════════════════════════════════════════════════════\n" +
-                "  GRAPH QUERY ACTIONS (10)\n" +
+                "  CONTEXT ASSEMBLY (1 action)\n" +
                 "═══════════════════════════════════════════════════════════════\n" +
-                "  • list_projects — List all discovered projects with object counts.\n" +
-                "  • list_objects — List objects in a project (requires `project` param).\n" +
-                "  • shareable — List cross-project reusable objects (common Permission, 3rd-party Arb).\n" +
-                "  • dependencies — Trace forward dependencies of an object (BFS + dangling refs).\n" +
-                "  • referenced_by — Reverse query: who references this object?\n" +
-                "  • pre_publish_check — Pre-publish sanity check (dangling deps + cycles).\n" +
-                "  • cross_project_refs — Find edges crossing project boundaries.\n" +
-                "  • graph_stats — Graph statistics (node/edge counts, cycles, dangling deps).\n" +
-                "  • save_graph — Save graph to ~/.wowok/project-graph.json.\n" +
-                "  • load_graph — Load graph from file (restore after restart).\n\n" +
+                "  • assemble_context — Query on-chain object states + extract embedded history + optional events, " +
+                "and assemble a structured semantic context for LLM consumption. Required: context_objects (array of IDs/names).\n\n" +
+                "Correct object creation order (topological): Permission → Allocation → Guard → Machine → Service.\n" +
+                "All objects created as draft (publish=false) first; publish Machine before Service (last).\n\n" +
                 "💡 Schema hint: Use schema_query with action='get' and name='project_operation' for exact field definitions.",
             inputSchema: ProjectOperationInputSchema,
             outputSchema: ProjectOperationOutputSchema,
             annotations: { readOnlyHint: false, destructiveHint: false, idempotentHint: false, openWorldHint: false },
-            _meta: createToolMeta("project", ["project", "namespace", "graph", "dag", "dependency", "reference", "organization", "deployment", "5-stage", "analyze_intent", "aggregate_risks", "deployment_doc", "trace_substeps", "puzzle", "risk", "odg"]),
+            _meta: createToolMeta("project", ["project", "entity", "sqlite", "graph", "evaluation", "risk", "trust", "completeness", "worth_buying", "registrar", "diff", "version", "context", "assembly"]),
         },
     },
     {
@@ -329,7 +315,7 @@ export const TOOL_REGISTRY = [
                 "  • info — Get detailed info about a service (requires `service` param).\n\n" +
                 "Services:\n" +
                 "  • confirm_gate — Safety Confirmation Gate (default ON)\n" +
-                "  • project_service — Project Namespace + Dependency Graph (default ON)\n" +
+                "  • project_service — On-chain project tag auto-injection (default ON). When ON, objects created via onchain_operations are auto-tagged with project:<prefix> for on-chain grouping. Use project_operation for SQLite-based project management (evaluation, graph, versioning).\n" +
                 "  • harness — L4 Verify/Recover Loop (default OFF)\n" +
                 "  • graph_persist — Graph Persistence to File (default OFF)\n" +
                 "  • semantic_rich — Semantic Layer Enrichment Reminder (default ON)\n" +
@@ -417,7 +403,7 @@ const WOWOK_TOOL_DESCRIPTION = [
     "  wowok_buildin_info — Protocol constants, built-in permissions, bridge tokens.",
     "  schema_query — Query JSON schemas for any sub-tool (action: list/get/get_output/search).",
     "  bridge_operation — Cross-chain bridge between WOW and EVM (mainnet only).",
-    "  project_operation — 5-stage project deployment workflow (C1-C4 + graph queries).",
+    "  project_operation — Project entity management (SQLite) + 3-pathway graph + evaluation engine.",
     "  config_operation — Runtime service toggles (confirm_gate, harness, etc.).",
     "  trust_score — Service trust/risk assessment (0-100 score, 5 dimensions).",
     "",
@@ -438,16 +424,59 @@ const WOWOK_TOOL_DESCRIPTION = [
     "    4. CACHE the schema in your context for future calls to the SAME sub-tool",
     "  You should only need to see each sub-tool's schema once per conversation.",
     "",
-    "PROJECT-BASED DEPLOYMENT (5 stages):",
-    "  Stage 1: Project naming (provide project + version params)",
-    "  Stage 2: project_operation action='analyze_intent' → ODG + puzzles",
-    "  Stage 3: project_operation action='aggregate_risks' → risk findings",
-    "  Stage 4: project_operation action='generate_deployment_doc' → deployment doc",
-    "  Stage 5: project_operation action='trace_substeps' → substep verification",
-    "  Status: project_operation action='get_project_status' → current stage + next action",
+    "PROJECT MANAGEMENT (SQLite-based):",
+    "  project_operation action='list_projects' → list all projects with object counts",
+    "  project_operation action='create_project' → create a new project (producer/consumer/both)",
+    "  project_operation action='get_project_detail' → full project info (objects, graph, evaluations, versions)",
+    "  project_operation action='build_graph' → build 3-pathway relationship graph",
+    "  project_operation action='evaluate_project' → rule-based (risk/trust/completeness) or LLM-assisted (value/worth_buying)",
+    "  project_operation action='assemble_context' → assemble semantic context for LLM consumption",
+    "",
+    "═══════════════════════════════════════════════════════════════",
+    "PROJECT ASSOCIATION POLICY (context-aware, read before build/buy):",
+    "═══════════════════════════════════════════════════════════════",
+    "",
+    "Projects are the core organizing unit for all WoWok workflows. The policy is context-aware:",
+    "",
+    "CASE 1 — COMPLEX REQUIREMENT (user wants to build/deploy a full service):",
+    "  Examples: '搭建旅行地陪服务', '开一个玩具店', '创建租赁服务'",
+    "  → You MUST auto-create a project FIRST, then create objects.",
+    "  → Check for similar existing projects first: project_operation action='list_projects'",
+    "    If similar projects exist (same industry), remind the user: '发现类似项目 X, 是否复用或新建?'",
+    "  → Workflow:",
+    "    1. project_operation action='create_project' (perspective='producer', project_industry=<best match>)",
+    "    2. Create on-chain objects via onchain_operations with env.project='<prefix>' (auto-tags + auto-associates to SQLite project)",
+    "    3. After EACH creation, objects are auto-added to the project (via env.project)",
+    "    4. project_operation action='build_graph' — build 3-pathway relationship graph",
+    "    5. project_operation action='evaluate_project' (completeness → R1-R12 check, then risk)",
+    "    6. Report results, fix critical findings, then publish Service",
+    "",
+    "CASE 2 — SINGLE OBJECT CREATION (user wants one specific object):",
+    "  Examples: '创建一个Permission', '添加一个Contact', '建一个Guard'",
+    "  → Do NOT auto-create a project. If the user has an existing project, create with env.project='<prefix>' to auto-associate.",
+    "  → If no existing project, after creation, REMIND the user:",
+    "    '此对象已创建。建议将其加入一个项目以便管理: project_operation action=\"add_object\"",
+    "    如还没有项目, 可用 action=\"create_project\" 新建。现有项目: [list projects if any]'",
+    "  → If the user then says 'yes, create a project' or 'add to project X', proceed accordingly.",
+    "",
+    "CASE 3 — CONSUMER FLOW (user wants to buy/evaluate a service):",
+    "  → Suggest: project_operation action='create_project_from_onchain' (auto-discovers objects + graph)",
+    "  → Then: project_operation action='evaluate_project' (risk → trust → worth_buying)",
+    "  → Report findings, let user decide whether to proceed with onchain_operations service_buy",
+    "",
+    "CASE 4 — SIMPLE QUERY (user wants to check object info, balance, etc.):",
+    "  → No project needed. Proceed directly with the query.",
     "",
-    "Correct object creation order: Permission → Allocation → Guard → Machine → Service.",
-    "All objects created as draft (publish=false) first; publish Machine before Service (last).",
+    "INDUSTRY MATCHING (for create_project project_industry param):",
+    "  travel → tour guides, transportation, accommodation, sightseeing",
+    "  retail → shops, e-commerce, physical goods",
+    "  service → professional services, consulting, design",
+    "  rental → equipment rental, property rental",
+    "  freelance → freelance work, gig economy",
+    "  education → courses, training, tutoring",
+    "  subscription → subscription services, memberships",
+    "  general → fallback for unclear industry",
+    "═══════════════════════════════════════════════════════════════",
 ].join("\n");
 function formatZodErrors(error) {
     return error.issues.map(issue => {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wowok/agent-mcp",
-  "version": "2.5.3",
+  "version": "2.5.5",
   "description": "Making It Easy for AI Agents to Communicate, Collaborate, Trade, and Trust.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -50,7 +50,7 @@
   "license": "Apache-2.0",
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.29.0",
-    "@wowok/wowok": "2.5.2",
+    "@wowok/wowok": "2.5.5",
     "lodash": "^4.18.1",
     "zod": "^3.25.76",
     "zod-to-json-schema": "^3.25.2"