@shipit-ai/cli 1.164.2 → 1.165.0

package/dist/packages/core/src/infrastructure/services/agents/common/executors/fixtures/plan.fixture.d.ts

@@ -1,7 +1,7 @@
 /**
  * Plan Fixture
  *
- * Realistic fixture for the fictional "Add dark-mode toggle to Shep Web UI" feature.
+ * Realistic fixture for the fictional "Add dark-mode toggle to ShipIT Web UI" feature.
  * Passes validatePlan() with zero repair iterations.
  */
 export declare const PLAN_FIXTURE = "name: dark-mode-toggle\nsummary: >\n  Implement dark-mode toggle across 3 phases: ThemeProvider context foundation,\n  ThemeToggle component, and settings panel integration. No interface changes\n  required; the feature slots into existing React context and component patterns.\n\nrelatedFeatures: []\n\ntechnologies:\n  - React 19 context API\n  - Tailwind CSS v4\n  - shadcn/ui Switch\n  - Next.js App Router\n  - Storybook\n  - Vitest\n\nrelatedLinks: []\n\nphases:\n  - id: phase-1\n    name: 'Theme Context Foundation'\n    description: >\n      Create the ThemeProvider component and useTheme hook. This phase establishes\n      the theme state management infrastructure that all subsequent phases depend on.\n      ThemeProvider reads from localStorage on mount and writes on toggle.\n    parallel: false\n\n  - id: phase-2\n    name: 'ThemeToggle Component'\n    description: >\n      Create the ThemeToggle UI component using shadcn/ui Switch and Label.\n      Includes Storybook story with light and dark variant knobs and unit tests\n      using jsdom for DOM interaction.\n    parallel: false\n\n  - id: phase-3\n    name: 'Settings Panel Integration'\n    description: >\n      Mount ThemeProvider in the root layout and add ThemeToggle to the settings\n      panel. Run full pnpm validate and pnpm test to confirm no regressions.\n    parallel: false\n\nfilesToCreate:\n  - src/presentation/web/components/common/theme/theme-provider.tsx\n  - src/presentation/web/components/common/theme/use-theme.ts\n  - src/presentation/web/components/common/theme/theme-toggle.tsx\n  - src/presentation/web/components/common/theme/theme-toggle.stories.tsx\n\nfilesToModify:\n  - src/presentation/web/app/layout.tsx\n  - src/presentation/web/components/features/settings/settings-panel.tsx\n\nopenQuestions: []\n\ncontent: |\n  ## Architecture Overview\n\n  The ThemeProvider wraps the Next.js App Router root layout, making the theme context\n  available to the entire component tree via useTheme hook. The ThemeToggle component\n  is a pure UI component that consumes useTheme and renders a shadcn/ui Switch with\n  no business logic.\n\n  ## Key Design Decisions\n\n  **ThemeProvider in root layout**: Placing the provider at the top of the component\n  tree avoids prop drilling and matches the SettingsProvider pattern already in use.\n\n  **localStorage persistence**: Read on mount, write on toggle. No SSR conflicts\n  because localStorage is only accessed in useEffect (client-side only).\n\n  **Tailwind dark: class**: Toggling the html element class is the zero-config\n  approach for Tailwind v4. No tailwind.config.ts changes needed.\n\n  ## Implementation Strategy\n\n  Phase 1 establishes the foundation (context, hook) before any UI is built.\n  Phase 2 builds the UI component in isolation \u2014 fully testable without the settings\n  panel. Phase 3 wires everything together and validates the full integration. This\n  dependency ordering ensures each phase is independently verifiable.\n\n  ## Risk Mitigation\n\n  | Risk | Mitigation |\n  | ---- | ---------- |\n  | FOUC on initial load | ThemeProvider sets html class synchronously from localStorage on mount |\n  | localStorage unavailable (SSR) | useEffect guard: only access localStorage in browser context |\n  | shadcn/ui Switch not yet installed | Check if component exists; install via shadcn add switch if needed |\n";

package/dist/packages/core/src/infrastructure/services/agents/common/executors/fixtures/plan.fixture.js

