Reachability-Scoped Delta

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

A teaching framework upgrade v1→v2 changes alpha parameters and removes beta. The project statically uses alpha, while plugin configuration may load beta dynamically. Global migration notes are not confirmed local defects.

Mechanism

Freeze current/target versions and migration materials. Inventory imports, callers, configuration, generated code and dynamic entry points, intersecting them with version changes. Trace reachable differences to local behavior and checks. Treat unused changes as scoped inapplicability candidates and unknown dynamic use as coverage gaps. Run affected contract examples and separate risk from confirmed failure.

Bad example

List every v2 breaking change as a project defect, or declare beta irrelevant because no import appears.

Good example

Inspect actual alpha arguments against the v2 contract and beta loading in plugin configuration. Record version change, local path and check result for each. Unobserved dynamic entry points remain pending, not reproduced defects. Scope explanations accompany inapplicable items.

Why the change matters

Reachability connects migration documentation to project behavior, focusing advice on used changes. Visible dynamic gaps prevent static scanning from claiming complete coverage.

Observable expectation

Teaching results include the local alpha check. Enabled beta configuration requires checking; unknown configuration remains pending. Missing imports alone do not close it. Removing alpha use requires reassessing applicability rather than retaining an outdated defect.

Limits

No frozen source is confirmed; versions and APIs are illustrative. Reflection, plugins, generation and runtime configuration exceed static reachability. Real upgrades require verified target contracts and environments rather than compatibility inferred from version numbers.