@iloom/cli 0.5.5 → 0.6.1

package/dist/{init-XQQGC6DN.js → init-UTYRHNJJ.js}

@@ -1,12 +1,13 @@
 #!/usr/bin/env node
 import {
   InitCommand
-} from "./chunk-WZHBRKLN.js";
-import "./chunk-NKRQNER7.js";
+} from "./chunk-LVBRMTE6.js";
+import "./chunk-Q7POFB5Q.js";
 import "./chunk-F2PWIRV4.js";
+import "./chunk-SN3Z6EZO.js";
 import "./chunk-EK3XCAAS.js";
 import "./chunk-FXDYIV3K.js";
-import "./chunk-K5G5SFWY.js";
+import "./chunk-W6WVRHJ6.js";
 import "./chunk-GEXP5IOF.js";
 import "./chunk-F6WVM437.js";
 import "./chunk-CFUWQHCJ.js";
@@ -17,4 +18,4 @@ import "./chunk-VT4PDUYT.js";
 export {
   InitCommand
 };
-//# sourceMappingURL=init-XQQGC6DN.js.map
+//# sourceMappingURL=init-UTYRHNJJ.js.map

package/dist/lint-5JMCWE4Y.js

@@ -0,0 +1,27 @@
+#!/usr/bin/env node
+import {
+  ScriptCommandBase
+} from "./chunk-TRQ76ISK.js";
+import "./chunk-AXX3QIKK.js";
+import "./chunk-UQIXZ3BA.js";
+import "./chunk-BXCPJJYM.js";
+import "./chunk-EK3XCAAS.js";
+import "./chunk-GEXP5IOF.js";
+import "./chunk-F6WVM437.js";
+import "./chunk-CFUWQHCJ.js";
+import "./chunk-6MLEBAYZ.js";
+import "./chunk-VT4PDUYT.js";
+
+// src/commands/lint.ts
+var LintCommand = class extends ScriptCommandBase {
+  getScriptName() {
+    return "lint";
+  }
+  getScriptDisplayName() {
+    return "Lint";
+  }
+};
+export {
+  LintCommand
+};
+//# sourceMappingURL=lint-5JMCWE4Y.js.map

package/dist/lint-5JMCWE4Y.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/commands/lint.ts"],"sourcesContent":["import { ScriptCommandBase, ScriptCommandInput } from './script-command-base.js'\n\nexport type { ScriptCommandInput as LintCommandInput }\n\n/**\n * LintCommand - Run the lint script for a workspace\n * Uses package.iloom.json if available, otherwise falls back to package.json\n */\nexport class LintCommand extends ScriptCommandBase {\n\tgetScriptName(): string {\n\t\treturn 'lint'\n\t}\n\n\tgetScriptDisplayName(): string {\n\t\treturn 'Lint'\n\t}\n}\n"],"mappings":";;;;;;;;;;;;;;;AAQO,IAAM,cAAN,cAA0B,kBAAkB;AAAA,EAClD,gBAAwB;AACvB,WAAO;AAAA,EACR;AAAA,EAEA,uBAA+B;AAC9B,WAAO;AAAA,EACR;AACD;","names":[]}

package/dist/{open-AIZG5756.js → open-WHVUYGPY.js}

@@ -1,18 +1,18 @@
 #!/usr/bin/env node
 import {
   DevServerManager
-} from "./chunk-SHVB3EFE.js";
-import "./chunk-LVLRMP7V.js";
+} from "./chunk-64O2UIWO.js";
 import {
   calculatePortForBranch
 } from "./chunk-VU3QMIP2.js";
+import "./chunk-AXX3QIKK.js";
 import {
   IdentifierParser
 } from "./chunk-UQIXZ3BA.js";
 import {
   ProjectCapabilityDetector
-} from "./chunk-EBISESAP.js";
-import "./chunk-2ZPFJQ3B.js";
+} from "./chunk-ZPSTA5PR.js";
+import "./chunk-BXCPJJYM.js";
 import {
   GitWorktreeManager
 } from "./chunk-EK3XCAAS.js";
