docs: fix all broken references to 13 deleted docs

Updated references in:
- AGENTS.md (root): AMD-FIRST-INTEGRATION → CONSOLE-TO-KDE, DESKTOP-STACK → CONSOLE-TO-KDE
- docs/AGENTS.md: removed entries for DESKTOP-STACK, QT6-PORT, AMD-FIRST, RELIBC-COMPLETENESS
- docs/README.md: removed AMD-FIRST, QT6-PORT, DESKTOP-STACK references

All now point to CONSOLE-TO-KDE-DESKTOP-PLAN.md v4.0 as single authority.

AGENTS.md

@@ -277,7 +277,7 @@ git reset --hard upstream-redox/master
 
 ## AMD-FIRST INTEGRATION PATH
 
-See `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` for the canonical desktop path plan and `local/docs/AMD-FIRST-INTEGRATION.md` for deeper AMD-specific technical detail.
+See `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` for the canonical desktop path plan.
 
 **Target**: AMD64 bare metal, with AMD and Intel machines treated as equal-priority hardware targets.
 
@@ -350,7 +350,7 @@ All custom work goes in `local/` — see `local/AGENTS.md` for overlay usage.
 - QEMU used for testing (make qemu). VirtualBox also supported
 - The `repo` binary (cookbook CLI) may crash with TUI in non-interactive environments — use `CI=1`
 - No git submodules — external repos managed via recipe source URLs and repo manifests
-- Historical integration report removed (2026-04-16); see `local/docs/DESKTOP-STACK-CURRENT-STATUS.md` for current state
+- Historical integration report removed (2026-04-16); see `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` for current state
 
 ## WARNING POLICY
 

docs/AGENTS.md

@@ -12,10 +12,8 @@ For current Red Bear OS status, also read:
 
 - `docs/README.md` — canonical docs index + status matrix
 - `docs/07-RED-BEAR-OS-IMPLEMENTATION-PLAN.md` — canonical public implementation plan
-- `local/docs/DESKTOP-STACK-CURRENT-STATUS.md` — current desktop stack build/runtime truth
+- `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` — **canonical comprehensive implementation plan** — all current state
 - `local/docs/DRM-MODERNIZATION-EXECUTION-PLAN.md` — current DRM-focused execution plan beneath the canonical desktop path
-- `local/docs/QT6-PORT-STATUS.md` — current Qt/KF6 package-level status
-- `local/docs/AMD-FIRST-INTEGRATION.md` — deeper AMD/graphics technical roadmap, useful detail but not the canonical desktop plan
 - `local/docs/SCRIPT-BEHAVIOR-MATRIX.md` — current script guarantees and non-guarantees
 
 ## STRUCTURE
@@ -40,11 +38,9 @@ docs/
 | Which docs are current vs historical? | README | Document Status Matrix |
 | What is the current WIP ownership policy? | `local/docs/RELIBC-COMPLETENESS-AND-ENHANCEMENT-PLAN.md` | Phase R1 |
 | What do the main sync/fetch/apply/build scripts actually guarantee? | local/docs/SCRIPT-BEHAVIOR-MATRIX.md | Entire document |
+| What is the current desktop-stack truth? | `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` | Entire document |
 | What is the current Wi-Fi architecture and validation path? | local/docs/WIFI-IMPLEMENTATION-PLAN.md | Entire document |
-| What is the current desktop-stack truth? | local/docs/DESKTOP-STACK-CURRENT-STATUS.md | Entire document |
-| What is the current Qt/KF6 status? | local/docs/QT6-PORT-STATUS.md | Entire document |
 | What's missing for Wayland? | local/docs/WAYLAND-IMPLEMENTATION-PLAN.md | Entire document |
-| How to fix POSIX gaps? | local/docs/RELIBC-COMPLETENESS-AND-ENHANCEMENT-PLAN.md | Current relibc completeness work |
 | What is the current Wayland plan? | local/docs/WAYLAND-IMPLEMENTATION-PLAN.md | Entire document |
 | How to run Linux GPU drivers? | 04 | Architecture diagram, i915 porting example |
 | What is redox-driver-sys? | 04 | Crate 1: memory, IRQ, PCI, DMA wrappers |

docs/README.md

@@ -14,13 +14,13 @@ current/canonical versus historical/reference split obvious.
 > **Status note (2026-04-14):** several documents below are historical implementation plans whose
 > original "missing / not started" language is now stale. The repo already contains substantial
 > Red Bear OS work under `local/`; use each document's top-level status notes together with
-> `local/docs/AMD-FIRST-INTEGRATION.md` and `local/docs/QT6-PORT-STATUS.md` for current state.
+> `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` (v4.0) for current state.
 
 > **Red Bear note:** newer subsystem plans can also live under `local/docs/` when they are Red Bear-
 > specific rather than general Redox architecture material. In particular, see
 > `local/docs/WIFI-IMPLEMENTATION-PLAN.md` for the current Wi-Fi direction,
 > `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` for the canonical desktop path,
-> and `local/docs/AMD-FIRST-INTEGRATION.md` for AMD-specific technical detail only.
+> and `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` for the canonical desktop path.
 
 > **Repository model:** RedBearOS relates to Redox in the same way Ubuntu relates to Debian.
 > Upstream Redox remains the base platform; Red Bear carries packaging, patch, validation, and
@@ -97,8 +97,8 @@ Do not flatten those into one “supported” claim in public summaries.
 This summary is only a quick orientation layer. For canonical current-state detail, prefer:
 
 - `docs/07-RED-BEAR-OS-IMPLEMENTATION-PLAN.md` for repository-wide execution order,
-- `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` for the canonical desktop path from console to KDE Plasma on Wayland,
-- `local/docs/DESKTOP-STACK-CURRENT-STATUS.md` for desktop build/runtime truth,
+- `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` for the canonical comprehensive plan,
+- `local/docs/PROFILE-MATRIX.md` for support-language by tracked profile,
 - `local/docs/PROFILE-MATRIX.md` for support-language by tracked profile,
 - and the active subsystem plans under `local/docs/` for detailed current workstreams.