P1: Refresh CUA/TryCUA and Peekaboo fallback package proof

[100yenadmin]

P1: Refresh CUA/TryCUA and Peekaboo fallback package proof

The released Mac-control path currently reports CUA as primary and Peekaboo as fallback. Make that release contract durable by auditing packaged versions, refreshing stale packages if needed, and proving the fallback chain without redesigning the Mac connector.

Acceptance:

• CUA/TryCUA is detected as the primary Mac-control engine in signed installed-app proof.
• Peekaboo remains available as fallback, with package/version freshness recorded.
• Accessibility/manual control remains final fallback.
• Stop/revoke and kill-switch fail closed.
• No connector URLs, tokens, IPs, ports, or raw audit secrets appear in UI/issues/evidence.
• Core broker surfaces remain green.

Parent: #569

[coderabbitai]

🔗 Related PRs

#391 - Restore beta3 Mac pairing baseline [merged]
#403 - fix: recover Mac control installed app states [merged]
#416 - Fix Mac control connector-service ready reconciliation [merged]
#449 - Fix legacy app stale owner proof path [merged]
#462 - [codex] Document Workbench release proof lanes [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[100yenadmin]

Current package audit and implementation boundary (2026-07-10)

Observed current state:

• Installed Workbench is 2.1.31; its bundled bridge manifest pins evaos-desktop-bridge commit 4753cbd8e17d30a3f0f344cc88d4cc86f3e97422 and its bundled Peekaboo reports 3.7.1.
• The separately installed cua-driver reports 0.6.8. That is current-machine evidence only; it is not a signed Workbench package claim.
• Upstream Peekaboo stable is v3.8.0. Its official universal CLI archive is reproducibly pinned by archive digest; the extracted executable reports 3.8.0, is universal arm64/x86_64, and has a valid Developer ID signature. The included MIT notice is also digest-pinned for bundling.
• Upstream CUA has cua-driver-rs-v0.7.1, currently marked prerelease. Its embedded TCC model requires the GUI permission owner to spawn the driver directly; the evaOS connector currently runs through a LaunchAgent bridge. Updating CUA in this packaging-only slice could therefore change the permission owner or duplicate prompts.

Selected implementation slice:

• Branch codex/issue-573-peekaboo-3-8-0, based on evaos/beta-rc-20260612 at 19997d4a781084cd974ca55742a92c5cfc17a12a.
• Replace mutable Homebrew-latest Peekaboo acquisition with the official v3.8.0 universal asset, exact archive checksum, exact version check, and bundled MIT-notice retention.
• Record packaged binary/license identity in the existing bridge manifest and make Workbench Functional Smoke compare the manifest with the actual packaged files.
• Preserve bridge SHA, CUA detection/routing, Accessibility fallback, broker/session/auth, stop/revoke, kill-switch, and no-ACP packaging behavior.

Current local proof: 3 focused test files / 63 tests pass, the beta release-config audit passes, the official binary identity/digest rehearsal passes, and the changed hunks introduce no new actionlint finding. Existing unrelated shellcheck findings in the large workflows remain outside this slice.

Explicitly not proven here: CUA 0.7.1 adoption, CUA-as-primary signed installed-app behavior, Accessibility/manual fallback, stop/revoke, kill-switch, signed/notarized artifacts, production distribution, or customer readiness. CUA 0.7.1 stays architecture/permission-owner gated; no Matt setup or customer runtime was changed.