framework-resumelisted

# Framework Resume ## Purpose Continue from persisted evidence without blindly trusting an old Checkpoint or hidden conversation history. ## Trigger Run at session recovery, after `PAUSED_AT_STAGE`, after a handoff/context reset, or whenever repository activity may have occurred since the last Checkpoint. ## Inputs - `config/project.md`, user request, latest Checkpoint, State, Artifact Registry, and dependency/traceability records. - Current repository revision, branch/worktree, working-tree status, files, and available validation evidence. - Open clarifications, decisions, assumptions, risks, and prior Minimum Necessary Path. ## Prerequisites - Locate the latest relevant Checkpoint by ID/time/repository lineage, not filename guess alone. - Do not mutate project work until reconciliation identifies a safe next action. ## Procedure 1. Read Project Configuration, latest Checkpoint, linked Artifacts, State, and target. 2. Inspect current repository revision, branch/worktree, dirty state, and relevant file changes. 3. Compare repository/Artifact/Component revisions with the Checkpoint. 4. Detect added, removed, modified, or externally changed assets since the snapshot. 5. Reopen unresolved Clarifications, assumptions, decisions, risks, failures, and blockers. 6. Run Change Impact for every material drift and mark affected Artifacts `STALE`/`UNVERIFIED` and Components `UNVERIFIED` as appropriate. 7. Revalidate affected Artifacts and current Gate evidence; preserve unaffe