@shipit-ai/cli 1.166.2 → 1.167.0

package/dist/packages/core/src/infrastructure/services/agents/common/executors/dev-executor.service.js

@@ -1,233 +0,0 @@
-/** Dev Agent Executor — local development mock for the full SDLC flow.
- * Activated when settings.agent.type = "dev". Phase detection via regex on
- * prompt text; no interface changes. Delay: DEV_EXECUTOR_DELAY_MS (default 2000ms). */
-import * as fs from 'node:fs';
-import * as path from 'node:path';
-import { SPEC_ANALYZE_FIXTURE } from './fixtures/spec-analyze.fixture.js';
-import { SPEC_REQUIREMENTS_FIXTURE } from './fixtures/spec-requirements.fixture.js';
-import { RESEARCH_FIXTURE } from './fixtures/research.fixture.js';
-import { PLAN_FIXTURE } from './fixtures/plan.fixture.js';
-import { TASKS_FIXTURE } from './fixtures/tasks.fixture.js';
-const DEFAULT_DELAY_MS = 2000;
-const ADJECTIVES = [
-    'quantum',
-    'blazing',
-    'cosmic',
-    'fuzzy',
-    'turbo',
-    'hyperbolic',
-    'spectral',
-    'chromatic',
-    'orbital',
-    'fractal',
-    'velvet',
-    'neon',
-    'arctic',
-    'molten',
-    'prismatic',
-    'phantom',
-    'galactic',
-    'atomic',
-    'sonic',
-    'ethereal',
-];
-const NOUNS = [
-    'widget',
-    'pipeline',
-    'dashboard',
-    'renderer',
-    'compiler',
-    'beacon',
-    'transformer',
-    'navigator',
-    'interceptor',
-    'gateway',
-    'synthesizer',
-    'orchestrator',
-    'resolver',
-    'dispatcher',
-    'emitter',
-    'detector',
-    'aggregator',
-    'scheduler',
-    'validator',
-    'serializer',
-];
-const VERBS = [
-    'add',
-    'implement',
-    'integrate',
-    'build',
-    'create',
-    'wire up',
-    'introduce',
-    'scaffold',
-    'bootstrap',
-    'enable',
-];
-function randomMetadata() {
-    const adj = ADJECTIVES[Math.floor(Math.random() * ADJECTIVES.length)];
-    const noun = NOUNS[Math.floor(Math.random() * NOUNS.length)];
-    const verb = VERBS[Math.floor(Math.random() * VERBS.length)];
-    const slug = `${adj}-${noun}`;
-    const name = `${adj.charAt(0).toUpperCase() + adj.slice(1)} ${noun.charAt(0).toUpperCase() + noun.slice(1)}`;
-    return JSON.stringify({
-        slug,
-        name,
-        description: `${verb.charAt(0).toUpperCase() + verb.slice(1)} a ${adj} ${noun} to the application`,
-    });
-}
-function randomPrNumber() {
-    return Math.floor(Math.random() * 900) + 100;
-}
-function randomCommitHash() {
-    return Math.random().toString(16).slice(2, 10);
-}
-function mergeCommitResult() {
-    const pr = randomPrNumber();
-    const hash = randomCommitHash();
-    return (`[feat/dev-branch ${hash}] feat: dev implementation\n` +
-        `https://github.com/jrmatherly/shipit/pull/${pr}\nPull request #${pr} created successfully.`);
-}
-function mergeSquashResult() {
-    const pr = randomPrNumber();
-    return `Merged PR #${pr} with squash merge. Branch feat/dev-branch deleted.`;
-}
-const IMPLEMENT_RESULT = 'Implementation complete. All tests pass.\npnpm test: 47 passed, 0 failed';
-const CI_FIX_RESULT = 'Fixed CI failure: corrected import path. All checks now passing.';
-/**
- * Extract specDir from a YAML-producing prompt.
- * Refs: analyze.prompt.ts:39, requirements.prompt.ts:92, research.prompt.ts:45,
- * plan.prompt.ts:199.
- */
-function extractSpecDir(prompt) {
-    // Match both Unix absolute paths (/...) and Windows absolute paths (C:\...)
-    const ABS_PATH = String.raw `(?:\/|[A-Za-z]:[/\\])[^\s\n]+`;
-    // Analyze ("Write your analysis to:"), requirements ("Update the file at:"),
-    // research ("Write your research to:")
-    const fileMatch = prompt.match(new RegExp(`(?:Write your \\w+ to|Update the file at):\\s+(${ABS_PATH})`));
-    if (fileMatch)
-        return path.dirname(fileMatch[1]);
-    // Plan: "Write to BOTH /path/plan.yaml AND /path/tasks.yaml"
-    const planMatch = prompt.match(new RegExp(`Write to BOTH\\s+(${ABS_PATH})[/\\\\]plan\\.yaml`));
-    if (planMatch)
-        return planMatch[1];
-    return null;
-}
-/** Validate extracted specDir: must be absolute, no ".." traversal. */
-function validateSpecDir(specDir) {
-    if (!path.isAbsolute(specDir))
-        throw new Error(`DevAgentExecutorService: invalid specDir (not absolute): ${specDir}`);
-    if (specDir.includes('..'))
-        throw new Error(`DevAgentExecutorService: invalid specDir (contains ".."): ${specDir}`);
-}
-export class DevAgentExecutorService {
-    agentType = 'dev';
-    delayMs;
-    constructor() {
-        this.delayMs = parseInt(process.env.DEV_EXECUTOR_DELAY_MS ?? String(DEFAULT_DELAY_MS), 10);
-    }
-    async execute(prompt, _options) {
-        if (this.delayMs > 0) {
-            await new Promise((resolve) => setTimeout(resolve, this.delayMs));
-        }
-        const result = this.dispatch(prompt);
-        // Simulate realistic Claude Code token counts: prompts are large due to
-        // system prompt + codebase context; output varies by phase.
-        const baseInputTokens = Math.floor(prompt.length * 0.25); // ~4 chars/token
-        const contextTokens = 25000 + Math.floor(Math.random() * 15000); // cached context
-        const cacheReadTokens = Math.floor(contextTokens * 0.7);
-        const cacheCreationTokens = contextTokens - cacheReadTokens;
-        const inputTokens = baseInputTokens + contextTokens;
-        const outputTokens = Math.floor(result.length * 0.25) + 500;
-        const numTurns = Math.floor(Math.random() * 8) + 1;
-        // Pricing: ~$3/M input, ~$15/M output, cache read ~$0.30/M, cache write ~$3.75/M
-        const costUsd = baseInputTokens * 0.000003 +
-            cacheCreationTokens * 0.00000375 +
-            cacheReadTokens * 0.0000003 +
-            outputTokens * 0.000015;
-        // API time correlates with output tokens and turns
-        const durationApiMs = Math.floor(outputTokens * 0.08 * numTurns + Math.random() * 2000);
-        return {
-            result,
-            usage: {
-                inputTokens,
-                outputTokens,
-                cacheCreationInputTokens: cacheCreationTokens,
-                cacheReadInputTokens: cacheReadTokens,
-                costUsd: Math.round(costUsd * 10000) / 10000, // 4 decimal places
-                numTurns,
-                durationApiMs,
-            },
-        };
-    }
-    async *executeStream(prompt, options) {
-        const result = await this.execute(prompt, options);
-        yield { type: 'result', content: result.result, timestamp: new Date() };
-    }
-    supportsFeature(_feature) {
-        return false;
-    }
-    dispatch(prompt) {
-        // Metadata: mock-executor.service.ts extractUserInput pattern
-        if (prompt.includes('User request:\n"'))
-            return randomMetadata();
-        // Analyze: analyze.prompt.ts:39
-        if (prompt.includes('Write your analysis to:')) {
-            const specDir = extractSpecDir(prompt);
-            if (specDir) {
-                validateSpecDir(specDir);
-                fs.mkdirSync(specDir, { recursive: true });
-                fs.writeFileSync(path.join(specDir, 'spec.yaml'), SPEC_ANALYZE_FIXTURE, 'utf8');
-            }
-            return 'Analysis complete. spec.yaml written.';
-        }
-        // Requirements: requirements.prompt.ts:92
-        if (prompt.includes('Update the file at:')) {
-            const specDir = extractSpecDir(prompt);
-            if (specDir) {
-                validateSpecDir(specDir);
-                fs.mkdirSync(specDir, { recursive: true });
-                fs.writeFileSync(path.join(specDir, 'spec.yaml'), SPEC_REQUIREMENTS_FIXTURE, 'utf8');
-            }
-            return 'Requirements complete. spec.yaml updated.';
-        }
-        // Research: research.prompt.ts:45
-        if (prompt.includes('Write your research to:')) {
-            const specDir = extractSpecDir(prompt);
-            if (specDir) {
-                validateSpecDir(specDir);
-                fs.mkdirSync(specDir, { recursive: true });
-                fs.writeFileSync(path.join(specDir, 'research.yaml'), RESEARCH_FIXTURE, 'utf8');
-            }
-            return 'Research complete. research.yaml written.';
-        }
-        // Plan: plan.prompt.ts:199
-        if (prompt.includes('Write to BOTH')) {
-            const specDir = extractSpecDir(prompt);
-            if (specDir) {
-                validateSpecDir(specDir);
-                fs.mkdirSync(specDir, { recursive: true });
-                fs.writeFileSync(path.join(specDir, 'plan.yaml'), PLAN_FIXTURE, 'utf8');
-                fs.writeFileSync(path.join(specDir, 'tasks.yaml'), TASKS_FIXTURE, 'utf8');
-            }
-            return 'Planning complete. plan.yaml and tasks.yaml written.';
-        }
-        // Implement: implement.prompt.ts:91
-        if (prompt.includes('performing autonomous implementation'))
-            return IMPLEMENT_RESULT;
-        // Merge commit/push/PR: merge-prompts.ts:88
-        if (prompt.includes('performing git operations in a feature worktree'))
-            return mergeCommitResult();
-        // Merge squash (PR): merge-prompts.ts:131
-        if (prompt.includes('merging a pull request via the GitHub CLI'))
-            return mergeSquashResult();
-        // Merge squash (local): merge-prompts.ts:168
-        if (prompt.includes('performing a local merge'))
-            return mergeSquashResult();
-        // CI fix: merge.prompt.ts:28
-        if (prompt.includes('fixing a CI failure'))
-            return CI_FIX_RESULT;
-        return '{}';
-    }
-}

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

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

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

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

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

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

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

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

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

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

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

