mirror of
https://github.com/runkids/skillshare.git
synced 2026-11-18 18:04:17 +00:00
Setting targets on a skill inside a tracked repo used to be refused, because writing its SKILL.md leaves the clone dirty and `update` then skips the repo (or `--force` throws the setting away). Store those targets in the source's .metadata.json instead, keyed by the skill's path, and apply them at discovery over the frontmatter. The clone stays clean, `update` keeps working, and the setting survives it. Uninstalling a repo or skill drops its entries. Overrides are saved in the same lock section that writes them: every API request reloads the store from disk, so saving after unlocking could lose them, and saving outside the lock raced with other writers. Refs #295