chore(deps): update dependency https://gitlab.com/gitlab-com/gl-infra/common-template-copier.git to v1.52.0

chore(deps): update dependency abiosoft/colima to v0.10.3

See merge request !726

chore(deps): update dependency https://gitlab.com/gitlab-com/gl-infra/common-template-copier.git to v1.52.0

See merge request !728

chore(deps): update dependency lima-vm/lima to v2.1.2

See merge request !727

chore(deps): update dependency gitlab-org/caproni to v2.48.1

See merge request !729

Capture what we learned about authoring and testing copier migrations
in this repo so the knowledge is reusable instead of tribal.

Add docs/migrations.md as the conceptual reference, covering:

- Anatomy of a `_migrations:` entry (`command`, `version`, `when`).
- Picking a `version:` pin so a migration fires once for projects last
  rendered at the previous tag (e.g. `1.46.0.post1` for v1.46.0), using
  PEP 440 post-release semantics.
- Choosing the `before` vs `after` stage, with a cheat sheet for common
  goals (seed an answer, patch the answers file, modify rendered files,
  delete obsolete files).
- A repeatable local testing recipe and common gotchas: migrations
  filtered out by the version range, `_skip_if_exists` masking template
  changes, `after`-stage answer writes only landing on the next update,
  prompts firing when the answer is seeded too late, git commands
  failing in non-git destinations, and idempotency requirements for
  versionless migrations.

Add two agent skills as the runnable counterparts to the doc:

- `write-copier-migration` for authoring a new `_migrations:` entry.
- `test-copier-migration` for provisioning a fixture at the previous
  tag and running `copier update` against in-flight template changes
  (works for both jj and git checkouts).

Symlink `.agents/skills` to `.claude/skills` so the skills are
discoverable under both conventions.

Extend the `copier.yml` `_exclude:` list with `docs`, `.claude`, and
`.agents` (and their `**` globs) so this documentation and tooling
ships only in the source repo and is never rendered into consuming
projects.

AI-assisted: Zed Agent (Claude Opus 4.8)

docs(migrations): add migration guide and skills

See merge request !718

chore(deps): update common-ci-tasks to v4.12

See merge request !730

Rename the rendered manifest from .runway/fairway.yml to
.runway/fairway.yaml so the file uses the conventional .yaml extension.

Mirror the relocation pattern: exclude the old path so copier does not
delete it before the after-stage migration moves it, then carry the
existing (possibly customized) file to the new name and rewrite the
fairway_manifest input in .gitlab-ci.yml (which is in _skip_if_exists,
so the template default never reaches existing projects).

The migration is pinned to 1.52.0.post1 so it fires once for projects
last rendered at v1.52.0 and chains after the .fairway/manifest.yaml
relocation for older projects.

update-fairway-manifest-path.py takes the old and new manifest path as
two required positional arguments so it backs both moves with an
explicit, self-documenting invocation at each call site.

AI-assisted: opencode (anthropic/claude-opus-4-8)

fix: rename release-platform manifest to .runway/fairway.yaml

See merge request !731