# ADB bridge second-pass disposition — revision 31 to 32

Pioneer `zai/glm-5.3` and `kimi-code/k3-256k` independently reviewed exact-text excerpts of revision 31. GLM reported no substantive findings in its scope. Kimi reported two remaining defects, both amended in revision 32:

1. **Approval priority had no enforcer across separate transports.** The unprivileged Mac approval transport now sends a bounded pending/clear signal to the bridge over authenticated local IPC. The bridge throttles or pauses Mac-originated frames, and the Android app prioritizes its approval socket and pauses phone-originated bridge frames. The signal carries no request details or authority; shared-link contention remains measurable rather than assumed absent.
2. **A self-update had no result path after terminating its own bridge.** The Mac now records the interrupted install as unknown. After Ready mode is restored, a new paired session independently checks installed package state and resolves only a matching observed result. Without reconnection or verification, unknown remains.

The session-admission UX, stronger local ADB client boundary, Android platform behavior, and bridge-hosting app recovery remain open gates. A focused revision 32 review of these amendments is in progress.