# Git Sync And Sync Notes Workflow

## Why this note exists

The template now ships a dedicated `/git-sync` command and a `.claude/sync-notes/` contract for downstream release guidance. This separates plain git transport from manual template reconciliation work.

## Applies to

All template-derived projects that pull this train and previously relied on `/sync` for pull-plus-reinstall behavior.

## Required actions

- Use `/git-sync` for future release-train pulls so new sync notes are surfaced automatically
- Keep using `/sync` only for local cache resets or fresh reinstalls when git transport is not part of the task
- Read any newly introduced note file after `/git-sync` and apply the listed manual follow-up before considering the update complete

## Verification

- Run `/git-sync`
- Confirm it reports this note as newly introduced on the first pull that contains it
- Confirm the baseline verification flow passes or follow the reported failure

## Not handled by /git-sync

- registry/template reconciliation
- project-specific migration edits
- conflict resolution in project-owned files
