Development trajectory reviewed — chips open the recorded evidence behind a statement.

1 · Goal — why this change

This PR

Epic Intent corroborated by the recorded session goals

2 · Implementation strategy

Approach.

3 · The change, explained — components and how they interact

Click any component for why it was touched and its before → after behavior.

New in this PR Modified by this PR

Only changed areas are shown. Omitted for clarity:

Changed areas at a glance (file-level breakdown)
AreaFilesNature

4 · Affected flows and impact radius

Detail: computed evidence and per-flow breakdown

Computed signal (call graph + exact search — not reviewer judgment)

FlowHow it is touchedBlast-radius risk

5 · Risks and de-risk factors

Assessed summary — computed signals kept separate below; findings carry the detail

Raises risk

Lowers risk

Computed signals (from the repository, not reviewer judgment)

6 · Focused review — start here

The 1–2 code locations most worth human eyes, ranked. Expand for the change, the recorded why, and how it's used.

▲ HIGH

Why this priority:

Why it was written this way:

7 · Findings — surfaced

confidence:
Claim
Evidence
Cost
Check
Fix

8 · Post-merge checklist

Answer each by looking at the named code/artifact, not at this document.