Put the last good version back in front of users while you fix a broken release.
First, confirm Yard is set up on this machine. Run `yard version`, and check that the Yard skill exists at ~/.agents/skills/yard/SKILL.md (%USERPROFILE%\.agents\skills\yard\SKILL.md on Windows). If either the CLI or the skill is missing, fetch https://yard.sh/setup.txt and follow it through to the end before you do anything else. If both are already in place, go straight to the task below. --- My latest Yard release is broken. Put the previous good version back in front of users right now. 1. Work in the Yard project linked to this directory. Run yard sandbox list --json and tell me which release the project itself is serving and why (channel, pinned or rolled back). 2. Ask me which earlier version to go back to. If this repo tags its releases, suggest the tag before the broken one. 3. After I confirm, run yard sandbox rollback <tag> --json. If it's refused because the project is pinned, ask me before moving the pin with yard sandbox pin <tag> instead. 4. Run yard sandbox list --json again and confirm the project now serves the older release. Then explain my options. The rollback lasts until I publish the next release, which takes over automatically once the fix is out. yard sandbox pin makes it permanent, and yard releases archive <bad tag> removes the broken release from its channel for good. Don't do either unless I ask.