Alpha.9 firstboot configuration recovery

[Deadbytes101]

Purpose

Fix the physical alpha.8 failure mode where the appliance can boot without presenting any configuration UI and the miner remains blocked.

Tracks #20.

Root cause

rigos-firstboot.service hard-required successful rigos-state-ready.service. The firstboot program already had a state_not_ready diagnostic path, but systemd suppressed the program before it could show that screen.

The unit also waited for network-online.target, making a local setup path depend unnecessarily on external connectivity.

Changes

• change state-ready from Requires= to Wants= for firstboot only
• preserve ordering after state, state-ready, and profile-apply attempts
• remove network-online from the firstboot path
• use StandardInput=tty-force on /dev/tty1
• keep miner, SSH identity, huge-page, and runtime authorities fail-closed on state failure
• add source tests for the failed-state console path
• add an exact-image firstboot verifier
• require the image build entrypoint to run firstboot source and image gates
• advance the new artifact version to 0.0.4-alpha.9

Safety boundary

This does not weaken miner state/config gates. A failed or unavailable state still blocks configuration persistence and mining; the change only guarantees that the local console explains the failure instead of silently skipping firstboot.

Stacked relationship

This draft is based on ui/firstboot-2009-theme so the alpha.9 image contains both the verified console presentation and the boot-path correction. It must not be merged or released until exact-head source verification, exact image construction, and physical first-boot validation pass.

[Deadbytes101]

First alpha.9 WSL run: firstboot gates passed, environment dependency exposed

Exact tested head before this follow-up:

ea6463349e6685834a5c981ef63a56b2c47f534a

The rebuilt RIGOS-Dev WSL environment successfully reached and passed all alpha.9 firstboot-specific source tests:

firstboot_image_gate: 2/2 passed
firstboot_observability: 1/1 passed
firstboot_theme: 5/5 passed
firstboot_theme_preview: 2/2 passed
firstboot_tty: 4/4 passed

The overall source gate then failed in the pre-existing hive_exit_runtime_publish integration test because the fresh distro did not have jq installed. The panic came from Command::new("jq").status().unwrap() returning ENOENT; this was not an alpha.9 firstboot logic failure.

Follow-up commits:

b0965f7f9e8a8eade49144a8396e13c517ff615b  require jq in WSL tool preflight
79e769b4b9fe367e918611dd9096a5396d4c42d4  lock jq preflight into source tests

New exact head:

79e769b4b9fe367e918611dd9096a5396d4c42d4

No PASS is claimed yet. Install jq, pull the exact head, and rerun the full WSL source authority.

[Deadbytes101]

Exact-head WSL source gate PASS

Verified exact PR head:

79e769b4b9fe367e918611dd9096a5396d4c42d4

Environment authority:

WSL distribution = RIGOS-Dev
user             = deadbyte
cargo            = 1.85.1
rustc            = 1.85.1
jq                = 1.6

Authoritative source verification completed successfully:

RIGOS verification passed
RIGOS firstboot theme wrapper verification passed
RIGOS_WSL_SOURCE_GATE=PASS

Relevant alpha.9 results:

• firstboot image-gate source contract: 2/2 passed
• firstboot observability: 1/1 passed
• firstboot theme: 5/5 passed
• firstboot preview safety: 2/2 passed
• firstboot tty/state-failure reachability: 4/4 passed
• runtime publication authority: 2/2 passed
• systemd ordering verification passed
• miner observer, stability, RandomX MSR, recovery, state, runtime, and release-build gates passed
• repository policy and exact dependency scans passed

The earlier failure was an incomplete fresh WSL environment missing jq; the WSL preflight now rejects that condition before entering the Rust test suite.

This closes the exact-head source gate for PR #21. Exact alpha.9 image construction, exact-image verification, and physical clean first-boot/configuration/miner-activation testing remain pending. PR stays draft and unmerged.

[Deadbytes101]

Exact alpha.9 image build and flash authority passed on Windows against the manifest and build log.

Verified head:
79e769b4b9fe367e918611dd9096a5396d4c42d4

Artifact:
rigos-usb-amd64-0.0.4-alpha.9.img

SHA256:
be5926ea427691ffe7113632ffaed64530876d5e0a0cfaa46387e3a820a56f7f

Verified markers:

• RIGOS USB appliance verification passed:
• RIGOS RandomX performance image verification passed:
• RIGOS authenticated XMRig observer image verification passed:
• RIGOS firstboot exact-image verification passed:

Additional authority:

• manifest source commit matches exact head
• manifest image version is 0.0.4-alpha.9
• manifest artifact hash matches Windows Get-FileHash
• .img.sha256 matches the same hash

Classification:

ALPHA9_SOURCE_GATE=PASS
ALPHA9_EXACT_IMAGE_BUILD=PASS
ALPHA9_FLASH_AUTHORITY=PASS
ALPHA9_PHYSICAL_FIRSTBOOT=PENDING

PR remains draft and must not be merged until clean physical first-boot, configuration commit, miner start, and reboot persistence pass.