emirb wrote that the refresh downgrades to whatever the destination repositories list, and only after that the switch installs omarchy and omarchy-settings. He wrote that stable's database had listed development builds from August, so the refresh moved an edge machine onto that older build. He wrote that the older build predates command-scoped sudo, so the wrapper check stopped the switch and said the packages were switched when they had not been.

emirb wrote that the refresh now ignores the development packages on stable and the release candidate, so the swap is the only transaction that touches that pair. He wrote that removing the stale build from the repository fixed that case, and that this change keeps the switch safe whatever a destination repository lists. emirb wrote that machines already stranded on r1832 recover with omarchy channel set stable.