@iloom/cli 0.3.2 → 0.3.4

package/dist/init-4FHTAM3F.js

@@ -0,0 +1,19 @@
+#!/usr/bin/env node
+import {
+  InitCommand
+} from "./chunk-UAN4A3YU.js";
+import "./chunk-PA6Q6AWM.js";
+import "./chunk-OSCLCMDG.js";
+import "./chunk-2CXREBLZ.js";
+import "./chunk-RIEO2WML.js";
+import "./chunk-5Q3NDNNV.js";
+import "./chunk-CDZERT7Z.js";
+import "./chunk-CE26YH2U.js";
+import "./chunk-OYF4VIFI.js";
+import "./chunk-RW54ZMBM.js";
+import "./chunk-UJL4HI2R.js";
+import "./chunk-GEHQXLEI.js";
+export {
+  InitCommand
+};
+//# sourceMappingURL=init-4FHTAM3F.js.map

package/dist/{neon-helpers-5HBYO2VP.js → neon-helpers-77PBPGJ5.js}

@@ -1,10 +1,10 @@
 #!/usr/bin/env node
 import {
   createNeonProviderFromSettings
-} from "./chunk-GVICXJHW.js";
-import "./chunk-JKXJ7BGL.js";
+} from "./chunk-5VK4NRSF.js";
+import "./chunk-CE26YH2U.js";
 import "./chunk-GEHQXLEI.js";
 export {
   createNeonProviderFromSettings
 };
-//# sourceMappingURL=neon-helpers-5HBYO2VP.js.map
+//# sourceMappingURL=neon-helpers-77PBPGJ5.js.map

package/dist/{open-FCHKQ77R.js → open-UMXANW5S.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 {
   OpenCommand
 };
-//# sourceMappingURL=open-FCHKQ77R.js.map
+//# sourceMappingURL=open-UMXANW5S.js.map

package/dist/{prompt-7INJ7YRU.js → prompt-QALMYTVC.js}

@@ -1,15 +1,17 @@
 #!/usr/bin/env node
 import {
   isInteractiveEnvironment,
+  promptCommitAction,
   promptConfirmation,
   promptInput,
   waitForKeypress
-} from "./chunk-JKXJ7BGL.js";
+} from "./chunk-CE26YH2U.js";
 import "./chunk-GEHQXLEI.js";
 export {
   isInteractiveEnvironment,
+  promptCommitAction,
   promptConfirmation,
   promptInput,
   waitForKeypress
 };
-//# sourceMappingURL=prompt-7INJ7YRU.js.map
+//# sourceMappingURL=prompt-QALMYTVC.js.map

package/dist/prompt-QALMYTVC.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":[],"sourcesContent":[],"mappings":"","names":[]}

package/dist/prompts/init-prompt.txt

@@ -417,14 +417,32 @@ The following JSON Schema defines valid iloom settings:
                 "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
@@ -647,7 +665,7 @@ Use AskUserQuestion to ask ALL local development settings questions **IN A SINGL
      - "bypassPermissions" - Claude executes without confirmation (use with caution)
    - Default: currentPermissionMode or "acceptEdits"
    - Validation: Must be one of: default, plan, acceptEdits, bypassPermissions
-   - Store answer as: `workflows.issue.permissionMode`
+   - Store answer as: `workflows.issue.permissionMode` - NOTE: this is a personal preference - recommend it be stored in the gitignored local settings file.
 
 4. **Base Port**
    - Question format: "What base port should web development servers use?{{#IF currentBasePort}} (Currently: [currentBasePort]){{/IF currentBasePort}}"
@@ -754,10 +772,11 @@ REMOTES_INFO
      - "sublime" - Sublime Text
      - "intellij" - JetBrains IntelliJ IDEA
      - "windsurf" - Windsurf editor
+     - "antigravity" - Antigravity IDE
    - Default: currentIdeType or "vscode"
    - Validation: Must be one of the listed options
    - Store answer as: `ide.type`
-   - Note: Color synchronization (title bar colors) only works with VSCode-compatible editors (vscode, cursor, windsurf). Other IDEs will launch without color theming.
+   - Note: Color synchronization (title bar colors) only works with VSCode-compatible editors (vscode, cursor, windsurf, antigravity). Other IDEs will launch without color theming.
 
 **Step 4: Merge Mode** (only ask if multiple remotes detected OR user requests advanced config)
 
