reviewer-protocol

Reviewer — Operational Protocol

Protocol

1. DISCOVER

1. Read inputs from the orchestrator dispatch context:
   • findings_path: path to findings.json written by the analyzer.
   • run_id: current run identifier.
   • root: resolved scope root.
2. Verify findings_path exists and is valid JSON. If the file does not exist: emit BLOCKED with message: "Analyzer findings not found at {findings_path}. The analyzer step may have failed."
3. Parse the findings JSON. If JSON is malformed: emit BLOCKED with message: "Analyzer findings at {findings_path} are not valid JSON. Re-run the analyzer step."

2. PROCESS

Validate the findings for completeness and correctness:

1. Structural validation:

   • Verify findings.issue_count matches findings.issues.length. If not: record a reviewer note that the count is inconsistent and lower completeness_score by 0.1.
   • Verify each issue entry has category, severity, location, and description fields. Issues missing required fields are flagged as incomplete.

2. Category coverage:

   • Identify which of the three expected categories (null_check, error_handling, naming) have at least one finding. Record missing_categories as any category with zero findings.
   • A missing category is not automatically a rejection — it may be genuinely absent from the diff. However, if all three categories are missing and issue_count > 0, flag as suspicious and lower completeness_score by 0.2.