@skrr-ai/cli 0.1.10 → 0.1.12

package/dist/lib/daemon-setup.js

@@ -0,0 +1,103 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.offerDaemonSetup = offerDaemonSetup;
+/**
+ * daemon-setup.ts — offer to set this machine up, at the moment we can.
+ *
+ * ## Why login and not `npm install`
+ *
+ * The obvious way to remove a step is a `postinstall` that installs the daemon
+ * when the CLI is installed. It cannot work, and the reason is specific rather
+ * than aesthetic: installing the daemon BINDS it to a deployment and profile,
+ * taken from the CLI's session (`bindToCliSession`, OSK-279 — a daemon on a
+ * different deployment than its CLI is the failure that binding exists to
+ * prevent). At `npm install` time there is no session.
+ *
+ * It would not even fail loudly. With no config on disk `loadConfig()` returns
+ * DEFAULT_CONFIG, whose baseURL is the DEV deployment — so a postinstall would
+ * quietly bind the machine to dev, and the first `skrr login` against
+ * production would produce exactly the split. That is the default path on a
+ * clean machine, not an edge case.
+ *
+ * Login is the first moment the answer exists. It is also where the credential
+ * handoff already runs, so this is not a new path through the program; it is
+ * the branch where that path used to give up.
+ *
+ * ## Why it asks
+ *
+ * Signing in and "run a process on this machine that can execute bash, read and
+ * write files, and drive a browser" are not the same size of decision. Doing
+ * the second as a silent consequence of the first is the class of surprise this
+ * whole area has been removing. So: asked when there is someone to ask, skipped
+ * with an instruction when there is not, and never on the opt-out.
+ */
+const prompt_1 = require("./prompt");
+const daemon_binding_1 = require("./daemon-binding");
+const exec_oversky_1 = require("./exec-oversky");
+const daemon_installer_1 = require("./daemon-installer");
+const ssh_detect_1 = require("./ssh-detect");
+/**
+ * Ask, then install. Returns without touching anything when there is nobody to
+ * ask or the operator has opted out.
+ */
+async function offerDaemonSetup(opts = {}) {
+    const env = opts.env ?? process.env;
+    const log = opts.log ?? ((line) => console.log(line));
+    // The same switch that turns the credential handoff off. An operator who has
+    // said "do not touch my daemon" has not asked a narrower question, and a
+    // second variable for the same intent is a second thing to remember.
+    if (env.OVERSKY_SKIP_DAEMON_HANDOFF === '1' || env.SKRR_SKIP_DAEMON_HANDOFF === '1') {
+        return { status: 'skipped', detail: 'skipped by OVERSKY_SKIP_DAEMON_HANDOFF' };
+    }
+    const interactive = opts.interactive ?? !(0, ssh_detect_1.isNonInteractive)();
+    if (!interactive) {
+        // A prompt with no terminal hangs forever, which is worse than the extra
+        // step. Say which command does it instead.
+        return {
+            status: 'skipped',
+            detail: 'no terminal to ask — run `skrr daemon install` to set this machine up',
+        };
+    }
+    const confirmImpl = opts.confirmImpl ?? prompt_1.confirm;
+    log('');
+    log('  This machine has no skrr runtime. It is what lets your agents work here —');
+    log('  running commands, editing files, and driving a browser on this machine.');
+    const yes = await confirmImpl('  Set it up now?', false);
+    if (!yes) {
+        return {
+            status: 'declined',
+            detail: 'run `skrr daemon install` when you want it',
+        };
+    }
+    // Fetch the signed binary only when there is none. When the binary is already
+    // present and only the service is missing, this step is skipped entirely —
+    // downloading over a working runtime is not what "set it up" asked for.
+    const binaryPresent = opts.binaryPresent ?? Boolean((0, exec_oversky_1.findOverskyBinary)());
+    if (!binaryPresent) {
+        log('  Fetching the signed release...');
+        const fetched = await (0, daemon_installer_1.installDaemon)({ env });
+        if (!fetched.ok) {
+            return { status: 'failed', detail: fetched.error };
+        }
+        log(`  Installed skrrd ${fetched.version} (${fetched.platformKey})`);
+    }
+    // Register the OS service, bound to the deployment and profile of the session
+    // that just authenticated — which is the whole reason this runs here and not
+    // at install time.
+    try {
+        const code = await (0, exec_oversky_1.execOversky)(['install', ...(0, daemon_binding_1.bindToCliSession)([])]);
+        if (code !== 0) {
+            return { status: 'failed', detail: `\`skrrd install\` exited ${code}` };
+        }
+    }
+    catch (err) {
+        if (err.message === 'oversky-not-installed') {
+            return {
+                status: 'failed',
+                detail: 'the runtime vanished between fetching and installing it',
+            };
+        }
+        return { status: 'failed', detail: err.message };
+    }
+    return { status: 'installed', detail: 'this machine is set up' };
+}

