docs: clarify build setup defaults

Recipe example now notes that core components use path-fork recipes, while the CONFIG_NAME table entry is aligned to the actual default behavior exposed by mk/config.mk and build-redbear.sh.

docs/06-BUILD-SYSTEM-SETUP.md

@@ -230,7 +230,7 @@ git = "https://example.com/repo.git"    # Git source
 # tar = "https://example.com/source.tar.gz"  # Or tar source
 # branch = "main"                        # Git branch
 # rev = "abc123"                         # Or specific commit
-# patches = ["redox.patch"]              # Patches to apply
+# patches = ["redox.patch"]              # Patches to apply (non-core recipes only; core components use path = "../../../local/sources/<component>" instead of patches = [...])
 
 [build]
 template = "cargo"   # Build template: cargo, meson, cmake, make, custom
@@ -263,7 +263,7 @@ cp target/release/myapp ${COOKBOOK_STAGE}/usr/bin/
 | Variable | Default | Description |
 |---|---|---|
 | `ARCH` | Host arch | Target architecture (x86_64, aarch64, i586, riscv64gc) |
-| `CONFIG_NAME` | `redbear-full` | Build config name |
+| `CONFIG_NAME` | `redbear-full` (mk/config.mk; build-redbear.sh passes its selected config through `make live CONFIG_NAME=...`) | Build config name |
 | `PODMAN_BUILD` | `1` | Use Podman container |
 | `PREFIX_BINARY` | `1` | Use prebuilt toolchain (faster) |
 | `REPO_BINARY` | `0` | Use prebuilt packages (faster, no compilation) |