rig/pixi.lock: re-lock with pixi >= 0.80 and pin requires-pixi (plain install on a rig rewrites the lock) #280

Found in the ww18 QC of #274 (#274 (comment)).

rig/pixi.lock was written by pixi 0.69.0 (Mac). On a rig PC with pixi 0.80.0 a plain cd rig; pixi install succeeds but rewrites the lock in place (1095 lines, 554+/541−): the osx-arm64 platform becomes osx-arm64-macos-14-0, virtual-packages: blocks appear, and every conda_source hash is recomputed. The rig-nodes pin does not change. The checkout is then dirty and the next git checkout refuses (Your local changes … would be overwritten: rig/pixi.lock). pixi install --locked installs the committed lock unchanged on both versions, so it is the documented rig command; this issue is about not leaving the trap.

Every pixi command also warns that [system-requirements] is deprecated in favor of virtual packages on platforms.

Fix, one PR for the next candidate:

• upgrade the Mac's pixi, move macos = "14.0" onto platforms = [{ name = "osx-arm64", platform = "osx-arm64", macos = "14.0" }, "win-64", "linux-64"], re-lock with the new pixi;
• add requires-pixi = ">=0.80" to rig/pixi.toml so an older pixi refuses instead of writing an older lock;
• verify pixi install --locked on ww18 leaves git status rig/ clean.

Check the root pixi.toml/pixi.lock for the same skew while at it. The ww18 diff is kept at C:\qc\_pixi_lock_rewrite_ca9f5c4.diff.

LAB-338.

🤖 Generated with Claude Code