auditor:triage

auditor-skill — Batch Triage Checkpoint

Arguments: $ARGUMENTS

Run one consolidated triage pass over the candidate finding set, so calibration is a single auditable checkpoint instead of being diffused across the leaf reviewers. Read OUTPUT-RULES.md first — Rule 1 (severity 1–10, the "Notes & Nitpicks" tier below severity 1), Rule 5b (the validation gate + [UNCONFIRMED]/[UNDETERMINED] outcomes) — and references/false-positives.md (the triage catalog + the "quantify the barrier" symmetric-rejection rule). Re-run this after any new review phase adds candidates.

Input

The current candidate set — every [FAIL-N] / [PARTIAL] / [UNCONFIRMED] the reviewers have emitted this run (from audit_<n>/ worksheets / session findings). Triage is idempotent: re-running folds in new candidates without re-litigating settled ones.

Steps

1. Dedup by root-cause signature. Collapse candidates that share a root-cause signature — the normalized code shape of the bug (e.g. a missing signer check, an unchecked *, a PDA derived without the stored bump), the same signature /auditor:re-audit uses for its sibling sweep. Two candidates with the same signature at the same root cause are one finding (record all locations); the same signature at different sites are siblings (keep separate, note the shared class).

   • If tools/auditor-tools is built (test -x tools/auditor-tools/target/release/audit-mem), run audit-mem check --program-id <id> --signature <sig> per candidate: an authoritative FALSE_POSITIVE ruling auto-suppresses the candidate to [N/A — prior ruling #<id>] (record the ruling id in the suppression appendix — never drop it silently). audit-mem regressions --program-id <id> flags any finding_id previously FIXED and now re-observed as REGRESSED (deterministic). If the tools are absent, dedup by signature manually and note the tooling gap. (See references/orchestration/pre-scan.md.)

2. Rule 5b calibration (the gate, applied in batch). Every candidate at N≥6 must carry a filled Reachability + Math/State-Bounds block (plus Attacker-Model for N≥7). A candidate that cannot complete the gate with cited evidence is downgraded — never left as a bare [FAIL-N]:

   • [UNCONFIRMED] — the gate failed on reachability or bounds (unreachable / unbounded as written); reported for manual follow-up, not counted as a confirmed FAIL.
   • [UNDETERMINED] — the path is reachable but its full impact could not be quantified in scope; carried at its likely severity band with "extent not determined within this assessment". Reachable-but-unquantified ≠ unreachable.
   • Cross-check each candidate against references/false-positives.md (FP-1…FP-6 + the fast pass): a candidate matching an entry needs the specific escape cited to file:line, or it is downgraded.
   • Quantify every downgrade. A rejection on "not profitable" / "not exploitable" must show the worked bound — concrete numbers (capital vs. max extractable, cost > gain by how much) or the named blocking precondition @ file:line. A bare "not profitable" / "attacker gains nothing" is not a valid rejection (symmetric to an unquantified High): the finding stays open ([PARTIAL]/[UNCONFIRMED]) until the barrier is computed. Delegate re-derivation of contested N≥8 candidates to peer-reviewer if a judgment call needs an independent read.