neotoma 0.3.0 → 0.3.2

package/docs/releases/v0.1.0/mcp_actions_status.md

@@ -1,101 +0,0 @@
-# MCP Actions Status Across Releases
-## Complete MCP Action Catalog
-### ✅ v0.1.0 (Internal MCP Release) — 13 Actions
-**Core Record Operations (4):**
-- `store_record` (FU-201)
-- `update_record` (FU-203)
-- `retrieve_records` (FU-202)
-- `delete_record` (FU-204)
-**File Operations (2):**
-- `upload_file` (FU-205)
-- `get_file_url` (FU-206)
-**Observation & Snapshot Operations (5):**
-- `get_entity_snapshot` (FU-061)
-- `list_observations` (FU-061)
-- `get_field_provenance`  (FU-061)
-- `create_relationship`   (FU-061)
-- `list_relationships`    (FU-061)
-**Provider Integrations (2, Optional):**
-- `list_provider_catalog` (FU-208, optional)
-- `sync_provider_imports` (FU-208, optional)
-**Total:** 13 actions (11 required + 2 optional)
-### ✅ v0.2.2 (Capability Discovery) — Adds list_capabilities
-**Adds:**
-- `list_capabilities` (FU-304)
-**Total:** 14 actions (13 from v0.1.0 + 1 capability discovery action)
-**Note:** Enables dynamic discovery of available capabilities for payload submission. Integrations can discover capabilities at runtime without hardcoding capability IDs.
-### ✅ v1.0.0 (MVP) — Adds Provider Integrations
-**Adds (Required):**
-- `list_provider_catalog` (FU-208, now required)
-- `sync_provider_imports` (FU-208, now required)
-**Total:** 16 actions (14 from v0.2.2 + 2 provider actions)
-**Note:** v1.0.0 explicitly excludes Plaid and Metrics actions (see below).
-### ⏳ Post-MVP (Not Scheduled) — 6 Actions
-**Plaid Integration (4 actions):**
-- `plaid_create_link_token` (FU-207)
-- `plaid_exchange_public_token` (FU-207)
-- `plaid_sync` (FU-207)
-- `plaid_list_items` (FU-207)
-**Rationale:** Plaid serves Tier 3+ ICPs (Cross-Border Solopreneurs, Agentic Portfolio) who need live bank transaction sync, not Tier 1 MVP targets who primarily upload static documents (PDF invoices/receipts/statements).
-**Status:** FU-207 marked as "Post-MVP" in `MVP_FEATURE_UNITS.md`. No specific release assigned yet.
-**Metrics & Analytics (2 actions):**
-- `get_technical_metrics` (FU-800, Prometheus integration)
-- `get_product_analytics` (FU-803, PostHog/Mixpanel integration)
-**Rationale:** Requires Prometheus and PostHog/Mixpanel integration (Phase 8 observability). Enables AI-generated reports on system performance and user behavior.
-**Status:** 
-- FU-800 (Technical Metrics) — P1 priority, ⏳ Not Started
-- FU-803 (Product Analytics) — P1 priority, ⏳ Not Started
-- Not explicitly in v1.0.0 scope (v1.0.0 release plan excludes them)
-**Likely Release:** Post-v1.0.0 (v1.1.0+ or v2.0.0+)
-## Summary Table
-| Action | v0.1.0 | v0.2.2 | v1.0.0 | Post-MVP | Feature Unit | Notes |
-|--------|--------|--------|--------|----------|--------------|-------|
-| **Core Record Operations** |
-| `store_record` | ✅ | ✅ | ✅ | - | FU-201 | Required |
-| `update_record` | ✅ | ✅ | ✅ | - | FU-203 | Required |
-| `retrieve_records` | ✅ | ✅ | ✅ | - | FU-202 | Required |
-| `delete_record` | ✅ | ✅ | ✅ | - | FU-204 | Required |
-| **File Operations** |
-| `upload_file` | ✅ | ✅ | ✅ | - | FU-205 | Required |
-| `get_file_url` | ✅ | ✅ | ✅ | - | FU-206 | Required |
-| **Observation & Snapshot Operations** |
-| `get_entity_snapshot` | ✅ | ✅ | ✅ | - | FU-061 | Required |
-| `list_observations` | ✅ | ✅ | ✅ | - | FU-061 | Required |
-| `get_field_provenance` | ✅ | ✅ | ✅ | - | FU-061 | Required |
-| `create_relationship` | ✅ | ✅ | ✅ | - | FU-061 | Required |
-| `list_relationships` | ✅ | ✅ | ✅ | - | FU-061 | Required |
-| **Capability Discovery** |
-| `list_capabilities` | ❌ | ✅ | ✅ | - | FU-304 | Dynamic capability discovery |
-| **Provider Integrations** |
-| `list_provider_catalog` | ⏳ Optional | ⏳ Optional | ✅ | - | FU-208 | Required in v1.0.0 |
-| `sync_provider_imports` | ⏳ Optional | ⏳ Optional | ✅ | - | FU-208 | Required in v1.0.0 |
-| **Plaid Integration** |
-| `plaid_create_link_token` | ❌ | ❌ | ❌ | ⏳ | FU-207 | Post-MVP |
-| `plaid_exchange_public_token` | ❌ | ❌ | ❌ | ⏳ | FU-207 | Post-MVP |
-| `plaid_sync` | ❌ | ❌ | ❌ | ⏳ | FU-207 | Post-MVP |
-| `plaid_list_items` | ❌ | ❌ | ❌ | ⏳ | FU-207 | Post-MVP |
-| **Metrics & Analytics** |
-| `get_technical_metrics` | ❌ | ❌ | ❌ | ⏳ | FU-800 | Post-MVP |
-| `get_product_analytics` | ❌ | ❌ | ❌ | ⏳ | FU-803 | Post-MVP |
-**Legend:**
-- ✅ Included
-- ⏳ Optional / Planned
-- ❌ Explicitly Excluded
-## Release Breakdown
-### v0.1.0 (Internal MCP Release)
-- **Total Actions:** 13 (11 required + 2 optional)
-- **Focus:** Core Truth Layer validation via MCP
-- **Provider Actions:** Optional (FU-208)
-### v0.2.2 (Capability Discovery)
-- **Total Actions:** 14 (13 from v0.1.0 + 1 capability discovery action)
-- **Adds:** Dynamic capability discovery (`list_capabilities`)
-- **Focus:** Enable integrations to discover available capabilities at runtime
-### v1.0.0 (MVP)
-- **Total Actions:** 16 (14 from v0.2.2 + 2 provider actions)
-- **Adds:** Provider integrations (FU-208, now required)
-- **Excludes:** Plaid (FU-207), Metrics (FU-800, FU-803)
-### Post-MVP (Future Releases)
-- **Plaid Actions:** 4 actions (FU-207)
-- No specific release assigned. Will be added when Tier 3+ ICP demand is validated.
-- **Metrics Actions:** 2 actions (FU-800, FU-803)
-   No specific release assigned. Requires observability infrastructure (Prometheus, PostHog/Mixpanel).

