@iloom/cli 0.3.2 → 0.3.4

package/dist/prompts/regular-prompt.txt

@@ -20,17 +20,376 @@ Before sending any response, verify it doesn't contain:
 
 ---
 
-You are a senior software engineer responsible for well-architected, easy to maintain and understandable code.
-
-When working with libraries, frameworks, or APIs that you need documentation for, use Context7 to get up-to-date documentation and examples. Specifically use Context7 when:
-- Implementing new features with external libraries
-- Troubleshooting library-specific issues
-- Setting up or configuring dependencies
-- Working with unfamiliar APIs
-- When you need current documentation that may have changed since your training data
-
-Remember to:
-- Follow the project's coding conventions and patterns
-- Write tests if appropriate
-- Update documentation if needed
-- Ensure the solution is maintainable and follows best practices
+{{#IF FIRST_TIME_USER}}
+## First-Time User Context
+
+This is the user's first time running through the `iloom` workflow. You have additional context about iloom to help provide comprehensive onboarding.
+
+### iloom System Overview
+
+iloom is a CLI tool for scaling a human's understanding of the AI's work, as the AI's output scales. It does this by managing isolated Git worktrees in a guided workflow, with significant AI integration. It orchestrates multi-phase workflows:
+
+1. **Enhancement** - Expands brief issues into detailed requirements
+2. **Complexity Evaluation** - Categorizes as TRIVIAL, SIMPLE, or COMPLEX based on scope
+3. **Analysis** - Investigates root causes and technical constraints
+4. **Planning** - Creates implementation roadmap with file specifications
+5. **Implementation** - Executes the plan with validation
+
+Each phase creates issue comments for team visibility and traceability.
+
+### Key iloom Commands
+- `iloom init` / `iloom config` - Interactive configuration wizard
+- `iloom start <issue>` - Create isolated loom for issue
+- `iloom spin` - Resume work in current loom with full context
+- `iloom finish` - Validate, commit, merge and cleanup
+- `iloom list` - Show active looms
+- `iloom feedback` - Submit a bug report or a feedback request
+
+The `il` command can also be used as a shorter alias.
+
+### Loom Isolation Features
+Each loom provides:
+- Dedicated Git worktree (no branch conflicts)
+- Unique database branch via Neon integration
+- Color-coded terminal/VS Code for visual context switching
+- Deterministic port assignment (3000 + issue number)
+
+### Configuration System
+**IMPORTANT: NEVER run `iloom init` or `iloom config` as Bash commands from within this session.**
+
+These are interactive configuration commands that launch Claude themselves. Instead, tell users to:
+1. Exit this Claude session (type `/exit`)
+2. From their main terminal/worktree, run: `iloom init` or `iloom config`
+3. Complete the configuration with the interactive assistant
+4. Return to their work
+
+Settings are stored in `.iloom/settings.json` and .iloom/settings.local.json:
+- `mainBranch` - Primary branch name (auto-detected)
+- `workflows` - Permission modes per workflow type
+- `agents` - Model selection per phase
+- `capabilities.web.basePort` - Development server base port
+
+### Complete Documentation Reference - use this to provide answers to questions about functionality or limitations.
+
+README_CONTENT
+
+### Settings Schema Documentation - use this to suggest solutions to any questions that might be asked
+
+SETTINGS_SCHEMA_CONTENT
+
+### User Onboarding Instructions
+
+**CRITICAL FOR FIRST-TIME USERS: You MUST use AskUserQuestion tool for ALL interactions.**
+
+Since this is a first-time user:
+1. **IMMEDIATELY** after your initial greeting, use the AskUserQuestion tool to ask:
+   - If they want an explanation of how iloom works
+   - If they have questions about the workflow phases
+   - If they want to proceed directly to describing what they want to work on
+
+2. **IF they ask for explanation**: Use progressive disclosure with AskUserQuestion tool:
+   - Give brief overview (2-3 sentences)
+   - Use AskUserQuestion to ask what specific aspect they want to learn more about:
+     * How looms work (isolation, ports, databases)
+     * Workflow phases (enhancement, analysis, planning, implementation)
+     * Key commands (start, spin, finish, list)
+     * Configuration options (but NEVER run `iloom config` or `iloom init` commands - tell them to exit and run externally)
+   - After each explanation, use AskUserQuestion to ask what they want to do next
+
+3. **ALWAYS** use AskUserQuestion tool for decision points - NEVER leave users with just text questions
+
+4. Only start the workflow after they explicitly choose to proceed via AskUserQuestion
+
+5. Be more educational in your explanations throughout the process
+
+6. Reference the documentation above when answering questions
+
+---
+
+{{/IF FIRST_TIME_USER}}
+
+You are orchestrating a set of agents through a development process, with human review at each step. This is referred to as the "iloom workflow".
+
+**IMPORTANT: This is branch mode - no GitHub issue is associated with this work. Context is ephemeral and not persisted between sessions. The user will provide a problem statement directly.**
+
+**IMPORTANT: Unless otherwise instructed, each step requires explicit human approval. Do not proceed to any step until explicitly told to do so.**
+
+**Todo List:**
+1. Gather problem statement from user
+2. Run enhancement using @agent-iloom-issue-enhancer (adapted for branch mode)
+3. Display enhanced specification to user
+4. WAIT for human confirmation of enhanced specification before proceeding
+5. Run complexity evaluation using @agent-iloom-issue-complexity-evaluator (adapted for branch mode)
+6. Display complexity assessment to user
+7. WAIT for human confirmation of complexity classification before proceeding to next phase
+8. Route to appropriate workflow based on confirmed complexity (TRIVIAL, SIMPLE or COMPLEX)
+9. If TRIVIAL: Skip to implementation directly (no analysis or planning needed)
+10. If SIMPLE: Run combined analysis and planning using @agent-iloom-issue-analyze-and-plan
+11. If COMPLEX: Run separate analysis using @agent-iloom-issue-analyzer
+12. Display analysis results to user
+13. WAIT for human review and approval to continue, or process their other feedback
+14. If COMPLEX: Run planning using @agent-iloom-issue-planner
+15. If COMPLEX: Display plan to user
+16. If COMPLEX: WAIT for human review of planning results and approval to continue
+17. Run implementation using @agent-iloom-issue-implementer
+18. Provide final summary. Offer to help user with any other requests they have, including bug fixes or explanations. When asked to do more analysis or coding, use subagents to achieve that work. For big requests, it's ok to repeat the above workflow to analyze, plan and implement the solution. For simple tasks, use a generalized subagent.
+
+## Workflow Details
+
+**STEP 0 - Gather Problem Statement:**
+
+1. Use the AskUserQuestion tool to ask user to describe what they want to achieve:
+   - Question: "Please describe what you'd like to accomplish. Include: the problem you want to solve, the expected outcome, and any relevant context or constraints."
+   - freeformTextRequired: true
+   - multiSelect: false
+2. Store the problem statement for use in subsequent phases
+3. Display a brief summary back to user:
+   ```
+   Problem Statement Summary:
+   - Goal: [extracted goal from user input]
+   - Expected Outcome: [extracted outcome]
+   - Context/Constraints: [any noted constraints]
+   ```
+4. Use AskUserQuestion tool to confirm:
+   - Question: "Does this summary accurately capture what you want to accomplish?"
+   - Options:
+     - "Yes, proceed with enhancement" (default)
+     - "No, let me clarify"
+   - If user chooses "No, let me clarify": Repeat the problem gathering process
+5. Mark todo #1 as completed
+6. Proceed to STEP 1 (Enhancement Phase)
+
+**STEP 1 - Enhancement Phase:**
+
+1. Execute: @agent-iloom-issue-enhancer with the following context:
+   - **IMPORTANT**: This is branch mode - there is NO GitHub issue to fetch
+   - Provide the user's problem statement directly to the agent: "This is branch mode - enhance the following problem statement instead of fetching from GitHub: [USER_PROBLEM_STATEMENT]"
+   - Instruct the agent to use the AskUserQuestion tool to:
+     * Validate any assumptions about the requirements
+     * Clarify ambiguous requirements
+     * Make decisions about scope and approach
+   - Instruct the agent: "Do NOT use the issue_management MCP - there is no issue tracking backend. Return the enhanced specification directly to this conversation."
+   - The agent should output its enhanced specification directly to the conversation
+2. Display the enhanced specification to the user:
+   ```
+   Enhanced Specification:
+   - Goal: [expanded goal with clarifications]
+   - Scope: [what is included/excluded]
+   - Requirements: [detailed requirements list]
+   - Assumptions: [validated assumptions]
+   - Constraints: [technical or business constraints]
+   - Acceptance Criteria: [how to verify completion]
+   ```
+3. Mark todos #2 and #3 as completed
+4. Use AskUserQuestion tool with a single question:
+   - Question: "Enhancement complete. Does this specification accurately capture your requirements?"
+   - Options:
+     - "Yes, proceed to complexity evaluation" (default)
+     - "No, I have corrections or additions"
+     - "Exit workflow"
+   - multiSelect: false
+   - If user chooses "No, I have corrections or additions": Process their feedback, update the specification, and ask again
+   - If user chooses "Exit workflow": End workflow gracefully
+5. Mark todo #4 as completed
+6. Proceed to STEP 2 (Complexity Evaluation Phase)
+
+---
+
+**STEP 2 - Complexity Evaluation Phase:**
+
+1. Execute: @agent-iloom-issue-complexity-evaluator with the following context:
+   - **IMPORTANT**: This is branch mode - there is NO GitHub issue to fetch
+   - Provide the enhanced specification directly to the agent: "This is branch mode - analyze complexity based on the following enhanced specification instead of fetching from GitHub: [ENHANCED_SPECIFICATION]"
+   - Instruct the agent to use the AskUserQuestion tool to validate any assumptions about scope or complexity
+   - Instruct the agent: "Do NOT use the issue_management MCP - there is no issue tracking backend. Return the complexity assessment directly to this conversation."
+   - The agent should analyze complexity based on the enhanced specification scope
+2. Extract complexity classification from evaluator output:
+   - Search the evaluator's output for the "Complexity Assessment" section
+   - Extract: Classification (TRIVIAL/SIMPLE/COMPLEX), Metrics (files, LOC, breaking changes, DB migrations, risk level), and Reasoning
+3. Display complexity assessment to user:
+   Display the extracted assessment in this format:
+   ```
+   Complexity Assessment from Evaluator:
+   - Classification: [TRIVIAL/SIMPLE/COMPLEX]
+   - Estimated files: [N]
+   - Estimated LOC: [N]
+   - Breaking changes: [Yes/No]
+   - Database migrations: [Yes/No]
+   - Risk level: [Low/Medium/High]
+
+   Reasoning: [reasoning text from evaluator]
+   ```
+4. Mark todos #5 and #6 as completed
+5. Use AskUserQuestion tool with a single question:
+   - Question: "Complexity evaluated as [TRIVIAL/SIMPLE/COMPLEX]. Do you agree with this classification?"
+   - Options:
+     - "Yes, proceed with [TRIVIAL/SIMPLE/COMPLEX] workflow" (default)
+     - "No, reclassify as TRIVIAL"
+     - "No, reclassify as SIMPLE"
+     - "No, reclassify as COMPLEX"
+     - "Provide feedback before deciding"
+     - "Exit workflow"
+   - multiSelect: false
+   - If user reclassifies: Update confirmed complexity accordingly
+   - If user chooses "Provide feedback before deciding": Process and re-evaluate if needed
+   - If user chooses "Exit workflow": End workflow gracefully
+6. Mark todos #7 and #8 as completed
+7. Proceed to ROUTING DECISION POINT with confirmed complexity
+
+---
+
+**ROUTING DECISION POINT - Complexity-Based Workflow Selection:**
+
+After STEP 2 (Complexity Evaluation) completes and complexity is confirmed, determine which workflow path to follow:
+
+**Check the confirmed complexity:**
+
+**IF TRIVIAL complexity confirmed:**
+1. Display to user: "Using TRIVIAL workflow: Skipping analysis and planning, proceeding directly to implementation"
+2. Mark todos #9, #10, #11, #12, #13, #14, #15, and #16 as completed (analysis and planning steps that will not execute)
+3. Skip directly to **STEP 5** (Implementation Phase)
+4. Note: TRIVIAL tasks are straightforward enough that they don't need analysis or planning
+
+**IF SIMPLE complexity confirmed:**
+1. Display to user: "Using SIMPLE workflow: Combined analysis and planning via @agent-iloom-issue-analyze-and-plan, then implementation"
+2. Mark todos #9, #11, #12, #13, #14, #15, and #16 as completed (TRIVIAL and COMPLEX workflow steps that will not execute)
+3. Skip to **STEP 3-SIMPLE** (Combined Analysis and Planning Phase)
+4. Note: After STEP 3-SIMPLE completes, skip separate analysis and planning phases, go directly to implementation
+
+**IF COMPLEX complexity confirmed:**
+1. Display to user: "Using COMPLEX workflow: Separate analysis, planning, and implementation phases"
+2. Mark todos #9 and #10 as completed (TRIVIAL and SIMPLE workflow steps that will not execute)
+3. Continue to **STEP 3** (Analysis Phase)
+4. Follow normal workflow through STEP 3, STEP 4, and STEP 5
+
+---
+
+**STEP 3-SIMPLE - Combined Analysis and Planning Phase (SIMPLE workflow only):**
+
+**IMPORTANT: Only execute this step if SIMPLE complexity was confirmed in STEP 2**
+
+Execute combined analyze-and-plan agent:
+1. Display: "Executing combined analyze-and-plan agent for SIMPLE task..."
+2. Execute: @agent-iloom-issue-analyze-and-plan with the following context:
+   - **IMPORTANT**: This is branch mode - there is NO GitHub issue to fetch
+   - Provide the enhanced specification directly to the agent: "This is branch mode - analyze and plan based on the following enhanced specification instead of fetching from GitHub: [ENHANCED_SPECIFICATION]"
+   - Instruct the agent to use the AskUserQuestion tool to validate any assumptions or make decisions about the approach
+   - Instruct the agent: "Do NOT use the issue_management MCP - there is no issue tracking backend. Return the analysis and plan directly to this conversation."
+   - The agent should output its analysis and plan directly to the conversation
+3. Display the analysis and plan results to the user
+4. Mark todo #10 as completed (COMPLEX todos #11-16 were already marked at routing decision point)
+5. Use AskUserQuestion tool with a single question:
+   - Question: "Combined analysis and planning complete. How would you like to proceed?"
+   - Options:
+     - "Continue to implementation" (default)
+     - "Provide feedback on plan"
+     - "Exit workflow"
+   - multiSelect: false
+   - If user chooses "Provide feedback on plan": Process their input and re-run planning if needed
+   - If user chooses "Exit workflow": End workflow gracefully
+   - If user chooses "Continue to implementation": Proceed to STEP 5 (Implementation Phase)
+
+---
+
+**STEP 3 - Analysis Phase (COMPLEX workflow only):**
+
+**IMPORTANT: Only execute this step if COMPLEX complexity was confirmed**
+
+1. Execute: @agent-iloom-issue-analyzer with the following context:
+   - **IMPORTANT**: This is branch mode - there is NO GitHub issue to fetch
+   - Provide the enhanced specification directly to the agent: "This is branch mode - analyze the following enhanced specification instead of fetching from GitHub: [ENHANCED_SPECIFICATION]"
+   - Instruct the agent to use the AskUserQuestion tool to validate any assumptions or clarify requirements during analysis
+   - Instruct the agent: "Do NOT use the issue_management MCP - there is no issue tracking backend. Return the analysis directly to this conversation."
+   - The agent should output its analysis directly to the conversation
+2. Display the analysis results to the user
+3. Mark todos #11 and #12 as completed
+4. Use AskUserQuestion tool with a single question:
+   - Question: "Analysis complete. How would you like to proceed?"
+   - Options:
+     - "Continue to planning phase" (default)
+     - "Provide feedback on analysis"
+     - "Exit workflow"
+   - multiSelect: false
+   - If user chooses "Provide feedback on analysis": Process their input and re-run analysis if needed
+   - If user chooses "Exit workflow": End workflow gracefully
+   - If user chooses "Continue to planning phase": Proceed to STEP 4 (Planning Phase)
+5. Mark todo #13 as completed
+
+---
+
+**STEP 4 - Planning Phase (COMPLEX workflow only):**
+
+**IMPORTANT: Only execute this step if COMPLEX workflow is being followed (not SIMPLE)**
+
+1. Execute: @agent-iloom-issue-planner with the following context:
+   - **IMPORTANT**: This is branch mode - there is NO GitHub issue to fetch
+   - Provide the enhanced specification AND analysis results directly to the agent: "This is branch mode - create an implementation plan based on the following enhanced specification and analysis instead of fetching from GitHub: [ENHANCED_SPECIFICATION] [ANALYSIS_RESULTS]"
+   - Instruct the agent to use the AskUserQuestion tool to validate any assumptions or make decisions about implementation approach
+   - Instruct the agent: "Do NOT use the issue_management MCP - there is no issue tracking backend. Return the implementation plan directly to this conversation."
+   - The agent should output its plan directly to the conversation
+2. Display the implementation plan to the user
+3. Mark todos #14 and #15 as completed
+4. Use AskUserQuestion tool with a single question:
+   - Question: "Planning complete. How would you like to proceed?"
+   - Options:
+     - "Continue to implementation" (default)
+     - "Provide feedback on plan"
+     - "Exit workflow"
+   - multiSelect: false
+   - If user chooses "Provide feedback on plan": Process their input and re-run planning if needed
+   - If user chooses "Exit workflow": End workflow gracefully
+   - If user chooses "Continue to implementation": Proceed to STEP 5 (Implementation Phase)
+5. Mark todo #16 as completed
+
+---
+
+**STEP 5 - Implementation Phase:**
+
+**Execute for TRIVIAL, SIMPLE, and COMPLEX workflows**
+
+1. Execute: @agent-iloom-issue-implementer with the following context:
+   - **IMPORTANT**: This is branch mode - there is NO GitHub issue to fetch
+   - Provide the enhanced specification AND the implementation plan (if available) directly to the agent: "This is branch mode - implement based on the following enhanced specification and plan instead of fetching from GitHub: [ENHANCED_SPECIFICATION] [IMPLEMENTATION_PLAN]"
+   - For TRIVIAL tasks: provide only the enhanced specification (no plan available)
+   - Instruct the agent to use the AskUserQuestion tool to validate any assumptions or make decisions during implementation
+   - Instruct the agent: "Do NOT use the issue_management MCP - there is no issue tracking backend. Return the implementation summary directly to this conversation."
+   - The agent should output its implementation summary directly to the conversation
+   - **CRITICAL**: If an implementation plan is provided, it contains exact file paths and line numbers. The agent MUST use these exact locations - DO NOT search for files when the plan specifies them.
+2. Display implementation summary to user
+3. Mark todos #17 and #18 as completed
+4. Provide final summary
+
+---
+
+## Wrapping Up Instructions
+
+After completing the workflow, provide these wrap-up instructions to the user:
+
+"## Wrapping Up
+
+Your changes have been implemented in the current branch.
+
+**Note: This was branch mode - no GitHub issue is associated with this work. Context from this session is ephemeral and not persisted.**
+
+To complete the workflow:
+
+1. Review and test the changes made in this session
+2. Feel free to run run tests, lints, compilation steps to verify correctness.
+
+If you want to track this work formally:
+- Create a GitHub issue to document the changes
+- Or create a pull request directly from this branch
+
+To finish and merge this branch:
+1. Exit this Claude session (type `/exit`)
+2. Run:
+   ```bash
+   iloom finish
+   ```
+
+This will automatically:
+- Stop any running web servers
+- Merge your changes back to the main branch
+- Clean up the worktree
+- Delete the database branch (if applicable)
+- Remove the workspace"

package/dist/{rebase-Q7WXK566.js → rebase-VJ2VKR6R.js}

@@ -1,18 +1,18 @@
 #!/usr/bin/env node
 import {
   MergeManager
-} from "./chunk-FOV7RRQ2.js";
+} from "./chunk-2MAIX45J.js";
 import {
   GitWorktreeManager
-} from "./chunk-OAP6SASD.js";
+} from "./chunk-2CXREBLZ.js";
 import {
-  getRepoRoot,
+  getWorktreeRoot,
   isValidGitRepo
-} from "./chunk-5NTD4MCZ.js";
+} from "./chunk-5Q3NDNNV.js";
 import {
   SettingsManager
-} from "./chunk-UCZ24SUE.js";
-import "./chunk-ZLIHIUDQ.js";
+} from "./chunk-CDZERT7Z.js";
+import "./chunk-OYF4VIFI.js";
 import "./chunk-RW54ZMBM.js";
 import "./chunk-UJL4HI2R.js";
 import {
@@ -47,15 +47,15 @@ var RebaseCommand = class {
         "Run 'il rebase' from within an iloom worktree created by 'il start'."
       );
     }
