magpie-setup-shared-config-synclisted

<!-- Placeholder convention (see AGENTS.md#placeholder-convention-used-in-skill-files): <project-config> → adopting project's `.apache-magpie/` directory --> # setup-shared-config-sync This skill propagates local edits in `~/.claude-config/` to the sync repo's remote, so other machines can pull them. It is the counterpart to the periodic `git pull --rebase --autostash` that the framework's example `sync.sh` runs on a timer — that direction pulls *upstream* into the local clone; this skill pushes *local* modifications upstream. ## Adopter overrides Before running the default behaviour documented below, this skill consults [`.apache-magpie-overrides/setup-shared-config-sync.md`](../../docs/setup/agentic-overrides.md) in the adopter repo if it exists, and applies any agent-readable overrides it finds. See [`docs/setup/agentic-overrides.md`](../../docs/setup/agentic-overrides.md) for the contract — what overrides may contain, hard rules, the reconciliation flow on framework upgrade, upstreaming guidance. **Hard rule**: agents NEVER modify the snapshot under `<adopter-repo>/.apache-magpie/`. Local modifications go in the override file. Framework changes go via PR to `apache/airflow-steward`. --- ## Snapshot drift Also at the top of every run, this skill compares the gitignored `.apache-magpie.local.lock` (per-machine fetch) against the committed `.apache-magpie.lock` (the project pin). On mismatch the skill surfaces the gap and proposes [`/magpie-setup upgrade`](../se