neotoma 0.3.0 → 0.3.2

package/docs/feature_units/standards/release_report_spec.md

@@ -1,444 +0,0 @@
-# Release Report Specification
-**Purpose:** Defines the structure, format, and generation rules for release build reports.
-**Related Documents:**
-- [`release_workflow.md`](./release_workflow.md) — Release workflow integration
-- [`discovery_process.md`](./discovery_process.md) — Discovery report formats
-- [`../../.cursor/rules/post_build_testing.md`](../../.cursor/rules/post_build_testing.md) — Post-build testing requirements
-**CRITICAL REQUIREMENT:** 
-- **Release reports MUST be generated immediately after all batches complete** (per `foundation/development/release_workflow.md` Step 1.4)
-- **Section 9 (Testing Guidance) is REQUIRED** and MUST include all manual test cases from `integration_tests.md`
-- **Agents MUST always generate the complete release report** after completing a release build
-- **Report generation is a blocker** - release cannot transition to `in_testing` status until report exists with Section 9 populated
-- [`release_report_generation.md`](./release_report_generation.md) — Step-by-step generation guide
-- [`release_report_template.md`](./release_report_template.md) — Report template with placeholders
-## 1. Report Structure
-### 1.1 Required Sections
-Release reports MUST include the following sections in order:
-1. **Header** — Release metadata (ID, name, status, generation date)
-2. **Executive Summary** — High-level completion metrics and status
-3. **Batch Completion Summary** — Batch-by-batch completion status
-4. **Feature Unit Completion Summary** — Detailed FU status breakdown
-5. **Checkpoint Status** — Checkpoint completion tracking
-6. **Integration Test Results** — Test execution results
-7. **Key Achievements** — Completed FUs grouped by category
-8. **Issues and Blockers** — Partial/failed FUs and test failures
-9. **Decision Log Summary** — Key decisions made during release
-10. **Next Steps** — Recommended actions based on release status
-11. **Testing Guidance** — Concrete steps for testing built Feature Units (integration tests, manual validation, acceptance criteria)
-12. **Release Metrics** — Quantitative completion and quality metrics
-13. **Related Documents** — Links to related release documentation
-### 1.2 Section Templates
-#### Header Template
-```markdown
-# Release {RELEASE_ID} — Build Report
-**Report Generated:** {REPORT_DATE}
-**Release Name:** {RELEASE_NAME}
-**Release Status:** {RELEASE_STATUS}
-```
-#### Executive Summary Template
-```markdown
-## Executive Summary
-{STATUS_ICON} **Release Status:** {RELEASE_STATUS}
-- **Batches:** {COMPLETED_BATCHES}/{TOTAL_BATCHES} complete ({BATCH_COMPLETION}%)
-- **Feature Units:** {COMPLETED_FUS}/{TOTAL_FUS} complete ({FU_COMPLETION}%)
-- **Checkpoints:** {COMPLETED_CHECKPOINTS}/{TOTAL_CHECKPOINTS} completed
-- **Integration Tests:** {COMPLETED_TESTS}/{TOTAL_TESTS} passed
-{CONDITIONAL_WARNINGS}
-```
-**Conditional Warnings:**
-- If `PARTIAL_FUS > 0`: Show warning about partial FUs
-- If `FAILED_FUS > 0`: Show critical alert about failed FUs
-#### Batch Completion Summary Template
-```markdown
-## 1. Batch Completion Summary
-| Batch ID | Feature Units | Status | Completion |
-| -------- | ------------- | ------ | ---------- |
-{BATCH_ROWS}
-**Summary:**
-- ✅ **Complete:** {COMPLETED_BATCHES} batch(es)
-- ⚠️ **Partial:** {PARTIAL_BATCHES} batch(es)
-- ❌ **Incomplete:** {INCOMPLETE_BATCHES} batch(es)
-```
-**Batch Row Format:**
-```markdown
-| {BATCH_ID} | {FU_LIST} | {STATUS} | {ICON} |
-```
-**Status Icons:**
-- `Complete` → ✅
-- `Partial` → ⚠️
-- Other → ❌
-#### Feature Unit Completion Summary Template
-```markdown
-## 2. Feature Unit Completion Summary
-### 2.1 By Status
-| Status                | Count             | Percentage           |
-| --------------------- | ----------------- | -------------------- |
-| ✅ Complete           | {COMPLETED_COUNT} | {COMPLETED_PERCENT}% |
-| ⚠️ Partial            | {PARTIAL_COUNT}   | {PARTIAL_PERCENT}%   |
-| ❌ Failed/Not Started | {FAILED_COUNT}    | {FAILED_PERCENT}%    |
-| **Total**             | **{TOTAL}**       | **100%**             |
-### 2.2 Feature Unit Details
-| FU ID | Name | Status | Notes |
-| ----- | ---- | ------ | ----- |
-{FU_ROWS}
-```
-**FU Row Format:**
-```markdown
-| {FU_ID} | {FU_NAME} | {STATUS_ICON} {STATUS} | {NOTES} |
-```
-**Status Icons:**
-- Status contains "Complete" → ✅
-- Status contains "Partial" → ⚠️
-- Other → ❌
-#### Checkpoint Status Template
-```markdown
-## 3. Checkpoint Status
-{CHECKPOINT_ITEMS}
-**Completion:** {COMPLETED}/{TOTAL} checkpoints completed
-```
-**Checkpoint Item Format:**
-```markdown
-- {ICON} **{CHECKPOINT_NAME}**: `{STATUS}`
-```
-**Status Icons:**
-- `completed` → ✅
-- `pending` → ⏳
-- Other → ❌
-#### Integration Test Results Template
-```markdown
-## 4. Integration Test Results
-{TEST_TABLE}
-**Summary:** {COMPLETED}/{TOTAL} tests passed
-```
-**Test Table Format:**
-```markdown
-| Test ID | Name | Status |
-| ------- | ---- | ------ |
-{TEST_ROWS}
-```
-**Test Row Format:**
-```markdown
-| {TEST_ID} | {TEST_NAME} | {ICON} {STATUS} | {FUS_TESTED} | {DESCRIPTION} |
-```
-**Status Icons:**
-- `passed` or `completed` → ✅
-- `failed` → ❌
-- Other → ⏳
-**Test Case Details Format:**
-```markdown
-#### {TEST_ID}: {TEST_NAME}
-**Goal:** {GOAL}
-**Test Steps:**
-{TEST_STEPS}
-**Expected Results:**
-{EXPECTED_RESULTS}
-**Status:** {ICON} {STATUS}
-```
-Extract from `integration_tests.md`:
-- Goal from "Goal:" line
-- Test Steps from "Steps:" section
-- Expected Results from "Expected Results:" section
-- Status from status.md integration test status
-#### Key Achievements Template
-```markdown
-## 5. Key Achievements
-{COMPLETED_FUS_SECTION}
-### Infrastructure Delivered
-{INFRASTRUCTURE_FUS}
-### Core Services Delivered
-{CORE_SERVICES_FUS}
-### MCP Actions Delivered
-{MCP_ACTIONS_FUS}
-```
-**FU Categories:**
-- **Infrastructure:** FU-000, FU-002, FU-050, FU-051, FU-052, FU-053, FU-054
-- **Core Services:** FU-100, FU-101, FU-102, FU-103, FU-105
-- **MCP Actions:** FU-200, FU-201, FU-202, FU-203, FU-204, FU-205, FU-206, FU-061
-**Completed FUs Section Format:**
-```markdown
-### Completed Feature Units
-{FU_LIST}
-```
-**FU List Item Format:**
-```markdown
-- ✅ **{FU_ID}**: {FU_NAME}{NOTES}
-```
-#### Issues and Blockers Template
-```markdown
-## 6. Issues and Blockers
-{PARTIAL_FUS_SECTION}
-{FAILED_FUS_SECTION}
-{FAILED_TESTS_SECTION}
-```
-**Partial FUs Section:**
-```markdown
-### Partial Feature Units Requiring Follow-up
-{FU_LIST}
-```
-**Failed FUs Section:**
-```markdown
-### Failed or Not Started Feature Units
-{FU_LIST}
-```
-**Failed Tests Section:**
-```markdown
-### Failed Integration Tests
-{TEST_LIST}
-```
-**FU List Item Format:**
-```markdown
-- {ICON} **{FU_ID}**: {FU_NAME}
-  - {NOTES}
-```
-#### Decision Log Summary Template
-```markdown
-## 7. Decision Log Summary
-{DECISION_TABLE}
-```
-**Decision Table Format:**
-```markdown
-| Date | Decision | Rationale |
-| ---- | -------- | --------- |
-{DECISION_ROWS}
-```
-**Decision Row Format:**
-```markdown
-| {DATE} | {DECISION} | {RATIONALE} |
-```
-#### Next Steps Template
-```markdown
-## 8. Next Steps
-{STATUS_BASED_RECOMMENDATIONS}
-## 9. Testing Guidance
-{TESTING_GUIDANCE_SECTION}
-```
-**Testing Guidance Section Format:**
-- Integration Tests: List all tests from `integration_tests.md` with IDs, names, and FUs tested
-- Test Commands: Extract npm test commands from test definitions
-- Manual Validation: List manual validation steps (e.g., Cursor/ChatGPT integration)
-- Acceptance Criteria: Reference acceptance criteria from `release_plan.md` or `acceptance_criteria.md`
-**Status-Based Recommendations:**
-**Ready for Deployment:**
-```markdown
-### Ready for Deployment
-✅ Release is ready for deployment. Recommended next steps:
-1. **Final Review:** Conduct final code review and acceptance criteria validation
-2. **Integration Testing:** Run all integration tests to validate end-to-end workflows
-3. **Deployment:** Deploy to target environment (internal validation)
-4. **Monitoring:** Set up monitoring and observability for post-deployment validation
-5. **Documentation:** Update deployment documentation and runbooks
-```
-**Completed:**
-```markdown
-### Release Completed
-✅ Release has been completed and deployed. Recommended next steps:
-1. **Post-Deployment Validation:** Validate all acceptance criteria in production
-2. **Monitoring:** Monitor key metrics and system health
-3. **Documentation:** Update user documentation and API references
-4. **Retrospective:** Conduct release retrospective to capture learnings
-5. **Next Release Planning:** Begin planning for next release cycle
-```
-**In Progress:**
-```markdown
-### In Progress
-⚠️ Release is still in progress. Recommended next steps:
-1. **Complete Remaining FUs:** Focus on completing {REMAINING_COUNT} remaining Feature Unit(s)
-2. **Integration Testing:** Run integration tests for completed batches
-3. **Checkpoint Reviews:** Complete pending checkpoint reviews
-4. **Issue Resolution:** Address any blockers or partial implementations
-```
-#### Release Metrics Template
-```markdown
-## 9. Release Metrics
-### Completion Metrics
-- **Batch Completion Rate:** {BATCH_COMPLETION}%
-- **Feature Unit Completion Rate:** {FU_COMPLETION}%
-- **Checkpoint Completion Rate:** {CHECKPOINT_COMPLETION}%
-- **Integration Test Pass Rate:** {TEST_PASS_RATE}%
-### Quality Metrics
-- **Partial Implementation Rate:** {PARTIAL_RATE}%
-- **Failure Rate:** {FAILURE_RATE}%
-```
-#### Related Documents Template
-```markdown
-## 10. Related Documents
-- **Release Plan:** `docs/releases/in_progress/{RELEASE_ID}/release_plan.md`
-- **Manifest:** `docs/releases/in_progress/{RELEASE_ID}/manifest.yaml`
-- **Status:** `docs/releases/in_progress/{RELEASE_ID}/status.md`
-- **Execution Schedule:** `docs/releases/in_progress/{RELEASE_ID}/execution_schedule.md`
-- **Integration Tests:** `docs/releases/in_progress/{RELEASE_ID}/integration_tests.md`
-```
-## 2. Data Sources
-Reports MUST be generated from the following sources:
-1. **Status File:** `docs/releases/in_progress/{RELEASE_ID}/status.md`
-   - Release metadata (ID, name, status)
-   - Batch completion status
-   - Feature Unit status
-   - Checkpoint status
-   - Integration test status
-   - Decision log
-2. **Manifest File:** `docs/releases/in_progress/{RELEASE_ID}/manifest.yaml`
-   - Feature Unit definitions
-   - Dependencies
-   - Execution strategy
-## 3. Calculation Rules
-### 3.1 Completion Percentages
-- **Batch Completion:** `(COMPLETED_BATCHES / TOTAL_BATCHES) * 100`
-- **FU Completion:** `(COMPLETED_FUS / TOTAL_FUS) * 100`
-- **Checkpoint Completion:** `(COMPLETED_CHECKPOINTS / TOTAL_CHECKPOINTS) * 100`
-- **Test Pass Rate:** `(PASSED_TESTS / TOTAL_TESTS) * 100`
-### 3.2 Status Detection
-- **Complete:** Status contains "Complete" (case-insensitive)
-- **Partial:** Status contains "Partial" (case-insensitive)
-- **Failed:** Status contains "Failed" or "Not Started" (case-insensitive)
-### 3.3 FU Categorization
-- **Infrastructure:** FU-000, FU-002, FU-050, FU-051, FU-052, FU-053, FU-054
-- **Core Services:** FU-100, FU-101, FU-102, FU-103, FU-105
-- **MCP Actions:** FU-200, FU-201, FU-202, FU-203, FU-204, FU-205, FU-206, FU-061
-## 4. Report Generation
-### 4.1 When to Generate
-Reports MUST be generated:
-- After all batches complete (automatic via orchestrator)
-- On-demand via manual script execution
-- Before release deployment
-### 4.2 Output Location
-Reports MUST be written to:
-```
-docs/releases/in_progress/{RELEASE_ID}/release_report.md
-```
-### 4.3 Report Metadata
-Each report MUST include:
-- Generation timestamp (ISO 8601)
-- Report version (currently 1.0)
-- Release ID
-- Report type (Build Report)
-## 5. Report Template
-The report structure is defined in:
-```
-docs/feature_units/standards/release_report_template.md
-```
-This template file contains placeholders (e.g., `{RELEASE_ID}`, `{BATCH_ROWS}`) that are replaced with actual data during report generation.
-## 6. Report Generation Process
-**Report generation is documentation-driven.** There is no script - agents or humans follow these instructions to generate reports.
-### 6.1 Generation Steps
-1. **Load Template:** Read `docs/feature_units/standards/release_report_template.md`
-2. **Load Data Sources:**
-   - Parse `docs/releases/in_progress/{RELEASE_ID}/status.md`
-   - Parse `docs/releases/in_progress/{RELEASE_ID}/manifest.yaml`
-3. **Calculate Metrics:** Apply calculation rules from Section 3
-4. **Generate Content Sections:**
-   - Extract batch data and format rows
-   - Extract feature unit data and format rows
-   - Extract checkpoint data and format items
-   - Extract integration test data and format table
-   - Generate achievement sections (infrastructure, core services, MCP actions)
-   - Generate issues sections (partial FUs, failed FUs, failed tests)
-   - Extract decision log and format table
-   - Generate next steps based on release status
-5. **Replace Placeholders:** Replace all `{PLACEHOLDER}` tokens in template with calculated/formatted values
-6. **Write Report:** Save to `docs/releases/in_progress/{RELEASE_ID}/release_report.md`
-### 6.2 Placeholder Reference
-| Placeholder               | Source                       | Format                                             |
-| ------------------------- | ---------------------------- | -------------------------------------------------- |
-| `{RELEASE_ID}`            | Command argument             | String (e.g., "v0.1.0")                            |
-| `{REPORT_DATE}`           | Current date                 | ISO date (YYYY-MM-DD)                              |
-| `{RELEASE_NAME}`          | status.md                    | String                                             |
-| `{RELEASE_STATUS}`        | status.md                    | String                                             |
-| `{STATUS_ICON}`           | Calculated from status       | ✅ or ⚠️                                           |
-| `{COMPLETED_BATCHES}`     | Calculated                   | Integer                                            |
-| `{TOTAL_BATCHES}`         | Calculated                   | Integer                                            |
-| `{BATCH_COMPLETION}`      | Calculated                   | Percentage (X.X%)                                  |
-| `{COMPLETED_FUS}`         | Calculated                   | Integer                                            |
-| `{TOTAL_FUS}`             | Calculated                   | Integer                                            |
-| `{FU_COMPLETION}`         | Calculated                   | Percentage (X.X%)                                  |
-| `{COMPLETED_CHECKPOINTS}` | Calculated                   | Integer                                            |
-| `{TOTAL_CHECKPOINTS}`     | Calculated                   | Integer                                            |
-| `{COMPLETED_TESTS}`       | Calculated                   | Integer                                            |
-| `{TOTAL_TESTS}`           | Calculated                   | Integer                                            |
-| `{CONDITIONAL_WARNINGS}`  | Conditional                  | Markdown (or empty)                                |
-| `{BATCH_ROWS}`            | Formatted from batches       | Markdown table rows                                |
-| `{PARTIAL_BATCHES}`       | Calculated                   | Integer                                            |
-| `{INCOMPLETE_BATCHES}`    | Calculated                   | Integer                                            |
-| `{COMPLETED_COUNT}`       | Calculated                   | Integer                                            |
-| `{COMPLETED_PERCENT}`     | Calculated                   | Percentage (X.X%)                                  |
-| `{PARTIAL_COUNT}`         | Calculated                   | Integer                                            |
-| `{PARTIAL_PERCENT}`       | Calculated                   | Percentage (X.X%)                                  |
-| `{FAILED_COUNT}`          | Calculated                   | Integer                                            |
-| `{FAILED_PERCENT}`        | Calculated                   | Percentage (X.X%)                                  |
-| `{TOTAL}`                 | Calculated                   | Integer                                            |
-| `{FU_ROWS}`               | Formatted from FUs           | Markdown table rows                                |
-| `{CHECKPOINT_ITEMS}`      | Formatted from checkpoints   | Markdown list items                                |
-| `{TEST_TABLE}`            | Formatted from tests         | Markdown table (or "No integration tests defined") |
-| `{COMPLETED_FUS_SECTION}` | Formatted from completed FUs | Markdown section (or empty)                        |
-| `{INFRASTRUCTURE_FUS}`    | Filtered and formatted       | Markdown list items                                |
-| `{CORE_SERVICES_FUS}`     | Filtered and formatted       | Markdown list items                                |
-| `{MCP_ACTIONS_FUS}`       | Filtered and formatted       | Markdown list items                                |
-| `{PARTIAL_FUS_SECTION}`   | Formatted from partial FUs   | Markdown section (or empty)                        |
-| `{FAILED_FUS_SECTION}`    | Formatted from failed FUs    | Markdown section (or empty)                        |
-| `{FAILED_TESTS_SECTION}`  | Formatted from failed tests  | Markdown section (or empty)                        |
-| `{DECISION_TABLE}`        | Formatted from decisions     | Markdown table (or "No decisions recorded")        |
-| `{NEXT_STEPS_SECTION}`    | Generated based on status    | Markdown section                                   |
-| `{CHECKPOINT_COMPLETION}` | Calculated                   | Percentage (X.X%)                                  |
-| `{TEST_PASS_RATE}`        | Calculated                   | Percentage (X.X%)                                  |
-| `{PARTIAL_RATE}`          | Calculated                   | Percentage (X.X%)                                  |
-| `{FAILURE_RATE}`          | Calculated                   | Percentage (X.X%)                                  |
-| `{GENERATION_TIMESTAMP}`  | Current time                 | ISO 8601 timestamp                                 |
-### 6.3 Formatting Rules
-**Batch Rows Format:**
-```markdown
-| {BATCH_ID} | {FU_LIST} | {STATUS} | {ICON} |
-```
-- Icon: ✅ if status contains "Complete", ⚠️ if "Partial", ❌ otherwise
-**FU Rows Format:**
-```markdown
-| {FU_ID} | {FU_NAME} | {ICON} {STATUS} | {NOTES} |
-```
-- Icon: ✅ if status contains "Complete", ⚠️ if "Partial", ❌ otherwise
-- Notes: Use "-" if empty
-**Checkpoint Items Format:**
-```markdown
-- {ICON} **{CHECKPOINT_NAME}**: `{STATUS}`
-```
-- Icon: ✅ if status is "completed", ⏳ if "pending", ❌ otherwise
-**Test Rows Format:**
-```markdown
-| {TEST_ID} | {TEST_NAME} | {ICON} {STATUS} |
-```
-- Icon: ✅ if status is "passed" or "completed", ❌ if "failed", ⏳ otherwise
-**FU List Items Format:**
-```markdown
-- ✅ **{FU_ID}**: {FU_NAME}{NOTES}
-```
-- Notes: Include in parentheses if present
-**Decision Rows Format:**
-```markdown
-| {DATE} | {DECISION} | {RATIONALE} |
-```
-### 6.4 Conditional Sections
-**Conditional Warnings:**
-- If `PARTIAL_FUS > 0`: Add warning about partial FUs
-- If `FAILED_FUS > 0`: Add critical alert about failed FUs
-**Next Steps Section:**
-- If status is "ready_for_deployment": Use "Ready for Deployment" template
-- If status is "completed": Use "Release Completed" template
-- Otherwise: Use "In Progress" template
-### 6.5 Agent Instructions
-When generating a release report:
-1. **Read this specification** to understand the structure and rules
-2. **Load the template** from `docs/feature_units/standards/release_report_template.md`
-3. **Parse data sources** (status.md, manifest.yaml)
-4. **Calculate all metrics** using the rules in Section 3
-5. **Format all sections** according to Section 6.3
-6. **Replace all placeholders** in the template
-7. **Write the report** to `docs/releases/in_progress/{RELEASE_ID}/release_report.md`
-8. **Verify completeness** - ensure all placeholders are replaced
-**When to Generate:**
-- After all batches complete (automatic via orchestrator)
-- On-demand when requested
-- Before release deployment
-## 6. Future Enhancements
-Potential future enhancements:
-- Custom report templates per release type
-- Additional metrics (time-to-completion, risk scores)
-- Comparison with previous releases
-- Export to multiple formats (JSON, HTML, PDF)