@@ -1,7 +1,7 @@
 /**
  * Plan Fixture
  *
- * Realistic fixture for the fictional "Add dark-mode toggle to Shep Web UI" feature.
+ * Realistic fixture for the fictional "Add dark-mode toggle to ShipIT Web UI" feature.
  * Passes validatePlan() with zero repair iterations.
  */
 export const PLAN_FIXTURE = `name: dark-mode-toggle

package/dist/packages/core/src/infrastructure/services/agents/common/executors/fixtures/research.fixture.d.ts

@@ -1,7 +1,7 @@
 /**
  * Research Fixture
  *
- * Realistic fixture for the fictional "Add dark-mode toggle to Shep Web UI" feature.
+ * Realistic fixture for the fictional "Add dark-mode toggle to ShipIT Web UI" feature.
  * Passes validateResearch() with zero repair iterations.
  */
 export declare const RESEARCH_FIXTURE = "name: dark-mode-toggle\nsummary: >\n  The dark-mode implementation uses React context for theme state distribution,\n  Tailwind CSS v4 class-based dark mode, and localStorage for preference persistence.\n  No new npm dependencies are required. Three architectural decisions cover state\n  management, CSS strategy, and persistence layer.\n\nrelatedFeatures: []\n\ntechnologies:\n  - React 19 context API\n  - 'Tailwind CSS v4 (dark: modifier)'\n  - localStorage Web API\n  - shadcn/ui Switch component\n  - Next.js App Router root layout\n\nrelatedLinks: []\n\ndecisions:\n  - title: 'Theme State Management'\n    chosen: >\n      React context with a ThemeProvider component and useTheme hook. The provider\n      reads the initial value from localStorage and sets the html element class on\n      mount and on toggle.\n    rejected:\n      - >\n        Zustand global store: adds a new state management library dependency for a\n        single boolean value; over-engineered for this scope when React context\n        achieves the same result in ~40 lines.\n      - >\n        next-themes library: a popular choice but adds a new npm package for\n        functionality achievable in-house; the project guideline prefers no new\n        dependencies when existing tools suffice (NFR-3).\n    rationale: >\n      The project already uses React context extensively (e.g., SettingsProvider).\n      A simple context-based ThemeProvider follows the established pattern and\n      requires zero new dependencies \u2014 consistent with NFR-3.\n\n  - title: 'CSS Dark Mode Strategy'\n    chosen: >\n      Tailwind CSS v4 class-based dark mode: add the dark class to the html element\n      and rely on Tailwind dark: variants already present in shadcn/ui components.\n    rejected:\n      - >\n        CSS custom properties (CSS variables) approach: requires redefining all\n        existing Tailwind color tokens as CSS variables and large changes to every\n        styled component \u2014 disproportionate for this feature.\n      - >\n        Inline style overrides on individual components: does not scale; breaks\n        existing Tailwind utility classes; produces unmaintainable ad-hoc styling.\n    rationale: >\n      Tailwind CSS v4 with darkMode: class is already configured in the project.\n      All shadcn/ui components expose dark: variants. Toggling the html class is\n      the minimal, canonical approach that requires no additional configuration.\n\n  - title: 'Persistence Layer for Theme Preference'\n    chosen: >\n      localStorage Web API. Read on ThemeProvider mount to restore the preference;\n      write on every toggleTheme() call. Key: shep-theme, values: light or dark.\n    rejected:\n      - >\n        SQLite settings via backend API: requires a new settings field, API endpoint,\n        and schema migration \u2014 out of scope for a client-side preference.\n      - >\n        sessionStorage: does not persist across browser sessions; the whole point\n        is remembering the user preference between visits.\n    rationale: >\n      localStorage is the de-facto standard for persisting UI theme preferences\n      client-side. It is synchronous, zero-dependency, available in all target\n      browsers, and requires no backend changes \u2014 satisfying NFR-3.\n\nopenQuestions: []\n\ncontent: |\n  ## Technology Decisions\n\n  ### 1. Theme State Management\n\n  **Chosen:** React context ThemeProvider + useTheme hook\n\n  **Rejected:**\n  - Zustand global store \u2014 adds a new dependency for a single boolean\n  - next-themes library \u2014 adds a package for functionality achievable in ~40 lines\n\n  **Rationale:** Follows established SettingsProvider pattern. Zero new dependencies.\n\n  ### 2. CSS Dark Mode Strategy\n\n  **Chosen:** Tailwind CSS v4 dark: class-based (dark class on html element)\n\n  **Rejected:**\n  - CSS custom properties \u2014 requires redefining all color tokens (large change surface)\n  - Inline style overrides \u2014 unmaintainable, breaks Tailwind utilities\n\n  **Rationale:** Already configured; shadcn/ui components expose dark: variants natively.\n\n  ### 3. Persistence Layer\n\n  **Chosen:** localStorage (key: shep-theme, values: light | dark)\n\n  **Rejected:**\n  - SQLite settings via API \u2014 out of scope, requires migration\n  - sessionStorage \u2014 does not survive browser restarts\n\n  **Rationale:** De-facto standard for client-side theme persistence. Zero backend changes.\n\n  ## Library Analysis\n\n  | Library | Purpose | Decision | Reasoning |\n  | ------- | ------- | -------- | --------- |\n  | next-themes | SSR-safe theme management | Reject | Adds dependency for in-house functionality |\n  | Tailwind CSS v4 | Dark mode via dark: class | Use (existing) | Already configured, shadcn/ui compatible |\n  | shadcn/ui Switch | Toggle UI control | Use (existing) | Already a project dependency, accessible |\n  | localStorage | Preference persistence | Use (built-in) | No dependency, synchronous, universally available |\n\n  ## Security Considerations\n\n  localStorage is readable by any JavaScript on the page. The stored value is\n  light or dark \u2014 no sensitive data. The ThemeProvider must sanitize the retrieved\n  value (only accept light or dark; default to light for any other value) to prevent\n  unexpected CSS class injection.\n\n  ## Performance Implications\n\n  localStorage.getItem() is synchronous and executes in under 1ms. Setting the html\n  class on mount avoids a flash of unstyled content (FOUC) provided the ThemeProvider\n  is high enough in the component tree.\n\n  ## Architecture Notes\n\n  ThemeProvider wraps the root layout, making theme state available to all pages and\n  components without prop drilling. The useTheme hook is consumed only by ThemeToggle\n  and the root layout. This follows the existing SettingsProvider pattern.\n";

package/dist/packages/core/src/infrastructure/services/agents/common/executors/fixtures/research.fixture.js

@@ -1,7 +1,7 @@
 /**
  * Research Fixture
  *
- * Realistic fixture for the fictional "Add dark-mode toggle to Shep Web UI" feature.
+ * Realistic fixture for the fictional "Add dark-mode toggle to ShipIT Web UI" feature.
  * Passes validateResearch() with zero repair iterations.
  */
 export const RESEARCH_FIXTURE = `name: dark-mode-toggle

package/dist/packages/core/src/infrastructure/services/agents/common/executors/fixtures/spec-analyze.fixture.d.ts

@@ -1,8 +1,8 @@
 /**
  * Spec (Analyze Phase) Fixture
  *
- * Realistic fixture for the fictional "Add dark-mode toggle to Shep Web UI" feature.
+ * Realistic fixture for the fictional "Add dark-mode toggle to ShipIT Web UI" feature.
  * Passes validateSpecAnalyze() with zero repair iterations.
  */
-export declare const SPEC_ANALYZE_FIXTURE = "name: dark-mode-toggle\nnumber: 42\nbranch: feat/042-dark-mode-toggle\noneLiner: Add a dark-mode toggle to the Shep web UI settings panel\nsummary: >\n  Introduce a persistent dark-mode toggle to the Shep web UI settings panel that\n  applies a CSS class-based theme, stores the user preference in localStorage, and\n  is surfaced as a shadcn/ui Switch component with full Storybook coverage.\nphase: Analysis\nsizeEstimate: M\n\nrelatedFeatures: []\n\ntechnologies:\n  - React 19\n  - Next.js 16 (App Router)\n  - Tailwind CSS v4\n  - shadcn/ui\n  - Storybook\n  - TypeScript\n\nrelatedLinks: []\n\nopenQuestions: []\n\ncontent: |\n  ## Problem Statement\n\n  The Shep web UI currently renders only in light mode. Developers working in dark\n  environments or those who prefer dark themes have no way to switch the UI appearance.\n  Adding a first-class dark-mode toggle improves developer experience and demonstrates\n  the Shep settings panel as a configurable surface.\n\n  ## Codebase Analysis\n\n  ### Project Structure\n\n  The web UI lives in src/presentation/web/ following Next.js App Router conventions.\n  Components are organized into four tiers: ui/ (Tier 0), common/ (Tier 1),\n  layouts/ (Tier 2), and features/ (Tier 3). Storybook stories are mandatory for every\n  component.\n\n  ### Architecture Patterns\n\n  The project uses shadcn/ui (Radix primitives + Tailwind CSS v4) for all UI components.\n  Theme state would live in a React context provider wrapping the root layout, following\n  the existing SettingsProvider pattern in the codebase. Clean Architecture layers keep\n  theme state in the presentation layer only.\n\n  ### Relevant Technologies\n\n  Tailwind CSS v4 supports dark mode via the `dark` CSS class on the html element.\n  shadcn/ui provides a Switch component suitable for the toggle control. localStorage\n  provides client-side persistence without any backend changes.\n\n  ## Affected Areas\n\n  | Area | Impact | Reasoning |\n  | ---- | ------ | --------- |\n  | src/presentation/web/components/features/settings/ | High | Settings panel receives the toggle component |\n  | src/presentation/web/app/layout.tsx | Medium | Root layout needs ThemeProvider wrapper |\n  | src/presentation/web/components/common/ | Medium | ThemeToggle and ThemeProvider components created here |\n  | tailwind.config.ts | Low | Verify darkMode: class is configured |\n\n  ## Dependencies\n\n  - shadcn/ui Switch component\n  - React context for theme state distribution\n  - localStorage Web API for persistence (built-in, no new dependency)\n\n  ## Size Estimate\n\n  **M (days)** \u2014 Context setup, toggle component, settings integration, Storybook stories,\n  and tests across 3 phases add up to roughly 2 developer-days with TDD.\n";
+export declare const SPEC_ANALYZE_FIXTURE = "name: dark-mode-toggle\nnumber: 42\nbranch: feat/042-dark-mode-toggle\noneLiner: Add a dark-mode toggle to the ShipIT web UI settings panel\nsummary: >\n  Introduce a persistent dark-mode toggle to the ShipIT web UI settings panel that\n  applies a CSS class-based theme, stores the user preference in localStorage, and\n  is surfaced as a shadcn/ui Switch component with full Storybook coverage.\nphase: Analysis\nsizeEstimate: M\n\nrelatedFeatures: []\n\ntechnologies:\n  - React 19\n  - Next.js 16 (App Router)\n  - Tailwind CSS v4\n  - shadcn/ui\n  - Storybook\n  - TypeScript\n\nrelatedLinks: []\n\nopenQuestions: []\n\ncontent: |\n  ## Problem Statement\n\n  The ShipIT web UI currently renders only in light mode. Developers working in dark\n  environments or those who prefer dark themes have no way to switch the UI appearance.\n  Adding a first-class dark-mode toggle improves developer experience and demonstrates\n  the ShipIT settings panel as a configurable surface.\n\n  ## Codebase Analysis\n\n  ### Project Structure\n\n  The web UI lives in src/presentation/web/ following Next.js App Router conventions.\n  Components are organized into four tiers: ui/ (Tier 0), common/ (Tier 1),\n  layouts/ (Tier 2), and features/ (Tier 3). Storybook stories are mandatory for every\n  component.\n\n  ### Architecture Patterns\n\n  The project uses shadcn/ui (Radix primitives + Tailwind CSS v4) for all UI components.\n  Theme state would live in a React context provider wrapping the root layout, following\n  the existing SettingsProvider pattern in the codebase. Clean Architecture layers keep\n  theme state in the presentation layer only.\n\n  ### Relevant Technologies\n\n  Tailwind CSS v4 supports dark mode via the `dark` CSS class on the html element.\n  shadcn/ui provides a Switch component suitable for the toggle control. localStorage\n  provides client-side persistence without any backend changes.\n\n  ## Affected Areas\n\n  | Area | Impact | Reasoning |\n  | ---- | ------ | --------- |\n  | src/presentation/web/components/features/settings/ | High | Settings panel receives the toggle component |\n  | src/presentation/web/app/layout.tsx | Medium | Root layout needs ThemeProvider wrapper |\n  | src/presentation/web/components/common/ | Medium | ThemeToggle and ThemeProvider components created here |\n  | tailwind.config.ts | Low | Verify darkMode: class is configured |\n\n  ## Dependencies\n\n  - shadcn/ui Switch component\n  - React context for theme state distribution\n  - localStorage Web API for persistence (built-in, no new dependency)\n\n  ## Size Estimate\n\n  **M (days)** \u2014 Context setup, toggle component, settings integration, Storybook stories,\n  and tests across 3 phases add up to roughly 2 developer-days with TDD.\n";
 //# sourceMappingURL=spec-analyze.fixture.d.ts.map

