mycoglobal-symbiont-installlisted

Apply this skill when working on global symbiont installation, extending the global install model, adding new symbionts for global deployment, or debugging issues that touch multiple projects simultaneously — even if the user doesn't explicitly ask about the install model or its constraints. Covers six repeatable procedures: (1) eliminating legacy fallback code during migration, (2) scoping the Symbiont page UI to auto-detect plus per-project override only, (3) scheduling symbiont health checks against PowerManager state, (4) previewing blast radius before any global write, (5) enforcing walker grove-ownership filtering to prevent cross-grove mutations, and (6) running a dry-run validation before committing global installs. Also covers the invariant that the global model is canonical — fallbacks are traps, per-project config is the escape hatch. Includes the managed skills architecture (binary-embedded, agent-standard install) and three known failure modes for global skill symlinks.
goondocks-co/myco · ★ 13 · AI & Automation · score 79

Install: claude install-skill goondocks-co/myco

# Global Symbiont Install: Design Decisions and Hazard Disciplines The global symbiont install model auto-registers all detected symbionts into every project owned by the current grove. This makes scope mutations wide by design — a single command can touch dozens of project directories simultaneously. The three design decisions below define the model's coherent shape; the three hazard disciplines prevent it from corrupting unrelated projects. ## Prerequisites - The grove walker and MYCO_HOME are initialized; the current grove's ownership list is available from the registry. - You are operating inside an active, named grove — not an unbound bootstrap state (the daemon ensures this before surfacing any global-install UI). - Project initialization has been migrated to the daemon UI. `myco init --project` no longer exists as a CLI command; do not attempt to restore it. ## Design Decision 1: No Legacy Fallback Code After Migration When the migration walker has run, the configuration is global. Do not add "if old config exists, use that" fallback paths. **Why:** Legacy fallbacks compound into divergent code paths, exponential test burden, and permanent production debt. From code review: > *"It's this class of bug that's continuously plagued us time and time again. > We just squashed another one today with a Grove migration legacy fallback. > So we know we're going to migrate it so let's not worry about the legacy > fallback. I don't want that trap in the code."* Three