Road to v1.0

[btsouth]

Track the remaining work toward an official v1. Current public baseline: v0.0.18-preview, published September 13. v15–17 were unpublished candidates.

The reconciled scope, evidence boundaries and testing instructions merged in #115. Use V1 readiness for detailed acceptance requirements and TESTING.md for reports.

Completed baseline

• Ship Omarchy 4.0.3, browser-theme repair (Theme changes prompt for a password: image omits /etc/sudoers.d/omarchy-theme-browser and the Chromium policy dir #89) and an in-place guest runtime update path.
• Ship resource/disk controls (Increase storage , ram , cpu. #87), installation moves, file/folder clipboard and transfer windows, snapshots and recovery controls.
• Pin the source-built graphics runtime and matching source archive.
• Record physical AMD Windows 11 acceptance, including storage/recovery, transfers and graphics testing, with individual artifact limits.
• Publish signed v18 and verify public downloads, versions and update signatures.

Evidence: guest upgrades and Windows acceptance. Earlier-runtime tests do not establish every check on the final runtime.

Next candidate and v1 gates

• Include merged, unreleased Reduce portable copy space and retry transient Windows publication locks #113/Copy existing portable disks without raw staging #114 storage improvements and Fix duplicate runtime ownership without losing Neovim helpers #118 runtime ownership repair in the next candidate; record exact launcher/runtime/guest hashes.
• Fix duplicate Neovim helper ownership in v18 runtime package duplicates ownership of omarchy-nvim helpers #116 via Fix duplicate runtime ownership without losing Neovim helpers #118; full factory build/boot and normal existing-guest upgrade/reboot checks pass. Runtime 4.0.3-4 and compatibility 21 are not yet in a public release.
• Resolve Update not working after fresh install #90: reproduce the stale package-lock report and verify interrupted package-update recovery. Active locks must remain protected.
• Validate preserved guest upgrades, interrupted launcher/payload updates and forced rollback; cover pre-transfer installs, both signed feeds, old previews skipping the bridge, preview-to-stable, direct stable and stable-to-stable.
• Complete Intel/NVIDIA graphics, full Hyper-V and Core Ultra physical coverage; test each advertised Windows version and lower-memory hosts.
• Complete host sleep/resume, physical mixed-DPI displays, keyboard/focus and RDP/VNC, headphone switching and microphone-indicator checks. Record idle CPU and endurance on the selected runtime.
• Regress moves, backup/restore/reset, snapshot rollback, growth and reclaim on the exact candidate with file hashes, interruption, low-space and temporary Windows-lock cases.
• Restore configuration, packages and theme onto a fresh physical Omarchy install without VM-specific state.
• Finalize support ownership, tested host scope, user docs, stable release notes and winget distribution; verify public assets after publication.

Scope

Prioritize a dependable persistent Omarchy desktop, transfers, resource controls, updates and recovery. Portable mode remains experimental until installed-guest conversion, external-drive lifecycle and second-PC use pass. Webcam capture, accelerated RAM resume, direct drops into arbitrary guest apps, bridged networking, ARM64 and booting a physical installation are outside the v1 commitment. Multiple display windows exist but need the physical display/input checks above. Borderless mode (#111) is optional follow-up.

Next checkpoint: package-update/recovery evidence plus targeted hardware reports. Passing CI alone does not establish release readiness.

September 14 checkpoint

Readiness cleanup #115 is merged with all required checks passing. Investigation #117 verifies that published v18 starts unlocked and completes system package updates on Linux/KVM. A controlled pre-transaction SIGKILL reproduces a stale lock across reboot; recovery and the final reboot preserve the fixture package and user-file hash. This does not close interruption-during-write or Windows update/rollback coverage. The run also exposed the separate ownership defect #116.

Runtime ownership acceptance

#118 fixes the confirmed ownership defect and preserves the Neovim helpers through upgrades. Full factory build/boot CI and all five normal-updater boot phases passed, including old-image boot and return to the candidate. Evidence. This is headless KVM/CI evidence; signed Windows release acceptance remains open. #119 separately tracks the missing Neovim skeleton template audit without assuming user-visible breakage.

[btsouth]

v0.0.19-preview is published and is now Latest (Release run 35043448976, September 16). Verified public: releases/latest serves v19; TryOmarchy.exe, its .sha256, SHA256SUMS, and both signed update feeds return 200; update-v2.json carries version v0.0.19-preview, manifest a4d2f54d, launcher sha256 90a74976.

This supersedes the September 13 baseline in the checklist above. Two notes for the record:

• The launcher pin had been left on the unpublished v19 draft, which broke fresh builds from master (Fresh installs fail with HTTP 404 because the pinned release does not exist yet #124). Point the launcher's release pin back at v0.0.18-preview until v0.0.19-preview is published #126 reverted the pin, Catch an unpublished release pin in CI before it reaches master #125 added a CI network check to validate-pin.py so it cannot happen silently again, and Only check the install path itself for extra data streams, not every ancestor folder #123 fixed the installation-move ancestor-stream bug (Installation move fails with "additional Windows data stream" when an unrelated ancestor folder has one #122).
• The draft physical test was not run for v19. Accepted because the guest kernel and GPU runtime are byte-identical to v18 and only guest packages plus the compat-22 initramfs/rootfs changed; the KVM five-boot preservation run covered that path. This is not physical v19 acceptance. A physical smoke can be recorded later if useful.

Remaining v1 gates in this issue are unchanged: #90 interruption/recovery, the Intel/NVIDIA/Core Ultra/Hyper-V and Windows-version hardware matrix, sleep/resume and mixed-DPI input, native export/restore acceptance, and stable release notes plus winget distribution.