package/dist/packages/core/src/infrastructure/services/agents/common/executors/fixtures/spec-analyze.fixture.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"spec-analyze.fixture.d.ts","sourceRoot":"","sources":["../../../../../../../../../../packages/core/src/infrastructure/services/agents/common/executors/fixtures/spec-analyze.fixture.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,eAAO,MAAM,oBAAoB,gtFA0EhC,CAAC"}
+{"version":3,"file":"spec-analyze.fixture.d.ts","sourceRoot":"","sources":["../../../../../../../../../../packages/core/src/infrastructure/services/agents/common/executors/fixtures/spec-analyze.fixture.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,eAAO,MAAM,oBAAoB,wtFA0EhC,CAAC"}

package/dist/packages/core/src/infrastructure/services/agents/common/executors/fixtures/spec-analyze.fixture.js

@@ -1,15 +1,15 @@
 /**
  * Spec (Analyze Phase) Fixture
  *
- * Realistic fixture for the fictional "Add dark-mode toggle to Shep Web UI" feature.
+ * Realistic fixture for the fictional "Add dark-mode toggle to ShipIT Web UI" feature.
  * Passes validateSpecAnalyze() with zero repair iterations.
  */
 export const SPEC_ANALYZE_FIXTURE = `name: dark-mode-toggle
 number: 42
 branch: feat/042-dark-mode-toggle
-oneLiner: Add a dark-mode toggle to the Shep web UI settings panel
+oneLiner: Add a dark-mode toggle to the ShipIT web UI settings panel
 summary: >
-  Introduce a persistent dark-mode toggle to the Shep web UI settings panel that
+  Introduce a persistent dark-mode toggle to the ShipIT web UI settings panel that
   applies a CSS class-based theme, stores the user preference in localStorage, and
   is surfaced as a shadcn/ui Switch component with full Storybook coverage.
 phase: Analysis
@@ -32,10 +32,10 @@ openQuestions: []
 content: |
   ## Problem Statement
 
-  The Shep web UI currently renders only in light mode. Developers working in dark
+  The ShipIT web UI currently renders only in light mode. Developers working in dark
   environments or those who prefer dark themes have no way to switch the UI appearance.
   Adding a first-class dark-mode toggle improves developer experience and demonstrates
-  the Shep settings panel as a configurable surface.
+  the ShipIT settings panel as a configurable surface.
 
   ## Codebase Analysis
 

package/dist/packages/core/src/infrastructure/services/agents/common/executors/fixtures/spec-requirements.fixture.d.ts

@@ -1,8 +1,8 @@
 /**
  * Spec (Requirements Phase) Fixture
  *
- * Realistic fixture for the fictional "Add dark-mode toggle to Shep Web UI" feature.
+ * Realistic fixture for the fictional "Add dark-mode toggle to ShipIT Web UI" feature.
  * Passes validateSpecRequirements() with zero repair iterations.
  */
-export declare const SPEC_REQUIREMENTS_FIXTURE = "name: dark-mode-toggle\nnumber: 42\nbranch: feat/042-dark-mode-toggle\noneLiner: Add a dark-mode toggle to the Shep web UI settings panel\nsummary: >\n  Introduce a persistent dark-mode toggle to the Shep web UI settings panel that\n  applies a CSS class-based theme via Tailwind dark: variants, stores the user\n  preference in localStorage, and is surfaced as a shadcn/ui Switch component\n  with full Storybook coverage and TDD-driven unit tests.\nphase: Requirements\nsizeEstimate: M\n\nrelatedFeatures: []\n\ntechnologies:\n  - React 19\n  - Next.js 16 (App Router)\n  - Tailwind CSS v4\n  - shadcn/ui\n  - Storybook\n  - TypeScript\n  - localStorage Web API\n\nrelatedLinks: []\n\nopenQuestions:\n  - question: 'Where should the dark-mode preference be persisted?'\n    resolved: true\n    options:\n      - option: 'localStorage only'\n        description: >\n          Store the theme preference in localStorage. Zero backend changes,\n          instant read on page load, and no need for a settings schema migration.\n          The ThemeProvider reads the key on mount and writes on toggle.\n        selected: true\n      - option: 'SQLite settings via backend API'\n        description: >\n          Persist the preference in the Shep SQLite settings store alongside\n          other settings. Syncs across devices but requires API changes and a\n          settings migration \u2014 out of scope for this feature.\n        selected: false\n    selectionRationale: >\n      localStorage is the conventional approach for client-side theme preferences\n      and requires no backend changes. The Shep settings API is out of scope for\n      this feature; localStorage ships the value faster with zero migration risk.\n    answer: 'localStorage only'\n\n  - question: 'How should the CSS dark-mode implementation be applied?'\n    resolved: true\n    options:\n      - option: 'Tailwind CSS class-based dark mode (dark: modifier)'\n        description: >\n          Add the dark class to the html element and use Tailwind dark: modifier\n          on all themed elements. Supported natively in Tailwind CSS v4 and fully\n          compatible with the shadcn/ui component library.\n        selected: true\n      - option: 'CSS custom properties via a custom ThemeProvider stylesheet'\n        description: >\n          Define a set of CSS custom properties (--color-bg, --color-text, etc.)\n          and swap them by toggling a data attribute. More flexible but requires\n          redefining all existing color tokens \u2014 a large change surface.\n        selected: false\n    selectionRationale: >\n      Tailwind CSS v4 with dark: modifier is already the standard in this codebase.\n      All shadcn/ui components are built to accept Tailwind dark: variants. Using\n      the dark class on html is the minimal, zero-extra-dependency approach.\n    answer: 'Tailwind CSS class-based dark mode (dark: modifier)'\n\ncontent: |\n  ## Problem Statement\n\n  The Shep web UI currently renders only in light mode. Developers working in dark\n  environments or those who prefer dark themes have no way to switch the UI appearance.\n\n  ## Success Criteria\n\n  - [ ] A ThemeProvider wraps the root layout and provides a useTheme hook\n  - [ ] A ThemeToggle component renders in the settings panel with a Switch and label\n  - [ ] Clicking the toggle switches the html element class between light and dark\n  - [ ] The preference persists across page refreshes via localStorage\n  - [ ] All new components have Storybook stories with light and dark variants\n  - [ ] pnpm validate passes with no new errors\n\n  ## Functional Requirements\n\n  - **FR-1**: A ThemeProvider component must wrap the root Next.js App Router layout\n    and provide theme state to the component tree via React context.\n  - **FR-2**: A useTheme hook must expose { theme, toggleTheme } to any component.\n  - **FR-3**: A ThemeToggle component must render a Switch and a label (Dark mode).\n  - **FR-4**: Toggling the Switch must apply the dark CSS class to the html element.\n  - **FR-5**: The selected theme must be persisted to localStorage and restored on load.\n  - **FR-6**: ThemeToggle must appear in the settings panel (features/settings/).\n\n  ## Non-Functional Requirements\n\n  - **NFR-1**: Theme switch must complete within one animation frame (no FOUC).\n  - **NFR-2**: All new components must have Storybook stories per project conventions.\n  - **NFR-3**: No new npm dependencies may be added; use existing React, Tailwind, shadcn/ui.\n  - **NFR-4**: Each new file must stay within the 150-line project guideline.\n\n  ## Product Questions & AI Recommendations\n\n  | # | Question | AI Recommendation | Rationale |\n  | - | -------- | ----------------- | --------- |\n  | 1 | Persistence layer? | localStorage | Zero backend changes required |\n  | 2 | CSS implementation? | Tailwind dark: class | Already standard in the codebase |\n\n  ## Affected Areas\n\n  | Area | Impact | Reasoning |\n  | ---- | ------ | --------- |\n  | src/presentation/web/components/features/settings/ | High | Toggle component added here |\n  | src/presentation/web/app/layout.tsx | Medium | ThemeProvider wrapper added |\n  | src/presentation/web/components/common/ | Medium | ThemeToggle and ThemeProvider created |\n\n  ## Dependencies\n\n  - shadcn/ui Switch and Label components (already installed)\n  - React context API (built-in)\n  - localStorage Web API (built-in)\n\n  ## Size Estimate\n\n  **M (days)** \u2014 3 phases: context + provider, toggle component, settings integration.\n";
+export declare const SPEC_REQUIREMENTS_FIXTURE = "name: dark-mode-toggle\nnumber: 42\nbranch: feat/042-dark-mode-toggle\noneLiner: Add a dark-mode toggle to the ShipIT web UI settings panel\nsummary: >\n  Introduce a persistent dark-mode toggle to the ShipIT web UI settings panel that\n  applies a CSS class-based theme via Tailwind dark: variants, stores the user\n  preference in localStorage, and is surfaced as a shadcn/ui Switch component\n  with full Storybook coverage and TDD-driven unit tests.\nphase: Requirements\nsizeEstimate: M\n\nrelatedFeatures: []\n\ntechnologies:\n  - React 19\n  - Next.js 16 (App Router)\n  - Tailwind CSS v4\n  - shadcn/ui\n  - Storybook\n  - TypeScript\n  - localStorage Web API\n\nrelatedLinks: []\n\nopenQuestions:\n  - question: 'Where should the dark-mode preference be persisted?'\n    resolved: true\n    options:\n      - option: 'localStorage only'\n        description: >\n          Store the theme preference in localStorage. Zero backend changes,\n          instant read on page load, and no need for a settings schema migration.\n          The ThemeProvider reads the key on mount and writes on toggle.\n        selected: true\n      - option: 'SQLite settings via backend API'\n        description: >\n          Persist the preference in the ShipIT SQLite settings store alongside\n          other settings. Syncs across devices but requires API changes and a\n          settings migration \u2014 out of scope for this feature.\n        selected: false\n    selectionRationale: >\n      localStorage is the conventional approach for client-side theme preferences\n      and requires no backend changes. The ShipIT settings API is out of scope for\n      this feature; localStorage ships the value faster with zero migration risk.\n    answer: 'localStorage only'\n\n  - question: 'How should the CSS dark-mode implementation be applied?'\n    resolved: true\n    options:\n      - option: 'Tailwind CSS class-based dark mode (dark: modifier)'\n        description: >\n          Add the dark class to the html element and use Tailwind dark: modifier\n          on all themed elements. Supported natively in Tailwind CSS v4 and fully\n          compatible with the shadcn/ui component library.\n        selected: true\n      - option: 'CSS custom properties via a custom ThemeProvider stylesheet'\n        description: >\n          Define a set of CSS custom properties (--color-bg, --color-text, etc.)\n          and swap them by toggling a data attribute. More flexible but requires\n          redefining all existing color tokens \u2014 a large change surface.\n        selected: false\n    selectionRationale: >\n      Tailwind CSS v4 with dark: modifier is already the standard in this codebase.\n      All shadcn/ui components are built to accept Tailwind dark: variants. Using\n      the dark class on html is the minimal, zero-extra-dependency approach.\n    answer: 'Tailwind CSS class-based dark mode (dark: modifier)'\n\ncontent: |\n  ## Problem Statement\n\n  The ShipIT web UI currently renders only in light mode. Developers working in dark\n  environments or those who prefer dark themes have no way to switch the UI appearance.\n\n  ## Success Criteria\n\n  - [ ] A ThemeProvider wraps the root layout and provides a useTheme hook\n  - [ ] A ThemeToggle component renders in the settings panel with a Switch and label\n  - [ ] Clicking the toggle switches the html element class between light and dark\n  - [ ] The preference persists across page refreshes via localStorage\n  - [ ] All new components have Storybook stories with light and dark variants\n  - [ ] pnpm validate passes with no new errors\n\n  ## Functional Requirements\n\n  - **FR-1**: A ThemeProvider component must wrap the root Next.js App Router layout\n    and provide theme state to the component tree via React context.\n  - **FR-2**: A useTheme hook must expose { theme, toggleTheme } to any component.\n  - **FR-3**: A ThemeToggle component must render a Switch and a label (Dark mode).\n  - **FR-4**: Toggling the Switch must apply the dark CSS class to the html element.\n  - **FR-5**: The selected theme must be persisted to localStorage and restored on load.\n  - **FR-6**: ThemeToggle must appear in the settings panel (features/settings/).\n\n  ## Non-Functional Requirements\n\n  - **NFR-1**: Theme switch must complete within one animation frame (no FOUC).\n  - **NFR-2**: All new components must have Storybook stories per project conventions.\n  - **NFR-3**: No new npm dependencies may be added; use existing React, Tailwind, shadcn/ui.\n  - **NFR-4**: Each new file must stay within the 150-line project guideline.\n\n  ## Product Questions & AI Recommendations\n\n  | # | Question | AI Recommendation | Rationale |\n  | - | -------- | ----------------- | --------- |\n  | 1 | Persistence layer? | localStorage | Zero backend changes required |\n  | 2 | CSS implementation? | Tailwind dark: class | Already standard in the codebase |\n\n  ## Affected Areas\n\n  | Area | Impact | Reasoning |\n  | ---- | ------ | --------- |\n  | src/presentation/web/components/features/settings/ | High | Toggle component added here |\n  | src/presentation/web/app/layout.tsx | Medium | ThemeProvider wrapper added |\n  | src/presentation/web/components/common/ | Medium | ThemeToggle and ThemeProvider created |\n\n  ## Dependencies\n\n  - shadcn/ui Switch and Label components (already installed)\n  - React context API (built-in)\n  - localStorage Web API (built-in)\n\n  ## Size Estimate\n\n  **M (days)** \u2014 3 phases: context + provider, toggle component, settings integration.\n";
 //# sourceMappingURL=spec-requirements.fixture.d.ts.map

package/dist/packages/core/src/infrastructure/services/agents/common/executors/fixtures/spec-requirements.fixture.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"spec-requirements.fixture.d.ts","sourceRoot":"","sources":["../../../../../../../../../../packages/core/src/infrastructure/services/agents/common/executors/fixtures/spec-requirements.fixture.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,eAAO,MAAM,yBAAyB,m8KA4HrC,CAAC"}
+{"version":3,"file":"spec-requirements.fixture.d.ts","sourceRoot":"","sources":["../../../../../../../../../../packages/core/src/infrastructure/services/agents/common/executors/fixtures/spec-requirements.fixture.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,eAAO,MAAM,yBAAyB,68KA4HrC,CAAC"}

package/dist/packages/core/src/infrastructure/services/agents/common/executors/fixtures/spec-requirements.fixture.js

@@ -1,15 +1,15 @@
 /**
  * Spec (Requirements Phase) Fixture
  *
- * Realistic fixture for the fictional "Add dark-mode toggle to Shep Web UI" feature.
+ * Realistic fixture for the fictional "Add dark-mode toggle to ShipIT Web UI" feature.
  * Passes validateSpecRequirements() with zero repair iterations.
  */
 export const SPEC_REQUIREMENTS_FIXTURE = `name: dark-mode-toggle
 number: 42
 branch: feat/042-dark-mode-toggle
-oneLiner: Add a dark-mode toggle to the Shep web UI settings panel
+oneLiner: Add a dark-mode toggle to the ShipIT web UI settings panel
 summary: >
-  Introduce a persistent dark-mode toggle to the Shep web UI settings panel that
+  Introduce a persistent dark-mode toggle to the ShipIT web UI settings panel that
   applies a CSS class-based theme via Tailwind dark: variants, stores the user
   preference in localStorage, and is surfaced as a shadcn/ui Switch component
   with full Storybook coverage and TDD-driven unit tests.
@@ -41,13 +41,13 @@ openQuestions:
         selected: true
       - option: 'SQLite settings via backend API'
         description: >
-          Persist the preference in the Shep SQLite settings store alongside
+          Persist the preference in the ShipIT SQLite settings store alongside
           other settings. Syncs across devices but requires API changes and a
           settings migration — out of scope for this feature.
         selected: false
     selectionRationale: >
       localStorage is the conventional approach for client-side theme preferences
-      and requires no backend changes. The Shep settings API is out of scope for
+      and requires no backend changes. The ShipIT settings API is out of scope for
       this feature; localStorage ships the value faster with zero migration risk.
     answer: 'localStorage only'
 
@@ -75,7 +75,7 @@ openQuestions:
 content: |
   ## Problem Statement
 
-  The Shep web UI currently renders only in light mode. Developers working in dark
+  The ShipIT web UI currently renders only in light mode. Developers working in dark
   environments or those who prefer dark themes have no way to switch the UI appearance.
 
   ## Success Criteria

package/dist/packages/core/src/infrastructure/services/agents/common/executors/fixtures/tasks.fixture.d.ts

@@ -1,5 +1,5 @@
 /**
- * Tasks Fixture — fictional "Add dark-mode toggle to Shep Web UI" feature.
+ * Tasks Fixture — fictional "Add dark-mode toggle to ShipIT Web UI" feature.
  * Passes validateTasks() against plan phase IDs [phase-1, phase-2, phase-3].
  */
 export declare const TASKS_FIXTURE = "name: dark-mode-toggle\nsummary: >\n  8 tasks across 3 phases: ThemeProvider context (phase-1), ThemeToggle component\n  (phase-2), settings panel integration and validation (phase-3).\n\nrelatedFeatures: []\ntechnologies: []\nrelatedLinks: []\n\ntasks:\n  - id: task-1\n    phaseId: phase-1\n    title: 'Create ThemeProvider and useTheme hook'\n    description: 'ThemeProvider managing light/dark state via React context with localStorage persistence.'\n    state: Todo\n    dependencies: []\n    acceptanceCriteria:\n      - 'ThemeProvider renders children without error'\n      - 'useTheme returns { theme, toggleTheme } where theme is \"light\" or \"dark\"'\n      - 'toggleTheme() switches theme and toggles html element dark class'\n      - 'Theme persists to localStorage key \"shep-theme\" on toggle'\n    tdd:\n      red: ['Write test: useTheme default is \"light\" with no localStorage entry', 'Write test: toggleTheme() adds dark class to html element']\n      green: ['Implement ThemeProvider reading localStorage and calling classList.toggle', 'Implement useTheme hook calling useContext(ThemeContext)']\n      refactor: ['Extract THEME_KEY constant; add sanitization for non-light/dark values']\n    estimatedEffort: '2h'\n\n  - id: task-2\n    phaseId: phase-1\n    title: 'Write unit tests for ThemeProvider edge cases'\n    description: 'Cover edge cases: invalid stored value, double-toggle cycle, SSR safety.'\n    state: Todo\n    dependencies: ['task-1']\n    acceptanceCriteria:\n      - 'Test: invalid localStorage value \"purple\" defaults to \"light\"'\n      - 'Test: toggling twice returns to original theme'\n      - 'Test: ThemeProvider handles window being undefined (SSR safety)'\n    tdd:\n      red: ['Write test: localStorage \"purple\" \u2192 theme defaults to \"light\"']\n      green: ['Sanitization branch handles all non-light/dark values']\n      refactor: ['Consolidate theme validation into isValidTheme() helper']\n    estimatedEffort: '1h'\n\n  - id: task-3\n    phaseId: phase-2\n    title: 'Create ThemeToggle component'\n    description: 'shadcn/ui Switch + Label component wired to useTheme(). onClick calls toggleTheme().'\n    state: Todo\n    dependencies: ['task-1']\n    acceptanceCriteria:\n      - 'ThemeToggle renders a Switch with aria-label \"Toggle dark mode\"'\n      - 'Switch checked reflects current theme (\"dark\" = checked)'\n      - 'Clicking Switch calls toggleTheme() exactly once'\n      - 'Component file is <= 50 lines'\n    tdd:\n      red: ['Write test: Switch checked is false when theme is \"light\"', 'Write test: Switch click triggers toggleTheme()']\n      green: ['Implement ThemeToggle with Switch checked wired to theme === \"dark\"']\n      refactor: ['Extract aria-label constant; remove any inline styles']\n    estimatedEffort: '1h'\n\n  - id: task-4\n    phaseId: phase-2\n    title: 'Create Storybook story for ThemeToggle'\n    description: 'theme-toggle.stories.tsx with Default and DarkMode variants using ThemeProvider decorator.'\n    state: Todo\n    dependencies: ['task-3']\n    acceptanceCriteria:\n      - 'Story includes Default and DarkMode variants with ThemeProvider decorator'\n      - 'pnpm dev:storybook runs without error for the new story'\n    tdd: null\n    estimatedEffort: '30min'\n\n  - id: task-5\n    phaseId: phase-2\n    title: 'Write integration test for ThemeToggle + ThemeProvider'\n    description: 'Mount ThemeProvider wrapping ThemeToggle; assert full toggle cycle including localStorage.'\n    state: Todo\n    dependencies: ['task-3']\n    acceptanceCriteria:\n      - 'After clicking Toggle: html has dark class, localStorage has \"dark\"'\n      - 'After clicking Toggle again: html has no dark class, localStorage has \"light\"'\n    tdd:\n      red: ['Write integration test: html class and localStorage after two toggle cycles']\n      green: ['Test passes with existing ThemeProvider + ThemeToggle implementations']\n      refactor: ['Extract renderWithTheme() test helper for reuse']\n    estimatedEffort: '45min'\n\n  - id: task-6\n    phaseId: phase-3\n    title: 'Wrap root layout in ThemeProvider'\n    description: 'Update app/layout.tsx to wrap children with ThemeProvider.'\n    state: Todo\n    dependencies: ['task-1']\n    acceptanceCriteria:\n      - 'layout.tsx imports ThemeProvider and wraps children'\n      - 'Existing Playwright e2e tests continue to pass'\n    tdd:\n      red: ['Write e2e test: dark class persists after page reload when toggled']\n      green: ['Add ThemeProvider wrapping children in layout.tsx']\n      refactor: ['Ensure import order follows project eslint rules']\n    estimatedEffort: '30min'\n\n  - id: task-7\n    phaseId: phase-3\n    title: 'Add ThemeToggle to settings panel'\n    description: 'Add ThemeToggle to the Appearance section of settings-panel.tsx.'\n    state: Todo\n    dependencies: ['task-3', 'task-6']\n    acceptanceCriteria:\n      - 'settings-panel.tsx imports and renders ThemeToggle in the Appearance section'\n      - 'ThemeToggle is visible and functional in the running web UI'\n    tdd:\n      red: ['Write unit test: ThemeToggle is present in rendered SettingsPanel']\n      green: ['Add import and render ThemeToggle in the Appearance section']\n      refactor: ['Ensure Appearance section heading is semantically correct (h2/h3)']\n    estimatedEffort: '30min'\n\n  - id: task-8\n    phaseId: phase-3\n    title: 'Run full validation and fix any issues'\n    description: 'Run pnpm validate and pnpm test; fix any failures before marking complete.'\n    state: Todo\n    dependencies: ['task-6', 'task-7']\n    acceptanceCriteria:\n      - 'pnpm lint passes with no errors'\n      - 'pnpm typecheck passes with no errors'\n      - 'pnpm test passes with no failures'\n      - 'pnpm build completes successfully'\n    tdd: null\n    estimatedEffort: '30min'\n\ntotalEstimate: '7.25h'\nopenQuestions: []\n\ncontent: |\n  ## Summary\n\n  Phase-1 builds ThemeProvider + useTheme hook with full test coverage.\n  Phase-2 creates ThemeToggle in isolation with Storybook stories and integration tests.\n  Phase-3 wires the provider into the root layout, adds the toggle to the settings panel,\n  then validates with pnpm validate + pnpm test.\n";

package/dist/packages/core/src/infrastructure/services/agents/common/executors/fixtures/tasks.fixture.js

@@ -1,5 +1,5 @@
 /**
- * Tasks Fixture — fictional "Add dark-mode toggle to Shep Web UI" feature.
+ * Tasks Fixture — fictional "Add dark-mode toggle to ShipIT Web UI" feature.
  * Passes validateTasks() against plan phase IDs [phase-1, phase-2, phase-3].
  */
 export const TASKS_FIXTURE = `name: dark-mode-toggle

package/dist/packages/core/src/infrastructure/services/agents/feature-agent/nodes/prompts/evidence-prompts.js

@@ -50,7 +50,7 @@ ${tasksContent}
 
 Save all evidence files to BOTH locations:
 
-1. **Shipit AI home folder** (persistent local storage):
+1. **ShipIT AI home folder** (persistent local storage):
    \`mkdir -p ${shipitAiEvidenceDir}/\`
    Save each file here first.
 

package/dist/packages/core/src/infrastructure/services/agents/feature-agent/nodes/prompts/merge-prompts.js

@@ -155,7 +155,7 @@ export function buildCommitPushPrPrompt(state, branch, baseBranch, repoUrl) {
    - Write a descriptive PR title using conventional commit format
    - Write a rich PR body that summarizes the changes using the spec context below
    - The PR body MUST end with this exact branding line (on its own line): \`${PR_BRANDING}\`
-   - Do NOT include any other attribution footer (e.g. "Generated with Claude Code" or similar) — only the Shep branding line above`);
+   - Do NOT include any other attribution footer (e.g. "Generated with Claude Code" or similar) — only the ShipIT branding line above`);
     }
     const resumeContext = buildResumeContext(state.resumeReason);
     return `${resumeContext}You are performing git operations in a feature worktree.

