Headless Hardening

Align smoke coverage with the published headless workflows. Why it matters: The smoke test is the broadest end-to-end headless gate. If it does not match the workflows the docs claim to support, the release story is rhetorical instead of evidence-backed. Focus on `smoke_test_script` and `cmd_smoke_test` in `xtask/src/main.rs` while you trace the snippet.

/// Comprehensive smoke test: login, coreutils, TCC, Phase 32 build tools.
///
/// Replaces the Phase 31 smoke test with a more thorough script that validates
/// the full userspace stack including new utilities and the make build tool.
#[allow(unreachable_code)]
fn smoke_test_script(doom_wad_available: bool) -> Vec<SmokeStep> {
    let _ = doom_wad_available;
    let mut steps = Vec::new();

    // -----------------------------------------------------------------------
    // 1. Boot and login (handles both first-boot locked accounts and normal login)
    // -----------------------------------------------------------------------
    // First-boot: account is locked (hash "!"), login prompts to set password.
    // Normal boot: account has a password, login prompts for it.
    // Both paths use "root" as the password.
    const FIRST_BOOT_LOGIN: &[SmokeStep] = &[
        SmokeStep::Send {
            input: "root\n",
            label: "set initial password",
        },
        SmokeStep::Wait {
            pattern: "Retype password:",
            timeout_secs: 10,
            label: "wait for password confirmation prompt",

View on GitHub

Make service state inspection and control part of the normal path. Why it matters: A headless/reference system needs one documented way to inspect, restart, stop, and reason about services. If the normal path is still ad hoc, the service model is not trustworthy enough for a release claim. Focus on `ServiceManager` and `cmd_list` in `userspace/init/src/main.rs` while you trace the snippet.

struct ServiceManager {
    services: [ServiceDef; MAX_SERVICES],
    count: usize,
    discovered_disabled: [FixedStr<MAX_NAME>; MAX_DISCOVERED_DISABLED],
    discovered_disabled_count: usize,
    pid_table: PidTable,
    shutdown_requested: bool,
    login_pid: i32,
    /// File descriptor for the syslog socket (`/dev/log`), or -1 if unavailable.
    syslog_fd: i32,
}

View on GitHub

Make the storage workflow part of the supported headless path. Why it matters: Phase 53's release story explicitly includes storage. Operators need a documented way to verify that the writable data path backing packages, logs, and user data is healthy and recoverable. Focus on `main` in `userspace/coreutils-rs/src/mount.rs` while you trace the snippet.

fn main(args: &[&str]) -> i32 {
    // No arguments: print /proc/mounts.
    if args.len() == 1 {
        return show_mounts();
    }

    // Parse: mount -t TYPE SOURCE TARGET
    let mut argi = 1usize;
    let mut fstype: Option<&str> = None;

    if argi < args.len() && args[argi] == "-t" {
        argi += 1;
        if argi >= args.len() {
            write_str(STDERR_FILENO, "usage: mount -t TYPE SOURCE TARGET\n");
            return 1;
        }
        fstype = Some(args[argi]);
        argi += 1;
    }

    if args.len() - argi != 2 || fstype.is_none() {
        write_str(STDERR_FILENO, "usage: mount -t TYPE SOURCE TARGET\n");
        return 1;
    }

View on GitHub