v0.3.1

Fixed

• Install-state misdetection on legacy installs. A v0.1.x install (complete by its era's standards, using the older ## Tracker — Linear section heading) was being detected as PARTIAL when the v0.2.0+ setup ran on it, suggesting incomplete remediation. Now classified as LEGACY (a separate state) and routed automatically to UPGRADE mode, which walks through the new v0.2.0 migration to rename the section + add new fields. Spec §A detection logic now distinguishes "legacy-format complete install" from "half-finished current-format install."
• Linear MCP delete limitation called out. Some MCP builds expose delete_attachment / delete_comment / delete_status_update but NOT delete_project / delete_document. The spec previously implied a setup could "retire" auto-created projects via deletion — now reframed as archive / cancel / tombstone, with a manual-UI-cleanup fallback when full deletion is needed. General MCP capability caveats added for Jira / Notion / GitHub Issues too.
• triageEnabled field assumption. Spec previously instructed the agent to check triageEnabled on get_team to detect Linear's built-in Triage inbox. Some MCP builds don't surface this field. Added a fallback order: try the field, then a URL probe, then ask the user, then default to "Triage exists" (Linear's default for new teams) with the assumption surfaced in the §E report.

Added

• migrations/v0.2.0.md — retroactive migration documenting the v0.1.x → v0.2.0 transition (section rename + new fields). Required infrastructure so legacy installs upgrade cleanly through the migration mechanism rather than being misdetected.