Editing one skill in the shared skill catalog no longer stops every agent's skills. Only that skill is skipped, with a warning, until you commit it.
One skill being edited in the managed skill catalog no longer blocks every agent's skills. Before, any uncommitted or untracked file in the catalog made it unavailable, so rig context work-install, rig up, launch and restore preflight failed for every agent. Now that skill is skipped and named in a warning, the remaining clean skills stay available, and an agent's launch only warns. An agent that already has a copy of the skipped skill keeps it as it was, and the next applied projection can refresh it once the change is committed or restored. No agent receives uncommitted files.
An uncommitted change to `catalog.yaml` itself still makes the whole catalog unavailable, because it changes what every selection means.
- Pull request
- #1031
- Release
- OpenRig 0.6.8 release notes