# Minion Template Version

Current version: 1.4.0-1.0.0

Version format for downstream repos: `<base-template-version>-<downstream-version>`

Example downstream version: `1.4.0-1.0.0`

## Downstream Onboarding Method

- Keep the initial export-ready template snapshot in `.minions-template/`.
- Use [docs/downstream-onboarding-playbook.md](docs/downstream-onboarding-playbook.md) and [docs/export-manifest.md](docs/export-manifest.md) to perform the first controlled export into the live downstream repo.
- Treat `INIT.md`, `MEMORY.md`, `docs/operator-onboarding-checklist.md`, and `minion-version.md` as onboarding merge files, not blind copies.
- Exclude `.git/` and `do-not-export` files such as `.mm.md` from the vendored snapshot.
- After the first export, bootstrap mailbox coordination with `docs/project/mailbox-collaboration-model.md`, `minions/mail/README.md`, and `minions/mail/packet-template.md` before opening new actionable packets.
- Commit the vendored snapshot and exported live files together so later upgrades have a stable comparison base.

## Downstream Upgrade Method

- Keep the currently approved export-ready template snapshot in `.minions-template/`.
- During upgrade, stage the incoming export-ready template in a temporary path such as `.minions-template.next/`.
- `PM` owns the downstream merge/migration unless the Operator assigns another owner.
- Use [docs/downstream-upgrade-playbook.md](docs/downstream-upgrade-playbook.md) and [docs/export-manifest.md](docs/export-manifest.md) to compare:
  - old vendored template
  - new vendored template
  - live downstream files
- Only update the base-template portion of `minion-version.md` after the live files and vendored snapshot both reflect the approved upgrade.