reporter-protocol

Reporter — Operational Protocol

Protocol

1. DISCOVER

1. Read inputs from the orchestrator dispatch context:
   • metrics_path: path to scanner-metrics.json written by the scanner.
   • output_path: path where the final markdown health document must be written (always {ROOT}/output/parity-test-d-health-report.md).
   • state_path: path to pipeline-state.json for status updates.
   • run_id: current run identifier.
   • root: resolved scope root.
2. Verify metrics_path exists and is valid JSON. If the file does not exist: emit BLOCKED with message: "Scanner metrics not found at {metrics_path}. The scanner step may have failed."
3. Parse the metrics JSON. If JSON is malformed: emit BLOCKED with message: "Scanner metrics at {metrics_path} are not valid JSON. Re-run the scanner step."

2. PROCESS

Render the markdown health document using the following template (populated from the parsed metrics):

# Code Health Report — parity-test-d

> Generated by the parity-test-d pipeline (Tier 1c — Antigravity CLI)

## Source

**Directory scanned:** `{metrics.scanned_directory}`
**Files scanned:** {metrics.file_count}

## High-Complexity Files

{If metrics.high_complexity is non-empty, for each entry render:}
- **`{entry.file}`** — complexity score {entry.complexity_score}: {entry.reason}

{If metrics.high_complexity is empty, render:}
- No high-complexity files detected.

## Missing Docstrings

{If metrics.missing_docstrings is non-empty, for each entry render:}
- **`{entry.file}`** — missing docstrings at: {entry.locations joined by ", "}

{If metrics.missing_docstrings is empty, render:}
- No missing docstrings detected.

## Long Functions

{If metrics.long_functions is non-empty, for each entry render:}
- **`{entry.file}`** — `{entry.function}`: {entry.line_count} lines

{If metrics.long_functions is empty, render:}
- No long functions detected.