Handle Rust e2fsck exit Some(4) in verified state recovery

[Deadbytes101]

Alpha.12 physical boot on exact image SHA-256 e4cc44215c70cba7b3d7a9c5916256992c40161e110314a657c1856d9d1a3a16 still left persistent state unavailable.

Physical evidence:

• release commit: 5af491daed09dff4b5f90244f4fee718edd5ade2
• state device: /dev/sdb4
• state PARTUUID: 5249474f-04
• state outcome: limited_capacity
• exact core message: bounded command failed: e2fsck: exit Some(4): ... UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
• /var/lib/rigos remained the live overlay
• recovery credential remained boot-scoped and non-persistent
• SSH host identity remained ephemeral
• profile and miner remained blocked

Root cause:

Alpha.12 routes e2fsck: exit 4 into the verified repair path, but the Rust state core formats the process status as exit Some(4). The string matcher therefore misses the physical condition and never reaches the bounded verified e2fsck -f -y escalation.

Required fix:

• advance the next immutable artifact to Alpha.13
• recognize the exact Rust exit Some(4) representation as the uncorrected ext4 condition
• retain compatibility with the Python repair helper's exit 4 representation
• use a narrow parser/helper rather than broad substring matching
• reject exit 8 and other operational/usage/cancelled/library failures
• preserve current-boot USB attestation, exact PARTUUID/ext4/label verification, and unmounted-device checks
• rerun source and exact-image gates
• keep credentials boot-scoped and miner/configuration fail-closed until state is genuinely ready

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]

Implemented on branch fix/alpha13-state-e2fsck-option-exit at exact head 4f82bab050038465831b620f8444361a2130d711 in draft PR #30.

The failure was a representation mismatch: the Rust core emitted e2fsck: exit Some(4), while Alpha.12 only matched e2fsck: exit 4.

The new parser accepts both exact forms, routes only exit code 4 into the existing verified repair path, rejects Some(8) and other outcomes, and keeps all USB attestation/revalidation/fail-closed boundaries intact.

Source gate and exact-image build remain pending.

[Deadbytes101]

Alpha.13 source gate passed at exact head 4f82bab050038465831b620f8444361a2130d711 with a clean worktree.

The behavioral source tests now cover the physical Rust status form e2fsck: exit Some(4) and preserve fail-closed handling for Some(8) and other non-4 outcomes. All source verification stages completed successfully, ending with RIGOS_WSL_SOURCE_GATE=PASS.

Exact-image build and physical state/password/SSH persistence validation remain pending.

[Deadbytes101]

Alpha.13 exact-image verification is complete at head 4f82bab050038465831b620f8444361a2130d711.

Artifact authority:

• dist/usb/rigos-usb-amd64-0.0.4-alpha.13.img
• SHA-256 454b008c75a4b3e1634bf6081dfab352205b86b4e2b162838ecc7e160c44c154

All source/image authority gates passed, including the state recovery and credential exact-image verifier. Physical validation remains pending; do not close this issue until the real node reaches state ready, mounts the verified ext4 state partition at /var/lib/rigos, restores the same recovery password across reboot, preserves the SSH fingerprint, and starts configuration/mining successfully.