Reviewed IMPLEMENTATION-PLAN.md (revision 45, full read) against PREVIOUS-REVIEW.md and DISPOSITION.md, tracing each fix and its cross-section interactions.

**Verification per finding**

1. **Provisioning/import scopes** — Resolved. Section 16 now splits onboarding provisioning (exportable credential that creates fresh tunnels/Access apps/service tokens in the selected account/zone, explicitly *not* scoped to the source Mac's resource IDs) from steady-state management (per-Mac recorded resources, provider scoping where supported). The credential table distinguishes both tokens; provider-granularity disclosure and the feasibility fallback ("disclose the broader scope and obtain setup approval") are preserved. Section 2's export exclusions and "create fresh resource identities on import" are consistent; the encrypted export is the stated sole exception for management secrets.

2. **Disabled new ADB grants** — Resolved. Section 2 shared-defaults list no longer includes ADB enablement; it declares enablement "never an exportable or inheritable default," with every new pair starting disabled; export exclusions name "ADB pair grants or enabled state." Consistent with section 1's per-pair default-disabled statement and section 5's "pairing does not grant ADB access."

3. **macOS floor** — Resolved. Both stale references are re-anchored: the service-installation spike now says "Test macOS 26+ on Apple Silicon, matching the supported platform baseline," and section 17 says "Validate API availability and behavior on the supported macOS 26+ Apple Silicon baseline." No "macOS 14"/"provisional floor" text remains.

4. **Authority-origin priority snapshots** — Resolved per disposition. Section 19 makes the root authority originate an authenticated aggregate pending/clear attestation (transport relays, never originates), scoped to phone-eligible traffic ("local-only requests do not assert network contention"), bound to authority incarnation/sequence/freshness, with expiry/disconnect → unknown (not clear), automatic invalidation on root restart, and snapshot reconciliation on both root and transport restarts. Old-incarnation replay tests included. No lingering transport-owned lease or local-only pause.

5. **Android single-active-session admission** — Resolved per disposition (including the disposition's narrowing of the reported consequence). Section 19 defines atomic phone-side admission of one bridge session per device, Busy to competing Macs without disabling their grants, reservation spanning setup–teardown, no preemption, and old-stream reconciliation before release; restore path "keep[s] existing concurrency and session-admission limits." Multi-phone approval enrollment explicitly unaffected; the section 2 same-user caveat remains accurate (phone-side admission covers cross-Mac serialization, not a same-user host-key holder).

6. **Gateway/tunnel release manifest** — Resolved. Section 17's signed manifest now includes "bundled notification gateway/push sender, tunnel client" plus service registrations, with gateway/bridge/tunnel subject to the same protected-placement, quiescence, coordinated-activation, and minimum-build rules and post-update verification; gateway updates preserve durable recipient revisions and cannot restore revoked recipients — consistent with the section 16 control plane.

7. **Opaque enrollment push tags** — Resolved. Section 15 defines per-(Mac/account–Android enrollment) random routing tags registered via the authenticated pairing channel, containing no hostname/account/request data, hint-not-authority, never following push-supplied endpoints, per-enrollment coalescing, and cross-Mac isolation under a shared FCM token. Consistent with section 5's shared-token semantics (the tag is an opaque identifier, not request content).

8. **Retention reference** — Resolved. Section 19's bridge terminal-metadata line now cites "the section 12 audit-retention policy," and section 12 contains the configurable retention/storage-budget rules.

**Settled UX constraints** — Intact: no recurring biometric/per-install/per-session confirmations introduced, no arbitrary pair-grant expiry ("Connection challenges may expire, but the pair grant has no arbitrary expiry"), no central server/SaaS, legacy ADB fallback retained with its disclosures.

**Minor editorial residue (not substantive):** the section 19 acceptance list still says "Mac-local lease renewal" where the mechanism is now authority attestation refresh, but the tested semantics (renewal, expiry-without-clear, recovered clear) match the new text.

**No substantive findings in the reviewed changes and interactions.**