Codex Lifeboat v3.4.11

Codex Lifeboat 3.4.11 — Windows provisioning guard handling

Nederlands

Codex Lifeboat 3.4.11 fixes a backup failure caused by a live Windows sandbox
provisioning guard directly below .codex.

Fixed

• Recognizes only root-level names matching
  .codex-provisioning-<16 hexadecimal characters>.guard.
• Excludes those guards consistently from backup inventory, portable-profile
  copying, restore safety copies, and legacy portable-profile restore payloads.
• Keeps all near-matching names, nested guard files, ordinary *.guard files,
  conversations, projects, settings, and registrations mandatory.
• Preserves a destination computer's live provisioning guard when validating an
  older package that happens to contain one.
• Keeps the operation header and current status visibly failed after an exception
  instead of returning to the misleading Ready state.

The official Codex Windows sandbox creates these empty files with
FILE_DELETE_ON_CLOSE to keep a pinned directory nonempty during privileged
provisioning. They are synchronization/runtime state, not user data.

Validation

• Added positive coverage for lowercase and uppercase valid guard names.
• Added negative coverage for suffixes, malformed IDs, nested guard files, and
  ordinary files.
• Added backup inventory, copy, safety-copy, and legacy-restore coverage.
• Added a terminal GUI-state regression check.
• All 97 source checks and all 12 automated Windows compatibility scenarios pass.

Download

Download Codex-Lifeboat-Windows-x64-Portable.zip, extract it completely, and run
Codex-Lifeboat.exe.

The executable remains unsigned. Keep the old computer and an independent recovery
copy unchanged until the destination has passed post-restore checks.