Document workaround caveat

Author: MhmRdd

README.md

@@ -10,6 +10,8 @@ On Android 10+ a service can declare `android:useAppZygote="true"` together with
 
 The hook is on `com.android.server.am.ProcessList#startProcessLocked` inside `system_server`. When the target process is being hosted by App Zygote and its package is in the deny list, the hook reports the process-start request as accepted but skips the actual fork. The caller's `Context.bindIsolatedService(...)` can resolve to `true`, but no service connection arrives. The `ZygotePreload` callback never runs in `app_zygote`.
 
+> Note: This is not a fix, it's just a tricky workaround that tries to mimic a known behavior of optimization implemented by some other manufacturers, at cost of diverging from normal behavior of AOSP.
+
 System packages cannot be added to the deny list. The module's own package is always denied and cannot be unchecked, so the built-in tester can verify that the hook is blocking `useAppZygote` binds for the host.
 
 ## References