Three clean boots
The image should boot into the shell repeatedly, not just once after a lucky build.
Sky OS is still pre-alpha. A download button would be easy to fake. A build that boots cleanly, explains itself, and does not waste people’s time takes longer.
The first public release is planned as a VM/QEMU-friendly preview image with notes, setup steps, and a clear list of what works.
For an operating system, “it opened once” is not enough. Before a public image makes sense, Sky OS needs repeatable boot tests, safe file operations, stable shell behavior, desktop entry/exit, and release notes that do not hide the rough parts.
The download page will stay honest: if something is experimental, it will say experimental. If something can break data, it will say that too.
The image should boot into the shell repeatedly, not just once after a lucky build.
The desktop preview should open, respond, and return to the shell without corrupting input.
Every preview will explain what works, what is mocked, what is internal-only, and what users should avoid.