rite-upgradelisted

# /rite-upgrade: bring an active workspace onto the current contract Use this when a workspace created under older DevRites rules cannot safely continue with the installed pack. It reconciles the workspace to the current desired state; it does not replay a chain of release-specific scripts. Structural `devrites-engine migrate` remains a separate first step. Current semantic contract: `devrites.readiness-artifacts.v2`. ## Rules consulted Read `devrites-lib/reference/standards/core.md`, `devrites-lib/reference/standards/agents.md`, `devrites-lib/reference/workspace-artifact-schema.md`, and the current Clarify, Define, Plan, Vet, Converge, and Build phase contracts needed by the assessment. ## Invariants - Never edit application source, tests, dependencies, Git state, or historical evidence. - Preserve completed-slice identity, status, acceptance, dependencies, historical proof, answered questions, and `touched-files.md`. - Reassess only unfinished planning. Archived or `done` workspaces are a no-op. - Never downgrade a workspace that names a future semantic contract. - This is a recovery command, not a lifecycle phase; never write `Phase: upgrade`. - Durable plans contain portable repository commands, not RTK/local aliases, user-specific absolute paths, or temporary proof trees. Runtime packets may name an execution adapter; evidence may record both logical and executed forms. - Ask at most one coherent question, and only for product, policy, irreversible risk, or