Skip to content

Commit caa9867

Browse files
committed
Merge origin/main into fix/ipad-deep-tree-interaction
Takes main's slim host app from #3956 and re-applies #3918's safe-area-anchored back-regression button inside AgentDeviceRunnerAppFixtures.m.
2 parents 1d9d95f + 632c83d commit caa9867

60 files changed

Lines changed: 5168 additions & 1111 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.changeset/expired-resource-404.md‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
'agent-device': patch
3+
---
4+
5+
Answer `404` instead of `500` when an artifact download, upload ticket, uploaded artifact, or materialized path id was already consumed, has expired, or never existed. The error keeps `code: "COMMAND_FAILED"` and `details.reason: "RESOURCE_EXPIRED"`. Daemon HTTP REST error bodies, such as those on `/artifacts/*` and `/upload/*`, now also carry `reason` when the error has one, and a `hint`. A host lease allocation on `/admin/leases` that a human-control hold refuses now answers `423` instead of `500`. A `/rpc` call that does not stream progress now answers `423` when its handler throws that refusal, as it already did when the handler returned it. A call that streams progress keeps its `200` once it has written progress, and its final envelope carries the failure.
Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
---
2+
'agent-device': patch
3+
---
4+
5+
Keep a remote recording downloadable when its leased session ends mid-recording (lease expiry, release, or `close`). Teardown finishes the recording and registers the video and gesture telemetry as downloadable artifacts of the lease's tenant, instead of leaving them unreachable in the daemon's temp directory. `GET /artifacts` entries now carry an optional `sessionName` for such artifacts. A later `record stop` replay returns the same artifact ids.

‎.github/workflows/docs.yml‎

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,8 @@ on:
1414
- 'scripts/__tests__/check-doc-links.test.ts'
1515
- 'scripts/check-doc-prose.ts'
1616
- 'scripts/__tests__/check-doc-prose.test.ts'
17+
- 'scripts/capability-matrix/**'
18+
- 'test/repo-guards/capability-matrix.test.ts'
1719
- 'scripts/check-affected/**'
1820
- 'package.json'
1921
- 'pnpm-lock.yaml'
@@ -32,6 +34,8 @@ on:
3234
- 'scripts/__tests__/check-doc-links.test.ts'
3335
- 'scripts/check-doc-prose.ts'
3436
- 'scripts/__tests__/check-doc-prose.test.ts'
37+
- 'scripts/capability-matrix/**'
38+
- 'test/repo-guards/capability-matrix.test.ts'
3539
- 'scripts/check-affected/**'
3640
- 'package.json'
3741
- 'pnpm-lock.yaml'
@@ -64,6 +68,12 @@ jobs:
6468
uses: ./.github/actions/run-gate
6569
with: { gate: docs-prose }
6670

71+
# The page's cells are generated from runtime facts; the guard regenerates,
72+
# diffs, and proves its own negative cases before anything reads the page.
73+
- name: Check the capabilities page against runtime facts
74+
uses: ./.github/actions/run-gate
75+
with: { gate: capabilities-matrix }
76+
6777
# Builds the site (root install covers the website workspace), then checks it.
6878
- name: Check docs links
6979
uses: ./.github/actions/run-gate

‎.github/workflows/release.yml‎

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -248,11 +248,14 @@ jobs:
248248

249249
- name: Setup toolchain
250250
uses: ./.github/actions/setup-node-pnpm
251-
with:
252-
install-deps: 'false'
253251

254252
# main must never carry a published version. Retried because merges can
255253
# land on main while the release runs.
254+
#
255+
# The capabilities page stamps the version it covers and the drift check
256+
# compares that stamp to package.json, so the version bump restamps the
257+
# page in the same commit. The collector reads runtime sources and needs
258+
# no device.
256259
- name: Commit the next development version
257260
env:
258261
VERSION: ${{ needs.plan.outputs.version }}
@@ -264,6 +267,7 @@ jobs:
264267
git fetch origin main
265268
git reset --hard origin/main
266269
next="$(node scripts/release-version.mjs advance "$VERSION")"
270+
pnpm generate:capabilities
267271
if git diff --quiet; then
268272
echo "main already builds towards $next."
269273
exit 0

‎README.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,7 @@ The same session and evidence model works at every step: the agent explores the
157157

158158
`agent-device` keeps device state in sessions. It uses a local accessibility bridge for iOS Simulator snapshots and XCTest for iOS interactions, physical iOS, and tvOS; ADB and the snapshot helper on Android, Android TV, and Fire OS; HDC and ArkUI `uitest` on HarmonyOS; Vega CLI/VDA on the Vega Virtual Device; a local helper on macOS, including Electron and other Chromium-based apps through the accessibility tree; and AT-SPI on Linux.
159159

160-
Support depth varies by target. Some backends, such as HarmonyOS and Vega OS, cover a subset of commands; run `agent-device capabilities --platform <platform>` to see what a target supports.
160+
Support depth varies by target. Some backends, such as HarmonyOS and Vega OS, cover a subset of commands; run `agent-device capabilities --platform <platform>` to see what a target supports. The [capabilities matrix](https://oss.callstack.com/agent-device/docs/capabilities) shows which commands each target, desktop, web, and cloud provider supports.
161161

162162
Sessions are scoped to the caller's git worktree, and host-local device claims stop parallel agents from taking over each other's simulators and emulators. Run `agent-device device status` to inspect ownership without a daemon, and `agent-device device release --stale` to release claims whose owner is provably no longer running. The same commands drive hosted devices on [BrowserStack, AWS Device Farm, TestMu AI, and Limrun](https://oss.callstack.com/agent-device/docs/device-clouds).
163163

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
// The runner host app's UIKit view controller, shared by the two source units that draw it.
2+
// AgentDeviceRunnerApp.m implements the screen the npm package ships;
3+
// AgentDeviceRunnerAppFixtures.m subclasses it for the unit-test build only and is dropped from
4+
// the package. A packaged build compiles this header with the fixtures file absent, so nothing
5+
// here may name fixture code.
6+
#import <TargetConditionals.h>
7+
8+
#if !TARGET_OS_OSX
9+
#import <UIKit/UIKit.h>
10+
11+
@interface AgentDeviceRunnerViewController : UIViewController
12+
13+
// The host's own title label. The fixture screens lay out against it, so the unit-test host keeps
14+
// the anchors the shipped host draws.
15+
@property(nonatomic, strong, readonly) UILabel *label;
16+
17+
// The one extension point between the shipped host and the fixture host: called after the window
18+
// carries its root view controller and before it is shown, so a fixture window an override adds
19+
// stays behind the main window, as before. The shipped host does nothing here.
20+
- (void)agentDeviceWillAttachToWindow:(UIWindow *)window;
21+
22+
@end
23+
24+
#endif

0 commit comments

Comments
 (0)