@@ -780,6 +799,40 @@ REMOTES_INFO
 - Set multiSelect: false for all questions
 - Process answers sequentially as they depend on each other
 
+### Phase 2.5: Color Synchronization Settings - ONLY IF USER HAS CHOSEN the vscode, cursor, windsurf, or antigravity IDE
+
+After Phase 2, handle color settings based on gitignore status.
+
+Analyis of system: Is VSCode Settings ignore? VSCODE_SETTINGS_GITIGNORED
+
+**IMPORTANT DISTINCTION:**
+- Schema defaults are: terminal=true, vscode=false (for safety)
+- Your job in init is to RECOMMEND optimal settings based on the project
+- IMPORTANT: This is a per-project setting - recommend to save it in shared project settings (not globally). EVEN IF OTHER SETTINGS ARE SAVED ELSEHWERE
+
+**Terminal Color Recommendation:**
+- Always recommend `true` - terminal colors only affect macOS Terminal.app, no file changes
+
+**VSCode Color Recommendation:**
+
+**If "VSCODE_SETTINGS_GITIGNORED" == "true":**
+- Recommend `colors.vscode: true` (safe since file is gitignored)
+- Explain: "VSCode title bar coloring is safe to enable since .vscode/settings.json is gitignored"
+
+**If "VSCODE_SETTINGS_GITIGNORED" == "false":**
+- Warn user: "VSCode/Cursor title bar coloring modifies .vscode/settings.json which is tracked in git."
+- Ask user: "Would you like to:
+  1. Add .vscode/settings.json to .gitignore (recommended - enables color sync without git pollution)
+  2. Keep VSCode color sync disabled (default - keeps .vscode/settings.json in source control unchanged)
+  3. Enable anyway (Please don't do this - colors will appear in git diffs)"
+
+Based on the users answer:
+- Option 1: Add to .gitignore, set `colors.vscode: true`
+- Option 2: Set `colors.vscode: false` (matches safe default)
+- Option 3: Set `colors.vscode: true` (with warning noted)
+
+**Note:** Terminal colors default to `true` (always recommend unless user explicitly disables).
+
 ### Phase 3: Configuration Summary
 
 After gathering all answers from Phase 1 and Phase 2, display a summary like this:
@@ -953,9 +1006,24 @@ When both settings.json and settings.local.json exist, you MUST prevent duplicat
    }
    ```
 
-7. **Combine all applicable sections** into a single JSON object. Only include sections where the value differs from the default.
+7. **Add colors settings based on Phase 2.5 recommendations (if vscode or cursor IDE):**
+   ```json
+   {
+     "colors": {
+       "terminal": true,  // Always recommend true unless user explicitly disabled
+       "vscode": <based on gitignore status and user choice>
+     }
+   }
+   ```
+   - Default behavior: Only include if vscode differs from default (false) or terminal is disabled
+   - If "VSCODE_SETTINGS_GITIGNORED" == "true" (note: variable has been subsituted) and user accepted recommendation: `"vscode": true`
+   - If user chose to add .vscode/settings.json to .gitignore: `"vscode": true`
+   - If user chose to keep disabled or enable anyway: set accordingly
+   - Terminal should be true unless user explicitly disabled it
+
+8. **Combine all applicable sections** into a single JSON object. Only include sections where the value differs from the default.
 
-8. **If existing settings exist, MERGE** the new values with existing ones. Don't overwrite settings the user didn't modify.
+9. **If existing settings exist, MERGE** the new values with existing ones. Don't overwrite settings the user didn't modify.
 
 ### Phase 6: Write File
 
@@ -963,6 +1031,8 @@ When both settings.json and settings.local.json exist, you MUST prevent duplicat
 
 Before writing the file, perform a final duplication check:
 
+**You might need to create/update multiple files - if some settigns should be not commitedd (ie. API Keys, permissionMode etc), then recommend create a local settings file for those settings and a shared one for others.
+
 **If writing to settings.local.json:**
 1. Load the current settings.json (if it exists)
 2. Compare EVERY setting in the generated local config against settings.json
@@ -992,7 +1062,7 @@ Reason: mainBranch has same value in both files, so it's removed from local
    - For global: Ensure `~/.config/iloom-ai/` directory exists (create if needed)
    - For project/local: Ensure `.iloom/` directory exists (create if needed)
 2. Perform duplication check as described above
-3. Write the deduplicated settings to the chosen file:
+3. For each settings file you need to update, write the deduplicated settings to the chosen file:
    - `~/.config/iloom-ai/settings.json` if user chose Global
    - `.iloom/settings.json` if user chose Project
    - `.iloom/settings.local.json` if user chose Local
@@ -1073,9 +1143,12 @@ Would you like to commit these changes?
 - **NEVER stage or commit unrelated files** - even if they appear in `git status`
 - **If the commit fails, you must then subsequently request to use --no-verify flag** to bypass pre-commit hooks that might fail due to unrelated codebase state
 - **Do NOT commit settings.local.json** - it should be gitignored, not committed
+- **YOU MAY NEED TO EDIT/UPDATE MORE THAN ONE FILE if the user is changing something like API Keys (local only), permissionsMode (local only), IDE (recommened global) as well as shared settings.
 
 **Step 3: If user says yes, commit the changes**
 
+VERIFY YOU'RE NOT BUNDLING ALL CHANGES IN ONE FILE DESPITE GUIDANCE TO SPLIT ACCORDING TO RULES/RECOMMENDATIONS ABOVE
+
 Stage ONLY the iloom-related files that should be committed:
 ```bash
 git add .iloom/settings.json .gitignore 2>/dev/null || true
