docs: round 4 — Qt 6.11.1 upgrade + durability correction (qtbase pristine)

local/docs/REDBEAR-FULL-SDDM-BRINGUP.md

@@ -113,3 +113,21 @@ the tracked recipe (durable):
      Vulkan; Vulkan WSI was the only consumer) + collision-proof define.
 Next: full build assembles the ISO (mesa cached, + driver-manager [operator WIP]
 + redox-drm/qt/kwin/sddm) → boot QEMU virtio-gpu → SDDM prompt.
+
+### Round 4 (2026-07-24) — Qt 6.11.1 upgrade + durability correction
+- **Durability correction:** diffed committed qtbase source vs pristine 6.11.0 →
+  BYTE-IDENTICAL (0 changed files). qtbase has NO in-place fixes; it simply never
+  built before (no pkgar). Its Redox fixes are all in redox.patch (durable). The
+  earlier "lost in-place fixes" alarm was a MISDIAGNOSIS — re-fetching 6.11.1 is
+  safe. All session porting fixes go into durable patches in local/.
+- **Qt version:** recipes are tar=6.11.1 (operator intent); committed source was
+  stale 6.11.0 (never re-fetched after the bump). Correct path = 6.11.1 for all
+  modules + fixes as patches. Re-fetching 6.11.1 (safe, verified).
+- **Durable patches so far:** mesa (5 fixes, recipe+patch08), qtbase
+  redox-in6-pktinfo.patch (recipe dir), qtsvg CVE patch reference fixed.
+- **Next 6.11.1 gap:** forkfd_wait4 conflicting types (a 6.11.1 header change vs
+  6.11.0; forkfd.c itself identical) — to fix as a durable patch.
+- **Build-system deficiency noted:** Qt source is committed in-tree (22k files/mod)
+  yet re-fetch overwrites it — the durable truth should be recipe(tar+blake3)+patches,
+  source gitignored. Flagged for operator (repo restructure).
+- **ISO blocker (not mine):** operator's driver-manager/redox-driver-sys WIP.