What problem does it solve? Upgrading installed aos capabilities risks losing the user's hand-edits and personalization, and blind re-renders can silently destroy untracked files or leave stale tool binaries behind. ## Core Features & Use Cases - Personalization preservation: Folds the user's hand-edited render drift into MOD.md before re-applying it to fresh upstream, so upgrades never erase customization. - Diff-gated commits: Stages each capability's re-render in the personal git repo and requires review of the staged diff before committing, with a clean restore path on decline. - Lifecycle housekeeping: Repairs broken links, re-installs shipped CLI tools via uv, handles renamed skills and absorbed capabilities, and offers retirement of MOD statements now covered upstream. - Use Case: After pulling the latest aos upstream clone, ask your agent to upgrade all installed capabilities; it re-renders each one against your MOD.md, shows you a per-capability diff, and commits only what you approve. ## Quick Start Tell your agent to upgrade my installed aos capabilities after pulling the latest upstream, and review each staged diff before it commits.