package/dist/packages/core/src/infrastructure/services/environment-detector.service.d.ts

@@ -0,0 +1,38 @@
+/**
+ * Environment Detector Service Implementation
+ *
+ * Probes environment variables and system binaries to detect the user's
+ * default editor, shell, and terminal emulator. Used during onboarding
+ * to pre-populate settings with sensible defaults.
+ */
+import type { IEnvironmentDetectorService, DetectedEnvironment, AvailableEditorEntry, AvailableShellEntry } from '../../application/ports/output/services/environment-detector.service.js';
+import type { IToolInstallerService } from '../../application/ports/output/services/tool-installer.service.js';
+export declare class EnvironmentDetectorServiceImpl implements IEnvironmentDetectorService {
+    private readonly toolInstallerService;
+    constructor(toolInstallerService: IToolInstallerService);
+    /**
+     * Detect default editor, shell, and terminal from environment variables.
+     */
+    detectDefaults(): DetectedEnvironment;
+    /**
+     * List all known editors with their availability on the current system.
+     */
+    listAvailableEditors(): Promise<AvailableEditorEntry[]>;
+    /**
+     * List all known shells with their availability on the current system.
+     */
+    listAvailableShells(): Promise<AvailableShellEntry[]>;
+    /**
+     * Detect the default editor from $VISUAL or $EDITOR environment variables.
+     */
+    private detectEditor;
+    /**
+     * Detect the default shell from $SHELL or Windows environment.
+     */
+    private detectShell;
+    /**
+     * Detect the default terminal from $TERM_PROGRAM or $TERM.
+     */
+    private detectTerminal;
+}
+//# sourceMappingURL=environment-detector.service.d.ts.map

