# Sync Notes

Template-owned downstream migration guidance lives in this directory.

## File Contract

- Operative note files must be named `YYYY-MM-DD-<slug>.md`
- `README.md` explains the contract and is ignored by `/git-sync`
- Notes are append-only. Add a new dated file for each downstream-affecting release train instead of rewriting an older note

## When A Note Is Mandatory

Add a new operative note whenever a train affects derived projects beyond a normal pull, install, and baseline verify. Common triggers:

- template dependency-baseline changes
- scaffold or sync-contract changes
- rename or migration work
- verifier or behavior changes that downstream maintainers need to understand
- any release train that will ask maintainers to do manual follow-up after pulling

## Required Sections

Every operative note must include these exact headings:

## Why this note exists

Explain what changed and why downstream maintainers are seeing this note.

## Applies to

State which projects, app modes, or versions need the follow-up.

## Required actions

List the manual work maintainers need to do after `/git-sync`.

## Verification

List the commands or flows that confirm the migration landed correctly.

## Not handled by /git-sync

Call out what remains manual so maintainers do not assume the pull/install/verify flow reconciled everything.