@@ -1,140 +0,0 @@
-/**
- * Research Fixture
- *
- * Realistic fixture for the fictional "Add dark-mode toggle to ShipIT Web UI" feature.
- * Passes validateResearch() with zero repair iterations.
- */
-export const RESEARCH_FIXTURE = `name: dark-mode-toggle
-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: shipit-ai-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: shipit-ai-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

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

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

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

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

@@ -1,81 +0,0 @@
-/**
- * Spec (Analyze Phase) Fixture
- *
- * Realistic fixture for the fictional "Add dark-mode toggle to ShipIT Web UI" feature.
- * Passes validateSpecAnalyze() with zero repair iterations.
- */
-export const SPEC_ANALYZE_FIXTURE = `name: dark-mode-toggle
-number: 42
-branch: feat/042-dark-mode-toggle
-oneLiner: Add a dark-mode toggle to the ShipIT web UI settings panel
-summary: >
-  Introduce a persistent dark-mode toggle to the ShipIT web UI settings panel that
-  applies a CSS class-based theme, stores the user preference in localStorage, and
-  is surfaced as a shadcn/ui Switch component with full Storybook coverage.
-phase: Analysis
-sizeEstimate: M
-
-relatedFeatures: []
-
-technologies:
-  - React 19
-  - Next.js 16 (App Router)
-  - Tailwind CSS v4
-  - shadcn/ui
-  - Storybook
-  - TypeScript
-
-relatedLinks: []
-
-openQuestions: []
-
-content: |
-  ## Problem Statement
-
-  The ShipIT web UI currently renders only in light mode. Developers working in dark
-  environments or those who prefer dark themes have no way to switch the UI appearance.
-  Adding a first-class dark-mode toggle improves developer experience and demonstrates
-  the ShipIT 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

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

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

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