Fix fresh LXC provisioning and desktop runtime packaging

[gitcommit90]

Summary

• fence fleet reconciliation during the intentional marker-less window of a fresh LXC provisioning transaction
• preserve strict ownership verification outside that transaction and after restart
• keep required Mnemosyne and Windows WSL/removal scripts in macOS and Windows desktop packages
• bump the versioned channel-machine contract to 0.0.7

Verification

• npm run typecheck
• npm run build
• npm test — 115 native-world assertions and 63 Node suites passed; only the two expected no-Chrome skips
• npm run test:onboarding-browser — 20/20 passed
• node test/channel-computers-isolated-backends.mjs
• node --test test/desktop.mjs
• git diff --check

Real-host evidence

• retained Linux CT 101 passed fresh unprivileged LXC provisioning, private networking, workspace/files, archive/delete, and transactional update rollback
• retained Windows VM 112 passed product-level WSL archive/restore/delete
• native x64 packaged Windows app was Squirrel-installed, launched from AppData\\Local\\1Helm\\app-0.0.6, and survived two installed-app restarts with the same Captain/workspace/provider/Skipper/#main, durable marker, and DB file identity
• the installed Windows app contains the WSL runtime/removal scripts and x64 ConPTY payload; its WSL data root remains outside the replaceable app directory

Windows artifacts remain unpublished because the release gate correctly requires a trusted Authenticode identity.