neotoma 0.3.0 → 0.3.2

package/docs/releases/v0.2.1/feature_unit_overview.md

@@ -1,246 +0,0 @@
-# Release v0.2.1 — Feature Unit Overview
-**Release ID**: v0.2.1  
-**Release Name**: Documentation & Support System  
-**Release Type**: Not Marketed  
-**Deployment**: Production (neotoma.io)
-## Feature Unit Catalog
-### FU-300: AI-Powered Documentation Analysis & Generation
-**Priority:** P0  
-**Risk Level:** Medium  
-**Dependencies:** None
-**Purpose:**
-Generate comprehensive, static documentation derived from AI analysis of the repository. Analyzes codebase structure, architecture, APIs, workflows, and generates documentation in markdown/HTML format suitable for web viewing.
-**Key Components:**
-1. **Repository Analysis Engine**
-   - Codebase structure analysis
-   - Architecture pattern detection
-   - API endpoint discovery
-   - Workflow identification
-   - Dependency mapping
-2. **Documentation Generator**
-   - API reference generation (MCP actions, request/response schemas)
-   - Architecture documentation (diagrams, system design)
-   - Feature unit documentation (specs, implementation guides)
-   - Developer guides (getting started, workflows, testing)
-   - Integration guides (MCP setup, provider integrations)
-   - Troubleshooting and FAQ generation
-3. **Documentation Indexer**
-   - Content indexing for search
-   - Cross-reference generation
-   - Topic categorization
-   - Metadata extraction
-**Output:**
-- Static markdown/HTML files
-- Documentation index (searchable)
-- Cross-reference map
-- Version metadata
-**Acceptance Criteria:**
-- Comprehensive documentation generated covering all major topics
-- Documentation deterministic (same repo state → same docs)
-- Documentation includes API references, architecture diagrams, guides
-- Documentation index created for search functionality
-**Estimated Duration:** 8-12 hours
-### FU-301: Static Documentation Web Server
-**Priority:** P0  
-**Risk Level:** Low  
-**Dependencies:** FU-300 (Documentation Generation)
-**Purpose:**
-Serve statically-generated documentation files via web interface with a one-page landing website, search functionality, navigation, and cross-linking.
-**Key Components:**
-1. **One-Page Landing Website**
-   - Root URL landing page presenting key information from README.md
-   - What Neotoma is and problems it solves
-   - Target users and use cases
-   - Core workflow and architecture overview
-   - Key features and capabilities
-   - Directory access to documentation organized by category
-   - MCP setup instructions with step-by-step guide
-   - Quick links to essential documentation
-   - Design system compliance:
-     - Colors: Neutral grays, blue accents (#0066CC primary)
-     - Typography: Inter for UI text, JetBrains Mono for code/data
-     - Spacing: 4px base unit (8px, 16px, 24px, etc.)
-     - Components: shadcn/ui components where applicable
-     - Dark mode support
-     - Accessibility: WCAG AA compliance (keyboard nav, ARIA, contrast)
-     - Brand alignment: Minimal, technical, trustworthy, deterministic
-2. **Static File Server**
-   - Markdown/HTML file serving
-   - Asset serving (images, CSS, JS)
-   - Efficient file delivery (< 200ms page load)
-3. **Search Functionality**
-   - Full-text search across documentation
-   - Query processing (< 500ms response)
-   - Result ranking and highlighting
-   - Search index management
-4. **Navigation System**
-   - Table of contents generation
-   - Cross-link resolution
-   - Breadcrumb navigation
-   - Related content suggestions
-   - Directory browsing interface
-5. **Versioning Support**
-   - Versioned documentation directories
-   - Version selector UI
-   - Version-specific navigation
-**Acceptance Criteria:**
-- One-page landing website accessible at root URL
-- Landing page displays key README information clearly
-- Design system compliance verified (colors, typography, spacing, components)
-- Accessibility requirements met (WCAG AA, keyboard navigation, ARIA labels)
-- Dark mode support functional
-- Directory access to documentation functional
-- MCP setup instructions available and clear
-- Static documentation served via web server
-- Page load performance < 200ms (p95)
-- Search functionality operational
-- Cross-links functional
-- Navigation usable
-**Estimated Duration:** 4-6 hours
-### FU-302: MCP Support Inquiry Endpoint
-**Priority:** P0  
-**Risk Level:** Low  
-**Dependencies:** FU-200 (MCP Server Core from v0.1.0)
-**Purpose:**
-Implement new MCP action `query_support` for support inquiries. Provides structured interface for users to query support via MCP clients.
-**Key Components:**
-1. **MCP Action Implementation**
-   - Action name: `query_support`
-   - Request schema validation (Zod)
-   - Response schema definition
-   - Error handling (ErrorEnvelope)
-2. **Request Schema**
-   ```typescript
-   {
-     query: string; // User's support question
-     context?: {
-       // Optional context (current action, error message, etc.)
-     };
-   }
-   ```
-3. **Response Schema**
-   ```typescript
-   {
-     answer: string; // Agent-generated answer
-     citations: Array<{
-       title: string;
-       url: string;
-       excerpt?: string;
-     }>;
-     confidence?: number; // Optional confidence score
-   }
-   ```
-4. **Integration**
-   - Integration with support agent (FU-303)
-   - Error handling and validation
-   - MCP protocol compliance
-**Acceptance Criteria:**
-- MCP `query_support` action implemented
-- Request/response schema validated
-- Error handling functional
-- MCP protocol compliance verified
-- Integration tests passing
-**Estimated Duration:** 4-6 hours
-### FU-303: Support Agent System
-**Priority:** P0  
-**Risk Level:** Medium  
-**Dependencies:** FU-300 (Documentation Generation), FU-301 (Documentation Web Server), FU-302 (MCP Support Endpoint)
-**Purpose:**
-RAG-based support agent that uses static documentation as knowledge base. Understands user queries, retrieves relevant context, and generates helpful responses with citations.
-**Key Components:**
-1. **Query Understanding**
-   - Intent classification
-   - Query preprocessing
-   - Context extraction
-   - Multi-part question handling
-2. **Context Retrieval**
-   - Documentation index search
-   - Relevant section identification
-   - Context ranking and selection
-   - Multi-document context aggregation
-3. **Response Generation**
-   - Answer synthesis from context
-   - Citation extraction
-   - Response formatting
-   - Confidence scoring (optional)
-4. **Integration**
-   - Integration with MCP endpoint (FU-302)
-   - Documentation index access (FU-301)
-   - Error handling and fallbacks
-**Acceptance Criteria:**
-- Support agent operational
-- Response accuracy >= 80% on test queries
-- Responses include citations to source documentation
-- Context retrieval functional
-- Integration with MCP endpoint working
-- Multi-topic queries handled correctly
-**Estimated Duration:** 8-12 hours
-## Feature Unit Dependencies
-```
-FU-300 (Documentation Generation)
-  └─> FU-301 (Documentation Web Server)
-FU-200 (MCP Server Core from v0.1.0)
-  └─> FU-302 (MCP Support Endpoint)
-FU-300, FU-301, FU-302
-  └─> FU-303 (Support Agent System)
-```
-## Implementation Notes
-### Design System Compliance (All UI Work)
-**CRITICAL:** All UI-related work in this release MUST follow the design system (`docs/ui/design_system.md`).
-**Required Elements:**
-- Colors: Neutral grays with blue accents (#0066CC primary), dark mode support
-- Typography: Inter for UI text, JetBrains Mono for code/data
-- Spacing: 4px base unit scale (8px, 16px, 24px, etc.)
-- Components: shadcn/ui components where applicable, aligned with design system
-- Dark Mode: Full support required
-- Accessibility: WCAG AA compliance (keyboard navigation, ARIA labels, contrast)
-- Brand Alignment: Minimal, technical, trustworthy, deterministic
-**Verification:**
-- Design system compliance must be verified in acceptance criteria
-- Integration tests must verify design system compliance
-- Code review must check design system adherence
-### Documentation Generation (FU-300)
-- Use AI analysis to understand codebase structure
-- Generate documentation following Neotoma documentation standards
-- Ensure deterministic output (no timestamps, random IDs)
-- Create comprehensive index for search functionality
-### Web Server (FU-301)
-- **MUST follow design system** (`docs/ui/design_system.md`) for all UI components
-- Use efficient static file serving (e.g., Express static middleware)
-- Implement search using documentation index from FU-300
-- Optimize for performance (< 200ms page load)
-- Support versioned documentation directories
-- Landing page must comply with design system (colors, typography, spacing, components, accessibility, dark mode)
-### MCP Endpoint (FU-302)
-- Follow MCP protocol specification strictly
-- Use existing MCP server infrastructure from v0.1.0
-- Implement proper error handling with ErrorEnvelope
-- Validate request/response schemas
-### Support Agent (FU-303)
-- Use RAG pattern with static documentation as knowledge base
-- Implement semantic search for context retrieval
-- Generate responses with citations to source documentation
-- Validate accuracy on test query set (>= 80%)
-## Testing Strategy
-**Unit Tests:**
-- Each FU component tested independently
-- Mock dependencies where appropriate
-- Test edge cases and error handling
-**Integration Tests:**
-- Cross-FU workflows tested end-to-end
-- Documentation generation → web serving → support agent flow
-- MCP endpoint integration with support agent
-**Accuracy Tests:**
-- Support agent accuracy validated on test query set
-- Citation quality verified
-- Response relevance assessed
-## Success Metrics
-- **Documentation Coverage:** All major topics documented
-- **Documentation Quality:** Accurate, clear, actionable
-- **Support Agent Accuracy:** >= 80% on test queries
-- **Performance:** Page load < 200ms, search < 500ms
-- **User Satisfaction:** Users can self-serve answers effectively
-- **Production Deployment:** Successfully deployed to neotoma.io
-  - Landing page accessible at neotoma.io
-  - Documentation accessible at neotoma.io/docs
-  - MCP support endpoint operational

package/docs/releases/v0.2.1/integration_tests.md

@@ -1,281 +0,0 @@
-# Release v0.2.1 — Integration Tests
-**Release ID**: v0.2.1  
-**Release Name**: Documentation & Support System  
-**Release Type**: Not Marketed  
-**Deployment**: Production (neotoma.io)
-## Test Execution
-Tests are executed automatically by the release orchestrator after batch completion. Test commands are defined in the `test:` field for each test.
-## Integration Test Catalog
-### IT-001: Documentation Generation → Web Viewing Flow
-**Goal:** Verify that documentation generation produces comprehensive, accurate documentation that is accessible via web interface with a functional landing page.
-**Batches Covered:** 0, 1
-**FUs Involved:** FU-300, FU-301
-**Test Steps:**
-1. Run documentation generation process (FU-300)
-2. Verify documentation files generated in output directory
-3. Verify documentation covers all major topics:
-   - Architecture overview
-   - API reference (all MCP actions)
-   - Feature unit specifications
-   - Developer guides
-   - Integration guides
-   - Troubleshooting and FAQ
-4. Start documentation web server (FU-301)
-5. Access landing page at root URL
-6. Verify landing page displays:
-   - Key information from README.md (what Neotoma is, problems solved, who it's for)
-   - Core workflow and architecture overview
-   - Key features and capabilities
-   - Directory access to documentation
-   - MCP setup instructions
-   - Quick links to essential documentation
-7. Verify directory browsing functional (navigate to documentation categories)
-8. Verify MCP setup instructions are accessible and clear
-9. Access documentation via web interface
-10. Verify page load performance (< 200ms p95)
-11. Verify navigation functional
-12. Verify cross-links work correctly
-**Expected Results:**
-- Documentation generated successfully
-- All major topics covered
-- Landing page accessible and displays key information
-- Directory access functional
-- MCP setup instructions available
-- Web interface accessible
-- Page load performance within target
-- Navigation and cross-links functional
-**Machine-Checkable:**
-```bash
-test: "tests/integration/documentation_web.test.ts"
-```
-**Status:** ⏳ not_run
-### IT-009: Landing Page Functionality
-**Goal:** Verify that the one-page landing website presents key README information, provides directory access, and includes clear MCP setup instructions.
-**Batches Covered:** 1
-**FUs Involved:** FU-301
-**Test Steps:**
-1. Ensure documentation generated and web server operational
-2. Access landing page at root URL
-3. Verify landing page content:
-   - What Neotoma is (Truth Layer for AI Memory)
-   - Problems solved (fragmented data, no AI memory, etc.)
-   - Target users (AI-native individuals, knowledge workers, teams)
-   - Core workflow overview
-   - Architecture overview (five-layer architecture)
-   - Key features (MVP and post-MVP)
-   - Core principles
-4. Verify directory access:
-   - Documentation organized by category visible
-   - Links to documentation sections functional
-   - Directory browsing works
-5. Verify MCP setup instructions:
-   - Step-by-step guide present
-   - Configuration examples provided
-   - Links to detailed MCP documentation
-   - Instructions actionable and clear
-6. Verify quick links:
-   - Links to getting started guide
-   - Links to MVP overview
-   - Links to architecture docs
-   - All links functional
-7. Verify responsive design (basic mobile view)
-**Expected Results:**
-- Landing page displays all key README information
-- Design system compliance verified
-- Accessibility requirements met
-- Directory access functional
-- MCP setup instructions clear and actionable
-- Quick links functional
-- Page responsive and visually clear
-**Machine-Checkable:**
-```bash
-test: "tests/integration/landing_page.test.ts"
-```
-**Status:** ⏳ not_run
-### IT-002: Support Query → Agent Response Flow
-**Goal:** Verify that MCP support queries trigger support agent to retrieve relevant documentation context and generate accurate responses with citations.
-**Batches Covered:** 2, 3
-**FUs Involved:** FU-302, FU-303
-**Test Steps:**
-1. Ensure documentation generated and indexed (FU-300, FU-301)
-2. Ensure MCP support endpoint operational (FU-302)
-3. Ensure support agent system operational (FU-303)
-4. Query MCP `query_support` action with test question:
-   - "How do I upload a file via MCP?"
-5. Verify agent retrieves relevant documentation context
-6. Verify response includes accurate answer
-7. Verify response includes citations to source documentation
-8. Verify response format follows MCP response schema
-**Expected Results:**
-- MCP endpoint accepts query
-- Agent retrieves relevant context
-- Response accurate and helpful
-- Citations present and correct
-- Response format valid
-**Machine-Checkable:**
-```bash
-test: "tests/integration/support_agent.test.ts"
-```
-**Status:** ⏳ not_run
-### IT-003: Documentation Update → Support Agent Knowledge Flow
-**Goal:** Verify that documentation updates are reflected in support agent knowledge base after regeneration.
-**Batches Covered:** 0, 1, 3
-**FUs Involved:** FU-300, FU-301, FU-303
-**Test Steps:**
-1. Generate initial documentation (FU-300)
-2. Start web server and support agent (FU-301, FU-303)
-3. Query support agent with question about specific feature
-4. Record initial response
-5. Update source documentation (add new section or modify existing)
-6. Regenerate documentation (FU-300)
-7. Restart support agent with updated documentation
-8. Query support agent with same question
-9. Verify response reflects updated documentation
-**Expected Results:**
-- Initial response recorded
-- Documentation updated successfully
-- Support agent uses updated documentation
-- Response reflects changes
-**Machine-Checkable:**
-```bash
-test: "tests/integration/documentation_update.test.ts"
-```
-**Status:** ⏳ not_run
-### IT-004: Multi-Topic Support Query Flow
-**Goal:** Verify that support agent handles complex multi-part questions by retrieving context from multiple documentation sections.
-**Batches Covered:** 3
-**FUs Involved:** FU-303
-**Test Steps:**
-1. Ensure documentation generated and support agent operational
-2. Query support agent with complex multi-part question:
-   - "How do I set up MCP integration and what are the available actions?"
-3. Verify agent retrieves context from multiple documentation sections:
-   - MCP setup guide
-   - MCP action catalog
-4. Verify response addresses all parts of question
-5. Verify citations reference correct documentation sections
-**Expected Results:**
-- Agent retrieves multiple context sections
-- Response addresses all question parts
-- Citations reference correct sections
-- Response coherent and comprehensive
-**Machine-Checkable:**
-```bash
-test: "tests/integration/multi_topic_support.test.ts"
-```
-**Status:** ⏳ not_run
-### IT-005: Documentation Search Functionality
-**Goal:** Verify that documentation search returns relevant results quickly.
-**Batches Covered:** 1
-**FUs Involved:** FU-301
-**Test Steps:**
-1. Ensure documentation generated and web server operational
-2. Perform search queries:
-   - "MCP actions"
-   - "entity resolution"
-   - "file upload"
-3. Verify search returns relevant results
-4. Verify search query response time < 500ms (p95)
-5. Verify search results ranked by relevance
-6. Verify search highlights matching terms
-**Expected Results:**
-- Search returns relevant results
-- Response time within target
-- Results ranked appropriately
-- Matching terms highlighted
-**Machine-Checkable:**
-```bash
-test: "tests/integration/documentation_search.test.ts"
-```
-**Status:** ⏳ not_run
-### IT-006: Support Agent Accuracy Validation
-**Goal:** Verify that support agent achieves >= 80% accuracy on test query set.
-**Batches Covered:** 3
-**FUs Involved:** FU-303
-**Test Steps:**
-1. Prepare test query set (20+ queries covering common support topics)
-2. Ensure support agent operational
-3. Execute each test query via MCP endpoint
-4. Evaluate responses for accuracy (manual or automated)
-5. Calculate accuracy rate (correct responses / total queries)
-6. Verify accuracy >= 80%
-**Expected Results:**
-- Test query set prepared
-- All queries executed successfully
-- Accuracy rate >= 80%
-- Incorrect responses analyzed for improvement
-**Machine-Checkable:**
-```bash
-test: "tests/integration/support_agent_accuracy.test.ts"
-```
-**Status:** ⏳ not_run
-### IT-007: MCP Endpoint Protocol Compliance
-**Goal:** Verify that MCP support endpoint follows MCP protocol specification.
-**Batches Covered:** 2
-**FUs Involved:** FU-302
-**Test Steps:**
-1. Ensure MCP support endpoint operational
-2. Test request validation:
-   - Valid request accepted
-   - Invalid request rejected with appropriate error
-3. Test response format:
-   - Response follows MCP response schema
-   - Error responses use ErrorEnvelope format
-4. Test error handling:
-   - Network errors handled gracefully
-   - Invalid queries return helpful errors
-5. Verify MCP protocol compliance (check against MCP spec)
-**Expected Results:**
-- Request validation functional
-- Response format compliant
-- Error handling appropriate
-- Protocol compliance verified
-**Machine-Checkable:**
-```bash
-test: "tests/integration/mcp_support_endpoint.test.ts"
-```
-**Status:** ⏳ not_run
-### IT-008: Documentation Generation Determinism
-**Goal:** Verify that documentation generation is deterministic (same repo state → same docs).
-**Batches Covered:** 0
-**FUs Involved:** FU-300
-**Test Steps:**
-1. Capture repository state (commit hash)
-2. Run documentation generation
-3. Record generated documentation (file hashes)
-4. Run documentation generation again (same repo state)
-5. Compare generated documentation (should be identical)
-6. Repeat 10 times to verify consistency
-**Expected Results:**
-- Same repo state produces identical documentation
-- File hashes match across runs
-- No non-deterministic content (timestamps, random IDs, etc.)
-**Machine-Checkable:**
-```bash
-test: "tests/integration/documentation_determinism.test.ts"
-```
-**Status:** ⏳ not_run
-## Test Summary
-| Test ID | Name                                                | Status     | FUs Tested             | Description                                        |
-| ------- | --------------------------------------------------- | ---------- | ---------------------- | -------------------------------------------------- |
-| IT-001  | Documentation Generation → Web Viewing Flow         | ⏳ not_run | FU-300, FU-301         | Verify documentation generation and web serving    |
-| IT-002  | Support Query → Agent Response Flow                 | ⏳ not_run | FU-302, FU-303         | Verify MCP support endpoint and agent integration  |
-| IT-003  | Documentation Update → Support Agent Knowledge Flow | ⏳ not_run | FU-300, FU-301, FU-303 | Verify documentation updates reflected in agent    |
-| IT-004  | Multi-Topic Support Query Flow                      | ⏳ not_run | FU-303                 | Verify complex multi-part question handling        |
-| IT-005  | Documentation Search Functionality                  | ⏳ not_run | FU-301                 | Verify search performance and relevance            |
-| IT-006  | Support Agent Accuracy Validation                   | ⏳ not_run | FU-303                 | Verify support agent accuracy >= 80%               |
-| IT-007  | MCP Endpoint Protocol Compliance                    | ⏳ not_run | FU-302                 | Verify MCP protocol compliance                     |
-| IT-008  | Documentation Generation Determinism                | ⏳ not_run | FU-300                 | Verify deterministic documentation generation      |
-| IT-009  | Landing Page Functionality                          | ⏳ not_run | FU-301                 | Verify landing page with README info and MCP setup |
-**Summary:** 0/9 tests passed
-## Manual Validation Requirements
-**Documentation Web Interface:**
-- Access documentation via web browser
-- Verify visual design and readability
-- Test navigation and cross-links manually
-- Verify mobile responsiveness (basic)
-**Support Agent via MCP:**
-- Connect MCP client (Cursor/ChatGPT) to Neotoma MCP server
-- Query support agent via `query_support` action
-- Verify response quality and citations
-- Test various question types (API usage, troubleshooting, architecture)

package/docs/releases/v0.2.1/manifest.yaml

@@ -1,141 +0,0 @@
-release:
-  id: "v0.2.1"
-  name: "Documentation Generation System"
-  type: "not_marketed" # marketed | not_marketed
-  status: "planning" # planning | in_progress | in_testing | ready_for_deployment | deployed | completed
-  target_date: "when ready"
-  priority: "P0"
-  marketing_required: false
-  scope_change: "Support features (FU-302, FU-303) moved to v0.9.0"
-
-# Execution strategy
-execution_strategy:
-  type: "sequential" # "multi_agent" or "sequential"
-  max_parallel_fus: 1 # Maximum FUs executing simultaneously
-  max_high_risk_in_parallel: 1 # Maximum high-risk FUs executing simultaneously
-  agent_spawning:
-    enabled: true
-    status_tracking: "file" # "file" or "api"
-    status_file: "docs/releases/v0.2.1/status.md"
-
-feature_units:
-  # Documentation Generation System
-  - id: "FU-300"
-    priority: "P0"
-    dependencies: []
-    risk_level: "medium"
-    notes: "AI-powered repository analysis and comprehensive documentation generation"
-
-  # Static Documentation Web Server
-  - id: "FU-301"
-    priority: "P0"
-    dependencies: ["FU-300"]
-    risk_level: "low"
-    notes: "One-page landing website with README info, directory access, MCP setup instructions, and static file serving with search"
-
-# Moved to v0.9.0
-deferred_feature_units:
-  - id: "FU-302"
-    name: "MCP Support Inquiry Endpoint"
-    moved_to: "v0.9.0"
-    reason: "Better positioned before v1.0.0 when user base exists"
-    
-  - id: "FU-303"
-    name: "Support Agent System"
-    moved_to: "v0.9.0"
-    reason: "Better positioned before v1.0.0 when user base exists"
-
-execution_schedule:
-  batches:
-    # Batch 0: Documentation Generation
-    - batch_id: 0
-      feature_units: ["FU-300"]
-      dependencies: []
-
-    # Batch 1: Documentation Web Server
-    - batch_id: 1
-      feature_units: ["FU-301"]
-      dependencies: ["FU-300"]
-
-checkpoints:
-  checkpoint_1_after_batch: 1 # Review documentation generation before release
-
-acceptance_criteria:
-  product:
-    - criterion: "Comprehensive documentation available via web interface"
-      test: "tests/integration/documentation_web.test.ts"
-      metric: null
-    - criterion: "Support agent responds accurately to common inquiries (80%+ accuracy)"
-      test: "tests/integration/support_agent.test.ts"
-      metric: "support_agent_accuracy >= 0.80"
-    - criterion: "Documentation search functional"
-      test: "tests/integration/documentation_search.test.ts"
-      metric: null
-    - criterion: "MCP support endpoint operational"
-      test: "tests/integration/mcp_support_endpoint.test.ts"
-      metric: null
-  technical:
-    - criterion: "All P0 FUs deployed and passing tests"
-      test: null
-      metric: "SELECT COUNT(*) FROM feature_units WHERE priority='P0' AND status='completed'"
-    - criterion: "Documentation generation deterministic"
-      test: "tests/integration/documentation_generation.test.ts"
-      metric: null
-    - criterion: "Static documentation served efficiently (< 200ms page load)"
-      test: "tests/integration/documentation_performance.test.ts"
-      metric: "page_load_p95 < 200"
-    - criterion: "Documentation search responsive (< 500ms query response)"
-      test: "tests/integration/documentation_search.test.ts"
-      metric: "search_query_p95 < 500"
-    - criterion: "Support agent responses cite source documentation"
-      test: "tests/integration/support_agent.test.ts"
-      metric: "citation_rate >= 1.0"
-    - criterion: "MCP endpoint follows MCP protocol specification"
-      test: "tests/integration/mcp_support_endpoint.test.ts"
-      metric: null
-    - criterion: "Documentation generation integrated into build process"
-      test: null
-      metric: "Documentation generation runs automatically on build"
-  business:
-    - criterion: "Users can self-serve answers via documentation web interface"
-      test: null
-      metric: "Manual validation via web interface"
-    - criterion: "Users can query support via MCP without leaving AI tool"
-      test: null
-      metric: "Manual validation via MCP client"
-
-pre_mortem:
-  failure_modes:
-    - mode: "Documentation generation failures"
-      early_warning: "Documentation generation script fails, incomplete docs generated"
-      mitigation: "FU-300 includes validation checks, comprehensive test coverage"
-      rollback: "Revert documentation generation changes, use manual docs"
-    - mode: "Support agent accuracy below threshold"
-      early_warning: "Support agent test suite shows accuracy < 80%"
-      mitigation: "FU-303 includes accuracy validation, iterative improvement process"
-      rollback: "Disable support agent, fall back to static documentation only"
-    - mode: "MCP endpoint protocol violations"
-      early_warning: "MCP integration tests fail, protocol compliance issues"
-      mitigation: "FU-302 includes comprehensive MCP protocol tests"
-      rollback: "Revert MCP endpoint changes, check protocol compliance"
-    - mode: "Design system compliance failures"
-      early_warning: "UI components don't match design system, accessibility tests fail"
-      mitigation: "FU-301 includes design system compliance checks, reference docs/ui/design_system.md"
-      rollback: "Revert UI changes, ensure design system compliance before re-implementation"
-
-deployment:
-  target: "production" # All releases deploy to production at neotoma.io
-  target_url: "neotoma.io"
-  marketing: false # Not marketed release - no marketing activities
-  rollback_plan: "Revert code changes and redeploy to neotoma.io; restore previous documentation version if needed"
-
-monitoring:
-  key_metrics:
-    - "documentation_generation_success_rate"
-    - "documentation_page_load_p95"
-    - "documentation_search_latency_p95"
-    - "support_agent_query_success_rate"
-    - "support_agent_response_accuracy"
-    - "support_agent_citation_rate"
-    - "mcp_support_endpoint_success_rate"
-    - "mcp_support_endpoint_latency_p95"