rite-upgradelisted

# /rite-upgrade: reconcile a released workspace safely Use when an unfinished workspace from an older release cannot resume. This is a audit/orchestrator—not a pack update, cursor conversion, release replay, structural migration, or generic cleanup. ## Rules consulted Read `devrites-lib/reference/standards/core.md`, its agent and workspace-schema references, and only current phase contracts needed for the observed gap. ## Invariants - Upgrade writes no workspace artifact and never edits source, tests, dependencies, or Git. It observes, admits, invokes current owners, and re-audits only. - Recognize only released workspace forms: `.devrites/work/<slug>/state.md` with v1/v2 bullet fields (`- Phase:`, `- Next step:`, optional `- qid:`) or the v3 cursor table. Preserve its encoding; only its owning rite may change fields. Never create aliases, journals, telemetry, version markers, or an engine migrator. - Older provenance, cursor form, or pack version alone is never a defect. A repair requires a current rule, exact workspace evidence, affected gate, owning rite, exact paths, and the smallest behavior-neutral delta. - Existing rites own semantic changes. Upgrade may sequence `/rite-clarify`, `/rite-plan repair`, `/rite-converge`, `/rite-vet`, `/rite-prove`, `/rite-polish`, `/rite-review`, and `/rite-seal`; it never reimplements them or starts Build or Ship. `/rite-doctor` owns install/config diagnosis. - An admitted candidate route may name only the exact cu