@xopcai/xopc 0.0.179 → 0.0.187

package/dist/src/agent/tool-manuals/xopc-use.js

@@ -1,50 +1,68 @@
 //#region src/agent/tool-manuals/xopc-use.ts
 const xopcUseManual = `# XOPC Use Tool Manual
 
-## Overview
+## Purpose
 
-\`xopc_use\` is the unified tool for operating XOPC product objects. Use it instead of editing storage files or database rows directly.
-
-Basic shape:
+\`xopc_use\` operates first-class XOPC product objects without editing SQLite or product files directly.
+Load this manual before a non-trivial mutation.
 
 \`\`\`json
 {
-  "mode": "project | note | work_item | local_app | settings",
-  "command": "list | get | create | update | append | preview_edit | resolve_workspace | validate | open",
-  "args": { "...": "..." },
+  "mode": "project | automation | note | task | task_run | local_app | settings",
+  "command": "...",
+  "args": {},
   "dryRun": false
 }
 \`\`\`
 
-## General Rules
+Send one object command per call. Inspect the returned JSON \`ok\` field; a tool call can
+complete successfully while the product command returns \`ok: false\`.
 
-- Use \`list\` or \`get\` first when the target object is ambiguous.
-- Use \`dryRun: true\` before a broad or risky change.
-- Prefer additive operations over destructive replacement.
-- Do not invent ids. If an id is not known, search/list first.
-- Do not attempt delete/archive workflows through this tool unless the command is explicitly supported.
-- For non-trivial note rewrites, use \`note.preview_edit\` before \`note.update\`.
-- Preserve the returned “Open in xopc” link in channel replies so the user can jump directly into the delivered object.
+## Object routing
 
-## Projects
+| Object | Tool |
+| --- | --- |
+| Project, milestone, project update | \`xopc_use\` mode \`project\` |
+| Automation | \`xopc_use\` mode \`automation\` |
+| Task intent and lifecycle | \`xopc_use\` mode \`task\` |
+| Task execution attempt, receipt, events and waits | \`xopc_use\` mode \`task_run\` |
+| Note | \`xopc_use\` mode \`note\` |
+| Local app | \`xopc_use\` mode \`local_app\` |
+| Settings jump target | \`xopc_use\` mode \`settings\` |
+| Workflow run | dedicated \`workflow\` tool; pass \`taskId\` to link it to a Task |
+| Session, memory, skill, connected app or workspace file | its dedicated tool |
 
-Projects group sessions, work items, goals, workflows, files, and project instructions.
+Do not emulate Workflow APIs through \`xopc_use\`. A Task is durable intent;
+a TaskRun is one execution attempt; a WorkflowRun is a procedure execution and may belong
+to a TaskRun. Never treat these three objects as interchangeable.
 
-### Find projects
+## Reliable protocol
 
-\`\`\`json
-{ "mode": "project", "command": "list", "args": { "search": "release", "limit": 10 } }
-\`\`\`
+1. Use \`list\` then \`get\` when an id is unknown.
+2. Read the current \`version\` before a Task mutation.
+3. Use \`dryRun: true\` for broad Project changes or uncertain mutations.
+4. Mutate once with the exact id and current concurrency token.
+5. Verify the returned object and preserve any “Open in xopc” delivery link.
+6. On a conflict, read again and reconsider the operation; do not blindly retry.
 
-### Read project detail
+Timestamps are Unix epoch milliseconds. Array fields are arrays of strings. Omission
+preserves a patchable field; an empty array intentionally clears it. Prefer explicit
+\`projectId\`, \`taskId\`, \`runId\`, \`noteId\`, and \`localAppId\` fields over \`id\`.
 
-\`\`\`json
-{ "mode": "project", "command": "get", "args": { "projectId": "project_id" } }
-\`\`\`
+## Projects
+
+Commands: \`list\`, \`get\`, \`create\`, \`update\`, \`resolve_workspace\`,
+\`list_milestones\`, \`create_milestone\`, \`update_milestone\`, \`list_updates\`,
+and \`create_update\`.
 
-### Create a project
+Project statuses: \`planned\`, \`active\`, \`paused\`, \`completed\`, \`cancelled\`,
+\`archived\`. Health values: \`unknown\`, \`on_track\`, \`at_risk\`, \`off_track\`.
 
-Use when the user asks to keep an outcome moving across conversations, or explicitly accepts an offer to do so. The user does not need to say “project”. Do not create one merely because a task is complex: continuity across sessions, files, decisions, or dependencies is the key signal. Include \`workspaceRoot\` when the work maps to a local repository or directory. Include \`brief\` for the desired outcome and \`instructions\` only for durable operating guidance.
+A Project defines a bounded goal. Its durable planning fields are \`outcome\`,
+\`successCriteria\`, \`scope\`, \`nonGoals\`, \`ownerId\`, \`targetAt\`, and \`health\`.
+Use \`brief\` for a concise description and \`instructions\` for durable operating guidance.
+
+### Create
 
 \`\`\`json
 {
@@ -52,16 +70,18 @@ Use when the user asks to keep an outcome moving across conversations, or explic
   "command": "create",
   "args": {
     "name": "AI Product Research",
-    "workspaceRoot": "/path/to/repo",
-    "brief": "Explore demand and feasibility for an AI product.",
-    "instructions": "Keep decisions and open questions current."
+    "outcome": "Choose a validated product direction",
+    "successCriteria": ["Ten customer interviews", "Decision recorded"],
+    "scope": { "market": "developer tools" },
+    "nonGoals": ["Build the production product"],
+    "health": "on_track",
+    "targetAt": 1760000000000,
+    "workspaceRoot": "/path/to/repo"
   }
 }
 \`\`\`
 
-### Update a project
-
-Use for metadata, brief, status, or instructions. Use \`dryRun\` first when changing \`workspaceRoot\` or broad instructions.
+### Update
 
 \`\`\`json
 {
@@ -70,172 +90,287 @@ Use for metadata, brief, status, or instructions. Use \`dryRun\` first when chan
   "args": {
     "projectId": "project_id",
     "status": "active",
-    "instructions": "Prioritize safe previews before changing notes."
+    "health": "at_risk",
+    "successCriteria": ["Ten interviews", "Evidence-backed decision"]
   }
 }
 \`\`\`
 
-### Resolve workspace
+### Resolve a workspace
 
-Use when a file path or current working directory should be mapped to a project.
+Use \`autoCreate: false\` for lookup. Set it to true only when creating a Project is authorized.
+
+\`\`\`json
+{ "mode": "project", "command": "resolve_workspace", "args": { "workspacePath": "/path/to/repo", "autoCreate": false } }
+\`\`\`
+
+### Milestones
+
+Milestone statuses: \`planned\`, \`active\`, \`completed\`, \`cancelled\`.
 
 \`\`\`json
 {
   "mode": "project",
-  "command": "resolve_workspace",
-  "args": { "workspacePath": "/path/to/repo", "autoCreate": false }
+  "command": "create_milestone",
+  "args": {
+    "projectId": "project_id",
+    "title": "Finish discovery",
+    "status": "active",
+    "targetAt": 1760000000000,
+    "sortOrder": 10
+  }
 }
 \`\`\`
 
-## Notes
+Use \`list_milestones\` with \`projectId\`. Use \`update_milestone\` with both
+\`projectId\` and \`milestoneId\`. Milestone deletion is intentionally not exposed.
 
-Notes are user-owned markdown objects. Treat them as durable user content.
+### Immutable project updates
 
-### Find notes
+Project updates are append-only progress snapshots. They also update Project health.
 
 \`\`\`json
-{ "mode": "note", "command": "list", "args": { "search": "pricing", "limit": 10 } }
+{
+  "mode": "project",
+  "command": "create_update",
+  "args": {
+    "projectId": "project_id",
+    "health": "on_track",
+    "summary": "Discovery is complete",
+    "progress": ["Interviewed ten users"],
+    "risks": ["Pricing remains unvalidated"],
+    "nextSteps": ["Run pricing tests"]
+  }
+}
 \`\`\`
 
-### Create a note
+Use \`list_updates\` with \`projectId\` and optional \`limit\`. Updates cannot be edited.
+
+## Automations
+
+Commands: \`list\`, \`get\`, \`create\`, \`update\`, \`delete\`, \`run\`, \`pause\`,
+\`resume\`, and \`history\`.
+
+Automation \`create\` automatically uses the current session Project when \`projectId\` is
+omitted. An explicit \`projectId\` takes precedence and is validated before mutation. Use an
+explicit id when creating for a Project other than the current session Project.
+
+### Create in the current Project
+
+\`trigger\` and \`action\` use the same shapes as the Automation product API.
 
 \`\`\`json
 {
-  "mode": "note",
+  "mode": "automation",
   "command": "create",
   "args": {
-    "title": "Product direction",
-    "markdown": "Initial notes...",
-    "tags": ["product"]
+    "name": "Daily project review",
+    "trigger": { "kind": "schedule", "schedule": { "kind": "cron", "expr": "0 9 * * 1-5", "tz": "Asia/Shanghai" } },
+    "action": { "kind": "agent", "instruction": "Review the current project and summarize risks." }
   }
 }
 \`\`\`
 
-### Append to a note
+To override the inherited Project, add \`"projectId": "project_id"\` to \`args\`.
+The create payload may also be nested under \`args.automation\`; top-level \`args.projectId\`
+has precedence.
+
+### List and history
+
+\`list\` and unqualified \`history\` inherit the current session Project. Pass an explicit
+\`projectId\` to query another Project. Pass \`automationId\` to \`history\` for one Automation.
+
+### Update and operate
+
+Use \`automationId\` for \`get\`, \`update\`, \`delete\`, \`run\`, \`pause\`, and \`resume\`.
+For \`update\`, patch fields may be direct args or nested under \`args.patch\`. Supplying a new
+\`projectId\` reassigns the Automation after validating the target Project.
+
+## Tasks
+
+Commands: \`list\`, \`get\`, \`create\`, \`update_dependencies\`, \`add_context\`,
+\`remove_context\`, and \`command\`.
+
+Task phases are \`backlog\`, \`ready\`, \`active\`, \`review\`, and \`closed\`.
+Operational state is projected separately as \`idle\`, \`queued\`, \`running\`, \`waiting\`,
+\`verifying\`, \`succeeded\`, \`failed\`, or \`cancelled\`. Never send either value as a
+free-form status update.
+
+\`task.get\` returns the Task, its projected \`model\`, dependencies, dependents, context,
+authority grants, TaskRuns, receipts, and waits.
+The projected model is the correct source for current operational state and attention items.
+
+### Capture or start
 
-Prefer append when preserving original user notes and adding AI output.
+\`createMode\` defaults to \`capture\`, which creates a backlog Task without executing it.
+Use \`start\` only when immediate execution is intended.
 
 \`\`\`json
 {
-  "mode": "note",
-  "command": "append",
+  "mode": "task",
+  "command": "create",
   "args": {
-    "noteId": "note_id",
-    "heading": "AI synthesis",
-    "content": "Key points..."
+    "objective": "Complete the customer research report",
+    "projectId": "project_id",
+    "createMode": "capture",
+    "priority": "high",
+    "expectedOutputs": ["Research report"],
+    "acceptanceCriteria": ["Sources are cited"],
+    "constraints": ["Do not contact customers without approval"],
+    "dependsOnTaskIds": []
   }
 }
 \`\`\`
 
-### Preview an edit
-
-Use before rewriting or restructuring a note.
+### Dependencies
 
 \`\`\`json
 {
-  "mode": "note",
-  "command": "preview_edit",
+  "mode": "task",
+  "command": "update_dependencies",
   "args": {
-    "noteId": "note_id",
-    "instruction": "Summarize this as action items"
+    "taskId": "task_id",
+    "expectedVersion": 3,
+    "dependsOnTaskIds": ["dependency_task_id"]
   }
 }
 \`\`\`
 
-### Update a note
+### Context links
 
-Use only when the user clearly wants the canonical note changed. Prefer \`append\` or \`preview_edit\` otherwise.
+Use \`add_context\` to link a document, file, URL, session, memory, Task, artifact, or source
+as \`input\`, \`reference\`, \`constraint\`, \`deliverable\`, or \`evidence\` context.
 
 \`\`\`json
 {
-  "mode": "note",
-  "command": "update",
+  "mode": "task",
+  "command": "add_context",
   "args": {
-    "noteId": "note_id",
-    "status": "processed",
-    "tags": ["product", "validated"]
+    "taskId": "task_id",
+    "targetKind": "file",
+    "targetId": "/path/to/spec.md",
+    "role": "input",
+    "title": "Product specification",
+    "pinned": true,
+    "retrievalPolicy": {},
+    "metadata": {}
   }
 }
 \`\`\`
 
-## Work Items
+Use \`remove_context\` with \`taskId\` and the exact \`edgeId\` returned by \`task.get\`.
+Do not add authority grants through this tool; an Agent must not authorize itself.
 
-Work items are project-scoped tasks. If \`projectId\` is omitted, the tool may inherit the current session's project binding.
+### Typed lifecycle commands
 
-### Create a work item
+Every command requires \`taskId\`, the Task's current \`expectedVersion\`, a \`type\`, and
+type-specific fields inside \`commandArgs\`.
+
+Supported command types:
+
+- \`mark_ready\`
+- \`start\`: \`{ "executor": { "kind": "agent", "agentId": "main" } }\`
+- \`request_review\`
+- \`close\`: \`{ "resolution": "done | cancelled | duplicate | wont_do" }\`
+- \`reopen\`: \`{ "phase": "ready | active" }\`
+- \`add_wait\`: \`{ "wait": { "kind": "dependency | approval | input | schedule | external | paused", "reason": "...", "condition": {} } }\`
+- \`resolve_wait\`: \`{ "waitId": "wait_id", "resolution": {} }\`
+- \`delegate\`: \`{ "agentId": "agent_id" }\`
+- \`revise_contract\`: \`{ "contract": { ...complete contract... } }\`
 
 \`\`\`json
 {
-  "mode": "work_item",
-  "command": "create",
+  "mode": "task",
+  "command": "command",
   "args": {
-    "projectId": "project_id",
-    "title": "Validate technical feasibility",
-    "description": "Check API, storage, UI, and safety implications.",
-    "priority": "high",
-    "status": "todo"
+    "taskId": "task_id",
+    "expectedVersion": 3,
+    "type": "start",
+    "commandArgs": {
+      "executor": { "kind": "agent", "agentId": "main" }
+    }
   }
 }
 \`\`\`
 
-### Update a work item
+Contract revision is replacement, not a patch. Read the Task and preserve all contract fields
+the user did not ask to change. Resolve a wait through \`resolve_wait\`; do not directly mutate
+a TaskRun or manufacture a phase transition.
+
+## TaskRuns
+
+TaskRun inspection is read-only except for explicit cancellation. Other execution state is
+controlled by Task commands and the runtime coordinator.
+
+### List attempts for a Task
 
 \`\`\`json
-{
-  "mode": "work_item",
-  "command": "update",
-  "args": {
-    "workItemId": "work_item_id",
-    "status": "in_progress",
-    "nextAction": "Prototype the xopc_use tool path."
-  }
-}
+{ "mode": "task_run", "command": "list", "args": { "taskId": "task_id", "limit": 20 } }
 \`\`\`
 
-## Local Apps
+The result contains run attempts, finalized receipts, and active waits.
 
-Local apps are first-class XOPC extension UIs backed by a project workspace.
+### Inspect one attempt
 
 \`\`\`json
-{
-  "mode": "local_app",
-  "command": "create",
-  "args": {
-    "name": "Research Hub",
-    "idea": "Keep product research sources and decisions together.",
-    "description": "A compact local research workspace."
-  }
-}
+{ "mode": "task_run", "command": "get", "args": { "runId": "run_id" } }
 \`\`\`
 
-Use \`list\`, \`get\`, and \`validate\` to inspect an existing app. Installation,
-activation, rollback, and uninstall remain explicit product UI operations because
-they change the extension runtime.
+The result contains the TaskRun, its receipt when terminal, ordered events, and active Task waits.
 
-## Settings
+### Cancel an attempt
 
-Use settings references when the user must review credentials, privacy, gateway,
-appearance, agent browser, or another configuration surface. This does not change
-configuration silently; it returns an exact inline jump target.
+Read the run first, then pass its current version. Cancellation creates a terminal receipt.
 
 \`\`\`json
 {
-  "mode": "settings",
-  "command": "open",
-  "args": {
-    "section": "credentials",
-    "title": "Provider credentials",
-    "summary": "Add the API key required by the selected model."
-  }
+  "mode": "task_run",
+  "command": "cancel",
+  "args": { "runId": "run_id", "expectedVersion": 2, "reason": "User cancelled execution" }
 }
 \`\`\`
 
-## Safety
+Do not guess commands such as retry, force-complete, heartbeat, or transition; they are not Agent APIs.
+
+## Notes
+
+Commands: \`list\`, \`get\`, \`create\`, \`append\`, \`preview_edit\`, and \`update\`.
+Use Notes for durable prose and reference material, not as a Task substitute. Prefer \`append\`
+when preserving user content. Use \`preview_edit\` before a canonical rewrite.
+
+\`\`\`json
+{ "mode": "note", "command": "create", "args": { "title": "Decision", "markdown": "...", "projectId": "project_id" } }
+\`\`\`
+
+\`\`\`json
+{ "mode": "note", "command": "append", "args": { "noteId": "note_id", "heading": "AI synthesis", "content": "..." } }
+\`\`\`
+
+## Local apps and settings
+
+Local app commands are \`list\`, \`get\`, \`create\`, and \`validate\`. Installation,
+activation, rollback, and uninstall remain product runtime operations.
+
+Settings supports only \`open\` and returns an exact product jump target without changing config.
+
+## Error recovery
+
+| Result | Recovery |
+| --- | --- |
+| service unavailable | Stop retrying and report the unavailable capability. |
+| not found | Re-list in the intended scope; do not invent another id. |
+| conflict | Read the current object and reassess using its latest version. |
+| waiting | Inspect the Task projection and TaskRun waits; resolve only the real blocker. |
+| invalid command or state | Read the object and use only a documented transition. |
+| unsupported operation | Use the dedicated tool or product UI; never write storage directly. |
+
+## Deliberate boundaries
 
-- \`note.update\` can replace canonical user content. Use \`preview_edit\` first for content rewrites.
-- \`project.update.workspaceRoot\` changes project-file scope. Use \`dryRun\` and ask the user if intent is unclear.
-- \`work_item.update.archivedAt\` hides work from normal active views. Confirm before archiving.
-- If the user asks for deletion, explain that deletion is not exposed through \`xopc_use\` yet.
+- Project deletion and milestone deletion are not Agent APIs.
+- TaskRun mutation is internal to execution coordination except for optimistic cancellation.
+- Project updates are immutable.
+- Workflow and Automation operations remain in their dedicated tools.
+- Only the documented Task and TaskRun commands are valid; do not infer hidden aliases.
 `;
 //#endregion
 export { xopcUseManual };

