Physical alpha.10 reboot exposed that rigos-recovery-access writes the rigosadmin password hash under /var/lib/rigos/recovery even when persistent state was never mounted. In that case the path is only the live overlay, credential_persisted is reported true, and the password disappears on reboot, forcing setup again.
Observed alongside issue #24 (resize2fs timed out and state remained unavailable).
Required behavior:
- never claim persistence unless
/var/lib/rigos is the current verified persistent state mount
- never write a credential hash into an unverified or overlay-backed
/var/lib/rigos
- when state is unavailable, explicitly mark the credential as boot-scoped while keeping local/SSH diagnostics available
- once state initialization succeeds, persist the password hash exactly once and restore it on subsequent boots without prompting
- retain strict hash validation, atomic writes, redaction, and fail-closed configuration/miner behavior
- add source and image regression coverage
The underlying state timeout is tracked separately in #24.
Physical alpha.10 reboot exposed that
rigos-recovery-accesswrites therigosadminpassword hash under/var/lib/rigos/recoveryeven when persistent state was never mounted. In that case the path is only the live overlay,credential_persistedis reported true, and the password disappears on reboot, forcing setup again.Observed alongside issue #24 (
resize2fstimed out and state remained unavailable).Required behavior:
/var/lib/rigosis the current verified persistent state mount/var/lib/rigosThe underlying state timeout is tracked separately in #24.