Sync the ClaudeTools and vault repos with Gitea.

## What this does

Invokes `bash .claude/scripts/sync.sh`, which:

1. Stages tracked local changes **by name** (never `git add -A` — avoids picking up `.env`, generated files, etc.)
2. Auto-commits any local changes with `sync: auto-sync from <hostname> at <timestamp>`
3. Fetches from origin, rebases local commits onto remote
4. Pushes to origin
5. Repeats 1-4 for the **vault** repo (path read from `.claude/identity.json` `vault_path` field)
6. Surfaces any `## Note for <user>` / `## Message for <user>` blocks from incoming session logs

The script is the single source of truth for git operations. Both `/sync` and `/save` invoke it.

---

## Cross-user note handling (CRITICAL)

If sync surfaces a note from another user, display it **prominently at the top of the response, before the sync summary**, formatted as:

```
============================================================
MESSAGE FROM <author> (<date>)
============================================================
<full note content>
============================================================
```

Address each action item or question explicitly before moving on. Do not bury cross-user notes in the sync summary or skip them because other work is in progress.

---

## Output format

Report:
- Pulled commits — count + authors + one-line summaries
- Pushed commits — count + your commits + outgoing SHAs
- Vault sync status — pulled/pushed/clean
- Cross-user notes addressed (if any)
- Final HEAD + status

---

## Companion: `/save`

`/save` writes a comprehensive session log first, then invokes the same `sync.sh`. Use `/save` after substantive work to capture context for future sessions. Use `/sync` for routine repo sync without writing a log (start of day, switching machines, mid-session check-in).
