@iloom/cli 0.7.6 → 0.8.1

package/dist/{recap-ZKGHZCX6.js → recap-GSXFEOD6.js}

@@ -4,13 +4,13 @@ import {
 } from "./chunk-NXMDEL3F.js";
 import {
   IdentifierParser
-} from "./chunk-5V74K5ZA.js";
+} from "./chunk-TVH67KEO.js";
 import {
   GitWorktreeManager
-} from "./chunk-UDRZY65Y.js";
-import "./chunk-ZA575VLF.js";
-import "./chunk-WFQ5CLTR.js";
-import "./chunk-VWGKGNJP.js";
+} from "./chunk-HSGZW3ID.js";
+import "./chunk-GDS2HXSW.js";
+import "./chunk-IWIIOFEB.js";
+import "./chunk-KBEIQP4G.js";
 import "./chunk-6MLEBAYZ.js";
 import "./chunk-VT4PDUYT.js";
 
@@ -107,4 +107,4 @@ var RecapCommand = class {
 export {
   RecapCommand
 };
-//# sourceMappingURL=recap-ZKGHZCX6.js.map
+//# sourceMappingURL=recap-GSXFEOD6.js.map

package/dist/{run-QEIS2EH2.js → run-XPGCMFFO.js}

@@ -1,21 +1,21 @@
 #!/usr/bin/env node
 import {
   DevServerManager
-} from "./chunk-ENMTWE74.js";
-import "./chunk-WZYBHD7P.js";
+} from "./chunk-VZYSM7N7.js";
+import "./chunk-XHNACIHO.js";
 import {
   getWorkspacePort
-} from "./chunk-CFQVOTHO.js";
+} from "./chunk-52MVUK5V.js";
 import {
   IdentifierParser
-} from "./chunk-5V74K5ZA.js";
+} from "./chunk-TVH67KEO.js";
 import {
   ProjectCapabilityDetector
 } from "./chunk-7GLZVDPQ.js";
 import "./chunk-RD7I2Q2F.js";
 import {
   GitWorktreeManager
-} from "./chunk-UDRZY65Y.js";
+} from "./chunk-HSGZW3ID.js";
 import "./chunk-XPKN3QWY.js";
 import {
   openBrowser
@@ -25,11 +25,11 @@ import {
 } from "./chunk-GYCR2LOU.js";
 import {
   extractIssueNumber
-} from "./chunk-ZA575VLF.js";
+} from "./chunk-GDS2HXSW.js";
 import {
   SettingsManager
-} from "./chunk-WFQ5CLTR.js";
-import "./chunk-VWGKGNJP.js";
+} from "./chunk-IWIIOFEB.js";
+import "./chunk-KBEIQP4G.js";
 import "./chunk-6MLEBAYZ.js";
 import {
   logger
@@ -238,4 +238,4 @@ Make sure the project is built (run 'il start' first)`
 export {
   RunCommand
 };
-//# sourceMappingURL=run-QEIS2EH2.js.map
+//# sourceMappingURL=run-XPGCMFFO.js.map

package/dist/schema/settings.schema.json

@@ -196,6 +196,24 @@
                           "haiku"
                         ],
                         "description": "Claude model shorthand: sonnet, opus, or haiku"
+                      },
+                      "enabled": {
+                        "type": "boolean",
+                        "description": "Whether this agent is enabled. Defaults to true."
+                      },
+                      "providers": {
+                        "type": "object",
+                        "additionalProperties": {
+                          "type": "string"
+                        },
+                        "propertyNames": {
+                          "enum": [
+                            "claude",
+                            "gemini",
+                            "codex"
+                          ]
+                        },
+                        "description": "Map of review providers to model names. Keys: claude, gemini, codex. Values: model name strings (e.g., \"sonnet\", \"gemini-3-pro-preview\", \"gpt-5.2-codex\")"
                       }
                     },
                     "additionalProperties": false
@@ -207,7 +225,7 @@
               "type": "null"
             }
           ],
-          "description": "Per-agent configuration overrides. Available agents: iloom-issue-analyzer (analyzes issues), iloom-issue-planner (creates implementation plans), iloom-issue-analyze-and-plan (combined analysis and planning), iloom-issue-complexity-evaluator (evaluates complexity), iloom-issue-enhancer (enhances issue descriptions), iloom-issue-implementer (implements code changes), iloom-issue-reviewer (reviews code changes against requirements)"
+          "description": "Per-agent configuration overrides. Available agents: iloom-issue-analyzer (analyzes issues), iloom-issue-planner (creates implementation plans), iloom-issue-analyze-and-plan (combined analysis and planning), iloom-issue-complexity-evaluator (evaluates complexity), iloom-issue-enhancer (enhances issue descriptions), iloom-issue-implementer (implements code changes), iloom-code-reviewer (reviews code changes against requirements)"
         },
         "spin": {
           "type": "object",
@@ -226,6 +244,44 @@
           "additionalProperties": false,
           "description": "Spin orchestrator configuration. Model defaults to opus when not configured."
         },
+        "plan": {
+          "type": "object",
+          "properties": {
+            "model": {
+              "type": "string",
+              "enum": [
+                "sonnet",
+                "opus",
+                "haiku"
+              ],
+              "default": "opus",
+              "description": "Claude model shorthand for plan command"
+            },
+            "planner": {
+              "type": "string",
+              "enum": [
+                "claude",
+                "gemini",
+                "codex"
+              ],
+              "default": "claude",
+              "description": "AI provider for creating the plan"
+            },
+            "reviewer": {
+              "type": "string",
+              "enum": [
+                "claude",
+                "gemini",
+                "codex",
+                "none"
+              ],
+              "default": "none",
+              "description": "AI provider for reviewing the plan (none to skip review)"
+            }
+          },
+          "additionalProperties": false,
+          "description": "Plan command configuration. Model defaults to opus, planner to claude, reviewer to none when not configured."
+        },
         "summary": {
           "type": "object",
           "properties": {

package/dist/{shell-2NNSIU34.js → shell-2SPM3Z5O.js}

@@ -1,17 +1,17 @@
 #!/usr/bin/env node
 import {
   IdentifierParser
-} from "./chunk-5V74K5ZA.js";
+} from "./chunk-TVH67KEO.js";
 import {
   GitWorktreeManager
-} from "./chunk-UDRZY65Y.js";
+} from "./chunk-HSGZW3ID.js";
 import {
   extractIssueNumber
-} from "./chunk-ZA575VLF.js";
+} from "./chunk-GDS2HXSW.js";
 import {
   SettingsManager
-} from "./chunk-WFQ5CLTR.js";
-import "./chunk-VWGKGNJP.js";
+} from "./chunk-IWIIOFEB.js";
+import "./chunk-KBEIQP4G.js";
 import "./chunk-6MLEBAYZ.js";
 import {
   getDotenvFlowFiles,
@@ -235,4 +235,4 @@ var ShellCommand = class {
 export {
   ShellCommand
 };
-//# sourceMappingURL=shell-2NNSIU34.js.map
+//# sourceMappingURL=shell-2SPM3Z5O.js.map

package/dist/{summary-MPOOQIOX.js → summary-C5VVSJAJ.js}

@@ -1,29 +1,29 @@
 #!/usr/bin/env node
 import {
   SessionSummaryService
-} from "./chunk-WT4UGBE2.js";
+} from "./chunk-PBSHQVCT.js";
 import "./chunk-NXMDEL3F.js";
 import {
   GitWorktreeManager
-} from "./chunk-UDRZY65Y.js";
+} from "./chunk-HSGZW3ID.js";
 import {
   PRManager
-} from "./chunk-6YAMWLCP.js";
+} from "./chunk-EQOFNPEY.js";
 import "./chunk-YETJNRQM.js";
-import "./chunk-NPEMVE27.js";
-import "./chunk-HBJITKSZ.js";
+import "./chunk-UDZCTLD6.js";
+import "./chunk-RNBIISBZ.js";
 import "./chunk-FXDYIV3K.js";
-import "./chunk-TIYJEEVO.js";
+import "./chunk-66QOCD5N.js";
 import {
   extractIssueNumber
-} from "./chunk-ZA575VLF.js";
+} from "./chunk-GDS2HXSW.js";
 import {
   SettingsManager
-} from "./chunk-WFQ5CLTR.js";
+} from "./chunk-IWIIOFEB.js";
 import {
   MetadataManager
-} from "./chunk-VWGKGNJP.js";
-import "./chunk-GCPAZSGV.js";
+} from "./chunk-KBEIQP4G.js";
+import "./chunk-THS5L54H.js";
 import "./chunk-IGKPPACU.js";
 import {
   getLogger
@@ -280,4 +280,4 @@ Please provide an issue number, PR number, or branch name.`
 export {
   SummaryCommand
 };
-//# sourceMappingURL=summary-MPOOQIOX.js.map
+//# sourceMappingURL=summary-C5VVSJAJ.js.map

package/dist/{test-75WAA6DU.js → test-N2725YRI.js}

@@ -1,14 +1,14 @@
 #!/usr/bin/env node
 import {
   ScriptCommandBase
-} from "./chunk-ELJKYFSH.js";
-import "./chunk-5V74K5ZA.js";
+} from "./chunk-BCQDYAOJ.js";
+import "./chunk-TVH67KEO.js";
 import "./chunk-RD7I2Q2F.js";
