Roadmap: Code Review Skill — Golden 10

## Type

Documentation

## Area

Research

## Priority

P1 — High

## Problem

The repository has many possible roadmap directions. This issue fixes a small,
ordered backlog of the ten highest-value initiatives so work stays focused and
each initiative has one parent issue to track.

## Goal

One compact, current view of the Golden 10 initiatives — their parent issues,
status, priority, and the few dependencies that actually constrain order.

## Scope

| # | Initiative | Parent | Priority | Status |
| --- | --- | --- | --- | --- |
| 1 | Measurable review-quality benchmark | #40 | P1 | Closed |
| 2 | False-positive / false-negative metrics | #41 | P1 | Closed |
| 3 | Stable finding identity | #42 | P1 | Closed |
| 4 | Finding lifecycle + stateful re-review | #43 | P1 | Closed |
| 5 | Versioned machine-readable output contract | #44 | P1 | Open |
| 6 | Normalized Review Context input model | #45 | P2 | Open |
| 7 | Policy / packaging integrity validation | #46 | P1 | Open |
| 8 | Opt-in specialist review profiles | #47 | P2 | Closed |
| 9 | Risk-based + large-PR review | #48 | P2 | Closed |
| 10 | GitHub-native enforcement (research/design) | #49 | P2 | Open |

Dependency order (only the constraining edges):

- #40 → #41 (both delivered)
- #42 → #43 (both delivered)
- #45 supports #43 (delivered)
- #40 + #41 → #47 (delivered)
- #40 + #41 → #48 (delivered)
- #46 is an independent foundation

#44 and #49 are both open and independent of each other: #44's machine-readable
output contract does not gate #49's GitHub-native enforcement research, since
#49's remaining scope (#91, #93, #95) operates on the existing verdict→status
mapping directly, not on a hypothetical output document. A previously stated
"#44 → #49" edge here, and a "Supported by #45" edge on #44 itself, were not
load-bearing and have been removed from both issues.

6 of 10 Golden parents are closed. The remaining open work is #44 (output
contract), #45 (context input model), #46 (integrity validation), and #49
(GitHub-native enforcement research) — see each parent for its current
residual scope.

## Non-Goals

- No initiatives beyond these ten (no nice-to-have, speculative, or runtime-integration work).
- No status labels, sprints, story points, or milestones — GitHub open/closed is the status.
- Not a design document for any initiative; detail lives in each parent and its children.

## Acceptance Criteria

- [x] All ten Golden parents exist and are linked from this issue.
- [x] Each parent links its own children; each child names its parent.
- [x] The dependency edges above match the parents' Dependencies fields.
- [x] This table reflects current open/closed status.

## Dependencies

Depends on: none
Blocks: none
Parent: none

Children (Golden parents): #40 #41 #42 #43 #44 #45 #46 #47 #48 #49

## Validation

- Manual GitHub check: roadmap → parent → child links resolve.
- Each parent and child carries type / area / priority labels.
- Dependency references point to real issue numbers.

Start in issue #39 by checking the Golden 10 table against parent issues #40–#49 and their child links. Verify the dependency statements, statuses, labels, and issue-number references using the manual GitHub checks listed under Validation; done means the roadmap is compact, current, and all links and dependencies resolve.

Written by the indexing model from the issue text.