@iloom/cli 0.13.0-beta.0 → 0.13.1

package/LICENSE

@@ -20,7 +20,7 @@ it within your organization. What is prohibited is redistributing or offering
 access to this software (in original or modified form) as part of something
 you sell or provide to others.
 
-Change Date: 2030-03-10
+Change Date: 2030-03-16
 Change License: Apache License 2.0
 
 For clarity, on or after the Change Date, the Licensed Work will

package/README.md

@@ -97,7 +97,7 @@ Each loom is a fully isolated container for your work:
 
 *   **Git Worktree:** A separate filesystem at ~/project-looms/issue-25/. No stashing, no branch switching overhead.
     
-*   **Database Branch:** (Neon and Supabase support) Schema changes in this loom are isolated—they won't break your main environment or your other active looms.
+*   **Database Branch:** (Neon support) Schema changes in this loom are isolated—they won't break your main environment or your other active looms.
 
 *   **Environment Variables:** Each loom has its own environment files (`.env`, `.env.local`, `.env.development`, `.env.development.local`). Uses `development` by default, override with `DOTENV_FLOW_NODE_ENV`. See [Secret Storage Limitations](#multi-language-project-support) for frameworks with encrypted credentials.
 
@@ -153,7 +153,7 @@ Configuration
 
 ### 1. Interactive Setup (Recommended)
 
-The easiest way to configure iloom is the interactive wizard. It guides you through setting up your environment (GitHub/Linear, Neon/Supabase, IDE).
+The easiest way to configure iloom is the interactive wizard. It guides you through setting up your environment (GitHub/Linear, Neon, IDE).
 
 You can even use natural language to jump-start the process:
 
@@ -206,21 +206,6 @@ This example shows how to configure a project-wide default (e.g., GitHub remote)
 }
 ```
 
-Or, if using Supabase (requires a paid plan):
-
-```json
-{
-  "databaseProviders": {
-    "supabase": {
-      "projectRef": "abcdefghijklmnop",
-      "parentBranch": "main"
-    }
-  }
-}
-```
-
-> Only one database provider can be active at a time. See [Database Branching](docs/iloom-commands.md#database-branching) for full details.
-
 **.iloom/settings.local.json (Gitignored)**
 
 ```json
@@ -895,7 +880,7 @@ License & Name
     
 *   ❌ You cannot resell iloom itself as a product or SaaS.
     
-*   Converts to Apache 2.0 on 2030-03-10.
+*   Converts to Apache 2.0 on 2030-03-16.
     
 
 See [LICENSE](https://raw.githubusercontent.com/iloom-ai/iloom-cli/main/LICENSE) for complete terms.

package/dist/{ClaudeContextManager-RRGREEZQ.js → ClaudeContextManager-ZH6LEA5I.js}

@@ -1,14 +1,14 @@
 #!/usr/bin/env node
 import {
   ClaudeContextManager
-} from "./chunk-JDN4SPV3.js";
-import "./chunk-XCP2WDYA.js";
-import "./chunk-7RCUWU3I.js";
+} from "./chunk-WYDLOQYO.js";
+import "./chunk-T4NESGYB.js";
+import "./chunk-MRPIDNZU.js";
 import "./chunk-DDHWZNGL.js";
-import "./chunk-WGUGB54H.js";
+import "./chunk-F5NKWLMQ.js";
 import "./chunk-FTYWGQFM.js";
 import "./chunk-VRPPI6GU.js";
 export {
   ClaudeContextManager
 };
-//# sourceMappingURL=ClaudeContextManager-RRGREEZQ.js.map
+//# sourceMappingURL=ClaudeContextManager-ZH6LEA5I.js.map

package/dist/{ClaudeService-LEPW6QAC.js → ClaudeService-YR66WXZN.js}

@@ -1,13 +1,13 @@
 #!/usr/bin/env node
 import {
   ClaudeService
-} from "./chunk-XCP2WDYA.js";
-import "./chunk-7RCUWU3I.js";
+} from "./chunk-T4NESGYB.js";
+import "./chunk-MRPIDNZU.js";
 import "./chunk-DDHWZNGL.js";
