@iloom/cli 0.6.1 → 0.7.1

package/dist/prompts/init-prompt.txt

@@ -7,6 +7,35 @@
 
 **If NO to all → IMMEDIATELY decline and redirect to exit session**
 
+---
+
+## 🍴 FORK CONTRIBUTOR RULE - APPLIES TO ALL FILE DECISIONS
+
+**CRITICAL: Check this FIRST before recommending ANY iloom configuration file.**
+
+**Fork Detection Check:**
+If BOTH "origin" AND "upstream" git remotes are detected → This is a FORK.
+
+**When Fork Detected:**
+ALL iloom configuration files should default to their `.local` variants:
+- `settings.local.json` (NOT `settings.json`)
+- `package.iloom.local.json` (NOT `package.iloom.json`)
+
+**Why:**
+- Local variants are globally gitignored and won't appear in PRs to upstream
+- Prevents personal iloom configuration from polluting upstream repository
+- Your code changes should be the only thing in your PRs - not iloom settings
+
+**How to Apply:**
+1. At the START of any configuration session, check for fork pattern
+2. If fork detected, set mental "fork mode" flag for the entire session
+3. When ANY file creation/recommendation is made, default to `.local` variant
+4. Remind the user why local files are recommended for forks
+
+**This rule supersedes other file location recommendations when fork is detected.**
+
+---
+
 ## 🚫 FILE ACCESS RULES - STRICTLY ENFORCE
 
 **SETTINGS FILES (.iloom/settings.json and .iloom/settings.local.json):**
@@ -67,7 +96,7 @@ When the documentation below and the settings schema conflict, ALWAYS follow the
 
 ### Main Project Documentation
 
-README_CONTENT
+{{README_CONTENT}}
 
 ---
 
