@shipit-ai/cli 1.164.2-pr11.775607f → 1.164.2-pr6.3fe19cf

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 ShipIT Web UI" feature.
+ * Realistic fixture for the fictional "Add dark-mode toggle to Shep 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 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";
+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";
 //# 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,68KA4HrC,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,m8KA4HrC,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 ShipIT Web UI" feature.
+ * Realistic fixture for the fictional "Add dark-mode toggle to Shep 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 ShipIT web UI settings panel
+oneLiner: Add a dark-mode toggle to the Shep web UI settings panel
 summary: >
-  Introduce a persistent dark-mode toggle to the ShipIT web UI settings panel that
+  Introduce a persistent dark-mode toggle to the Shep 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 ShipIT SQLite settings store alongside
+          Persist the preference in the Shep 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 ShipIT settings API is out of scope for
+      and requires no backend changes. The Shep 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 ShipIT web UI currently renders only in light mode. Developers working in dark
+  The Shep 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 ShipIT Web UI" feature.
+ * Tasks Fixture — fictional "Add dark-mode toggle to Shep 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 ShipIT Web UI" feature.
+ * Tasks Fixture — fictional "Add dark-mode toggle to Shep 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 ShipIT branding line above`);
+   - Do NOT include any other attribution footer (e.g. "Generated with Claude Code" or similar) — only the Shep 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/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';

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

@@ -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 { execFileSync } from 'node:child_process';
@@ -81,9 +81,9 @@ export class FeatureContextBuilder {
         }
         const sections = [];
         // ── Identity ──────────────────────────────────────────────────────────
-        sections.push(`# ShipIT AI Interactive Agent
-You are **ShipIT AI** — the interactive AI assistant for the ShipIT AI SDLC platform.
-ShipIT AI is an Autonomous AI Native SDLC Platform that automates the development
+        sections.push(`# Shipit AI Interactive Agent
+You are **Shipit AI** — the interactive AI assistant for the Shipit AI SDLC platform.
+Shipit AI is an Autonomous AI Native SDLC Platform that automates the development
 cycle from idea to deploy.
 
 Version: ${version}
@@ -99,11 +99,11 @@ Platform: ${process.platform} (${process.arch})`);
 - When you DO act, be thorough and explain what you did.
 - You have full access to the worktree via your tools (git, gh, filesystem,
   bash, read, write, edit, grep, glob). Use them proactively.
-- You know the ShipIT AI CLI inside out. Help users with any shipit-ai command.
+- You know the Shipit AI CLI inside out. Help users with any shipit-ai command.
 - When working on this feature, stay focused on the feature context below.
-- If the user asks about ShipIT AI itself, answer from your knowledge of the CLI.`);
+- If the user asks about Shipit AI itself, answer from your knowledge of the CLI.`);
         // ── CLI Reference ─────────────────────────────────────────────────────
-        sections.push(`## ShipIT AI CLI Reference
+        sections.push(`## Shipit AI CLI Reference
 \`\`\`
 ${getCliHelpText()}
 \`\`\``);

package/dist/packages/core/src/infrastructure/services/port.service.d.ts

@@ -4,7 +4,7 @@
  * Port availability checking and auto-increment logic for the web server.
  * Uses node:net try-bind pattern (same approach as Vite).
  */
-/** Default port for the ShipIT web UI */
+/** Default port for the Shep web UI */
 export declare const DEFAULT_PORT = 4050;
 /** Maximum number of ports to try before giving up */
 export declare const MAX_PORT_ATTEMPTS = 20;