@@ -288,4 +288,4 @@ Make sure the project is built (run 'il start' first)`
 export {
   OpenCommand
 };
-//# sourceMappingURL=open-AIZG5756.js.map
+//# sourceMappingURL=open-WHVUYGPY.js.map

package/dist/prompts/init-prompt.txt

@@ -692,6 +692,72 @@ 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}}
+### 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.
+
+**Invoke the framework detector agent** using the `iloom-framework-detector` agent:
+
+The agent will:
+1. Scan for language markers (Cargo.toml, requirements.txt, Gemfile, go.mod, etc.)
+2. Detect common frameworks
+3. Generate appropriate scripts for build, test, and dev commands
+4. Create `.iloom/package.iloom.json` with the detected configuration
+5. Detect and set project capabilities (cli, web) based on the framework
+
+**File Format:**
+```json
+{
+  "capabilities": ["cli"],
+  "scripts": {
+    "install": "your-install-command",
+    "build": "your-build-command",
+    "test": "your-test-command",
+    "dev": "your-dev-command",
+    "lint": "your-lint-command",
+    "typecheck": "your-typecheck-command"
+  }
+}
+```
+
+**Supported Scripts:**
+| Script | Purpose | When Used |
+|--------|---------|-----------|
+| `install` | Install dependencies | `il start` (loom creation), `il finish` (post-merge) |
+| `build` | Compile/build project | `il build`, `il finish` (CLI projects, post-merge) |
+| `test` | Run test suite | `il test`, `il finish` validation |
+| `dev` | Start dev server | `il dev-server` |
+| `lint` | Run linter | `il lint`, `il finish` validation |
+| `typecheck` | Type checking | `il typecheck`, `il finish` validation |
+| `compile` | Alternative to typecheck | `il compile`, `il finish` validation (preferred over typecheck if both exist) |
+
+**Capabilities:**
+- `"cli"` - Command-line interface/tool (enables CLI isolation features)
+- `"web"` - Web application with dev server (enables port assignment)
+
+**Note:** Scripts in `package.iloom.json` are raw shell commands, not npm script names. iloom will execute them directly.
+
+**After framework detection, verify capabilities were set correctly:**
+
+If the framework detector did not set capabilities, or if you need to ask the user:
+- Question: "What type of project is this?"
+- Options:
+  - "cli" - Command-line interface/tool
+  - "web" - Web application with dev server
+  - "both" - Both CLI and web capabilities
+  - "neither" - Library or other project type
+- Update `.iloom/package.iloom.json` with the appropriate `capabilities` array.
+
+**When to infer capabilities:**
+- Flask/Django/FastAPI/Rails/Actix/Rocket detected -> include "web"
+- CLI frameworks (click, fire, typer, clap) detected -> include "cli"
+- `[[bin]]` in Cargo.toml -> include "cli"
+- No clear indicators -> ask user explicitly
+
+After the framework detector agent completes (and capabilities are set), proceed to Phase 2.
+{{/IF NO_PACKAGE_JSON}}
+
 ### Phase 2: Tooling Configuration
 
 This phase configures external tooling integrations. Use AskUserQuestion to gather these settings.
@@ -1084,14 +1150,7 @@ Reason: mainBranch has same value in both files, so it's removed from local
    - `.iloom/settings.local.json` if user chose Local
 4. Use the Write tool to create/update the file
 
-### Phase 7: Update .gitignore
-
-If the user chose `.iloom/settings.local.json`, ensure `.gitignore` includes this entry:
-- Read `.gitignore` if it exists
-- Check if `.iloom/settings.local.json` is already listed
-- If not, append it to the file
-
-### Phase 7.5: Offer to Commit Changes
+### Phase 7: Offer to Commit Changes
 
 After making configuration changes, offer to commit the iloom-related files:
 
@@ -1237,6 +1296,7 @@ Need more advanced configuration? I can help you set up:
   • Database Settings - Configure database branching for isolated development
   • Workflow Behavior - Control permissions, IDE launching, dev servers, and terminal behavior
   • Protected Branches - Prevent iloom from creating worktrees for certain branches
+  • Custom Scripts - Override package.json scripts with custom commands
 
 You can ask me questions like:
   "Is it possible to have the analysis agent use a different model?"
@@ -1244,6 +1304,7 @@ You can ask me questions like:
   "Can I disable the IDE from launching automatically?"
   "How do I protect my main branch from worktree creation?"
   "What models are available for the different agents?"
+  "How do I use custom build/test commands instead of package.json scripts?"
 
 Just ask any of these questions and I'll help you modify your settings.
 
@@ -1297,6 +1358,38 @@ If users ask about specific configurations, help them add these sections to thei
    }
    ```
 
