migrate: complete source ownership transition

- Create source symlinks for all 7 core components (kernel, relibc, base,
  bootloader, installer, redoxfs, userutils) pointing at local/sources/
- Create redoxfs and userutils fork repos from frozen 0.1.0 archives
- Fix relibc-tests recipes: replace patch commands with direct fork build
- Archive all 417 patch files to local/archived/patches-2026-06-migration/
- Full AGENTS.md rewrite: remove all 31 remaining stale patch references,
  update DURABILITY POLICY to describe git commit workflow, update WHERE TO
  LOOK table, fix build flow description, replace Recipe Patch Wiring section
  with Recipe Source Configuration
- Zero active patches = [...] arrays remain in any recipe.toml file
- All 13 remaining grep hits for 'patches' are TODO comments in WIP recipes

AGENTS.md

@@ -83,50 +83,19 @@ Layer 2: Durable (survives clean/fetch/rebuild/release provisioning)
 | Editing files in `recipes/<pkg>/source/` | Those are symlinks to `local/sources/`. Git operations must happen in the actual repo. |
 | Creating new patch files in `local/patches/` | `local/patches/` is historical only. Changes go as git commits in `local/sources/<component>/`. |
 | Hand-writing patches | No patches exist. Use standard git workflow. |
-| Editing `recipe.toml` patches list without creating the actual `.patch` file | Build fails with "missing patch" error |
 | Expecting `source/` changes to survive `make clean` | `make clean` deletes `source/` directories |
 | Running `repo cook` without `--allow-protected` for core packages | Protected recipes (kernel, relibc, base) are offline-only by default |
 
-### Patch file location convention
+### Recipe source configuration
 
-- `local/patches/base/` — for the `base` package (init, daemon, all drivers)
-- `local/patches/kernel/` — for the kernel
-- `local/patches/relibc/` — for relibc
-- `local/patches/installer/` — for the installer
-- `local/patches/bootloader/` — for the bootloader
-- `local/patches/<package>/` — for any other patched package
-
-### Recipe patch wiring
-
-Each recipe's `recipe.toml` lists patches relative to `local/patches/<pkg>/`:
+Red Bear-owned recipes use the `Local` source type, pointing at the fork repo:
 
 ```toml
 [source]
-git = "https://gitlab.redox-os.org/redox-os/base.git"
-rev = "463f76b96..."
-patches = [
-    "P0-daemon-fix-init-notify-unwrap.patch",   # applied first
-    "P9-init-scheduler-completed.patch",          # applied second
-    # ... more patches
-]
+path = "../../../local/sources/base"
 ```
 
-Patches are applied in listed order. Dependencies between patches must be respected (a patch
-that defines a type must come before a patch that uses it).
-
-### Kernel-specific notes
-
-The kernel source at `recipes/core/kernel/source/` is a separate git worktree (rev `866dfad`).
-The kernel recipe is at `recipes/core/kernel/recipe.toml` and patches are at
-`local/patches/kernel/`. The same durability rules apply — all kernel changes must be
-in `local/patches/kernel/*.patch`, never in the `source/` tree directly.
-
-**Red Bear OS is offline-first by default. No script, build target, or tool may silently pull
-from any upstream repository without explicit user instruction.**
-
-This policy exists because silent upstream pulls are the root cause of stale and orphaned patches.
-When sources change underneath wired patches, those patches break. The only safe workflow is:
-frozen sources → patches applied atomically → build.
+Non-forked recipes use standard git or tar sources — no patches needed.
 
 ### Rules
 
@@ -216,9 +185,9 @@ redox-master/
 |------|----------|-------|
 | Add a package | `recipes/<category>/<name>/recipe.toml` | Use `template = "cargo\|cmake\|meson\|custom"` |
 | Change build config | `config/<name>.toml` | Include chain: wayland→desktop→desktop-minimal→minimal→base |
