# Test Strategy: Clean Repository Enterprise Profile

## Overview
This directory contains strategy, coverage matrices, and execution reports for testing the `clean-release` subsystem, ensuring 100% compliance with GRACE-Poly semantic standards and enterprise deployment isolation policies.

## Mandate
- **CRITICAL Modules**: Strictly enforce `@TEST_CONTRACT` coherence, verifying that all defined `@TEST_FIXTURE`, `@TEST_EDGE`, and `@TEST_INVARIANT` definitions map directly to semantic tests.
- **STANDARD Modules**: Validate expected inputs, outputs, and edge cases (e.g., manifest hashes, source isolation algorithms).
- **No Degradation**: Tests must never be deleted; regression implies an invariant violation.

## Scope
1. `policy_engine.py` (CRITICAL): Deterministic policy evaluations for artifacts and resource registries.
2. `compliance_orchestrator.py` (CRITICAL): State-machine enforcing mandatory execution of `DATA_PURITY`, `MANIFEST_CONSISTENCY`, `INTERNAL_SOURCES_ONLY`, and `NO_EXTERNAL_ENDPOINTS`.
3. `report_builder.py` (CRITICAL): Integrity validation for compliance counters and operator summaries.
4. Additional subsystems: `manifest_builder.py`, `source_isolation.py`, and `api/routes/clean_release.py`.

## Execution
Run testing via Pytest targeting backend test modules:
```bash
cd backend && .venv/bin/python3 -m pytest tests/services/clean_release tests/api/routes/test_clean_release_api.py tests/api/routes/test_clean_release_source_policy.py -v
```