potiuk opened a new pull request, #443:
URL: https://github.com/apache/airflow-steward/pull/443

   ## Summary
   
   - Adds a **`method:local` self-adoption** path to `/magpie-setup`. The
     Apache Magpie framework checkout is the one repo that can't use the
     snapshot mechanism — a remote snapshot of the framework into itself
     is circular. `adopt` now detects the framework checkout *structurally*
     (`skills/setup/SKILL.md` with `name: magpie-setup` + `skills/list-skills/`)
     and links the in-repo `skills/` source directly: each
     `.claude/skills/magpie-<skill>` is a **committed** symlink into
     `../../skills/<skill>/`. No remote URL, no snapshot, no copy.
   - **Self-adopts this repo**: 38 committed `magpie-*` symlinks,
     `.gitignore` un-ignores them, and a `method: local` marker lock. Every
     contributor now gets the framework's own skills active on a fresh
     clone with no setup step.
   - **Drops the `setup-steward` migration shim** and its references.
     Pre-Magpie → Magpie migration is no longer automated; the docs
     (`install-recipes.md`, `upgrade.md` Step 0a) now describe the manual
     path.
   
   ## Type of change
   
   - [x] Skill change (`.claude/skills/<name>/`) — `setup` skill
   - [x] Documentation (`docs/`, `AGENTS.md`)
   - [x] Cross-cutting (adoption mechanism)
   
   ## Test plan
   
   - [x] `prek run --all-files` clean on commit (markdownlint, typos,
         check-placeholders, `skill-and-tool-validate` all green)
   - [x] `skill-and-tool-validate` exits 0 — link/anchor integrity holds
         across the new `adopt.md` / `verify.md` / `SKILL.md` sections and
         after the `setup-steward` deletion
   - [x] Validator unit tests: 218 passed
   - [x] Self-adoption verified live: all 38 `magpie-*` symlinks resolve to
         a `skills/<n>/SKILL.md`; git stores them as symlinks (mode 120000)
   
   ## RFC-AI-0004 compliance
   
   - [x] **HITL** — `adopt` surfaces the symlink list and confirms before 
writing
   - [x] **Vendor neutrality** — placeholders preserved; no project names 
introduced
   
   ## Notes for reviewers
   
   - The `magpie-*` symlinks are committed deliberately (targets are
     in-repo and always resolve) — this is the "commit the symlinks" choice,
     distinct from the gitignored symlinks an *adopter* repo gets.
   - `setup-steward` carried a "do not delete until pre-Magpie migration is
     dropped" note in AGENTS.md; this PR makes that call — migration is now
     documented as manual.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to