package/dist/packages/core/src/infrastructure/services/environment-detector.service.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"environment-detector.service.d.ts","sourceRoot":"","sources":["../../../../../../packages/core/src/infrastructure/services/environment-detector.service.ts"],"names":[],"mappings":"AAAA;;;;;;GAMG;AAOH,OAAO,KAAK,EACV,2BAA2B,EAC3B,mBAAmB,EACnB,oBAAoB,EACpB,mBAAmB,EACpB,MAAM,yEAAyE,CAAC;AACjF,OAAO,KAAK,EAAE,qBAAqB,EAAE,MAAM,mEAAmE,CAAC;AA0E/G,qBACa,8BAA+B,YAAW,2BAA2B;IAG9E,OAAO,CAAC,QAAQ,CAAC,oBAAoB;gBAApB,oBAAoB,EAAE,qBAAqB;IAG9D;;OAEG;IACH,cAAc,IAAI,mBAAmB;IAQrC;;OAEG;IACG,oBAAoB,IAAI,OAAO,CAAC,oBAAoB,EAAE,CAAC;IAe7D;;OAEG;IACG,mBAAmB,IAAI,OAAO,CAAC,mBAAmB,EAAE,CAAC;IAoC3D;;OAEG;IACH,OAAO,CAAC,YAAY;IAUpB;;OAEG;IACH,OAAO,CAAC,WAAW;IAmBnB;;OAEG;IACH,OAAO,CAAC,cAAc;CAcvB"}

