fraim-framework 2.0.35 → 2.0.37

package/registry/workflows/bootstrap/evaluate-code-quality.md

@@ -1,36 +0,0 @@
-# FRAIM Workflow: evaluate-code-quality
-
-## Intent
-To perform a deep analysis of the codebase's quality, evaluating it against FRAIM's standards and generating a comprehensive health report.
-
-## Execution Steps
-
-1. **Environment Check**
-   - Ensure `npm install` and `npm run build` have been attempted.
-   - Verify that `.fraim` directory (or equivalent config) is present.
-
-2. **Run Quality Analysis**
-    - Execute the self-contained quality analysis script:
-    ```bash
-    # Execute evaluate-code-quality script directly from synced location
-    npx tsx ~/.fraim/scripts/evaluate-code-quality.ts
-    
-    # On Windows:
-    # npx tsx %USERPROFILE%\.fraim\scripts\evaluate-code-quality.ts
-    ```
-
-3. **Author Report**
-    - Read the terminal output from Step 2.
-    - Locate the template: `get_fraim_file({ path: "templates/bootstrap/CODE-QUALITY-REPORT-TEMPLATE.md" })`
-    - Create a new file at `docs/bootstrap/code-quality-report.md`.
-    - Use your intelligence to synthesize the findings into the template:
-        - Assign a fair grade (A-F) based on build success and diagnostic results.
-        - Detail specific quality risks found in Gate 1-11.
-        - Propose actionable remediation steps.
-
-4. **Review Findings**
-   - Summarize the top 3 quality risks to the user.
-   - Propose a remediation plan if the grade is below 'B'.
-
-5. **Update Status**
-   - Label any relevant issues with `quality:evaluated`.

package/registry/workflows/bootstrap/verify-test-coverage.md

@@ -1,37 +0,0 @@
-# FRAIM Workflow: verify-test-coverage
-
-## Intent
-To verify the depth and effectiveness of the test suite by comparing actual test execution against the validation plans defined in specifications.
-
-## Execution Steps
-
-1. **Run Tests with Coverage**
-   - Execute the project's test suite with coverage enabled (e.g., `npm test -- --coverage`).
-   - Ensure coverage reports (LCOV or JSON) are generated.
-
-2. **Map Validation Plans**
-   - Identify all RFCs and Spec documents in `docs/`.
-   - Extract "Validation Plan" tables from these documents.
-
-3. **Analyze Coverage Gaps**
-    - Execute the self-contained test coverage verification script:
-    ```bash
-    # Execute verify-test-coverage script directly from synced location
-    npx tsx ~/.fraim/scripts/verify-test-coverage.ts
-    
-    # On Windows:
-    # npx tsx %USERPROFILE%\.fraim\scripts\verify-test-coverage.ts
-    ```
-
-4. **Author Report**
-    - Read the terminal output from Step 3.
-    - Locate the template: `get_fraim_file({ path: "templates/bootstrap/TEST-COVERAGE-REPORT-TEMPLATE.md" })`
-    - Create a new file at `docs/bootstrap/test-coverage-report.md`.
-    - Use your intelligence to synthesize the findings into the template:
-        - Highlight mission-critical scenarios that lack automated test evidence.
-        - Discuss line coverage trends.
-        - Recommend specific test cases to bridge coverage gaps.
-
-5. **Review Findings**
-   - Alert the user if critical validation scenarios are uncovered.
-   - Suggest specific tests to improve coverage score.