fix(limrun): attribute API-key traffic with the SDK userAgent option

[thymikee]

Summary

Upgrade @limrun/api to 0.64.1 and use its new userAgent client option (limrun-inc/typescript-sdk#546) in place of the per-request User-Agent override on instance creation. Requests made with the Limrun API key now start their User-Agent with agent-device-cli/<version>, ahead of the SDK's own Limrun/JS <sdk-version>. This covers creating, listing, and deleting instances, uploading assets, and connect verification.

• limrunUserAgent(clientVersion) in client-options.ts builds the value for both API-key clients: the runtime and connect verification.
• client-options.test.ts drives the real SDK through a fetch stub and asserts the prefix reaches the wire. The old allocation test duplicated the cleanup coverage in limrun-runtime.test.ts, so it is removed.
• Docs updated in website/docs/docs/limrun.md.
• chore(gates) adds a minimumReleaseAgeExclude entry for @limrun/api@0.64.1, published today.

13 files.

Validation

Head 1cd2ce113: pnpm check:affected --run, all runnable checks passed. Fresh-context review found one issue (the test no longer covered attribution), which is now fixed.

Wire check: the real runtime and SDK sent to a local HTTP server:

	base 35c21b618 (SDK 0.60.0)	head 1cd2ce113 (SDK 0.64.1)
POST /v1/ios_instances	agent-device-cli/<v>	agent-device-cli/<v> Limrun/JS 0.64.1
DELETE /v1/ios_instances/<id>	Limrun/JS 0.60.0	agent-device-cli/<v> Limrun/JS 0.64.1
GET /v1/ios_instances (connect)	Limrun/JS 0.60.0	agent-device-cli/<v> Limrun/JS 0.64.1

Not live-verified: we have no confirmation yet that Limrun receives the header. The local CLI (0.21.11) and T3's bundled daemon (0.21.12) both predate attribution, which likely explains why Limrun hasn't seen it so far.

🤖 Generated with Claude Code

[cubic-dev-ai]

No issues found across 14 files

_{View guided diff | Turn on auto-fix | Re-trigger cubic}

[thymikee]

This is ready. The change sets the SDK userAgent option for API-key traffic, and I found no problems at 1cd2ce1. Not blocking: limrunUserAgent is asserted with a hand-built prefix in three test files (client-options.test.ts, connection-verification.test.ts, limrun-runtime.test.ts), so the mocked constructor-option tests could assert through limrunUserAgent instead. Take it or leave it. I could not run the tests against @limrun/api 0.64.1 here, so I did not confirm the SDK's prefix-before-Limrun/JS ordering myself. I rely on the wire table and the real-SDK test in the PR. No live Limrun run is needed, since this touches no device path. CI is still queued, with nothing failed yet. Before merge, CI must pass on 1cd2ce1, especially the lockfile and install checks for the 0.64.1 bump and the minimumReleaseAgeExclude entry.

[github-actions]

Size Report

Metric	Base	Current	Diff
Installed (including dependencies)	5.24 MB	5.24 MB	+324 B
Package (unpacked)	5.24 MB	5.24 MB	+324 B
Package (download)	1.57 MB	1.57 MB	+93 B

Startup median (7 runs, lower is better):

Scenario	Base	Current	Diff
CLI --version	27.9 ms	27.0 ms	-0.9 ms
CLI --help	78.3 ms	76.6 ms	-1.6 ms

[github-actions]

PR Preview Action v1.8.1
🚀 View preview at https://callstack.github.io/agent-device/pr-preview/pr-3679/
Built to branch gh-pages at 2026-10-15 15:23 UTC. Preview will be ready when the GitHub Pages deployment is complete.