agent-shims

# Agent Shims This is an experimental lifecycle tool. Installing authenticated standalone agent TOML does not prove that the active collaboration interface can select that custom profile. A task name or child path matching the role name is not proof. Use installed shims only when the runtime exposes an explicit custom-agent selector and observed child metadata plus verifier output prove selection; otherwise use blank-agent role-card injection. Accept exactly one action: `doctor`, `status`, `install`, or `remove`. Reject missing, extra, or unknown arguments without writes. Locate `../../scripts/manage_role_agents.py` relative to this installed `SKILL.md`. Run it with the current Python 3.10+ interpreter and the selected action. Do not copy the manager, resolve it through a source checkout, or edit generated agent files directly. - `doctor`: run the read-only live prerequisite check and render its JSON result for a person. - `status`: run the read-only health and installed-roster summary and render its JSON result for a person. - `install`: report the stable platform block. Do not request approval; no new shim plan or write is allowed. - `remove`: use the same exact-digest flow to remove every intact managed shim. Never delete by filename prefix or marker alone. Preserve the manager's exit contract: `0` success/converged, `2` usage, `3` cancelled, `4` drift/conflict, `5` prerequisite blocked, `6` untrusted state, `7` internal/recovery failure. Do not retry a mutating actio...