argent-device-interact still applies for everything not listed here (run-sequence, await-ui-element, secrets).

Contract

Needs the macos-apps flag, which is on by default. When a tool says it is off, tell the user to run the command it names. Do not change the flag yourself.
One app is one device. list-devices shows only apps argent started that still run, also those of other sessions: never pick one unless the user named that app or this session started it.
Start an app with boot-device {macosAppPath: "<abs path>.app"}, never with open or Xcode. Use launch-app only for an app argent already started: with no recorded path it takes whichever copy Spotlight finds.
Build the .app without starting it: xcodebuild ... build, then take the bundle from BUILT_PRODUCTS_DIR (xcodebuild -showBuildSettings). Xcode Run and react-native run-macos start a copy without the argent library: boot-device then fails with already running ... without the argent library. Retry with force: true, but ask the user first when they may have work open in that copy.
Never pass force when the error names another build path; report it.
After a code change: rebuild, then restart-app.
A start result with a note that the app showed no window: taps and screenshots need one. Tell the user, and read the log file it names.
On a hardened-runtime refusal, report it to the user. Do not sign files or change code signing.
Never activate the app or drive it with osascript, open or other system tools.
At the end: stop-all-simulator-servers {devices: ["macos-app-<bundle id>"]} closes argent's connection; the app keeps running.

argent-macos-app-interact

Contract

Per-tool notes