-import "./chunk-WGUGB54H.js";
+import "./chunk-F5NKWLMQ.js";
 import "./chunk-FTYWGQFM.js";
 import "./chunk-VRPPI6GU.js";
 export {
   ClaudeService
 };
-//# sourceMappingURL=ClaudeService-LEPW6QAC.js.map
+//# sourceMappingURL=ClaudeService-YR66WXZN.js.map

package/dist/{IssueTrackerFactory-KE2BDCLC.js → IssueTrackerFactory-O2ZBA666.js}

@@ -1,15 +1,15 @@
 #!/usr/bin/env node
 import {
   IssueTrackerFactory
-} from "./chunk-NUUFP53X.js";
+} from "./chunk-GPBX2BY2.js";
 import "./chunk-DMSL5BAP.js";
 import "./chunk-D4Q7T5KD.js";
 import "./chunk-KV4NU3RP.js";
 import "./chunk-NPVA65KS.js";
-import "./chunk-WGUGB54H.js";
+import "./chunk-F5NKWLMQ.js";
 import "./chunk-FTYWGQFM.js";
 import "./chunk-VRPPI6GU.js";
 export {
   IssueTrackerFactory
 };
-//# sourceMappingURL=IssueTrackerFactory-KE2BDCLC.js.map
+//# sourceMappingURL=IssueTrackerFactory-O2ZBA666.js.map

package/dist/{LoomLauncher-GKQMR5E6.js → LoomLauncher-V54ENBEF.js}

@@ -4,9 +4,9 @@ import {
 } from "./chunk-CE676WCN.js";
 import {
   ClaudeContextManager
-} from "./chunk-JDN4SPV3.js";
-import "./chunk-XCP2WDYA.js";
-import "./chunk-7RCUWU3I.js";
+} from "./chunk-WYDLOQYO.js";
+import "./chunk-T4NESGYB.js";
+import "./chunk-MRPIDNZU.js";
 import {
   getExecutablePath
 } from "./chunk-GYCR2LOU.js";
@@ -15,7 +15,7 @@ import {
   hexToRgb
 } from "./chunk-OIVFHJOA.js";
 import "./chunk-DDHWZNGL.js";
-import "./chunk-WGUGB54H.js";
+import "./chunk-F5NKWLMQ.js";
 import {
   getLogger
 } from "./chunk-FTYWGQFM.js";
@@ -255,4 +255,4 @@ var LoomLauncher = class {
 export {
   LoomLauncher
 };
-//# sourceMappingURL=LoomLauncher-GKQMR5E6.js.map
+//# sourceMappingURL=LoomLauncher-V54ENBEF.js.map

package/dist/{MetadataManager-V4LSJ2PB.js → MetadataManager-HHE6LQF2.js}

@@ -1,10 +1,10 @@
 #!/usr/bin/env node
 import {
   MetadataManager
-} from "./chunk-4JZEQBWV.js";
+} from "./chunk-XIVLGWUX.js";
 import "./chunk-FTYWGQFM.js";
 import "./chunk-VRPPI6GU.js";
 export {
   MetadataManager
 };
-//# sourceMappingURL=MetadataManager-V4LSJ2PB.js.map
+//# sourceMappingURL=MetadataManager-HHE6LQF2.js.map

package/dist/{PromptTemplateManager-I75WKXM4.js → PromptTemplateManager-4RFELNYY.js}

@@ -2,10 +2,10 @@
 import {
   PromptTemplateManager,
   buildReviewTemplateVariables
-} from "./chunk-7RCUWU3I.js";
+} from "./chunk-MRPIDNZU.js";
 import "./chunk-VRPPI6GU.js";
 export {
   PromptTemplateManager,
   buildReviewTemplateVariables
 };
-//# sourceMappingURL=PromptTemplateManager-I75WKXM4.js.map
+//# sourceMappingURL=PromptTemplateManager-4RFELNYY.js.map

package/dist/README.md

@@ -97,7 +97,7 @@ Each loom is a fully isolated container for your work:
 
 *   **Git Worktree:** A separate filesystem at ~/project-looms/issue-25/. No stashing, no branch switching overhead.
     