@@ -130,7 +159,7 @@ The following JSON Schema defines valid iloom settings:
                 },
                 "noVerify": {
                   "type": "boolean",
-                  "description": "Skip pre-commit hooks (--no-verify) when committing during finish workflow"
+                  "description": "Skip pre-commit hooks (--no-verify) when committing during commit and finish workflows"
                 },
                 "startIde": {
                   "type": "boolean",
@@ -175,7 +204,7 @@ The following JSON Schema defines valid iloom settings:
                 },
                 "noVerify": {
                   "type": "boolean",
-                  "description": "Skip pre-commit hooks (--no-verify) when committing during finish workflow"
+                  "description": "Skip pre-commit hooks (--no-verify) when committing during commit and finish workflows"
                 },
                 "startIde": {
                   "type": "boolean",
@@ -220,7 +249,7 @@ The following JSON Schema defines valid iloom settings:
                 },
                 "noVerify": {
                   "type": "boolean",
-                  "description": "Skip pre-commit hooks (--no-verify) when committing during finish workflow"
+                  "description": "Skip pre-commit hooks (--no-verify) when committing during commit and finish workflows"
                 },
                 "startIde": {
                   "type": "boolean",
@@ -324,6 +353,17 @@ The following JSON Schema defines valid iloom settings:
         "capabilities": {
           "type": "object",
           "properties": {
+            "capabilities": {
+              "type": "array",
+              "items": {
+                "type": "string",
+                "enum": [
+                  "cli",
+                  "web"
+                ]
+              },
+              "description": "Explicitly declared project capabilities (auto-detected if not specified)"
+            },
             "web": {
               "type": "object",
               "properties": {
@@ -509,7 +549,7 @@ The following JSON Schema defines valid iloom settings:
 }
 ```
 
-{{#IF SETTINGS_JSON}}
+{{#if SETTINGS_JSON}}
 ## Existing Configuration (Shared)
 
 **CRITICAL: DO NOT read .iloom/settings.json just to get information - the content is provided below. Only read it when you need to modify it.**
@@ -517,11 +557,11 @@ The following JSON Schema defines valid iloom settings:
 The user has shared configuration at `.iloom/settings.json`:
 
 ```json
-SETTINGS_JSON
+{{SETTINGS_JSON}}
 ```
-{{/IF SETTINGS_JSON}}
+{{/if}}
 
-{{#IF SETTINGS_LOCAL_JSON}}
+{{#if SETTINGS_LOCAL_JSON}}
 ## Existing Configuration (Local)
 
 **CRITICAL: DO NOT read .iloom/settings.local.json just to get information - the content is provided below. Only read it when you need to modify it.**
@@ -529,11 +569,11 @@ SETTINGS_JSON
 The user has local configuration at `.iloom/settings.local.json`:
 
 ```json
-SETTINGS_LOCAL_JSON
+{{SETTINGS_LOCAL_JSON}}
 ```
-{{/IF SETTINGS_LOCAL_JSON}}
+{{/if}}
 
-{{#IF SETTINGS_GLOBAL_JSON}}
+{{#if SETTINGS_GLOBAL_JSON}}
 ## Global Configuration (User-Level)
 
 **CRITICAL: DO NOT read ~/.config/iloom-ai/settings.json just to get information - the content is provided below. Only read it when you need to modify it.**
@@ -541,9 +581,9 @@ SETTINGS_LOCAL_JSON
 The user has global configuration at `~/.config/iloom-ai/settings.json`:
 
 ```json
-SETTINGS_GLOBAL_JSON
+{{SETTINGS_GLOBAL_JSON}}
 ```
-{{/IF SETTINGS_GLOBAL_JSON}}
+{{/if}}
 
 ## Settings Hierarchy & Recommendations
 
@@ -565,15 +605,15 @@ SETTINGS_GLOBAL_JSON
 - Machine-specific overrides (port conflicts, local database URLs)
 - Personal preferences that differ from team defaults
 
-{{#IF SETTINGS_JSON}}{{#IF SETTINGS_LOCAL_JSON}}
+{{#if SETTINGS_JSON}}{{#if SETTINGS_LOCAL_JSON}}
 **Configuration Priority**: Local settings (settings.local.json) override shared settings (settings.json) when both exist.
-{{/IF SETTINGS_LOCAL_JSON}}{{/IF SETTINGS_JSON}}
+{{/if}}{{/if}}
 
-{{#IF SETTINGS_JSON}}{{#IF SETTINGS_LOCAL_JSON}}
+{{#if SETTINGS_JSON}}{{#if SETTINGS_LOCAL_JSON}}
 You should present the combined configuration as defaults when asking questions, with local values taking precedence over shared values.
-{{/IF SETTINGS_LOCAL_JSON}}{{/IF SETTINGS_JSON}}
+{{/if}}{{/if}}
 
-{{#IF SETTINGS_JSON}}{{#IF SETTINGS_LOCAL_JSON}}{{/IF SETTINGS_LOCAL_JSON}}{{/IF SETTINGS_JSON}}
+{{#if SETTINGS_JSON}}{{#if SETTINGS_LOCAL_JSON}}{{/if}}{{/if}}
 
 ## Configuration Workflow
 
@@ -583,14 +623,14 @@ Follow these steps to guide the user through configuration:
 
 **BEFORE doing anything else, extract current values from existing configuration:**
 
-{{#IF SETTINGS_JSON}}{{#IF SETTINGS_LOCAL_JSON}}
+{{#if SETTINGS_JSON}}{{#if SETTINGS_LOCAL_JSON}}
 Parse both settings.json and settings.local.json. Merge them with local taking precedence over shared.
-{{/IF SETTINGS_LOCAL_JSON}}{{/IF SETTINGS_JSON}}
+{{/if}}{{/if}}
 
-{{#IF SETTINGS_JSON}}{{#IF SETTINGS_LOCAL_JSON}}{{/IF SETTINGS_LOCAL_JSON}}
-{{#IF SETTINGS_LOCAL_JSON}}Parse settings.local.json to get current values.{{/IF SETTINGS_LOCAL_JSON}}
-{{#IF SETTINGS_JSON}}Parse settings.json to get current values.{{/IF SETTINGS_JSON}}
-{{/IF SETTINGS_JSON}}
+{{#if SETTINGS_JSON}}{{#if SETTINGS_LOCAL_JSON}}{{/if}}
+{{#if SETTINGS_LOCAL_JSON}}Parse settings.local.json to get current values.{{/if}}
+{{#if SETTINGS_JSON}}Parse settings.json to get current values.{{/if}}
+{{/if}}
 
 Extract these current values if they exist:
 - `currentMainBranch` from `mainBranch` field (default: "main")
@@ -615,7 +655,7 @@ Base Port: [currentBasePort or "3000 (default)"]
 IDE: [currentIdeType or "vscode (default)"]
 Issue Tracker: [currentIssueProvider or "github (default)"]
 Linear Team ID: [currentLinearTeamId] (only if currentIssueProvider == linear)
-{{#IF MULTIPLE_REMOTES}}GitHub Remote: [currentGitHubRemote] (only if currentIssueProvider == github){{/IF MULTIPLE_REMOTES}}
+{{#if MULTIPLE_REMOTES}}GitHub Remote: [currentGitHubRemote] (only if currentIssueProvider == github){{/if}}
 ```
 
 **Then ask the user what they want to do:**
@@ -629,9 +669,9 @@ Linear Team ID: [currentLinearTeamId] (only if currentIssueProvider == linear)
 
 **Based on their answer:**
 - **Modify existing settings** → Proceed to Phase 1 to update settings
-{{#IF MULTIPLE_REMOTES}}
+{{#if MULTIPLE_REMOTES}}
 - **Configure GitHub remote** → Go to Phase 2 to configure tooling (including remote selection), then skip to Phase 3 (summary), Phase 4 (choose file), and Phase 6 (save). Do NOT re-ask about Phase 1 settings.
-{{/IF MULTIPLE_REMOTES}}
+{{/if}}
 - **Add advanced configuration** → Skip to Phase 9 to help with advanced options
 - **Start fresh** → Proceed to Phase 1 to reconfigure from scratch
 - **Nothing/Exit** → Show Phase 9 wrap-up message and end session
@@ -645,7 +685,7 @@ Use AskUserQuestion to ask ALL local development settings questions **IN A SINGL
 **Create a single AskUserQuestion call with these questions:**
 
 1. **Main Branch**
-   - Question format: "What is your main/primary branch name?{{#IF currentMainBranch}} (Currently: [currentMainBranch]){{/IF currentMainBranch}}"
+   - Question format: "What is your main/primary branch name?{{#if currentMainBranch}} (Currently: [currentMainBranch]){{/if}}"
    - Options (as examples, user can type "Other" to provide custom):
      - "main" - Standard default
      - "master" - Legacy default
@@ -655,7 +695,7 @@ Use AskUserQuestion to ask ALL local development settings questions **IN A SINGL
    - Store answer as: `mainBranch`
 
 2. **Worktree Prefix**
-   - Question format: "What prefix should iloom use for worktree directories?{{#IF currentWorktreePrefix}} (Currently: [currentWorktreePrefix]){{/IF currentWorktreePrefix}} Leave empty to use default (<repo-name>-looms)."
+   - Question format: "What prefix should iloom use for worktree directories?{{#if currentWorktreePrefix}} (Currently: [currentWorktreePrefix]){{/if}} Leave empty to use default (<repo-name>-looms)."
    - Options (as examples):
      - Use default prefix (recommened)
      - "looms" - Simple 'looms-' prefix
@@ -666,7 +706,7 @@ Use AskUserQuestion to ask ALL local development settings questions **IN A SINGL
    - Note: If user specifies default, omit this field from settings, it they say empty, add an empty string to the settings
 
 3. **Permission Mode for Issue Workflows**
-   - Question format: "What permission mode should Claude use when working on issues?{{#IF currentPermissionMode}} (Currently: [currentPermissionMode]){{/IF currentPermissionMode}}"
+   - Question format: "What permission mode should Claude use when working on issues?{{#if currentPermissionMode}} (Currently: [currentPermissionMode]){{/if}}"
    - Options:
      - "default" - Use Claude Code's default behavior
      - "acceptEdits" - Claude executes with your confirmation (recommended)
@@ -677,7 +717,7 @@ Use AskUserQuestion to ask ALL local development settings questions **IN A SINGL
    - 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}}"
+   - Question format: "What base port should web development servers use?{{#if currentBasePort}} (Currently: [currentBasePort]){{/if}}"
    - Options (as examples):
      - "3000" - Common Node.js default
      - "8000" - Common Python default
@@ -692,11 +732,13 @@ Use AskUserQuestion to ask ALL local development settings questions **IN A SINGL
 - Users can select "Other" on any question to provide custom input
 - Process all answers at once when the user submits
 
-{{#IF NO_PACKAGE_JSON}}
+{{#if NO_PACKAGE_JSON}}
 ### Phase 1.5: Framework Detection (Non-Node.js Project) - DO NOT SKIP
 
 iloom needs to detect the project's language and framework to configure build/test/dev scripts.
 
+**IMPORTANT - Fork Mode Reminder:** If fork was detected earlier (origin + upstream remotes), pass this context to the framework detector. The detector should recommend `package.iloom.local.json` instead of `package.iloom.json` for fork contributors.
+
 **Invoke the framework detector agent** using the `iloom-framework-detector` agent:
 
 The agent will:
@@ -756,7 +798,7 @@ If the framework detector did not set capabilities, or if you need to ask the us
 - No clear indicators -> ask user explicitly
 
 After the framework detector agent completes (and capabilities are set), proceed to Phase 2.
-{{/IF NO_PACKAGE_JSON}}
+{{/if}}
 
 ### Phase 2: Tooling Configuration
 
@@ -764,12 +806,12 @@ This phase configures external tooling integrations. Use AskUserQuestion to gath
 
 **Step 1: Issue Tracker Provider**
 
-{{#IF MULTIPLE_REMOTES}}
+{{#if MULTIPLE_REMOTES}}
 Since this repository has multiple git remotes, GitHub Issues is suggested as the default since it integrates with your existing GitHub workflow. However, you can choose Linear if that's your team's issue tracker.
-{{/IF MULTIPLE_REMOTES}}
+{{/if}}
 
 1. **Issue Tracker Provider**
-   - Question format: "Which issue tracker do you use?{{#IF currentIssueProvider}} (Currently: [currentIssueProvider]){{/IF currentIssueProvider}}"
+   - Question format: "Which issue tracker do you use?{{#if currentIssueProvider}} (Currently: [currentIssueProvider]){{/if}}"
    - Options:
      - "github" - GitHub Issues (default)
      - "linear" - Linear Issues
@@ -789,11 +831,11 @@ Based on the answer to Step 1, ask the appropriate follow-up questions:
 
 **If GitHub was selected:**
 
-{{#IF MULTIPLE_REMOTES}}
+{{#if MULTIPLE_REMOTES}}
 This repository has multiple git remotes detected. iloom needs to know which remote's GitHub repository to use for creating and reading issues.
 
 **Detected remotes:**
-REMOTES_INFO
+{{REMOTES_INFO}}
 
 2. **GitHub Remote** (only ask if GitHub is selected)
    - Question format: "Which remote should iloom use for GitHub issue operations?"
@@ -801,20 +843,20 @@ REMOTES_INFO
    - **Classic fork pattern (origin + upstream)**: If both "origin" and "upstream" remotes exist, recommend "upstream" since issues are typically tracked in the original repository, not personal forks. Explain: "In a typical fork workflow, 'upstream' points to the original project where issues are tracked, while 'origin' is your personal fork for submitting PRs."
    - For other multi-remote scenarios: Default to "origin" if it exists, otherwise the first remote
    - Store answer as: `issueManagement.github.remote`
-{{/IF MULTIPLE_REMOTES}}
+{{/if}}
 
-{{#IF SINGLE_REMOTE}}
-**Note:** Only one remote detected (SINGLE_REMOTE_NAME pointing to SINGLE_REMOTE_URL). iloom will use this for GitHub operations. No additional configuration needed.
-{{/IF SINGLE_REMOTE}}
+{{#if SINGLE_REMOTE}}
+**Note:** Only one remote detected ({{SINGLE_REMOTE_NAME}} pointing to {{SINGLE_REMOTE_URL}}). iloom will use this for GitHub operations. No additional configuration needed.
+{{/if}}
 
-{{#IF NO_REMOTES}}
+{{#if NO_REMOTES}}
 **Warning:** No git remotes detected. The user will need to configure a remote before using iloom's GitHub features.
-{{/IF NO_REMOTES}}
+{{/if}}
 
 **If Linear was selected:**
 
 2. **Linear Team ID** (only ask if issue provider is "linear")
-   - Question format: "What is your Linear team ID/key?{{#IF currentLinearTeamId}} (Currently: [currentLinearTeamId]){{/IF currentLinearTeamId}}"
+   - Question format: "What is your Linear team ID/key?{{#if currentLinearTeamId}} (Currently: [currentLinearTeamId]){{/if}}"
    - Options (as examples):
      - "ENG" - Engineering team
      - "PLAT" - Platform team
@@ -840,7 +882,7 @@ REMOTES_INFO
 **Step 3: IDE Selection**
 
 4. **IDE Selection**
-   - Question format: "Which IDE should iloom launch when starting a loom?{{#IF currentIdeType}} (Currently: [currentIdeType]){{/IF currentIdeType}}"
+   - Question format: "Which IDE should iloom launch when starting a loom?{{#if currentIdeType}} (Currently: [currentIdeType]){{/if}}"
    - Options:
      - "vscode" - Visual Studio Code (default)
      - "cursor" - Cursor AI editor
@@ -857,7 +899,7 @@ REMOTES_INFO
 **Step 4: Merge Mode** (only ask if multiple remotes detected OR user requests advanced config)
 
 5. **Merge Mode**
-   - Question format: "How should iloom handle finishing work?{{#IF currentMergeMode}} (Currently: [currentMergeMode]){{/IF currentMergeMode}}"
+   - Question format: "How should iloom handle finishing work?{{#if currentMergeMode}} (Currently: [currentMergeMode]){{/if}}"
    - Options:
      - "local" - Merge changes locally (traditional workflow)
      - "github-pr" - Create GitHub PR when finishing (for PR-based workflows)
@@ -884,7 +926,7 @@ REMOTES_INFO
 
 After Phase 2, handle color settings based on gitignore status.
 
-Analyis of system: Is VSCode Settings ignore? VSCODE_SETTINGS_GITIGNORED
+Analyis of system: Is VSCode Settings ignore? {{VSCODE_SETTINGS_GITIGNORED}}
 
 **IMPORTANT DISTINCTION:**
 - Schema defaults are: terminal=true, vscode=false (for safety)
@@ -932,7 +974,7 @@ Tooling Configuration (Phase 2):
   Issue Tracker: [value]
   Linear Team ID: [value] (only if issue tracker is Linear)
   Linear API Token: [configured/not configured] (only if issue tracker is Linear - never show actual token)
-  {{#IF MULTIPLE_REMOTES}}GitHub Remote: [value] (only if issue tracker is GitHub){{/IF MULTIPLE_REMOTES}}
+  {{#if MULTIPLE_REMOTES}}GitHub Remote: [value] (only if issue tracker is GitHub){{/if}}
   IDE: [value or "vscode (default)"]
   Merge Mode: [value] (only if configured)
 ```
@@ -948,7 +990,7 @@ Then ask: "Does this configuration look correct?"
 
 ### Phase 4: Choose Configuration File
 
-**Fork/Contributor Check:** If "GitHub Remote Configuration" shows both "origin" and "upstream" remotes (classic fork pattern), display: "It looks like you're working on a fork (origin + upstream remotes detected). For contributors, we recommend saving to settings.local.json to avoid including personal settings in PRs to upstream, but you can still choose shared if needed."
+**Fork/Contributor Check:** If "GitHub Remote Configuration" shows both "origin" and "upstream" remotes (classic fork pattern), display: "**FORK DETECTED**: You're working on a fork (origin + upstream remotes detected). **ALL configuration settings should be saved to settings.local.json** to avoid polluting the upstream repository with your personal settings. When you submit PRs to upstream, only your code changes should be included - not iloom configuration. The Local option below is strongly recommended."
 
 **CRITICAL: You MUST ask the user where to save the configuration. DO NOT make assumptions or decide for them.**
 
@@ -962,7 +1004,7 @@ Ask the user: "Where should this configuration be saved?
 - **Recommend Project for**: Main branch, worktree prefix, base port (when standardized for the team)
 - **Recommend Local for**: Machine-specific overrides, personal preferences that differ from team defaults
 
-**Fork/Contributor Note:** For fork setups, recommend Local over Project to avoid including personal settings in PRs to upstream.
+**Fork/Contributor Note:** For fork setups, **ALL settings should go to Local (settings.local.json)**, not Project. This prevents your personal iloom configuration from being included in PRs to the upstream repository. Even settings like mainBranch or basePort should be stored locally in fork scenarios to keep your contributions clean.
 
 **DO NOT:**
 - Assume what the user wants based on the type of setting
@@ -1390,6 +1432,32 @@ If users ask about specific configurations, help them add these sections to thei
    - Running additional commands before/after the standard npm scripts
    - Wrapping commands with environment variables or tools
 
+   **Local Overrides for Fork Contributors:**
+
+   If you're contributing to a forked repository, save your customizations to `.iloom/package.iloom.local.json` instead of `package.iloom.json`. This file:
+   - Is automatically added to global gitignore (won't appear in PRs)
+   - Merges with package.iloom.json (local scripts override base scripts)
+   - Is automatically copied to new looms
+
+   **When to use each file:**
+   - `package.iloom.json` - Shared team configuration, committed to git
+   - `package.iloom.local.json` - Personal overrides, never committed (gitignored globally)
+
+   Example `.iloom/package.iloom.local.json`:
+   ```json
+   {
+     "scripts": {
+       "test": "pytest --my-local-options",
+       "dev": "python -m mymodule --debug"
+     }
+   }
+   ```
+
+   This is especially useful when:
+   - Working on a fork where upstream has different script requirements
+   - Your local environment needs different commands than the team standard
+   - You want to add debug flags or local-only tooling without affecting others
+
 ## Important Notes
 
 - **Validate ALL inputs** against the schema before writing files