docs: add Red Bear build flow and config chains

docs/01-REDOX-ARCHITECTURE.md

@@ -233,6 +233,15 @@ Configs are TOML files that include each other:
 
 ```
 wayland.toml → desktop.toml → desktop-minimal.toml → minimal.toml → base.toml
+
+Red Bear include chains (per ground-truth §B):
+  redbear-mini.toml → minimal.toml + base.toml
+                       + redbear-legacy-base.toml
+                       + redbear-netctl.toml
+                       + redbear-device-services.toml
+                       + redbear-boot-stages.toml
+  redbear-full.toml  → redbear-mini.toml (+ graphics/Qt/KDE extends)
+  redbear-grub.toml  → redbear-mini.toml + redbear-grub-policy.toml
 ```
 
 Each config selects packages and overrides init scripts. The tracked Red Bear desktop direction now
@@ -242,16 +251,16 @@ forward desktop path.
 ### Build Flow
 
 ```bash
-make all
-  → downloads cross-toolchain (Clang/LLVM for x86_64-unknown-redox)
-  → fetches recipe sources (git/tar)
-  → applies patches (redox.patch files)
-  → builds each recipe (cargo, meson, cmake, make, custom)
-  → stages into sysroot
-  → creates RedoxFS image
-  → produces harddrive.img / redox-live.iso
+./local/scripts/build-redbear.sh redbear-mini
+  → .config + README canon checks, fork drift verify
+  → build prefix from local/sources/{relibc,kernel,base,...}
+  → cook recipes (per config + package_groups)
+  → create iso
 ```
 
+Direct `make all` invocations bypass these gates per local/AGENTS.md § BUILD COMMANDS. Always use
+`build-redbear.sh`.
+
 ## 7. Existing Wayland/X11 Support
 
 ### Compatibility and Validation Surfaces