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

cmd/schdbgd/main.c

@@ -44,16 +44,16 @@
 // register, and arming one is a fine thing for a debugger to do and not a thing
 // for a stranger on a socket to do. The refusal is in the kernel, driven by the
 // view's own registration, so it cannot be got round from here and does not go
-// stale when a new view is added. See include/dbg.h.
+// stale when a new view is added. See include/core/dbg.h.
 //
 // One connection at a time, because /dev/dbg holds one answer at a time: two
 // clients would read each other's. A second caller waits rather than
 // interleaving.
 
-#include "types.h"
-#include "user.h"
-#include "fcntl.h"
-#include "socket.h"
+#include "core/types.h"
+#include "uapi/user.h"
+#include "uapi/fcntl.h"
+#include "net/socket.h"
 
 #define DEFAULT_PORT 4444