docs: README, plan, guides and the site describe what is built now

README: rewritten around what runs (Linux software, Xorg, apk, Linux's drivers), the honest gaps, measured numbers.
plan/: 1.0.md is the finish line, where each clause of the acceptance test stands, and the register (one failing
clause: a root that survives a reboot); built plans (foundations, hybrid, alpine, xorg) and the decided-against one
(wayland) are gone, their content lives in architecture/; roadmap.md is only what is still open.
guides: building/layout/testing/adding-a-driver (Linux code may be used). history: four entries (ls -lR, TLB
shootdowns, MDIO 0x02460246, netlink MSG_TRUNC). Website: cards, stack, download page, docs index.
Code comments that pointed at deleted plan docs point at the architecture docs.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EVRhxi9zpdW2uDUN4FVcao

docs/Website/download.html

@@ -66,33 +66,34 @@
     <p class="nv-prose">
       SchOS ships as one bootable ISO. It boots on UEFI, runs entirely from
       RAM, and touches nothing on the machine unless you tell it to — there is
-      no installer yet, and that is the point of trying it this way.
+      no installer yet, and that is the point of trying it this way. It comes up with
+      Xorg, Window Maker and Alpine's package manager.
     </p>
 
     <div class="nv-cluster">
-      <a class="nv-button nv-button--primary nv-button--lg" href="releases/schos.iso" download>Download the ISO</a>
+      <a class="nv-button nv-button--primary nv-button--lg" href="https://pandor.pl/git/nexoniarz/SchOS/releases">Download the ISO</a>
       <a class="nv-button nv-button--lg" href="#build">Build it yourself</a>
     </div>
 
     <p class="nv-caption">
-      <code class="nv-code">schos.iso</code> · about 62 MB · UEFI x86-64 ·
-      nothing is written to your disks
+      <code class="nv-code">schos.iso</code> · a few hundred MB · UEFI x86-64 ·
+      nothing is written to your disks · only the newest release keeps its ISO
     </p>
   </div>
 
-  <!-- The support table. Deliberately not a compatibility list: one Chromebox
-       is the entire bare-metal record, and a longer table would be fiction. -->
+  <!-- The support table. Deliberately not a compatibility list: three machines
+       are the entire bare-metal record, and a longer table would be fiction. -->
   <article class="nv-card nv-card--elevated">
     <div class="nv-card__header">
       <div>
         <p class="nv-overline nv-text-tertiary">Before you do</p>
-        <h2 class="nv-card__title">This has booted on exactly one real machine</h2>
+        <h2 class="nv-card__title">This has booted on three real machines</h2>
       </div>
     </div>
     <div class="nv-card__body nv-text-secondary">
       Everything below QEMU is honest reporting rather than a compatibility
       list. SchOS drives real hardware, and it has been run on a very small
-      number of it.
+      number of it — from a USB stick, each time.
     </div>
     <div class="nv-card__body">
       <div class="nv-table-frame">
@@ -103,8 +104,16 @@
               <td class="nv-table__actions"><span class="nv-badge nv-badge--success">boots</span></td>
             </tr>
             <tr>
-              <td>Asus Chromebox <span class="nv-text-tertiary">Guado CN62</span></td>
-              <td class="nv-table__actions"><span class="nv-badge nv-badge--warning">under test</span></td>
+              <td>AMD B550 desktop <span class="nv-text-tertiary">Ryzen 5 4600G</span></td>
+              <td class="nv-table__actions"><span class="nv-badge nv-badge--success">boots</span></td>
+            </tr>
+            <tr>
+              <td>ASUS TUF A15 laptop <span class="nv-text-tertiary">Ryzen, RTL8168H</span></td>
+              <td class="nv-table__actions"><span class="nv-badge nv-badge--warning">boots, network under test</span></td>
+            </tr>
+            <tr>
+              <td>HP all-in-one <span class="nv-text-tertiary">Ivy Bridge, 2012</span></td>
+              <td class="nv-table__actions"><span class="nv-badge nv-badge--success">boots</span></td>
             </tr>
             <tr>
               <td>Anything else</td>
@@ -231,11 +240,10 @@
       <span class="nv-overline nv-text-tertiary">Step three</span>
         <h3 class="nv-steps__title">A shell</h3>
         <p class="nv-steps__text">
-        <code class="nv-code">schinit</code> starts one on the console and a
-        second on <code class="nv-code">tty2</code>.
-        <code class="nv-code">mksh</code> is <code class="nv-code">/bin/sh</code>,
-        with <code class="nv-code">zsh</code> beside it and the real toybox
-        userland behind both.
+        <code class="nv-code">schinit</code> starts one on the console and one on
+        each of the next five terminals. <code class="nv-code">zsh</code> is the login shell,
+        <code class="nv-code">/bin/sh</code> is busybox's, and <code class="nv-code">mksh</code> is
+        the static one recovery uses. Type <code class="nv-code">startx</code> for the desktop.
         </p>
       </div>
     </li>