docs: the tree moved and the documentation did not

The site and several documents still described the system as it was before
virtual terminals, the new schinit, the hybrid work and descriptor passing.

docs/architecture/init.md described the wrong program. It documented a single
schinit that parses manifests and supervises jobs, which has not been true since
PID 1 was split: PID 1 forks a supervisor, spawns jobs on its behalf and reaps;
the job table lives in /proc/schinit; a heartbeat runs both ways; and
proc_reincarnate() re-execs PID 1 in place rather than panicking. Rewritten
around what exists, keeping the reasoning that is still load-bearing -- the five
failures of the sibling-init scheme, the escalation ladder, and the three bugs in
the reincarnation path that each had to happen before they were obvious.

docs/plan/init.md is deleted, which is the tree's own rule for finished work and
had not been applied. Fourteen source comments referenced it by part number, so
they are repointed at the architecture doc by section name rather than left
dangling -- a deleted document nobody notices is worse than a stale one.

docs/architecture/devices.md gained the section it has been missing since
/dev/pci existed: what a driver needs from a kernel, why mmap is checked against
the caller's claims, why DMA is a call and not a mapping, and why the write back
after an interrupt is not optional. Also that a released device does not come
back by itself, which is true and was nowhere.

docs/architecture/networking.md gained a descriptor-passing section, and
docs/architecture/README.md's stack diagram gained the two layers and the third
seam it was missing. "Two seams hold the whole thing together" has not been true
since /dev/pci.

docs/plan/README.md said the hybrid work was deliberately last, on the argument
that an interface with no consumer is wrong in ways nobody can see. The argument
was right; the conclusion was not, and the document now says why it changed --
the alternative to a driver compatibility layer is writing a driver for every
device that exists, and the original objection is answered rather than ignored
because SchOS's own drivers are the consumers.

The site: a Hybrid section with the eviction transcript, cards for virtual
terminals, schinit and drivers outside the kernel, and the numbers remeasured
rather than estimated -- 46,961 lines, 207 syscalls. The boot log in app.js is
from a boot taken today, and the lines are trimmed to what the console can show
without clipping, each still a verbatim prefix of real output.

Two small rendering fixes found by looking at the pages rather than assuming:
.console pre's min-height is now scoped to the hero, so a static transcript sizes
to its content instead of reserving eight lines it does not have; and the docs
reader's contents panel strips inline marks from headings, so a heading written
`proc_reincarnate()` no longer carries its backticks into the sidebar.

Every intra-doc link checked; none broken.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VQ7Qx8E1q1M1bbCq8QLHS2

docs/plan/roadmap.md

@@ -25,9 +25,10 @@ would most enlarge what SchOS can boot from.
 ## 2. Graphics
 
 - **A `/dev/dri`-style device with mode setting**, so resolution stops being
-  whatever the loader asked for. Worth doing *with*
-  [hybrid.md](hybrid.md)'s GPU eviction rather than before it — moving the driver
-  out is what makes a modeset API affordable to design properly.
+  whatever the loader asked for. This was to be done *with*
+  [hybrid.md](hybrid.md)'s GPU eviction, and that eviction has now happened —
+  `cmd/vgpud` drives virtio-gpu from userspace. The modeset API is the next thing
+  it makes affordable, and is milestone H3 over there rather than here.
 - **Double buffering and vblank.** `display_ops` specifies both and no driver
   implements either. Schcom needs both to not tear.
 - **Port the console onto the text layer and delete the cell grid.** The layer
@@ -43,7 +44,7 @@ belongs to the GUI.
 
 ## 3. Networking
 
-Three things the stack owed on the day it landed, all still owed:
+Two things the stack owed on the day it landed, both still owed:
 
 - **`accept()` does not report the peer's address**, and there is no
   `getsockname`/`getpeername`. Nothing has needed them yet; a server that wants
@@ -52,8 +53,11 @@ Three things the stack owed on the day it landed, all still owed:
   and the second is reachable only by an address on its own subnet. That is a
   rule rather than an accident, and it is not routing.
 
-`setsockopt` returning 0 for everything is in
-[foundations.md](foundations.md) instead, because the Wayland work needs it.
+Two that were on this list are now done and described in
+[../architecture/networking.md](../architecture/networking.md): `setsockopt`
+honours six options and refuses the rest, and `sendmsg`/`recvmsg` carry
+`SCM_RIGHTS`. A third is closer than it was — toybox's `ping` needed `recvmsg`
+*and* `IP_RECVTTL`, and only the second is still missing.
 
 ## 4. The interactive crash screen
 
@@ -159,11 +163,13 @@ Not phases, and each one improves everything above it:
   and sufficient for the GUI.
 - **Symlinks in procfs**, so `/proc/<pid>/exe` can be one and `ps -o comm` stops
   printing `[init]`. Belongs with the rest of the VFS work rather than on its own.
-- **The `ls -lR` hang.** Heavy directory listing across many commands in one long
-  shell session eventually makes a *later*, unrelated directory hang; the same
-  command succeeds on a fresh boot. Not inode or file table exhaustion — both
-  fail cleanly and neither fired. Next step: instrument `itable`/`ftable`
-  occupancy across a long session and watch what climbs.
+- **The `ls -lR` hang** — **not reproducible**, and kept here because the absence
+  of a result is a result. Instrumented and hunted at length; see Gate 0 of
+  [1.0.md](1.0.md). Two real defects were found on the way and fixed, neither
+  proven to be the cause.
+- **No garbage collector for descriptors in flight.** An `AF_UNIX` socket passed
+  over itself and never received leaks the pair. Bounded at thirty-two sockets,
+  and nothing in the tree does it — but a third-party program could.
 
 ---