Refresh project documentation

Ultraworked with [Sisyphus](https://github.com/code-yeongyu/oh-my-openagent)

Co-authored-by: Sisyphus <clio-agent@sisyphuslabs.ai>

docs/04-LINUX-DRIVER-COMPAT.md

@@ -34,7 +34,7 @@ The tree now also contains comprehensive wireless-subsystem compatibility inside
 `sk_buff` with queue operations, `net_device` with NAPI and queue state, `cfg80211` / `wiphy` with
 scan/connect/disconnect/BSS events, `mac80211` with `ieee80211_ops` callback mechanism, channel/
 band/rate/BSS definitions, PCI MSI/MSI-X support, DMA pool allocation, `list_head`, full `atomic_t`,
-and IO barrier/copy helpers — all compile- and host-test-validated (90 tests pass). This should still
+and IO barrier/copy helpers — all compile- and host-test-validated (93 tests pass). This should still
 be read as comprehensive compatibility work, not as proof that Red Bear now has working Intel Wi‑Fi
 connectivity.
 
@@ -59,7 +59,7 @@ Concrete repo entry points for that current bounded Wi‑Fi path are:
   architecture and operator validation path
 
 The validation claim here should also be read narrowly: the repo now has a clean host-side
-`linux-kpi` test suite (90 tests pass), passing comprehensive PCIe transport tests in the
+`linux-kpi` test suite (93 tests pass), passing comprehensive PCIe transport tests in the
 dependent crates (DMA pool, MSI-X, ieee80211_ops, skb queue, NAPI, list_head, atomic_t,
 completion timeout, IO barriers), and the iwlwifi transport builds and passes its host-side
 test suite (8 tests). This is not a claim that a full Linux Wi‑Fi stack is validated on hardware.

docs/07-RED-BEAR-OS-IMPLEMENTATION-PLAN.md

@@ -333,6 +333,9 @@ Current state:
 - packaged in-target Wi-Fi validation/capture commands now exist for the current bounded Intel path
   (`redbear-phase5-wifi-check`, `redbear-phase5-wifi-link-check`, `redbear-phase5-wifi-capture`,
   `redbear-phase5-wifi-run`, `redbear-phase5-wifi-analyze`),
+- the separate `redbear-phase5-network-check` / `test-phase5-network-qemu.sh` path on `redbear-full`
+  now proves bounded desktop/network plumbing in QEMU and should not be confused with the Wi-Fi
+  plan's later real-hardware Phase W5 completion criteria,
 - real hardware scan/auth/association/data-path proof is still missing,
 - `linux-kpi` is still not the Wi-Fi architecture by itself.
 

docs/README.md

@@ -102,10 +102,11 @@ This summary is only a quick orientation layer. For canonical current-state deta
 - **Input**: evdevd compiled, libevdev built, libinput 1.30.2 built
 - **Networking**: native wired stack present (`pcid-spawner` → NIC daemon → `smolnetd`/`dhcpd`/`netcfg`), Red Bear ships a native `netctl` command, RTL8125 is wired into the existing Realtek autoload path, and the bounded Intel Wi‑Fi path now has host-tested profile start/stop plus interface-specific DHCP handoff without claiming real wireless connectivity.
 - **Wi-Fi profile target**: `config/redbear-wifi-experimental.toml` is the first explicit tracked image slice for bounded Intel Wi‑Fi validation, instead of spreading that claim across the generic desktop profiles.
-- **Bluetooth**: one bounded in-tree BLE-first experimental slice exists, and the Battery Level read-only workload is now QEMU-validated through a packaged in-guest checker plus a host harness; broad desktop Bluetooth parity is still incomplete
+- **Bluetooth**: one bounded in-tree BLE-first experimental slice exists, and the Battery Level read-only workload now has a packaged in-guest checker plus a host QEMU harness; QEMU validation is still in progress, so broad desktop Bluetooth parity is still incomplete
 - **KDE**: `redbear-kde.toml` exists and the recipe tree is populated, but the runtime stack is still incomplete.
 - **Linux driver compat**: linux-kpi now includes early wireless-subsystem compatibility scaffolding in addition to the earlier helper layer, redox-driver-sys and firmware-loader compile, and the bounded Intel Wi-Fi path now has host-tested scan/connect/disconnect/profile/reporting flows without claiming real hardware Wi-Fi connectivity.
 - **Wi-Fi validation tooling**: `redbear-phase5-wifi-check` and `redbear-phase5-wifi-capture` are now packaged in-guest helpers for bounded Intel Wi-Fi runtime validation and evidence capture on bare metal or VFIO-backed guests.
+- **Phase 5 naming note**: the bounded `redbear-phase5-network-check` / `test-phase5-network-qemu.sh` path proves desktop/network plumbing on `redbear-full` in QEMU; it does **not** mean the Wi-Fi implementation plan's later Phase W5 real-hardware reporting/recovery milestone is complete.
 
 ## Quick Start