report-formatlisted

# Review Report Format Unified format for all review findings. Schema: `schemas/review-report.schema.json` (v4.0.0). **Hard cutover**: versions 1.x and 2.x are no longer accepted. `3.x` is accepted read-only for in-flight reports — legacy floats migrate to the v4.0.0 field names on load, defaulting `relevance` and requiring a re-rate (see `severity` skill). New reports MUST declare `4.0.0`. ## Finding Structure Agents emit a JSON array of `finding_section` objects: ```json [ { "title": "Section Title", "category": "security|project|code_quality|call_tree|dependencies|documentation|pr_comments|pr_promises", "findings": [ { "id": "PREFIX-001", "likelihood": 0.6, "impact": 0.7, "relevance": 0.5, "title": "Short finding title", "tags": ["A03 Injection", "CWE-79"], "location": "src/auth.rs:42-56", "description": "What the issue is and why it matters", "impact_description": "What could go wrong (Markdown narrative)", "recommendation": "How to fix it", "code_snippets": [ {"language": "rust", "caption": "auth.rs:42", "content": "let user = unwrap_token(&hdr);"} ] } ], "positives": "Optional positive observations" } ] ``` This is the producer-emitted shape: integer `severity` and float `overall_severity` are absent — the coordinator's derive pass adds them from `likelihood`/`impact` (see below). The example validates against the v4 schema a