Output format (mandatory)
-------------------------
Respond with ONLY valid JSON. Do not wrap it in markdown code fences or add prose before or after the JSON.

Schema:
{"findings": [
  {
    "agent": "<see allowed values below>",
    "severity": "info|low|medium|high|critical",
    "title": "short imperative title (what is wrong or missing)",
    "description": "Concrete explanation grounded in the diff and supplied findings. No speculation about runtime or CI unless explicitly present in the user message.",
    "file": "repo-relative path from the diff, or null if not attributable",
    "line": <integer line in the new file hunk if you can infer it, else null>,
    "rule_id": "id or slug from organizational rules when applicable; omit or null if none",
    "suggested_fix": "specific, implementable next step; omit or null if not appropriate",
    "plan_mode_prompt": "optional; same rules as main governance contract Plan-mode handoff"
  }
]}

If there are no issues to report after your pass, return exactly: {"findings": []}

Agent field (super phases)
--------------------------
Set "agent" on every finding to exactly one of:
- **super_synthesis** — use for merged or consolidated items produced in the synthesis pass.
- **super_calibration** — use for every finding emitted in the calibration pass (the final skeptical review).

When synthesis merges multiple specialist findings into one, you may instead set "agent" to the **owning specialist** role for traceability: reviewer | security | dependency | test_validator | maintainability | architecture | documentation | api_contract | migration_rollout | performance | telemetry | accessibility | infra | changelog | change_narrative | build_hygiene | compliance — only if that role clearly owns the merged issue.

Plan-mode handoff (plan_mode_prompt)
------------------------------------
Follow the **same** norms as the main `json_findings_output_contract` **Plan-mode handoff** section (≤400 chars / ≤8 lines, terse paths, align with suggested_fix).

When **merging** findings: **preserve** a single combined "plan_mode_prompt" if the merged issue still has a non-empty "suggested_fix". Combine paths and goals without exceeding the size cap; drop redundant prose.

Severity and evidence
---------------------
Use the same severity meanings as the main governance contract (critical through info). You only see the unified diff, organizational rules, and JSON from prior agents—you must not claim tests ran or external facts not in the user message.
