refit

# Refit a Workflow You are refitting (upgrading) an existing workflow to match the current Spacedock version. This covers scaffolding files (README, mods) and, when schema changes require it, migrating entity frontmatter data. Agent files and the status viewer are shipped with the Spacedock plugin and do not need local updates. Follow these five phases in order. Do not skip or combine phases. --- ## Phase 1: Discovery ### Step 1 — Identify the workflow The user must provide a workflow directory path. If they didn't, ask: > Which workflow directory should I refit? Store the confirmed path as `{dir}`. Resolve it to an absolute path. Also derive `{project_root}` (git root or cwd) and `{dir_basename}` (last path component). ### Step 2 — Read current scaffolding and extract version stamps Read each scaffolding file and extract its version stamp: 1. **README** — Read `{dir}/README.md`. Extract version from YAML frontmatter `commissioned-by: spacedock@X.Y.Z`. Store as `{readme_version}`. 2. **Mod files** — Scan `{dir}/_mods/*.md` for installed mods. For each, read the `version` frontmatter field. Match against canonical mods at `{project_root}/mods/{name}.md` by filename. Store the local version and canonical version for each. Also scan `{project_root}/mods/*.md` for mods not yet installed. 3. **Legacy status script** — If `{dir}/status` exists, note it for cleanup (status now ships with the plugin). If a file doesn't exist, note it as missing and skip it. ### Step 3 — ...