-import "./chunk-UDRZY65Y.js";
+import "./chunk-HSGZW3ID.js";
 import "./chunk-XPKN3QWY.js";
-import "./chunk-ZA575VLF.js";
-import "./chunk-WFQ5CLTR.js";
-import "./chunk-VWGKGNJP.js";
+import "./chunk-GDS2HXSW.js";
+import "./chunk-IWIIOFEB.js";
+import "./chunk-KBEIQP4G.js";
 import "./chunk-6MLEBAYZ.js";
 import "./chunk-VT4PDUYT.js";
 
@@ -24,4 +24,4 @@ var TestCommand = class extends ScriptCommandBase {
 export {
   TestCommand
 };
-//# sourceMappingURL=test-75WAA6DU.js.map
+//# sourceMappingURL=test-N2725YRI.js.map

package/dist/{test-git-E2BLXR6M.js → test-git-ZPSPA2TP.js}

@@ -1,11 +1,11 @@
 #!/usr/bin/env node
 import {
   findMainWorktreePath
-} from "./chunk-ZA575VLF.js";
+} from "./chunk-GDS2HXSW.js";
 import {
   SettingsManager
-} from "./chunk-WFQ5CLTR.js";
-import "./chunk-VWGKGNJP.js";
+} from "./chunk-IWIIOFEB.js";
+import "./chunk-KBEIQP4G.js";
 import "./chunk-6MLEBAYZ.js";
 import {
   logger
@@ -51,4 +51,4 @@ var TestGitCommand = class {
 export {
   TestGitCommand
 };
-//# sourceMappingURL=test-git-E2BLXR6M.js.map
+//# sourceMappingURL=test-git-ZPSPA2TP.js.map

package/dist/{test-prefix-A7JGGYAA.js → test-prefix-6DLB2BHE.js}

@@ -1,11 +1,11 @@
 #!/usr/bin/env node
 import {
   generateWorktreePath
-} from "./chunk-ZA575VLF.js";
+} from "./chunk-GDS2HXSW.js";
 import {
   SettingsManager
-} from "./chunk-WFQ5CLTR.js";
-import "./chunk-VWGKGNJP.js";
+} from "./chunk-IWIIOFEB.js";
+import "./chunk-KBEIQP4G.js";
 import "./chunk-6MLEBAYZ.js";
 import {
   logger
@@ -67,4 +67,4 @@ var TestPrefixCommand = class {
 export {
   TestPrefixCommand
 };
-//# sourceMappingURL=test-prefix-A7JGGYAA.js.map
+//# sourceMappingURL=test-prefix-6DLB2BHE.js.map

package/dist/{test-webserver-J6SMNLU2.js → test-webserver-XLJ2TZFP.js}

@@ -1,13 +1,13 @@
 #!/usr/bin/env node
 import {
   ProcessManager
-} from "./chunk-WZYBHD7P.js";
-import "./chunk-CFQVOTHO.js";
-import "./chunk-ZA575VLF.js";
+} from "./chunk-XHNACIHO.js";
+import "./chunk-52MVUK5V.js";
+import "./chunk-GDS2HXSW.js";
 import {
   SettingsManager
-} from "./chunk-WFQ5CLTR.js";
-import "./chunk-VWGKGNJP.js";
+} from "./chunk-IWIIOFEB.js";
+import "./chunk-KBEIQP4G.js";
 import "./chunk-6MLEBAYZ.js";
 import {
   logger
@@ -81,4 +81,4 @@ var TestWebserverCommand = class {
 export {
   TestWebserverCommand
 };
-//# sourceMappingURL=test-webserver-J6SMNLU2.js.map
+//# sourceMappingURL=test-webserver-XLJ2TZFP.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iloom/cli",
-  "version": "0.7.6",
+  "version": "0.8.1",
   "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",

package/dist/GitHubService-O7U4UQ7N.js

@@ -1,12 +0,0 @@
-#!/usr/bin/env node
-import {
-  GitHubService
-} from "./chunk-USJSNHGG.js";
-import "./chunk-GCPAZSGV.js";
-import "./chunk-ZX3GTM7O.js";
-import "./chunk-6MLEBAYZ.js";
-import "./chunk-VT4PDUYT.js";
-export {
-  GitHubService
-};
-//# sourceMappingURL=GitHubService-O7U4UQ7N.js.map

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

@@ -1,139 +0,0 @@
----
-name: iloom-issue-reviewer
-description: Use this agent when you need to review uncommitted code changes against a specific issue to verify completeness and quality. The agent will analyze the issue requirements, examine the code changes, and post a detailed review comment directly on the issue. Examples:\n\n<example>\nContext: The user has made code changes to address an issue and wants to verify the implementation before committing.\nuser: "I've finished implementing the fix for issue #42, can you review it?"\nassistant: "I'll use the Task tool to launch the iloom-issue-reviewer agent to analyze your changes against issue #42."\n<commentary>\nSince the user has completed work on an issue and wants a review, use the iloom-issue-reviewer agent to verify the implementation.\n</commentary>\n</example>\n\n<example>\nContext: The user wants to ensure their changes fully address all requirements in an issue.\nuser: "Check if my changes properly solve issue #15"\nassistant: "Let me use the iloom-issue-reviewer agent to verify your implementation against issue #15's requirements."\n<commentary>\nThe user is asking for verification that their code changes meet the issue requirements, so use the iloom-issue-reviewer agent.\n</commentary>\n</example>
-tools: Bash, Glob, Grep, Read, Edit, Write, NotebookEdit, WebFetch, TodoWrite, WebSearch, BashOutput, SlashCommand, ListMcpResourcesTool, ReadMcpResourceTool, mcp__context7__resolve-library-id, mcp__context7__get-library-docs, mcp__issue_management__get_issue, mcp__issue_management__get_pr, mcp__issue_management__get_comment, mcp__issue_management__create_comment, mcp__issue_management__update_comment, mcp__recap__get_recap, mcp__recap__add_entry, mcp__recap__add_artifact
-model: sonnet
-color: cyan
----
-
-You are an expert code reviewer specializing in issue verification. Your primary responsibility is to thoroughly analyze uncommitted code changes against their corresponding issue requirements and provide comprehensive feedback. Ultrathink as you execute the following.
-
-## Loom Recap
-
-After creating or updating any issue comment, use the Recap MCP tools:
-- `recap.add_artifact` - Log comments with type='comment', primaryUrl (full URL with comment ID), and description. Re-calling with the same primaryUrl will update the existing entry.
-
-This enables the recap panel to show quick-reference links to artifacts created during the session.
-
-**Core Responsibilities:**
-
-1. **Issue Analysis**: You will first retrieve and carefully read the entire issue using the MCP tool `mcp__issue_management__get_issue` with parameters `{ number: {{ISSUE_NUMBER}}, includeComments: true }`. Extract all requirements, acceptance criteria, and context from both the issue body and all comments. Pay special attention to any clarifications or requirement changes mentioned in the comment thread. If no issue number has been provided, use the current branch name to look for an issue number (i.e issue-NN). If there is a pr_NN suffix, look at both the PR and the issue (if one is also referenced in the branch name).
-
-2. **Code Review Process**: You will examine the uncommitted changes using `git diff` and `git status`. Analyze each change against the issue requirements with deep critical thinking. Consider:
-   - Does the implementation fully address all stated requirements?
-   - Are there any edge cases mentioned in the issue that aren't handled?
-   - Is the code quality appropriate (following project patterns from any CLAUDE.md context)?
-   - Are there any unintended side effects or regressions?
-   - Does the solution align with the architectural decisions discussed in the issue?
-
-3. **Verification Methodology**: You will:
-   - Create a mental checklist of all requirements from the issue
-   - Map each requirement to specific code changes
-   - Identify any gaps between requirements and implementation
-   - Assess code quality, maintainability, and adherence to project standards
-   - Consider performance implications if relevant to the issue
-
-4. **Comment Composition**: You will write your review as a structured issue comment that includes:
-   - A summary verdict (e.g., "✅ Implementation Complete" or "⚠️ Partial Implementation")
-   - A requirement-by-requirement breakdown showing what was addressed
-   - Specific observations about code quality and implementation choices
-   - Any concerns, missing pieces, or suggestions for improvement
-   - Positive acknowledgment of well-implemented aspects
-   - IMPORTANT: When including code excerpts or diffs >5 lines, wrap in `<details>/<summary>` tags with format: "Click to expand [type] ([N] lines) - [context]"
-
-5. **Technical Execution**: To post your comment, you will use the MCP tool `mcp__issue_management__create_comment` with parameters `{ number: {{ISSUE_NUMBER}}, body: "your review content", type: "issue" }`. This approach properly handles markdown content and works across different issue tracking systems.
-
-<comment_tool_info>
-IMPORTANT: You have been provided with MCP tools for issue management during this workflow.
-
-Available Tools:
-- mcp__issue_management__get_issue: Fetch issue details
-  Parameters: { number: string, includeComments?: boolean }
-  Returns: { title, body, comments, labels, assignees, state, ... }
-
-- mcp__issue_management__get_comment: Fetch a specific comment
-  Parameters: { commentId: string, number: string }
-  Returns: { id, body, author, created_at, ... }
-
-{{#if DRAFT_PR_MODE}}- mcp__issue_management__create_comment: Create a new comment on PR {{DRAFT_PR_NUMBER}}
-  Parameters: { number: string, body: "markdown content", type: "pr" }{{/if}}{{#if STANDARD_ISSUE_MODE}}- mcp__issue_management__create_comment: Create a new comment on issue {{ISSUE_NUMBER}}
-  Parameters: { number: string, body: "markdown content", type: "issue" }{{/if}}
-  Returns: { id: string, url: string, created_at: string }
-
-- mcp__issue_management__update_comment: Update an existing comment
-  Parameters: { commentId: string, number: string, body: "updated markdown content" }
-  Returns: { id: string, url: string, updated_at: string }
-
-Workflow Comment Strategy:
-1. When beginning review, create a NEW comment informing the user you are working on reviewing 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., "Code review comment").
-3. Once you have formulated your review tasks in a todo format, update the comment using mcp__issue_management__update_comment with your tasks formatted as checklists using markdown:
-   - [ ] for incomplete tasks (which should be all of them at this point)
-4. After you complete every todo item, update the comment using mcp__issue_management__update_comment with your progress - you may add todo items if you need:
-   - [ ] for incomplete tasks
-   - [x] for completed tasks
-
-   * 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.
-
-Example Usage:
-```
-// Start
-{{#if DRAFT_PR_MODE}}const comment = await mcp__issue_management__create_comment({
-  number: {{DRAFT_PR_NUMBER}},
-  body: "# Code Review Phase\n\n- [ ] Fetch issue details\n- [ ] Analyze requirements\n- [ ] Review code changes",
-  type: "pr"
-}){{/if}}{{#if STANDARD_ISSUE_MODE}}const comment = await mcp__issue_management__create_comment({
-  number: {{ISSUE_NUMBER}},
-  body: "# Code Review Phase\n\n- [ ] Fetch issue details\n- [ ] Analyze requirements\n- [ ] Review code changes",
-  type: "issue"
-}){{/if}}
-
-// Log the comment as an artifact
-await mcp__recap__add_artifact({
-  type: "comment",
-  primaryUrl: comment.url,
-  description: "Code review comment"
-})
-
-// Update as you progress
-{{#if DRAFT_PR_MODE}}await mcp__issue_management__update_comment({
-  commentId: comment.id,
-  number: {{DRAFT_PR_NUMBER}},
-  body: "# Code Review Phase\n\n- [x] Fetch issue details\n- [ ] Analyze requirements\n- [ ] Review code changes"
-}){{/if}}{{#if STANDARD_ISSUE_MODE}}await mcp__issue_management__update_comment({
-  commentId: comment.id,
-  number: {{ISSUE_NUMBER}},
-  body: "# Code Review Phase\n\n- [x] Fetch issue details\n- [ ] Analyze requirements\n- [ ] Review code changes"
-}){{/if}}
-```
-</comment_tool_info>
-
-**Quality Standards:**
-- Be thorough but concise - every observation should add value
-- Use specific code references when pointing out issues
-- Maintain a constructive, professional tone
-- Acknowledge good implementation decisions, not just problems
-- If the implementation is incomplete, clearly state what remains to be done
-- If you notice improvements beyond the issue scope, mention them as "future considerations"
-
-**Decision Framework:**
-When evaluating completeness:
-- ✅ Complete: All requirements met, code quality good, no significant issues
-- ⚠️ Mostly Complete: Core requirements met but minor items missing or quality concerns
-- ❌ Incomplete: Major requirements unaddressed or significant issues present
-
-**Important Notes:**
-- Always think critically and deeply about the context before making judgments
-- If the issue references other issues or PRs, consider checking those for additional context
-- Never assume implementation details not explicitly shown in the diff
-- If you cannot access the issue or code, clearly state this limitation
-- Focus on uncommitted changes only - do not review the entire codebase unless specifically requested
-
-## HOW TO UPDATE THE USER OF YOUR PROGRESS
-* AS SOON AS YOU CAN, once you have formulated an initial plan/todo list for your review 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 your complete review. 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.
-
-Your review should help the developer understand exactly where their implementation stands relative to the issue requirements and what, if anything, needs additional work.

package/dist/chunk-5V74K5ZA.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../src/utils/IdentifierParser.ts"],"sourcesContent":["import type { ParsedInput } from '../commands/start.js'\nimport type { GitWorktreeManager } from '../lib/GitWorktreeManager.js'\nimport { extractIssueNumber, extractPRNumber } from './git.js'\n\n/**\n * IdentifierParser provides consistent identifier parsing across commands\n * using pattern-based detection without GitHub API calls.\n *\n * Detection Strategy:\n * 1. For numeric input (e.g., \"42\", \"#66\"):\n *    - Check for PR worktree first (_pr_N pattern in path)\n *    - Then check for issue worktree (issue-N pattern in branch)\n * 2. For alphanumeric input (e.g., \"ENG-123\"):\n *    - Check for issue worktree with alphanumeric identifier\n * 3. For branch-style input (e.g., \"feat/issue-42__description\", \"pr/123\"):\n *    - Find matching worktree by branch name\n *    - Extract PR number from branch name if present (priority)\n *    - Extract issue number from branch name if present\n *    - Return as PR/issue type if number found, otherwise branch type\n *\n * This ensures:\n * - No unnecessary GitHub API calls\n * - Consistent behavior across finish/cleanup commands\n * - PR detection takes priority over issue detection\n * - Issue numbers are extracted from branch names for \"Fixes #N\" commit trailers\n */\nexport class IdentifierParser {\n\tconstructor(private gitWorktreeManager: GitWorktreeManager) {}\n\n\t/**\n\t * Parse identifier using pattern-based detection on existing worktrees.\n\t * Does NOT make GitHub API calls - only checks local worktree patterns.\n\t *\n\t * @param identifier - The identifier to parse (e.g., \"42\", \"#66\", \"ENG-123\", \"my-branch\")\n\t * @returns ParsedInput with type, number/branchName, and originalInput\n\t * @throws Error if no matching worktree is found\n\t */\n\tasync parseForPatternDetection(identifier: string): Promise<ParsedInput> {\n\t\t// Remove # prefix if present and trim whitespace\n\t\tconst cleanId = identifier.replace(/^#/, '').trim()\n\t\tconst originalInput = identifier\n\n\t\t// Check if input is numeric (GitHub-style issue/PR numbers)\n\t\tconst numericMatch = cleanId.match(/^(\\d+)$/)\n\n\t\tif (numericMatch?.[1]) {\n\t\t\tconst number = parseInt(numericMatch[1], 10)\n\n\t\t\t// Priority 1: Check for PR worktree (_pr_N pattern)\n\t\t\t// Pass empty string for branch name since we don't know it yet\n\t\t\tconst prWorktree = await this.gitWorktreeManager.findWorktreeForPR(number, '')\n\t\t\tif (prWorktree) {\n\t\t\t\treturn {\n\t\t\t\t\ttype: 'pr',\n\t\t\t\t\tnumber,\n\t\t\t\t\toriginalInput,\n\t\t\t\t}\n\t\t\t}\n\n\t\t\t// Priority 2: Check for issue worktree (issue-N pattern)\n\t\t\tconst issueWorktree = await this.gitWorktreeManager.findWorktreeForIssue(number)\n\t\t\tif (issueWorktree) {\n\t\t\t\treturn {\n\t\t\t\t\ttype: 'issue',\n\t\t\t\t\tnumber,\n\t\t\t\t\toriginalInput,\n\t\t\t\t}\n\t\t\t}\n\n\t\t\t// No matching worktree found for numeric input\n\t\t\tthrow new Error(`No worktree found for identifier: ${identifier}`)\n\t\t}\n\n\t\t// Check if input is alphanumeric issue identifier (Linear/Jira-style: ABC-123, ENG-42)\n\t\tconst alphanumericMatch = cleanId.match(/^([A-Za-z]+-\\d+)$/)\n\n\t\tif (alphanumericMatch?.[1]) {\n\t\t\tconst alphanumericId = alphanumericMatch[1]\n\n\t\t\t// Check for issue worktree with alphanumeric identifier\n\t\t\tconst issueWorktree = await this.gitWorktreeManager.findWorktreeForIssue(alphanumericId)\n\t\t\tif (issueWorktree) {\n\t\t\t\treturn {\n\t\t\t\t\ttype: 'issue',\n\t\t\t\t\tnumber: alphanumericId,\n\t\t\t\t\toriginalInput,\n\t\t\t\t}\n\t\t\t}\n\n\t\t\t// No matching worktree found for alphanumeric identifier\n\t\t\tthrow new Error(`No worktree found for identifier: ${identifier}`)\n\t\t}\n\n\t\t// Non-numeric/non-alphanumeric input: treat as branch name\n\t\tconst branchWorktree = await this.gitWorktreeManager.findWorktreeForBranch(cleanId)\n\t\tif (branchWorktree) {\n\t\t\t// Priority 1: Check for PR pattern in the input\n\t\t\tconst prFromBranch = extractPRNumber(cleanId)\n\t\t\tif (prFromBranch !== null) {\n\t\t\t\treturn {\n\t\t\t\t\ttype: 'pr',\n\t\t\t\t\tnumber: prFromBranch,\n\t\t\t\t\toriginalInput,\n\t\t\t\t}\n\t\t\t}\n\n\t\t\t// Priority 2: Try to extract issue number from branch name\n\t\t\t// This handles cases like \"feat/issue-42__description\" passed as explicit input\n\t\t\tconst issueFromBranch = extractIssueNumber(cleanId)\n\t\t\tif (issueFromBranch !== null) {\n\t\t\t\treturn {\n\t\t\t\t\ttype: 'issue',\n\t\t\t\t\tnumber: issueFromBranch,\n\t\t\t\t\toriginalInput,\n\t\t\t\t}\n\t\t\t}\n\n\t\t\treturn {\n\t\t\t\ttype: 'branch',\n\t\t\t\tbranchName: cleanId,\n\t\t\t\toriginalInput,\n\t\t\t}\n\t\t}\n\n\t\t// No matching worktree found for branch name\n\t\tthrow new Error(`No worktree found for identifier: ${identifier}`)\n\t}\n}\n"],"mappings":";;;;;;;AA0BO,IAAM,mBAAN,MAAuB;AAAA,EAC7B,YAAoB,oBAAwC;AAAxC;AAAA,EAAyC;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAU7D,MAAM,yBAAyB,YAA0C;AAExE,UAAM,UAAU,WAAW,QAAQ,MAAM,EAAE,EAAE,KAAK;AAClD,UAAM,gBAAgB;AAGtB,UAAM,eAAe,QAAQ,MAAM,SAAS;AAE5C,QAAI,6CAAe,IAAI;AACtB,YAAM,SAAS,SAAS,aAAa,CAAC,GAAG,EAAE;AAI3C,YAAM,aAAa,MAAM,KAAK,mBAAmB,kBAAkB,QAAQ,EAAE;AAC7E,UAAI,YAAY;AACf,eAAO;AAAA,UACN,MAAM;AAAA,UACN;AAAA,UACA;AAAA,QACD;AAAA,MACD;AAGA,YAAM,gBAAgB,MAAM,KAAK,mBAAmB,qBAAqB,MAAM;AAC/E,UAAI,eAAe;AAClB,eAAO;AAAA,UACN,MAAM;AAAA,UACN;AAAA,UACA;AAAA,QACD;AAAA,MACD;AAGA,YAAM,IAAI,MAAM,qCAAqC,UAAU,EAAE;AAAA,IAClE;AAGA,UAAM,oBAAoB,QAAQ,MAAM,mBAAmB;AAE3D,QAAI,uDAAoB,IAAI;AAC3B,YAAM,iBAAiB,kBAAkB,CAAC;AAG1C,YAAM,gBAAgB,MAAM,KAAK,mBAAmB,qBAAqB,cAAc;AACvF,UAAI,eAAe;AAClB,eAAO;AAAA,UACN,MAAM;AAAA,UACN,QAAQ;AAAA,UACR;AAAA,QACD;AAAA,MACD;AAGA,YAAM,IAAI,MAAM,qCAAqC,UAAU,EAAE;AAAA,IAClE;AAGA,UAAM,iBAAiB,MAAM,KAAK,mBAAmB,sBAAsB,OAAO;AAClF,QAAI,gBAAgB;AAEnB,YAAM,eAAe,gBAAgB,OAAO;AAC5C,UAAI,iBAAiB,MAAM;AAC1B,eAAO;AAAA,UACN,MAAM;AAAA,UACN,QAAQ;AAAA,UACR;AAAA,QACD;AAAA,MACD;AAIA,YAAM,kBAAkB,mBAAmB,OAAO;AAClD,UAAI,oBAAoB,MAAM;AAC7B,eAAO;AAAA,UACN,MAAM;AAAA,UACN,QAAQ;AAAA,UACR;AAAA,QACD;AAAA,MACD;AAEA,aAAO;AAAA,QACN,MAAM;AAAA,QACN,YAAY;AAAA,QACZ;AAAA,MACD;AAAA,IACD;AAGA,UAAM,IAAI,MAAM,qCAAqC,UAAU,EAAE;AAAA,EAClE;AACD;","names":[]}