Repository navigation
v0.15.11 - the config migration keeps a legacy file that changed during the move
The config migration keeps a legacy file that changed during the move
Fixed
- A legacy project config edited during the migration is no longer deleted. Severity HIGH: one edit to a setting, lost silently, inside a one-time migration.
node scripts/configure.mjsmoved the legacy file to.claude/coal/coalface.jsonand removed it on its first read, so an edit made in that window was lost without a word. The legacy file is now re-checked just before removal: if it changed, it is kept, one warning names it, the new config does not include that change, and the run exits 1. The window is narrowed, not closed. Regression test:scripts/configure-migrate.test.mjs.