ofiere-openclaw-plugin 4.55.0 → 4.56.0

package/dist/src/prompt.js

@@ -31,92 +31,92 @@ const TOOL_SUMMARIES = {
 // These are used as tool descriptions in registerTools(), NOT in the system prompt.
 // The LLM sees them only when exploring available tools or preparing a tool call.
 export const TOOL_DOCS = {
-    OFIERE_TASK_OPS: `Manage tasks and approvals.
-Actions: "list", "create", "update", "delete", "add_approval", "list_approvals", "resolve_approval"
-- list: Filter by status, agent_id, space_id, folder_id, limit. Returns execution_plan, goals, constraints if present
-- create: Requires title. IMPORTANT: Always pass agent_id with your own name to self-assign (e.g. agent_id: "celia")
-  - Optional: description, instructions, execution_plan, goals, constraints, system_prompt, priority, tags, dates
-  - For COMPLEX tasks: include execution_plan (step-by-step), goals, constraints, and system_prompt
-  - For SIMPLE tasks: just title and optionally description
-- update: Requires task_id. All create fields + progress
-- delete: Requires task_id. Removes task and subtasks
-- add_approval: Request sign-off. Requires: task_id, approver_name. Optional: approver_type (human|agent), due_date, comment
-- list_approvals: List approvals. Optional: task_id, approval_status (pending|approved|rejected)
+    OFIERE_TASK_OPS: `Manage tasks and approvals.
+Actions: "list", "create", "update", "delete", "add_approval", "list_approvals", "resolve_approval"
+- list: Filter by status, agent_id, space_id, folder_id, limit. Returns execution_plan, goals, constraints if present
+- create: Requires title. IMPORTANT: Always pass agent_id with your own name to self-assign (e.g. agent_id: "celia")
+  - Optional: description, instructions, execution_plan, goals, constraints, system_prompt, priority, tags, dates
+  - For COMPLEX tasks: include execution_plan (step-by-step), goals, constraints, and system_prompt
+  - For SIMPLE tasks: just title and optionally description
+- update: Requires task_id. All create fields + progress
+- delete: Requires task_id. Removes task and subtasks
+- add_approval: Request sign-off. Requires: task_id, approver_name. Optional: approver_type (human|agent), due_date, comment
+- list_approvals: List approvals. Optional: task_id, approval_status (pending|approved|rejected)
 - resolve_approval: Approve/reject. Requires: approval_id, approval_status. Optional: comment`,
-    OFIERE_AGENT_OPS: `Query + manage agents and their staff subagents.
-Actions: "list", "list_subagents", "create_subagent", "delete_subagent", "invalidate_tier_cache"
-- list: All top-level agents (chiefs / native + OpenClaw) with IDs, names, roles. Use for task assignment lookup.
-- list_subagents: Staff under a chief. Required: chief_agent_id.
-- create_subagent: Add a staff subagent under a chief (max 5 per chief). Required: chief_agent_id, name. Optional: role (default "Staff"), codename, color_hex.
-- delete_subagent: Remove a staff subagent. Required: subagent_id.
+    OFIERE_AGENT_OPS: `Query + manage agents and their staff subagents.
+Actions: "list", "list_subagents", "create_subagent", "delete_subagent", "invalidate_tier_cache"
+- list: All top-level agents (chiefs / native + OpenClaw) with IDs, names, roles. Use for task assignment lookup.
+- list_subagents: Staff under a chief. Required: chief_agent_id.
+- create_subagent: Add a staff subagent under a chief (max 5 per chief). Required: chief_agent_id, name. Optional: role (default "Staff"), codename, color_hex.
+- delete_subagent: Remove a staff subagent. Required: subagent_id.
 - invalidate_tier_cache: Flush plugin's in-process tier cache (5 min TTL). Optional: agent_id. Use after direct-DB mutation of agent_tier_overrides.`,
-    OFIERE_PROJECT_OPS: `Manage PM hierarchy.
-Actions: "list_spaces", "create_space", "update_space", "delete_space", "list_folders", "create_folder", "update_folder", "delete_folder", "list_dependencies", "add_dependency", "remove_dependency"
-- Spaces: Top-level containers. CRUD with name, icon, icon_color
-- Folders: Inside spaces. Nest via parent_folder_id. Types: folder, project
+    OFIERE_PROJECT_OPS: `Manage PM hierarchy.
+Actions: "list_spaces", "create_space", "update_space", "delete_space", "list_folders", "create_folder", "update_folder", "delete_folder", "list_dependencies", "add_dependency", "remove_dependency"
+- Spaces: Top-level containers. CRUD with name, icon, icon_color
+- Folders: Inside spaces. Nest via parent_folder_id. Types: folder, project
 - Dependencies: Link tasks. Types: finish_to_start (default), start_to_start, finish_to_finish, start_to_finish. lag_days optional`,
-    OFIERE_SCHEDULE_OPS: `Calendar events.
-Actions: "list", "create", "update", "delete"
-- list: Filter by start_date, end_date, agent_id
-- create: Requires title + scheduled_date (YYYY-MM-DD). Optional: scheduled_time, duration_minutes, task_id, agent_id, recurrence_type, color
+    OFIERE_SCHEDULE_OPS: `Calendar events.
+Actions: "list", "create", "update", "delete"
+- list: Filter by start_date, end_date, agent_id
+- create: Requires title + scheduled_date (YYYY-MM-DD). Optional: scheduled_time, duration_minutes, task_id, agent_id, recurrence_type, color
 - Recurrence: none, hourly, daily, weekly, monthly with interval`,
-    OFIERE_KNOWLEDGE_OPS: `Ofiere Knowledge Library.
-Actions: "search", "list", "create", "update", "delete"
-- ALWAYS use when user mentions "knowledge base", "knowledge library", or asks to recall stored knowledge
-- search: Keyword search. Requires: query
-- list: Paginated listing with full content. Optional: search filter
-- create: Requires: file_name. Optional: content, source, author, credibility_tier
+    OFIERE_KNOWLEDGE_OPS: `Ofiere Knowledge Library.
+Actions: "search", "list", "create", "update", "delete"
+- ALWAYS use when user mentions "knowledge base", "knowledge library", or asks to recall stored knowledge
+- search: Keyword search. Requires: query
+- list: Paginated listing with full content. Optional: search filter
+- create: Requires: file_name. Optional: content, source, author, credibility_tier
 - update/delete: By document ID`,
-    OFIERE_WORKFLOW_OPS: `Full workflow automation (13 actions).
-Actions: "list", "get", "create", "update", "delete", "list_runs", "trigger", "add_nodes", "update_node", "delete_nodes", "add_edges", "delete_edges", "insert_node_between"
-- ALWAYS call "get" before modifying to see node IDs and graph structure
-- Node types: manual_trigger, webhook_trigger, agent_step, formatter_step, http_request, task_call, variable_set, condition, human_approval, delay, loop, convergence, output, checkpoint, note
-- Edge handles: condition edges use "condition-true"/"condition-false". Loop edges use "loop_body"/"done"
+    OFIERE_WORKFLOW_OPS: `Full workflow automation (13 actions).
+Actions: "list", "get", "create", "update", "delete", "list_runs", "trigger", "add_nodes", "update_node", "delete_nodes", "add_edges", "delete_edges", "insert_node_between"
+- ALWAYS call "get" before modifying to see node IDs and graph structure
+- Node types: manual_trigger, webhook_trigger, agent_step, formatter_step, http_request, task_call, variable_set, condition, human_approval, delay, loop, convergence, output, checkpoint, note
+- Edge handles: condition edges use "condition-true"/"condition-false". Loop edges use "loop_body"/"done"
 - Variables: {{prev.nodeId.outputText}}, {{variables.key}}`,
-    OFIERE_NOTIFY_OPS: `Notifications & Channel Reports.
-Actions: "list", "mark_read", "mark_all_read", "delete", "send_report", "get_task_detail", "schedule_report", "list_schedules", "delete_schedule"
-- send_report: Send PM progress report to YOUR channels. Required: scope_type, agent_id (YOUR name)
-- get_task_detail: Get full task result by report number. Required: task_number
+    OFIERE_NOTIFY_OPS: `Notifications & Channel Reports.
+Actions: "list", "mark_read", "mark_all_read", "delete", "send_report", "get_task_detail", "schedule_report", "list_schedules", "delete_schedule"
+- send_report: Send PM progress report to YOUR channels. Required: scope_type, agent_id (YOUR name)
+- get_task_detail: Get full task result by report number. Required: task_number
 - schedule_report: Recurring reports. Required: scope_type, recurrence_type, agent_id`,
-    OFIERE_MEMORY_OPS: `Conversation history & knowledge memory.
+    OFIERE_MEMORY_OPS: `Conversation history & knowledge memory.
 Actions: "list_conversations", "get_messages", "search_messages", "add_knowledge", "search_knowledge"`,
-    OFIERE_PROMPT_OPS: `Manage prompt instruction chunks.
-Actions: "list", "get", "create", "update", "delete"
+    OFIERE_PROMPT_OPS: `Manage prompt instruction chunks.
+Actions: "list", "get", "create", "update", "delete"
 - create: New chunk with name (max 30 chars) + content. Optional: color (hex), category`,
-    OFIERE_CONSTELLATION_OPS: `Create/edit/delete OpenClaw agents from chat.
-Actions: "list_agents", "get_agent", "read_file", "write_file", "create_agent", "delete_agent", "delete_file", "read_blueprint", "list_agent_mesh"
-- CRITICAL: ALWAYS call read_blueprint before creating/editing agents
+    OFIERE_CONSTELLATION_OPS: `Create/edit/delete OpenClaw agents from chat.
+Actions: "list_agents", "get_agent", "read_file", "write_file", "create_agent", "delete_agent", "delete_file", "read_blueprint", "list_agent_mesh"
+- CRITICAL: ALWAYS call read_blueprint before creating/editing agents
 - delete_agent: IRREVERSIBLE. Always ask user for explicit confirmation first`,
-    OFIERE_FILE_OPS: `Manage Space Files.
-Actions: "list_files", "list_folders", "create_folder", "create_text_file", "upload_file", "read_text_file", "rename_file", "rename_folder", "move_file", "move_folder", "delete_file", "delete_folder", "share_file", "unshare_file"
-- read_text_file: Use when task references @[name](file:ID)
+    OFIERE_FILE_OPS: `Manage Space Files.
+Actions: "list_files", "list_folders", "create_folder", "create_text_file", "upload_file", "read_text_file", "rename_file", "rename_folder", "move_file", "move_folder", "delete_file", "delete_folder", "share_file", "unshare_file"
+- read_text_file: Use when task references @[name](file:ID)
 - Files appear in PM Space Files tab immediately`,
-    OFIERE_PLAN_OPS: `Visual execution plan builder.
-Actions: "list", "get", "create", "update", "delete", "add_nodes", "execute"
-- Plans are visual DAG drafts — not real tasks until "execute"
-- Node types: task, gate, milestone
+    OFIERE_PLAN_OPS: `Visual execution plan builder.
+Actions: "list", "get", "create", "update", "delete", "add_nodes", "execute"
+- Plans are visual DAG drafts — not real tasks until "execute"
+- Node types: task, gate, milestone
 - Execution maps ALL fields: execution_steps, goals, constraints, system_prompt`,
-    OFIERE_SOP_OPS: `Standard Operating Procedures.
-Actions: "list_templates", "create", "list", "get", "update", "delete", "list_subagents", "apply_template", "propose_attach", "commit_attach"
-- sop_data: { title, purpose, scope, applicability, prerequisites:{ conditions, required_tools, required_permissions, safety_warnings }, procedure_steps[], expected_outputs[], escalation_rules[], acceptance_criteria[], rollback_procedure, notes }
-- Legacy field names still accepted (objective→purpose, steps→procedure_steps, deliverables→expected_outputs, escalationRules→escalation_rules, successCriteria→acceptance_criteria) — prefer new names.
-- propose_attach / commit_attach: attach SOPs to a run (target_kind: conversation|task|scheduler_event). Tier rule: SOPs only attach to STAFF-tier targets; for c-suite use OFIERE_FRAMEWORK_OPS instead. propose_attach returns a token-cost summary + confirmation_token (5-min ttl). You MUST surface the cost and ask the user before calling commit_attach. The user must explicitly approve.
+    OFIERE_SOP_OPS: `Standard Operating Procedures.
+Actions: "list_templates", "create", "list", "get", "update", "delete", "list_subagents", "apply_template", "propose_attach", "commit_attach"
+- sop_data: { title, purpose, scope, applicability, prerequisites:{ conditions, required_tools, required_permissions, safety_warnings }, procedure_steps[], expected_outputs[], escalation_rules[], acceptance_criteria[], rollback_procedure, notes }
+- Legacy field names still accepted (objective→purpose, steps→procedure_steps, deliverables→expected_outputs, escalationRules→escalation_rules, successCriteria→acceptance_criteria) — prefer new names.
+- propose_attach / commit_attach: attach SOPs to a run (target_kind: conversation|task|scheduler_event). Tier rule: SOPs only attach to STAFF-tier targets; for c-suite use OFIERE_FRAMEWORK_OPS instead. propose_attach returns a token-cost summary + confirmation_token (5-min ttl). You MUST surface the cost and ask the user before calling commit_attach. The user must explicitly approve.
 - See SOP PROTOCOL section for when to load vs skip`,
-    OFIERE_BRAIN_OPS: `Agent memory, knowledge graph, self-improvement (TMT/MAGMA).
-Memory Tiers: L1_focus (24h), L2_episode (days), L3_pattern (weeks), L4_rule (permanent), L5_persona (permanent)
-Actions: save_memory, recall, delete_memory, promote_memory, log_learning, list_learnings, resolve_learning, save_entity, link_entities, query_graph, start_trajectory, end_trajectory, get_brain_status
+    OFIERE_BRAIN_OPS: `Agent memory, knowledge graph, self-improvement (TMT/MAGMA).
+Memory Tiers: L1_focus (24h), L2_episode (days), L3_pattern (weeks), L4_rule (permanent), L5_persona (permanent)
+Actions: save_memory, recall, delete_memory, promote_memory, log_learning, list_learnings, resolve_learning, save_entity, link_entities, query_graph, start_trajectory, end_trajectory, get_brain_status
 - This is your SUBCONSCIOUS — use instinctively, not deliberately`,
-    OFIERE_TALENT_OPS: `Manage cognitive skill presets (Talents).
-Actions: "list", "get", "activate", "deactivate"
-- list: List all talents. Optional: category, scope, status
-- get: Get full talent details. Required: talent_id OR name
-- activate: Enable a talent (status → active). Required: talent_id
-- deactivate: Disable a talent (status → inactive). Required: talent_id
-- Active talents inject their execution_protocol and guardrails into your system prompt automatically
+    OFIERE_TALENT_OPS: `Manage cognitive skill presets (Talents).
+Actions: "list", "get", "activate", "deactivate"
+- list: List all talents. Optional: category, scope, status
+- get: Get full talent details. Required: talent_id OR name
+- activate: Enable a talent (status → active). Required: talent_id
+- deactivate: Disable a talent (status → inactive). Required: talent_id
+- Active talents inject their execution_protocol and guardrails into your system prompt automatically
 - Talents chain other tools: SPHINX chains KNOWLEDGE_OPS+BRAIN_OPS, PRISM chains BRAIN_OPS trajectories, ATLAS chains PLAN_OPS+TASK_OPS+SOP_OPS`,
-    OFIERE_FRAMEWORK_OPS: `Corporate Frameworks — strategic mandates, KPIs, risk governance.
-Actions: "create", "list", "get", "update", "delete", "propose_attach", "commit_attach"
-- content: JSON string with { mission, vision, core_principles[], decision_authority, budget_constraints, resource_limits, tool_stack[], strategic_objectives[], risk_appetite, compliance_requirements[], escalation_matrix[], team_composition (STRING — paragraph or newline-joined, NOT an array), integration_points[], review_frequency, last_reviewed, next_review, notes }
+    OFIERE_FRAMEWORK_OPS: `Corporate Frameworks — strategic mandates, KPIs, risk governance.
+Actions: "create", "list", "get", "update", "delete", "propose_attach", "commit_attach"
+- content: JSON string with { mission, vision, core_principles[], decision_authority, budget_constraints, resource_limits, tool_stack[], strategic_objectives[], risk_appetite, compliance_requirements[], escalation_matrix[], team_composition (STRING — paragraph or newline-joined, NOT an array), integration_points[], review_frequency, last_reviewed, next_review, notes }
 - propose_attach / commit_attach: attach Frameworks to a run (target_kind: conversation|task|scheduler_event). Tier rule: Frameworks only attach to C-SUITE-tier targets; for staff use OFIERE_SOP_OPS instead. propose_attach returns a token-cost summary + confirmation_token (5-min ttl). You MUST surface the cost and ask the user before calling commit_attach. The user must explicitly approve.`,
 };
 export function getSystemPrompt(state) {
@@ -131,71 +131,71 @@ export function getSystemPrompt(state) {
         const toolIndex = Object.entries(TOOL_SUMMARIES)
             .map(([name, desc]) => `- **${name}** — ${desc}`)
             .join("\n");
-        return `<ofiere-pm>
-You are connected to the Ofiere Project Management dashboard via the Ofiere PM plugin.
-${agentLine}
-
-## Your Ofiere PM Tools (${state.toolCount} meta-tools)
-
-Each tool uses an "action" parameter to select the operation. Always include action.
-Full parameter docs are in each tool's description — call the tool to see details.
-
-${toolIndex}
-
-## ⛔ PLANNING GATE (NON-NEGOTIABLE)
-- Before creating ANY task with 3+ total execution steps, goals, or constraints, you MUST ask the user: "Would you like me to plan this first, or create the task directly?"
-- If the user chooses to plan, use OFIERE_PLAN_OPS to create a visual plan first, then execute it.
-- NEVER skip this step. The server will block creation of complex tasks — use action: "create_force" only if the user explicitly confirms bypass.
-
-## Rules
-- ALWAYS pass agent_id with your own name when creating tasks (e.g. agent_id: "ivy").
-- ${assignRule}
-- To create an unassigned task, pass agent_id as "none" or "unassigned".
-- When user says "create a task for [agent]", use OFIERE_AGENT_OPS action:"list" first.
-- Task statuses: PENDING, IN_PROGRESS, DONE, FAILED. Priority: 0=LOW, 1=MED, 2=HIGH, 3=CRITICAL.
-- Changes appear in the dashboard immediately via real-time sync.
-- Do NOT fabricate task IDs — always look up real IDs first.
-- For complex tasks, include execution_plan, goals, constraints. For simple tasks, just title.
-- When user asks about "knowledge base/library", ALWAYS use OFIERE_KNOWLEDGE_OPS.
-- CONSTELLATION: ALWAYS read_blueprint before creating/editing agents. ALWAYS confirm before delete.
-- WORKFLOWS: ALWAYS "get" before modifying. Use "insert_node_between" for mid-flow additions.
-- CHANNEL REPORTS: ALWAYS include agent_id (YOUR name) in send_report. Use get_task_detail for drill-down.
-- File refs @[name](file:ID): Use OFIERE_FILE_OPS read_text_file to retrieve — don't ask user.
-- Task approvals (OFIERE_TASK_OPS) ≠ workflow gate approvals (human_approval nodes).
-
-## SOP PROTOCOL — Adaptive Complexity
-
-Classify complexity before executing:
-- **User Override**: "apply full SOP"/"use SOP" → 🔴 COMPLEX. "no SOP"/"just do it" → 🟢 SIMPLE.
-- **🟢 SIMPLE** (≤2 tool calls, no coordination): Execute directly. Do NOT mention SOPs.
-- **🟡 MODERATE** (3-5 calls, single dept): Ask briefly if SOPs needed.
-- **🔴 COMPLEX** (5+ calls, multi-dept, escalation risk): Auto-load relevant SOPs via list→get.
-
-## Agent Brain Protocol (TMT Subconscious)
-
-Your brain persists across conversations. L5 persona, L4 guardrails, L1 focus are injected at startup.
-- Save memories after significant interactions (not greetings/CRUD). Keep content to 1-3 sentences.
-- Log learnings on corrections, errors, feature requests, insights, best practices.
-- Do NOT announce memory operations — this is subconscious.
-- Never delay your reply to save a memory.
+        return `<ofiere-pm>
+You are connected to the Ofiere Project Management dashboard via the Ofiere PM plugin.
+${agentLine}
+
+## Your Ofiere PM Tools (${state.toolCount} meta-tools)
+
+Each tool uses an "action" parameter to select the operation. Always include action.
+Full parameter docs are in each tool's description — call the tool to see details.
+
+${toolIndex}
+
+## ⛔ PLANNING GATE (NON-NEGOTIABLE)
+- Before creating ANY task with 3+ total execution steps, goals, or constraints, you MUST ask the user: "Would you like me to plan this first, or create the task directly?"
+- If the user chooses to plan, use OFIERE_PLAN_OPS to create a visual plan first, then execute it.
+- NEVER skip this step. The server will block creation of complex tasks — use action: "create_force" only if the user explicitly confirms bypass.
+
+## Rules
+- ALWAYS pass agent_id with your own name when creating tasks (e.g. agent_id: "ivy").
+- ${assignRule}
+- To create an unassigned task, pass agent_id as "none" or "unassigned".
+- When user says "create a task for [agent]", use OFIERE_AGENT_OPS action:"list" first.
+- Task statuses: PENDING, IN_PROGRESS, DONE, FAILED. Priority: 0=LOW, 1=MED, 2=HIGH, 3=CRITICAL.
+- Changes appear in the dashboard immediately via real-time sync.
+- Do NOT fabricate task IDs — always look up real IDs first.
+- For complex tasks, include execution_plan, goals, constraints. For simple tasks, just title.
+- When user asks about "knowledge base/library", ALWAYS use OFIERE_KNOWLEDGE_OPS.
+- CONSTELLATION: ALWAYS read_blueprint before creating/editing agents. ALWAYS confirm before delete.
+- WORKFLOWS: ALWAYS "get" before modifying. Use "insert_node_between" for mid-flow additions.
+- CHANNEL REPORTS: ALWAYS include agent_id (YOUR name) in send_report. Use get_task_detail for drill-down.
+- File refs @[name](file:ID): Use OFIERE_FILE_OPS read_text_file to retrieve — don't ask user.
+- Task approvals (OFIERE_TASK_OPS) ≠ workflow gate approvals (human_approval nodes).
+
+## SOP PROTOCOL — Adaptive Complexity
+
+Classify complexity before executing:
+- **User Override**: "apply full SOP"/"use SOP" → 🔴 COMPLEX. "no SOP"/"just do it" → 🟢 SIMPLE.
+- **🟢 SIMPLE** (≤2 tool calls, no coordination): Execute directly. Do NOT mention SOPs.
+- **🟡 MODERATE** (3-5 calls, single dept): Ask briefly if SOPs needed.
+- **🔴 COMPLEX** (5+ calls, multi-dept, escalation risk): Auto-load relevant SOPs via list→get.
+
+## Agent Brain Protocol (TMT Subconscious)
+
+Your brain persists across conversations. L5 persona, L4 guardrails, L1 focus are injected at startup.
+- Save memories after significant interactions (not greetings/CRUD). Keep content to 1-3 sentences.
+- Log learnings on corrections, errors, feature requests, insights, best practices.
+- Do NOT announce memory operations — this is subconscious.
+- Never delay your reply to save a memory.
 </ofiere-pm>`;
     }
     if (state.ready) {
         const diagnostic = diagnoseError(state.connectError);
-        return `<ofiere-pm>
-The Ofiere PM plugin failed to connect.${state.connectError ? ` Error: ${state.connectError}` : ""}
-
-Diagnosis: ${diagnostic.reason}
-
-When the user asks about task management or the Ofiere dashboard, respond with:
-"${diagnostic.userMessage}"
-
-Do NOT pretend Ofiere tools exist or hallucinate tool calls. You have zero Ofiere tools available.
+        return `<ofiere-pm>
+The Ofiere PM plugin failed to connect.${state.connectError ? ` Error: ${state.connectError}` : ""}
+
+Diagnosis: ${diagnostic.reason}
+
+When the user asks about task management or the Ofiere dashboard, respond with:
+"${diagnostic.userMessage}"
+
+Do NOT pretend Ofiere tools exist or hallucinate tool calls. You have zero Ofiere tools available.
 </ofiere-pm>`;
     }
-    return `<ofiere-pm>
-The Ofiere PM plugin is loading. Tools should be available shortly.
-If the user asks about tasks right now, ask them to wait a moment.
+    return `<ofiere-pm>
+The Ofiere PM plugin is loading. Tools should be available shortly.
+If the user asks about tasks right now, ask them to wait a moment.
 </ofiere-pm>`;
 }
 function diagnoseError(error) {

package/dist/src/tools.js

@@ -16,6 +16,8 @@ import { resolveAgentId } from "./agent-resolver.js";
 import { handleProposeAttach, handleCommitAttach, registerAttachmentContextHook, } from "./attachments.js";
 import { invalidateAgentTier } from "./agent-tier.js";
 import { loadSubagentRow, readDispatchSubagentId, loadDispatchContextBySession } from "./staffPersona.js";
+import { expandPlanToDependencyEdges } from "./planExecute.js";
+import { registerGateOps } from "./gateOps.js";
 function ok(data) {
     return {
         content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
@@ -4867,7 +4869,7 @@ async function handleExecutePlan(supabase, userId, resolveAgent, params) {
         let tasksCreated = 0;
         while (queue.length > 0) {
             const { node, parentTaskId } = queue.shift();
-            if (node.type === "task") {
+            if (node.type === "task" || node.type === "milestone") {
                 const taskId = `task-${Date.now()}-${Math.random().toString(36).slice(2, 8)}`;
                 const now = new Date().toISOString();
                 const agentId = node.agentId ? await resolveAgent(node.agentId) : null;
@@ -4928,76 +4930,45 @@ async function handleExecutePlan(supabase, userId, resolveAgent, params) {
                 }
             }
         }
-        // Step 3: Create dependencies — sibling chaining + parent→child
-        const depsQueue = [...rootNodes];
+        // Step 3: Build dependencies + manual-gate rows via shared helper.
+        // The helper handles gate-skip-through (Option A), OR-join via group_id (Option B),
+        // and manual gates via pm_gates rows (Option C). See dashboard/lib/pm/planExecute.ts.
+        const { edges, gates: gateRows, emptyGates } = expandPlanToDependencyEdges(rootNodes, idMap);
         let depsCreated = 0;
-        // Helper: resolve a node to its nearest task ID (skip gates/milestones)
-        function resolveTaskId(n) {
-            return idMap.get(n.id);
-        }
-        // Helper: insert a dependency row into pm_dependencies
-        async function insertDep(predId, succId) {
+        let gatesCreated = 0;
+        for (const e of edges) {
             const { error } = await supabase.from("pm_dependencies").insert({
                 id: `dep-${Date.now()}-${Math.random().toString(36).slice(2, 8)}`,
-                user_id: userId, predecessor_id: predId, successor_id: succId,
-                dependency_type: "finish_to_start", lag_days: 0,
+                user_id: userId,
+                predecessor_id: e.predTaskId,
+                successor_id: e.succTaskId,
+                dependency_type: e.dependencyType,
+                lag_days: e.lagDays,
+                group_id: e.groupId,
             });
-            return !error;
-        }
-        while (depsQueue.length > 0) {
-            const node = depsQueue.shift();
-            const nodeRealId = resolveTaskId(node);
-            // Chain siblings: sequential children of this node get chained left-to-right
-            if (Array.isArray(node.children) && node.children.length > 1 && !node.parallel) {
-                const taskChildren = [];
-                for (const child of node.children) {
-                    const cid = resolveTaskId(child);
-                    if (cid)
-                        taskChildren.push(cid);
-                }
-                for (let i = 1; i < taskChildren.length; i++) {
-                    if (await insertDep(taskChildren[i - 1], taskChildren[i]))
-                        depsCreated++;
-                }
-            }
-            // Parent → first child link (sequential only)
-            if (nodeRealId && !node.parallel && node.children?.length > 0) {
-                const firstChildId = resolveTaskId(node.children[0]);
-                if (firstChildId) {
-                    if (await insertDep(nodeRealId, firstChildId))
-                        depsCreated++;
-                }
-            }
-            // Parallel fan-out: parent → each child
-            if (nodeRealId && node.parallel && node.children?.length > 0) {
-                for (const child of node.children) {
-                    const childId = resolveTaskId(child);
-                    if (childId) {
-                        if (await insertDep(nodeRealId, childId))
-                            depsCreated++;
-                    }
-                }
-            }
-            if (Array.isArray(node.children))
-                depsQueue.push(...node.children);
-        }
-        // Chain root-level siblings (sequential root nodes)
-        const rootTaskIds = [];
-        for (const rn of rootNodes) {
-            const rid = resolveTaskId(rn);
-            if (rid)
-                rootTaskIds.push(rid);
-        }
-        for (let i = 1; i < rootTaskIds.length; i++) {
-            if (await insertDep(rootTaskIds[i - 1], rootTaskIds[i]))
+            if (!error)
                 depsCreated++;
         }
+        for (const g of gateRows) {
+            const { error } = await supabase.from("pm_gates").insert({
+                user_id: userId,
+                plan_id: params.plan_id,
+                plan_node_id: g.planNodeId,
+                gate_label: g.gateLabel,
+                gate_condition: g.gateCondition,
+                task_id_blocked: g.taskIdBlocked,
+            });
+            if (!error)
+                gatesCreated++;
+        }
         // Mark plan as deployed
         await supabase.from("pm_plans").update({ is_deployed: true, deployed_at: new Date().toISOString(), updated_at: new Date().toISOString() }).eq("id", params.plan_id).eq("user_id", userId);
         return ok({
             message: `Plan "${data.name || plan.name}" executed successfully`,
             tasks_created: tasksCreated,
             dependencies_created: depsCreated,
+            gates_created: gatesCreated,
+            empty_gates: emptyGates,
             folder_id: folderId,
             space_id: spaceId,
             ...(folderSkipped ? { folder_skipped_reason: "No space_id provided — assign the plan to a space to enable folder creation" } : {}),
@@ -6927,6 +6898,7 @@ supabase, config) {
     registerTalentOps(api, supabase, userId); // 15
     registerFrameworkOps(api, supabase, userId, resolveAgent); // 16
     registerOfficeOps(api, supabase, userId, resolveAgent); // 17
+    registerGateOps(api, supabase, userId, fallbackAgentId); // 18
     // ── Register dynamic brain context hook ──
     registerBrainContextHook(api, supabase, userId, fallbackAgentId);
     // ── Register talent context hook ──
@@ -6936,7 +6908,7 @@ supabase, config) {
     // ── Register agent_end hook for server-side brain extraction ──
     registerBrainExtractionHook(api, supabase, userId, fallbackAgentId);
     // ── Count and log ──
-    const toolCount = 17;
+    const toolCount = 18;
     const callerName = getCallingAgentName(api);
     const agentLabel = fallbackAgentId || callerName || "auto-detect";
     api.logger.info(`[ofiere] ${toolCount} meta-tools registered (agent: ${agentLabel})`);