Recover verified state when PARTUUID symlink disappears after resize timeout

[Deadbytes101]

Alpha.13 physical boot on exact image SHA-256 454b008c75a4b3e1634bf6081dfab352205b86b4e2b162838ecc7e160c44c154 advanced past the previous Rust e2fsck: exit Some(4) mismatch but still failed to establish persistent state.

Physical evidence:

• release commit: 4f82bab050038465831b620f8444361a2130d711
• boot-attested state path: /dev/sdb4
• state PARTUUID: 5249474f-04
• core reported resize2fs: timeout
• recovery then failed with attested state PARTUUID is unavailable: ... /dev/disk/by-partuuid/5249474f-04
• final state outcome: repair_required
• /var/lib/rigos remained the live overlay
• recovery credential remained boot-scoped
• SSH host identity remained ephemeral

Root cause:

The Python recovery authority currently requires the /dev/disk/by-partuuid/<PARTUUID> udev symlink. After the bounded core resize attempt, that symlink can be temporarily or persistently absent even though the current-boot attestation still identifies the exact state block device by path and major:minor. Recovery fails before it can run its bounded verified e2fsck/resize2fs path.

Required fix:

• advance the next immutable artifact to Alpha.14
• retain PARTUUID symlink resolution when available
• when the symlink is absent, allow only the exact current-boot attested state path as a fallback
• verify that fallback is a block device with the exact attested major:minor
• verify its sysfs parent is the exact attested boot disk major:minor
• verify ext4 type, expected RIGOS state label, exact PARTUUID, and unmounted state
• reject any mismatch or device substitution
• keep filesystem commands bounded and configuration/miner fail-closed until state is genuinely ready
• add source and exact-image assertions for the fallback safety boundary

Physical acceptance requires state ready, /var/lib/rigos mounted from the verified ext4 state partition, password restoration across reboot, persistent SSH fingerprint, configuration activation, and miner startup.

[Deadbytes101]

Alpha.14 implementation is now staged in draft PR #32 at exact head 3762791a3ac7a06101a4e11aa337acee7ef612e8.

The recovery authority now handles the physical missing /dev/disk/by-partuuid link without relaxing disk identity: fallback is restricted to the current-boot attested state path and must match the attested state major:minor, attested boot-disk sysfs parent, ext4 type, expected label, exact PARTUUID, and unmounted state. Existing symlink substitution is rejected.

Source verification, exact-image verification, and physical acceptance remain pending.

[Deadbytes101]

Alpha.14 source gate passed at exact head 3762791a3ac7a06101a4e11aa337acee7ef612e8 with a clean worktree.

The full WSL verification suite passed, including the state recovery behavioral tests for exact current-boot attested-path fallback when the PARTUUID symlink is absent, plus rejection of mismatched/substituted block identity. Final authority marker: RIGOS_WSL_SOURCE_GATE=PASS.

Image build and physical verification remain pending. Issue stays open until persistent state mounts successfully and password/SSH identity survive reboot.

[Deadbytes101]

Alpha.14 exact-image build and verification passed for the fix tracked here.

• exact source head: 3762791a3ac7a06101a4e11aa337acee7ef612e8
• image: rigos-usb-amd64-0.0.4-alpha.14.img
• SHA-256: 5a85aa8cff0588c34bcd4b54a2913778b5b06d87d011e9f77469da1f7b3f6612
• USB appliance gate: PASS
• RandomX gate: PASS
• authenticated XMRig observer gate: PASS
• firstboot exact-image gate: PASS
• state recovery and credential exact-image gate: PASS
• manifest head/version/integrity: PASS
• wrapper final marker: ALPHA14_EXACT_IMAGE_BUILD=PASS

Physical acceptance is still pending. Keep this issue open until the exact image proves state ready, /var/lib/rigos mounted from the verified ext4 state partition, persistent password restoration and SSH fingerprint across reboot, configuration activation, and miner startup.