package/docs/releases/v0.1.0/release_plan.md

@@ -1,196 +0,0 @@
-## Release v0.1.0 — Internal MCP Release
-### 1. Release Overview
-- **Release ID**: `v0.1.0`
-- **Name**: Internal MCP Release
-- **Release Type**: Not Marketed (production deployment without marketing activities)
-- **Goal**: Validate deterministic ingestion, extraction, entity resolution, event generation, and graph construction through MCP-only access. Enable internal validation via Cursor and ChatGPT integration without UI or multi-user infrastructure.
-- **Priority**: P0 (critical for MVP foundation)
-- **Target Ship Date**: When ready
-- **Marketing Required**: No (not marketed release)
-- **Deployment**: Production (neotoma.io)
-#### 1.1 Canonical Specs (Authoritative Sources)
-- **Manifest**: `docs/NEOTOMA_MANIFEST.md`
-- **Internal MCP Release Spec**: `docs/specs/INTERNAL_MCP_RELEASE.md`
-- **MVP Feature Units**: `docs/specs/MVP_FEATURE_UNITS.md`
-- **MCP Specification**: `docs/specs/MCP_SPEC.md`
-This release plan coordinates the internal MCP release scope into a concrete release plan.
-### 2. Scope
-#### 2.1 Included Feature Units (P0 Critical Path)
-**Blockchain-Ready Architecture Foundation:**
-- `FU-050`: Event-Sourcing Foundation (append-only event log, reducers, historical replay)
-- `FU-051`: Repository Abstractions (EventRepository, StateRepository interfaces)
-- `FU-052`: Reducer Versioning (version metadata, reducer registry)
-- `FU-053`: Cryptographic Schema Fields (signer_public_key, signature fields)
-- `FU-054`: Hash Chaining Schema Fields (previous_event_hash, event_hash fields)
-**Observation Architecture (Building on Event-Sourcing Foundation):**
-- `FU-055`: Observation Storage Layer (observations, snapshots, raw_fragments tables)
-- `FU-056`: Enhanced Reducer Engine for Observations (merge strategies, provenance)
-- `FU-057`: Schema Registry Service (config-driven schemas, versioning)
-- `FU-058`: Observation-Aware Ingestion Pipeline (observation creation, reducer invocation)
-- `FU-059`: Relationship Types (first-class typed relationships)
-- `FU-061`: MCP Actions for Observation Architecture (snapshot, provenance, relationships)
-**Optional (P1):**
-- `FU-060`: Automated Schema Promotion (optional, pattern detection from raw_fragments)
-**Core Backend Services:**
-- `FU-000`: Database Schema v1.0 (single-user, no RLS, includes state_events table)
-- `FU-002`: Configuration Management
-- `FU-100`: File Analysis Service (rule-based extraction, type detection analytics)
-- `FU-101`: Entity Resolution Service
-- `FU-102`: Event Generation Service
-- `FU-103`: Graph Builder Service
-- `FU-105`: Search Service (structured search only, deterministic ranking)
-**MCP Actions:**
-- `FU-200`: MCP Server Core
-- `FU-201`: MCP Action — `store_record` (emits events, applies reducers)
-- `FU-202`: MCP Action — `retrieve_records`
-- `FU-203`: MCP Action — `update_record` (emits events, applies reducers)
-- `FU-204`: MCP Action — `delete_record` (emits events, applies reducers)
-- `FU-205`: MCP Action — `upload_file`
-- `FU-206`: MCP Action — `get_file_url`
-- `FU-061`: MCP Actions — `get_entity_snapshot`, `list_observations`, `get_field_provenance`, `create_relationship`, `list_relationships`
-**Optional (P1):**
-- `FU-104`: Embedding Service (optional, not required for validation)
-- `FU-208`: MCP Provider Integrations (optional, Gmail testing)
-#### 2.2 Explicitly Excluded
-- All UI components (FU-300 through FU-307)
-- Multi-user infrastructure (FU-700, FU-701, FU-702, FU-703)
-- Onboarding flow (FU-400-403)
-- Plaid integration (FU-207, post-MVP)
-- Semantic/vector search (structured search only)
-- LLM-based extraction (rule-based only)
-### 3. Release-Level Acceptance Criteria
-#### 3.1 Product
-- Core workflow: **upload_file → extraction → observation creation → reducer execution → snapshot computation → entity resolution → event generation → graph insertion → retrieve_records** is functional via MCP.
-- MCP actions return structured, deterministic responses.
-- Entity resolution validated: same entity name → same entity_id across multiple uploads.
-- Timeline events validated: date fields → chronological events.
-- **4-layer model operational**: Document → Entity → Observation → Snapshot data flow validated.
-- **Multi-source entity resolution**: Multiple observations about same entity merge correctly via reducers.
-- **Provenance tracking**: Every snapshot field traces to source observations and documents.
-#### 3.2 Technical
-- Deterministic ingestion and extraction for PDF, JPG, PNG (100% reproducible, 100 runs).
-- Graph integrity: **0 orphans**, **0 cycles** in memory graph.
-- Deterministic search ranking (same query + same DB state → same order).
-- **Event-sourcing foundation operational**: Events emitted for all state changes, reducers applied, historical replay functional.
-- **Repository abstractions in place**: Domain logic isolated from storage via repository interfaces.
-- **Type detection analytics**: Unknown schema types tracked in `extraction_metadata` and telemetry events (forward-compatible with E2EE).
-- **Observation layer operational**: Observations created during ingestion, snapshots computed by reducers.
-- **Reducer determinism validated**: Same observations + merge rules → same snapshot (100 runs).
-- **Schema registry functional**: Config-driven schemas loaded and applied.
-- **Relationship types operational**: First-class typed relationships (PART_OF, CORRECTS, etc.).
-- All P0 Feature Units listed above are `completed` with passing tests.
-- 100% test coverage on critical path (ingestion, extraction, observation creation, reducer execution, entity resolution, events, graph builder, search, event-sourcing, repositories).
-- MCP server operational with all core actions including observation architecture actions (using event-sourcing).
-#### 3.3 Business
-- Internal validation successful via Cursor and ChatGPT MCP integration.
-- Core capabilities validated before building UI and multi-user infrastructure.
-### 4. Cross-FU Integration Scenarios (High-Level)
-These scenarios must pass end-to-end before v0.1.0 is approved:
-1. **File Upload → Extraction → Query Flow**
-   - Upload PDF via MCP `upload_file` action.
-   - System extracts fields via rule-based extraction (FU-100).
-   - Entities resolved deterministically (FU-101).
-   - Events generated and inserted into graph (FU-102, FU-103).
-   - Query records via `retrieve_records` with deterministic ranking (FU-105).
-2. **Entity Resolution Validation**
-   - Upload two documents containing "Acme Corp" and "ACME CORP".
-   - Verify both records link to same entity_id (canonical resolution).
-3. **Timeline Event Validation**
-   - Upload document with date fields.
-   - Verify events generated with correct timestamps.
-   - Query events chronologically.
-4. **Graph Integrity Validation**
-   - Upload multiple documents.
-   - Verify 0 orphan nodes, 0 cycles in graph.
-   - Verify transactional inserts (all-or-nothing).
-5. **Determinism Validation**
-   - Upload same file 100 times.
-   - Verify identical extraction, entity IDs, event IDs.
-   - Verify same query returns same order.
-6. **Event-Sourcing Validation**
-   - Create/update/delete records via MCP.
-   - Verify events emitted to `state_events` table.
-   - Verify state reconstructed via reducers matches direct DB state.
-   - Verify historical replay: get record state at specific timestamp.
-7. **Repository Abstraction Validation**
-   - Verify domain services use repository interfaces (no direct DB access).
-   - Verify file-based repository implementations functional.
-8. **Observation Architecture Validation**
-   - Upload document via MCP `upload_file` action.
-   - Verify observations created for each entity.
-   - Verify reducer computes snapshots with provenance.
-   - Verify multiple observations about same entity merge correctly.
-   - Query entity snapshot via `get_entity_snapshot` MCP action.
-   - Trace field provenance via `get_field_provenance` MCP action.
-9. **Multi-Source Entity Resolution Validation**
-   - Upload two documents about same entity from different sources.
-   - Verify observations created for each.
-   - Verify snapshot correctly merges observations.
-   - Verify provenance traces to both documents.
-10. **Relationship Types Validation**
-    - Create typed relationships (PART_OF, CORRECTS, etc.) via MCP.
-    - Verify graph traversal queries work.
-    - Verify relationship metadata preserved.
-The detailed test specifications for these flows live in `docs/releases/v0.1.0/integration_tests.md`.
-### 5. Deployment and Rollout Strategy
-- **Deployment Target**: Production (neotoma.io)
-  - All releases deploy to production at neotoma.io
-  - Deploy MCP server to neotoma.io
-  - MCP endpoints accessible via MCP protocol
-- **Marketing Strategy**: Not Marketed
-  - No pre-launch marketing activities
-  - No post-launch marketing activities
-  - No user acquisition campaigns
-  - No announcement or promotion
-  - Release deployed silently to production
-- **Rollback Plan**: Revert code changes and redeploy to neotoma.io
-### 6. Post-Release Validation
-- Validate core capabilities via MCP integration:
-  - Cursor integration tested (upload_file, retrieve_records)
-  - ChatGPT integration tested (store_record, retrieve_records)
-  - Entity resolution validated
-  - Event generation validated
-  - Graph integrity validated
-  - Search determinism validated
-### 7. Success Criteria
-**Internal Release is Complete When:**
-1. ✅ All core MCP actions functional (using event-sourcing)
-2. ✅ File upload → extraction → observation creation → reducer execution → graph insertion working end-to-end
-3. ✅ Entity resolution validated (canonical IDs)
-4. ✅ Event generation validated (timeline events)
-5. ✅ Graph integrity validated (0 orphans, 0 cycles)
-6. ✅ Search deterministic (same query → same order)
-7. ✅ **Event-sourcing foundation operational** (events emitted, reducers applied, historical replay functional)
-8. ✅ **Repository abstractions in place** (domain logic isolated from storage)
-9. ✅ **Observation layer operational** (observations created, snapshots computed, provenance tracked)
-10. ✅ **4-layer model functional** (Document → Entity → Observation → Snapshot)
-11. ✅ **Reducer determinism validated** (same observations → same snapshot)
-12. ✅ **Relationship types operational** (PART_OF, CORRECTS, etc.)
-13. ✅ Cursor integration tested (upload_file, retrieve_records, get_entity_snapshot)
-14. ✅ ChatGPT integration tested (store_record, retrieve_records, get_entity_snapshot)
-15. ✅ All critical path tests passing (100% coverage)
-16. ✅ Determinism validated (100 runs, same input → same output)
-### 8. Status
-- **Current Status**: `planning`
-- **Release Type**: Not Marketed
-- **Deployment**: Production (neotoma.io)
-- **Owner**: Mark Hendrickson
-- **Notes**:
-  - Not marketed release - deploys to production without marketing activities
-  - All releases deploy to production at neotoma.io
-  - No UI or multi-user infrastructure required.
-  - Focus on MCP-only validation of core Truth Layer capabilities.
-  - Type detection analytics implemented for schema expansion insights (see `type_detection_analytics.md`).
-  - Observation architecture builds on event-sourcing foundation (FU-050 through FU-054).
-  - Four-layer truth model (Document → Entity → Observation → Snapshot) enables multi-source entity resolution and full provenance tracking.
-### 9. Related Documentation
-- `type_detection_analytics.md` — Type detection analytics strategy (forward-compatible with E2EE)
-- `integration_tests.md` — Cross-FU integration test specifications
-- `execution_schedule.md` — Detailed batch execution plan
-- `manifest.yaml` — Feature Unit manifest and dependencies
-- `fu_spec_status.md` — Feature Unit specification status (which FUs have standalone specs)
-### 10. Feature Unit Specifications
-**Specification Sources:**
-- **Standalone Specs:** FU-050 through FU-054 have standalone spec files in `docs/feature_units/completed/FU-XXX/`
-- **MVP_FEATURE_UNITS.md:** All other FUs have specifications in `docs/specs/MVP_FEATURE_UNITS.md`
-**See:** `fu_spec_status.md` for complete status of all FUs.