package/dist/src/agent/tools/apply-patch.d.ts

@@ -1,5 +1,4 @@
 import type { AgentTool } from '@earendil-works/pi-agent-core';
-import type { GoalEvidenceRecordInput } from './goal-evidence-recorder.js';
 export type AppliedPatchChangeKind = 'add' | 'delete' | 'update' | 'move';
 export interface AppliedPatchChange {
     kind: AppliedPatchChangeKind;
@@ -19,7 +18,4 @@ export interface ApplyPatchDetails {
     added: number;
     removed: number;
 }
-export interface CreateApplyPatchToolOptions {
-    recordGoalEvidence?: (input: GoalEvidenceRecordInput) => Promise<void> | void;
-}
-export declare function createApplyPatchTool(workspace: string, options?: CreateApplyPatchToolOptions): AgentTool;
+export declare function createApplyPatchTool(workspace: string): AgentTool;

package/dist/src/agent/tools/apply-patch.js

@@ -248,7 +248,7 @@ async function commitPatchPlan(changes) {
 		throw error;
 	}
 }
-function createApplyPatchTool(workspace, options) {
+function createApplyPatchTool(workspace) {
 	return {
 		name: "apply_patch",
 		label: "Apply Patch",
@@ -272,17 +272,6 @@ function createApplyPatchTool(workspace, options) {
 					const display = change.moveTo ? `${change.path} -> ${change.moveTo}` : change.path;
 					return `${change.kind}: ${display} (+${change.added}/-${change.removed})`;
 				}).join("\n");
-				await options?.recordGoalEvidence?.({
-					kind: "diff",
-					title: `Patch applied: ${changes.length} file${changes.length === 1 ? "" : "s"}`,
-					summary: diff.slice(0, 4e3),
-					uri: changes.length === 1 ? changes[0].absoluteMoveTo ?? changes[0].absolutePath : void 0,
-					data: {
-						files,
-						added,
-						removed
-					}
-				});
 				return {
 					content: [{
 						type: "text",

package/dist/src/agent/tools/clarify-tool.js

@@ -23,7 +23,7 @@ function createClarifyTool(deps) {
 	return {
 		name: "clarify",
 		label: "❓ Clarify",
-		description: "Ask the user a clarifying question and wait for their response.\n\nUse this when you need more information to proceed correctly, rather than guessing.\n\nWHEN TO USE:\n- Ambiguous instructions with multiple valid interpretations\n- Missing critical information (which file, which approach, etc.)\n- Confirming destructive or irreversible actions\n\nWHEN NOT TO USE:\n- When you can reasonably infer the answer from context\n- For trivial decisions that do not affect the outcome\n- When the user explicitly said \"just do it\" or \"your choice\"\n\nTIPS:\n- Provide choices when there are clear options (faster for the user)\n- Keep questions short and specific\n- Include a default when one option is clearly more likely",
+		description: "Ask the user a clarifying question and wait for their response.\n\nUse this when you need more information to proceed correctly, rather than guessing.\n\nWHEN TO USE:\n- Ambiguous instructions with multiple valid interpretations\n- Missing critical information (which file, which approach, etc.)\n- Confirming destructive or irreversible actions\n\nWHEN NOT TO USE:\n- When you can reasonably infer the answer from context\n- For trivial decisions that do not affect the task\n- When the user explicitly said \"just do it\" or \"your choice\"\n\nTIPS:\n- Provide choices when there are clear options (faster for the user)\n- Keep questions short and specific\n- Include a default when one option is clearly more likely",
 		parameters: ClarifySchema,
 		async execute(_toolCallId, params, signal) {
 			const p = params;

package/dist/src/agent/tools/delegate-tool.js

@@ -17,7 +17,6 @@ const DEFAULT_DELEGATE_TOOLS = [
 const DELEGATE_BLOCKED_TOOLS = new Set([
 	"delegate_task",
 	"clarify",
-	"curated_memory",
 	"send_message",
 	"send_media",
 	"todo",
@@ -30,7 +29,8 @@ const DELEGATE_BLOCKED_TOOLS = new Set([
 	"skill_manage",
 	"skills_marketplace_search",
 	"skill_install",
-	"bundle-mcp"
+	"bundle-mcp",
+	"managed_job"
 ]);
 const DelegateTaskSchema = Type.Object({
 	goal: Type.String({ description: "Clear description of what the sub-agent should accomplish" }),
@@ -45,7 +45,7 @@ function createDelegateTool(deps) {
 	return {
 		name: "delegate_task",
 		label: "🤖 Delegate",
-		description: "Spawn a sub-agent for an isolated subtask with a fresh conversation (no parent transcript).\n\nThe sub-agent returns a text summary only — tool traces stay out of your context.\n\nWHEN TO USE:\n- Independent work (research, multi-file exploration) where you only need the outcome\n- Avoiding context bloat from long intermediate tool output\n\nWHEN NOT TO USE:\n- Tasks that need this chat history or user clarification\n- Single trivial steps\n\nSub-agents cannot use clarify, messaging, memory tools, todo, or nested delegate_task.",
+		description: "Spawn a sub-agent for an isolated subtask with a fresh conversation (no parent transcript).\n\nThe sub-agent returns a text summary only — tool traces stay out of your context.\n\nWHEN TO USE:\n- Independent work (research, multi-file exploration) where you only need the task\n- Avoiding context bloat from long intermediate tool output\n\nWHEN NOT TO USE:\n- Tasks that need this chat history or user clarification\n- Single trivial steps\n\nSub-agents cannot use clarify, messaging, memory tools, todo, or nested delegate_task.",
 		parameters: DelegateTaskSchema,
 		async execute(_toolCallId, params, signal) {
 			const p = params;
@@ -87,10 +87,13 @@ function createDelegateTool(deps) {
 					}
 				};
 			}
+			const ctx = deps.getCurrentContext?.() ?? null;
+			const parentSessionKey = ctx?.sessionKey;
 			const childOptions = {
 				workspace: deps.workspace,
 				goal: p.goal,
 				context: p.context,
+				requesterSessionKey: parentSessionKey,
 				allowedToolNames: allowedNames,
 				maxIterations,
 				model,
@@ -99,8 +102,6 @@ function createDelegateTool(deps) {
 				toolExecutorConfig: deps.toolExecutorConfig,
 				buildChildTools: deps.buildChildTools
 			};
-			const ctx = deps.getCurrentContext?.() ?? null;
-			const parentSessionKey = ctx?.sessionKey;
 			let childSessionKey;
 			try {
 				if (deps.hookRunner && parentSessionKey) {

package/dist/src/agent/tools/dreaming-tool.d.ts

@@ -2,7 +2,6 @@ import type { AgentTool } from '@earendil-works/pi-agent-core';
 import type { Config } from '../../config/schema.js';
 export interface DreamingToolDeps {
     getWorkspace: () => string;
-    getDreamingRoot: () => string;
     getConfig: () => Config | undefined;
     getAgentId?: () => string | undefined;
 }