From 299bad56b4b0ce34c1e15dcccd2e9d87e36828cf Mon Sep 17 00:00:00 2001
From: oxmc7769 <oxmc7769.mail@gmail.com>
Date: Sat, 11 Jul 2026 19:38:36 -0700
Subject: [PATCH] Drop dead TWRP-fork manifest block, add
 external_update_binary

Old bootable/recovery + vendor/pawlet/twrp_recovery + vendor/twrp
projects were commented-out remnants of the abandoned full-fork
approach. Current design keeps stock bootable/recovery unforked and
plugs TWRP's GUI/toolkit in via vendor/pawlet/recovery_ui and
recovery_toolkit, already synced as part of vendor/pawlet. Adds
external/update_binary (applypatch/updater/edify, restored after
Google dropped it from AOSP) which had no manifest entry at all.
---
 common/pawletos.xml | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/common/pawletos.xml b/common/pawletos.xml
index fb7b453..4255b85 100644
--- a/common/pawletos.xml
+++ b/common/pawletos.xml
@@ -11,6 +11,10 @@
   <!-- Framework API Extensions -->
   <project path="vendor/pawlet/frameworks/pawlet" name="PawletOS/frameworks_pawlet" remote="oxmc_git" revision="main" />
 
+  <!-- Recovery — stock bootable/recovery stays unforked, TWRP GUI/toolkit plug in via
+       vendor/pawlet/recovery_ui + vendor/pawlet/recovery_toolkit (already synced as part of
+       vendor/pawlet below, no separate project needed). See NOTES-ota-recovery-ab.md. -->
+  <project path="external/update_binary" name="PawletOS/external_update_binary" remote="oxmc_git" revision="android-16.0" />
   <!-- Vendor (HALs, system apps, etc.) -->
   <project path="vendor/pawlet" name="PawletOS/android_vendor_pawlet" remote="oxmc_git" revision="android-16.0" />