promote

Finalizing a plugin manifest for release involves converting `plugin.json.draft` into production `plugin.json`, bumping the patch version or applying an explicit version, and wiring up `skills/`, `commands/`, `hooks/`, and `mcpServers` based on target directory contents.

Archiving design documents after a release is handled by snapshotting the active design workspace from `studio/changes/{name}/` into a dated iteration archive directory. This process updates both active and archived `status.json` files to distinguish shipped milestones from continued design work.

Prerequisites for promoting a plugin version require the workspace to be in the `approved` phase in `studio/changes/{name}/status.json`. Guardrail pre-checks verify all in-scope skills hold `tested` status and the implementation exists under the target directory.

Design snapshot versioning during plugin promotion copies the active design workspace from `studio/changes/{name}/` into a date-and-iteration archive directory. It updates archived and active `status.json` files to reflect shipped versus ongoing work.

Plugin promotion fails when not approved because guardrail pre-checks require `studio/changes/{name}/status.json` to be in the `approved` phase. The workflow also verifies all in-scope skills have reached `tested` status before proceeding.