vlsi opened a new issue, #518:
URL: https://github.com/apache/airflow-steward/issues/518

   ### What should happen
   
   Prototype APM as the packaging layer behind the existing `/magpie-setup` 
entry point. Keep `/magpie-setup` as the guided wrapper, but let it call `apm 
install` for fetch, lock, deploy, and namespacing instead of the bespoke 
snapshot-and-symlink machinery.
   
   ## In scope (APM would subsume)
   
   - Snapshot fetch and the two lock files
   - Multi-target deploy and `magpie-` namespacing
   - Family opt-in (maps onto `--skill` / sub-packages; splitting into separate 
packages is not required)
   - Drift detection
   
   
   ### Why
   
   `setup` reimplements most of a package manager by hand: a committed pin 
(`.apache-magpie.lock`), a per-machine lock, a gitignored snapshot 
(`.apache-magpie/`), multi-target deploy through a canonical `.agents/skills/` 
plus relay symlinks, `magpie-` namespacing, version pinning, and drift 
detection. 
[[microsoft/apm](https://github.com/microsoft/apm)](https://github.com/microsoft/apm)
 already provides all of that: `apm.yml` + content-hashed `apm.lock.yaml`, 
native deploy to eight agents (Claude, Copilot, Cursor, Codex, Gemini, 
Windsurf, Kiro, OpenCode), git-ref/tag pinning, and per-skill selection (`apm 
install … --skill <name>`). Carrying our own resolver may be a cost we do not 
need.
   
   ### Which layer
   
   Other / unsure
   
   ### Boundary conditions (optional)
   
   _No response_
   
   ### Out of scope (optional)
   
   - Secure-agent setup (sandbox, clean-env wrapper, pinned tools)
   - `post-checkout` hook and worktree propagation
   - Agentic overrides: the protocol is plain text in each `SKILL.md`, and 
override files live in the adopter's own `.apache-magpie-overrides/`, which 
`apm install` never touches
   
   ### References (optional)
   
   * https://github.com/microsoft/apm


-- 
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