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

kernel/drivers/gpu/vga/vga_fb.c

@@ -272,7 +272,7 @@ const struct display_ops vga_display_ops = {
 // driver that leaves has to name its replacement rather than simply detaching;
 // detaching alone leaves gfx pointing at a device nobody is driving.
 //
-// This is the fallback rule from docs/plan/hybrid.md made real: the kernel
+// This is the fallback rule from docs/architecture/devices.md made real: the kernel
 // keeps a minimal driver for everything on the path to a shell, so a fancy
 // driver leaving degrades to a working screen instead of to no screen.
 int

kernel/drivers/gpu/virtio_gpu/virtio_gpu.c

@@ -557,7 +557,7 @@ static struct {
 
 // Hand the device to a userspace driver.
 //
-// docs/plan/hybrid.md's first eviction, and the reason it is this device: the
+// docs/architecture/devices.md's first eviction, and the reason it is this device: the
 // boundary already exists (struct display_ops), it has exactly one consumer,
 // and there is a working fallback underneath. So letting go is safe in a way
 // it would not be for the disk the root filesystem is on.
@@ -580,7 +580,7 @@ vgpu_release(struct pci_dev *d)
   if (!g)
     return -1;
 
-  // The rule from docs/plan/hybrid.md, enforced rather than described: **the
+  // The rule from docs/architecture/devices.md, enforced rather than described: **the
   // kernel keeps a minimal driver for everything on the path to a shell.** If
   // there is no framebuffer to fall back to, this device is the only screen the
   // machine has, and handing it to a process that might crash would make a
@@ -645,7 +645,7 @@ vgpu_release(struct pci_dev *d)
 
 // --- the crash screen, on a device this driver was told to let go ----------
 //
-// docs/plan/hybrid.md's bargain has a clause nobody wrote down: a device the
+// docs/architecture/devices.md's bargain has a clause nobody wrote down: a device the
 // kernel hands away is a device the kernel cannot use to tell you the machine
 // died. The second monitor sat there showing a shell prompt from before the
 // panic, which is the most misleading thing a screen can do.

kernel/drivers/net/e1000/e1000.c

@@ -423,7 +423,7 @@ e1000_link_up(struct device *dev)
 
 // Let go of the device, so a userspace driver can have it.
 //
-// The same hook virtio-gpu grew for H1, on a NIC. docs/plan/hybrid.md's rule
+// The same hook virtio-gpu grew for H1, on a NIC. docs/architecture/devices.md's rule
 // is that the kernel keeps a minimal driver for everything on the path to a
 // shell -- and a network interface is not on that path, so this one may leave.
 //