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/1.0.md

@@ -237,14 +237,32 @@ memory object, `AF_UNIX` in the filesystem namespace.
 
 Nothing above needs these; everything below stops without them.
 
-### Gate 2 — Init as a role
+- [x] ~~**Item 1 — `sendmsg`/`recvmsg` with `SCM_RIGHTS`.**~~ Built and tested;
+      fourteen checks in `cmd/socktest`, each moving data through the passed
+      descriptor rather than inspecting it. Described in
+      [../architecture/networking.md](../architecture/networking.md#descriptor-passing).
+      This was also mechanism 1 of [hybrid.md](hybrid.md) — one primitive for
+      both, which is the whole reason those are one plan.
+- [ ] **Item 2 — a shareable memory object** (`memfd_create`, and
+      `mmap(MAP_SHARED)` on it genuinely working between two processes). This is
+      what a Wayland buffer still cannot cross on.
+- [ ] **Item 3 — `AF_UNIX` sockets in the filesystem namespace.**
 
-[init.md](init.md), milestones I0–I3.
+### Gate 2 — Init as a role — **done**
+
+Milestones I0–I3, all built. PID 1 forks a supervisor and spawns jobs on its
+behalf; the job table lives in `/proc/schinit`; a heartbeat runs both ways; and
+`proc_reincarnate()` re-execs PID 1 in place rather than panicking. Both failure
+paths are exercised by `sysrq` keys rather than reasoned about.
 
 Before the desktop rather than after, because a compositor being brought up for
 the first time crashes constantly, and something that restarts it and says why is
 worth far more during that work than at the end of it.
 
+The description is now [../architecture/init.md](../architecture/init.md); the
+plan document it replaced has been deleted, per
+[the rule](../README.md#the-rule-that-keeps-this-from-rotting).
+
 ### Gate 3 — The desktop
 
 [wayland.md](wayland.md), W1–W3, and the terminal.
@@ -261,7 +279,7 @@ attention. Nothing here is cancelled.
 
 | | Why it waits |
 |---|---|
-| **The hybrid kernel** ([hybrid.md](hybrid.md)) | An architecture improvement, not a completeness requirement. It is also the work that most wants a demanding consumer first, and 1.0's compositor is exactly that consumer. |
+| **The rest of the hybrid kernel** ([hybrid.md](hybrid.md)) | Still not a completeness requirement — but the mechanisms and the first eviction happened early, because the alternative to a driver compatibility layer is writing a driver for every device that exists, and that is not a plan. What is deferred is the foreign driver host, not the interface it needs. |
 | **Dynamic linking, Mesa, SDL3** | Everything at 1.0 is statically linked. This is the single biggest post-1.0 unlock and it is a whole project. |
 | **A page cache** | `memfd` covers the desktop's needs. General writable `MAP_SHARED` of a file is a real project with no 1.0 consumer. |
 | **`.sip` and the installer** | 1.0 installs by writing a USB stick. That is how most systems start and it is honest. |