phase 2.3 (local): add orphan-patch decision tree reference to local/AGENTS.md

Mirrors the parent AGENTS.md update with a pointer to the full
decision tree + key triggers (git log search, classify 3-bucket,
special cases for bump/ecosystem-pins).

Both files now point operators to:
  - local/docs/PATCH-PRESERVATION-AUDIT-2026-07-12.md
  - local/patches/legacy-superseded-<date>/SUPERSEDED.md
  - AGENTS.md § 'Orphan-Patch Supersession Decision Tree'

local/AGENTS.md

@@ -613,6 +613,29 @@ If we can fetch fresh upstream sources tomorrow, provision sources from `sources
 If a change exists only inside an upstream-owned `recipes/*/source/` tree, then it is **not yet
 preserved**, even if the current build happens to pass.
 
+### Orphan-patch decision tree (added 2026-07-12, Phase 2.3)
+
+When `local/scripts/verify-patch-content.sh` reports a patch in
+`local/patches/<comp>/` is no longer present in the fork HEAD
+(orphan), the default action is NOT to reapply. Apply this decision
+tree per AGENTS.md § "Orphan-Patch Supersession Decision Tree":
+
+  1. Run 'git -C local/sources/<comp> log --all --oneline -i --grep <topic-kw>'
+     where <topic-kw> is extracted from the orphan's filename.
+
+  2. Classify the orphan:
+     (a) SUPERSEDED upstream      → MOVE to legacy-superseded-<date>/
+     (b) INTEGRATED via other commit → MOVE to legacy-superseded-<date>/
+     (c) MISSING-UPSTREAM    → try patch -p1 --fuzz=5, else mark Phase 2.4+
+                                and leave in local/patches/<comp>/
+
+  3. Special cases (always SUPERSEDED):
+     - 'bump' patches: managed by sync-versions.sh
+     - 'ecosystem-pins': managed by Local Fork Supremacy + AGENTS.md rules
+
+See: `local/docs/PATCH-PRESERVATION-AUDIT-2026-07-12.md` and the
+`SUPERSEDED.md` audit log in `local/patches/legacy-superseded-<date>/`.
+
 ### Local fork recipe directories must not carry patch files
 
 When a recipe's `[source]` uses `path = ".../local/sources/<component>/"`, the local fork