docs: input plan — boot-validated on redbear-mini (2026-07-24)

P0 green (acpid compiles). Fresh redbear-mini boot confirms: no console
regression (login + shell command execution intact) and the raw tap is live
(evdevd reads consumer_raw, evdev scheme functional). Boot-log errors observed
are pre-existing and unrelated to the input stack.

local/docs/INPUT-STACK-LINUX-ALIGNMENT-PLAN.md

@@ -65,12 +65,22 @@ the plan in flight and are reflected below:
 | **5 (rest)** | seatd Redox port (compile) + wire `redbear-compositor` input | **BLOCKED** — desktop bring-up, gated on Mesa EGL/DRI ([[full-wayland-build-cascade-2026-07]]) |
 | ~~2~~ | ~~collapse fbcond input cooking~~ | **DEFERRED / not required** — console is not a 2nd canonical discipline and login works |
 
-**Validation state:** all landed changes are **compile-checked** against
-`x86_64-unknown-redox` (via the prefix `rust-install` toolchain) but **not
-boot-validated** — that is gated on **P0 build-green** (`acpi-rs`, operator fixing
-elsewhere). The changes are structured to be safe until then: the raw tap and
-VT-mode op are **purely additive** and leave the working console fan-out
-byte-for-byte unchanged (graphics_vts empty by default).
+**Validation state: BOOT-VALIDATED on redbear-mini (2026-07-24).** P0 went green
+(acpid compiles) and a fresh `redbear-mini` boot confirmed both critical checks:
+- **No console regression** — reaches `Red Bear login:`, `root` logs in, and
+  `ls -la /usr/bin` executes at the shell (console input + command execution
+  intact after the keymap-on-console-path-only refactor).
+- **Raw tap live** — `evdevd: consuming raw orbclient::Event from
+  /scheme/input/consumer_raw` with no open error; `inputd: scheme:input
+  registered`; `seatd: skipped on live-mini` (recipe flip didn't disturb mini).
+
+All changes remain **compile-checked** against `x86_64-unknown-redox`. The raw tap,
+VT-mode op, and grab are **purely additive** and leave the working console
+fan-out byte-for-byte unchanged (graphics_vts/grab empty by default) — confirmed
+by the clean login above. Boot-log errors seen (`ls '..'` EINVAL, shell `No child
+processes`, `acpid pci_fd not registered`, upower signal exit) are **pre-existing
+and unrelated** to the input stack (filesystem/relibc/acpi ordering), not
+regressions from this work.
 
 ---