freeze: one register for everything half-built, and the corners cleared

The failure this is against is not scope creep. It is abandonment by promotion:
a thing gets built to the point where it works, the next thing becomes more
interesting, and the first is left in a corner -- in the tree, not finished, not
deleted, and not in any list. Enough of those and the tree stops matching its
own documentation.

docs/plan/1.0.md now holds the register, and it is the only place anything
half-built is listed. Four sections, because the kinds are genuinely different:
built and connected to nothing (the text layer, a font from disk, socket
activation, wait_vblank); started and stopped part-way (foundations 2-5, hybrid
H2, Schcom v0, a released PCI device that nothing brings back); named in a "what
it does not do" and still true; and frozen -- scoped, unstarted, not to be
started. The rule is that nothing enters except by being finished or deleted,
and that adding a row requires closing one.

1.0.md already said "two things in flight, never three". It was right and it was
not being followed.

Then the corners themselves, because a register written over a tree full of them
is just a longer list:

  - cmd/init is deleted. Nothing had execed /bin/init since initcode.S changed
    to /bin/schinit; it was built and installed on every image as an unreachable
    fallback, and an unreachable fallback rots rather than saves.
  - projects/schwm/ and projects/schde/ are deleted. Both said "to be deleted"
    in their own first paragraph, which proves only that a directory marked for
    deletion is not deleted by being marked. README-only, no code lost, and the
    arguments each made are moved into wayland.md where they are still true.
  - projects/schcom/schcom and schcom-demo were tracked binaries. Untracked, and
    .gitignore'd.

Three code comments and one document described a boot that has not happened
since 7d44eb7. cons_serial_only starts set, but kmain clears it on its first
lines now, so the splash does not survive the boot and the kernel log is on
screen from the start. That reversal was earned by a Chromebox with no serial
port freezing at boot showing nothing at all, and the comments still argued the
losing side of it.

The site:

  - a download page. One ISO, what it has actually been run on -- one machine,
    under test -- Ventoy and dd, what the first boot looks like step by step,
    and the build if you would rather. The support table names one Chromebox
    rather than listing hardware, because one Chromebox is the entire bare-metal
    record and a list would be fiction.
  - Assets/usb.svg, drawn to the same rule as the other marks: two tones,
    geometry only, the accent spent in one place, and that place is the activity
    light because it is the part that tells you something is happening.
  - Download is in both navs and is the hero's primary action; a closing band
    ends the front page on it.
  - the uberblock-slots and drivers-outside-the-kernel figures are gone. Three
    numbers left, including the fastfetch one, which stays because it is funny.

Two things caught by rendering the pages instead of assuming: .hero p was
beating .filemeta on specificity and the file line was coming out at body size,
and the dd command was one line long enough that the card clipped it at `conv=`
-- a destructive command that can scroll half of itself out of view is a good
way to take somebody's disk. It is two lines now.

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

docs/plan/1.0.md

@@ -54,6 +54,83 @@ currently either broken, missing, or unproven.
 
 ---
 
+## The freeze, and the register of unfinished work
+
+**No new capability is started until this register is empty.**
+
+The failure this exists to stop is not laziness and not scope creep — it is
+*abandonment by promotion*. A thing gets built to the point where it works, the
+next thing becomes more interesting, and the first one is left in a corner:
+present in the tree, not finished, not deleted, and not visible in any list.
+Enough of those and the tree stops matching its own documentation, which is the
+state this register was written to end.
+
+Two rules, and they are the same rule seen from either end:
+
+> **Nothing enters the register except by being finished or being deleted.**
+>
+> **Adding a row requires closing one.** Two things in flight. Never three.
+
+A row leaves this table in one of exactly two ways. Either it is **finished** —
+and finished means a description exists in [../architecture/](../architecture/),
+not that the code works — or it is **deleted**, and deleted means gone from the
+tree, not marked for deletion. A directory that has said "to be deleted" for
+months is the corner, not the cure; `projects/schwm/` and `projects/schde/`
+proved that and are now actually gone.
+
+### Built, and not connected to anything
+
+The galling ones. The work exists, is tested, and nothing uses it.
+
+| | Where it stopped |
+|---|---|
+| **The text layer** | `kernel/dev/text.c` and `kernel/dev/ttf.c` are 850 lines that rasterise TrueType and draw at any pixel position. The console still indexes `font_data[256][16]`. The only caller is a self-test. |
+| **A font from disk** | Same layer, same reason. The console's 8×16 CP437 grid is compiled in. |
+| **Socket activation** | `schinitd` parses `[Socket name]` and remembers the path. Nothing holds the socket. **This is the entire reason for copying launchd**, and it is the half that was not built. |
+| **`display_ops.wait_vblank`** | In the vtable, implemented by the VBE driver, left null by virtio-gpu. A compositor that needs it cannot rely on it. |
+
+### Started, and stopped part-way
+
+| | Where it stopped |
+|---|---|
+| **`foundations.md`** | Item 1 built. Items 2 (a shareable memory object), 3 (`AF_UNIX` in the filesystem namespace), 4 and 5 open. **Wayland stops at item 2.** |
+| **`hybrid.md`** | All four mechanisms built, H1 done. **H2 — kill the driver on purpose and watch it come back — is the milestone the plan itself calls the one that proves the whole idea**, and it is not done. |
+| **Schcom v0** | 715 lines that composite, over a wire format that is superseded. Frozen: it runs, nothing more is added, and it is kept only because it is the one thing in the tree that has ever put a client's pixels on screen. |
+| **A released PCI device** | `PCIIOC_RELEASE` leaves the line masked and the in-kernel driver unbound. Nothing starts a replacement. Half a handover. |
+
+### Named in a "what it does not do" and still true
+
+Not corners — these were written down honestly on the day and stayed written
+down. They are here so the register is the whole picture rather than the
+flattering part of it.
+
+| | |
+|---|---|
+| `/proc/<pid>/exe` is a regular file | so `readlink()` fails and `ps -o comm` prints `[init]` |
+| `getrusage` | does not distinguish `RUSAGE_CHILDREN` from `RUSAGE_SELF` |
+| No slab allocator | every subsystem's fixed-size table is a consequence |
+| No `getsockname`/`getpeername` | and `accept()` does not report an AF_INET peer |
+| No routing table | first interface wins, which is a rule and not routing |
+| No descriptor garbage collector | a socket passed over itself and never received leaks the pair |
+
+### Frozen — scoped, unstarted, and not to be started
+
+Neither cancelled nor in progress. **Do not open these.**
+
+| | |
+|---|---|
+| `projects/schinst/` | the installer, the installation environment, `.sip` |
+| `projects/schfs-linux/` | SchFS as a filesystem for Linux |
+| [roadmap.md](roadmap.md) §4 | the interactive crash screen |
+| [roadmap.md](roadmap.md) §6 | SchFS beyond SchOS |
+| [schapi.md](schapi.md) | the API layering, designed and not built |
+
+Each of those is well argued and none of them is on the path to the acceptance
+test above. That is the whole test for whether something belongs in this section:
+**not "is it worth doing" but "does 1.0 fail without it".**
+
+---
+
 ## The four gates
 
 In order. **Do not start a gate before the one before it closes**, and closing

