## 0.2.6 migration

Version `0.2.6` adds tracked `.myteam` versions and packaged built-in upgrade skills for older
projects.

### What changed

- New `.myteam/.myteam-version` metadata records which `myteam` release most recently initialized
  or refreshed the local agent tree.
- New packaged maintenance skills are available under the reserved `builtins/` namespace, including
  `builtins/migration` and `builtins/changelog`.
- The default root `load.py` can now alert the agent when the installed `myteam` version is newer
  than the tracked `.myteam` version.

### How to migrate an existing `.myteam` folder

1. Review these migration notes and the matching changelog entries for versions newer than your
   tracked `.myteam` version.
2. Remove any copied `.myteam/myteam/` maintenance subtree if your project still has one. The
   packaged `builtins/` skills now live inside the installed `myteam` package and should be loaded
   from there instead of from project files.
3. Update your project guidance so agents use the packaged `builtins/migration` and
   `builtins/changelog` skills for upgrade help.
4. To see the new default root loader, create a temporary empty directory, run `myteam init`
   there, and inspect the generated `.myteam/load.py`.
5. If your project uses the default root `.myteam/load.py`, update it so it can surface version
   upgrade notices when appropriate. If your project uses a customized root loader, adapt that
   custom logic instead of overwriting it blindly.
6. If any existing role or skill loaders were copied from earlier templates, update them so they
   use `get_active_myteam_root()` instead of `get_myteam_root()` when they need the active project
   tree.
7. Once the approved project-specific updates are complete, update `.myteam/.myteam-version` to the
   installed `myteam` release.
