upgrade

Prepare a v0.1 DESIGN.md for the WebDesignHot v0.2 catalog profile.

Prepare an existing DESIGN.md for webdesignhot/0.2. The command is deliberately conservative: it changes only version metadata and never guesses icons, component states, naming, or design intent from prose.

Usage

design-md upgrade DESIGN.md --to webdesignhot/0.2
design-md upgrade site/src/content/designs --to webdesignhot/0.2 --format=json
design-md upgrade DESIGN.md --to webdesignhot/0.2 --write

The first two forms are dry-runs. Use --write explicitly to update files. For a directory, each v0.1 file is considered independently and the JSON report contains changed files, warnings, and fields that need manual work.

Deterministic changes

For a v0.1 document the upgrader can:

  • change spec: webdesignhot/0.1 to spec: webdesignhot/0.2;
  • add profile: catalog when it is absent;
  • preserve the existing frontmatter formatting and Markdown body.

It does not infer icons, naming, token prompts, component state matrices, or computed expressions. Add those fields only after checking the source design and then run strict lint:

design-md lint DESIGN.md --strict --spec 0.2