-*   **Database Branch:** (Neon and Supabase support) Schema changes in this loom are isolated—they won't break your main environment or your other active looms.
+*   **Database Branch:** (Neon support) Schema changes in this loom are isolated—they won't break your main environment or your other active looms.
 
 *   **Environment Variables:** Each loom has its own environment files (`.env`, `.env.local`, `.env.development`, `.env.development.local`). Uses `development` by default, override with `DOTENV_FLOW_NODE_ENV`. See [Secret Storage Limitations](#multi-language-project-support) for frameworks with encrypted credentials.
 
@@ -153,7 +153,7 @@ Configuration
 
 ### 1. Interactive Setup (Recommended)
 
-The easiest way to configure iloom is the interactive wizard. It guides you through setting up your environment (GitHub/Linear, Neon/Supabase, IDE).
+The easiest way to configure iloom is the interactive wizard. It guides you through setting up your environment (GitHub/Linear, Neon, IDE).
 
 You can even use natural language to jump-start the process:
 
@@ -206,21 +206,6 @@ This example shows how to configure a project-wide default (e.g., GitHub remote)
 }
 ```
 
-Or, if using Supabase (requires a paid plan):
-
-```json
-{
-  "databaseProviders": {
-    "supabase": {
-      "projectRef": "abcdefghijklmnop",
-      "parentBranch": "main"
-    }
-  }
-}
-```
-
-> Only one database provider can be active at a time. See [Database Branching](docs/iloom-commands.md#database-branching) for full details.
-
 **.iloom/settings.local.json (Gitignored)**
 
 ```json
@@ -895,7 +880,7 @@ License & Name
     
 *   ❌ You cannot resell iloom itself as a product or SaaS.
     
