magpie-setuplisted
Install: claude install-skill apache/airflow-steward
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/legal/release-policy.html -->
<!-- Placeholder convention (see ../../AGENTS.md#placeholder-convention-used-in-skill-files):
<project-config> → adopter's `.apache-magpie-overrides/` directory
<snapshot-dir> → `.apache-magpie/` (gitignored snapshot of the framework)
<committed-lock> → `.apache-magpie.lock` (committed — project's pin)
<local-lock> → `.apache-magpie.local.lock` (gitignored — per-machine record)
<upstream> → adopter's public source repo (the repo this skill is being run in)
<framework-source> → the apache-steward source we download a snapshot from
— one of: signed zip from ASF dist, git tag, git branch.
See [`docs/setup/install-recipes.md`](../../docs/setup/install-recipes.md). -->
# setup
This skill is **the only framework artefact an adopter
project commits**. Every other apache-steward skill (security,
pr-management, issue) is a gitignored symlink into the gitignored
snapshot at `<snapshot-dir>` that this skill manages.
The adoption model is **snapshot + agentic overrides + drift-
aware updates** (not submodule, not marketplace, not vendored
copy):
- The framework is downloaded into `<snapshot-dir>` and
**gitignored** in the adopter repo. The snapshot is a build
artefact, not source.
- Three install methods are suppor