Refresh project documentation

Red Bear OS Team

local/docs/PROFILE-MATRIX.md

@@ -23,8 +23,10 @@ USB plan uses:
 | Profile | Intent | Key Fragments | Current support language |
 |---|---|---|---|
 | `redbear-minimal` | Console + storage + wired-network baseline | `minimal.toml`, `redbear-legacy-base.toml`, `redbear-device-services.toml`, `redbear-netctl.toml` | builds / primary validation baseline / DHCP boot profile enabled / input-runtime substrate wired |
+| `redbear-bluetooth-experimental` | First bounded Bluetooth validation profile | `redbear-bluetooth-experimental.toml`, `redbear-minimal.toml` | builds / boots in QEMU / validated bounded Battery Level slice via `redbear-bluetooth-battery-check` and `test-bluetooth-qemu.sh --check` / explicit-startup USB BLE-first only / repeated helper + restart cleanup covered / not generic GATT / not USB-class-autospawn |
+| `redbear-wifi-experimental` | First bounded Intel Wi-Fi validation profile | `redbear-wifi-experimental.toml`, `redbear-device-services.toml`, `redbear-netctl.toml` | builds / experimental bounded Intel Wi-Fi slice / driver + control/profile/reporting stack present / packaged in-target validation and capture commands available / real hardware connectivity still unproven |
 | `redbear-desktop` | Main Red Bear desktop integration profile without KDE-specific session wiring | `desktop.toml`, `redbear-legacy-base.toml`, `redbear-device-services.toml`, `redbear-netctl.toml` | builds / input-runtime substrate wired / runtime reporting installed |
-| `redbear-wayland` | Phase 4 Wayland runtime validation profile | `wayland.toml` | builds / boots in QEMU / experimental graphics-runtime path |
+| `redbear-wayland` | Phase 4 Wayland runtime validation profile | `wayland.toml` | builds / boots in QEMU / experimental software-path graphics-runtime slice / not QEMU hardware-acceleration proof |
 | `redbear-full` | Phase 5 desktop/network plumbing profile | `desktop.toml`, `redbear-legacy-base.toml`, `redbear-legacy-desktop.toml`, `redbear-device-services.toml`, `redbear-netctl.toml` | builds / boots in QEMU / D-Bus system bus wired / experimental runtime path |
 | `redbear-kde` | Phase 6 KDE session-surface profile | `desktop.toml`, `redbear-legacy-base.toml`, `redbear-legacy-desktop.toml`, `redbear-device-services.toml`, `redbear-netctl.toml` | builds / experimental desktop path / D-Bus+seatd+KWin session surface wired |
 | `redbear-live` | Live and recovery image layered on desktop | `redbear-desktop.toml` | builds |
@@ -38,6 +40,29 @@ USB plan uses:
 - Enables the shared `wired-dhcp` netctl profile by default for the Phase 2 VM/wired baseline.
 - Ships the shared firmware/input runtime service prerequisites so the early substrate can be tested on the smallest profile as well.
 
+### `redbear-bluetooth-experimental`
+
+- Standalone tracked profile for the first in-tree Bluetooth slice instead of a blanket claim about
+  all Red Bear images.
+- Extends `redbear-minimal` so the baseline runtime tooling is already present, then adds only the
+  bounded Bluetooth pieces on top.
+- Current verified path: QEMU/UEFI boot to login prompt plus guest-side `redbear-bluetooth-battery-check`, with repeated in-boot reruns, daemon-restart coverage, and one experimental battery-sensor Battery Level read-only workload.
+- Current support language is intentionally narrow: explicit-startup only, USB-attached transport,
+  BLE-first CLI/scheme surface, one experimental battery-sensor Battery Level read-only workload,
+  and no USB-class autospawn claim yet.
+
+### `redbear-wifi-experimental`
+
+- Standalone tracked profile for the current bounded Intel Wi-Fi slice instead of implying that the
+  wider desktop profiles already carry the full driver stack.
+- Extends `redbear-minimal` so the baseline firmware/input/reporting/profile-manager surface stays
+  inherited while the Intel Wi-Fi driver package and bounded validation role remain isolated here.
+- Includes the Intel driver package (`redbear-iwlwifi`) in addition to the shared firmware,
+  control-plane, reporting, and profile-manager pieces.
+- Current support language is intentionally narrow: bounded probe/prepare/init/activate/scan/
+  connect/disconnect lifecycle, packaged in-target validation and capture commands, and no claim yet
+  of validated real AP association or end-to-end Wi-Fi connectivity.
+
 ### `redbear-desktop`
 
 - Carries the standard Red Bear desktop-facing package additions.
@@ -50,6 +75,8 @@ USB plan uses:
 - Wraps the repo's existing `wayland.toml` into a first-class Red Bear build target.
 - Serves as the Phase 4 runtime-validation surface for `orbital-wayland` and `smallvil`.
 - Current verified path: QEMU/UEFI boot to login prompt plus guest-side `redbear-phase4-wayland-check`, with `smallvil` reaching xkbcommon initialization and EGL platform selection on Redox.
+- Current QEMU renderer evidence is still software-based (`llvmpipe` on the current `-vga std` harness), so this profile must not be described as a hardware-accelerated desktop proof yet.
+- Treat this profile as the bounded Phase 4 Wayland/Qt regression harness; the final hardware-desktop claim still belongs to the bare-metal accelerated graphics path.
 
 ### `redbear-full`
 
@@ -68,3 +95,13 @@ USB plan uses:
 
 - Intended for install, demo, and recovery workflows.
 - Should inherit only stable desktop-profile assumptions unless explicitly documented.
+
+## Bluetooth Note
+
+- `redbear-bluetooth-experimental` is now the tracked first Bluetooth-specific profile.
+- Its support language remains experimental and bounded; it should not be used to imply Bluetooth
+  support across the wider Red Bear profile set.
+- The current bounded BLE workload is one read-only battery-sensor Battery Level interaction; this
+  profile still does not claim generic GATT, write, or notify support.
+- The current validation claim is QEMU-scoped and packaged-checker-scoped, not a blanket claim
+  about real hardware Bluetooth maturity.