Admiral v00048: Local Time Sanity, Unpairing Flows, and Image Preloading

Operating edge hardware in unpredictable field environments requires software that expects physical limitations — whether that is a missing Real-Time Clock (RTC) battery, unreliable Bluetooth silicon, or inconsistent local power. Admiral v00048 targets these systemic edge constraints with dirty-power timing safeguards, deterministic factory reset paths, and streamlined provisioning pipelines.

1. Local Clock Sanity & Time Drift Mitigation

Many low-cost edge boards lack a battery-backed Real-Time Clock (RTC), causing them to default to the Unix epoch on cold boot. This disrupts TLS handshakes, certificate validation, and log ordering before NTP syncs:

• Monotonic Disk-Backed Time: Admiral now constantly serializes the latest known system timestamp directly to non-volatile disk. On boot, the system initializes its clock to this saved state. While this does not replace NTP, it guarantees chronological monotonicity and limits potential time skew to the delta since the last disk flush.

2. Hardened Provisioning & De-registration

Onbox resets and device lifecycle transitions must be absolute, ensuring no dirty or paired state remains:

• Reworked Unpair & Factory Resets: Fully remodeled the local unpairing API and factory reset flow. Initiating a reset now deterministically purges local credentials, clears encrypted state directories, resets the network configuration store, and reinitializes device identity metadata back to a clean state.
• Preloaded Images: Our companion image-generation utility, Shipwright, now supports pre-packaging active workload container images and their definitions directly into the flashable system image. This enables zero-download, offline provisioning straight from the initial boot.

3. Connectivity, Control, & Race Condition Fixes

We have eliminated early-boot race conditions and fixed a few issues in the version comparison for customer specific builds:

• Late-Binding IP Specifications: Resolved a startup race condition where early specs reporting ran before network interfaces fully bound or leased local IP addresses, resulting in missing IP information in the cloud console.
• Version Comparison Overhaul: Fixed a bug in the update runner comparing older, non-standard semantic version strings, ensuring smooth automated paths when upgrading highly dated nodes.

4. Hardware Recovery & Installer Polish

• Bluetooth Host Controller Resets: Cheap internal USB/UART Bluetooth controllers often lock up under load. We now detect interface dropouts and automatically execute hardware-level subsystem resets on the adapter.
• Installer Crash Fix: Patched a critical crash on installer startup caused by layout constraints in the updated high-density Terminal User Interface (TUI).
• Build-Time Flag Isolation: Refactored our build pipeline to utilize strict compiler flags to explicitly isolate development, pre-release, and production builds.