package/dist/packages/core/src/infrastructure/services/port.service.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"port.service.d.ts","sourceRoot":"","sources":["../../../../../../packages/core/src/infrastructure/services/port.service.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAIH,yCAAyC;AACzC,eAAO,MAAM,YAAY,OAAO,CAAC;AAEjC,sDAAsD;AACtD,eAAO,MAAM,iBAAiB,KAAK,CAAC;AAKpC;;GAEG;AACH,wBAAsB,eAAe,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC,CAgBpE;AAED;;;GAGG;AACH,wBAAsB,iBAAiB,CACrC,SAAS,EAAE,MAAM,EACjB,WAAW,GAAE,MAA0B,GACtC,OAAO,CAAC,MAAM,CAAC,CAejB"}
+{"version":3,"file":"port.service.d.ts","sourceRoot":"","sources":["../../../../../../packages/core/src/infrastructure/services/port.service.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAIH,uCAAuC;AACvC,eAAO,MAAM,YAAY,OAAO,CAAC;AAEjC,sDAAsD;AACtD,eAAO,MAAM,iBAAiB,KAAK,CAAC;AAKpC;;GAEG;AACH,wBAAsB,eAAe,CAAC,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC,OAAO,CAAC,CAgBpE;AAED;;;GAGG;AACH,wBAAsB,iBAAiB,CACrC,SAAS,EAAE,MAAM,EACjB,WAAW,GAAE,MAA0B,GACtC,OAAO,CAAC,MAAM,CAAC,CAejB"}

package/dist/packages/core/src/infrastructure/services/port.service.js

@@ -5,7 +5,7 @@
  * Uses node:net try-bind pattern (same approach as Vite).
  */
 import net from 'node:net';
-/** Default port for the ShipIT web UI */
+/** Default port for the Shep web UI */
 export const DEFAULT_PORT = 4050;
 /** Maximum number of ports to try before giving up */
 export const MAX_PORT_ATTEMPTS = 20;

package/dist/packages/core/src/infrastructure/services/tool-installer/tool-metadata.d.ts

@@ -15,7 +15,7 @@ export interface ToolMetadata {
     /** Detailed description */
     description: string;
     /** Tool tags for grouping in listings. A tool can belong to multiple categories. */
-    tags: ('ide' | 'cli-agent' | 'vcs' | 'terminal' | 'shell')[];
+    tags: ('ide' | 'cli-agent' | 'vcs' | 'terminal')[];
     /** Company or developer name */
     author?: string;
     /** Main website/homepage URL (separate from documentation) */
@@ -71,9 +71,4 @@ export declare function getIdeEntries(): [string, ToolMetadata][];
  * `openDirectory` field. Each entry is [toolId, metadata].
  */
 export declare function getTerminalEntries(): [string, ToolMetadata][];
-/**
- * Returns entries from TOOL_METADATA tagged as "shell".
- * Each entry is [toolId, metadata].
- */
-export declare function getShellEntries(): [string, ToolMetadata][];
 //# sourceMappingURL=tool-metadata.d.ts.map

package/dist/packages/core/src/infrastructure/services/tool-installer/tool-metadata.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"tool-metadata.d.ts","sourceRoot":"","sources":["../../../../../../../packages/core/src/infrastructure/services/tool-installer/tool-metadata.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAMH,MAAM,WAAW,YAAY;IAC3B,kCAAkC;IAClC,IAAI,EAAE,MAAM,CAAC;IAEb,6BAA6B;IAC7B,OAAO,EAAE,MAAM,CAAC;IAEhB,2BAA2B;IAC3B,WAAW,EAAE,MAAM,CAAC;IAEpB,oFAAoF;IACpF,IAAI,EAAE,CAAC,KAAK,GAAG,WAAW,GAAG,KAAK,GAAG,UAAU,GAAG,OAAO,CAAC,EAAE,CAAC;IAE7D,gCAAgC;IAChC,MAAM,CAAC,EAAE,MAAM,CAAC;IAEhB,8DAA8D;IAC9D,OAAO,CAAC,EAAE,MAAM,CAAC;IAEjB,iDAAiD;IACjD,SAAS,CAAC,EAAE,CAAC,OAAO,GAAG,QAAQ,GAAG,OAAO,CAAC,EAAE,CAAC;IAE7C,wCAAwC;IACxC,OAAO,CAAC,EAAE,MAAM,CAAC;IAEjB,6EAA6E;IAC7E,MAAM,EAAE,MAAM,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAExC,6CAA6C;IAC7C,cAAc,EAAE,MAAM,CAAC;IAEvB,wFAAwF;IACxF,QAAQ,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAEjC,2CAA2C;IAC3C,OAAO,EAAE,MAAM,CAAC;IAEhB,iCAAiC;IACjC,gBAAgB,EAAE,MAAM,CAAC;IAEzB,8DAA8D;IAC9D,aAAa,EAAE,MAAM,CAAC;IAEtB,uEAAuE;IACvE,WAAW,CAAC,EAAE,OAAO,CAAC;IAEtB,kFAAkF;IAClF,QAAQ,CAAC,EAAE,OAAO,CAAC;IAEnB;;yGAEqG;IACrG,aAAa,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAEhD;;iGAE6F;IAC7F,YAAY,CAAC,EAAE;QACb,KAAK,CAAC,EAAE,OAAO,CAAC;QAChB,KAAK,CAAC,EAAE,QAAQ,GAAG,SAAS,GAAG,MAAM,CAAC;QACtC,QAAQ,CAAC,EAAE,OAAO,CAAC;KACpB,CAAC;IAEF;;;;wEAIoE;IACpE,eAAe,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CACnD;AAmDD,eAAO,MAAM,aAAa,EAAE,MAAM,CAAC,MAAM,EAAE,YAAY,CAAsB,CAAC;AAE9E;;;;GAIG;AACH,wBAAgB,aAAa,IAAI,CAAC,MAAM,EAAE,YAAY,CAAC,EAAE,CAExD;AAED;;;GAGG;AACH,wBAAgB,kBAAkB,IAAI,CAAC,MAAM,EAAE,YAAY,CAAC,EAAE,CAI7D;AAED;;;GAGG;AACH,wBAAgB,eAAe,IAAI,CAAC,MAAM,EAAE,YAAY,CAAC,EAAE,CAE1D"}
+{"version":3,"file":"tool-metadata.d.ts","sourceRoot":"","sources":["../../../../../../../packages/core/src/infrastructure/services/tool-installer/tool-metadata.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAMH,MAAM,WAAW,YAAY;IAC3B,kCAAkC;IAClC,IAAI,EAAE,MAAM,CAAC;IAEb,6BAA6B;IAC7B,OAAO,EAAE,MAAM,CAAC;IAEhB,2BAA2B;IAC3B,WAAW,EAAE,MAAM,CAAC;IAEpB,oFAAoF;IACpF,IAAI,EAAE,CAAC,KAAK,GAAG,WAAW,GAAG,KAAK,GAAG,UAAU,CAAC,EAAE,CAAC;IAEnD,gCAAgC;IAChC,MAAM,CAAC,EAAE,MAAM,CAAC;IAEhB,8DAA8D;IAC9D,OAAO,CAAC,EAAE,MAAM,CAAC;IAEjB,iDAAiD;IACjD,SAAS,CAAC,EAAE,CAAC,OAAO,GAAG,QAAQ,GAAG,OAAO,CAAC,EAAE,CAAC;IAE7C,wCAAwC;IACxC,OAAO,CAAC,EAAE,MAAM,CAAC;IAEjB,6EAA6E;IAC7E,MAAM,EAAE,MAAM,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAExC,6CAA6C;IAC7C,cAAc,EAAE,MAAM,CAAC;IAEvB,wFAAwF;IACxF,QAAQ,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAEjC,2CAA2C;IAC3C,OAAO,EAAE,MAAM,CAAC;IAEhB,iCAAiC;IACjC,gBAAgB,EAAE,MAAM,CAAC;IAEzB,8DAA8D;IAC9D,aAAa,EAAE,MAAM,CAAC;IAEtB,uEAAuE;IACvE,WAAW,CAAC,EAAE,OAAO,CAAC;IAEtB,kFAAkF;IAClF,QAAQ,CAAC,EAAE,OAAO,CAAC;IAEnB;;yGAEqG;IACrG,aAAa,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;IAEhD;;iGAE6F;IAC7F,YAAY,CAAC,EAAE;QACb,KAAK,CAAC,EAAE,OAAO,CAAC;QAChB,KAAK,CAAC,EAAE,QAAQ,GAAG,SAAS,GAAG,MAAM,CAAC;QACtC,QAAQ,CAAC,EAAE,OAAO,CAAC;KACpB,CAAC;IAEF;;;;wEAIoE;IACpE,eAAe,CAAC,EAAE,MAAM,GAAG,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;CACnD;AAmDD,eAAO,MAAM,aAAa,EAAE,MAAM,CAAC,MAAM,EAAE,YAAY,CAAsB,CAAC;AAE9E;;;;GAIG;AACH,wBAAgB,aAAa,IAAI,CAAC,MAAM,EAAE,YAAY,CAAC,EAAE,CAExD;AAED;;;GAGG;AACH,wBAAgB,kBAAkB,IAAI,CAAC,MAAM,EAAE,YAAY,CAAC,EAAE,CAI7D"}

package/dist/packages/core/src/infrastructure/services/tool-installer/tool-metadata.js

@@ -70,10 +70,3 @@ export function getIdeEntries() {
 export function getTerminalEntries() {
     return Object.entries(TOOL_METADATA).filter(([, meta]) => meta.tags.includes('terminal') && meta.openDirectory != null);
 }
-/**
- * Returns entries from TOOL_METADATA tagged as "shell".
- * Each entry is [toolId, metadata].
- */
-export function getShellEntries() {
-    return Object.entries(TOOL_METADATA).filter(([, meta]) => meta.tags.includes('shell'));
-}

package/dist/packages/core/src/infrastructure/services/tool-installer/tool-metadata.service.d.ts

@@ -8,6 +8,5 @@ export declare class ToolMetadataServiceImpl implements IToolMetadataService {
     getAllToolMetadata(): Record<string, ToolMetadata>;
     getIdeEntries(): [string, ToolMetadata][];
     getTerminalEntries(): [string, ToolMetadata][];
-    getShellEntries(): [string, ToolMetadata][];
 }
 //# sourceMappingURL=tool-metadata.service.d.ts.map

package/dist/packages/core/src/infrastructure/services/tool-installer/tool-metadata.service.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"tool-metadata.service.d.ts","sourceRoot":"","sources":["../../../../../../../packages/core/src/infrastructure/services/tool-installer/tool-metadata.service.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EACV,oBAAoB,EACpB,YAAY,EACb,MAAM,+EAA+E,CAAC;AAQvF;;;GAGG;AACH,qBACa,uBAAwB,YAAW,oBAAoB;IAClE,eAAe,CAAC,MAAM,EAAE,MAAM,GAAG,YAAY,GAAG,SAAS;IAIzD,kBAAkB,IAAI,MAAM,CAAC,MAAM,EAAE,YAAY,CAAC;IAIlD,aAAa,IAAI,CAAC,MAAM,EAAE,YAAY,CAAC,EAAE;IAIzC,kBAAkB,IAAI,CAAC,MAAM,EAAE,YAAY,CAAC,EAAE;IAI9C,eAAe,IAAI,CAAC,MAAM,EAAE,YAAY,CAAC,EAAE;CAG5C"}
+{"version":3,"file":"tool-metadata.service.d.ts","sourceRoot":"","sources":["../../../../../../../packages/core/src/infrastructure/services/tool-installer/tool-metadata.service.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EACV,oBAAoB,EACpB,YAAY,EACb,MAAM,+EAA+E,CAAC;AAGvF;;;GAGG;AACH,qBACa,uBAAwB,YAAW,oBAAoB;IAClE,eAAe,CAAC,MAAM,EAAE,MAAM,GAAG,YAAY,GAAG,SAAS;IAIzD,kBAAkB,IAAI,MAAM,CAAC,MAAM,EAAE,YAAY,CAAC;IAIlD,aAAa,IAAI,CAAC,MAAM,EAAE,YAAY,CAAC,EAAE;IAIzC,kBAAkB,IAAI,CAAC,MAAM,EAAE,YAAY,CAAC,EAAE;CAG/C"}

package/dist/packages/core/src/infrastructure/services/tool-installer/tool-metadata.service.js

@@ -5,7 +5,7 @@ var __decorate = (this && this.__decorate) || function (decorators, target, key,
     return c > 3 && r && Object.defineProperty(target, key, r), r;
 };
 import { injectable } from 'tsyringe';
-import { TOOL_METADATA, getIdeEntries, getTerminalEntries, getShellEntries, } from './tool-metadata.js';
+import { TOOL_METADATA, getIdeEntries, getTerminalEntries } from './tool-metadata.js';
 /**
  * DI-injectable wrapper around the tool metadata module.
  * Delegates to the existing TOOL_METADATA constant and helper functions.
@@ -23,9 +23,6 @@ let ToolMetadataServiceImpl = class ToolMetadataServiceImpl {
     getTerminalEntries() {
         return getTerminalEntries();
     }
-    getShellEntries() {
-        return getShellEntries();
-    }
 };
 ToolMetadataServiceImpl = __decorate([
     injectable()

package/dist/packages/core/src/infrastructure/services/tool-installer/tools/CLAUDE.md

@@ -10,7 +10,7 @@ Files are loaded dynamically by `tool-metadata.ts` — the filename (minus `.jso
 | `name`             | `string`                                    | Yes      | Human-readable display name                                              |
 | `summary`          | `string`                                    | Yes      | One-line description                                                     |
 | `description`      | `string`                                    | Yes      | Detailed description                                                     |
-| `tags`             | `("ide"\|"cli-agent"\|"vcs"\|"terminal"\|"shell")[]` | Yes      | Categories for filtering in UI and CLI                                   |
+| `tags`             | `("ide"\|"cli-agent"\|"vcs"\|"terminal")[]` | Yes      | Categories for filtering in UI and CLI                                   |
 | `iconUrl`          | `string`                                    | No       | URL to SVG/PNG icon (use cdn.simpleicons.org when possible)              |
 | `binary`           | `string \| Record<string,string>`           | Yes      | Binary name for `which` check. Per-platform map if differs               |
 | `packageManager`   | `string`                                    | Yes      | Install method label (apt, brew, curl, manual, download)                 |
@@ -60,7 +60,6 @@ The launcher auto-detects TTY: CLI launch uses `openDirectory`, web launch uses
 | `cli-agent` | Terminal-based AI coding agent | Claude Code, Cursor CLI |
 | `vcs`       | Version control tool           | Git, GitHub CLI         |
 | `terminal`  | Terminal emulator/multiplexer  | tmux, Kitty, Alacritty  |
-| `shell`     | Shell interpreter              | Bash, Zsh, Fish         |
 
 Tools can have multiple tags. A tool appears in all matching filter tabs in the UI.
 

package/dist/src/presentation/cli/commands/agent/approve.command.d.ts

@@ -4,7 +4,7 @@
  * Approves a paused agent run (waiting_approval) and resumes execution.
  *
  * Usage:
- *   shipit-ai agent approve <id>
+ *   shep agent approve <id>
  */
 import { Command } from 'commander';
 export declare function createApproveCommand(): Command;

package/dist/src/presentation/cli/commands/agent/approve.command.js

@@ -4,7 +4,7 @@
  * Approves a paused agent run (waiting_approval) and resumes execution.
  *
  * Usage:
- *   shipit-ai agent approve <id>
+ *   shep agent approve <id>
  */
 import { Command } from 'commander';
 import { container } from '../../../../../packages/core/src/infrastructure/di/container.js';

package/dist/src/presentation/cli/commands/agent/delete.command.d.ts

@@ -4,7 +4,7 @@
  * Remove an agent run record from the database.
  *
  * Usage:
- *   shipit-ai agent delete <id>
+ *   shep agent delete <id>
  */
 import { Command } from 'commander';
 export declare function createDeleteCommand(): Command;

package/dist/src/presentation/cli/commands/agent/delete.command.js

@@ -4,7 +4,7 @@
  * Remove an agent run record from the database.
  *
  * Usage:
- *   shipit-ai agent delete <id>
+ *   shep agent delete <id>
  */
 import { Command } from 'commander';
 import { container } from '../../../../../packages/core/src/infrastructure/di/container.js';

package/dist/src/presentation/cli/commands/agent/index.d.ts

@@ -4,14 +4,14 @@
  * Top-level agent command with subcommands for managing and viewing agent runs.
  *
  * Usage:
- *   shipit-ai agent [subcommand]
+ *   shep agent [subcommand]
  *
  * Subcommands:
- *   shipit-ai agent show <id>     Display details of an agent run
- *   shipit-ai agent ls             List all agent runs
- *   shipit-ai agent stop <id>     Stop a running agent
- *   shipit-ai agent logs <id>     View agent run logs
- *   shipit-ai agent delete <id>   Delete an agent run record
+ *   shep agent show <id>     Display details of an agent run
+ *   shep agent ls             List all agent runs
+ *   shep agent stop <id>     Stop a running agent
+ *   shep agent logs <id>     View agent run logs
+ *   shep agent delete <id>   Delete an agent run record
  */
 import { Command } from 'commander';
 /**

package/dist/src/presentation/cli/commands/agent/index.js

@@ -4,14 +4,14 @@
  * Top-level agent command with subcommands for managing and viewing agent runs.
  *
  * Usage:
- *   shipit-ai agent [subcommand]
+ *   shep agent [subcommand]
  *
  * Subcommands:
- *   shipit-ai agent show <id>     Display details of an agent run
- *   shipit-ai agent ls             List all agent runs
- *   shipit-ai agent stop <id>     Stop a running agent
- *   shipit-ai agent logs <id>     View agent run logs
- *   shipit-ai agent delete <id>   Delete an agent run record
+ *   shep agent show <id>     Display details of an agent run
+ *   shep agent ls             List all agent runs
+ *   shep agent stop <id>     Stop a running agent
+ *   shep agent logs <id>     View agent run logs
+ *   shep agent delete <id>   Delete an agent run record
  */
 import { Command } from 'commander';
 import { createShowCommand } from './show.command.js';

package/dist/src/presentation/cli/commands/agent/logs.command.d.ts

@@ -4,9 +4,9 @@
  * View log output for an agent run with efficient streaming.
  *
  * Usage:
- *   shipit-ai agent logs <id>         # Print full log
- *   shipit-ai agent logs -f <id>      # Follow (tail -f) using fs.watch
- *   shipit-ai agent logs -n 50 <id>   # Last 50 lines
+ *   shep agent logs <id>         # Print full log
+ *   shep agent logs -f <id>      # Follow (tail -f) using fs.watch
+ *   shep agent logs -n 50 <id>   # Last 50 lines
  */
 import { Command } from 'commander';
 export declare function createLogsCommand(): Command;

package/dist/src/presentation/cli/commands/agent/logs.command.js

@@ -4,9 +4,9 @@
  * View log output for an agent run with efficient streaming.
  *
  * Usage:
- *   shipit-ai agent logs <id>         # Print full log
- *   shipit-ai agent logs -f <id>      # Follow (tail -f) using fs.watch
- *   shipit-ai agent logs -n 50 <id>   # Last 50 lines
+ *   shep agent logs <id>         # Print full log
+ *   shep agent logs -f <id>      # Follow (tail -f) using fs.watch
+ *   shep agent logs -n 50 <id>   # Last 50 lines
  */
 import { Command } from 'commander';
 import { join } from 'node:path';

package/dist/src/presentation/cli/commands/agent/ls.command.d.ts

@@ -5,7 +5,7 @@
  * Auto-detects dead PIDs and shows them as "crashed" instead of "running".
  *
  * Usage:
- *   shipit-ai agent ls
+ *   shep agent ls
  */
 import { Command } from 'commander';
 export declare function createLsCommand(): Command;

package/dist/src/presentation/cli/commands/agent/ls.command.js

@@ -5,7 +5,7 @@
  * Auto-detects dead PIDs and shows them as "crashed" instead of "running".
  *
  * Usage:
- *   shipit-ai agent ls
+ *   shep agent ls
  */
 import { Command } from 'commander';
 import { container } from '../../../../../packages/core/src/infrastructure/di/container.js';

package/dist/src/presentation/cli/commands/agent/reject.command.d.ts

@@ -4,7 +4,7 @@
  * Rejects a paused agent run (waiting_approval) and cancels it.
  *
  * Usage:
- *   shipit-ai agent reject <id> [--reason <text>]
+ *   shep agent reject <id> [--reason <text>]
  */
 import { Command } from 'commander';
 export declare function createRejectCommand(): Command;

package/dist/src/presentation/cli/commands/agent/reject.command.js

@@ -4,7 +4,7 @@
  * Rejects a paused agent run (waiting_approval) and cancels it.
  *
  * Usage:
- *   shipit-ai agent reject <id> [--reason <text>]
+ *   shep agent reject <id> [--reason <text>]
  */
 import { Command } from 'commander';
 import { container } from '../../../../../packages/core/src/infrastructure/di/container.js';

package/dist/src/presentation/cli/commands/agent/show.command.d.ts

@@ -5,7 +5,7 @@
  * PID, current node, heartbeat, and output.
  *
  * Usage:
- *   shipit-ai agent show <id>
+ *   shep agent show <id>
  */
 import { Command } from 'commander';
 export declare function createShowCommand(): Command;

package/dist/src/presentation/cli/commands/agent/show.command.js

@@ -5,7 +5,7 @@
  * PID, current node, heartbeat, and output.
  *
  * Usage:
- *   shipit-ai agent show <id>
+ *   shep agent show <id>
  */
 import { Command } from 'commander';
 import { colors, messages, symbols, renderDetailView } from '../../ui/index.js';

package/dist/src/presentation/cli/commands/agent/stop.command.d.ts

@@ -4,7 +4,7 @@
  * Sends SIGTERM to a running agent and marks it as interrupted (resumable).
  *
  * Usage:
- *   shipit-ai agent stop <id>
+ *   shep agent stop <id>
  */
 import { Command } from 'commander';
 export declare function createStopCommand(): Command;

package/dist/src/presentation/cli/commands/agent/stop.command.js

@@ -4,7 +4,7 @@
  * Sends SIGTERM to a running agent and marks it as interrupted (resumable).
  *
  * Usage:
- *   shipit-ai agent stop <id>
+ *   shep agent stop <id>
  */
 import { Command } from 'commander';
 import { container } from '../../../../../packages/core/src/infrastructure/di/container.js';