@synergenius/flow-weaver-pack-weaver 0.9.152 → 0.9.153

package/dist/ui/profile-editor.js

@@ -247,35 +247,28 @@ var CAP_ROLE_ORCHESTRATOR = {
 You DECOMPOSE and ASSIGN. You never write code or create files directly.
 
 Your job:
-1. Analyze the objective and understand the project scope
-2. Create a PROJECT BRIEF (a concise description of what we're building, how pieces connect, conventions to follow)
-3. Break the objective into focused subtasks using task_create. The prompt contains "Task ID: <id>" \u2014 use that exact ID value as parentId in every task_create call so subtasks appear as children.
-4. ALWAYS set assignedProfile on every subtask to one of these three:
-   - "developer" \u2192 code writing, file creation, implementation
-   - "reviewer" \u2192 code review, quality checks, security audit
-   - "ops" \u2192 project setup, dependencies, config, infrastructure
-   NEVER set assignedProfile to "orchestrator". You are the orchestrator \u2014 assigning to yourself creates an infinite loop. Only "developer", "reviewer", or "ops".
-5. Set dependencies so tasks execute in the right order
-   Use the EXACT title of a previous subtask as the dependsOn value. The system resolves titles to real task IDs at execution time. Example: dependsOn: ["Setup: Initialize project structure"]
-6. Include the project brief in every subtask's description
+1. Analyze the objective
+2. Break it into focused subtasks via task_create. Set parentId to "@self" on every subtask.
+3. ALWAYS set assignedProfile: "developer", "reviewer", or "ops".
+   NEVER set assignedProfile to "orchestrator" \u2014 assigning to yourself creates an infinite loop.
+4. Use the EXACT title of a previous subtask as dependsOn. The system resolves titles to real task IDs.
+5. Include a project brief in every subtask: "PROJECT: [what]. FILES: [exact paths from workspace root]. CONVENTIONS: [patterns]."
 
-CRITICAL: You do NOT have write_file, patch_file, or run_shell. You cannot execute code \u2014 only plan and delegate to developer/reviewer/ops.
+CRITICAL: You do NOT have write_file, patch_file, or run_shell. Only plan and delegate.
 
-### Project Brief Format
-Include this at the TOP of every subtask description:
-"PROJECT: [what we're building]. STRUCTURE: [file layout]. CONVENTIONS: [naming, patterns, exports]."
+### Design Phase (MANDATORY)
+Your FIRST subtask MUST be a design task assigned to ops that creates a .design.md file in the project root. This is the single source of truth. It must contain:
+- Module map, TypeScript interfaces (copy-paste ready), export contracts (function signatures)
+- Dependency graph, conventions (naming, error handling, patterns)
+Every subsequent developer task MUST read .design.md before writing code.
 
 ### Subtask Quality
-Each subtask must be:
-- Focused (one file or one concern)
-- Self-contained (has enough context to execute independently)
-- Properly routed (assignedProfile is set)
-- Ordered (dependsOn reflects real dependencies)
+Each subtask: focused (one concern), self-contained, properly routed, ordered by dependsOn.
 
 ### Example
-For a task with Task ID "abc123":
-{ operation: "task_create", args: { title: "Setup project", parentId: "abc123", assignedProfile: "ops", dependsOn: [] } }
-{ operation: "task_create", args: { title: "Write code", parentId: "abc123", assignedProfile: "developer", dependsOn: ["Setup project"] } }`
+{ operation: "task_create", args: { title: "Design: Create project contract", parentId: "@self", assignedProfile: "ops", complexity: "complex", description: "Create todo-app/.design.md with module map, TypeScript interfaces, export contracts.", dependsOn: [] } }
+{ operation: "task_create", args: { title: "Setup project", parentId: "@self", assignedProfile: "ops", dependsOn: ["Design: Create project contract"] } }
+{ operation: "task_create", args: { title: "Write code", parentId: "@self", assignedProfile: "developer", dependsOn: ["Setup project"] } }`
 };
 var CAP_ROLE_DEVELOPER = {
   name: "role-developer",
@@ -284,17 +277,28 @@ var CAP_ROLE_DEVELOPER = {
 You WRITE CODE. Execute the task directly using write_file, patch_file, and run_shell.
 
 Your job:
-1. Read the task description (including the project brief)
-2. Create a plan with CONCRETE file operations (write_file, patch_file, run_shell)
-3. Execute every step \u2014 produce actual files on disk
-4. Verify your work compiles and is correct
+1. Read .design.md in the project root to understand interfaces and contracts
+2. Read files created by previous tasks (your dependencies are done \u2014 their files are on disk)
+3. Write code that MATCHES the contracts in .design.md exactly \u2014 same types, same function signatures, same exports
+4. Verify your imports resolve to real exports in existing files
 
 You do NOT have task_create. You cannot create subtasks or delegate.
 If the task seems too large, do your best \u2014 the orchestrator already decomposed it for you.
 
+### File Paths
+All paths in write_file/patch_file are RELATIVE TO THE WORKSPACE ROOT. If the task says "inside todo-app/", your paths MUST start with todo-app/ (e.g., todo-app/src/cli.ts, NOT src/cli.ts).
+
+### Code Quality
+- Write COMPLETE, WORKING code. No TODOs, no placeholders, no empty function bodies, no "// implement later".
+- Every function must be fully implemented with real logic.
+- Use proper TypeScript types. Use strict mode patterns.
+- Export everything that other files will import.
+- Handle edge cases (empty input, file not found, invalid args).
+- Use ESM-compatible patterns: import.meta.url instead of __dirname, import.meta.filename instead of __filename. Use fileURLToPath(import.meta.url) for path resolution.
+
 ### Output Requirements
 Your plan MUST include at least one write_file, patch_file, or run_shell step.
-A plan with only "respond" steps is a FAILURE \u2014 you must produce artifacts.`
+A plan with only read_file, list_files, or respond steps is a FAILURE \u2014 you must produce artifacts.`
 };
 var CAP_ROLE_REVIEWER = {
   name: "role-reviewer",
@@ -318,10 +322,19 @@ var CAP_ROLE_OPS = {
 You SET UP infrastructure \u2014 package.json, tsconfig.json, directory structure, dependencies.
 
 Your job:
-1. Initialize project structure (create config files, directories)
-2. Install dependencies with run_shell
-3. Ensure the project builds and tests can run
+1. Create the project directory first: run_shell with mkdir -p <project>/src
+2. Write config files (package.json, tsconfig.json) using write_file
+3. Install dependencies with run_shell (npm install)
+4. Ensure the project structure is ready for developers
+
+### File Paths
+All paths are RELATIVE TO THE WORKSPACE ROOT. If the project is in a subfolder (e.g., todo-app/), ALL your paths must include that prefix: todo-app/package.json, todo-app/tsconfig.json, todo-app/src/.
 
+### Design Tasks
+When the task is a Design task, create a .design.md file with detailed TypeScript interfaces, module exports, and dependency graph. This file must contain copy-paste ready interface definitions that developers will implement exactly.
+
+### Output Requirements
+Your plan MUST include write_file and/or run_shell steps that create real files.
 You do NOT have task_create. You execute infrastructure tasks directly.`
 };
 var CAP_FILE_OPS = {

package/dist/ui/swarm-dashboard.js

@@ -943,6 +943,25 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
       if (!data) return;
       const t = data.task ?? data;
       setTask(t);
+      const rs = t.context;
+      const summaries = rs?.runSummaries;
+      if (summaries?.length) {
+        setHistory((prev) => {
+          if (prev.length > 0) return prev;
+          return summaries.map((s) => ({
+            id: s.runId,
+            runId: s.runId,
+            outcome: s.outcome,
+            summary: s.summary,
+            report: s.report,
+            filesModified: s.filesModified,
+            durationMs: s.durationMs,
+            cost: s.cost,
+            tokensUsed: s.tokensUsed,
+            error: s.error
+          }));
+        });
+      }
       if (data.subtasks && Array.isArray(data.subtasks)) {
         setSubtasks(data.subtasks);
       } else if (t.isParent) {
@@ -959,13 +978,14 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
     try {
       const raw = await callTool("fw_weaver_history", { taskId });
       const data = typeof raw === "string" ? JSON.parse(raw) : raw;
-      if (Array.isArray(data)) {
+      if (Array.isArray(data) && data.length > 0) {
         setHistory(
           data.map((r) => {
             const costObj = r.cost && typeof r.cost === "object" ? r.cost : void 0;
             return { ...r, costDetail: costObj, cost: costObj?.totalCost };
           })
         );
+        return;
       }
     } catch {
     }
@@ -1380,7 +1400,7 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
             React6.createElement(
               Flex5,
               { variant: "row-center-start-nowrap-6" },
-              task.status === "failed" && React6.createElement(Button2, {
+              (task.status === "failed" || task.status === "open" && task.attempt >= task.maxAttempts) && React6.createElement(Button2, {
                 size: "xs",
                 variant: "fill",
                 color: "primary",
@@ -2738,35 +2758,28 @@ var CAP_ROLE_ORCHESTRATOR = {
 You DECOMPOSE and ASSIGN. You never write code or create files directly.
 
 Your job:
-1. Analyze the objective and understand the project scope
-2. Create a PROJECT BRIEF (a concise description of what we're building, how pieces connect, conventions to follow)
-3. Break the objective into focused subtasks using task_create. The prompt contains "Task ID: <id>" \u2014 use that exact ID value as parentId in every task_create call so subtasks appear as children.
-4. ALWAYS set assignedProfile on every subtask to one of these three:
-   - "developer" \u2192 code writing, file creation, implementation
-   - "reviewer" \u2192 code review, quality checks, security audit
-   - "ops" \u2192 project setup, dependencies, config, infrastructure
-   NEVER set assignedProfile to "orchestrator". You are the orchestrator \u2014 assigning to yourself creates an infinite loop. Only "developer", "reviewer", or "ops".
-5. Set dependencies so tasks execute in the right order
-   Use the EXACT title of a previous subtask as the dependsOn value. The system resolves titles to real task IDs at execution time. Example: dependsOn: ["Setup: Initialize project structure"]
-6. Include the project brief in every subtask's description
+1. Analyze the objective
+2. Break it into focused subtasks via task_create. Set parentId to "@self" on every subtask.
+3. ALWAYS set assignedProfile: "developer", "reviewer", or "ops".
+   NEVER set assignedProfile to "orchestrator" \u2014 assigning to yourself creates an infinite loop.
+4. Use the EXACT title of a previous subtask as dependsOn. The system resolves titles to real task IDs.
+5. Include a project brief in every subtask: "PROJECT: [what]. FILES: [exact paths from workspace root]. CONVENTIONS: [patterns]."
 
-CRITICAL: You do NOT have write_file, patch_file, or run_shell. You cannot execute code \u2014 only plan and delegate to developer/reviewer/ops.
+CRITICAL: You do NOT have write_file, patch_file, or run_shell. Only plan and delegate.
 
-### Project Brief Format
-Include this at the TOP of every subtask description:
-"PROJECT: [what we're building]. STRUCTURE: [file layout]. CONVENTIONS: [naming, patterns, exports]."
+### Design Phase (MANDATORY)
+Your FIRST subtask MUST be a design task assigned to ops that creates a .design.md file in the project root. This is the single source of truth. It must contain:
+- Module map, TypeScript interfaces (copy-paste ready), export contracts (function signatures)
+- Dependency graph, conventions (naming, error handling, patterns)
+Every subsequent developer task MUST read .design.md before writing code.
 
 ### Subtask Quality
-Each subtask must be:
-- Focused (one file or one concern)
-- Self-contained (has enough context to execute independently)
-- Properly routed (assignedProfile is set)
-- Ordered (dependsOn reflects real dependencies)
+Each subtask: focused (one concern), self-contained, properly routed, ordered by dependsOn.
 
 ### Example
-For a task with Task ID "abc123":
-{ operation: "task_create", args: { title: "Setup project", parentId: "abc123", assignedProfile: "ops", dependsOn: [] } }
-{ operation: "task_create", args: { title: "Write code", parentId: "abc123", assignedProfile: "developer", dependsOn: ["Setup project"] } }`
+{ operation: "task_create", args: { title: "Design: Create project contract", parentId: "@self", assignedProfile: "ops", complexity: "complex", description: "Create todo-app/.design.md with module map, TypeScript interfaces, export contracts.", dependsOn: [] } }
+{ operation: "task_create", args: { title: "Setup project", parentId: "@self", assignedProfile: "ops", dependsOn: ["Design: Create project contract"] } }
+{ operation: "task_create", args: { title: "Write code", parentId: "@self", assignedProfile: "developer", dependsOn: ["Setup project"] } }`
 };
 var CAP_ROLE_DEVELOPER = {
   name: "role-developer",
@@ -2775,17 +2788,28 @@ var CAP_ROLE_DEVELOPER = {
 You WRITE CODE. Execute the task directly using write_file, patch_file, and run_shell.
 
 Your job:
-1. Read the task description (including the project brief)
-2. Create a plan with CONCRETE file operations (write_file, patch_file, run_shell)
-3. Execute every step \u2014 produce actual files on disk
-4. Verify your work compiles and is correct
+1. Read .design.md in the project root to understand interfaces and contracts
+2. Read files created by previous tasks (your dependencies are done \u2014 their files are on disk)
+3. Write code that MATCHES the contracts in .design.md exactly \u2014 same types, same function signatures, same exports
+4. Verify your imports resolve to real exports in existing files
 
 You do NOT have task_create. You cannot create subtasks or delegate.
 If the task seems too large, do your best \u2014 the orchestrator already decomposed it for you.
 
+### File Paths
+All paths in write_file/patch_file are RELATIVE TO THE WORKSPACE ROOT. If the task says "inside todo-app/", your paths MUST start with todo-app/ (e.g., todo-app/src/cli.ts, NOT src/cli.ts).
+
+### Code Quality
+- Write COMPLETE, WORKING code. No TODOs, no placeholders, no empty function bodies, no "// implement later".
+- Every function must be fully implemented with real logic.
+- Use proper TypeScript types. Use strict mode patterns.
+- Export everything that other files will import.
+- Handle edge cases (empty input, file not found, invalid args).
+- Use ESM-compatible patterns: import.meta.url instead of __dirname, import.meta.filename instead of __filename. Use fileURLToPath(import.meta.url) for path resolution.
+
 ### Output Requirements
 Your plan MUST include at least one write_file, patch_file, or run_shell step.
-A plan with only "respond" steps is a FAILURE \u2014 you must produce artifacts.`
+A plan with only read_file, list_files, or respond steps is a FAILURE \u2014 you must produce artifacts.`
 };
 var CAP_ROLE_REVIEWER = {
   name: "role-reviewer",
@@ -2809,10 +2833,19 @@ var CAP_ROLE_OPS = {
 You SET UP infrastructure \u2014 package.json, tsconfig.json, directory structure, dependencies.
 
 Your job:
-1. Initialize project structure (create config files, directories)
-2. Install dependencies with run_shell
-3. Ensure the project builds and tests can run
+1. Create the project directory first: run_shell with mkdir -p <project>/src
+2. Write config files (package.json, tsconfig.json) using write_file
+3. Install dependencies with run_shell (npm install)
+4. Ensure the project structure is ready for developers
+
+### File Paths
+All paths are RELATIVE TO THE WORKSPACE ROOT. If the project is in a subfolder (e.g., todo-app/), ALL your paths must include that prefix: todo-app/package.json, todo-app/tsconfig.json, todo-app/src/.
 
+### Design Tasks
+When the task is a Design task, create a .design.md file with detailed TypeScript interfaces, module exports, and dependency graph. This file must contain copy-paste ready interface definitions that developers will implement exactly.
+
+### Output Requirements
+Your plan MUST include write_file and/or run_shell steps that create real files.
 You do NOT have task_create. You execute infrastructure tasks directly.`
 };
 var CAP_FILE_OPS = {
@@ -4349,7 +4382,7 @@ function SwarmDashboard() {
     React11.createElement(Tabs2, {
       tabs: [
         { id: "tasks", title: `Tasks (${tasks.length})` },
-        { id: "bots", title: hasSwarmInstances ? `Instances (${swarmInstanceEntries.length})` : `Bots (${registeredBots.length})` },
+        { id: "bots", title: hasSwarmInstances ? `Workers (${swarmInstanceEntries.length})` : `Bots (${registeredBots.length})` },
         { id: "profiles", title: `Profiles (${profiles.length})` },
         { id: "config", title: "Config" }
       ],
@@ -4490,7 +4523,7 @@ function SwarmDashboard() {
               variant: "smallCaption-regular",
               color: "color-text-subtle",
               style: { width: "120px", flexShrink: 0 }
-            }, "Instance"),
+            }, "Worker"),
             React11.createElement(Typography10, {
               variant: "smallCaption-regular",
               color: "color-text-subtle",
@@ -4530,7 +4563,7 @@ function SwarmDashboard() {
               key: inst.instanceId,
               bot: {
                 botId: inst.instanceId,
-                botName: `${inst.profileId} #${inst.index}`,
+                botName: inst.profileId ? `${inst.instanceId} (${inst.profileId})` : inst.instanceId,
                 status: inst.status,
                 currentTaskId: inst.currentTaskId,
                 currentRunId: inst.currentRunId,

package/dist/ui/task-detail-view.js

@@ -437,6 +437,25 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
       if (!data) return;
       const t = data.task ?? data;
       setTask(t);
+      const rs = t.context;
+      const summaries = rs?.runSummaries;
+      if (summaries?.length) {
+        setHistory((prev) => {
+          if (prev.length > 0) return prev;
+          return summaries.map((s) => ({
+            id: s.runId,
+            runId: s.runId,
+            outcome: s.outcome,
+            summary: s.summary,
+            report: s.report,
+            filesModified: s.filesModified,
+            durationMs: s.durationMs,
+            cost: s.cost,
+            tokensUsed: s.tokensUsed,
+            error: s.error
+          }));
+        });
+      }
       if (data.subtasks && Array.isArray(data.subtasks)) {
         setSubtasks(data.subtasks);
       } else if (t.isParent) {
@@ -453,13 +472,14 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
     try {
       const raw = await callTool("fw_weaver_history", { taskId });
       const data = typeof raw === "string" ? JSON.parse(raw) : raw;
-      if (Array.isArray(data)) {
+      if (Array.isArray(data) && data.length > 0) {
         setHistory(
           data.map((r) => {
             const costObj = r.cost && typeof r.cost === "object" ? r.cost : void 0;
             return { ...r, costDetail: costObj, cost: costObj?.totalCost };
           })
         );
+        return;
       }
     } catch {
     }
@@ -874,7 +894,7 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
             React2.createElement(
               Flex,
               { variant: "row-center-start-nowrap-6" },
-              task.status === "failed" && React2.createElement(Button, {
+              (task.status === "failed" || task.status === "open" && task.attempt >= task.maxAttempts) && React2.createElement(Button, {
                 size: "xs",
                 variant: "fill",
                 color: "primary",

package/dist/workflows/weaver-bot.d.ts

@@ -42,10 +42,10 @@
  * @connect readWf.onSuccess -> report.execute
  * @connect abort.onSuccess -> report.execute
  * @connect notify.onSuccess -> report.execute
- * @connect gitOps.ctx -> report.mainCtx
+ * @connect mergePlan.ctx -> report.mainCtx
  * @connect readWf.ctx -> report.readCtx
  * @connect abort.ctx -> report.abortCtx
- * @connect execRetry.ctx -> report.failCtx
+ * @connect plan.ctx -> report.failCtx
  * @connect report.summary -> Exit.summary
  * @param execute [order:-1] - Execute
  * @param taskJson [order:0] - TaskJson

package/dist/workflows/weaver-bot.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"weaver-bot.d.ts","sourceRoot":"","sources":["../../src/workflows/weaver-bot.ts"],"names":[],"mappings":"AAuaA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAwDG;AACH,wBAAsB,SAAS,CAC7B,OAAO,EAAE,OAAO,EAChB,MAAM,EAAE;IAAE,QAAQ,CAAC,EAAE,MAAM,CAAC;IAAC,UAAU,CAAC,EAAE,MAAM,CAAC;IAAC,YAAY,CAAC,EAAE,MAAM,CAAA;CAAE,EACzE,eAAe,CAAC,EAAE,WAAW,GAC5B,OAAO,CAAC;IAAE,SAAS,EAAE,OAAO,CAAC;IAAC,SAAS,EAAE,OAAO,CAAC;IAAC,OAAO,EAAE,MAAM,GAAG,IAAI,CAAA;CAAE,CAAC,CAwqD7E"}
+{"version":3,"file":"weaver-bot.d.ts","sourceRoot":"","sources":["../../src/workflows/weaver-bot.ts"],"names":[],"mappings":"AAuaA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAwDG;AACH,wBAAsB,SAAS,CAC7B,OAAO,EAAE,OAAO,EAChB,MAAM,EAAE;IAAE,QAAQ,CAAC,EAAE,MAAM,CAAC;IAAC,UAAU,CAAC,EAAE,MAAM,CAAC;IAAC,YAAY,CAAC,EAAE,MAAM,CAAA;CAAE,EACzE,eAAe,CAAC,EAAE,WAAW,GAC5B,OAAO,CAAC;IAAE,SAAS,EAAE,OAAO,CAAC;IAAC,SAAS,EAAE,OAAO,CAAC;IAAC,OAAO,EAAE,MAAM,GAAG,IAAI,CAAA;CAAE,CAAC,CAyqD7E"}

package/dist/workflows/weaver-bot.js

@@ -299,10 +299,10 @@ class GeneratedExecutionContext {
  * @connect readWf.onSuccess -> report.execute
  * @connect abort.onSuccess -> report.execute
  * @connect notify.onSuccess -> report.execute
- * @connect gitOps.ctx -> report.mainCtx
+ * @connect mergePlan.ctx -> report.mainCtx
  * @connect readWf.ctx -> report.readCtx
  * @connect abort.ctx -> report.abortCtx
- * @connect execRetry.ctx -> report.failCtx
+ * @connect plan.ctx -> report.failCtx
  * @connect report.summary -> Exit.summary
  * @param execute [order:-1] - Execute
  * @param taskJson [order:0] - TaskJson
@@ -1926,16 +1926,17 @@ export async function weaverBot(execute, params, __abortSignal__) {
         try {
             const report_execute = (readWfIdx !== undefined ? await ctx.getVariable({ id: 'readWf', portName: 'onSuccess', executionIndex: readWfIdx }) : false) || (abortIdx !== undefined ? await ctx.getVariable({ id: 'abort', portName: 'onSuccess', executionIndex: abortIdx }) : false) || (notifyIdx !== undefined ? await ctx.getVariable({ id: 'notify', portName: 'onSuccess', executionIndex: notifyIdx }) : false) || (gitOpsIdx !== undefined ? await ctx.getVariable({ id: 'gitOps', portName: 'onSuccess', executionIndex: gitOpsIdx }) : false) || (receiveIdx !== undefined ? await ctx.getVariable({ id: 'receive', portName: 'onFailure', executionIndex: receiveIdx }) : false) || (planIdx !== undefined ? await ctx.getVariable({ id: 'plan', portName: 'onFailure', executionIndex: planIdx }) : false) || (execRetryIdx !== undefined ? await ctx.getVariable({ id: 'execRetry', portName: 'onFailure', executionIndex: execRetryIdx }) : false);
             await ctx.setVariable({ id: 'report', portName: 'execute', executionIndex: reportIdx, nodeTypeName: 'weaverBotReport' }, report_execute);
-            const report_mainCtx = gitOpsIdx !== undefined ? await ctx.getVariable({ id: 'gitOps', portName: 'ctx', executionIndex: gitOpsIdx }) : undefined;
+            const report_mainCtx = mergePlanIdx !== undefined ? await ctx.getVariable({ id: 'mergePlan', portName: 'ctx', executionIndex: mergePlanIdx }) : undefined;
             await ctx.setVariable({ id: 'report', portName: 'mainCtx', executionIndex: reportIdx, nodeTypeName: 'weaverBotReport' }, report_mainCtx);
             const report_readCtx = readWfIdx !== undefined ? await ctx.getVariable({ id: 'readWf', portName: 'ctx', executionIndex: readWfIdx }) : undefined;
             await ctx.setVariable({ id: 'report', portName: 'readCtx', executionIndex: reportIdx, nodeTypeName: 'weaverBotReport' }, report_readCtx);
             const report_abortCtx = abortIdx !== undefined ? await ctx.getVariable({ id: 'abort', portName: 'ctx', executionIndex: abortIdx }) : undefined;
             await ctx.setVariable({ id: 'report', portName: 'abortCtx', executionIndex: reportIdx, nodeTypeName: 'weaverBotReport' }, report_abortCtx);
-            const report_failCtx = execRetryIdx !== undefined ? await ctx.getVariable({ id: 'execRetry', portName: 'ctx', executionIndex: execRetryIdx }) : undefined;
+            const report_failCtx = planIdx !== undefined ? await ctx.getVariable({ id: 'plan', portName: 'ctx', executionIndex: planIdx }) : undefined;
             await ctx.setVariable({ id: 'report', portName: 'failCtx', executionIndex: reportIdx, nodeTypeName: 'weaverBotReport' }, report_failCtx);
             const reportResult = await weaverBotReport(report_execute, report_mainCtx, report_readCtx, report_abortCtx, report_failCtx);
             await ctx.setVariable({ id: 'report', portName: 'summary', executionIndex: reportIdx, nodeTypeName: 'weaverBotReport' }, reportResult.summary);
+            await ctx.setVariable({ id: 'report', portName: 'report', executionIndex: reportIdx, nodeTypeName: 'weaverBotReport' }, reportResult.report);
             await ctx.setVariable({ id: 'report', portName: 'reportJson', executionIndex: reportIdx, nodeTypeName: 'weaverBotReport' }, reportResult.reportJson);
             await ctx.setVariable({ id: 'report', portName: 'onFailure', executionIndex: reportIdx, nodeTypeName: 'weaverBotReport' }, reportResult.onFailure);
             await ctx.setVariable({ id: 'report', portName: 'onSuccess', executionIndex: reportIdx, nodeTypeName: 'weaverBotReport' }, reportResult.onSuccess);