include: one folder per subsystem, and includes that name it

Sixty-five headers sat side by side in include/, so `#include "irq.h"`
said nothing about where irq.h was or what it belonged to, and errno.h,
stat.h and fcntl.h at the top shadowed the system's for any host tool
built with -I./include. They are in folders now -- arch/ core/ fs/
dev/ gfx/ net/ uapi/ (and ldls/ for the Linux driver layer) -- and
every include names the folder, as Linux's do: "core/proc.h".

Done mechanically and checked the hard way: the kernel built from this
tree disassembles identically to the one built from the tree before
it. The full image boots, and userland is the same set of programs.
Paths in docs and comments follow; docs/guides/layout.md has a table
of what is where, and tools/fix-includes.py rewrites old-style
includes from the folders in the tree, for code written before this.

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

.claude/memory/schunix-framebuffer-device.md

@@ -10,10 +10,10 @@ metadata:
 
 **`/dev/fb0` (major 2) is a real framebuffer device** as of 2026-08-04:
 `kernel/dev/fb.c` (read/write by byte offset, plus `fb_ioctl`), declared in
-`include/fb.h`. Before this it was wired to `{ nullread, nullwrite }` — writing
+`include/gfx/fb.h`. Before this it was wired to `{ nullread, nullwrite }` — writing
 pixels to it succeeded and did nothing.
 
-**`include/fb.h` holds Linux's fbdev request numbers and struct layouts**
+**`include/gfx/fb.h` holds Linux's fbdev request numbers and struct layouts**
 (`FBIOGET_VSCREENINFO` 0x4600, `fb_var_screeninfo` 160 bytes,
 `fb_fix_screeninfo` 80 bytes). Same reasoning as
 [[schunix-linux-open-flags]]: a shared number must mean the shared thing, or a