/**
 * 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