change-impactlisted

# Change Impact ## Purpose Invalidate only affected downstream work, preserve unaffected valid work, and trigger a new Minimum Necessary Path. ## Trigger Run after any relevant upstream revision, disproven assumption, changed decision, Contract/schema/API change, dependency upgrade, or code modification to a stable Component. ## Inputs - Changed item and old/new revisions, reason, effective decision, and changed semantics. - Artifact dependency graph, traceability links, Component Graph, Contracts, and current State. - Existing validation/Gate evidence, target, Workflow Level, and current Minimum Necessary Path. ## Prerequisites - Identify the exact changed revision and avoid treating formatting-only edits as semantic changes without evidence. - Preserve prior evidence as history. ## Procedure 1. Compare old and new revisions and describe semantic, interface, behavior, data, constraint, or evidence changes. 2. Locate direct downstream consumers through dependencies, Contracts, traceability, and code/test references. 3. Traverse transitively only while the changed semantics can affect the consumer. 4. For each affected Artifact, record the reason and mark `STALE` unless evidence already proves invalidity. 5. For affected `STABLE` Components, mark `UNVERIFIED`; set `FAILED` only when current evidence demonstrates failure. 6. Invalidate revision-specific test, review, integration, and Gate evidence as needed. 7. Identify unaffected scope and record why its evidence rem