feat(setup): install/uninstall primary commands; adopt/unadopt aliases - #913
Conversation
|
Looking for reviews :) |
milamberspace
left a comment
There was a problem hiding this comment.
Reviewed the full diff (24 files), CI, and the current state of main. This is a clean, backward-compatible terminology refactor — nicely done. Verified that every file on main referencing adopt.md / unadopt.md is repointed here, so the rename leaves no dangling links, and the renames preserve history. CI is all green.
Two things before merge:
-
Rebase needed — the PR is currently conflicting.
mainhas moved since this branched: #902 (Codex CLI runtime) editedadopt.mdandunadopt.mdafter the branch point, which creates a rename/edit conflict. The good news is #902 added no new references to the old filenames elsewhere, so the rebase is just folding its content edits into the renamedinstall.md/uninstall.md. -
Consistency nit in
skills/setup/SKILL.md. The lineMain-checkout-only sub-actions (
adopt,upgrade,unadopt) …still names the old primaries. It's harmless (they're valid aliases), but for consistency with making
install/uninstallprimary it'd read better asinstall,upgrade,uninstall.
Process checks (per AGENTS.md): since this touches skills, worth confirming the setup eval suite still passes (a pure rename shouldn't move behavior, but the rule asks for it) and that tools/spec-loop/.last-sync is current before pushing the rebase.
Nothing blocking on the substance — LGTM once rebased and the SKILL.md line is updated.
9210ebb to
8adc5a0
Compare
milamberspace
left a comment
There was a problem hiding this comment.
Reviewed the command-surface change and the renames — the dispatch logic looks right: no-arg → install.md, and install / adopt both route to install.md (adopt as a documented alias), same for uninstall / unadopt. Backward compatibility is preserved, and the repointed anchors (#local-self-adoption-methodlocal, #step-5, #step-12) all resolve in the renamed install.md. No broken links within the PR's own tree.
One thing that will bite on rebase, though: docs/rfcs/RFC-AI-0007.md landed on main after this branch's point, and line 184 still links to the old filename:
- [`skills/setup/SKILL.md`](../../skills/setup/SKILL.md),
[`adopt.md`](../../skills/setup/adopt.md),
[`upgrade.md`](../../skills/setup/upgrade.md) — the flow this RFC rewires.
Once this PR is rebased onto current main, that becomes a dangling link and the lychee link-check hook fails in CI. .gitignore:9 carries the same stale reference (see skills/setup/adopt.md → "Local self-adoption") — cosmetic, but worth fixing in the same pass. Both just need repointing to install.md. I confirmed the CI failure reproduces by cherry-picking the three commits onto a current-main-based branch.
Minor (probably your "PR B" scope): a couple of command-token spots in skills/setup/SKILL.md still name the alias rather than the primary — line 404 Main-checkout-only sub-actions (adopt, upgrade, unadopt) and line 439 *(unadopt only)*. Non-blocking.
Otherwise this reads well and the install/uninstall surface is a clear improvement. Happy to see it land once the rebase repoints those two references.
|
I think we need to rebase :) |
8adc5a0 to
55f5594
Compare
|
@choo121600 - rebased |
55f5594 to
07b2080
Compare
|
Rebased again after other merges - needs re-approve @choo121600 |
|
#1116 - should fix those |
Now that Magpie can be installed from agent marketplaces, 'install' is the more familiar term than 'adopt'. Make it the primary command surface: - /magpie-setup install (default, no-arg) is first-time install; 'adopt' is a documented alias. - /magpie-setup uninstall reverses it; 'unadopt' is a documented alias. - Rename adopt.md -> install.md, unadopt.md -> uninstall.md (skills + docs); repoint all path references. - Keep the 'adopter'/'adopter repo' noun and the 'Adopt a Magpie' slogan. Command surface only (PR A). The wider docs/skills prose reword of the adopt->install verb is a separate follow-up (PR B).
…' for the mechanism Per the terminology model: a project *adopts* Magpie (the relationship); the *installation* is the process/mechanism. Restores 'Adopt and maintain ... via the snapshot-based installation mechanism' in the skill description; the install/uninstall command names and adopt/unadopt aliases are unchanged.
…s install
- Reword process-y 'adoption/adopt flow' phrases to 'install/installation'
where they describe the mechanism (the adopt/install flow, first-time
install, during installation, install recipe/instructions, uninstall flow),
and prefer '/magpie-setup install' in how-to steps. Relationship/noun uses
('adopter', 'adopter repo', 'a project adopts Magpie', 'adoption model')
and the adopt/unadopt aliases are left untouched.
- Add an 'Adoption vs. installation' note to docs/setup/README.md: a project
ADOPTS Magpie (relationship); INSTALLATION is the process (adopt = alias).
07b2080 to
fb6db1d
Compare
The `skills/setup/adopt.md` → `install.md` rename in this PR missed one
reference, in RFC-AI-0007's References section. `lychee` caught it and
failed the required `prek` status:
[./docs/rfcs/RFC-AI-0007.md]:
[ERROR] .../skills/setup/adopt.md (at 184:3) | File not found.
A repo-wide sweep for `adopt.md` / `unadopt.md` finds no other stale
reference, and `prek run --all-files` now passes clean.
…tall.md The apache#913 rebase repointed two of the three adopt.md links in this file but missed the one inside the settings.local.json wiring bullet this PR adds, which is what the CI link validator (prek, validate skills and tool contracts) has been failing on.
Now that Magpie can be installed from agent marketplaces (#907), "install" is the more familiar term than "adopt." This makes
install/uninstallthe primary command surface, withadopt/unadoptkept as aliases (nothing breaks for anyone using them).Changes
/magpie-setup install— first-time install (the default no-arg action);/magpie-setup adoptis a documented alias./magpie-setup uninstall— reverses it;/magpie-setup unadoptis a documented alias.skills/setup/adopt.md→install.md,skills/setup/unadopt.md→uninstall.md, anddocs/setup/unadopt.md→uninstall.md; all path references repointed.argument-hint, sub-action list, and command table.Deliberately kept
Scope: command surface + file renames only. Part of the adoption→installation terminology shift discussed on the list.