v3.3.0

• Preview-first finding recovery (RCL-52): rcl evidence recover-finding
  validates explicit run, report digest, finding ref and retained native identity
  bindings. Preview is the default; --submit sends one authenticated correction.
  No reviewers, new verdicts, accounting changes or unrelated outbox delivery.
  Requires the Harness backend support from IO-12695 before live submission;
  an acknowledgment is not convergence. Original report bytes are not retrieved
  or reconstructed, and historical reports remain unchanged.

• Async patch convergence (RCL-50): collect delayed async results across
  distinct immutable patch captures using the validated convergence target.
  Preserve repository/worktree scope and other review modes' keys; do not
  migrate previously spooled path-keyed results. Reviewer health, historical
  finding handling and detached-worker lifetime are unchanged.

• Distinct report finding identities (RCL-51): consensus findings that
  share a line-bucket anchor receive separate report keys, including findings
  below the report threshold. All new report keys use report:<run-id>:<key>
  to separate them from native ledger keys and earlier runs' aliases, including
  while the current classification is awaiting delivery. Native location
  matching and existing ledger identities are unchanged. Legacy reports with
  conflicting classifications for one report key fail before the round state
  is written, rather than silently discarding a mapping, including missing-key
  fallback and telemetry-off
  use. Preserve those reports for separately supported finding-ref recovery;
  this change does not relabel already-published evidence.

npm: https://www.npmjs.com/package/review-council/v/3.3.0
Tarball SHA-256: 9ce6cd82a1426f75043ffb7e5632f49c67b37548ffd6289d14d8997b64e1a03a