Skill versions, updates, and conflicts
Keep installed instructions matched to retained packages without overwriting customer edits or confusing receipts with execution permission.
Keep instructions matched to the release
Framework skills come from the selected release, not the CLI binary's version or a global latest-skill feed. vendor/smoothie/application.json identifies the retained selection; its framework/skills/ files are immutable, hash-listed inputs. Installed copies carry provenance in .smoothie-install.json, with license paths returned by the CLI. A receipt records origin, not permission to execute instructions.
Keep product-specific rules in the application's own agent instructions rather than editing retained release files. If you customize an installed skill, preserve the customization and its origin; do not alter the receipt to make modified files appear identical to an official copy.
Preserve conflicting copies
Installation leaves byte-identical managed copies unchanged. It refuses same-named edited, unmanaged, or different-release copies rather than overwriting them. Inspect the conflict and preserve the complete existing directory, including companion files and its receipt, in your own backup outside the host's skill-discovery paths. A same-named copy moved elsewhere under those paths may still be discovered.
After resolving the conflict intentionally, obtain a fresh installation plan and review its identity and actions before applying it. There is no force, removal, selective-skill, or automatic-upgrade command in this installation flow. Do not delete customer instructions merely to obtain a passing install.
Replace or restore deliberately
A package update or restoration leaves installed instructions unchanged. Before further agent work, compare their provenance with the selected packages, preserve old copies, and use the installation flow to install that selection's skills. Reapply your local instructions through a reviewed merge, not a silent overwrite. Start a fresh host session and confirm discovery again.
An interrupted batch may contain some complete installed skills and others still pending. Inspect the result, then replan against the current state; complete identical copies remain unchanged. This is not a package rollback or permission to discard evidence of unrelated installation or deployment effects.