+6. **Custom Script Configuration (package.iloom.json):**
+
+   If users want to override or supplement npm scripts with custom commands, help them create `.iloom/package.iloom.json`:
+   ```json
+   {
+     "scripts": {
+       "install": "your-custom-install-command",
+       "build": "your-custom-build-command",
+       "test": "your-custom-test-command",
+       "dev": "your-custom-dev-command",
+       "lint": "your-custom-lint-command",
+       "typecheck": "your-custom-typecheck-command"
+     }
+   }
+   ```
+
+   When `package.iloom.json` exists, iloom uses its scripts instead of `package.json`.
+
+   **Supported scripts:**
+   - `install` - Run during loom creation and post-merge (e.g., `bundle install`, `poetry install`)
+   - `build` - Compile/build the project
+   - `test` - Run the test suite
+   - `dev` - Start the development server
+   - `lint` - Run the linter
+   - `typecheck` or `compile` - Type checking (compile takes precedence if both exist)
+
+   **Common use cases:**
+   - Non-Node.js projects (Ruby, Python, Rust, Go, etc.)
+   - Using a different test runner than what's in package.json
+   - Running additional commands before/after the standard npm scripts
+   - Wrapping commands with environment variables or tools
+
 ## Important Notes
 
 - **Validate ALL inputs** against the schema before writing files

package/dist/prompts/issue-prompt.txt

@@ -266,9 +266,9 @@ Perform ONE comprehensive scan to determine which agents need to run:
 **STEP 1 - Enhancement Phase:**
 
 Only execute if workflow plan determined NEEDS_ENHANCEMENT:
