@shepai/cli 1.50.0 → 1.51.1

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

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

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

@@ -0,0 +1,8 @@
+/**
+ * Spec (Analyze Phase) Fixture
+ *
+ * Realistic fixture for the fictional "Add dark-mode toggle to Shep 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";
+//# sourceMappingURL=spec-analyze.fixture.d.ts.map

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

@@ -0,0 +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"}

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

@@ -0,0 +1,81 @@
+/**
+ * Spec (Analyze Phase) Fixture
+ *
+ * Realistic fixture for the fictional "Add dark-mode toggle to Shep 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
+summary: >
+  Introduce a persistent dark-mode toggle to the Shep 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
+sizeEstimate: M
+
+relatedFeatures: []
+
+technologies:
+  - React 19
+  - Next.js 16 (App Router)
+  - Tailwind CSS v4
+  - shadcn/ui
+  - Storybook
+  - TypeScript
+
+relatedLinks: []
+
+openQuestions: []
+
+content: |
+  ## Problem Statement
+
+  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.
+  Adding a first-class dark-mode toggle improves developer experience and demonstrates
+  the Shep settings panel as a configurable surface.
+
+  ## Codebase Analysis
+
+  ### Project Structure
+
+  The web UI lives in src/presentation/web/ following Next.js App Router conventions.
+  Components are organized into four tiers: ui/ (Tier 0), common/ (Tier 1),
+  layouts/ (Tier 2), and features/ (Tier 3). Storybook stories are mandatory for every
+  component.
+
+  ### Architecture Patterns
+
+  The project uses shadcn/ui (Radix primitives + Tailwind CSS v4) for all UI components.
+  Theme state would live in a React context provider wrapping the root layout, following
+  the existing SettingsProvider pattern in the codebase. Clean Architecture layers keep
+  theme state in the presentation layer only.
+
+  ### Relevant Technologies
+
+  Tailwind CSS v4 supports dark mode via the \`dark\` CSS class on the html element.
+  shadcn/ui provides a Switch component suitable for the toggle control. localStorage
+  provides client-side persistence without any backend changes.
+
+  ## Affected Areas
+
+  | Area | Impact | Reasoning |
+  | ---- | ------ | --------- |
+  | src/presentation/web/components/features/settings/ | High | Settings panel receives the toggle component |
+  | src/presentation/web/app/layout.tsx | Medium | Root layout needs ThemeProvider wrapper |
+  | src/presentation/web/components/common/ | Medium | ThemeToggle and ThemeProvider components created here |
+  | tailwind.config.ts | Low | Verify darkMode: class is configured |
+
+  ## Dependencies
+
+  - shadcn/ui Switch component
+  - React context for theme state distribution
+  - localStorage Web API for persistence (built-in, no new dependency)
+
+  ## Size Estimate
+
+  **M (days)** — Context setup, toggle component, settings integration, Storybook stories,
+  and tests across 3 phases add up to roughly 2 developer-days with TDD.
+`;

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

@@ -0,0 +1,8 @@
+/**
+ * Spec (Requirements Phase) Fixture
+ *
+ * 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 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

@@ -0,0 +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"}

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

@@ -0,0 +1,131 @@
+/**
+ * Spec (Requirements Phase) Fixture
+ *
+ * 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 Shep web UI settings panel
+summary: >
+  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.
+phase: Requirements
+sizeEstimate: M
+
+relatedFeatures: []
+
+technologies:
+  - React 19
+  - Next.js 16 (App Router)
+  - Tailwind CSS v4
+  - shadcn/ui
+  - Storybook
+  - TypeScript
+  - localStorage Web API
+
+relatedLinks: []
+
+openQuestions:
+  - question: 'Where should the dark-mode preference be persisted?'
+    resolved: true
+    options:
+      - option: 'localStorage only'
+        description: >
+          Store the theme preference in localStorage. Zero backend changes,
+          instant read on page load, and no need for a settings schema migration.
+          The ThemeProvider reads the key on mount and writes on toggle.
+        selected: true
+      - option: 'SQLite settings via backend API'
+        description: >
+          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 Shep settings API is out of scope for
+      this feature; localStorage ships the value faster with zero migration risk.
+    answer: 'localStorage only'
+
+  - question: 'How should the CSS dark-mode implementation be applied?'
+    resolved: true
+    options:
+      - option: 'Tailwind CSS class-based dark mode (dark: modifier)'
+        description: >
+          Add the dark class to the html element and use Tailwind dark: modifier
+          on all themed elements. Supported natively in Tailwind CSS v4 and fully
+          compatible with the shadcn/ui component library.
+        selected: true
+      - option: 'CSS custom properties via a custom ThemeProvider stylesheet'
+        description: >
+          Define a set of CSS custom properties (--color-bg, --color-text, etc.)
+          and swap them by toggling a data attribute. More flexible but requires
+          redefining all existing color tokens — a large change surface.
+        selected: false
+    selectionRationale: >
+      Tailwind CSS v4 with dark: modifier is already the standard in this codebase.
+      All shadcn/ui components are built to accept Tailwind dark: variants. Using
+      the dark class on html is the minimal, zero-extra-dependency approach.
+    answer: 'Tailwind CSS class-based dark mode (dark: modifier)'
+
+content: |
+  ## Problem Statement
+
+  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
+
+  - [ ] A ThemeProvider wraps the root layout and provides a useTheme hook
+  - [ ] A ThemeToggle component renders in the settings panel with a Switch and label
+  - [ ] Clicking the toggle switches the html element class between light and dark
+  - [ ] The preference persists across page refreshes via localStorage
+  - [ ] All new components have Storybook stories with light and dark variants
+  - [ ] pnpm validate passes with no new errors
+
+  ## Functional Requirements
+
+  - **FR-1**: A ThemeProvider component must wrap the root Next.js App Router layout
+    and provide theme state to the component tree via React context.
+  - **FR-2**: A useTheme hook must expose { theme, toggleTheme } to any component.
+  - **FR-3**: A ThemeToggle component must render a Switch and a label (Dark mode).
+  - **FR-4**: Toggling the Switch must apply the dark CSS class to the html element.
+  - **FR-5**: The selected theme must be persisted to localStorage and restored on load.
+  - **FR-6**: ThemeToggle must appear in the settings panel (features/settings/).
+
+  ## Non-Functional Requirements
+
+  - **NFR-1**: Theme switch must complete within one animation frame (no FOUC).
+  - **NFR-2**: All new components must have Storybook stories per project conventions.
+  - **NFR-3**: No new npm dependencies may be added; use existing React, Tailwind, shadcn/ui.
+  - **NFR-4**: Each new file must stay within the 150-line project guideline.
+
+  ## Product Questions & AI Recommendations
+
+  | # | Question | AI Recommendation | Rationale |
+  | - | -------- | ----------------- | --------- |
+  | 1 | Persistence layer? | localStorage | Zero backend changes required |
+  | 2 | CSS implementation? | Tailwind dark: class | Already standard in the codebase |
+
+  ## Affected Areas
+
+  | Area | Impact | Reasoning |
+  | ---- | ------ | --------- |
+  | src/presentation/web/components/features/settings/ | High | Toggle component added here |
+  | src/presentation/web/app/layout.tsx | Medium | ThemeProvider wrapper added |
+  | src/presentation/web/components/common/ | Medium | ThemeToggle and ThemeProvider created |
+
+  ## Dependencies
+
+  - shadcn/ui Switch and Label components (already installed)
+  - React context API (built-in)
+  - localStorage Web API (built-in)
+
+  ## Size Estimate
+
+  **M (days)** — 3 phases: context + provider, toggle component, settings integration.
+`;

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

@@ -0,0 +1,6 @@
+/**
+ * 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";
+//# sourceMappingURL=tasks.fixture.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"tasks.fixture.d.ts","sourceRoot":"","sources":["../../../../../../../../../../packages/core/src/infrastructure/services/agents/common/executors/fixtures/tasks.fixture.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH,eAAO,MAAM,aAAa,wmMA6IzB,CAAC"}

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

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

package/dist/packages/core/src/infrastructure/services/agents/feature-agent/feature-agent-worker.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"feature-agent-worker.d.ts","sourceRoot":"","sources":["../../../../../../../../packages/core/src/infrastructure/services/agents/feature-agent/feature-agent-worker.ts"],"names":[],"mappings":";AACA;;;;;;;;GAQG;AAEH,OAAO,kBAAkB,CAAC;AAoB1B,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,8BAA8B,CAAC;AAElE,MAAM,WAAW,UAAU;IACzB,SAAS,EAAE,MAAM,CAAC;IAClB,KAAK,EAAE,MAAM,CAAC;IACd,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,EAAE,MAAM,CAAC;IAChB,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,aAAa,CAAC,EAAE,aAAa,CAAC;IAC9B,MAAM,CAAC,EAAE,OAAO,CAAC;IACjB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,mBAAmB,CAAC,EAAE,OAAO,CAAC;IAC9B,IAAI,CAAC,EAAE,OAAO,CAAC;IACf,MAAM,CAAC,EAAE,OAAO,CAAC;IACjB,aAAa,CAAC,EAAE,MAAM,CAAC;CACxB;AAED;;;GAGG;AACH,wBAAgB,eAAe,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,UAAU,CAoD1D;AAgCD;;;GAGG;AACH,wBAAsB,SAAS,CAAC,IAAI,EAAE,UAAU,GAAG,OAAO,CAAC,IAAI,CAAC,CAoM/D"}
+{"version":3,"file":"feature-agent-worker.d.ts","sourceRoot":"","sources":["../../../../../../../../packages/core/src/infrastructure/services/agents/feature-agent/feature-agent-worker.ts"],"names":[],"mappings":";AACA;;;;;;;;GAQG;AAEH,OAAO,kBAAkB,CAAC;AAoB1B,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,8BAA8B,CAAC;AAElE,MAAM,WAAW,UAAU;IACzB,SAAS,EAAE,MAAM,CAAC;IAClB,KAAK,EAAE,MAAM,CAAC;IACd,IAAI,EAAE,MAAM,CAAC;IACb,OAAO,EAAE,MAAM,CAAC;IAChB,YAAY,CAAC,EAAE,MAAM,CAAC;IACtB,aAAa,CAAC,EAAE,aAAa,CAAC;IAC9B,MAAM,CAAC,EAAE,OAAO,CAAC;IACjB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,mBAAmB,CAAC,EAAE,OAAO,CAAC;IAC9B,IAAI,CAAC,EAAE,OAAO,CAAC;IACf,MAAM,CAAC,EAAE,OAAO,CAAC;IACjB,aAAa,CAAC,EAAE,MAAM,CAAC;CACxB;AAED;;;GAGG;AACH,wBAAgB,eAAe,CAAC,IAAI,EAAE,MAAM,EAAE,GAAG,UAAU,CAoD1D;AAgCD;;;GAGG;AACH,wBAAsB,SAAS,CAAC,IAAI,EAAE,UAAU,GAAG,OAAO,CAAC,IAAI,CAAC,CAsM/D"}

package/dist/packages/core/src/infrastructure/services/agents/feature-agent/feature-agent-worker.js

@@ -130,6 +130,7 @@ export async function runWorker(args) {
             getDiffSummary: (cwd, baseBranch) => gitPrService.getPrDiffSummary(cwd, baseBranch),
             hasRemote: (cwd) => gitPrService.hasRemote(cwd),
             getDefaultBranch: (cwd) => gitPrService.getDefaultBranch(cwd),
+            verifyMerge: (cwd, featureBranch, baseBranch) => gitPrService.verifyMerge(cwd, featureBranch, baseBranch),
             featureRepository,
         },
     };

package/dist/packages/core/src/infrastructure/services/agents/feature-agent/nodes/merge.node.d.ts

@@ -17,6 +17,11 @@ export interface MergeNodeDeps {
     hasRemote: (cwd: string) => Promise<boolean>;
     getDefaultBranch: (cwd: string) => Promise<string>;
     featureRepository: Pick<IFeatureRepository, 'findById' | 'update'>;
+    /**
+     * Verify that featureBranch has been merged into baseBranch.
+     * Returns true if baseBranch contains all commits from featureBranch.
+     */
+    verifyMerge: (cwd: string, featureBranch: string, baseBranch: string) => Promise<boolean>;
 }
 /**
  * Factory that creates the merge node function.

package/dist/packages/core/src/infrastructure/services/agents/feature-agent/nodes/merge.node.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"merge.node.d.ts","sourceRoot":"","sources":["../../../../../../../../../packages/core/src/infrastructure/services/agents/feature-agent/nodes/merge.node.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAGH,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,+DAA+D,CAAC;AACpG,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AACrD,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,yEAAyE,CAAC;AAClH,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,iEAAiE,CAAC;AAqBnG,MAAM,WAAW,aAAa;IAC5B,QAAQ,EAAE,cAAc,CAAC;IACzB,cAAc,EAAE,CAAC,GAAG,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,KAAK,OAAO,CAAC,WAAW,CAAC,CAAC;IAC1E,SAAS,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC;IAC7C,gBAAgB,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;IACnD,iBAAiB,EAAE,IAAI,CAAC,kBAAkB,EAAE,UAAU,GAAG,QAAQ,CAAC,CAAC;CACpE;AAED;;;;;GAKG;AACH,wBAAgB,eAAe,CAAC,IAAI,EAAE,aAAa,IAGnC,OAAO,iBAAiB,KAAG,OAAO,CAAC,OAAO,CAAC,iBAAiB,CAAC,CAAC,CAoK7E"}
+{"version":3,"file":"merge.node.d.ts","sourceRoot":"","sources":["../../../../../../../../../packages/core/src/infrastructure/services/agents/feature-agent/nodes/merge.node.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAGH,OAAO,KAAK,EAAE,cAAc,EAAE,MAAM,+DAA+D,CAAC;AACpG,OAAO,KAAK,EAAE,iBAAiB,EAAE,MAAM,aAAa,CAAC;AACrD,OAAO,KAAK,EAAE,kBAAkB,EAAE,MAAM,yEAAyE,CAAC;AAClH,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,iEAAiE,CAAC;AAqBnG,MAAM,WAAW,aAAa;IAC5B,QAAQ,EAAE,cAAc,CAAC;IACzB,cAAc,EAAE,CAAC,GAAG,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,KAAK,OAAO,CAAC,WAAW,CAAC,CAAC;IAC1E,SAAS,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC;IAC7C,gBAAgB,EAAE,CAAC,GAAG,EAAE,MAAM,KAAK,OAAO,CAAC,MAAM,CAAC,CAAC;IACnD,iBAAiB,EAAE,IAAI,CAAC,kBAAkB,EAAE,UAAU,GAAG,QAAQ,CAAC,CAAC;IACnE;;;OAGG;IACH,WAAW,EAAE,CAAC,GAAG,EAAE,MAAM,EAAE,aAAa,EAAE,MAAM,EAAE,UAAU,EAAE,MAAM,KAAK,OAAO,CAAC,OAAO,CAAC,CAAC;CAC3F;AAED;;;;;GAKG;AACH,wBAAgB,eAAe,CAAC,IAAI,EAAE,aAAa,IAGnC,OAAO,iBAAiB,KAAG,OAAO,CAAC,OAAO,CAAC,iBAAiB,CAAC,CAAC,CAsL7E"}

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

@@ -61,10 +61,10 @@ export function createMergeNode(deps) {
             let prUrl = state.prUrl;
             let prNumber = state.prNumber;
             const ciStatus = state.ciStatus;
+            // --- Check for git remote (needed by both agent calls) ---
+            const remoteAvailable = await deps.hasRemote(cwd);
             // --- Agent Call 1: Commit + Push + PR (skip on approval resume) ---
             if (!isResumeAfterInterrupt) {
-                // --- Check for git remote ---
-                const remoteAvailable = await deps.hasRemote(cwd);
                 if (!remoteAvailable) {
                     log.info('No git remote configured — skipping push and PR, will merge locally');
                 }
@@ -110,8 +110,20 @@ export function createMergeNode(deps) {
             let merged = false;
             if (state.approvalGates?.allowMerge) {
                 log.info('Agent call 2: merge/squash');
-                const mergePrompt = buildMergeSquashPrompt({ ...state, prUrl, prNumber, commitHash }, branch, baseBranch);
-                await retryExecute(executor, mergePrompt, options, { logger: log });
+                const mergePrompt = buildMergeSquashPrompt({ ...state, prUrl, prNumber, commitHash }, branch, baseBranch, remoteAvailable);
+                // Run merge in the ORIGINAL repo, not the worktree — the worktree IS
+                // the feature branch and must not be modified or removed during merge.
+                const mergeOptions = { ...options, cwd: state.repositoryPath };
+                await retryExecute(executor, mergePrompt, mergeOptions, { logger: log });
+                // Verify the merge actually succeeded (agent may report success without merging)
+                if (!prUrl) {
+                    const mergeVerified = await deps.verifyMerge(state.repositoryPath, branch, baseBranch);
+                    if (!mergeVerified) {
+                        throw new Error(`Merge verification failed: ${branch} was not merged into ${baseBranch}. ` +
+                            `The agent may have encountered errors during the merge operation.`);
+                    }
+                    log.info('Merge verified: feature branch is ancestor of base branch');
+                }
                 messages.push(`[merge] Agent completed merge operation`);
                 merged = true;
             }

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

@@ -20,5 +20,5 @@ export declare function buildCommitPushPrPrompt(state: FeatureAgentState, branch
  * When no PR exists, performs a local merge in the ORIGINAL repo directory
  * (not the worktree, which IS the feature branch).
  */
-export declare function buildMergeSquashPrompt(state: FeatureAgentState, branch: string, baseBranch: string): string;
+export declare function buildMergeSquashPrompt(state: FeatureAgentState, branch: string, baseBranch: string, hasRemote?: boolean): string;
 //# sourceMappingURL=merge-prompts.d.ts.map