package/dist/packages/core/src/infrastructure/services/environment-detector.service.js

@@ -0,0 +1,196 @@
+/**
+ * Environment Detector Service Implementation
+ *
+ * Probes environment variables and system binaries to detect the user's
+ * default editor, shell, and terminal emulator. Used during onboarding
+ * to pre-populate settings with sensible defaults.
+ */
+var __decorate = (this && this.__decorate) || function (decorators, target, key, desc) {
+    var c = arguments.length, r = c < 3 ? target : desc === null ? desc = Object.getOwnPropertyDescriptor(target, key) : desc, d;
+    if (typeof Reflect === "object" && typeof Reflect.decorate === "function") r = Reflect.decorate(decorators, target, key, desc);
+    else for (var i = decorators.length - 1; i >= 0; i--) if (d = decorators[i]) r = (c < 3 ? d(r) : c > 3 ? d(target, key, r) : d(target, key)) || r;
+    return c > 3 && r && Object.defineProperty(target, key, r), r;
+};
+var __metadata = (this && this.__metadata) || function (k, v) {
+    if (typeof Reflect === "object" && typeof Reflect.metadata === "function") return Reflect.metadata(k, v);
+};
+var __param = (this && this.__param) || function (paramIndex, decorator) {
+    return function (target, key) { decorator(target, key, paramIndex); }
+};
+import { injectable, inject } from 'tsyringe';
+import { platform } from 'node:os';
+import path from 'node:path';
+import { EditorType, TerminalType } from '../../domain/generated/output.js';
+import { checkBinaryExists } from './tool-installer/binary-exists.js';
+/**
+ * Maps editor binary basenames to EditorType enum values.
+ */
+const EDITOR_BINARY_MAP = {
+    code: EditorType.VsCode,
+    cursor: EditorType.Cursor,
+    windsurf: EditorType.Windsurf,
+    zed: EditorType.Zed,
+    antigravity: EditorType.Antigravity,
+    agy: EditorType.Antigravity,
+};
+/**
+ * Maps TERM_PROGRAM environment variable values to TerminalType enum values.
+ */
+const TERM_PROGRAM_MAP = {
+    WarpTerminal: TerminalType.Warp,
+    'iTerm.app': TerminalType.ITerm2,
+    Apple_Terminal: TerminalType.System,
+};
+/**
+ * Fallback mapping from $TERM to TerminalType when TERM_PROGRAM is not set.
+ */
+const TERM_FALLBACK_MAP = {
+    alacritty: TerminalType.Alacritty,
+    'xterm-kitty': TerminalType.Kitty,
+};
+/**
+ * Maps shell basenames to canonical shell identifier strings.
+ */
+const SHELL_BASENAME_MAP = {
+    bash: 'bash',
+    zsh: 'zsh',
+    fish: 'fish',
+    sh: 'bash',
+    pwsh: 'powershell',
+    powershell: 'powershell',
+};
+/**
+ * Editor entries mapping tool metadata IDs to EditorType and display names.
+ */
+const EDITOR_ENTRIES = [
+    { toolId: 'vscode', editorType: EditorType.VsCode, name: 'VS Code' },
+    { toolId: 'cursor', editorType: EditorType.Cursor, name: 'Cursor' },
+    { toolId: 'windsurf', editorType: EditorType.Windsurf, name: 'Windsurf' },
+    { toolId: 'zed', editorType: EditorType.Zed, name: 'Zed' },
+    { toolId: 'antigravity', editorType: EditorType.Antigravity, name: 'Antigravity' },
+];
+/**
+ * Shell entries with display names and platform constraints.
+ */
+const SHELL_ENTRIES = [
+    { id: 'bash', name: 'Bash', platforms: null },
+    { id: 'zsh', name: 'Zsh', platforms: ['darwin', 'linux'] },
+    { id: 'fish', name: 'Fish', platforms: ['darwin', 'linux'] },
+    { id: 'powershell', name: 'PowerShell', platforms: null },
+];
+let EnvironmentDetectorServiceImpl = class EnvironmentDetectorServiceImpl {
+    toolInstallerService;
+    constructor(toolInstallerService) {
+        this.toolInstallerService = toolInstallerService;
+    }
+    /**
+     * Detect default editor, shell, and terminal from environment variables.
+     */
+    detectDefaults() {
+        return {
+            defaultEditor: this.detectEditor(),
+            defaultShell: this.detectShell(),
+            defaultTerminal: this.detectTerminal(),
+        };
+    }
+    /**
+     * List all known editors with their availability on the current system.
+     */
+    async listAvailableEditors() {
+        const results = [];
+        for (const entry of EDITOR_ENTRIES) {
+            const status = await this.toolInstallerService.checkAvailability(entry.toolId);
+            results.push({
+                id: entry.editorType,
+                name: entry.name,
+                available: status.status === 'available',
+            });
+        }
+        return results;
+    }
+    /**
+     * List all known shells with their availability on the current system.
+     */
+    async listAvailableShells() {
+        const currentPlatform = platform();
+        const results = [];
+        for (const entry of SHELL_ENTRIES) {
+            // Skip shells not available on this platform
+            if (entry.platforms && !entry.platforms.includes(currentPlatform)) {
+                continue;
+            }
+            let available = false;
+            if (entry.id === 'powershell') {
+                // Check pwsh first (cross-platform PowerShell), then powershell (Windows-only)
+                const pwshResult = await checkBinaryExists('pwsh');
+                if (pwshResult.found) {
+                    available = true;
+                }
+                else {
+                    const powershellResult = await checkBinaryExists('powershell');
+                    available = powershellResult.found;
+                }
+            }
+            else {
+                const result = await checkBinaryExists(entry.id);
+                available = result.found;
+            }
+            results.push({
+                id: entry.id,
+                name: entry.name,
+                available,
+            });
+        }
+        return results;
+    }
+    /**
+     * Detect the default editor from $VISUAL or $EDITOR environment variables.
+     */
+    detectEditor() {
+        const editorEnv = process.env.VISUAL ?? process.env.EDITOR;
+        if (!editorEnv) {
+            return null;
+        }
+        const basename = path.basename(editorEnv);
+        return EDITOR_BINARY_MAP[basename] ?? null;
+    }
+    /**
+     * Detect the default shell from $SHELL or Windows environment.
+     */
+    detectShell() {
+        const shellEnv = process.env.SHELL;
+        if (shellEnv) {
+            const basename = path.basename(shellEnv);
+            return SHELL_BASENAME_MAP[basename] ?? basename;
+        }
+        // Windows fallback: no $SHELL env var
+        if (platform() === 'win32') {
+            if (process.env.PSModulePath) {
+                return 'powershell';
+            }
+            return 'bash';
+        }
+        return null;
+    }
+    /**
+     * Detect the default terminal from $TERM_PROGRAM or $TERM.
+     */
+    detectTerminal() {
+        const termProgram = process.env.TERM_PROGRAM;
+        if (termProgram) {
+            return TERM_PROGRAM_MAP[termProgram] ?? null;
+        }
+        // Fallback to $TERM for terminals that only set this
+        const term = process.env.TERM;
+        if (term) {
+            return TERM_FALLBACK_MAP[term] ?? null;
+        }
+        return null;
+    }
+};
+EnvironmentDetectorServiceImpl = __decorate([
+    injectable(),
+    __param(0, inject('IToolInstallerService')),
+    __metadata("design:paramtypes", [Object])
+], EnvironmentDetectorServiceImpl);
+export { EnvironmentDetectorServiceImpl };