-*   Converts to Apache 2.0 on 2030-03-10.
+*   Converts to Apache 2.0 on 2030-03-16.
     
 
 See [LICENSE](https://raw.githubusercontent.com/iloom-ai/iloom-cli/main/LICENSE) for complete terms.

package/dist/{SettingsManager-KQU7OX7G.js → SettingsManager-SLSYEYDZ.js}

@@ -14,14 +14,14 @@ import {
   SettingsManager,
   SpinAgentSettingsSchema,
   SummarySettingsSchema,
-  SupabaseSettingsSchema,
+  VALID_CLAUDE_MODELS,
   WorkflowPermissionSchema,
   WorkflowPermissionSchemaNoDefaults,
   WorkflowsSettingsSchema,
   WorkflowsSettingsSchemaNoDefaults,
   mergeModeValues,
   redactSensitiveFields
-} from "./chunk-WGUGB54H.js";
+} from "./chunk-F5NKWLMQ.js";
 import "./chunk-VRPPI6GU.js";
 export {
   AgentSettingsSchema,
@@ -38,7 +38,7 @@ export {
   SettingsManager,
   SpinAgentSettingsSchema,
   SummarySettingsSchema,
-  SupabaseSettingsSchema,
+  VALID_CLAUDE_MODELS,
   WorkflowPermissionSchema,
   WorkflowPermissionSchemaNoDefaults,
   WorkflowsSettingsSchema,
@@ -46,4 +46,4 @@ export {
   mergeModeValues,
   redactSensitiveFields
 };
-//# sourceMappingURL=SettingsManager-KQU7OX7G.js.map
+//# sourceMappingURL=SettingsManager-SLSYEYDZ.js.map

package/dist/agents/iloom-artifact-reviewer.md

@@ -16,6 +16,7 @@ You are a skeptical senior staff engineer reviewing work produced by AI agents b
 - **Concise output**: Return structured review results suitable for the orchestrator.
 - **Autonomous decisions**: If improvements are needed, provide actionable feedback in the response.
 - **No state to done**: Do NOT call `recap.set_loom_state` with state `done` — only the swarm worker may do that after committing.
+- **Efficiency**: Maximize parallel tool calls. When verifying multiple file references or claims, batch reads/greps into a single message. Minimize text narration between tool calls.
 {{/if}}
 
 {{#if HAS_ARTIFACT_REVIEW_GEMINI}}

package/dist/agents/iloom-code-reviewer.md

@@ -55,6 +55,13 @@ Codex review configured with model: {{REVIEW_CODEX_MODEL}}
 {{#if HAS_REVIEW_CLAUDE}}
 {{#unless HAS_REVIEW_GEMINI}}
 {{#unless HAS_REVIEW_CODEX}}
+### Pre-provided Diff Check
+
+**FIRST**: Check whether the invocation prompt contains a `## Pre-gathered Diff` section.
+
+- **If yes**: Use that diff directly as your working diff. Skip all of Step 0 (diff gathering) and Step 1 (context gathering from git). The diff and CLAUDE.md content have already been provided. Proceed directly to the review execution (Gemini/Codex tool calls or Claude agent instructions).
+- **If no**: Proceed with normal flow below.
+
 ## Claude-Only Configuration Detected
 
 **IMPORTANT: You are a SUBAGENT. You were spawned by an orchestrator (the main Claude session). The orchestrator has the Task tool and can spawn sub-agents - you cannot.**
@@ -265,6 +272,13 @@ Summary: X critical, Y warnings, Z suggestions
 {{#if HAS_REVIEW_GEMINI}}
 ## Review Process
 
+### Pre-provided Diff Check
+
+**FIRST**: Check whether the invocation prompt contains a `## Pre-gathered Diff` section.
+
+- **If yes**: Use that diff directly as your working diff. Skip all of Step 0 (diff gathering) and Step 1 (context gathering from git). The diff and CLAUDE.md content have already been provided. Proceed directly to the review execution (Gemini/Codex tool calls or Claude agent instructions).
+- **If no**: Proceed with normal Step 0 diff gathering below.
+
 ### Step 0 - Determine What to Review
 
 Before gathering code for review, determine what changes to review:
@@ -523,6 +537,13 @@ If ANY critical issues (95-100 confidence) are found from Gemini review:
 {{#if HAS_REVIEW_CODEX}}
 ## Review Process
 
+### Pre-provided Diff Check
+
+**FIRST**: Check whether the invocation prompt contains a `## Pre-gathered Diff` section.
+
+- **If yes**: Use that diff directly as your working diff. Skip all of Step 0 (diff gathering) and Step 1 (context gathering from git). The diff and CLAUDE.md content have already been provided. Proceed directly to the review execution (Gemini/Codex tool calls or Claude agent instructions).
+- **If no**: Proceed with normal Step 0 diff gathering below.
+
 ### Step 0 - Determine What to Review
 
 Before gathering code for review, determine what changes to review:

package/dist/agents/iloom-issue-analyze-and-plan.md

@@ -15,6 +15,8 @@ model: opus
 - **No human interaction**: Do NOT pause for user input. Make your best judgment and proceed.
 - **Concise output**: Return a structured result suitable for the orchestrator, including the Execution Plan.
 - **No state to done**: Do NOT call `recap.set_loom_state` with state `done` — only the swarm worker may do that after committing.
+- **Efficiency**: Maximize parallel tool calls. When reading multiple files or searching for patterns, batch them into a single message with multiple tool calls. Minimize text narration between tool calls — let your tool calls speak for themselves.
+- **Single comment**: Post ONE comment at the end with your complete analysis and plan (Section 1 + Section 2). Do NOT create progress-tracking comments or update comments incrementally — the orchestrator tracks progress.
 {{else}}
 {{#if DRAFT_PR_MODE}}
 ## Comment Routing: Draft PR Mode
@@ -293,6 +295,27 @@ Available Tools:
   Parameters: { commentId: string, number: string, body: "updated markdown content" }
   Returns: { id: string, url: string, updated_at: string }
 
+{{#if SWARM_MODE}}
+Workflow Comment Strategy (Swarm Mode):
+1. Perform all research, analysis, and planning FIRST without posting comments.
+2. When your combined analysis and plan is complete, create ONE comment with the full output (Section 1 + Section 2).
+3. Store the returned comment ID and URL. Call `mcp__recap__add_artifact` to log it.
+4. Return the comment URL and Execution Plan to the calling process.
+
+Example Usage:
+```
+const comment = await mcp__issue_management__create_comment({
+  number: "<issue-number-from-invocation-prompt>",
+  body: "# Combined Analysis & Plan...\n\n[Full Section 1 + Section 2 content]",
+  type: "issue"
+})
+await mcp__recap__add_artifact({
+  type: "comment",
+  primaryUrl: comment.url,
+  description: "Combined analysis and plan comment"
+})
+```
+{{else}}
 Workflow Comment Strategy:
 1. When beginning work, create a NEW comment informing the user you are working on Analysis and Planning.
 2. Store the returned comment ID and URL. After creating the comment, call `mcp__recap__add_artifact` to log it with type='comment', primaryUrl=[comment URL], and a brief description (e.g., "Analysis and planning comment").
@@ -309,11 +332,7 @@ Workflow Comment Strategy:
 Example Usage:
 ```
 // Start
-{{#if SWARM_MODE}}const comment = await mcp__issue_management__create_comment({
-  number: "<issue-number-from-invocation-prompt>",
-  body: "# Combined Analysis and Planning\n\n- [ ] Perform lightweight analysis\n- [ ] Create implementation plan",
-  type: "issue"
-}){{else}}{{#if DRAFT_PR_MODE}}const comment = await mcp__issue_management__create_comment({
+{{#if DRAFT_PR_MODE}}const comment = await mcp__issue_management__create_comment({
   number: {{DRAFT_PR_NUMBER}}{{#unless DRAFT_PR_NUMBER}}/* PR NUMBER MISSING */{{/unless}},
   body: "# Combined Analysis and Planning\n\n- [ ] Perform lightweight analysis\n- [ ] Create implementation plan",
   type: "pr"
@@ -321,7 +340,7 @@ Example Usage:
   number: {{ISSUE_NUMBER}},
   body: "# Combined Analysis and Planning\n\n- [ ] Perform lightweight analysis\n- [ ] Create implementation plan",
   type: "issue"
-}){{/if}}{{/if}}
+}){{/if}}
 
 // Log the comment as an artifact
 await mcp__recap__add_artifact({
@@ -331,11 +350,7 @@ await mcp__recap__add_artifact({
 })
 
 // Update as you progress
-{{#if SWARM_MODE}}await mcp__issue_management__update_comment({
-  commentId: comment.id,
-  number: "<issue-number-from-invocation-prompt>",
-  body: "# Combined Analysis and Planning\n\n- [x] Perform lightweight analysis\n- [ ] Create implementation plan"
-}){{else}}{{#if DRAFT_PR_MODE}}await mcp__issue_management__update_comment({
+{{#if DRAFT_PR_MODE}}await mcp__issue_management__update_comment({
   commentId: comment.id,
   number: {{DRAFT_PR_NUMBER}}{{#unless DRAFT_PR_NUMBER}}/* PR NUMBER MISSING */{{/unless}},
   body: "# Combined Analysis and Planning\n\n- [x] Perform lightweight analysis\n- [ ] Create implementation plan"
@@ -343,8 +358,9 @@ await mcp__recap__add_artifact({
   commentId: comment.id,
   number: {{ISSUE_NUMBER}},
   body: "# Combined Analysis and Planning\n\n- [x] Perform lightweight analysis\n- [ ] Create implementation plan"
-}){{/if}}{{/if}}
+}){{/if}}
 ```
+{{/if}}
 </comment_tool_info>
 
 ### Step 4: Document Combined Results
@@ -578,10 +594,12 @@ If structure is >5 lines:
 
 **Questions/Risks filter**: Only HIGH/CRITICAL. Omit section if none exist.
 
+{{#unless SWARM_MODE}}
 ## HOW TO UPDATE THE USER OF YOUR PROGRESS
 * AS SOON AS YOU CAN, once you have formulated an initial plan/todo list for your task, you should create a comment as described in the <comment_tool_info> section above.
 * AFTER YOU COMPLETE EACH ITEM ON YOUR TODO LIST - update the same comment with your progress as described in the <comment_tool_info> section above.
 * When the whole task is complete, update the SAME comment with the results of your work including Section 1 and Section 2 above. DO NOT include comments like "see previous comment for details" - this represents a failure of your task. NEVER ATTEMPT CONCURRENT UPDATES OF THE COMMENT. DATA WILL BE LOST.
+{{/unless}}
 
 ## Analysis Guidelines
 

package/dist/agents/iloom-issue-analyzer.md

@@ -16,6 +16,8 @@ model: opus
 - **Concise output**: Return a structured analysis result suitable for the orchestrator.
 - **Full research still required**: Perform the same comprehensive research as in non-swarm mode. Thoroughness is critical even in autonomous execution.
 - **No state to done**: Do NOT call `recap.set_loom_state` with state `done` — only the swarm worker may do that after committing.
+- **Efficiency**: Maximize parallel tool calls. When reading multiple files, batch them into a single message with multiple tool calls. Minimize text narration between tool calls — let your tool calls speak for themselves.
+- **Single comment**: Post ONE comment at the end with your complete analysis (Section 1 + Section 2). Do NOT create progress-tracking comments or update comments incrementally — the orchestrator tracks progress.
 {{else}}
 {{#if DRAFT_PR_MODE}}
 ## Comment Routing: Draft PR Mode
@@ -371,6 +373,13 @@ Available Tools:
   Parameters: { commentId: string, number: string, body: "updated markdown content" }
   Returns: { id: string, url: string, updated_at: string }
 
+{{#if SWARM_MODE}}
+Workflow Comment Strategy (Swarm Mode):
+1. Perform all research and analysis FIRST without posting comments.
+2. When your analysis is complete, create ONE comment with the full analysis (Section 1 + Section 2).
+3. Store the returned comment ID and URL. Call `mcp__recap__add_artifact` to log it.
+4. Return the comment URL to the calling process.
+{{else}}
 Workflow Comment Strategy:
 1. When beginning analysis/research, create a NEW comment informing the user you are working on analyzing the issue.
 2. Store the returned comment ID and URL. After creating the comment, call `mcp__recap__add_artifact` to log it with type='comment', primaryUrl=[comment URL], and a brief description (e.g., "Analysis progress comment").
@@ -383,14 +392,22 @@ Workflow Comment Strategy:
    * Include relevant context (current step, progress, blockers) and a **very aggressive** estimated time to completion of this step and the whole task in each update after the comment's todo list
 5. When you have finished your task, update the same comment as before - MAKE SURE YOU DO NOT ERASE THE "details" section, then let the calling process know the full web URL of the issue comment, including the comment ID. NEVER ATTEMPT CONCURRENT UPDATES OF THE COMMENT. DATA WILL BE LOST.
 6. CONSTRAINT: After you create the initial comment, you may not create another comment. You must always update the initial comment instead.
+{{/if}}
 
 Example Usage:
 ```
 // Start
 {{#if SWARM_MODE}}const comment = await mcp__issue_management__create_comment({
   number: "<issue-number-from-invocation-prompt>",
-  body: "# Analysis Phase\n\n- [ ] Fetch issue details\n- [ ] Analyze requirements",
+  body: "# Analysis\n\n[full Section 1 + Section 2 content]",
   type: "issue"
+})
+
+// Log the comment as an artifact
+await mcp__recap__add_artifact({
+  type: "comment",
+  primaryUrl: comment.url,
+  description: "Analysis comment"
 }){{else}}{{#if DRAFT_PR_MODE}}const comment = await mcp__issue_management__create_comment({
   number: {{DRAFT_PR_NUMBER}}{{#unless DRAFT_PR_NUMBER}}/* PR NUMBER MISSING */{{/unless}},
   body: "# Analysis Phase\n\n- [ ] Fetch issue details\n- [ ] Analyze requirements",
@@ -399,7 +416,7 @@ Example Usage:
   number: {{ISSUE_NUMBER}},
   body: "# Analysis Phase\n\n- [ ] Fetch issue details\n- [ ] Analyze requirements",
   type: "issue"
-}){{/if}}{{/if}}
+}){{/if}}
 
 // Log the comment as an artifact
 await mcp__recap__add_artifact({
@@ -409,11 +426,7 @@ await mcp__recap__add_artifact({
 })
 
 // Update as you progress
-{{#if SWARM_MODE}}await mcp__issue_management__update_comment({
-  commentId: comment.id,
-  number: "<issue-number-from-invocation-prompt>",
-  body: "# Analysis Phase\n\n- [x] Fetch issue details\n- [ ] Analyze requirements"
-}){{else}}{{#if DRAFT_PR_MODE}}await mcp__issue_management__update_comment({
+{{#if DRAFT_PR_MODE}}await mcp__issue_management__update_comment({
   commentId: comment.id,
   number: {{DRAFT_PR_NUMBER}}{{#unless DRAFT_PR_NUMBER}}/* PR NUMBER MISSING */{{/unless}},
   body: "# Analysis Phase\n\n- [x] Fetch issue details\n- [ ] Analyze requirements"
@@ -595,11 +608,22 @@ Brief bullet list only:
 
 ## Comment Submission
 
+{{#if SWARM_MODE}}
+## HOW TO SUBMIT YOUR ANALYSIS
+* Complete ALL research and analysis before posting any comment.
+* When finished, create ONE comment with Section 1 + Section 2 as described in the <comment_tool_info> section above.
+* Return the comment URL to the calling process.
+{{else}}
 ## HOW TO UPDATE THE USER OF YOUR PROGRESS
 * AS SOON AS YOU CAN, once you have formulated an initial plan/todo list for your task, you should create a comment as described in the <comment_tool_info> section above.
 * AFTER YOU COMPLETE EACH ITEM ON YOUR TODO LIST - update the same comment with your progress as described in the <comment_tool_info> section above.
 * When the whole task is complete, update the SAME comment with the results of your work including Section 1 and Section 2 above. DO NOT include comments like "see previous comment for details" - this represents a failure of your task. NEVER ATTEMPT CONCURRENT UPDATES OF THE COMMENT. DATA WILL BE LOST.
+{{/if}}
 
+{{#if SWARM_MODE}}
+## Quality Check
+Before submitting: verify all file:line references are accurate, Section 1 is scannable in <3 minutes, Section 2 has complete technical details, and no solutions are proposed.
+{{else}}
 ## Quality Assurance Checklist
 
 Before submitting your analysis, verify:
@@ -624,6 +648,7 @@ Before submitting your analysis, verify:
 - [ ] You have not detailed the solution - only identified relevant parts of the code, and potential risks, edge cases to be aware of
 - [ ] **FOR CROSS-CUTTING CHANGES**: Architectural Flow Analysis section is complete with call chain map, ALL affected interfaces listed, and implementation complexity noted
 - [ ] **FOR CROSS-COMPONENT VALUES**: Every specific value (scores, thresholds, enums) referenced from other components has a file:line citation. Any unverified values are described by intent, not by fabricated numbers, with a corresponding `recap.add_entry({ type: 'assumption' })` call.
+{{/if}}
 
 ## Behavioral Constraints
 

package/dist/agents/iloom-issue-complexity-evaluator.md

@@ -16,6 +16,9 @@ model: haiku
 - **Concise output**: Return the classification result in the standard deterministic format.
 - **Still call `recap.set_complexity`**: This is required even in swarm mode for state tracking.
 - **No state to done**: Do NOT call `recap.set_loom_state` with state `done` — only the swarm worker may do that after committing.
+- **Efficiency**: Maximize parallel tool calls. When scanning files for scope estimates, batch searches into a single message. Minimize text narration between tool calls.
+- **Single comment**: Post ONE comment at the end with your classification result. Do NOT create progress-tracking comments or update incrementally — the orchestrator tracks progress.
+- **No COMPLEX classification**: In swarm mode, child issues are pre-planned and well-scoped. Classify as TRIVIAL or SIMPLE only — never COMPLEX. If the issue would normally qualify as COMPLEX, classify it as SIMPLE instead. The combined analyze-and-plan agent handles all analysis and planning in one phase.
 {{else}}
 {{#if DRAFT_PR_MODE}}
 ## Comment Routing: Draft PR Mode
@@ -268,6 +271,28 @@ Available Tools:
   Parameters: { commentId: string, number: string, body: "updated markdown content" }
   Returns: { id: string, url: string, updated_at: string }
 
+{{#if SWARM_MODE}}
+Workflow Comment Strategy (Swarm Mode):
+1. Perform the complexity scan FIRST without posting comments.
+2. When classification is complete, create ONE comment with the final assessment in the deterministic format.
+3. Store the returned comment ID and URL. Call `mcp__recap__add_artifact` to log it.
+4. Call `mcp__recap__set_complexity` with your classification.
+5. Return the result to the calling process.
+
+Example Usage:
+```
+const comment = await mcp__issue_management__create_comment({
+  number: "<issue-number-from-invocation-prompt>",
+  body: "## Complexity Assessment\n\n**Classification**: SIMPLE\n\n**Metrics**:\n- Estimated files affected: 3\n...\n\n**Reasoning**: ...",
+  type: "issue"
+})
+await mcp__recap__add_artifact({
+  type: "comment",
+  primaryUrl: comment.url,
+  description: "Complexity evaluation comment"
+})
+```
+{{else}}
 Workflow Comment Strategy:
 1. When beginning, create a NEW comment informing the user you are working on the task.
 2. Store the returned comment ID and URL. After creating the comment, call `mcp__recap__add_artifact` to log it with type='comment', primaryUrl=[comment URL], and a brief description (e.g., "Complexity evaluation comment").
@@ -285,11 +310,7 @@ Workflow Comment Strategy:
 Example Usage:
 ```
 // Start
-{{#if SWARM_MODE}}const comment = await mcp__issue_management__create_comment({
-  number: "<issue-number-from-invocation-prompt>",
-  body: "# Analysis Phase\n\n- [ ] Fetch issue details\n- [ ] Analyze requirements",
-  type: "issue"
-}){{else}}{{#if DRAFT_PR_MODE}}const comment = await mcp__issue_management__create_comment({
+{{#if DRAFT_PR_MODE}}const comment = await mcp__issue_management__create_comment({
   number: {{DRAFT_PR_NUMBER}}{{#unless DRAFT_PR_NUMBER}}/* PR NUMBER MISSING */{{/unless}},
   body: "# Analysis Phase\n\n- [ ] Fetch issue details\n- [ ] Analyze requirements",
   type: "pr"
@@ -297,7 +318,7 @@ Example Usage:
   number: {{ISSUE_NUMBER}},
   body: "# Analysis Phase\n\n- [ ] Fetch issue details\n- [ ] Analyze requirements",
   type: "issue"
-}){{/if}}{{/if}}
+}){{/if}}
 
 // Log the comment as an artifact
 await mcp__recap__add_artifact({
@@ -307,11 +328,7 @@ await mcp__recap__add_artifact({
 })
 
 // Update as you progress
-{{#if SWARM_MODE}}await mcp__issue_management__update_comment({
-  commentId: comment.id,
-  number: "<issue-number-from-invocation-prompt>",
-  body: "# Analysis Phase\n\n- [x] Fetch issue details\n- [ ] Analyze requirements"
-}){{else}}{{#if DRAFT_PR_MODE}}await mcp__issue_management__update_comment({
+{{#if DRAFT_PR_MODE}}await mcp__issue_management__update_comment({
   commentId: comment.id,
   number: {{DRAFT_PR_NUMBER}}{{#unless DRAFT_PR_NUMBER}}/* PR NUMBER MISSING */{{/unless}},
   body: "# Analysis Phase\n\n- [x] Fetch issue details\n- [ ] Analyze requirements"
@@ -319,8 +336,9 @@ await mcp__recap__add_artifact({
   commentId: comment.id,
   number: {{ISSUE_NUMBER}},
   body: "# Analysis Phase\n\n- [x] Fetch issue details\n- [ ] Analyze requirements"
-}){{/if}}{{/if}}
+}){{/if}}
 ```
+{{/if}}
 </comment_tool_info>
 
 ## Documentation Standards
@@ -352,12 +370,14 @@ await mcp__recap__add_artifact({
 - Keep reasoning concise (1-2 sentences maximum)
 - This is the ONLY content your comment should contain (after your todo list is complete)
 
+{{#unless SWARM_MODE}}
 ## Comment Submission
 
 ### HOW TO UPDATE THE USER OF YOUR PROGRESS
 * AS SOON AS YOU CAN, once you have formulated an initial plan/todo list for your task, you should create a comment as described in the <comment_tool_info> section above.
 * AFTER YOU COMPLETE EACH ITEM ON YOUR TODO LIST - update the same comment with your progress as described in the <comment_tool_info> section above.
 * When the whole task is complete, update the SAME comment with the results of your work in the exact format specified above. DO NOT include comments like "see previous comment for details" - this represents a failure of your task. NEVER ATTEMPT CONCURRENT UPDATES OF THE COMMENT. DATA WILL BE LOST.
+{{/unless}}
 
 ## Behavioral Constraints