mycoupgrade-path-safetylisted

Apply this skill when validating, testing, or releasing any version-to-version upgrade, addressing critical missing paths and suspected fabrications. Covers five orthogonal procedures: (1) clean-state revert methodology before upgrade testing to simulate real-world conditions; (2) CI-as-primary-gate discipline when local tests are flaky or environment-contaminated; (3) merge→publish→test release sequencing to avoid blocking on local reliability; (4) detecting and handling the self-propagation trap, where a bug disables the auto-adopt mechanism that would deliver its own fix; (5) dev environment routing via pattern extension (runtime.command + runtime.home + manual channel) instead of bespoke knobs.
goondocks-co/myco · ★ 13 · AI & Automation · score 79

Install: claude install-skill goondocks-co/myco

# Upgrade Path Safety Profile This skill governs the discipline around validating and releasing version-to-version upgrades in the Myco native installer. The procedures were established under real conditions during the `feat/native-installer` branch and apply to any upgrade cycle involving binary replacement, installer mechanics, or auto-adopt channels. Use this skill whenever you are: testing an upgrade path, cutting a release beta, debugging auto-adopt failures, or designing dev environment routing for dual-daemon setups. ## Prerequisites Before any upgrade-path work: - Know the **source version** (prior release) users will be upgrading from. - Know the **target channel** (`beta`, `stable`, or `manual`) for the upgrade. - Have a clean machine state available — or be prepared to revert to one. A development state with partial changes applied is **not** a valid starting point for upgrade testing. - CI must be available and healthy. If CI is down, all validation gates collapse. ## Procedure A: Clean-State Revert Before Upgrade Testing **Why:** Testing an upgrade from a mid-development state doesn't simulate real user conditions. Only a clean install of the prior release exercises the actual code path users will hit. **Steps:** 1. **Fully revert** to a clean install of the prior release — uninstall the current binary, clear `MYCO_HOME`, and reinstall as if you were a fresh user: ```bash # Remove current install rm -rf ~/.myco/bin/myco # Reinstall pri