Repository navigation
Conversation
|
Live Limrun evidence at Setup: branch CLI ( Commands per platform: Packed check on |
Size Report
Startup median (7 runs, lower is better):
|
This comment has been minimized.
This comment has been minimized.
|
Reply to the Sentinel finding "Ended Limrun lease stays stored when the command never primes the plugin store" ( The finding is correct. Route: Fixed in 82fd39f:
@apex-sentinel-staging review |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Apex Sentinel: 1 new finding on 82fd39f. The verdict and the full list are in the summary comment.
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Apex Sentinel: 1 new finding on 1c803c8. The verdict and the full list are in the summary comment.
This comment has been minimized.
This comment has been minimized.
|
Reviewed 997f851: a second independent pass found three problems to fix before merge, all where Limrun is now an optional plugin and stored state or the install hint is affected. The first is in cloud-profile.ts. Run The second is in cli.ts. Take a named Limrun remote profile with an HTTP daemon URL that triggers cloud authentication, no current CLI session, and no plugin. Both The third is in connection-runtime.ts. Upgrade a state directory that has a named pending Limrun connection A and a newer providerless connection B, with no record named For a follow-up issue, not for this PR:
Not blocking, and fine to take or leave: the stored The two earlier inline threads on ended-lease policy are fixed at this head and can be resolved: #4846 (comment) and #4846 (comment). CI is unclear. The failing jobs are the advisory mutation shards kernel-errors-3 and kernel-errors-4, which this PR triggers because it touches package manifests and the lockfile. The diff does not touch Required evidence is present. Before merge, the three fixes above are needed, and the mutation shards need a re-run or an explanation. |
Mutation shards
|
|
Reply to the review of 1. 2. Provider admission after remote authentication — fixed in cf9e4d4. 3. A catalog read changing the active connection — fixed in 5d14a0d with the simpler option. The stored Known limit after dropping the field: a third-party plugin that declares Not changed, per the review: provider-name normalization, the daemon-side hint, and the plugin showing as failed without Checks on the new head: typecheck, lint, format, layering, |
This comment has been minimized.
This comment has been minimized.
|
Correction to my note above on the mutation shards: the cause of the slow test is not the 250 ms sleeps (those were already mocked). The contention loop runs 300 iterations, and each one re-reads the daemon registration; reading a held lock takes one host The fix is up as #4856 (against |
|
Two problems remain at cf9e4d4, and both are about when the CLI admits the Limrun provider. The two earlier inline threads on the ended-lease policy are fixed at this head and can be resolved: #4846 (comment) ( A second independent pass found that interactive cloud discovery saves a CLI session before it refuses Limrun. Run A second independent pass also found that an inherited profile can select a different connection during materialization (provider-admission.ts:37). Connect session Not blocking, and fine to take or leave: admission derives the provider as The code needs the two fixes above. CI shows one red check, the |
|
Scope note for the review at cf9e4d4 (#4846 (comment)):
The author's per-point reply with SHAs follows after the push. |
|
Reply to the review of Point 1, a new login saved before Limrun is refused — fixed in 2240079. The fix is in the auth-session owner. A login that One consequence to know: a Point 2, an inherited profile selecting a different connection during materialization — not fixed in this PR. 37b7e68 adds one helper, Optional items, taken in 37b7e68: the shared helper above, and Checks on the new head: typecheck, lint, format, layering, |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Apex Sentinel: 1 new finding on 37b7e68. The verdict and the full list are in the summary comment.
37b7e68 to
6d735ae
Compare
|
Update to my reply on the review of Point 1, a new login saved before Limrun is refused — fixed. The final shape is in 6d735ae (it replaces the per-site commits of the earlier push). One limit on test (c) as asked: no device command can approve a login, because only Point 2, an inherited profile selecting a different connection during materialization — not fixed in this PR. 9d55d0d adds one helper, Optional items — both taken in the same commit: the shared helper, and the Checks on 6d735ae: typecheck, lint, format, layering, |
This comment has been minimized.
This comment has been minimized.
|
The earlier findings from cf9e4d4 are fixed at 6d735ae, and a second independent pass found three login-timing defects that remain. Login is no longer discarded on non-refusal failures (auth-session.ts:91-101), A second independent pass found that cloud discovery can save a login that admission then refuses. Set the user config to valid JSON with The same pass found that admitted connect persists state and reports success before the login is saved. Create a writable private state directory with The same ordering problem affects explicit The two open inline threads on provider-selection and ended-lease handling no longer apply and can be resolved: login is no longer discarded on non-refusal failures (#4846 (comment)), CI shows 26 checks with none failing at 6d735ae. The earlier kernel-errors-4 dry-run failure was fixed upstream by #4856, which arrived with the rebase. There are no conflicts. This was a read-only review, so no local test run was done. Not verified here: that the new tests pass, which rests on green CI and the author's report. Live device evidence is from 50a0163, and the changes since then touch only CLI auth-state timing and the provider-precedence helper, so no new device run is needed. Merge needs the three fixes above, with a test for each failing route. |
|
Reply to the round-three review at 6d735ae (#4846 (comment)). No push yet; this asks for the scope decision. Classification. None of the three belongs in #4858 (that issue is the cross-state-directory record selection). All three are consequences of the deferred-login change this PR added in round two:
Two ways to resolve, maintainer's choice:
I will implement the one you choose and not push before that. |
This comment has been minimized.
This comment has been minimized.
6dfaa01 to
5911afd
Compare
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Apex Sentinel: 2 new findings on 5911afd. The verdict and the full list are in the summary comment.
| // Help and version answer from the command line alone and load no plugin. | ||
| if (parsed.flags.help || parsed.flags.version) return undefined; | ||
| const profilePath = parsed.flags.remoteConfig; | ||
| if (typeof profilePath === 'string') return providerOfProfileFile(profilePath, host); | ||
| return parsed.positionals[0]; |
There was a problem hiding this comment.
No longer raised on bdaa850: deferred to #4940 by thymikee in this comment.
🆕 🟡 Minor · Connect preflight admits only an explicitly typed profile path
A remote-config profile with leaseProvider set to "limrun" selected by default (repo .env/AGENT_DEVICE_REMOTE_CONFIG, or config-schema default) skips preflight admission, so connect limrun-style authenticates and registers the daemon token before failing at materialization. parsed.remoteConfigLeaseProvider is truthy exactly when flags.remoteConfig is set (src/cli.ts:382), and providerOfProfileFile is only consulted for that path, leaving the defaulted selection unadmitted. The credential-order guarantee in provider-admission-credential-order.test.ts only covers the argv case the test writes.
Suggested change
Resolve the profile path the same way the ordinary parse does (flag, env, schema default) inside connectProviderNamedInArguments before reading leaseProvider, so a profile selected by default is admitted before any credential is read.
Details
persona: maintainability, senior-developer
Useful? Reply @apex-sentinel-staging like, or @apex-sentinel-staging dislike <why> if it is not.
Reply @apex-sentinel-staging note ... to add context, or @apex-sentinel-staging pivot ... if it is wrong — I will re-check the cited code.
There was a problem hiding this comment.
Valid, and not in this PR's scope. A profile selected by default (env or schema default) still ends with the typed plugin-not-installed diagnostic. The command only authenticates first. That credential is the user's own cloud login, and the refused route writes no profile or connection record. Admission ordering for logins is tracked in #4940. I added this case there so it is resolved with the same profile-path resolution.
|
The website card problem from the earlier review (#4846 (comment)) is fixed at 5911afd, and a second independent pass found four problems that remain. CI is green: 28 checks, none failing, and the earlier Coverage failure does not reproduce at this head. No conflicts. A second independent pass found that the new Run anywhere command in website/src/site/content.ts:478 installs the wrong package for a 0.22 nightly reader. The plugin store resolves a bare package name to latest (store.ts:414), and the registry points latest at the runtime-free 0.0.0 placeholder. The nightly hints deliberately select a different release (plugin-installation.ts:5-37). Readers who copy the command get the placeholder, and the base website did not send them through this step. Can the card use the nightly selector from limrun.md:13, or point readers to the install command the CLI prints? A second independent pass found that src/cli.ts:458 refuses authenticated remote Limrun sessions too early. A client with a saved named Limrun session, a valid daemon token and no local plugin now fails with plugin-not-installed on a materializing command such as snapshot, before it authenticates or dispatches. An explicit Limrun --remote-config with a valid token reaches the same refusal. At base, auth ran first (provider-policy.ts:47 treated Limrun as available), and the head pins the early refusal in provider-admission.test.ts:94-131. The rule: the local plugin is required for direct connect and local materialization only. For device commands against a configured remote daemon, auth and dispatch must proceed, the daemon provider registration decides runtime admission, and the Limrun connection metadata that remote materialization needs stays available. The provider-admission tests enumerate the sites. Validation: a run with a saved remote Limrun session and no local plugin must reach the daemon and return a snapshot. A second independent pass found that connection-verification.ts:62 can echo the API key. If the account endpoint returns an unlabeled HTTP 500 body containing the key, the SDK error message contains it, and Android and iOS verification both attach that error as the cause. The iOS attached-instance route wraps the SDK error the same way at line 124. Core redacts by pattern (redaction.ts:20-89) and prints the cause in --json (cli.ts:655-673), and an unlabeled fixture credential survived the head normalizer. The wrappers come from base, but the credential invariant still fails at the plugin error boundary. The rule: no raw SDK cause leaves these wrappers. Return the typed verification error with a safe summary, status and hint, or remove the specific credential values first. Validation: a fixture endpoint that echoes the key must produce --json output without it. A second independent pass found that download-file.ts:48 can echo the instance token. A direct instance that answers an authenticated download with an HTTP 500 body containing the bare token puts it in details.body on the recorder download (device-session.ts:183-189), iOS file copy (ios-files.ts:88-95) and the iOS Info.plist download (ios-files.ts:194-204). The iOS runner does the same under details.response for failed XCTest start text (ios-runner.ts:166-174). The daemon publishes normalized details (request-router.ts:759-774), and the head normalizer kept the bare token in both fields. These paths predate the move but fail the same invariant. The rule: error details from these routes carry the status and typed reason, and never raw response text unless the instance token is removed first. Validation: a fixture instance that returns a 500 with the token in the body must yield daemon error details without it. Not verified here: the Coverage failure log from 93de794, the provider-limrun dist build, and the website build. The open inline thread on remote-config login ordering (#4846 (comment)) still applies and stays deferred to #4940. The thread on the public declaration (#4846 (comment)) does not apply, because the only published entry exports just the default limrun() plugin, so it can be resolved. After these fixes, maintainer approval is next. |
The Run anywhere card printed the bare package name, which the plugin store resolves to latest: the runtime-free placeholder. Use the nightly selector the docs and the CLI hints use, and point readers at the printed command.
A saved or explicit Limrun connection whose daemon is configured elsewhere was refused with plugin-not-installed before it authenticated or dispatched, which no base release did. The plugin is needed where the device is driven: keep the refusal for a direct connect and for a connection with no configured daemon, and let the daemon's own provider registration decide runtime admission otherwise. The connection's metadata is still read and saved either way.
The Limrun SDK echoes a request body in its error message, so an endpoint that answers a verification with an unlabeled body naming the API key put that key in the cause the CLI prints, which pattern redaction cannot see. Answer with the typed verification error, its status and hint, and carry no cause.
An instance that answers an authenticated download or an XCTest start with an unlabeled body naming the bearer token it was given put that token in the error details the daemon publishes. Remove each value sent to the endpoint from the response text before publishing it; the status and typed reason answer for the failure.
|
Four fixes for the second independent pass, at head 1. The Run anywhere card installed the placeholder — fixed in content.ts:478. The card now prints 2. Authenticated remote Limrun sessions are no longer refused early — the rule is in provider-policy.ts:120 as 3. No raw SDK cause leaves the verification wrappers — connection-verification.ts:62 and :122 no longer pass a fourth argument, so the printed cause is empty; the error keeps its typed code, the status when the SDK reported one, and its hint. The new case fails verification against an endpoint whose 500 body names the key and asserts 4. No raw instance response text in error details — one owner, error-text.ts, removes every value this process sent to the endpoint from the text before it is published; core still bounds and pattern-redacts it as it does any detail. Applied to the download body at download-file.ts:49, which covers the recorder download, the iOS file copy and the Info.plist read, and to the XCTest launch text at ios-runner.ts:179. Validation at Out of scope here and unchanged: the remote-config login ordering thread stays with #4940, and the public-declaration thread is resolved as not applicable. |
This comment has been minimized.
This comment has been minimized.
|
Validation receipt, as promised: One note for anyone rerunning locally: the first run used the runner's default |
|
This follow-up to the earlier review covers bdaa850. A remote-daemon Limrun connection can now proceed without the local plugin, which fixes the earlier refusal. The code still has one regression and several credential-leak paths, so it needs changes. CI is green (27 checks, none failing), and the author reports A remote Limrun connection without the local plugin now gets the generic remote capabilities instead of Limrun's declared ones (provider-policy.ts:191). Base always supplied Limrun's capabilities. Now A second independent pass found the same gap from the user side (connection-runtime.ts:98). With a saved Limrun session or explicit profile that targets a loopback HTTP daemon, and an empty client plugin store, authentication and dispatch succeed but the capabilities are generic. A fresh A second independent pass found that A second independent pass found that core still routes on the Limrun provider name for a known missing or broken plugin (provider-policy.ts:109, cloud-profile.ts:78-83). The #3311 boundary removes Limrun-specific branches from A second independent pass found that SDK debug logging can print keys and tokens (connection-verification.ts:41). With A second independent pass found that short and clipped tokens survive sanitizing (error-text.ts:36). The credential reader accepts any nonempty attached-instance token, but the sanitizer ignores candidates shorter than eight characters. A six-character token in an HTTP 500 body reaches A second independent pass found that a malformed recording download URL exposes the token (download-file.ts:104). An attached instance returns its bare bearer token as the download URL, fetch rejects it, and the plugin publishes the value in both A second independent pass found that the iOS runner paths can publish the instance token (ios-runner.ts:50). The runner forwards the Limrun A second independent pass found that runtime API errors can expose the account key (runtime.ts:432). The SDK builds its error message from the response body, and lease creation rethrows it to the daemon, which records and returns it. Asset-list errors on A second independent pass found that instance SDK clients can log or return raw WebSocket replies (ios.ts:65). The runtime and app-log reconnect clients enable SDK warning and error logs, and the locked SDK writes failed frames and parse errors to the console, so a bare token sent as a text frame is visible. iOS Not blocking: Could the predicate, the No open inline thread of high priority still applies, and no lower-priority thread still applies. The remote-config login ordering thread does not apply, because that work moved to #4940 and was ruled out of scope here. The tsdown.config.ts thread does not apply, because the only published entry exports the default Not verified here: tests and the website and provider-limrun dist builds were not run, and the green CI and the author's |
A remote Limrun connection whose host has no plugin was answered from generic remote capabilities, so `apps` allocated a lease, `lease_allocate` sent the daemon's default TTL, and `open <app>` dropped the initial app. The plugin catalog now carries the provider's whole declared `ConnectionProviderCapabilities` and its admission policy, and `declaredConnectionCapabilities` falls back to that copy before the daemon's own routing, so a connection's lease policy is its provider's whether or not this host loads the plugin. The predicate, its without-refusal variant and the three duplicated if/else sites collapse into `admitProviderForRoute(provider, route, env)`, which primes the store, refuses only where this host must supply the provider, and answers capabilities from the plugin when loaded, else from the catalog. `providerRouteForConnection` reads the same two settings the daemon client reads.
This comment has been minimized.
This comment has been minimized.
1794c68 to
4926549
Compare
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Apex Sentinel: 1 new finding on 4926549. The verdict and the full list are in the summary comment.
The SDK, an attached instance and a forwarding service in front of one all answer with their own text, and this plugin authenticates each of them with an account key or an instance token. An unlabelled echo of a bare credential survives core's pattern redaction, so each path that published peer text is closed at its owner: - Every client this plugin builds logs nothing: `off` on the organization client and `none` on an instance client, which outranks `LIMRUN_LOG`, so the SDK cannot write a failed response body that carries an account key or an instance token. - The scrubber drops a credential however brief — the reader of an attached instance accepts any nonempty token — and takes the credential out of both a header value and its bare credential. - A download publishes its typed reason, its status and a transport code: no URL, no peer body, and no fetch message, since an attached instance answers with its token as the download URL. - An account-API failure is re-raised as an `AppError` carrying status and reason before a create, an asset list, a recovery list, a reconnect lookup or a delete records or returns it, keeping the 404 answer a caller acts on. A termination reason is bounded to one line and scrubbed. - The runner's forwarded credential reaches its response, its cause and its log redaction boundary, including a credential split across stream chunks, and a `/sync` field this upload did not name stays out of the upload failure. - An instance client's own failures are answered through one wrapper, so `listApps`, `pressKey` and a remote install cannot return the peer's frame with the session token in it. Only a failure that names a sent value is re-raised, so a clean SDK failure keeps the reason and cause the command that caught it publishes.
4926549 to
99e1e82
Compare
This comment has been minimized.
This comment has been minimized.
|
The code at 99e1e82 still has open issues, and the Limrun device paths it changed have no live run. CI is green (28 checks, none failing), and the R89 failure at 1794c68 is resolved by the ReasonTable at ios-runner-errors.ts:15. Of the earlier findings (#4846 (comment)), the termination reason slicing is fixed; the items below remain or are new. No conflicts. The delta puts every Limrun device command behind new code, and the last live run is at 50a016345a. Every instance client method goes through a Proxy (instance-error-scrubbing.ts:25, installed at ios.ts:69, android.ts:82 and app-log-reconnect.ts:102/162). The XCTest output stream goes through a holding scrubber (ios-runner.ts:233-245), sync needFull is filtered (ios-runner-products.ts:208-217), and lease allocation is wrapped (runtime.ts:562). The PR body's "later commits change only CLI admission" no longer holds, so open, snapshot, press, apps, logs and runner startup ship without a live run of the code they now execute. Please post a live run at 99e1e82 or later with the packed @agent-device/limrun plugin and A second independent pass found that an authenticated organization request can get a 2xx A second independent pass found that the iOS SDK asks for deviceInfo before A second independent pass found that when an organization GET reports a created instance as terminated, it can echo the instance token in A second independent pass found that during iOS runner preparation, a 2xx A second independent pass found that a forwarded iOS runner command can return an unsuccessful envelope whose A second independent pass found that an authenticated runner reply can fail with a payload holding an object keyed by the bare instance token (instance-error-scrubbing.ts:125). A second independent pass found that with app logging enabled, the iOS endpoint can echo its bare token in A second independent pass found that when the first A second independent pass found that error-text.ts:38 changes a credential before matching it. The environment reader (credentials.ts:103-119) accepts an instance token with two interior spaces. The scrubber keeps the full Bearer header but collapses those spaces when it extracts the bare token. A peer echoing the original bare value in an iOS runner refusal (ios-runner.ts:180-182) or the startup stream (:235-244) then leaks it. The head helper reproduced the unmatched value in memory. Pass the original bare token as a separate candidate, or split the header only at the scheme separator and keep the exact suffix. Scrub a termination reason before collapsing its whitespace. Could the plugin side be simpler? The core side is sound. Instead of seven per-call For a follow-up issue, not for this PR: the same three rules apply as general invariants. client-options.ts:141 should map any statusless organization failure to a typed error. ios.ts:70 and its twins at android.ts:83 and app-log-reconnect.ts:102/162 should share one owner that builds and wraps the instance client. ios-runner.ts:37 should scrub at the runner response boundary, and at minimum wrap Not blocking, and these can be taken or left: the Of the open inline threads, none still applies. The default-selected profile admission ordering thread is deferred to #4940, which is out of scope here, and the delta leaves that order unchanged: #4846 (comment). The termination reason thread is fixed at 99e1e82, which scrubs the whole one-line reason before Not verified here: @limrun/api 0.69.1 is not installed locally (only 0.49.3), so the SDK's construction-time rejection text, its statusless parse errors, and whether |
Part A · review fixes
The regression batch failed 10 tests before the fixes. The final focused run passed 372 tests, and the two focused Apple runner suites passed 43 tests. At Part B · packed Limrun runsHead
Each CLI command below used Created iOS
Created Android
Owner of the attachment test simulator
Token-only iOS attachment
Both iOS {"type":"case","testClass":"AgentDeviceRunnerUITests.RunnerTests","method":"testCommand","durationMs":12369,"passed":true}
{"type":"summary","passed":1,"failed":0,"planFinished":true}The initial runner packaging attempt rejected the tag |
This comment has been minimized.
This comment has been minimized.
|
Most of the earlier findings from the 99e1e82 review (#4846 (comment)) are fixed at 972b036: the live evidence and x1-x9 are closed, and a second independent pass found six remaining places where a credential returned by the instance can leak or break a normal reply. CI is green, with 28 checks and none failing, and there are no conflicts. Merge should wait until the six items below are fixed. A second independent pass found that a local app install or reinstall on iOS or Android can leak a token prefix. If the instance returns its bare token as an invalid 2xx sync body, the SDK passes it to JSON.parse, and Node can quote the first ten characters in the SyntaxError. The head redactor in instance-error-scrubbing.ts:79 only matches the full token, so the prefix survives. The call sites are ios.ts:107 and android.ts:135. sync-cache.ts keeps the exception as the cause, and kernel errors.ts:596 publishes it. The rule: SDK sync decoder failures must become the existing static typed app-sync error with no decoder cause, while cancellation and typed transport failures stay as they are. A second independent pass found that Android app logging can write the instance token to app.log. The current reader (device-session.ts:133, runtime.ts:853) and the recovered reader (app-log-reconnect.ts:166-167) both pass the raw logcat tail to provider-app-log-poller.ts:88-89. The rule: every Android log tail must be scrubbed with the session token at the provider reader boundary, for both current and recovered capture. A second independent pass found that Android ADB errors can expose the token. For A second independent pass found that the forwarding scrubber can remove the runner's success field. If an iOS endpoint accepts the instance token A second independent pass found that iOS install verification can publish a credential returned as an app identifier. A successful sync reply can return the token as installedBundleId, or a URL install reply as bundleId. ios.ts:190 puts it in the verification error, and the same diagnostic copies inventory identifiers verbatim. The rule: peer-supplied identifiers and inventory strings must be scrubbed when building the error details, after the original identifiers are used for verification. A second independent pass found that an ambiguous asset lookup can return the account key. If two available assets with the requested name exist and one id contains the key, app-catalog.ts:60 (fromLimrunOrgApi, lines 48-50) returns it in details.assetIds. The rule: scrub the asset ids with the account key in the ambiguity error, or report only the match count. The high-priority inline threads need no further action here. Of the open inline threads, the default-selected profile admission ordering one (#4846 (comment)) does not apply, because that ordering is deferred to #4940 and this change does not touch provider-admission.ts. The error-text.ts one (#4846 (comment)) is fixed at 972b036, since the whole reason is now scrubbed before whitespace collapse and truncation. Both can be resolved. Not verified here: @limrun/api 0.69.x is not installed locally, so whether an instance client constructor can reject with the org SDK's NotFoundError was not read. The base caught NotFoundError around the whole app-log reconnect, but at head only the org get maps 404 to "missing", so a vanished instance between the get and the connect could surface as an instance failure. Live runs, the regression batch that failed 10 tests before the fixes, and the check:affected receipt are taken from the author's comment, and nothing was run locally. Peer credential-echo behavior was not observed live, and the fixes were checked by reading the code paths. |
Follow-up to the review at 972b036
Each finding had a focused failing assertion before its fix. The final focused runs passed 379 Limrun and forwarded-runner tests and 50 Apple runner tests. At Packed created-iOS rerunFresh core and Limrun tarballs at
The Xcode 27.1 simulator runner archive was reused from the prior smoke. The Swift runner sources and packaging scripts match the earlier head.
|
Apex Sentinel · ✅ Approve · review of
|
| Command | What it does |
|---|---|
@apex-sentinel-staging note <context> |
Adds context; Sentinel re-checks the cited code |
@apex-sentinel-staging pivot <why> |
Says the finding is wrong; Sentinel re-checks the cited code |
@apex-sentinel-staging like |
Marks the finding as useful |
@apex-sentinel-staging dislike <why> |
Marks it as not useful, so it is not raised again |
On this conversation, comment @apex-sentinel-staging review to run a full review once again.
Summary
Limrun leaves the core package. The runtime, connection, iOS runner orchestration, download and
@limrun/apimove to@agent-device/limrun(packages/provider-limrun), installed through the plugin manager. Core adds lazy device capabilities to every providersetuphost. Without the plugin,connect limrunanswersplugin-not-installedwith its install command. Part of #3311.Auth is unchanged from the base: a login is saved when it is approved. A cloud-discovered Limrun refusal therefore keeps that login; #4940 tracks it. Preflight edge cases: #4914.
Value
Validation
Head
eb28689b6a8bfb6f1ad371b5f59358c7f5b25e59. The affected gate passed all 43 runnable checks againstorigin/0.22withexactCommit: true. The full unit suite passed 22,240 tests. The value figures were measured on an earlier head.The packed CLI and Limrun plugin passed the created-iOS open, snapshot, and press rerun at this head. XCTest passed and the instance inventory was empty. Follow-up fixes and rerun. Prior created Android and token-only iOS evidence.