# ADB bridge focused disposition — revision 32 to 33

Pioneer `zai/glm-5.3` and `kimi-code/k3-256k` independently reviewed exact-text revision 32 clauses. GLM found an incomplete failure outcome after bridge-hosting app self-update. Kimi found that the priority signal could expire while an approval remained pending and that the later install comparison lacked a retained reference record. Revision 33 changes:

- The Mac approval transport renews a bounded pending priority lease. On lost renewal without an authenticated clear, the bridge remains paused until the approval transport recovers and attests that no request remains pending. The phone's own app schedules its two sockets locally; the acceptance text no longer asks for a nonexistent phone-to-Mac priority signal.
- Before install, the Mac command retains operation-scoped expected and prior package metadata privately, without APK bytes or ADB payloads. On self-update disconnect it records unknown. At the next Ready session, it reconciles that same operation before another install to the package: expected state means success, verified old or different state means failure with retry guidance, and unavailable/inconclusive evidence remains unknown.

Revision 33 is undergoing a focused convergence check. Its platform and user-decision gates are not implementation proof.