package/docs/releases/v0.1.0/status.md

@@ -1,148 +0,0 @@
-## Release v0.1.0 — Status
-### 1. Summary
-- **Release ID**: `v0.1.0`
-- **Name**: Internal MCP Release
-- **Status**: `ready_for_deployment` ✅ (remediation validated)
-- **Release Type**: Not Marketed
-- **Deployment**: Production (neotoma.io)
-- **Owner**: Mark Hendrickson
-- **Target Date**: When ready
-- **Marketing**: No (not marketed release)
-- **Remediation Date**: 2025-12-11
-- **Test Validation Date**: 2025-12-11
-- **Test Pass Rate**: 99.5% (373/375 overall, 146/146 v0.1.0 tests)
-### 1.1 Time Tracking
-- **Development Start Date**: 2025-12-09 _(Estimated based on remediation date)_
-- **Development Finish Date**: 2025-12-11
-- **Deployment Date**: _[To be recorded when deployed]_
-- **Completion Date**: _[To be recorded when status changes to `completed`]_
-- **Estimated Development Time**: _[Not recorded in original plan]_
-- **Actual Development Time**: ~2-3 days (Dec 9-11, 2025)
-- **Estimation Accuracy**: _[Baseline established for future estimates]_
-### 2. Batch Progress
-| Batch ID | Feature Units                  | Status      | Notes                              |
-| -------- | ------------------------------ | ----------- | ---------------------------------- |
-| 0        | FU-000, FU-002                 | ✅ Complete |                                    |
-| 0.5      | FU-050, FU-051                 | ✅ Complete |                                    |
-| 0.6      | FU-052, FU-053, FU-054         | ✅ Complete |                                    |
-| 0.7      | FU-055, FU-057                 | ✅ Complete |                                    |
-| 0.8      | FU-056, FU-059                 | ✅ Complete |                                    |
-| 1        | FU-200, FU-100                 | ✅ Complete | Rule-based extraction implemented  |
-| 2        | FU-101, FU-102                 | ✅ Complete | Enhanced with database persistence |
-| 3        | FU-103                         | ✅ Complete | Enhanced graph integrity checks    |
-| 4        | FU-105                         | ✅ Complete |                                    |
-| 5        | FU-201, FU-203, FU-204, FU-206 | ✅ Complete |                                    |
-| 6        | FU-202, FU-205                 | ✅ Complete |                                    |
-| 6.5      | FU-058                         | ✅ Complete |                                    |
-| 6.6      | FU-061                         | ✅ Complete | Enhanced with 5 new MCP actions    |
-| 7        | FU-104, FU-208                 | ✅ Complete | Optional (FU-208 not started)      |
-### 3. Feature Unit Status
-| FU ID  | Name                          | Status         | Notes                                          |
-| ------ | ----------------------------- | -------------- | ---------------------------------------------- |
-| FU-000 | Database Schema v1.0          | ✅ Complete    | Enhanced with entities, events, edges tables   |
-| FU-002 | Configuration Management      | ✅ Complete    |                                                |
-| FU-050 | Event-Sourcing Foundation     | ✅ Complete    | Historical API endpoints added                 |
-| FU-051 | Repository Abstractions       | ✅ Complete    | DB and file implementations                    |
-| FU-052 | Reducer Versioning            | ✅ Complete    | Reducer registry implemented                   |
-| FU-053 | Cryptographic Schema Fields   | ✅ Complete    | Agent identity abstraction                     |
-| FU-054 | Hash Chaining Schema Fields   | ✅ Complete    | Hash utilities (stub)                          |
-| FU-055 | Observation Storage Layer     | ✅ Complete    | Tables and repositories                        |
-| FU-056 | Enhanced Reducer Engine       | ✅ Complete    | Merge strategies implemented                   |
-| FU-057 | Schema Registry Service       | ✅ Complete    | Schema registry service                        |
-| FU-058 | Observation-Aware Ingestion   | ✅ Complete    | Integrated into upload pipeline                |
-| FU-059 | Relationship Types            | ✅ Complete    | Relationships service                          |
-| FU-061 | MCP Actions for Observations  | ✅ Complete    | All 5 actions implemented (remediated)         |
-| FU-100 | File Analysis Service         | ✅ Complete    | Rule-based extraction implemented, LLM removed |
-| FU-101 | Entity Resolution Service     | ✅ Complete    | Enhanced with database persistence             |
-| FU-102 | Event Generation Service      | ✅ Complete    | Enhanced with database persistence             |
-| FU-103 | Graph Builder Service         | ✅ Complete    | Enhanced with entities/events/edges support    |
-| FU-105 | Search Service                | ✅ Complete    | Deterministic ranking implemented              |
-| FU-200 | MCP Server Core               | ✅ Complete    |                                                |
-| FU-201 | MCP Action — store_record     | ✅ Complete    |                                                |
-| FU-202 | MCP Action — retrieve_records | ✅ Complete    |                                                |
-| FU-203 | MCP Action — update_record    | ✅ Complete    |                                                |
-| FU-204 | MCP Action — delete_record    | ✅ Complete    |                                                |
-| FU-205 | MCP Action — upload_file      | ✅ Complete    |                                                |
-| FU-206 | MCP Action — get_file_url     | ✅ Complete    |                                                |
-| FU-104 | Embedding Service             | ✅ Complete    | Optional                                       |
-| FU-208 | MCP Provider Integrations     | ⏳ Not Started | Optional                                       |
-### 4. Checkpoints
-- **Checkpoint 0 — Release Planning**: `completed`
-  - `release_plan.md` and `manifest.yaml` created.
-  - Execution schedule defined in `execution_schedule.md`.
-- **Checkpoint 0.5 — Blockchain Foundation Review**: `completed`
-  - Configured after Batch 0.6 (blockchain-ready architecture foundation complete).
-  - Batch 0.6 completed: FU-052 (Reducer Versioning), FU-053 (Cryptographic Fields), FU-054 (Hash Chaining) all complete.
-  - Blockchain-ready architecture foundation validated.
-- **Checkpoint 1 — Mid-Release Review**: `completed`
-  - Configured after Batch 4 (graph builder and search).
-  - Batch 4 completed: FU-105 (Search Service) complete.
-  - Graph builder (FU-103) and search services validated.
-- **Checkpoint 2 — Pre-Release Sign-Off**: `completed`
-  - All batches complete (14/14).
-  - Release status: `ready_for_deployment`.
-  - All P0 Feature Units complete (26/27, with FU-208 optional and not started).
-- **Checkpoint 3 — Post-Remediation Review**: `in_progress`
-  - Fidelity review completed on 2025-12-11
-  - All critical gaps addressed
-  - Pending: migration execution, test execution, coverage validation
-### 5. Integration Test Status
-| Test ID | Name                                | Status     | Tests Passed | Notes                            |
-| ------- | ----------------------------------- | ---------- | ------------ | -------------------------------- |
-| IT-001  | File Upload → Extraction → Query    | ✅ Passing | All          | Pipeline integration complete    |
-| IT-002  | Entity Resolution Validation        | ✅ Passing | 3/3          | Database validation working      |
-| IT-003  | Timeline Event Validation           | ✅ Passing | 4/4          | Persistence tests passing        |
-| IT-004  | Graph Integrity Validation          | ✅ Passing | 6/6          | Orphan/cycle detection working   |
-| IT-005  | Determinism Validation              | ✅ Passing | All          | Determinism validated            |
-| IT-006  | MCP Action Validation               | ✅ Passing | 11/11        | All 11 MCP actions tested        |
-| IT-007  | Event-Sourcing Validation           | ✅ Passing | All          | Event sourcing operational       |
-| IT-008  | Observation Architecture Validation | ✅ Passing | 5/5          | Observation MCP actions working  |
-| IT-009  | Multi-Source Entity Resolution      | ✅ Passing | All          | Multi-source merging validated   |
-| IT-010  | Reducer Determinism Validation      | ✅ Passing | All          | Reducer determinism confirmed    |
-| IT-011  | Relationship Types Validation       | ✅ Passing | 4/4          | Relationship MCP actions working |
-**Summary:** 11/11 integration test suites passing (146/146 tests - 100%)
-**Additional Test Files Created:**
-| Test ID | Name                     | Status      | Test Count |
-| ------- | ------------------------ | ----------- | ---------- |
-| NEW-001 | Error Case Tests         | ✅ Complete | ~40 tests  |
-| NEW-002 | Edge Case Tests          | ✅ Complete | ~30 tests  |
-| NEW-003 | Validation Schema Tests  | ✅ Complete | ~25 tests  |
-| NEW-004 | Graph Builder Unit Tests | ✅ Complete | ~6 tests   |
-**Remediation Summary (2025-12-11):**
-- Database tables created: 3 migrations (entities, timeline_events, graph edges)
-- Services updated: 4 files (entity resolution, event generation, graph builder, observation ingestion)
-- MCP actions implemented: 5 new actions (get_entity_snapshot, list_observations, get_field_provenance, create_relationship, list_relationships)
-- Integration tests enhanced: 6 files updated with database validation
-- New test files created: 4 files (~101 new test cases)
-**Deployment Requirements Status:**
-1. ✅ Database migrations applied (`npm run migrate`)
-2. ✅ All tests executed (375 tests, 373 passing - 99.5%)
-3. ✅ All v0.1.0 integration tests passing (146/146 - 100%)
-4. ✅ Pipeline integration complete (entities, events, edges all persisting)
-5. ⏳ Install `@vitest/coverage-v8` package (optional)
-6. ⏳ Generate coverage report (optional)
-7. ⏳ Manual validation via Cursor/ChatGPT MCP integration
-**Test Execution Results (2025-12-11):**
-- Total tests: 375
-- Passed: 373 (99.5%)
-- Failed: 2 (pre-existing record_types.test.ts issues, non-blocking)
-- v0.1.0 integration tests: 146/146 (100%)
-### 6. Decision Log
-| Date       | Decision                                  | Rationale                                                 |
-| ---------- | ----------------------------------------- | --------------------------------------------------------- |
-| 2024-12-02 | Created v0.1.0 not marketed MCP release   | Split single-user MCP capabilities from MVP               |
-| 2024-12-02 | Excluded UI and multi-user infrastructure | Focus on MCP-only validation                              |
-| 2024-12-02 | Made FU-104 and FU-208 optional           | Not required for core validation                          |
-| 2025-12-11 | Fidelity remediation completed            | Addressed gaps between plan and implementation            |
-| 2025-12-11 | Added 3 database migrations               | Complete four-layer truth model (entities, events, edges) |
-| 2025-12-11 | Implemented 5 missing MCP actions         | FU-061 completion (observation/relationship actions)      |
-| 2025-12-11 | Created comprehensive test coverage       | Added error cases, edge cases, validation schema tests    |
-### 7. Notes
-- Not marketed release - deploys to production without marketing activities.
-- All releases deploy to production at neotoma.io.
-- No UI or multi-user infrastructure required.
-- Focus on MCP-only validation of core Truth Layer capabilities.
-- Type detection analytics implemented as part of FU-100 (see `type_detection_analytics.md`).
-- Release workflow pattern defined in `docs/feature_units/standards/release_workflow.md`.
-- This status file is the **single source of truth** for v0.1.0 release progress.
-- **Remediation (2025-12-11)**: Critical fidelity gaps addressed. See `test_coverage_gap_analysis.md` for complete details.