package/docs/feature_units/standards/release_report_template.md

@@ -1,76 +0,0 @@
-# Release {RELEASE_ID} — Build Report
-**Report Generated:** {REPORT_DATE}  
-**Release Name:** {RELEASE_NAME}  
-**Release Status:** {RELEASE_STATUS}
-## Executive Summary
-{STATUS_ICON} **Release Status:** {RELEASE_STATUS}
-- **Batches:** {COMPLETED_BATCHES}/{TOTAL_BATCHES} complete ({BATCH_COMPLETION}%)
-- **Feature Units:** {COMPLETED_FUS}/{TOTAL_FUS} complete ({FU_COMPLETION}%)
-- **Checkpoints:** {COMPLETED_CHECKPOINTS}/{TOTAL_CHECKPOINTS} completed
-- **Integration Tests:** {COMPLETED_TESTS}/{TOTAL_TESTS} passed
-{CONDITIONAL_WARNINGS}
-## 1. Batch Completion Summary
-| Batch ID | Feature Units | Status | Completion |
-| -------- | ------------- | ------ | ---------- |
-{BATCH_ROWS}
-**Summary:**
-- ✅ **Complete:** {COMPLETED_BATCHES} batch(es)
-- ⚠️ **Partial:** {PARTIAL_BATCHES} batch(es)
-- ❌ **Incomplete:** {INCOMPLETE_BATCHES} batch(es)
-## 2. Feature Unit Completion Summary
-### 2.1 By Status
-| Status                | Count             | Percentage           |
-| --------------------- | ----------------- | -------------------- |
-| ✅ Complete           | {COMPLETED_COUNT} | {COMPLETED_PERCENT}% |
-| ⚠️ Partial            | {PARTIAL_COUNT}   | {PARTIAL_PERCENT}%   |
-| ❌ Failed/Not Started | {FAILED_COUNT}    | {FAILED_PERCENT}%    |
-| **Total**             | **{TOTAL}**       | **100%**             |
-### 2.2 Feature Unit Details
-| FU ID | Name | Status | Notes |
-| ----- | ---- | ------ | ----- |
-{FU_ROWS}
-## 3. Checkpoint Status
-{CHECKPOINT_ITEMS}
-**Completion:** {COMPLETED_CHECKPOINTS}/{TOTAL_CHECKPOINTS} checkpoints completed
-## 4. Integration Test Results
-### 4.1 Test Execution Summary
-{TEST_TABLE}
-**Summary:** {COMPLETED_TESTS}/{TOTAL_TESTS} tests passed
-### 4.2 Test Case Details
-{TEST_CASE_DETAILS}
-## 5. Key Achievements
-{COMPLETED_FUS_SECTION}
-### Infrastructure Delivered
-{INFRASTRUCTURE_FUS}
-### Core Services Delivered
-{CORE_SERVICES_FUS}
-### MCP Actions Delivered
-{MCP_ACTIONS_FUS}
-## 6. Issues and Blockers
-{PARTIAL_FUS_SECTION}
-{FAILED_FUS_SECTION}
-{FAILED_TESTS_SECTION}
-## 7. Decision Log Summary
-{DECISION_TABLE}
-## 8. Next Steps
-{NEXT_STEPS_SECTION}
-## 9. Testing Guidance
-{TESTING_GUIDANCE_SECTION}
-## 10. Release Metrics
-### Completion Metrics
-- **Batch Completion Rate:** {BATCH_COMPLETION}%
-- **Feature Unit Completion Rate:** {FU_COMPLETION}%
-- **Checkpoint Completion Rate:** {CHECKPOINT_COMPLETION}%
-- **Integration Test Pass Rate:** {TEST_PASS_RATE}%
-### Quality Metrics
-- **Partial Implementation Rate:** {PARTIAL_RATE}%
-- **Failure Rate:** {FAILURE_RATE}%
-## 11. Related Documents
-- **Release Plan:** `docs/releases/in_progress/{RELEASE_ID}/release_plan.md`
-- **Manifest:** `docs/releases/in_progress/{RELEASE_ID}/manifest.yaml`
-- **Status:** `docs/releases/in_progress/{RELEASE_ID}/status.md`
-- **Execution Schedule:** `docs/releases/in_progress/{RELEASE_ID}/execution_schedule.md`
-- **Integration Tests:** `docs/releases/in_progress/{RELEASE_ID}/integration_tests.md`
-**Report Generated:** {GENERATION_TIMESTAMP}  
-**Report Version:** 1.0  
-**Report Specification:** `docs/feature_units/standards/release_report_spec.md`