-1. Execute: @agent-iloom-issue-enhancer ISSUE_NUMBER with the following instructions about assumptions:
+1. Execute: @agent-iloom-issue-enhancer ISSUE_NUMBER {{#IF ONE_SHOT_MODE}}with the following instructions about assumptions:
    - Before making assumptions, scan ALL issue comments for previously asked questions and their answers.
-   - When creating question tables in your issue comments, fill in your own assumed answers to each question. This documents assumptions made during execution.
+   - When creating question tables in your issue comments, fill in your own assumed answers to each question. This documents assumptions made during autonomous execution.{{/IF ONE_SHOT_MODE}}
 2. Upon completion: Extract issue+comment link (including comment ID) from agent output and provide link to issue comment
 {{#IF INTERACTIVE_MODE}}
 2.5. Extract and validate assumptions (batched validation):
@@ -317,9 +317,9 @@ If workflow plan determined SKIP_ENHANCEMENT:
 **STEP 1.5 - Complexity Evaluation Phase:**
 
 Only execute if workflow plan determined NEEDS_COMPLEXITY_EVAL:
-1. Execute: @agent-iloom-issue-complexity-evaluator ISSUE_NUMBER with the following instructions about assumptions:
+1. Execute: @agent-iloom-issue-complexity-evaluator ISSUE_NUMBER {{#IF ONE_SHOT_MODE}}with the following instructions about assumptions:
    - Before making assumptions, scan ALL issue comments for previously asked questions and their answers.
-   - When creating question tables in your issue comments, fill in your own assumed answers to each question. This documents assumptions made during execution.
+   - When creating question tables in your issue comments, fill in your own assumed answers to each question. This documents assumptions made during autonomous execution.{{/IF ONE_SHOT_MODE}}
 2. Upon completion: Extract issue+comment link from agent output and provide link to issue comment (including comment ID)
 {{#IF INTERACTIVE_MODE}}
 2.5. Extract and validate assumptions (batched validation):
@@ -385,9 +385,9 @@ If workflow plan determined SKIP_COMPLEXITY_EVAL:
 **STEP 2 - Analysis Phase (COMPLEX workflow only):**
 
 Only execute if workflow plan determined NEEDS_ANALYSIS AND complexity is COMPLEX:
-1. Execute: @agent-iloom-issue-analyzer ISSUE_NUMBER with the following instructions about assumptions:
+1. Execute: @agent-iloom-issue-analyzer ISSUE_NUMBER {{#IF ONE_SHOT_MODE}}with the following instructions about assumptions:
    - Before making assumptions, scan ALL issue comments for previously asked questions and their answers.
-   - When creating question tables in your issue comments, fill in your own assumed answers to each question. This documents assumptions made during execution.
+   - When creating question tables in your issue comments, fill in your own assumed answers to each question. This documents assumptions made during autonomous execution.{{/IF ONE_SHOT_MODE}}
 2. Upon completion: Extract issue+comment link from agent output and provide link to issue comment (including comment ID)
    - Use `recap.add_entry` to log significant technical findings (type: "insight" for dependencies/constraints, type: "risk" for problems identified)
 {{#IF INTERACTIVE_MODE}}
@@ -464,9 +464,9 @@ After STEP 1.5 completes and complexity is confirmed, determine which workflow p
 
 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 ISSUE_NUMBER with the following instructions about assumptions:
+2. Execute: @agent-iloom-issue-analyze-and-plan ISSUE_NUMBER {{#IF ONE_SHOT_MODE}}with the following instructions about assumptions:
    - Before making assumptions, scan ALL issue comments for previously asked questions and their answers.
-   - When creating question tables in your issue comments, fill in your own assumed answers to each question. This documents assumptions made during execution.
+   - When creating question tables in your issue comments, fill in your own assumed answers to each question. This documents assumptions made during autonomous execution.{{/IF ONE_SHOT_MODE}}
 3. Upon completion: Extract issue+comment link from agent output and provide link to issue comment (including comment ID)
    - Use `recap.add_entry` to log key technical discoveries (type: "insight") and design decisions (type: "decision")
 {{#IF INTERACTIVE_MODE}}
@@ -505,9 +505,9 @@ Execute combined analyze-and-plan agent:
 **IMPORTANT: Only execute this step if COMPLEX workflow is being followed (not SIMPLE)**
 
 Only execute if workflow plan determined NEEDS_PLANNING AND complexity is COMPLEX:
-1. Execute: @agent-iloom-issue-planner ISSUE_NUMBER with the following instructions about assumptions:
+1. Execute: @agent-iloom-issue-planner ISSUE_NUMBER {{#IF ONE_SHOT_MODE}}with the following instructions about assumptions:
    - Before making assumptions, scan ALL issue comments for previously asked questions and their answers.
-   - When creating question tables in your issue comments, fill in your own assumed answers to each question. This documents assumptions made during execution.
+   - When creating question tables in your issue comments, fill in your own assumed answers to each question. This documents assumptions made during autonomous execution.{{/IF ONE_SHOT_MODE}}
 2. Upon completion: Extract issue+comment link from agent output and provide link to issue comment (including comment ID)
    - Use `recap.add_entry` to log key architectural decisions (e.g., type: "decision", content: "Chose approach A over B due to X constraint")
 {{#IF INTERACTIVE_MODE}}
@@ -552,9 +552,9 @@ Only execute if workflow plan determined NEEDS_IMPLEMENTATION:
    - Look back at the planning phase output (STEP 3 for COMPLEX or STEP 2-SIMPLE for SIMPLE workflows)
    - Extract the comment ID from the issue comment URL that was provided
    - The comment ID is the numeric value after "#issuecomment-" in the URL (e.g., https://github.com/org/repo/issues/123#issuecomment-456789 has comment ID 456789)
-2. Execute: @agent-iloom-issue-implementer ISSUE_NUMBER with the following instructions about assumptions:
+2. Execute: @agent-iloom-issue-implementer ISSUE_NUMBER {{#IF ONE_SHOT_MODE}}with the following instructions about assumptions:
    - Before making assumptions, scan ALL issue comments for previously asked questions and their answers.
-   - When creating question tables in your issue comments, fill in your own assumed answers to each question. This documents assumptions made during execution.
+   - When creating question tables in your issue comments, fill in your own assumed answers to each question. This documents assumptions made during autonomous execution.{{/IF ONE_SHOT_MODE}}
    Additional critical instructions:
    - **CRITICAL**: The implementation plan in the issue comments contains exact file paths and line numbers. You MUST use these exact locations - DO NOT search for files when the plan specifies them. Extract file locations from the plan in Step 1.5 before implementing.
    - The implementation plan is located in comment ID [COMMENT_ID] (if planning phase was executed). Read this comment first in Step 1.5 to extract file specifications.

package/dist/{rebase-5EY3Q6XP.js → rebase-Y4AS6LQW.js}

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import {
   MergeManager
-} from "./chunk-WIJWIKAN.js";
+} from "./chunk-2A7WQKBE.js";
 import {
   GitWorktreeManager
 } from "./chunk-EK3XCAAS.js";
@@ -94,4 +94,4 @@ export {
   RebaseCommand,
   WorktreeValidationError
 };
-//# sourceMappingURL=rebase-5EY3Q6XP.js.map
+//# sourceMappingURL=rebase-Y4AS6LQW.js.map

package/dist/{run-CMZUYZVG.js → run-NCRK5NPR.js}

@@ -1,18 +1,18 @@
 #!/usr/bin/env node
 import {
   DevServerManager
-} from "./chunk-SHVB3EFE.js";
-import "./chunk-LVLRMP7V.js";
+} from "./chunk-64O2UIWO.js";
 import {
   calculatePortForBranch
 } from "./chunk-VU3QMIP2.js";
+import "./chunk-AXX3QIKK.js";
 import {
   IdentifierParser
 } from "./chunk-UQIXZ3BA.js";
 import {
   ProjectCapabilityDetector
-} from "./chunk-EBISESAP.js";
-import "./chunk-2ZPFJQ3B.js";
+} from "./chunk-ZPSTA5PR.js";
+import "./chunk-BXCPJJYM.js";
 import {
   GitWorktreeManager
 } from "./chunk-EK3XCAAS.js";
@@ -288,4 +288,4 @@ Make sure the project is built (run 'il start' first)`
 export {
   RunCommand
 };
-//# sourceMappingURL=run-CMZUYZVG.js.map
+//# sourceMappingURL=run-NCRK5NPR.js.map

package/dist/{summary-5YXUGPRN.js → summary-CVFAMDOJ.js}

@@ -1,14 +1,14 @@
 #!/usr/bin/env node
 import {
   SessionSummaryService
-} from "./chunk-SJIMVKK7.js";
+} from "./chunk-K7SEEHKO.js";
 import "./chunk-NXMDEL3F.js";
 import "./chunk-7Q66W4OH.js";
 import {
   GitWorktreeManager
 } from "./chunk-EK3XCAAS.js";
 import "./chunk-FXDYIV3K.js";
-import "./chunk-K5G5SFWY.js";
+import "./chunk-W6WVRHJ6.js";
 import {
   extractIssueNumber
 } from "./chunk-GEXP5IOF.js";
@@ -248,4 +248,4 @@ Please provide an issue number, PR number, or branch name.`
 export {
   SummaryCommand
 };
-//# sourceMappingURL=summary-5YXUGPRN.js.map
+//# sourceMappingURL=summary-CVFAMDOJ.js.map

package/dist/test-3KIVXI6J.js

@@ -0,0 +1,27 @@
+#!/usr/bin/env node
+import {
+  ScriptCommandBase
+} from "./chunk-TRQ76ISK.js";
+import "./chunk-AXX3QIKK.js";
+import "./chunk-UQIXZ3BA.js";
+import "./chunk-BXCPJJYM.js";
+import "./chunk-EK3XCAAS.js";
+import "./chunk-GEXP5IOF.js";
+import "./chunk-F6WVM437.js";
+import "./chunk-CFUWQHCJ.js";
+import "./chunk-6MLEBAYZ.js";
+import "./chunk-VT4PDUYT.js";
+
+// src/commands/test.ts
+var TestCommand = class extends ScriptCommandBase {
+  getScriptName() {
+    return "test";
+  }
+  getScriptDisplayName() {
+    return "Test";
+  }
+};
+export {
+  TestCommand
+};
+//# sourceMappingURL=test-3KIVXI6J.js.map

package/dist/test-3KIVXI6J.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../src/commands/test.ts"],"sourcesContent":["import { ScriptCommandBase, ScriptCommandInput } from './script-command-base.js'\n\nexport type { ScriptCommandInput as TestCommandInput }\n\n/**\n * TestCommand - Run the test script for a workspace\n * Uses package.iloom.json if available, otherwise falls back to package.json\n */\nexport class TestCommand extends ScriptCommandBase {\n\tgetScriptName(): string {\n\t\treturn 'test'\n\t}\n\n\tgetScriptDisplayName(): string {\n\t\treturn 'Test'\n\t}\n}\n"],"mappings":";;;;;;;;;;;;;;;AAQO,IAAM,cAAN,cAA0B,kBAAkB;AAAA,EAClD,gBAAwB;AACvB,WAAO;AAAA,EACR;AAAA,EAEA,uBAA+B;AAC9B,WAAO;AAAA,EACR;AACD;","names":[]}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@iloom/cli",
-  "version": "0.5.5",
+  "version": "0.6.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/ProjectCapabilityDetector-34LU7JJ4.js

@@ -1,9 +0,0 @@
-#!/usr/bin/env node
-import {
-  ProjectCapabilityDetector
-} from "./chunk-EBISESAP.js";
-import "./chunk-2ZPFJQ3B.js";
-export {
-  ProjectCapabilityDetector
-};
-//# sourceMappingURL=ProjectCapabilityDetector-34LU7JJ4.js.map

package/dist/chunk-2ZPFJQ3B.js

@@ -1,63 +0,0 @@
-#!/usr/bin/env node
-
-// src/utils/package-json.ts
-import fs from "fs-extra";
-import path from "path";
-async function readPackageJson(dir) {
-  const pkgPath = path.join(dir, "package.json");
-  try {
-    const pkgJson = await fs.readJson(pkgPath);
-    return pkgJson;
-  } catch (error) {
-    if (error.code === "ENOENT") {
-      throw new Error(`package.json not found in ${dir}`);
-    }
-    const message = error instanceof Error ? error.message : "Unknown error";
-    throw new Error(`Invalid package.json in ${dir}: ${message}`);
-  }
-}
-function parseBinField(bin, packageName) {
-  if (!bin) {
-    return {};
-  }
-  if (typeof bin === "string") {
-    return { [packageName]: bin };
-  }
-  return bin;
-}
-function hasWebDependencies(pkgJson) {
-  const webIndicators = [
-    "next",
-    "vite",
-    "express",
-    "react-scripts",
-    "nuxt",
-    "svelte-kit",
-    "astro",
-    "remix",
-    "fastify",
-    "koa",
-    "hapi",
-    "@angular/core",
-    "gatsby",
-    "@11ty/eleventy",
-    "ember-cli"
-  ];
-  const allDeps = {
-    ...pkgJson.dependencies,
-    ...pkgJson.devDependencies
-  };
-  return webIndicators.some((indicator) => indicator in allDeps);
-}
-function hasScript(pkgJson, scriptName) {
-  var _a;
-  return !!((_a = pkgJson.scripts) == null ? void 0 : _a[scriptName]);
-}
-
-export {
-  readPackageJson,
-  parseBinField,
-  hasWebDependencies,
-  hasScript
-};
-//# sourceMappingURL=chunk-2ZPFJQ3B.js.map

package/dist/chunk-2ZPFJQ3B.js.map

@@ -1 +0,0 @@
-{"version":3,"sources":["../src/utils/package-json.ts"],"sourcesContent":["import fs from 'fs-extra'\nimport path from 'path'\n\nexport interface PackageJson {\n  name: string\n  version?: string\n  bin?: string | Record<string, string>\n  dependencies?: Record<string, string>\n  devDependencies?: Record<string, string>\n  scripts?: Record<string, string>\n  [key: string]: unknown\n}\n\n/**\n * Read and parse package.json from a directory\n * @param dir Directory containing package.json\n * @returns Parsed package.json object\n * @throws Error if package.json doesn't exist or contains invalid JSON\n */\nexport async function readPackageJson(dir: string): Promise<PackageJson> {\n  const pkgPath = path.join(dir, 'package.json')\n\n  try {\n    const pkgJson = await fs.readJson(pkgPath)\n    return pkgJson as PackageJson\n  } catch (error) {\n    if ((error as { code?: string }).code === 'ENOENT') {\n      throw new Error(`package.json not found in ${dir}`)\n    }\n    const message = error instanceof Error ? error.message : 'Unknown error'\n    throw new Error(`Invalid package.json in ${dir}: ${message}`)\n  }\n}\n\n/**\n * Parse bin field into normalized Record format\n * @param bin The bin field from package.json (string or object)\n * @param packageName Package name to use for string bin variant\n * @returns Normalized bin entries as Record<string, string>\n */\nexport function parseBinField(\n  bin: string | Record<string, string> | undefined,\n  packageName: string\n): Record<string, string> {\n  if (!bin) {\n    return {}\n  }\n\n  if (typeof bin === 'string') {\n    return { [packageName]: bin }\n  }\n\n  return bin\n}\n\n/**\n * Check if package.json indicates a web application\n * @param pkgJson Parsed package.json object\n * @returns true if package has web framework dependencies\n */\nexport function hasWebDependencies(pkgJson: PackageJson): boolean {\n  const webIndicators = [\n    'next',\n    'vite',\n    'express',\n    'react-scripts',\n    'nuxt',\n    'svelte-kit',\n    'astro',\n    'remix',\n    'fastify',\n    'koa',\n    'hapi',\n    '@angular/core',\n    'gatsby',\n    '@11ty/eleventy',\n    'ember-cli'\n  ]\n\n  const allDeps = {\n    ...pkgJson.dependencies,\n    ...pkgJson.devDependencies\n  }\n\n  return webIndicators.some(indicator => indicator in allDeps)\n}\n\n/**\n * Check if package.json has a specific script\n * @param pkgJson Parsed package.json object\n * @param scriptName Script name to check for\n * @returns true if script exists\n */\nexport function hasScript(pkgJson: PackageJson, scriptName: string): boolean {\n  return !!pkgJson.scripts?.[scriptName]\n}\n"],"mappings":";;;AAAA,OAAO,QAAQ;AACf,OAAO,UAAU;AAkBjB,eAAsB,gBAAgB,KAAmC;AACvE,QAAM,UAAU,KAAK,KAAK,KAAK,cAAc;AAE7C,MAAI;AACF,UAAM,UAAU,MAAM,GAAG,SAAS,OAAO;AACzC,WAAO;AAAA,EACT,SAAS,OAAO;AACd,QAAK,MAA4B,SAAS,UAAU;AAClD,YAAM,IAAI,MAAM,6BAA6B,GAAG,EAAE;AAAA,IACpD;AACA,UAAM,UAAU,iBAAiB,QAAQ,MAAM,UAAU;AACzD,UAAM,IAAI,MAAM,2BAA2B,GAAG,KAAK,OAAO,EAAE;AAAA,EAC9D;AACF;AAQO,SAAS,cACd,KACA,aACwB;AACxB,MAAI,CAAC,KAAK;AACR,WAAO,CAAC;AAAA,EACV;AAEA,MAAI,OAAO,QAAQ,UAAU;AAC3B,WAAO,EAAE,CAAC,WAAW,GAAG,IAAI;AAAA,EAC9B;AAEA,SAAO;AACT;AAOO,SAAS,mBAAmB,SAA+B;AAChE,QAAM,gBAAgB;AAAA,IACpB;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,IACA;AAAA,EACF;AAEA,QAAM,UAAU;AAAA,IACd,GAAG,QAAQ;AAAA,IACX,GAAG,QAAQ;AAAA,EACb;AAEA,SAAO,cAAc,KAAK,eAAa,aAAa,OAAO;AAC7D;AAQO,SAAS,UAAU,SAAsB,YAA6B;AA7F7E;AA8FE,SAAO,CAAC,GAAC,aAAQ,YAAR,mBAAkB;AAC7B;","names":[]}