-| Fix kernel | `recipes/core/kernel/source/` | Kernel is a recipe, not top-level |
-| Fix a driver | `recipes/core/base/source/drivers/` | All drivers are userspace daemons |
-| Fix relibc (POSIX) | `recipes/core/relibc/source/` | C library written in Rust |
+| Fix kernel | `local/sources/kernel/` | Kernel is a recipe, not top-level |
+| Fix a driver | `local/sources/base/src/drivers/` | All drivers are userspace daemons |
+| Fix relibc (POSIX) | `local/sources/relibc/` | C library written in Rust |
 | Wayland integration | `recipes/wip/wayland/` + `local/docs/WAYLAND-IMPLEMENTATION-PLAN.md` | 21 WIP recipes + local validation/ownership plan |
 | KDE Plasma path | `recipes/wip/kde/` + `docs/05-KDE-PLASMA-ON-REDOX.md` | 9 WIP KDE app recipes |
 | **Desktop path plan** | `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` | **Canonical plan: console → HW-accelerated KDE** |
@@ -282,7 +251,7 @@ make all
   → mk/prefix.mk (download/setup cross-toolchain if needed)
   → mk/fstools.mk (build cookbook repo binary + fstools)
   → mk/repo.mk (repo cook --filesystem=config/*.toml)
-    → For each recipe: fetch source → apply patches → build → stage into sysroot
+    → For each recipe: fetch source → build → stage into sysroot
     → Each successful build produces repo/<arch>/<name>.pkgar + <name>.toml
   → mk/disk.mk (create filesystem.img, harddrive.img, redbear-live.iso or harddrive.img)
     → redoxfs-mkfs → redox_installer → bootloader embedding
@@ -297,7 +266,7 @@ Every successful `repo cook <package>` produces:
 | Package archive | `repo/x86_64-unknown-redox/<name>.pkgar` | Binary package for image assembly |
 | Package manifest | `repo/x86_64-unknown-redox/<name>.toml` | Metadata, version, deps, hashes |
 | Staged sysroot | `recipes/*/<name>/target/.../stage/` | Files for `repo push` |
-| Source tree | `recipes/*/<name>/source/` | Fetched + patched source (disposable) |
+| Source tree | `recipes/*/<name>/source/` | Symlink to local/sources/ or git clone |
 
 **A build is not complete until the .pkgar and .toml exist in `repo/`.**
 
@@ -452,9 +421,9 @@ See `local/docs/BUILD-SYSTEM-HARDENING-PLAN.md` for the full plan.
 - **DO NOT** modify kernel syscall ABI directly — use `libredox` or `relibc`
 - **DO NOT** put drivers in kernel space — all drivers are userspace daemons
 - **DO NOT** hardcode `/dev/` paths — use scheme paths (`/scheme/drm/card0`)
-- **DO NOT** skip patches in WIP recipes — document what's missing with `#TODO`
+- **DO NOT** skip required dependencies — document what's missing with `#TODO`
 - **DO NOT** skip warnings — investigate, diagnose, and fix the root cause; suppressing or ignoring warnings is not acceptable when a fix is feasible
-- **DO NOT** remove patches from `recipe.toml` to fix build failures — rebase the patch instead (see `local/docs/PATCH-GOVERNANCE.md`)
+- **DO NOT** suppress build failures by disabling features — fix the root cause instead
 - **DO NOT** remove BINS entries to fix build failures — fix the source or use EXISTING_BINS filtering
 - **DO NOT** use the VESA display driver (`vesad`) as the primary display surface after GPU detection. vesad is only for early-boot framebuffer handoff — after redox-drm loads, the display path is `/scheme/drm/card0`. See **NO VESA POLICY** below.
 
@@ -584,25 +553,27 @@ only inside a fetched source tree is not preserved.
 
 **Required actions after any source-tree edit:**
 
-1. **Generate a patch** from the source git diff and save it under `local/patches/<component>/`.
-2. **Wire the patch** into the recipe's `recipe.toml` `patches = [...]` list.
-3. **Commit** the patch file and recipe change before the session ends.
+1. **Commit** your changes in the fork repo: `git -C local/sources/<component>/ commit -m "..."`.
+2. **Push** if sharing: `git -C local/sources/<component>/ push`.
 
 **Why:** `make distclean`, `make clean`, and source immutable archivedes all
-discard or replace `recipes/*/source/` trees. Only `local/patches/`, `local/recipes/`,
+discard or replace `recipes/*/source/` trees. Only `local/sources/`, `local/recipes/`,
 tracked configs, `local/docs/`, and `sources/redbear-0.1.0/` survive.
 
-**Examples of changes that require immediate patching:**
+**Examples of changes that require immediate committing:**
 
-| What you edited | Durable location |
+| What you edited | Where to commit |
 |---|---|
-| `recipes/core/relibc/source/src/header/sys_select/mod.rs` | `local/patches/relibc/P3-select-not-epoll-timeout.patch` + `recipe.toml` |
-| `recipes/core/relibc/source/src/header/signal/cbindgen.toml` | same patch as above |
-| `recipes/core/userutils/source/res/issue` | `local/patches/userutils/redox.patch` + `recipe.toml` |
-| `recipes/core/kernel/source/...` | `local/patches/kernel/redox.patch` (symlinked from recipe) |
+| `local/sources/relibc/src/header/sys_select/mod.rs` | `git -C local/sources/relibc commit` |
+| `local/sources/relibc/src/header/signal/cbindgen.toml` | same repo as above |
+| `local/sources/userutils/res/issue` | `git -C local/sources/userutils commit` |
+| `local/sources/kernel/src/...` | `git -C local/sources/kernel commit` |
 
-**What does NOT need patching:** Files that already live in `local/`, tracked `config/redbear-*.toml`,
-or any path that is already git-tracked and not inside a fetched source tree.
+**What does NOT need committing to fork repos:** Files that already live in `local/recipes/`, tracked `config/redbear-*.toml`,
+or any path that is already git-tracked in the main repo.
+
+**What does NOT need committing to fork repos:** Files that already live in `local/recipes/`, tracked `config/redbear-*.toml`,
+or any path that is already git-tracked in the main repo.
 
 ## BUILD SYSTEM POLICIES
 
@@ -627,8 +598,7 @@ ls repo/x86_64-unknown-redox/<package>.pkgar
 If a package was built but the repo artifacts are missing, the build did not complete.
 Re-run `repo cook <package>` to regenerate them.
 
-If source patches were applied but not mirrored to `local/patches/`, see the
-DURABILITY POLICY section above.
+If source changes were made but not committed to `local/sources/<component>/`, commit them there.
 
 ### Cascade Rebuild Rule
 
@@ -699,7 +669,7 @@ See `local/docs/CONSOLE-TO-KDE-DESKTOP-PLAN.md` for the canonical desktop path p
 | ~~P0: Fix ACPI for AMD~~ | ~~4-6 weeks~~ | ✅ Materially complete — boots on modern AMD bare metal; see `local/docs/ACPI-IMPROVEMENT-PLAN.md` for forward work |
 | ~~P1: Driver infrastructure~~ | ~~8-12 weeks~~ | ✅ Complete — redox-driver-sys + linux-kpi + firmware-loader + pcid /config + MSI-X (compiles) |
 | ~~P2: AMD GPU display~~ | ~~12-16 weeks~~ | 🚧 Partial — redox-drm + bounded Red Bear AMD display glue build; imported Linux AMD DC/TTM/core remain builds and included in redbear-full (2026-04-29); Intel driver compiles, no HW validation |
-| ~~P3: POSIX + input~~ | ~~4-8 weeks~~ | 🚧 Build-side work substantially complete — the active relibc recipe patch chain now carries the bounded fd-event, semaphore, and waitid compatibility surface needed by current downstreams, while broader runtime validation and input-stack maturity remain open |
+| ~~P3: POSIX + input~~ | ~~4-8 weeks~~ | 🚧 Build-side work substantially complete — the relibc source fork carries the bounded fd-event, semaphore, and waitid compatibility surface needed by current downstreams, while broader runtime validation and input-stack maturity remain open |
 | P4: Wayland compositor | 4-6 weeks | 🚧 Partial — libwayland/Qt6 Wayland/Mesa EGL+GBM+GLES2/Qt6 OpenGL now build, but compositor/runtime validation is still incomplete |
 | ~~P5: DML2 enablement~~ | ~~partial~~ | 🚧 Historical DML2 config work landed, but the current retained AMDGPU build no longer treats imported DML2/TTM as part of the default bounded compile path; libdrm amdgpu ✅, `iommu` daemon now builds; hardware validation still open |
 | P6: KDE Plasma | 12-16 weeks | 🚧 In progress — Qt6 ✅, KF6 32/32 ✅, Mesa EGL/GBM/GLES2 ✅, kf6-kcmutils ✅, kf6-kwayland ✅, kdecoration ✅, KWin 🔄 building |