docs/plan/README.md

@@ -9,6 +9,11 @@ leaves — deleted from here, rewritten as a description in
 > It draws a finish line and puts most of the work below on the far side of it.
 > **Anything not named there is not being worked on**, and the documents in this
 > directory describe more than 1.0 contains.
+>
+> It also holds **[the register of unfinished work](1.0.md#the-freeze-and-the-register-of-unfinished-work)**,
+> which is the one place anything half-built is listed. No new capability starts
+> until that register is empty, and a row leaves it only by being finished or by
+> being deleted from the tree.
 
 ---
 
@@ -18,7 +23,7 @@ Taken together, because they turn out to need the same foundation.
 
 | | |
 |---|---|
-| **[wayland.md](wayland.md)** | The GUI stack becomes Wayland. SchWM and SchDE are deleted; Schcom survives and changes its wire format. |
+| **[wayland.md](wayland.md)** | The GUI stack becomes Wayland. SchWM and SchDE are **deleted** — actually gone from the tree, not marked; Schcom survives and changes its wire format. |
 | **[hybrid.md](hybrid.md)** | The kernel becomes hybrid — drivers move out into userspace processes, starting with the GPU. **Partly built**: all four mechanisms exist and the GPU driver already runs outside the kernel. |
 | ~~init.md~~ | **Built.** PID 1 is now a role the kernel refills; the description moved to [../architecture/init.md](../architecture/init.md). |
 

docs/plan/schapi.md

@@ -54,7 +54,7 @@ So, for SchOS:
 
 ```
     ┌──────────────────────────────────────────────┐
-    │  applications, SchWM, SchDE                  │
+    │  applications, Schcom and its clients        │
     ├──────────────────────────────────────────────┤
     │  SchAPI          │  POSIX / Linux personality│   ← THE STABLE BOUNDARY
     ├──────────────────┴───────────────────────────┤

docs/plan/wayland.md

@@ -3,13 +3,18 @@
 Schcom survives and changes its wire format. SchWM and SchDE are deleted. What
 follows is why that is not a retreat, and what it costs.
 
-Blocked on [foundations.md](foundations.md), items 1–4.
+Blocked on [foundations.md](foundations.md), items 1–4. **Item 1 is built** —
+descriptor passing, without which no Wayland client can hand over a buffer. Item
+2, a shareable memory object, is the next thing it stops at.
 
 ---
 
-## What is deleted
+## What was deleted
 
-`projects/schwm/` and `projects/schde/`. Both are README-only; no code is lost.
+`projects/schwm/` and `projects/schde/`, both README-only; no code was lost. They
+are **gone from the tree now** rather than marked for deletion — a directory that
+has said "to be deleted" for months is a corner, not a decision. The arguments
+each made are kept below, because they are the part worth keeping.
 
 ### SchWM is not abandoned — Wayland dissolves it
 
@@ -19,7 +24,7 @@ that the compositor *is* the window manager**: there is no protocol by which a
 second process places another's windows, and every attempt to add one has been a
 private extension.
 
-So the argument in `projects/schwm/README.md` —
+So SchWM's own argument —
 
 > *"Compositing is mechanical and must never stall: it runs every frame and a
 > mistake there is a frozen screen. Window management is policy, full of special
@@ -31,11 +36,15 @@ Schcom**, not a process boundary: policy in its own file behind its own
 interface. Do not keep it in its own process, because the protocol to talk to it
 does not exist.
 
-### SchDE is re-sited rather than deleted
+### SchDE is re-sited rather than abandoned
 
 A panel, a launcher and a wallpaper are ordinary Wayland clients using
 `wlr-layer-shell` — MIT, an XML file, no dependency. They need no directory of
-their own until one of them is written.
+their own until one of them is written. SchDE's other observation stands on its
+own and is recorded here so it does not go with the directory: **a GUI terminal
+is not the kernel console with a window around it.** The console parses ANSI
+because it draws straight to the framebuffer; a terminal client parses ANSI
+itself and renders it with proportional-capable text. The two share no code.
 
 ### `projects/schinst/` stays