v0.3.0

Added

• Iterative upgrade mechanism. When a user runs the setup skill on a workspace where a previous plugin version was installed, the setup now offers UPGRADE mode. It reads the installed version from AGENTS.md → "Tracker destinations" → "Workflow version", walks migration files between installed and current, and applies confirmed changes incrementally. Users no longer have to re-install from scratch on plugin updates.
• Migration manifest format. Each release that affects existing installations ships a vX.Y.Z.md file in plugins/agentic-engineering-workflow/migrations/. Files have structured from:/to:/date: frontmatter and list changes with Scope (local / team-wide / plugin-internal) + Automatable (yes / partial / no) fields so the setup can apply them mechanically with confirmation.
• §F APPLY UPGRADE MIGRATIONS phase in the spec — full procedure for identifying migrations to run, walking each with the user, applying changes per scope/automatability, and bumping the workflow version.
• migrations/README.md — maintainer guide to the format + when to write migrations.
• v0.3.0.md meta-migration — introduces the upgrade mechanism itself. Records the install version in AGENTS.md and seeds a local reference_workflow_upgrades.md memory.
• Top-level /setup-agentic-workflow slash command via a plugin commands file — invokable directly without the plugin namespace.

Changed

• Skill renamed: bootstrap → setup-agentic-workflow. Slash invocation is now /setup-agentic-workflow (or /agentic-engineering-workflow:setup-agentic-workflow via the namespaced form). All docs updated to use "setup" terminology — "bootstrap" was too generic an engineering term to be the skill's identifier.
• RELEASING.md now documents migration files: when to write them, format, examples.

Notes

• v0.2.x installs will see UPGRADE as an option next time they invoke the setup skill. Picking it walks through the v0.3.0 meta-migration (no behavior changes for users — just records the version + introduces the mechanism).
• v0.4.0 will be the first version to ship real iterative content via a migration file. The mechanism is now in place to keep installs current without re-bootstrap.