package/docs/releases/v0.1.0/test_coverage_setup_notes.md

@@ -1,39 +0,0 @@
-# Test Coverage Setup Notes
-## Required Dependencies
-To run test coverage, install the vitest coverage package:
-```bash
-npm install --save-dev @vitest/coverage-v8
-```
-## Running Coverage
-After installing dependencies:
-```bash
-# Run full test coverage
-npm run test:coverage
-# Run coverage for critical path services only
-npm run test:coverage:critical
-```
-## Coverage Configuration
-Coverage is configured in `vitest.config.ts` with the following settings:
-- **Provider**: v8
-- **Reporters**: text, json, html, lcov
-- **Thresholds**: 80% for lines, functions, branches, statements
-- **Critical Paths**: 100% coverage required for:
-  - `src/services/entity_resolution.ts`
-  - `src/services/event_generation.ts`
-  - `src/services/graph_builder.ts`
-  - `src/services/file_analysis.ts`
-  - `src/services/search.ts`
-  - `src/services/observation_ingestion.ts`
-  - `src/reducers/**/*.ts`
-## Coverage Reports
-Coverage reports will be generated in:
-- `coverage/index.html` - HTML report (browse in browser)
-- `coverage/coverage-final.json` - JSON report
-- `coverage/lcov.info` - LCOV format for CI/CD integration
-## Next Steps
-1. Install `@vitest/coverage-v8` package
-2. Run `npm run test:coverage`
-3. Review coverage reports
-4. Document gaps in `test_coverage_gap_analysis.md`
-5. Add tests to close gaps
-6. Verify 100% critical path coverage before v0.1.0 deployment

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