@@ -1219,6 +1292,7 @@ If users ask about specific configurations, help them add these sections to thei
 - **Phase 1 = Local dev settings** (main branch, worktree prefix, permission mode, base port)
 - **Phase 2 = Tooling integrations** (issue tracker provider, provider-specific config, IDE, merge mode)
 - **Keep configuration minimal** - only include non-default values
+- **Honor recommendations/requirements of where to save certain settings - this may mean you have to create/update multiple settings files. (e.g when adding API keys for permissions mode settings)
 - **Merge carefully** when updating existing settings - preserve any settings the user didn't modify
 - **Handle errors gracefully** - if schema validation fails, explain what went wrong and ask the user to try again
 - **CRITICAL: PREVENT DUPLICATION** - When writing settings.local.json, ONLY include settings that differ from settings.json. If a setting has the same value in both files, it MUST be removed from the local file. Local should only contain overrides, never duplicates.

package/dist/prompts/issue-prompt.txt

@@ -30,7 +30,7 @@ This is the user's first time running through the `iloom` workflow. You have add
 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 SIMPLE or COMPLEX based on scope
+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
@@ -121,7 +121,7 @@ You are orchestrating a set of agents through a development process, with human
 5. Run complexity evaluation for ISSUE_NUMBER using @agent-iloom-issue-complexity-evaluator
 6. Extract issue link that includes comment id from agent output, 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 (SIMPLE or COMPLEX)
+8. Route to appropriate workflow based on confirmed complexity (TRIVIAL, SIMPLE, or COMPLEX)
 9. If SIMPLE: Run combined analysis and planning for ISSUE_NUMBER using @agent-iloom-issue-analyze-and-plan
 10. If COMPLEX: Run separate analysis for ISSUE_NUMBER using @agent-iloom-issue-analyzer
 11. Extract issue link that includes comment id from agent output, display to user
@@ -152,10 +152,10 @@ Perform ONE comprehensive scan to determine which agents need to run:
    **Complexity Evaluation Decision:**
    - Search ALL comments for existing complexity evaluation. Consider "already evaluated" if ANY comment has:
      * Header containing "Complexity Assessment" or "Complexity Evaluation"
-     * Section with "**Classification**: [SIMPLE / COMPLEX]"
+     * Section with "**Classification**: [TRIVIAL / SIMPLE / COMPLEX]"
      * Metrics section with estimated files, LOC, breaking changes, DB migrations, and risk level
    - Decision: NEEDS_COMPLEXITY_EVAL or SKIP_COMPLEXITY_EVAL
