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

package/dist/ui/capability-editor.js

@@ -62,6 +62,7 @@ Do NOT describe what you would do \u2014 actually do it by calling tools.
 
 ## Safety Rules
 - Writes that shrink a file by >50% or write empty content are automatically BLOCKED.
+- NEVER write empty or placeholder files. Every write_file call MUST contain complete, meaningful content.
 - Blocked shell commands: rm -rf, git push, npm publish, sudo, curl|sh.
 - Always validate BEFORE and AFTER patching.
 - Always read a file before patching it (you need exact strings for find/replace).
@@ -78,8 +79,8 @@ You DECOMPOSE and ASSIGN. You never write code or create files directly.
 Your job:
 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.
+3. ALWAYS set assignedProfile: "developer", "reviewer", or "ops" for work tasks.
+   The ONLY exception: your final "Verify & Iterate" task should be assignedProfile: "orchestrator".
 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]."
 
@@ -93,11 +94,35 @@ Every subsequent developer task MUST read .design.md before writing code.
 
 ### Subtask Quality
 Each subtask: focused (one concern), self-contained, properly routed, ordered by dependsOn.
+- If an implementation task covers more than 2 files, SPLIT IT. Each task should produce 1-2 files max.
+- Design/architecture tasks \u2192 assignedProfile: "developer" (not ops). Ops is for infra only.
+- Add scope boundaries: "You may ONLY create/modify these files: [list]."
+
+### Maximize Parallelism
+- Minimize dependencies. Tasks that don't share files should NOT depend on each other.
+- Design and Setup can often run in parallel (setup doesn't need .design.md to create boilerplate).
+- Aim for at least 2 tasks that can run in parallel. If all tasks are serial, reconsider.
+- BAD: A \u2192 B \u2192 C \u2192 D (serial, slow)
+- GOOD: A \u2192 [B + C + D] \u2192 E (A blocks all, B/C/D run in parallel, E waits for all)
+
+### Build Verification Gate
+After implementation tasks, create a verification task (ops profile) that runs \`tsc --noEmit\`.
+This catches compilation errors before tests run, saving time and token spend.
+
+### Verify & Iterate Loop
+Your LAST subtask MUST be a "Verify & Iterate" task assigned to yourself (orchestrator):
+- dependsOn: ALL other subtasks
+- When it runs: review all task results, check for failures, gaps, or quality issues
+- If everything passes: signal done
+- If issues found: create fix tasks + another verify gate
+This creates a self-correcting loop: plan \u2192 execute \u2192 verify \u2192 fix \u2192 verify \u2192 done.
 
 ### Example
-{ 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"] } }`
+{ operation: "task_create", args: { title: "Design: Create project contract", parentId: "@self", assignedProfile: "developer", complexity: "moderate", description: "Create .design.md with interfaces and contracts.", dependsOn: [] } }
+{ operation: "task_create", args: { title: "Setup project", parentId: "@self", assignedProfile: "ops", dependsOn: [] } }
+{ operation: "task_create", args: { title: "Implement storage module", parentId: "@self", assignedProfile: "developer", dependsOn: ["Design: Create project contract", "Setup project"], description: "You may ONLY create: src/types.ts, src/storage.ts" } }
+{ operation: "task_create", args: { title: "Implement HTTP server", parentId: "@self", assignedProfile: "developer", dependsOn: ["Implement storage module"], description: "You may ONLY create: src/server.ts" } }
+{ operation: "task_create", args: { title: "Verify & Iterate", parentId: "@self", assignedProfile: "orchestrator", dependsOn: ["Implement HTTP server"], description: "Review all task results. If issues found, create fix tasks. If all good, signal done." } }`
 };
 var CAP_ROLE_DEVELOPER = {
   name: "role-developer",
@@ -117,6 +142,18 @@ If the task seems too large, do your best \u2014 the orchestrator already decomp
 ### 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).
 
+### Write Protocol
+Before writing ANY file:
+1. list_files to check if the file already exists
+2. If it exists \u2192 read_file, then patch_file with targeted changes
+3. If it does NOT exist \u2192 write_file with COMPLETE content
+Never call write_file on a file that already exists \u2014 the shrink guard will block you and waste a tool call.
+
+### Sibling Awareness
+Your context may include files modified by sibling tasks. Before writing a file:
+- Check "Previous Task Completions" \u2192 if a sibling already created it, READ it first, then patch_file
+- Never blindly overwrite files your siblings created
+
 ### 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.
@@ -180,7 +217,14 @@ var CAP_FILE_OPS = {
 PREFER patch_file over write_file for modifying existing files (surgical edits, no truncation risk).
 Use read_file to understand a file before modifying it.
 Use list_files to discover project structure.
-Writes that shrink a file by >50% or write empty content are automatically BLOCKED.`
+
+## Write Protocol
+Before writing ANY file:
+1. Use list_files to check if the file already exists
+2. If it EXISTS \u2192 read_file first, then patch_file with targeted changes
+3. If it does NOT exist \u2192 write_file with COMPLETE content
+NEVER call write_file on a file that already exists \u2014 use patch_file instead.
+Empty content and writes that shrink an existing file by >50% are automatically BLOCKED and waste a tool call.`
 };
 var CAP_SHELL = {
   name: "shell",
@@ -302,8 +346,9 @@ var CAP_CODE_REVIEW = {
   tools: [OP_READ_FILE, OP_PATCH_FILE, OP_RUN_SHELL],
   prompt: `## Code Review Checklist
 
-### 1. Correctness
+### 1. Correctness & Contract Compliance
 - Does the code do what the task asked?
+- If .design.md exists, verify: exported functions match contracts, interface shapes match, error behavior matches spec
 - Edge cases handled (empty input, null, invalid types)?
 - Error paths covered (try/catch, validation)?
 - Return types match function signature?
@@ -315,16 +360,19 @@ var CAP_CODE_REVIEW = {
 - User input validated and sanitized before use
 - File paths validated (no ../ traversal)
 
-### 3. Style
+### 3. Style & Dead Code
 - Naming is clear and consistent with project conventions
-- No dead code (unused variables, unreachable branches)
+- No dead code (unused variables, unreachable branches, duplicated functions across files)
+- No duplicated logic \u2014 if two files define the same function, flag it
 - No debug statements left in (console.log, debugger)
-- Imports organized, no duplicates
+- Imports organized, no duplicates, no unused imports
 
 ### 4. Testing
 - Unit tests exist for new/changed functions
 - Tests cover happy path AND edge cases
 - Error cases have tests
+- Test isolation: state reset between tests, server handles returned and closed in afterEach
+- No order-dependent tests (each test must pass in isolation)
 - Code coverage adequate (aim for 80%+ of changed code)
 
 ### 5. Performance
@@ -343,11 +391,18 @@ var CAP_WEB = {
 };
 var CAP_CONTEXT = {
   name: "context",
-  description: "Project file listings, directory structure, and workspace context.",
+  description: "Project file listings, directory structure, workspace context, and sibling task awareness.",
   prompt: `## Project Context
 
 Use list_files to understand the project structure before making changes.
-The context bundle (when available) provides a snapshot of the workspace.`
+The context bundle (when available) provides a snapshot of the workspace.
+
+## Sibling Awareness
+Your context includes files modified by sibling tasks (in "Previous Task Completions").
+Before writing a file:
+- Check if it appears in previous task completions \u2192 if yes, read_file first, then patch_file
+- NEVER blindly overwrite files your siblings created
+- If you need to extend a sibling's work, READ their output first and build on it`
 };
 var CAP_VERIFICATION = {
   name: "verification",

package/dist/ui/chat-task-result.js

@@ -18,6 +18,7 @@ function parseResult(result) {
 }
 function statusToIcon(status) {
   switch (status) {
+    case "open":
     case "pending":
     case "blocked":
       return "pending";
@@ -25,7 +26,6 @@ function statusToIcon(status) {
       return "running";
     case "done":
       return "completed";
-    case "failed":
     case "cancelled":
       return "failed";
     default:
@@ -34,16 +34,16 @@ function statusToIcon(status) {
 }
 function statusLabel(status) {
   switch (status) {
+    case "open":
+      return "Open";
     case "pending":
-      return "Pending";
+      return "Queued";
     case "in-progress":
-      return "In Progress";
+      return "Running";
     case "blocked":
       return "Blocked";
     case "done":
       return "Done";
-    case "failed":
-      return "Failed";
     case "cancelled":
       return "Cancelled";
     default:
@@ -51,7 +51,7 @@ function statusLabel(status) {
   }
 }
 function isTerminal(status) {
-  return status === "done" || status === "failed" || status === "cancelled";
+  return status === "done" || status === "cancelled";
 }
 function ChatTaskResult(props) {
   const { result = null, args = {}, callTool, openWorkspace } = props ?? {};
@@ -152,7 +152,7 @@ function ChatTaskResult(props) {
         // Status label
         React.createElement(Typography, {
           variant: "smallCaption-regular",
-          color: task.status === "done" ? "color-text-positive" : task.status === "failed" ? "color-text-negative" : task.status === "in-progress" ? "color-text-info" : "color-text-medium"
+          color: task.status === "done" ? "color-text-positive" : task.status === "cancelled" ? "color-text-negative" : task.status === "in-progress" ? "color-text-info" : "color-text-medium"
         }, statusLabel(task.status)),
         // Subtask progress
         hasSubtasks && React.createElement(Typography, {

package/dist/ui/profile-editor.js

@@ -233,6 +233,7 @@ Do NOT describe what you would do \u2014 actually do it by calling tools.
 
 ## Safety Rules
 - Writes that shrink a file by >50% or write empty content are automatically BLOCKED.
+- NEVER write empty or placeholder files. Every write_file call MUST contain complete, meaningful content.
 - Blocked shell commands: rm -rf, git push, npm publish, sudo, curl|sh.
 - Always validate BEFORE and AFTER patching.
 - Always read a file before patching it (you need exact strings for find/replace).
@@ -249,8 +250,8 @@ You DECOMPOSE and ASSIGN. You never write code or create files directly.
 Your job:
 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.
+3. ALWAYS set assignedProfile: "developer", "reviewer", or "ops" for work tasks.
+   The ONLY exception: your final "Verify & Iterate" task should be assignedProfile: "orchestrator".
 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]."
 
@@ -264,11 +265,35 @@ Every subsequent developer task MUST read .design.md before writing code.
 
 ### Subtask Quality
 Each subtask: focused (one concern), self-contained, properly routed, ordered by dependsOn.
+- If an implementation task covers more than 2 files, SPLIT IT. Each task should produce 1-2 files max.
+- Design/architecture tasks \u2192 assignedProfile: "developer" (not ops). Ops is for infra only.
+- Add scope boundaries: "You may ONLY create/modify these files: [list]."
+
+### Maximize Parallelism
+- Minimize dependencies. Tasks that don't share files should NOT depend on each other.
+- Design and Setup can often run in parallel (setup doesn't need .design.md to create boilerplate).
+- Aim for at least 2 tasks that can run in parallel. If all tasks are serial, reconsider.
+- BAD: A \u2192 B \u2192 C \u2192 D (serial, slow)
+- GOOD: A \u2192 [B + C + D] \u2192 E (A blocks all, B/C/D run in parallel, E waits for all)
+
+### Build Verification Gate
+After implementation tasks, create a verification task (ops profile) that runs \`tsc --noEmit\`.
+This catches compilation errors before tests run, saving time and token spend.
+
+### Verify & Iterate Loop
+Your LAST subtask MUST be a "Verify & Iterate" task assigned to yourself (orchestrator):
+- dependsOn: ALL other subtasks
+- When it runs: review all task results, check for failures, gaps, or quality issues
+- If everything passes: signal done
+- If issues found: create fix tasks + another verify gate
+This creates a self-correcting loop: plan \u2192 execute \u2192 verify \u2192 fix \u2192 verify \u2192 done.
 
 ### Example
-{ 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"] } }`
+{ operation: "task_create", args: { title: "Design: Create project contract", parentId: "@self", assignedProfile: "developer", complexity: "moderate", description: "Create .design.md with interfaces and contracts.", dependsOn: [] } }
+{ operation: "task_create", args: { title: "Setup project", parentId: "@self", assignedProfile: "ops", dependsOn: [] } }
+{ operation: "task_create", args: { title: "Implement storage module", parentId: "@self", assignedProfile: "developer", dependsOn: ["Design: Create project contract", "Setup project"], description: "You may ONLY create: src/types.ts, src/storage.ts" } }
+{ operation: "task_create", args: { title: "Implement HTTP server", parentId: "@self", assignedProfile: "developer", dependsOn: ["Implement storage module"], description: "You may ONLY create: src/server.ts" } }
+{ operation: "task_create", args: { title: "Verify & Iterate", parentId: "@self", assignedProfile: "orchestrator", dependsOn: ["Implement HTTP server"], description: "Review all task results. If issues found, create fix tasks. If all good, signal done." } }`
 };
 var CAP_ROLE_DEVELOPER = {
   name: "role-developer",
@@ -288,6 +313,18 @@ If the task seems too large, do your best \u2014 the orchestrator already decomp
 ### 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).
 
+### Write Protocol
+Before writing ANY file:
+1. list_files to check if the file already exists
+2. If it exists \u2192 read_file, then patch_file with targeted changes
+3. If it does NOT exist \u2192 write_file with COMPLETE content
+Never call write_file on a file that already exists \u2014 the shrink guard will block you and waste a tool call.
+
+### Sibling Awareness
+Your context may include files modified by sibling tasks. Before writing a file:
+- Check "Previous Task Completions" \u2192 if a sibling already created it, READ it first, then patch_file
+- Never blindly overwrite files your siblings created
+
 ### 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.
@@ -351,7 +388,14 @@ var CAP_FILE_OPS = {
 PREFER patch_file over write_file for modifying existing files (surgical edits, no truncation risk).
 Use read_file to understand a file before modifying it.
 Use list_files to discover project structure.
-Writes that shrink a file by >50% or write empty content are automatically BLOCKED.`
+
+## Write Protocol
+Before writing ANY file:
+1. Use list_files to check if the file already exists
+2. If it EXISTS \u2192 read_file first, then patch_file with targeted changes
+3. If it does NOT exist \u2192 write_file with COMPLETE content
+NEVER call write_file on a file that already exists \u2014 use patch_file instead.
+Empty content and writes that shrink an existing file by >50% are automatically BLOCKED and waste a tool call.`
 };
 var CAP_SHELL = {
   name: "shell",
@@ -473,8 +517,9 @@ var CAP_CODE_REVIEW = {
   tools: [OP_READ_FILE, OP_PATCH_FILE, OP_RUN_SHELL],
   prompt: `## Code Review Checklist
 
-### 1. Correctness
+### 1. Correctness & Contract Compliance
 - Does the code do what the task asked?
+- If .design.md exists, verify: exported functions match contracts, interface shapes match, error behavior matches spec
 - Edge cases handled (empty input, null, invalid types)?
 - Error paths covered (try/catch, validation)?
 - Return types match function signature?
@@ -486,16 +531,19 @@ var CAP_CODE_REVIEW = {
 - User input validated and sanitized before use
 - File paths validated (no ../ traversal)
 
-### 3. Style
+### 3. Style & Dead Code
 - Naming is clear and consistent with project conventions
-- No dead code (unused variables, unreachable branches)
+- No dead code (unused variables, unreachable branches, duplicated functions across files)
+- No duplicated logic \u2014 if two files define the same function, flag it
 - No debug statements left in (console.log, debugger)
-- Imports organized, no duplicates
+- Imports organized, no duplicates, no unused imports
 
 ### 4. Testing
 - Unit tests exist for new/changed functions
 - Tests cover happy path AND edge cases
 - Error cases have tests
+- Test isolation: state reset between tests, server handles returned and closed in afterEach
+- No order-dependent tests (each test must pass in isolation)
 - Code coverage adequate (aim for 80%+ of changed code)
 
 ### 5. Performance
@@ -514,11 +562,18 @@ var CAP_WEB = {
 };
 var CAP_CONTEXT = {
   name: "context",
-  description: "Project file listings, directory structure, and workspace context.",
+  description: "Project file listings, directory structure, workspace context, and sibling task awareness.",
   prompt: `## Project Context
 
 Use list_files to understand the project structure before making changes.
-The context bundle (when available) provides a snapshot of the workspace.`
+The context bundle (when available) provides a snapshot of the workspace.
+
+## Sibling Awareness
+Your context includes files modified by sibling tasks (in "Previous Task Completions").
+Before writing a file:
+- Check if it appears in previous task completions \u2192 if yes, read_file first, then patch_file
+- NEVER blindly overwrite files your siblings created
+- If you need to extend a sibling's work, READ their output first and build on it`
 };
 var CAP_VERIFICATION = {
   name: "verification",

package/dist/ui/swarm-dashboard.js

@@ -403,10 +403,10 @@ var React4 = require("react");
 var { useState: useState2 } = React4;
 var { Flex: Flex4, Typography: Typography4, Icon: Icon2, StatusIcon: StatusIcon2, Chip, ScrollArea, Badge, EmptyState } = require("@fw/plugin-ui-kit");
 var statusToIcon = {
+  "open": "pending",
   "pending": "pending",
   "in-progress": "running",
   "done": "completed",
-  "failed": "failed",
   "blocked": "pending",
   "cancelled": "failed"
 };
@@ -854,18 +854,18 @@ var {
   useEventStream
 } = require("@fw/plugin-ui-kit");
 var statusToIcon2 = {
+  "open": "pending",
   "pending": "pending",
   "in-progress": "running",
   "done": "completed",
-  "failed": "failed",
   "blocked": "pending",
   "cancelled": "failed"
 };
 var statusToLabel2 = {
-  "pending": "Pending",
-  "in-progress": "In Progress",
+  "open": "Open",
+  "pending": "Queued",
+  "in-progress": "Running",
   "done": "Done",
-  "failed": "Failed",
   "blocked": "Blocked",
   "cancelled": "Cancelled"
 };
@@ -1272,9 +1272,9 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
         Flex5,
         { variant: "row-center-start-wrap-6" },
         React6.createElement(Chip2, {
-          label: statusToLabel2[task.status] || task.status || "pending",
+          label: statusToLabel2[task.status] || task.status || "open",
           size: "small",
-          color: task.status === "done" ? "color-status-positive" : task.status === "failed" ? "color-status-negative" : task.status === "in-progress" ? "color-status-info" : task.status === "blocked" ? "color-status-caution" : "color-brand-alt"
+          color: task.status === "done" ? "color-status-positive" : task.status === "cancelled" ? "color-status-negative" : task.status === "in-progress" ? "color-status-info" : task.status === "blocked" ? "color-status-caution" : "color-brand-alt"
         }),
         task.assignedProfile && React6.createElement(Chip2, { key: `profile-${task.assignedProfile}`, label: task.assignedProfile, size: "small", color: "color-status-info" }),
         task.priority > 0 && React6.createElement(Chip2, {
@@ -1282,10 +1282,10 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
           size: "small",
           color: task.priority >= 3 ? "color-status-caution" : "color-status-info"
         }),
-        task.attempt != null && task.maxAttempts != null && React6.createElement(Typography5, {
+        task.maxAttempts != null && task.maxAttempts > 1 && React6.createElement(Typography5, {
           variant: "smallCaption-regular",
           color: "color-text-subtle"
-        }, `Attempt ${task.attempt}/${task.maxAttempts}`)
+        }, `${task.runs?.length ?? 0}/${task.maxAttempts} runs`)
       ),
       // Description
       task.description && React6.createElement(Typography5, {
@@ -1400,7 +1400,7 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
             React6.createElement(
               Flex5,
               { variant: "row-center-start-nowrap-6" },
-              (task.status === "failed" || task.status === "open" && task.attempt >= task.maxAttempts) && React6.createElement(Button2, {
+              task.status === "open" && (task.attempt ?? 0) > 0 && React6.createElement(Button2, {
                 size: "xs",
                 variant: "fill",
                 color: "primary",
@@ -1408,7 +1408,7 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
                 loading: actionLoading === "retry",
                 disabled: !!actionLoading
               }, "Retry Task"),
-              (task.status === "pending" || task.status === "in-progress" || task.status === "blocked") && React6.createElement(Button2, {
+              (task.status === "open" || task.status === "pending" || task.status === "in-progress" || task.status === "blocked") && React6.createElement(Button2, {
                 size: "xs",
                 variant: "outlined",
                 color: "danger",
@@ -1663,11 +1663,11 @@ var COMPLEXITY_OPTIONS = [
   { id: "complex", label: "Complex" }
 ];
 var STATUS_COLOR = {
+  "open": "color-brand-alt",
   "pending": "color-brand-alt",
   "in-progress": "color-status-info",
   "blocked": "color-status-caution",
   "done": "color-status-positive",
-  "failed": "color-status-negative",
   "cancelled": "color-status-negative"
 };
 function TaskEditor({ mode, taskId, onSave, onCancel, onDelete }) {
@@ -2744,6 +2744,7 @@ Do NOT describe what you would do \u2014 actually do it by calling tools.
 
 ## Safety Rules
 - Writes that shrink a file by >50% or write empty content are automatically BLOCKED.
+- NEVER write empty or placeholder files. Every write_file call MUST contain complete, meaningful content.
 - Blocked shell commands: rm -rf, git push, npm publish, sudo, curl|sh.
 - Always validate BEFORE and AFTER patching.
 - Always read a file before patching it (you need exact strings for find/replace).
@@ -2760,8 +2761,8 @@ You DECOMPOSE and ASSIGN. You never write code or create files directly.
 Your job:
 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.
+3. ALWAYS set assignedProfile: "developer", "reviewer", or "ops" for work tasks.
+   The ONLY exception: your final "Verify & Iterate" task should be assignedProfile: "orchestrator".
 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]."
 
@@ -2775,11 +2776,35 @@ Every subsequent developer task MUST read .design.md before writing code.
 
 ### Subtask Quality
 Each subtask: focused (one concern), self-contained, properly routed, ordered by dependsOn.
+- If an implementation task covers more than 2 files, SPLIT IT. Each task should produce 1-2 files max.
+- Design/architecture tasks \u2192 assignedProfile: "developer" (not ops). Ops is for infra only.
+- Add scope boundaries: "You may ONLY create/modify these files: [list]."
+
+### Maximize Parallelism
+- Minimize dependencies. Tasks that don't share files should NOT depend on each other.
+- Design and Setup can often run in parallel (setup doesn't need .design.md to create boilerplate).
+- Aim for at least 2 tasks that can run in parallel. If all tasks are serial, reconsider.
+- BAD: A \u2192 B \u2192 C \u2192 D (serial, slow)
+- GOOD: A \u2192 [B + C + D] \u2192 E (A blocks all, B/C/D run in parallel, E waits for all)
+
+### Build Verification Gate
+After implementation tasks, create a verification task (ops profile) that runs \`tsc --noEmit\`.
+This catches compilation errors before tests run, saving time and token spend.
+
+### Verify & Iterate Loop
+Your LAST subtask MUST be a "Verify & Iterate" task assigned to yourself (orchestrator):
+- dependsOn: ALL other subtasks
+- When it runs: review all task results, check for failures, gaps, or quality issues
+- If everything passes: signal done
+- If issues found: create fix tasks + another verify gate
+This creates a self-correcting loop: plan \u2192 execute \u2192 verify \u2192 fix \u2192 verify \u2192 done.
 
 ### Example
-{ 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"] } }`
+{ operation: "task_create", args: { title: "Design: Create project contract", parentId: "@self", assignedProfile: "developer", complexity: "moderate", description: "Create .design.md with interfaces and contracts.", dependsOn: [] } }
+{ operation: "task_create", args: { title: "Setup project", parentId: "@self", assignedProfile: "ops", dependsOn: [] } }
+{ operation: "task_create", args: { title: "Implement storage module", parentId: "@self", assignedProfile: "developer", dependsOn: ["Design: Create project contract", "Setup project"], description: "You may ONLY create: src/types.ts, src/storage.ts" } }
+{ operation: "task_create", args: { title: "Implement HTTP server", parentId: "@self", assignedProfile: "developer", dependsOn: ["Implement storage module"], description: "You may ONLY create: src/server.ts" } }
+{ operation: "task_create", args: { title: "Verify & Iterate", parentId: "@self", assignedProfile: "orchestrator", dependsOn: ["Implement HTTP server"], description: "Review all task results. If issues found, create fix tasks. If all good, signal done." } }`
 };
 var CAP_ROLE_DEVELOPER = {
   name: "role-developer",
@@ -2799,6 +2824,18 @@ If the task seems too large, do your best \u2014 the orchestrator already decomp
 ### 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).
 
+### Write Protocol
+Before writing ANY file:
+1. list_files to check if the file already exists
+2. If it exists \u2192 read_file, then patch_file with targeted changes
+3. If it does NOT exist \u2192 write_file with COMPLETE content
+Never call write_file on a file that already exists \u2014 the shrink guard will block you and waste a tool call.
+
+### Sibling Awareness
+Your context may include files modified by sibling tasks. Before writing a file:
+- Check "Previous Task Completions" \u2192 if a sibling already created it, READ it first, then patch_file
+- Never blindly overwrite files your siblings created
+
 ### 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.
@@ -2862,7 +2899,14 @@ var CAP_FILE_OPS = {
 PREFER patch_file over write_file for modifying existing files (surgical edits, no truncation risk).
 Use read_file to understand a file before modifying it.
 Use list_files to discover project structure.
-Writes that shrink a file by >50% or write empty content are automatically BLOCKED.`
+
+## Write Protocol
+Before writing ANY file:
+1. Use list_files to check if the file already exists
+2. If it EXISTS \u2192 read_file first, then patch_file with targeted changes
+3. If it does NOT exist \u2192 write_file with COMPLETE content
+NEVER call write_file on a file that already exists \u2014 use patch_file instead.
+Empty content and writes that shrink an existing file by >50% are automatically BLOCKED and waste a tool call.`
 };
 var CAP_SHELL = {
   name: "shell",
@@ -2984,8 +3028,9 @@ var CAP_CODE_REVIEW = {
   tools: [OP_READ_FILE, OP_PATCH_FILE, OP_RUN_SHELL],
   prompt: `## Code Review Checklist
 
-### 1. Correctness
+### 1. Correctness & Contract Compliance
 - Does the code do what the task asked?
+- If .design.md exists, verify: exported functions match contracts, interface shapes match, error behavior matches spec
 - Edge cases handled (empty input, null, invalid types)?
 - Error paths covered (try/catch, validation)?
 - Return types match function signature?
@@ -2997,16 +3042,19 @@ var CAP_CODE_REVIEW = {
 - User input validated and sanitized before use
 - File paths validated (no ../ traversal)
 
-### 3. Style
+### 3. Style & Dead Code
 - Naming is clear and consistent with project conventions
-- No dead code (unused variables, unreachable branches)
+- No dead code (unused variables, unreachable branches, duplicated functions across files)
+- No duplicated logic \u2014 if two files define the same function, flag it
 - No debug statements left in (console.log, debugger)
-- Imports organized, no duplicates
+- Imports organized, no duplicates, no unused imports
 
 ### 4. Testing
 - Unit tests exist for new/changed functions
 - Tests cover happy path AND edge cases
 - Error cases have tests
+- Test isolation: state reset between tests, server handles returned and closed in afterEach
+- No order-dependent tests (each test must pass in isolation)
 - Code coverage adequate (aim for 80%+ of changed code)
 
 ### 5. Performance
@@ -3025,11 +3073,18 @@ var CAP_WEB = {
 };
 var CAP_CONTEXT = {
   name: "context",
-  description: "Project file listings, directory structure, and workspace context.",
+  description: "Project file listings, directory structure, workspace context, and sibling task awareness.",
   prompt: `## Project Context
 
 Use list_files to understand the project structure before making changes.
-The context bundle (when available) provides a snapshot of the workspace.`
+The context bundle (when available) provides a snapshot of the workspace.
+
+## Sibling Awareness
+Your context includes files modified by sibling tasks (in "Previous Task Completions").
+Before writing a file:
+- Check if it appears in previous task completions \u2192 if yes, read_file first, then patch_file
+- NEVER blindly overwrite files your siblings created
+- If you need to extend a sibling's work, READ their output first and build on it`
 };
 var CAP_VERIFICATION = {
   name: "verification",

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

@@ -348,18 +348,18 @@ var {
   useEventStream
 } = require("@fw/plugin-ui-kit");
 var statusToIcon = {
+  "open": "pending",
   "pending": "pending",
   "in-progress": "running",
   "done": "completed",
-  "failed": "failed",
   "blocked": "pending",
   "cancelled": "failed"
 };
 var statusToLabel = {
-  "pending": "Pending",
-  "in-progress": "In Progress",
+  "open": "Open",
+  "pending": "Queued",
+  "in-progress": "Running",
   "done": "Done",
-  "failed": "Failed",
   "blocked": "Blocked",
   "cancelled": "Cancelled"
 };
@@ -766,9 +766,9 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
         Flex,
         { variant: "row-center-start-wrap-6" },
         React2.createElement(Chip, {
-          label: statusToLabel[task.status] || task.status || "pending",
+          label: statusToLabel[task.status] || task.status || "open",
           size: "small",
-          color: task.status === "done" ? "color-status-positive" : task.status === "failed" ? "color-status-negative" : task.status === "in-progress" ? "color-status-info" : task.status === "blocked" ? "color-status-caution" : "color-brand-alt"
+          color: task.status === "done" ? "color-status-positive" : task.status === "cancelled" ? "color-status-negative" : task.status === "in-progress" ? "color-status-info" : task.status === "blocked" ? "color-status-caution" : "color-brand-alt"
         }),
         task.assignedProfile && React2.createElement(Chip, { key: `profile-${task.assignedProfile}`, label: task.assignedProfile, size: "small", color: "color-status-info" }),
         task.priority > 0 && React2.createElement(Chip, {
@@ -776,10 +776,10 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
           size: "small",
           color: task.priority >= 3 ? "color-status-caution" : "color-status-info"
         }),
-        task.attempt != null && task.maxAttempts != null && React2.createElement(Typography, {
+        task.maxAttempts != null && task.maxAttempts > 1 && React2.createElement(Typography, {
           variant: "smallCaption-regular",
           color: "color-text-subtle"
-        }, `Attempt ${task.attempt}/${task.maxAttempts}`)
+        }, `${task.runs?.length ?? 0}/${task.maxAttempts} runs`)
       ),
       // Description
       task.description && React2.createElement(Typography, {
@@ -894,7 +894,7 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
             React2.createElement(
               Flex,
               { variant: "row-center-start-nowrap-6" },
-              (task.status === "failed" || task.status === "open" && task.attempt >= task.maxAttempts) && React2.createElement(Button, {
+              task.status === "open" && (task.attempt ?? 0) > 0 && React2.createElement(Button, {
                 size: "xs",
                 variant: "fill",
                 color: "primary",
@@ -902,7 +902,7 @@ function TaskDetailView({ taskId, onBack, onEdit }) {
                 loading: actionLoading === "retry",
                 disabled: !!actionLoading
               }, "Retry Task"),
-              (task.status === "pending" || task.status === "in-progress" || task.status === "blocked") && React2.createElement(Button, {
+              (task.status === "open" || task.status === "pending" || task.status === "in-progress" || task.status === "blocked") && React2.createElement(Button, {
                 size: "xs",
                 variant: "outlined",
                 color: "danger",