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/architecture/boot.md

@@ -176,24 +176,34 @@ and the reason is worth keeping:
 > constants and touches no disk. SchFS has no constant to offer — the root
 > object id comes off the uberblock — so that early `namei("/")` builds an inode
 > from an unmounted volume. Nothing complains, because absolute paths never
-> consult cwd: `exec("/bin/init")` works fine. It is the first *relative* lookup
+> consult cwd: an absolute `exec` works fine. It is the first *relative* lookup
 > that fails, and in init that is `open("console")`. No console means no fd
 > 0/1/2, so every shell it spawns exits immediately and init respawns it
 > forever. The symptom is a silent boot that reads like a hang and is not one.
 
-`initcode` then execs `/bin/init`, and [init.md](init.md) takes over.
+`initcode` then execs **`/bin/schinit`**, and [init.md](init.md) takes over.
+There is no fallback path and deliberately no `/bin/init` any more: the older
+hardcoded fork-a-shell PID 1 was unreachable from the day that string changed,
+and an unreachable fallback rots rather than saves.
 
 ## 6. What the screen shows
 
-**The display is not the kernel log.** `cons_serial_only` starts *set*: every
-boot message goes out the UART and nothing goes to the framebuffer. The loader's
-splash therefore survives the whole of boot rather than being wiped a few
-hundred milliseconds in, and `console_takeover()` clears the flag on the first
-`exec()`, when userspace genuinely starts.
+**The kernel log is on screen from the first line that can draw.** `kmain`
+attaches the loader's framebuffer and clears `cons_serial_only` before it does
+anything else, so `pci: 7 devices` and `schfs: mounted` are visible on the
+machine itself.
 
-Nothing is lost — the serial line is where `bootcheck` reads from and where you
-want the messages when something is wrong — and the F8 verbose boot never sets
-the flag, so "show me everything" still works.
+This is the reverse of what the flag was added for, and the reversal was earned.
+The original argument was that a boot which prints a developer's log to the
+screen looks like a hobby project, and it is a good argument — right up until a
+Chromebox with **no serial port** froze at boot showing nothing at all. The whole
+diagnosis had to be made from a photograph of a screen that had been told to stay
+quiet. A tidy boot that cannot be debugged on the hardware it fails on is not a
+trade worth making.
+
+`cons_serial_only` still exists for the case it is now the right answer to: no
+framebuffer from the loader. Then everything goes to the UART and
+`console_takeover()` clears the flag when userspace starts.
 
 ---