package/dist/packages/core/src/infrastructure/services/filesystem/shipit-ai-directory.service.d.ts

@@ -1,5 +1,5 @@
 /**
- * Shipit AI Directory Service
+ * ShipIT AI Directory Service
  *
  * Manages the ~/.shipit-ai/ directory for global settings and data storage.
  * Ensures directory exists with correct permissions before database operations.
@@ -7,7 +7,7 @@
  * Supports SHIPIT_AI_HOME env var for test isolation (overrides default ~/.shipit-ai/).
  */
 /**
- * Gets the path to the Shipit AI home directory.
+ * Gets the path to the ShipIT AI home directory.
  * Uses SHIPIT_AI_HOME env var if set, otherwise ~/.shipit-ai/
  *
  * @returns Path to shipit-ai home directory

package/dist/packages/core/src/infrastructure/services/filesystem/shipit-ai-directory.service.js

@@ -1,5 +1,5 @@
 /**
- * Shipit AI Directory Service
+ * ShipIT AI Directory Service
  *
  * Manages the ~/.shipit-ai/ directory for global settings and data storage.
  * Ensures directory exists with correct permissions before database operations.
@@ -11,14 +11,14 @@ import { homedir } from 'node:os';
 import { join } from 'node:path';
 import { existsSync } from 'node:fs';
 /**
- * Resolves the Shipit AI home directory.
+ * Resolves the ShipIT AI home directory.
  * Respects SHIPIT_AI_HOME env var for test isolation, falls back to ~/.shipit-ai/
  */
 function resolveShipitAiHomeDir() {
     return process.env.SHIPIT_AI_HOME ?? join(homedir(), '.shipit-ai');
 }
 /**
- * Gets the path to the Shipit AI home directory.
+ * Gets the path to the ShipIT AI home directory.
  * Uses SHIPIT_AI_HOME env var if set, otherwise ~/.shipit-ai/
  *
  * @returns Path to shipit-ai home directory
@@ -73,6 +73,6 @@ export async function ensureShipitAiDirectory() {
         });
     }
     catch (error) {
-        throw new Error(`Failed to create Shipit AI directory at ${shipitAiDir}: ${error instanceof Error ? error.message : String(error)}`);
+        throw new Error(`Failed to create ShipIT AI directory at ${shipitAiDir}: ${error instanceof Error ? error.message : String(error)}`);
     }
 }

package/dist/packages/core/src/infrastructure/services/git/pr-branding.d.ts

@@ -2,16 +2,16 @@
  * PR Branding
  *
  * Centralizes the branding footer used in pull request bodies
- * created by Shipit AI. Ensures consistent attribution across all
+ * created by ShipIT AI. Ensures consistent attribution across all
  * PR creation paths (agent-driven, fork-and-PR, etc.).
  */
 /** The branding line to append to PR bodies. */
