# Reviewer Coverage Recovery Implementation Plan

## Goal

Give every reviewer and reviewer repair an exact dynamic changed-file contract, retry only mismatched reviewers once, and surface actionable coverage differences without weakening publication safety.

## Tasks

1. Derive and expose one sorted, deduplicated expected-file list from the PR snapshot.
2. Add exact coverage instructions to reviewer tasks and isolated reviewer repair contracts.
3. Replace generic coverage verification with structured missing, unexpected, and incomplete comparisons.
4. Add one targeted full-review replacement attempt per mismatched reviewer instance.
5. Add retry progress events, retained milestones, and reviewer-labelled final diagnostics.
6. Add regression tests for dynamic lists, repair context, selective retry, persistent mismatch, cancellation, and sibling reviewer preservation.
7. Run complete checks, package verification, and a controlled packageauth PR 262 replay.

## Acceptance Criteria

- No repository path is hard-coded.
- Exact receipts complete without retry.
- Only mismatched reviewer instances retry, at most once each.
- Persistent mismatch reports reviewer label and path differences and remains unpublished.
- Repair stays tool-free and snapshot-isolated while receiving the expected coverage array.
- PR 262 reaches validation or clean aggregation with all five coverage receipts accepted.