usage: tautline finalize-implementation-review [-h] [--project PROJECT]
                                               [--target TARGET] --manifest
                                               MANIFEST --verdict
                                               {blocked,clean,clean-with-deferrals}
                                               --unresolved-critical-count
                                               UNRESOLVED_CRITICAL_COUNT
                                               --unresolved-p1-count
                                               UNRESOLVED_P1_COUNT
                                               [--classified-findings-json CLASSIFIED_FINDINGS_JSON]
                                               [--base BASE]

options:
  -h, --help            show this help message and exit
  --project PROJECT
  --target TARGET
  --manifest MANIFEST
  --verdict {blocked,clean,clean-with-deferrals}
  --unresolved-critical-count UNRESOLVED_CRITICAL_COUNT
  --unresolved-p1-count UNRESOLVED_P1_COUNT
  --classified-findings-json CLASSIFIED_FINDINGS_JSON
                        Path to a JSON file holding the review's classified
                        findings. On a push-eligible verdict each blocker-
                        severity finding needs "ac_ref" (the acceptance
                        criterion it violates, or null when out of scope) and
                        "disposition" (fixed/routed/refuted), plus "routed_to"
                        when routed; a Critical/P1-origin finding with
                        "status": "deferred" also needs "deferral_rationale"
                        and "acceptance_criterion". NOTE: this verb takes a
                        PATH; the plan-review verbs take inline JSON. See
                        docs/reference/operations/cli-operations.md,
                        Classified-Findings Contract.
  --base BASE           Override the base ref used for outgoing diff review
                        evidence.