-   - If skipping, log: "Issue #ISSUE_NUMBER already has complexity evaluation by @[author] from [date] showing [SIMPLE/COMPLEX] classification, skipping evaluation"
+   - If skipping, log: "Issue #ISSUE_NUMBER already has complexity evaluation by @[author] from [date] showing [TRIVIAL/SIMPLE/COMPLEX] classification, skipping evaluation"
 
    **Analysis Decision:**
    - Search ALL comments for existing analysis. Consider "already analyzed" if ANY comment has ALL:
@@ -227,13 +227,13 @@ Only execute if workflow plan determined NEEDS_COMPLEXITY_EVAL:
 2. Upon completion: Extract issue+comment link from agent output and provide link to issue comment (including comment ID)
 3. Extract complexity classification from evaluator output:
    - Search the evaluator's output for the "Complexity Assessment" section
-   - Extract: Classification (SIMPLE/COMPLEX), Metrics (files, LOC, breaking changes, DB migrations, risk level), and Reasoning
+   - Extract: Classification (TRIVIAL/SIMPLE/COMPLEX), Metrics (files, LOC, breaking changes, DB migrations, risk level), and Reasoning
    - The evaluator uses deterministic format - parse exactly as specified
 4. Display complexity assessment to user:
    Display the extracted assessment in this format:
    ```
    Complexity Assessment from Evaluator:
-   - Classification: [SIMPLE/COMPLEX]
+   - Classification: [TRIVIAL/SIMPLE/COMPLEX]
    - Estimated files: [N]
    - Estimated LOC: [N]
    - Breaking changes: [Yes/No]
@@ -243,9 +243,10 @@ Only execute if workflow plan determined NEEDS_COMPLEXITY_EVAL:
    Reasoning: [reasoning text from evaluator]
    ```
 5. Use AskUserQuestion tool with a single question:
-   - Question: "Complexity evaluated as [SIMPLE/COMPLEX]. See assessment at: [issue comment URL]. Do you agree with this classification?"
+   - Question: "Complexity evaluated as [TRIVIAL/SIMPLE/COMPLEX]. See assessment at: [issue comment URL]. Do you agree with this classification?"
    - Options:
-     - "Yes, proceed with [SIMPLE/COMPLEX] workflow" (default)
+     - "Yes, proceed with [TRIVIAL/SIMPLE/COMPLEX] workflow" (default)
+     - "No, reclassify as TRIVIAL"
      - "No, reclassify as SIMPLE"
      - "No, reclassify as COMPLEX"
      - "Provide feedback before deciding"
@@ -260,11 +261,11 @@ Only execute if workflow plan determined NEEDS_COMPLEXITY_EVAL:
 If workflow plan determined SKIP_COMPLEXITY_EVAL:
 1. Mark todos #5, #6, and #7 as completed
 2. Extract complexity from existing evaluation comment:
-   - Search ALL issue comments for "**Classification**: [SIMPLE / COMPLEX]"
-   - If found: Extract the classification (SIMPLE or COMPLEX)
+   - Search ALL issue comments for "**Classification**: [TRIVIAL / SIMPLE / COMPLEX]"
+   - If found: Extract the classification (TRIVIAL, SIMPLE, or COMPLEX)
    - If not found: Default to COMPLEX workflow
 3. Display classification to user:
-   If complexity found: "Previous evaluation classified this as [SIMPLE/COMPLEX]. Proceeding with [SIMPLE/COMPLEX] workflow."
+   If complexity found: "Previous evaluation classified this as [TRIVIAL/SIMPLE/COMPLEX]. Proceeding with [TRIVIAL/SIMPLE/COMPLEX] workflow."
    If not found: "No complexity classification found - defaulting to COMPLEX workflow."
 4. Proceed to ROUTING DECISION POINT with extracted complexity (no confirmation needed)
 
@@ -297,6 +298,12 @@ After STEP 1.5 completes and complexity is confirmed, determine which workflow p
 
 **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 todo #8 as completed
+3. Mark todos #9, #10, #11, #12, #13, #14, and #15 as completed (analysis/planning steps that will not execute)
+4. Skip directly to **STEP 4** (Implementation Phase)
+
 **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 todo #8 as completed