You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Host: install verification builds through Host, including private GitHub Actions artifacts #3268
Part of #3264. ADR 0021 §6. Design D6 in the umbrella.
Blocked by: #3265
The route policy from #3266 applies on top.
Purpose
A verification worker installs the exact CI build of a PR through Host, including builds stored as private GitHub Actions artifacts. It must not be able to point Host at files on the Host machine.
Required behavior
install-from-source <url> works through Host as it does through proxy, for public hosts only.
install-from-source --github-actions-artifact owner/repo:artifact works through Host. The daemon looks the artifact up through the GitHub REST API by id, by run and name, or by the newest live artifact with that name from the repository's own runs, never a fork pull request. It authorizes with AGENT_DEVICE_GITHUB_TOKEN from its own environment, sends the token only to an archive URL under the named repository, and hands that URL to the existing approved downloader, which drops the Authorization header at the cross-origin storage redirect.
AGENT_DEVICE_GITHUB_REPOSITORIES can limit which repositories the daemon token reads. A client holding a token refuses to reuse a daemon started without it or with another one.
Requests never carry a GitHub credential. The token is never written to daemon.json, logs or responses.
Tests with the network transport mocked: the lookup sends the daemon token, the storage redirect does not, and a missing token, a missing artifact and an expired artifact each get their typed refusal.
A test shows URL and artifact sources reach the daemon through Host.
A live iOS simulator run installs a real GitHub Actions artifact, opens the app and takes a snapshot, following docs/agents/device-verification.md. The PR records the commands and the result.
# on the Host machine
AGENT_DEVICE_GITHUB_TOKEN=... agent-device host --port 8443
# on the worker
agent-device install-from-source --github-actions-artifact callstack/app:ios-sim-build --platform ios
On hold: we are integrating Simlock first and will revisit ADR 0021 / remote Host implementation afterwards. See the sequencing decision.
Host-specific build installation is deferred with the front-end stack. Private GitHub Actions artifact installation may be considered as independent work if there is an immediate need; the current scope remains on hold.
Closing as superseded by the October 10 replacement of ADR 0021 and merged #3372. Agents now acquire, renew and release leases through Simlock themselves; agent-device drives those devices through its ordinary local runtimes. The in-process Host allocator integration was withdrawn.
The Host-specific artifact installation workflow no longer has its planned Host dependency. This does not reject private GitHub Actions artifact installation as an independent feature; any future proposal should state its concrete need against the existing installation/proxy surfaces.
Activity
feat(host): install verification builds through Host
feat(host): install verification builds through Host
thymikee commentedon Oct 7, 2026
On hold: we are integrating Simlock first and will revisit ADR 0021 / remote Host implementation afterwards. See the sequencing decision.
Host-specific build installation is deferred with the front-end stack. Private GitHub Actions artifact installation may be considered as independent work if there is an immediate need; the current scope remains on hold.
thymikee commentedon Oct 12, 2026
Closing as superseded by the October 10 replacement of ADR 0021 and merged #3372. Agents now acquire, renew and release leases through Simlock themselves; agent-device drives those devices through its ordinary local runtimes. The in-process Host allocator integration was withdrawn.
The Host-specific artifact installation workflow no longer has its planned Host dependency. This does not reject private GitHub Actions artifact installation as an independent feature; any future proposal should state its concrete need against the existing installation/proxy surfaces.