-export declare const PR_BRANDING = "Built with Shipit AI \uD83D\uDC11 [Shipit AI Bot](https://github.com/jrmatherly/shipit)";
+export declare const PR_BRANDING = "Built with ShipIT AI \uD83D\uDC11 [ShipIT AI Bot](https://github.com/jrmatherly/shipit)";
 /**
- * Ensure a PR body carries the correct Shipit AI branding.
+ * Ensure a PR body carries the correct ShipIT AI branding.
  *
  * 1. Strips any unwanted AI-tool attribution footers
- * 2. Appends the Shipit AI branding line if not already present
+ * 2. Appends the ShipIT AI branding line if not already present
  */
 export declare function applyPrBranding(body: string): string;
 //# sourceMappingURL=pr-branding.d.ts.map

package/dist/packages/core/src/infrastructure/services/git/pr-branding.js

@@ -2,21 +2,21 @@
  * PR Branding
  *
  * Centralizes the branding footer used in pull request bodies
- * created by Shipit AI. Ensures consistent attribution across all
+ * created by ShipIT AI. Ensures consistent attribution across all
  * PR creation paths (agent-driven, fork-and-PR, etc.).
  */
 /** The branding line to append to PR bodies. */
-export const PR_BRANDING = 'Built with Shipit AI \uD83D\uDC11 [Shipit AI Bot](https://github.com/jrmatherly/shipit)';
+export const PR_BRANDING = 'Built with ShipIT AI \uD83D\uDC11 [ShipIT AI Bot](https://github.com/jrmatherly/shipit)';
 /**
  * Pattern matching common AI-tool attribution footers that should be
  * replaced (e.g. "Generated with Claude Code", "Co-Authored-By: Claude").
  */
 const UNWANTED_BRANDING_PATTERN = /\n*(?:🤖\s*)?Generated with \[Claude Code\]\(https:\/\/claude\.com\/claude-code\)\s*/gi;
 /**
- * Ensure a PR body carries the correct Shipit AI branding.
+ * Ensure a PR body carries the correct ShipIT AI branding.
  *
  * 1. Strips any unwanted AI-tool attribution footers
- * 2. Appends the Shipit AI branding line if not already present
+ * 2. Appends the ShipIT AI branding line if not already present
  */
 export function applyPrBranding(body) {
     // Strip unwanted branding

package/dist/packages/core/src/infrastructure/services/interactive/feature-context.builder.d.ts

@@ -2,7 +2,7 @@
  * Feature Context Builder
  *
  * Builds the system prompt context for the interactive agent session.
- * Includes Shipit AI identity, CLI reference, feature context, and behavioral guidelines.
+ * Includes ShipIT AI identity, CLI reference, feature context, and behavioral guidelines.
  * The output string is suitable for use as systemPrompt content in SDK sessions.
  */
 import type { Feature } from '../../../domain/generated/output.js';