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-e1000-and-driver-layout.md

@@ -23,7 +23,7 @@ One directory per *driver*, not per class (Nexoniarz asked for this
 specifically), so a driver that grows a register header, a second source file or
 a firmware blob has somewhere to put it.
 
-Matches `DEVCLASS_*` in `include/device.h`. Flat was eight files with four
+Matches `DEVCLASS_*` in `include/dev/device.h`. Flat was eight files with four
 called `usb_something`, and each driver added made it worse.
 
 **Makefile note:** the compile rule is now