magpie-setup-statuslisted

<!-- SPDX-License-Identifier: Apache-2.0 https://www.apache.org/licenses/LICENSE-2.0 --> <!-- 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 — the project's pin) <local-lock> → `.apache-magpie.local.lock` (gitignored — per-machine record) <upstream> → adopter's public source repo (the repo this skill runs in) --> # setup-status Render a one-glance picture of **how apache-magpie is adopted in this repo**, then let the user reconfigure it without leaving the view. The dashboard answers the questions an operator actually asks: *which install method and version are pinned, has the snapshot drifted, which agent targets are wired, which skill families are installed, and are the symlinks healthy.* This skill is the **configuration** view of adoption. It is read- only on its own; every change it offers is carried out by delegating to [`/magpie-setup`](../setup/SKILL.md) — the one skill that owns adoption mutation. For a **deep integrity / health check** (lock parsing, per-check ✓/✗ matrix, permission-hygiene audit, ASF comdev MCP prerequisites, stale-worktree sweep), use [`/magpie-setup verify`](../setup/verify.md); this skill links to it rather than duplicating its checks. --- ## Adopter overrides B