package/dist/lib/daemonBroker.d.ts

@@ -80,6 +80,12 @@ export interface DaemonBrokerResult {
     cliId: string;
     userId: string;
     email: string | null;
+    /**
+     * The refresh family this credential belongs to, named so the caller can
+     * retire its predecessors AFTER persisting it. Absent on servers that predate
+     * the mint/confirm split, where the mint still revoked eagerly.
+     */
+    familyId?: string;
 }
 /**
  * Explicit reasons the broker path could fail. These exist to keep the
@@ -87,7 +93,7 @@ export interface DaemonBrokerResult {
  * fall through to PKCE; `ci_token_refused` is the one we surface
  * because re-driving it via PKCE would not change the outcome.
  */
-export type DaemonBrokerErrorReason = 'no_bootstrap' | 'stale_bootstrap' | 'bootstrap_parse' | 'base_url_mismatch' | 'daemon_not_authed' | 'ci_token_refused' | 'server_error' | 'network' | 'timeout' | 'unknown';
+export type DaemonBrokerErrorReason = 'no_bootstrap' | 'stale_bootstrap' | 'bootstrap_parse' | 'base_url_mismatch' | 'daemon_not_authed' | 'ci_token_refused' | 'rate_limited' | 'server_error' | 'network' | 'timeout' | 'unknown';
 export interface DaemonBrokerFailure {
     ok: false;
     reason: DaemonBrokerErrorReason;

package/dist/lib/daemonBroker.js

@@ -351,6 +351,22 @@ async function attemptDaemonBrokerLogin(opts) {
         if (response.status === 503 && code === 'DAEMON_NOT_AUTHED') {
             return { ok: false, reason: 'daemon_not_authed', detail: message, status: 503, code };
         }
+        // 429 is TRANSIENT and its remedy is time, which makes it the one failure
+        // here that a fall-through cannot substitute for. Left in the `unknown`
+        // bucket it fell silently through to PKCE, and in a non-interactive shell
+        // that surfaced as "skrr login requires an interactive terminal" — a
+        // sentence about the wrong thing entirely. Reachable in the ordinary way: a
+        // cold machine running several skrr commands at once has every process
+        // brokering, because none of them has a token yet.
+        if (response.status === 429) {
+            return {
+                ok: false,
+                reason: 'rate_limited',
+                detail: message,
+                status: 429,
+                ...(code ? { code } : {}),
+            };
+        }
         if (response.status === 400 && code === 'BASE_URL_MISMATCH') {
             // Older daemon binary that lacked the bootstrap.serverUrl field
             // ended up here despite the CLI sending baseURL. Treat as the
@@ -397,8 +413,52 @@ async function attemptDaemonBrokerLogin(opts) {
         cliId: parsedBody.cliId,
         userId: parsedBody.userId,
         email: parsedBody.email ?? null,
+        ...(typeof parsedBody.familyId === 'string' ? { familyId: parsedBody.familyId } : {}),
     };
 }
+/** Bound the confirm so a slow server cannot stall a login that already worked. */
+const CONFIRM_TIMEOUT_MS = 10_000;
+/**
+ * Retire the cli credentials this one replaces — after it is on disk, never
+ * before.
+ *
+ * The mint deliberately no longer does this. Between the server's response and
+ * the credential being usable there are two more hops (the daemon's loopback
+ * broker forwarding the body, this process writing it to the keychain), and a
+ * failure at either one used to leave the user with no working cli credential at
+ * all, recoverable only by a full browser login.
+ *
+ * Called with the NEW access token explicitly rather than through the shared
+ * client. That is the point rather than a detail: the route refuses unless the
+ * bearer's own `did` claim is the cliId being swept, so this call is not a claim
+ * that the delivery happened — it is a demonstration that it did.
+ *
+ * Best-effort and silent. The credential is already persisted and working by the
+ * time this runs; a failure leaves one extra live family, which the server's
+ * session cap bounds and the next confirm sweeps.
+ */
+async function confirmCliHandoff(opts) {
+    const controller = new AbortController();
+    const timer = setTimeout(() => controller.abort(), CONFIRM_TIMEOUT_MS);
+    try {
+        await fetch(`${opts.serverOrigin}/api/daemons/cli-handoff/confirm`, {
+            method: 'POST',
+            headers: {
+                Authorization: `Bearer ${opts.accessToken}`,
+                'Content-Type': 'application/json',
+                Accept: 'application/json',
+            },
+            body: JSON.stringify({ cliId: opts.cliId, familyId: opts.familyId }),
+            signal: controller.signal,
+        });
+    }
+    catch {
+        /* bookkeeping — the credential is already delivered */
+    }
+    finally {
+        clearTimeout(timer);
+    }
+}
 /**
  * Helper: coerce an ISO-string or numeric expiry to epoch ms for
  * `writeToBackend`. Returns undefined on missing / unparseable input.
@@ -436,6 +496,17 @@ async function attemptDaemonBrokerLoginAndPersist(opts) {
             ? { refreshExpiresAt: expiryToEpochMs(outcome.refreshExpiresAt) }
             : {}),
     }, { serverOrigin, clearReauth: true });
+    // Only now: the credential is on disk, so "the predecessor dies iff the
+    // replacement is in place" holds. A server that predates the split ships no
+    // `familyId` and has already revoked eagerly — nothing to do there.
+    if (outcome.familyId) {
+        await confirmCliHandoff({
+            serverOrigin,
+            accessToken: outcome.accessToken,
+            cliId: outcome.cliId,
+            familyId: outcome.familyId,
+        });
+    }
     return outcome;
 }
 // ---------------------------------------------------------------------

package/dist/lib/daemonHandoff.d.ts

@@ -0,0 +1,47 @@
+/**
+ * Hand the local daemon a credential of its own, right after `skrr login`.
+ *
+ * The inverse of the daemon-as-broker path that already ships. That one lets an
+ * authenticated DAEMON mint a cli-scope credential so the CLI can skip the
+ * browser; this lets an authenticated HUMAN mint a daemon-scope one so the
+ * machine is logged in by the same act. The direction added here is the safer of
+ * the two: daemon scope is deliberately lower-privileged than cli scope
+ * (`requireHumanScope` refuses it from billing, account management, password
+ * change and deletion), so this is a de-escalation, while the shipping direction
+ * is an escalation.
+ *
+ * Design record: docs/architecture/machine-login-broker-inversion-2026-09-03.md
+ *
+ * Three properties are deliberate:
+ *
+ *   - **Best-effort, never fatal.** `skrr login` has already SUCCEEDED by the time
+ *     this runs. A failure here must not fail the login or discard the credential
+ *     the user just earned — it degrades to exactly the old behaviour, with a hint.
+ *   - **Skipped when no daemon service is installed.** There is nothing to hand a
+ *     credential to, and minting one anyway leaves an orphaned daemon-scope family
+ *     on the account. A binary on PATH is not a service, so this is decided by the
+ *     daemon's own answer about where its id came from — not by whether `skrrd`
+ *     exists.
+ *   - **The bundle goes over STDIN**, never a file. It is a live credential; a temp
+ *     file would put it at rest with a lifetime nobody owns.
+ *   - **The predecessor is retired only after the new credential is written.** The
+ *     mint no longer revokes anything; `confirmDaemonHandoff` does, once the daemon
+ *     has accepted. So a handoff that fails leaves the machine exactly as it was,
+ *     rather than signed out.
+ */
+export interface DaemonHandoffOutcome {
+    status: 'delivered' | 'skipped' | 'failed';
+    detail: string;
+    /**
+     * Why it skipped, for a caller that must act on the difference.
+     *
+     * `detail` is a sentence for a human and is expected to be reworded; the
+     * caller deciding whether to OFFER TO INSTALL a daemon cannot key off that.
+     * The two absent cases are separated because they need different work — one
+     * needs a binary fetched, the other only needs the service registered.
+     */
+    reason?: 'opted-out' | 'brokered' | 'no-binary' | 'unsupported-daemon' | 'no-service';
+}
+export declare function handOffToLocalDaemon(env?: NodeJS.ProcessEnv, opts?: {
+    loginFlow?: string;
+}): Promise<DaemonHandoffOutcome>;

package/dist/lib/daemonHandoff.js

@@ -0,0 +1,304 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.handOffToLocalDaemon = handOffToLocalDaemon;
+const node_child_process_1 = require("node:child_process");
+const data_provider_1 = require("@skrr-ai/data-provider");
+const config_1 = require("./config");
+const exec_oversky_1 = require("./exec-oversky");
+const keychain_1 = require("./keychain");
+/**
+ * Ceilings, not expectations. Both calls finish in milliseconds when anything is
+ * working; these exist so that when something is NOT working the login ends.
+ *
+ * The failure this prevents is the worst one available here: `skrr login` has
+ * already printed "Login successful", and an unbounded wait on a child process
+ * leaves the user staring at a terminal that will never return, with no way to
+ * tell a hung handoff from a slow one. A blocked keychain prompt, a daemon
+ * binary wedged on a lock, an NFS home directory — none of them are exotic, and
+ * all of them used to hang the command.
+ *
+ * The accept side gets the longer budget because it may have to unlock a
+ * keychain. Killing it mid-write is the cost, and it is the lesser one: the
+ * credential write is a few milliseconds at the end of that window, so a timeout
+ * overwhelmingly lands BEFORE it rather than during it, and `skrr daemon login`
+ * recovers either way.
+ */
+const PROBE_TIMEOUT_MS = 15_000;
+const ACCEPT_TIMEOUT_MS = 60_000;
+function runOversky(binary, args, opts) {
+    const { input, timeoutMs } = opts;
+    return new Promise((resolve) => {
+        // A Windows npm-global install ships a `.cmd` shim, which `spawn` cannot
+        // execute without a shell — Node fires ENOENT instead. `execOversky` has
+        // handled this since it was written; this function did not, so the handoff
+        // failed on EVERY Windows login and reported it as the daemon refusing the
+        // bundle. Restricted to the shim case so real binaries keep the argv-array
+        // exec path, which needs no quoting rules to be right.
+        const isWinShim = process.platform === 'win32' && /\.(cmd|bat)$/i.test(binary);
+        const child = (0, node_child_process_1.spawn)(binary, args, {
+            // stderr is CAPTURED, not discarded. Discarding it cost a debugging cycle
+            // on the first real run: the daemon exited non-zero with
+            // `OVERSKY_KEK_REQUIRED`, and all the user saw was "the daemon refused the
+            // handoff" — an outcome with its reason thrown away. A wrapper that hides
+            // the wrapped program's error is worse than one that does not wrap.
+            stdio: [input === undefined ? 'ignore' : 'pipe', 'pipe', 'pipe'],
+            ...(isWinShim ? { shell: true } : {}),
+        });
+        let stdout = '';
+        let stderr = '';
+        let settled = false;
+        const settle = (value) => {
+            if (settled)
+                return;
+            settled = true;
+            clearTimeout(timer);
+            resolve(value);
+        };
+        const timer = setTimeout(() => {
+            child.kill('SIGKILL');
+            settle({
+                ok: false,
+                stdout,
+                stderr: `timed out after ${Math.round(timeoutMs / 1000)}s`,
+            });
+        }, timeoutMs);
+        // Never hold the event loop open on the timer alone.
+        if (typeof timer.unref === 'function')
+            timer.unref();
+        child.stdout?.on('data', (c) => (stdout += String(c)));
+        child.stderr?.on('data', (c) => (stderr += String(c)));
+        child.on('error', (err) => settle({ ok: false, stdout, stderr: err.message }));
+        child.on('close', (code) => settle({ ok: code === 0, stdout, stderr }));
+        if (input !== undefined) {
+            // An EPIPE here is the child having already exited — its own exit code and
+            // stderr are the real diagnosis, and an unhandled stream error would
+            // instead crash the CLI one line after a successful login.
+            child.stdin?.on('error', () => {
+                /* reported by the close handler */
+            });
+            child.stdin?.end(input);
+        }
+    });
+}
+/**
+ * The profile flags to pass to `skrrd`, so both spawns land in the same tenancy
+ * the CLI is signed in to.
+ *
+ * A profile is the daemon's tenancy boundary — separate config, state, keychain
+ * namespace and service label. The CLI resolves its own; the daemon resolves its
+ * own, from `--profile` → `OVERSKY_PROFILE` → its `profile.lock` → `default`.
+ * Passing nothing let those two answers differ, and the failure was silent in the
+ * damaging direction: `skrr --profile work login` would mint against the id
+ * printed by whichever profile the daemon's lock happened to name, then write a
+ * work-profile credential over THAT profile's store.
+ *
+ * `skrr daemon login` already binds the profile this way (`bindToCliSession`);
+ * this is the same rule for the path that runs without being asked.
+ */
+function profileArgs() {
+    const profile = (0, keychain_1.getActiveProfile)();
+    return profile && profile !== keychain_1.DEFAULT_PROFILE ? ['--profile', profile] : [];
+}
+/**
+ * Parse the machine-readable line `accept-handoff --print-id` writes to stderr.
+ *
+ * Absent on a daemon that predates it, which is a normal state during a rollout
+ * and not an error — the caller degrades to the older, less careful behaviour
+ * rather than refusing.
+ */
+function parseIdProvenance(stderr) {
+    const line = stderr.split('\n').find((l) => l.includes('skrrd:accept-handoff'));
+    if (!line)
+        return {};
+    const idSource = /id-source=([A-Za-z0-9._:-]+)/.exec(line)?.[1];
+    const machineUuid = /machine-uuid=([A-Za-z0-9._:-]+)/.exec(line)?.[1];
+    // Any non-space run: this one is a URL, and a URL contains characters the
+    // other two never do.
+    const daemonServer = /server=(\S+)/.exec(line)?.[1];
+    return { idSource, machineUuid, daemonServer };
+}
+/**
+ * What actually changed on this machine, said out loud.
+ *
+ * A handoff can re-point the machine to a different ACCOUNT (you signed in as
+ * someone else) or a different DEPLOYMENT (your daemon was on dev, your CLI is
+ * on prod). Both are the feature working — the machine follows the human, and
+ * moving a dev-bound daemon to prod is the exact story this path was written for
+ * — and both are state changes an operator should watch happen rather than
+ * discover later, when a daemon they thought was on dev answers from prod.
+ *
+ * Degrades cleanly: an older server sends no account, an older daemon reports no
+ * server, and the sentence simply says less rather than guessing.
+ */
+function describeDelivery(opts) {
+    const parts = [];
+    parts.push(opts.accountLabel
+        ? `now signed in as ${opts.accountLabel} on ${(0, config_1.describeDeployment)(opts.cliBaseURL)}`
+        : 'the local daemon now has its own credential');
+    if (opts.daemonServer &&
+        canonicalServer(opts.daemonServer) !== canonicalServer(opts.cliBaseURL)) {
+        parts.push(`moved from ${(0, config_1.describeDeployment)(opts.daemonServer)}`);
+    }
+    return parts.join(', ');
+}
+/**
+ * Compare deployments, not spellings.
+ *
+ * `https://oversky.ai` and `https://skrr.ai` are one deployment under two names,
+ * and the first is still what every daemon installed before the cutover carries.
+ * Trimming and lowercasing alone would report a move on every login from every
+ * one of those machines — a warning that is wrong for the largest group of users
+ * who would see it, which is how a signal becomes noise. `canonicalizeKnownBaseURL`
+ * is the fold the rest of the CLI already compares through.
+ */
+function canonicalServer(url) {
+    return (0, config_1.canonicalizeKnownBaseURL)(url).trim().replace(/\/+$/, '').toLowerCase();
+}
+/** The most useful line of a failure, so a remedy can name the cause. */
+function firstMeaningfulLine(text) {
+    const line = text
+        .split('\n')
+        .map((l) => l.trim())
+        .find((l) => l &&
+        !l.startsWith('at ') &&
+        !/^[{}]/.test(l) &&
+        // The provenance line is a protocol between these two programs, not a
+        // diagnosis. Reporting it as one would answer "why did this fail?" with
+        // a machine's own bookkeeping.
+        !l.includes('skrrd:accept-handoff'));
+    return line ? line.slice(0, 160) : 'no output';
+}
+async function handOffToLocalDaemon(env = process.env, opts = {}) {
+    // Mirrors `OVERSKY_SKIP_DAEMON_BROKER` on the other direction. An operator
+    // deliberately running a daemon against a different deployment than their CLI is
+    // doing a legitimate thing, and this must not overrule it.
+    if (env.OVERSKY_SKIP_DAEMON_HANDOFF === '1' || env.SKRR_SKIP_DAEMON_HANDOFF === '1') {
+        return {
+            status: 'skipped',
+            reason: 'opted-out',
+            detail: 'skipped by OVERSKY_SKIP_DAEMON_HANDOFF',
+        };
+    }
+    // The daemon brokered this login, which means it just used its OWN credential
+    // against this server and that credential works. There is nothing to fix.
+    //
+    // Running anyway is not merely redundant, it is destructive: it mints a
+    // replacement, writes it over the working one, revokes the family the daemon is
+    // authenticated with, and restarts the process — killing whatever sessions it
+    // was running. `skrr login` on a healthy machine is the path where the least
+    // should happen, and it was the path where the most did.
+    if (opts.loginFlow === 'daemon-broker') {
+        return {
+            status: 'skipped',
+            reason: 'brokered',
+            detail: 'the local daemon brokered this login, so it already has a working credential',
+        };
+    }
+    const binary = (0, exec_oversky_1.findOverskyBinary)();
+    if (!binary) {
+        return { status: 'skipped', reason: 'no-binary', detail: 'no local daemon installed' };
+    }
+    // An older daemon has no `accept-handoff`, and spawning it would fail with
+    // commander's "unknown command" rather than anything a reader could act on. A
+    // CLI that outruns the daemon on the machine is the normal case during a
+    // staged rollout, not an error.
+    const supported = await (0, exec_oversky_1.overskySupportsSubcommand)('accept-handoff');
+    if (supported === false) {
+        return {
+            status: 'skipped',
+            reason: 'unsupported-daemon',
+            detail: 'the installed daemon predates `accept-handoff`; run `skrr daemon login` once',
+        };
+    }
+    // Ask the daemon which id it will bind, rather than deriving it here. The id
+    // comes from cwd + profile, and a second copy of that derivation in the CLI
+    // would drift — producing a credential minted for a daemon that does not exist,
+    // which is indistinguishable from a login that simply did not work.
+    const printed = await runOversky(binary, ['accept-handoff', '--print-id', ...profileArgs()], {
+        timeoutMs: PROBE_TIMEOUT_MS,
+    });
+    const daemonId = printed.ok ? printed.stdout.trim() : '';
+    if (!daemonId) {
+        return {
+            status: 'failed',
+            detail: `could not read the local daemon id — ${firstMeaningfulLine(printed.stderr)}`,
+        };
+    }
+    const { idSource, machineUuid, daemonServer } = parseIdProvenance(printed.stderr);
+    // A well-formed id is not the same as a real daemon. With no service installed
+    // the daemon derives one from whatever directory this process is in, so the id
+    // above names a daemon that does not exist and will not exist under that id if
+    // one is ever installed from a different directory. Minting for it leaves an
+    // orphaned daemon-scope family on the account and hands the credential to
+    // nothing — which is the case the design record says to skip, and which the
+    // binary-presence check alone never detected because a binary on PATH is not a
+    // service.
+    //
+    // Only a daemon that reports its provenance can be skipped this way. An older
+    // one says nothing, and is left on the previous behaviour rather than refused.
+    if (idSource === 'cwd') {
+        return {
+            status: 'skipped',
+            reason: 'no-service',
+            detail: 'no daemon service is installed on this machine',
+        };
+    }
+    let bundle;
+    try {
+        bundle = (await data_provider_1.dataService.mintDaemonHandoff({
+            daemonId,
+            ...(machineUuid ? { machineUuid } : {}),
+        }));
+    }
+    catch (err) {
+        return { status: 'failed', detail: err.message };
+    }
+    const payload = JSON.stringify({
+        refreshToken: bundle.refreshToken,
+        refreshExpiresAt: bundle.refreshExpiresAt,
+        serverUrl: (0, config_1.loadConfig)().baseURL,
+        daemonId,
+    });
+    // No restart from here. `accept-handoff` runs the runtime's own
+    // `restartDisconnectedServiceAfterLogin` after it writes the credential — the
+    // same reconcile every other credential-write path in the daemon uses — and it
+    // is the better of the two: it checks that a service is installed and running,
+    // refuses to yank a daemon another profile owns, and gives the in-process
+    // watcher a window to converge before reaching for the heavy hammer.
+    //
+    // A second restart out here does not add a guarantee, it adds an outage. Each
+    // one kills in-flight Claude/Codex sessions and browser CDP attachments, and
+    // the second would land on a process that is seconds into starting up.
+    const accepted = await runOversky(binary, ['accept-handoff', ...profileArgs()], {
+        input: payload,
+        timeoutMs: ACCEPT_TIMEOUT_MS,
+    });
+    if (!accepted.ok) {
+        // Deliberately NOT confirming. The machine still holds the credential it had
+        // before this ran, and it still works — the mint no longer revokes anything,
+        // so the cost of a refused handoff is one unused family that the next
+        // successful login sweeps, rather than a signed-out machine.
+        return { status: 'failed', detail: firstMeaningfulLine(accepted.stderr) };
+    }
+    // Only now is the predecessor retired: the daemon has written the new
+    // credential to its own store, so "the old one dies iff the new one is in
+    // place" holds. Best-effort — a confirm that does not land leaves one extra
+    // live family, bounded by the server's concurrent-session cap and swept by the
+    // next confirm, which is a far cheaper failure than the one it replaces.
+    if (bundle.familyId) {
+        try {
+            await data_provider_1.dataService.confirmDaemonHandoff({ daemonId, familyId: bundle.familyId });
+        }
+        catch {
+            /* the credential is delivered; the sweep is bookkeeping */
+        }
+    }
+    return {
+        status: 'delivered',
+        detail: describeDelivery({
+            accountLabel: bundle.accountLabel,
+            daemonServer,
+            cliBaseURL: (0, config_1.loadConfig)().baseURL,
+        }),
+    };
+}

package/dist/lib/exec-oversky.d.ts

@@ -1,5 +1,35 @@
 /** Runtime binary names, current first. */
 export declare const RUNTIME_BINARY_NAMES: readonly ["skrrd", "oversky"];
+/**
+ * The sentence a `skrr daemon` pass-through appends to its description.
+ *
+ * OSK-296 made these commands forward their flags to `skrrd` instead of
+ * rejecting them, and stopped there. oclif renders the FLAGS section of help
+ * from a command's declared flags, and a pass-through declares none — so help
+ * kept describing the old, broken behaviour where these commands took nothing,
+ * while `skrr daemon status --profile work` quietly worked. The entire flag
+ * surface of the wrapped binary became reachable and undiscoverable in the
+ * same commit.
+ *
+ * `skrr code` hit this first and fixed BOTH halves: its description says out
+ * loud that engine flags are not listed there and where to find them. This is
+ * that sentence, for the other wrapper, in one place so eight commands cannot
+ * drift into eight wordings.
+ *
+ * It names `skrrd --help` separately because `--profile` is a GLOBAL option on
+ * the runtime, so a reader sent only to the subcommand's help would not find
+ * the flag they are most likely to want.
+ *
+ * This is a command's `description`, and each command keeps a short `summary`
+ * beside it. oclif renders `summary` in the topic listing and `description`
+ * only in the command's own help, so the note reaches someone asking about
+ * THIS command without turning `skrr daemon --help` into eight paragraphs of
+ * the same boilerplate — which is what it did when this text was appended to
+ * `description` alone.
+ */
+export declare function forwardedFlagsNote(verb: string, opts?: {
+    binds?: boolean;
+}): string;
 /** Resolve the absolute path of `oversky` if it exists, else return null. */
 export declare function findOverskyBinary(): string | null;
 /**

package/dist/lib/exec-oversky.js

@@ -4,6 +4,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 };
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.RUNTIME_BINARY_NAMES = void 0;
+exports.forwardedFlagsNote = forwardedFlagsNote;
 exports.findOverskyBinary = findOverskyBinary;
 exports.notInstalledMessage = notInstalledMessage;
 exports.execOversky = execOversky;
@@ -31,6 +32,46 @@ const node_fs_1 = require("node:fs");
 const node_path_1 = __importDefault(require("node:path"));
 /** Runtime binary names, current first. */
 exports.RUNTIME_BINARY_NAMES = ['skrrd', 'oversky'];
+/**
+ * The sentence a `skrr daemon` pass-through appends to its description.
+ *
+ * OSK-296 made these commands forward their flags to `skrrd` instead of
+ * rejecting them, and stopped there. oclif renders the FLAGS section of help
+ * from a command's declared flags, and a pass-through declares none — so help
+ * kept describing the old, broken behaviour where these commands took nothing,
+ * while `skrr daemon status --profile work` quietly worked. The entire flag
+ * surface of the wrapped binary became reachable and undiscoverable in the
+ * same commit.
+ *
+ * `skrr code` hit this first and fixed BOTH halves: its description says out
+ * loud that engine flags are not listed there and where to find them. This is
+ * that sentence, for the other wrapper, in one place so eight commands cannot
+ * drift into eight wordings.
+ *
+ * It names `skrrd --help` separately because `--profile` is a GLOBAL option on
+ * the runtime, so a reader sent only to the subcommand's help would not find
+ * the flag they are most likely to want.
+ *
+ * This is a command's `description`, and each command keeps a short `summary`
+ * beside it. oclif renders `summary` in the topic listing and `description`
+ * only in the command's own help, so the note reaches someone asking about
+ * THIS command without turning `skrr daemon --help` into eight paragraphs of
+ * the same boilerplate — which is what it did when this text was appended to
+ * `description` alone.
+ */
+function forwardedFlagsNote(verb, opts = {}) {
+    const base = `Flags are forwarded to \`skrrd ${verb}\` unchanged, so they are not listed here —` +
+        ` run \`skrrd ${verb} --help\` for this verb's own flags, or \`skrrd --help\` for` +
+        ' global ones such as `--profile`.';
+    // `install` and `login` are not pure pass-throughs: they fill in the server
+    // and profile from the CLI's own session when the caller named neither, so a
+    // daemon cannot silently end up on a different deployment than the CLI that
+    // installed it (OSK-279). Saying so is the difference between a flag you may
+    // pass and a flag that is already being passed for you.
+    return opts.binds
+        ? `${base} \`--server\` and \`--profile\` are filled in from your CLI session unless you pass them.`
+        : base;
+}
 /** Extra well-known install locations to check when PATH lookup misses. */
 const FALLBACK_PATHS = exports.RUNTIME_BINARY_NAMES.flatMap((name) => [
     `/opt/homebrew/bin/${name}`,