MIGRATION · 0.1 AND CLI 0.2

Migrate to 1.0 RC

Move the packages your project already uses onto one coordinated version, apply the safe syntax migration, then refresh lifecycle evidence when a source contract changes.

This is a prerelease. Use the npm next tag and commit your lockfile so humans and AI agents resolve the same package train.

Upgrade packages together

Compiler and design assets

npm install @coordiation/css@next @coordiation/icons@next
npm install -D @coordiation/cli@next @coordiation/vite@next

Replace the example list with the Coordiation packages your project actually uses. Do not mix 0.x and RC packages because internal contracts use exact release-train versions.

Migrate negative utilities

Canonical syntax

<!-- Before -->
<div class="co--mt-4"></div>

<!-- After -->
<div class="-co-mt-4"></div>

Preview and apply

npx @coordiation/upgrade@next src/App.tsx --json
npx @coordiation/upgrade@next src/App.tsx --write

The codemod changes registered literal syntax only. Dynamic class construction is preserved because rewriting it would require application intent.

Initialize the lifecycle contract

Terminal

npx @coordiation/cli@next init   --name "Customer portal"   --owner-name "Product owner"   --owner-email "owner@example.com"

npx @coordiation/cli@next compatibility
npx @coordiation/cli@next status

Commit the generated .coordiation directory. It is the versioned contract shared by product contributors and AI agents, not a disposable cache.

Revise instead of silently editing

Terminal

npx @coordiation/cli@next revise SPEC-001   --reason "Authentication policy changed"   --patch spec-update.json

A revision archives the prior contract, clears approvals and evidence, and supersedes dependent artifacts. Re-derive the affected stages and record new development or QA evidence for the current revision.

Verify before deployment

Terminal

npx @coordiation/cli@next compatibility
npx @coordiation/cli@next trace
npx @coordiation/cli@next gate check GATE-QA --artifact QA-001

Run the application build, automated tests, accessibility checks, and relevant lifecycle gates. A successful migration plan proves that edits were applied; it does not replace product QA.

ROLLBACK

Pin the previous exact versions

If the candidate blocks a project, restore the versions recorded in its last known-good lockfile.

Compiler baseline: @coordiation/css@0.1.0.
CLI baseline: @coordiation/cli@0.2.0.
Do not change public npm dist-tags as a project-level rollback.
Report the package, Node version, reproduction, and active schema version.

Previous← 1.0.0-rc.1 notes NextUpgrade codemods →