Skip to content

Commit 4f53e53

Browse files
thymikeeclaude
andcommitted
docs(test-app): drop the stale Device Hub requirement from the Duo lane note
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
1 parent e3f2a6f commit 4f53e53

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

‎examples/test-app/README.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -341,6 +341,6 @@ across a pose change or mutation (a dropped session re-opens but never replays a
341341
failure artifacts, closes the session, and restores the starting pose.
342342

343343
**Deferred GitHub Actions enablement (not a completion condition).** Wiring an automatic Duo job
344-
later requires, all at once: a Duo runtime/device type on the runner image, working Device Hub pose
345-
controls with Accessibility permission on the runner host, and one actual successful lane run — then
346-
re-check the runner-image inventories, which are dated, not permanent.
344+
later requires, all at once: a Duo runtime/device type on the runner image, an Xcode with foldable
345+
HID support, and one actual successful lane run — then re-check the runner-image inventories, which
346+
are dated, not permanent.

0 commit comments

Comments
 (0)