spec-editor migrate
Idempotently migrate a project to the current methodology and tooling conventions.
Steps: add the methodology types that the template gained since the project’s
methodology.yaml was last touched, rename legacy environment and deployment ids
to host ids, make sure journal/ is gitignored, backfill version snapshots on
relationships that predate them, seed questions.counter from questions.jsonl
if it does not cover it already, and give every stored plan task and queued-task
event the fields the current version expects.
Preview: spec-editor migrate -p . --dry-run
Apply: spec-editor migrate -p . --yesUsage
spec-editor migrate [OPTIONS] [settings|project-identity]Arguments
| Argument | Required |
|---|---|
TARGET |
no |
Options
| Option | Type | Default | Description |
|---|---|---|---|
--path, -p |
path | . |
Path to project (or SPEC_EDITOR_PROJECT) |
--dry-run |
flag | Show what would change without writing anything | |
--yes |
flag | Do not prompt for confirmation before writing | |
--relayout-elements |
flag | Also move nested element files onto aspects/<aspect>/<id>.md (skipped by default) | |
--json |
flag | Output as JSON |