# Round 28 disposition: revision 34 ADB bridge

Both requested Pioneer models completed focused reviews of the same exact-text section 19 revision 34 bundle. Reports: `round-28-glm.md` and `round-28-kimi.md`. Neither was clean.

They found that an install retry within the same ADB session could precede reconciliation; old records could later be misattributed to a new install; byte-identical reinstalls matched contradictory verdicts; the installed artifact digest and update marker were treated as stronger evidence than the plan justified; and time-bounded evidence could disappear before a phone returned online. Kimi also identified a prior-package/changed-marker case with no defined branch. GLM noted that a restarted companion could at least report its own current version.

Revision 35 removes retrospective command-outcome inference. A complete authenticated ADB success response is the only success acknowledgment. A lost response becomes a durable historical **outcome unknown**. A later package read is labeled as current state only and cannot rewrite that outcome; same-session and subsequent installs get new operation IDs. Detailed evidence has bounded retention, while the minimal unknown audit status remains. Any user-initiated later deployment may proceed without a new approval prompt, but it is never an automatic retry of the unknown command. The restarted companion may report its own version as a current-state observation. A focused follow-up review is pending.