# Audit - <ProjectName>

## Project
- Path: <ProjectPath>
- Module: <Module>
- Kind: <Kind>
- Audit date (UTC): <YYYY-MM-DD>
- Files scanned: <count>
- Files with issues: <count>
- File-level report: docs/implplan/audits/csproj-standards/file-audit.csv

## Coding Standards Findings
- Status: <PASS|FAIL>
- Nullable: <enable|disable|missing>
- TreatWarningsAsErrors: <inherited true|overridden false|explicit true>
- Deterministic: <inherited true|overridden false|explicit true>
- 100-line rule violations: <count>
- Namespace violations: <count>
- Using directive violations: <count>
- Naming violations (interfaces/fields/const/async): <count>
- Service locator usage (BuildServiceProvider/GetService): <count>
- Assembly.LoadFrom usage: <count>

### Details
- 100-line files:
  - <path> (<lines>)
- Namespace issues:
  - <path>: <issue>
- Using directive issues:
  - <path>: <issue>
- Naming issues:
  - <path>: <issue>
- Async issues:
  - <path>: <issue>
- Service locator matches:
  - <path>:<line> <snippet>
- Assembly.LoadFrom matches:
  - <path>:<line> <snippet>

### Fix Guidance
- Align interface/field/const naming to standards.
- Move and sort using directives (outside namespace).
- Split files over 100 lines into smaller types or partials.
- Replace service locator usage with constructor injection.
- Add analyzer packages or centralized analyzer references if missing.

## File-Level Findings
- Status: <PASS|FAIL>
- Files scanned: <count>
- Files with issues: <count>
- See docs/implplan/audits/csproj-standards/file-audit.csv for full per-file status.

| File | Issues | Fix guidance |
| --- | --- | --- |
| <path> | <issue; issue> | <guidance; guidance> |

## Testing Fullness Findings
- Status: <PASS|FAIL>
- Expected layers (heuristic): <Unit, Integration, E2E, Security, Offline, Performance, CLI>
- Detected test projects: <list>
- Missing layers: <list>

### Manual checks required
- Observability contract tests for WebService/Worker.
- Intent tagging for regulatory modules (Policy, Authority, Signer, Attestor, EvidenceLocker).
- Offline execution (tests must run without network access).
- Coverage matrix alignment (docs/technical/testing/TEST_COVERAGE_MATRIX.md).

### Fix Guidance
- Add test projects or extend existing suites to cover missing layers.
- Ensure tests use deterministic fixtures and offline harnesses.