Follow-up to v1.5.13. Source only — no new installer. Install with the AMBER_1.5.12.661_x64-setup.exe asset on the v1.5.12 release.
v1.5.13 stopped the installer from destroying agent definitions you own. It also, unintentionally, stopped it from updating the ones we manage.
What went wrong in v1.5.13
Ownership was decided from the provenance record alone. Definitions deployed before that record existed had no entry, so every one of them was classified as yours and skipped. The practical result: planner, coder, and servant froze at whatever content they had, and no future improvement to them would ever reach a source install.
What changed
Ownership now has a second, safe signal. If the file on disk is byte-identical to the definition we ship, it is not your work — the record is simply missing. Those files are adopted and kept current. Anything whose content differs is still left alone, exactly as in v1.5.13.
How to apply this hotfix
If you installed from source with INSTALL.ps1 — this is the only path that was ever affected.
cd <your checkout>
git pull
.\INSTALL.ps1The deployer runs straight from the checkout, so there is nothing else to do. On this run you should see the three managed definitions listed without SKIP; that is the adoption.
If you installed with the AMBER installer — nothing to do. The deployer is invoked only from modules/07_shims.ps1, so an installed copy never took this path. The fix ships with the next installer release.
Files already overwritten are not recovered. Before v1.5.13 no backup was taken — that was the defect. If you have ever installed from source and owned a planner, coder, or servant definition, check whether it is still yours. Recover from your own version control if you have it.
To deliberately reset the managed definitions to current:
.\installer\deploy_agent_definitions.ps1 -ProjectRoot . -UserProfile $env:USERPROFILE -Force-Force backs each file up to .engram-bak before overwriting.
Validation
The adoption regression was run against the v1.5.13 script: it fails there and passes here, and it is the only test whose result changes — the protections for user-authored files hold in both versions.