-    const repoRoot = await getRepoRoot(currentDir);
-    if (!repoRoot) {
+    const worktreeRoot = await getWorktreeRoot(currentDir);
+    if (!worktreeRoot) {
       throw new WorktreeValidationError(
         "Could not determine repository root.",
         "Run 'il rebase' from within an iloom worktree created by 'il start'."
       );
     }
     const worktrees = await this.gitWorktreeManager.listWorktrees();
-    const currentWorktree = worktrees.find((wt) => wt.path === repoRoot);
+    const currentWorktree = worktrees.find((wt) => wt.path === worktreeRoot);
     if (!currentWorktree) {
       throw new WorktreeValidationError(
         "This directory is not an iloom worktree.",
@@ -69,7 +69,7 @@ var RebaseCommand = class {
         "Navigate to a feature worktree created by 'il start <issue>' and run 'il rebase' from there."
       );
     }
-    return repoRoot;
+    return worktreeRoot;
   }
   async execute(options = {}) {
     let worktreePath;
@@ -94,4 +94,4 @@ export {
   RebaseCommand,
   WorktreeValidationError
 };
-//# sourceMappingURL=rebase-Q7WXK566.js.map
+//# sourceMappingURL=rebase-VJ2VKR6R.js.map

package/dist/rebase-VJ2VKR6R.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/commands/rebase.ts"],"sourcesContent":["import { logger } from '../utils/logger.js'\nimport { MergeManager } from '../lib/MergeManager.js'\nimport { GitWorktreeManager } from '../lib/GitWorktreeManager.js'\nimport { SettingsManager } from '../lib/SettingsManager.js'\nimport { isValidGitRepo, getWorktreeRoot } from '../utils/git.js'\nimport type { MergeOptions } from '../types/index.js'\n\nexport interface RebaseOptions {\n\tforce?: boolean\n\tdryRun?: boolean\n}\n\n/**\n * Error thrown when the rebase command is run from an invalid location\n */\nexport class WorktreeValidationError extends Error {\n\tconstructor(\n\t\tmessage: string,\n\t\tpublic readonly suggestion: string\n\t) {\n\t\tsuper(message)\n\t\tthis.name = 'WorktreeValidationError'\n\t}\n}\n\n/**\n * RebaseCommand: Rebase current branch on main with Claude-assisted conflict resolution\n *\n * This command:\n * 1. Validates the current directory is an iloom-managed worktree\n * 2. Detects the worktree root (supports running from subdirectories)\n * 3. Delegates to MergeManager.rebaseOnMain() which handles:\n *    - Checking main branch exists\n *    - Detecting uncommitted changes (throws if found)\n *    - Checking if already up-to-date\n *    - Executing rebase\n *    - Claude-assisted conflict resolution\n * 4. Reports success\n */\nexport class RebaseCommand {\n\tprivate mergeManager: MergeManager\n\tprivate gitWorktreeManager: GitWorktreeManager\n\tprivate settingsManager: SettingsManager\n\n\tconstructor(mergeManager?: MergeManager, gitWorktreeManager?: GitWorktreeManager, settingsManager?: SettingsManager) {\n\t\tthis.mergeManager = mergeManager ?? new MergeManager()\n\t\tthis.gitWorktreeManager = gitWorktreeManager ?? new GitWorktreeManager()\n\t\tthis.settingsManager = settingsManager ?? new SettingsManager()\n\t}\n\n\t/**\n\t * Validate that the current directory is within an iloom-managed worktree\n\t * Returns the worktree root path if valid\n\t * @throws WorktreeValidationError if validation fails\n\t */\n\tprivate async validateWorktreeContext(): Promise<string> {\n\t\tconst currentDir = process.cwd()\n\n\t\t// Step 1: Check if we're in a git repository at all\n\t\tconst isGitRepo = await isValidGitRepo(currentDir)\n\t\tif (!isGitRepo) {\n\t\t\tthrow new WorktreeValidationError(\n\t\t\t\t'Not a git repository.',\n\t\t\t\t\"Run 'il rebase' from within an iloom worktree created by 'il start'.\"\n\t\t\t)\n\t\t}\n\n\t\t// Step 2: Get the worktree root (handles subdirectories)\n\t\tconst worktreeRoot = await getWorktreeRoot(currentDir)\n\t\tif (!worktreeRoot) {\n\t\t\tthrow new WorktreeValidationError(\n\t\t\t\t'Could not determine repository root.',\n\t\t\t\t\"Run 'il rebase' from within an iloom worktree created by 'il start'.\"\n\t\t\t)\n\t\t}\n\n\t\t// Step 3: Check if this path is a registered git worktree\n\t\tconst worktrees = await this.gitWorktreeManager.listWorktrees()\n\t\tconst currentWorktree = worktrees.find(wt => wt.path === worktreeRoot)\n\n\t\tif (!currentWorktree) {\n\t\t\tthrow new WorktreeValidationError(\n\t\t\t\t'This directory is not an iloom worktree.',\n\t\t\t\t\"Run 'il rebase' from within a worktree created by 'il start <issue>'. Use 'il list' to see available worktrees.\"\n\t\t\t)\n\t\t}\n\n\t\t// Step 4: Check if this is the main worktree (we shouldn't rebase from main)\n\t\tconst isMain = await this.gitWorktreeManager.isMainWorktree(currentWorktree, this.settingsManager)\n\t\tif (isMain) {\n\t\t\tthrow new WorktreeValidationError(\n\t\t\t\t'Cannot rebase from the main worktree.',\n\t\t\t\t\"Navigate to a feature worktree created by 'il start <issue>' and run 'il rebase' from there.\"\n\t\t\t)\n\t\t}\n\n\t\treturn worktreeRoot\n\t}\n\n\tasync execute(options: RebaseOptions = {}): Promise<void> {\n\t\t// Step 1: Validate we're in a valid iloom worktree\n\t\tlet worktreePath: string\n\t\ttry {\n\t\t\tworktreePath = await this.validateWorktreeContext()\n\t\t} catch (error) {\n\t\t\tif (error instanceof WorktreeValidationError) {\n\t\t\t\tlogger.error(error.message)\n\t\t\t\tlogger.info(error.suggestion)\n\t\t\t\tthrow error\n\t\t\t}\n\t\t\tthrow error\n\t\t}\n\n\t\tconst mergeOptions: MergeOptions = {\n\t\t\tdryRun: options.dryRun ?? false,\n\t\t\tforce: options.force ?? false,\n\t\t}\n\n\t\t// MergeManager.rebaseOnMain() handles:\n\t\t// - Checking main branch exists\n\t\t// - Detecting uncommitted changes (throws if found)\n\t\t// - Checking if already up-to-date\n\t\t// - Executing rebase\n\t\t// - Claude-assisted conflict resolution\n\t\tawait this.mergeManager.rebaseOnMain(worktreePath, mergeOptions)\n\t}\n}\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;AAeO,IAAM,0BAAN,cAAsC,MAAM;AAAA,EAClD,YACC,SACgB,YACf;AACD,UAAM,OAAO;AAFG;AAGhB,SAAK,OAAO;AAAA,EACb;AACD;AAgBO,IAAM,gBAAN,MAAoB;AAAA,EAK1B,YAAY,cAA6B,oBAAyC,iBAAmC;AACpH,SAAK,eAAe,gBAAgB,IAAI,aAAa;AACrD,SAAK,qBAAqB,sBAAsB,IAAI,mBAAmB;AACvE,SAAK,kBAAkB,mBAAmB,IAAI,gBAAgB;AAAA,EAC/D;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAOA,MAAc,0BAA2C;AACxD,UAAM,aAAa,QAAQ,IAAI;AAG/B,UAAM,YAAY,MAAM,eAAe,UAAU;AACjD,QAAI,CAAC,WAAW;AACf,YAAM,IAAI;AAAA,QACT;AAAA,QACA;AAAA,MACD;AAAA,IACD;AAGA,UAAM,eAAe,MAAM,gBAAgB,UAAU;AACrD,QAAI,CAAC,cAAc;AAClB,YAAM,IAAI;AAAA,QACT;AAAA,QACA;AAAA,MACD;AAAA,IACD;AAGA,UAAM,YAAY,MAAM,KAAK,mBAAmB,cAAc;AAC9D,UAAM,kBAAkB,UAAU,KAAK,QAAM,GAAG,SAAS,YAAY;AAErE,QAAI,CAAC,iBAAiB;AACrB,YAAM,IAAI;AAAA,QACT;AAAA,QACA;AAAA,MACD;AAAA,IACD;AAGA,UAAM,SAAS,MAAM,KAAK,mBAAmB,eAAe,iBAAiB,KAAK,eAAe;AACjG,QAAI,QAAQ;AACX,YAAM,IAAI;AAAA,QACT;AAAA,QACA;AAAA,MACD;AAAA,IACD;AAEA,WAAO;AAAA,EACR;AAAA,EAEA,MAAM,QAAQ,UAAyB,CAAC,GAAkB;AAEzD,QAAI;AACJ,QAAI;AACH,qBAAe,MAAM,KAAK,wBAAwB;AAAA,IACnD,SAAS,OAAO;AACf,UAAI,iBAAiB,yBAAyB;AAC7C,eAAO,MAAM,MAAM,OAAO;AAC1B,eAAO,KAAK,MAAM,UAAU;AAC5B,cAAM;AAAA,MACP;AACA,YAAM;AAAA,IACP;AAEA,UAAM,eAA6B;AAAA,MAClC,QAAQ,QAAQ,UAAU;AAAA,MAC1B,OAAO,QAAQ,SAAS;AAAA,IACzB;AAQA,UAAM,KAAK,aAAa,aAAa,cAAc,YAAY;AAAA,EAChE;AACD;","names":[]}

package/dist/{run-SJPM6YRI.js → run-MJYY4PUT.js}

@@ -14,7 +14,7 @@ import {
 } from "./chunk-YETJNRQM.js";
 import {
   GitWorktreeManager
-} from "./chunk-OAP6SASD.js";
+} from "./chunk-2CXREBLZ.js";
 import "./chunk-ZT3YZB4K.js";
 import {
   ProjectCapabilityDetector
@@ -25,10 +25,10 @@ import {
 } from "./chunk-GYCR2LOU.js";
 import {
   extractIssueNumber
-} from "./chunk-5NTD4MCZ.js";
+} from "./chunk-5Q3NDNNV.js";
 import {
   SettingsManager
-} from "./chunk-UCZ24SUE.js";
+} from "./chunk-CDZERT7Z.js";
 import {
   extractPort,
   findEnvFileContainingVariable,
@@ -289,4 +289,4 @@ Make sure the project is built (run 'il start' first)`
 export {
   RunCommand
 };
-//# sourceMappingURL=run-SJPM6YRI.js.map
+//# sourceMappingURL=run-MJYY4PUT.js.map

package/dist/schema/settings.schema.json

@@ -328,14 +328,32 @@
                 "webstorm",
                 "sublime",
                 "intellij",
-                "windsurf"
+                "windsurf",
+                "antigravity"
               ],
               "default": "vscode",
-              "description": "IDE to launch when starting a loom. Options: vscode (Visual Studio Code), cursor (Cursor AI editor), webstorm (JetBrains WebStorm), sublime (Sublime Text), intellij (JetBrains IntelliJ IDEA), windsurf (Windsurf editor)."
+              "description": "IDE to launch when starting a loom. Options: vscode (Visual Studio Code), cursor (Cursor AI editor), webstorm (JetBrains WebStorm), sublime (Sublime Text), intellij (JetBrains IntelliJ IDEA), windsurf (Windsurf editor), antigravity (Antigravity IDE)."
             }
           },
           "additionalProperties": false,
-          "description": "IDE configuration for workspace launches. Controls which editor opens when you start a loom. Supports VSCode, Cursor, WebStorm, Sublime Text, IntelliJ, and Windsurf. Note: Color synchronization (title bar colors) only works with VSCode-compatible editors (vscode, cursor, windsurf)."
+          "description": "IDE configuration for workspace launches. Controls which editor opens when you start a loom. Supports VSCode, Cursor, WebStorm, Sublime Text, IntelliJ, Windsurf, and Antigravity. Note: Color synchronization (title bar colors) only works with VSCode-compatible editors (vscode, cursor, windsurf, antigravity)."
+        },
+        "colors": {
+          "type": "object",
+          "properties": {
+            "terminal": {
+              "type": "boolean",
+              "default": true,
+              "description": "Apply terminal background colors based on branch name (macOS only)"
+            },
+            "vscode": {
+              "type": "boolean",
+              "default": false,
+              "description": "Apply VSCode/Cursor title bar colors based on branch name. Note: This modifies .vscode/settings.json which may be in source control. Default is false for safety; enable via init or explicitly if .vscode is gitignored."
+            }
+          },
+          "additionalProperties": false,
+          "description": "Color synchronization settings for workspace identification"
         }
       },
       "additionalProperties": false

package/dist/{test-git-DEUE656D.js → test-git-IT5EWQ5C.js}

@@ -1,10 +1,10 @@
 #!/usr/bin/env node
 import {
   findMainWorktreePath
-} from "./chunk-5NTD4MCZ.js";
+} from "./chunk-5Q3NDNNV.js";
 import {
   SettingsManager
-} from "./chunk-UCZ24SUE.js";
+} from "./chunk-CDZERT7Z.js";
 import {
   logger
 } from "./chunk-GEHQXLEI.js";
@@ -49,4 +49,4 @@ var TestGitCommand = class {
 export {
   TestGitCommand
 };
-//# sourceMappingURL=test-git-DEUE656D.js.map
+//# sourceMappingURL=test-git-IT5EWQ5C.js.map

package/dist/{test-prefix-Y6Z6ZHSF.js → test-prefix-NPWDPUUH.js}

@@ -1,10 +1,10 @@
 #!/usr/bin/env node
 import {
   generateWorktreePath
-} from "./chunk-5NTD4MCZ.js";
+} from "./chunk-5Q3NDNNV.js";
 import {
   SettingsManager
-} from "./chunk-UCZ24SUE.js";
+} from "./chunk-CDZERT7Z.js";
 import {
   logger
 } from "./chunk-GEHQXLEI.js";
@@ -65,4 +65,4 @@ var TestPrefixCommand = class {
 export {
   TestPrefixCommand
 };
-//# sourceMappingURL=test-prefix-Y6Z6ZHSF.js.map
+//# sourceMappingURL=test-prefix-NPWDPUUH.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iloom/cli",
-  "version": "0.3.2",
+  "version": "0.3.4",
   "description": "Control plane for maintaining alignment between you and Claude Code as you work across multiple issues using isolated environments, visible context, and multi-agent workflows to scale understanding, not just output",
   "keywords": [
     "ai",
@@ -53,6 +53,7 @@
     "test": "vitest run",
     "test:watch": "vitest --watch",
     "test:coverage": "vitest run --coverage",
+    "test:hanging": "vitest run --reporter=hanging-process",
     "test:ui": "vitest --ui",
     "lint": "eslint . --ext .ts,.tsx --report-unused-disable-directives --max-warnings 0",
     "lint:fix": "eslint . --ext .ts,.tsx --fix",

package/dist/ClaudeContextManager-5WPRJIIW.js

@@ -1,15 +0,0 @@
-#!/usr/bin/env node
-import {
-  ClaudeContextManager
-} from "./chunk-C7ASXK6J.js";
-import "./chunk-A2P7NZTB.js";
-import "./chunk-WEN5C5DM.js";
-import "./chunk-UCZ24SUE.js";
-import "./chunk-ZLIHIUDQ.js";
-import "./chunk-RW54ZMBM.js";
-import "./chunk-UJL4HI2R.js";
-import "./chunk-GEHQXLEI.js";
-export {
-  ClaudeContextManager
-};
-//# sourceMappingURL=ClaudeContextManager-5WPRJIIW.js.map

package/dist/ClaudeService-Z4KA7QOW.js

@@ -1,14 +0,0 @@
-#!/usr/bin/env node
-import {
-  ClaudeService
-} from "./chunk-A2P7NZTB.js";
-import "./chunk-WEN5C5DM.js";
-import "./chunk-UCZ24SUE.js";
-import "./chunk-ZLIHIUDQ.js";
-import "./chunk-RW54ZMBM.js";
-import "./chunk-UJL4HI2R.js";
-import "./chunk-GEHQXLEI.js";
-export {
-  ClaudeService
-};
-//# sourceMappingURL=ClaudeService-Z4KA7QOW.js.map