reVault CLI 0.5.0

Publication status: CLI archives are available. Package-registry publication and final postpublication checks are still in progress.

reVault 0.5 introduces archive format 4 and the 0.5 compatibility line, with authenticated archive metadata and durable transaction recovery. Password-based access, Session Agent transport and compression-buffer ownership have been hardened. Extraction restores stored permissions by default.

Upgrade matching CLI and binding/native-carrier packages together. Migrate the Vault first, then older archives; signed v2/v3 migration requires the established owner key. Keep originals until migrated data is independently checked. The 0.4 line cannot read format-4 archives or Vault containers.

The exact Linux distribution binary completed a reduced comparison with 450 observations in 67 minutes 24 seconds. Across five measured workloads, unencrypted extraction took 16–55% less time than ZIP; all five paired statistical gates passed. Password-encrypted, owner-signed creation was faster than compression-only ZIP in these workloads. Protected extraction was faster for the larger and many-file workloads, but slower for both 64 MiB workloads. These protected comparisons are descriptive and compare different security capabilities.

The six-case resource screen peaked at a conservative 103.5 MB combined CLI and Session Agent bound. The release ceiling is 104 MB; 100 MB remains the target. The 450-observation comparison peaked at 100.43 MB. These bounds combine process lifetime peaks and do not establish a universal archive-capacity or memory guarantee. Measurements used four workers, verified extracted bytes and permissions, and the unchanged format-4 archive layout. Reusing fixed read archives and reducing redundant observations shortened the campaign; the shorter campaign is not itself a product speedup.

The manual source documents archive and metadata limits. The current reader keeps the complete file index in memory, so memory use grows with entry count, path lengths and chunk descriptors. CLI extraction defaults are 1 GiB per file, 10 GiB total and 100,000 selected entries; numeric overrides are not currently exposed. Practical capacity qualification and CLI overrides are tracked for post-release work in #330 and #331.

Qualified source: b086e6a. Candidate validation and artifact seal completed successfully: 61 jobs passed and 22 conditional jobs were skipped. This includes all twelve platform installed-package jobs and both secure-API configurations. The exact-artifact process admission, six-case resource screen and reduced comparison also passed. The release includes the historical migration decoder correction for RUSTSEC-2026-0344, extraction-memory corrections, and a framed Unix Session Agent reply-race correction. The comparison report and machine-readable results are attached to this release.