package/docs/feature_units/standards/spec_compliance_validation.md

@@ -1,147 +0,0 @@
-# Spec Compliance Validation Process
-## Overview
-The spec compliance validation system:
-1. Extracts requirements from FU specification files (MUST/MUST NOT/SHALL statements)
-2. Logs implementation decisions made during build
-3. Automatically checks code/schema against requirements
-4. Generates compliance reports with gaps
-5. Blocks FU completion until all requirements are met or explicitly deferred
-## Process Flow
-```mermaid
-flowchart TD
-    A[FU Implementation Complete] --> B[Extract Requirements from Spec]
-    B --> C[Generate Implementation Decision Log]
-    C --> D[Run Automated Compliance Checks]
-    D --> E{Gaps Found?}
-    E -->|Yes| F[Generate Compliance Report]
-    F --> G[Present Gaps to User]
-    G --> H{User Action}
-    H -->|Fix| I[Implement Missing Requirements]
-    H -->|Defer| J[Document Deferral in Decision Log]
-    H -->|Update Spec| K[Update Spec First]
-    I --> D
-    J --> L{User Approval}
-    K --> D
-    L -->|Approved| M[Mark FU Complete]
-    E -->|No| M
-    M --> N[Continue Release Process]
-```
-## Implementation
-### Scripts
-- `scripts/validate_spec_compliance.js` - Main validation script
-- `scripts/spec_compliance_patterns.js` - Reusable check patterns
-### Usage
-```bash
-# Validate a single FU
-node scripts/validate_spec_compliance.js FU-100 v0.1.0
-# Integrated into release orchestrator (automatic)
-node scripts/release_orchestrator.js v0.1.0
-```
-## Requirement Extraction
-The system extracts requirements from spec files by:
-1. Parsing markdown for requirement statements:
-   - MUST / MUST NOT
-   - SHALL / SHALL NOT
-   - REQUIRED
-   - MUST IMPLEMENT
-2. Tracking section context:
-   - Maintains section hierarchy (nested headings)
-   - Associates each requirement with its section
-3. Categorizing requirements:
-   - `implementation` - Functions, classes, modules
-   - `database` - Tables, columns, indexes
-   - `validation` - Validation logic
-   - `testing` - Test requirements
-   - `integration` - Service calls, imports
-## Compliance Checks
-### Check Types
-1. **Code Existence Checks:**
-   - Function existence: `checkFunctionExists(functionName, filePattern)`
-   - Import existence: `checkImportExists(moduleName, filePattern)`
-   - Pattern matching: `checkPatternExists(pattern, filePattern)`
-2. **Database Schema Checks:**
-   - Column existence: `checkDatabaseColumn(columnName, tableName)`
-   - Table existence: `checkDatabaseTable(tableName)`
-3. **Integration Checks:**
-   - Service call verification: `checkServiceCall(serviceName, functionName, callerPattern)`
-4. **Validation Logic Checks:**
-   - Validation functions: `checkValidationLogic(validationType, location)`
-### Automatic Detection
-The system attempts to automatically determine what to check based on requirement text:
-- Keywords like "table", "column" → database checks
-- Keywords like "function", "implement" → function existence
-- Keywords like "import", "use" → import checks
-- Keywords like "validate", "check" → validation logic
-- Keywords like "call", "invoke" → service calls
-## Decision Logging
-For each FU, an implementation decision log is generated at:
-`docs/releases/vX.Y.Z/implementation_logs/FU-XXX_implementation_log.md`
-The log documents:
-- Requirement text and location
-- Implementation approach taken
-- Files changed
-- Code references
-- Verification method
-- Status (Implemented/Partial/Not Implemented)
-## Compliance Reports
-For each FU, a compliance report is generated at:
-`docs/releases/vX.Y.Z/compliance_reports/FU-XXX_compliance.md`
-The report includes:
-1. **Summary:** Total requirements, passed, failed, compliance rate
-2. **Requirements Status Table:** Each requirement with status, evidence, gaps
-3. **Implementation Gaps:** Detailed descriptions of missing requirements
-4. **Recommendations:** Actions needed to achieve compliance
-## Integration Points
-### Release Orchestrator
-The validation runs automatically in `scripts/release_orchestrator.js`:
-- After batch integration tests pass
-- Before marking FUs as complete
-- Blocks batch completion if any FU fails compliance
-### Final Review
-The validation is required before final review approval:
-- Executed automatically in `.cursor/commands/final_review.md`
-- Must pass before FU can be marked complete
-- Report must be reviewed by user
-## Critical Rules
-1. **NO FU can be marked "complete" without passing spec compliance validation**
-2. **All implementation decisions MUST be logged before validation**
-3. **All gaps MUST be resolved OR explicitly deferred with user approval**
-4. **Deferred requirements MUST be tracked in decision log for future work**
-## Handling Gaps
-When gaps are found, the user must choose one of three actions:
-1. **Fix gaps:** Implement missing requirements
-2. **Update spec:** If requirement is incorrect/outdated, update spec first
-3. **Defer requirement:** Document why requirement is deferred (requires explicit approval)
-Deferred requirements are tracked in the decision log and marked for future implementation.
-## Examples
-### Example: FU-100 Compliance Check
-**Requirement:** "Store unknown fields in `extraction_metadata.unknown_fields`"
-**Check:** `checkDatabaseColumn("extraction_metadata", "records")`
-**Result:** ❌ Fail - Column not found in schema
-**Gap:** `extraction_metadata` column missing from `records` table
-**Fix:** Add migration to create column, update `schema.sql`
-## Testing
-To test the validation system:
-```bash
-# Test with FU-100 (should catch known gaps)
-node scripts/validate_spec_compliance.js FU-100 v0.1.0
-# Test with compliant FU (should pass)
-node scripts/validate_spec_compliance.js FU-101 v0.1.0
-```
-## Agent Instructions
-### When to Load This Document
-Load when:
-- Understanding spec compliance validation process
-- Debugging compliance check failures
-- Implementing new compliance check patterns
-- Integrating validation into workflows
-### Constraints Agents Must Enforce
-1. All compliance checks must run before marking FU complete
-2. Gaps must be resolved or explicitly deferred
-3. Decision logs must be maintained for traceability
-4. Compliance reports must be generated for all FUs
-### Forbidden Patterns
-- Marking FU complete without compliance validation
-- Ignoring compliance gaps
-- Skipping decision logging
-- Proceeding with non-compliant implementations