Adopt the next agent-device release (daemon/runner-ownership fixes)

[thiagobrez]

Part of the CI overhaul execution plan (#59, map #53). Follow-up, not one of the 9 ordered PR tasks — blocked externally: actionable only once agent-device publishes a release newer than 0.20.10.

Decisions: #56 and #60. The pinned 0.20.10 is the latest release; the fixes for the iOS runner … is already owned by another agent-device daemon collision (which neuters our attempt-2 retries) are merged upstream but unreleased: callstack/agent-device#2160, #2162, #2105 (plus #2057/#2171/#2015).

Scope

When the next release ships: bump the agent-device pin in package.json (and the version reference in ADR 0006), review the 0.21 breaking changes flagged in upstream's Unreleased changelog, and keep the local daemon-stop hygiene unless the release notes supersede it. Independent of the iOS 26 Detox reroute (#65) — this pin serves the iOS 27 Agent Device jobs.

Acceptance criteria

• Pin bumped; contract jobs updated for any breaking CLI changes.
• Five consecutive successful iOS 27 native and iOS 27 forced-fallback Agent Device contract runs after the bump (the Decide the iOS 26 device-contract input-readiness fix #60 acceptance streak).
• Local workaround audit revisited: drop any hygiene the release makes redundant, keep the rest.