# Migration evidence

Know what PatchFlow knew before the agent changed your repository.

| Level | Source | Interpretation |
| --- | --- | --- |
| playbook | Structured Before → After patterns | Strongest input |
| release_notes | Exact upstream GitHub release | Source-backed |
| inferred | Repository call sites and generic version context | Review closely |

## Evidence is not confidence theatre

PatchFlow records the actual input class instead of presenting every migration as equally informed. The value is operational: teams can require more review for inferred migrations or restrict major updates until a playbook exists.

## What enters the prompt

- Package and from/to versions
- Semantic update type
- Evidence level and source when available
- Release-note excerpt
- Structured Before → After patterns
- Repository test command and strict edit constraints

## Current limit

> Generic npm support does not synthesize structured API diffs. If matching release notes cannot be found, the run is explicitly marked inferred.