/**
 * Plan Fixture
 *
 * Realistic fixture for the fictional "Add dark-mode toggle to Shep 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