The small-kernel track says what is done, what is left, and in which order

issues/the-guest-suite-runs-only-what-no-cheaper-tier-reaches.md

@@ -115,10 +115,13 @@ and NVMe. Exit: as stage A.
   protocol, its restart, and its refusals with no controller.
 - host `nvme_large_device`, `nvme_wide_sector`: a device past 2 TiB and an 8 KiB namespace.
 - host `fsd_two_data`: two DATA partitions are refused by name.
-- metal `fsd_restart`, `fsd_end_at_mount`, `fsd_claim_held`: a file server ended under its
-  clients is restarted, or refused while its claim is held.
-- metal `home_overwrite_reads_back`, `apps_and_home_are_one_filesystem`, `layout_fresh_boot`:
-  `/home`'s bytes and layout on the disk.
+- `fsd_restart`, `fsd_end_at_mount` and `fsd_claim_held` are out under #890. Of
+  `issues/the-kernel-is-small-interrupts-post-and-threads-wait.md`, stage 3's module tests hold
+  the bytes a file server ended under its clients had flushed, and stage 4 owes the client's
+  `Gone` and reconnect, and the supervisor's restart, its bound and its refusal by name of a
+  restart whose claim is held, as module tests. The kernel's `AlreadyExists` on a held partition
+  is `partition_claim`'s.
+- metal `layout_fresh_boot`: `/home`'s layout on the disk.
 - metal `pkg_install_gbae`: `pkg install` lands a package that runs.
 - metal `partition_claim`: a partition claimed as a device, and its refusals.
 - metal `kernel_log_file`, `log_partition_layout`, `log_partition_identity`: `/log` on the stick

issues/the-kernel-depends-on-toyos-fat32-and-uses-none-of-it.md

@@ -0,0 +1,23 @@
+---
+status: open
+kind: defect
+opened: 2026-10-12
+---
+
+# The kernel depends on toyos-fat32 and uses none of it
+
+`kernel/Cargo.toml` lists `toyos-fat32` among the binary's dependencies
+(`[target.'cfg(target_os = "none")'.dependencies]`), and no kernel source
+names it: `git grep -n fat32 -- kernel` finds that manifest line alone, and
+the kernel crate includes no file from outside `kernel/`. Its last user, the
+kernel's FAT adapter, went in #536 and the edge stayed, so every kernel build
+compiles a FAT32 driver it never calls. Three comments still say the kernel
+uses it: `lib/fat32/Cargo.toml`'s header (the kernel depends on it by path),
+`build/fatformat.rs`'s module doc ("the kernel's driver") and `populate`'s
+doc in `build/image.rs` ("the driver the kernel appends `kernel.log` with").
+
+**Exit**: `git grep -n fat32 -- kernel` finds nothing, the root `Cargo.lock`
+lists no `toyos-fat32` among `kernel`'s dependencies, none of the three
+comments names the kernel, and `cargo run -- --build-only` exits 0.
+
+Owner: the orchestrator, which dispatches it.