OpenClaw migration completes without moving when the seed is absent
Pull request 15864, merged into quattro, says the OpenClaw migration completes without moving anything when the seed is absent. On version 4.0.5, pull request 14212 says that move cannot finish on a machine with the openclaw package. Without the seed, every omarchy update stops there.
Pull request 14212 says it retires migration 1790397381, so that migration finishes everywhere without changing anything, and that it brings the move back as migration 1792334754. It says that with the seed, the older move fails anyway, because omarchy update runs migrations on a PATH without ~/.local/bin and then reports that openclaw on PATH is missing.
Pull request 15875, merged into quattro, says migration 1792334754 stops every omarchy update when someone also has an OpenClaw of their own: one at ~/.local/bin, another on the session's PATH, or a gateway running another OpenClaw. The pull request says those three refusals now exit 79, and on that status the migration finishes and prints this line.
“Leaving OpenClaw as it is; launching it from Omarchy finishes the move once the OpenClaw above is out of the way”
Pull request 15875 says a setup that actually fails, such as the npm registry being out of reach, still keeps the migration pending. Pull request 15864 says a machine that takes 4.0.6 before the seed can complete the migration before there is anything to move, and that launching OpenClaw through Omarchy handles the setup. Pull request 15875 says the change is for 4.0.6 together with pull requests 14212 and 15864.