[NamelsKing]

Uploading Snap into a release folder that already contains Flatpak now merges the incoming files and preserves the existing platform artifacts. Missing leaves need no replacement flag; differing intact Swarm-owned files require the existing --allow-replace policy. Untracked or edited files remain protected.

The whole input is staged and verified privately before any public changes. Per-file ownership catalogs and a complete commit journal provide rollback and restart recovery; retention deletes only unchanged owned leaves and empty containers. Links remain separate publishing operations. Concurrent readers may briefly see a mix of complete old/new files during installation, as documented.

New state is guarded before writing, older clients retain wire compatibility, and legacy metadata/recovery/reset remain supported. Downgrading after using the new state requires restoring a consistent pre-feature backup. No new dependencies or CLI options. This completes the still-unpublished 0.8.0 release.

Validation:

• Final full suites: 788/788 tests on Bare/macOS and Node 22/Linux.
• Full Node 22/24 macOS suites passed at b911324 (786 each); final correction regressions passed on Node 22/24/Bare.
• Actual 0.3.0/0.6.3 clients and the 0.7 server compatibility cases pass against the final build.
• Build, formatting, lint/types and real npm package/install/CLI smoke checks pass.
• Snap hook checks pass: 50 tests using local CLI doubles, with no Store publication.
• Independent review of 9030173 is clean after fixes.

GitHub CI runs separately on the PR. No merge, release or server rollout is performed here.