gatelineAPI reference
interface ReviewReport {
    dispositions: ReviewDisposition[];
    findings: ReviewFinding[];
    path: string;
    rounds: ReviewRound[];
    task: null | string;
    verdict: null | "approve" | "escalate" | "request-changes";
}

Properties

dispositions: ReviewDisposition[]

Every - **F<n> — resolved|stands ...** line in this report, in document order, whether or not it names a finding this file raised.

finding.resolution can only carry the ones that attach within the file, which is the whole story when rounds append to one report as roles/reviewer.md directs. Where a run instead keeps a file per round, round 3's "F2 — resolved" names a finding round 2's file raised, and dropping it would make a decided part of the record unreachable — the one thing no view here is allowed to do (#261).

findings: ReviewFinding[]

Findings in document order. Callers sort; the record's order is kept here.

path: string

Run-relative artifact path.

rounds: ReviewRound[]
task: null | string

Task id from the first # Review Report: <id> header, or null.

verdict: null | "approve" | "escalate" | "request-changes"

The verdict in force: the last round's.