@@ -1,153 +0,0 @@
-release:
-  id: "v0.1.1"
-  name: "Documentation & Support 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
-
-# Execution strategy
-execution_strategy:
-  type: "multi_agent" # "multi_agent" or "sequential"
-  max_parallel_fus: 2 # 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.1.1/agent_status.json"
-
-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"
-
-  # MCP Support Inquiry Endpoint
-  - id: "FU-302"
-    priority: "P0"
-    dependencies: ["FU-200"] # MCP Server Core from v0.1.0
-    risk_level: "low"
-    notes: "New MCP action for support queries"
-
-  # Support Agent System
-  - id: "FU-303"
-    priority: "P0"
-    dependencies: ["FU-300", "FU-301", "FU-302"]
-    risk_level: "medium"
-    notes: "RAG-based agent using static documentation as knowledge base"
-
-execution_schedule:
-  batches:
-    # Batch 0: Documentation Generation (can run independently)
-    - batch_id: 0
-      feature_units: ["FU-300"]
-      dependencies: []
-
-    # Batch 1: Documentation Web Server (depends on generated docs)
-    - batch_id: 1
-      feature_units: ["FU-301"]
-      dependencies: ["FU-300"]
-
-    # Batch 2: MCP Support Endpoint (depends on MCP Server Core from v0.1.0)
-    - batch_id: 2
-      feature_units: ["FU-302"]
-      dependencies: ["FU-200"] # Assumes v0.1.0 FU-200 is complete
-
-    # Batch 3: Support Agent System (depends on all previous components)
-    - batch_id: 3
-      feature_units: ["FU-303"]
-      dependencies: ["FU-300", "FU-301", "FU-302"]
-
-checkpoints:
-  checkpoint_1_after_batch: 1 # Review documentation generation before proceeding
-  checkpoint_2_after_batch: 3 # Pre-release sign-off after support agent integration
-
-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"