Migration Guide

There is no released-version migration to document yet. Before the first tagged release, development-branch changes may evolve without a versioned migration guarantee.

Future migration entries should be organized by from → to and state:

1. who is affected;
2. the old and new CLI/API/bundle behavior;
3. an automated or copyable migration procedure;
4. validation that proves the migrated workload still works; and
5. the deprecation/removal timeline, when applicable.

Historical design plans and worklogs are not migration instructions unless a released contract links them explicitly.