@skrr-ai/cli 0.1.11 → 0.1.12

package/dist/commands/daemon/install.d.ts

@@ -10,6 +10,20 @@ import { Command } from '@oclif/core';
  * A thin proxy, like every other verb here: the service-management logic stays
  * in the runtime, which is the only component that knows its own service label
  * on each platform.
+ *
+ * WITH ONE ADDITION: it fetches the runtime first when there isn't one.
+ *
+ * Before that, this command refused with "install it with brew" whenever
+ * `skrrd` was absent — so the command whose entire job is to set the machine up
+ * required the machine to already be set up, and onboarding's first step was a
+ * second install from a second distribution channel, before the user had signed
+ * in or seen anything work. npm is the front door: `npm i -g @skrr-ai/cli`
+ * gives you `skrr`, and `skrr daemon install` gets the daemon.
+ *
+ * The download is verified against the same pinned ed25519 keys the daemon's
+ * own self-updater uses — see `daemon-installer.ts`. It is deliberately NOT a
+ * silent side effect: the fetch is announced, because a command that installs
+ * an executable should say so.
  */
 export default class DaemonInstall extends Command {
     static aliases: string[];

package/dist/commands/daemon/install.js

@@ -3,6 +3,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
 const core_1 = require("@oclif/core");
 const exec_oversky_1 = require("../../lib/exec-oversky");
 const daemon_binding_1 = require("../../lib/daemon-binding");
+const daemon_installer_1 = require("../../lib/daemon-installer");
 /**
  * `skrr daemon install` — install the local runtime's OS service.
  *
@@ -14,6 +15,20 @@ const daemon_binding_1 = require("../../lib/daemon-binding");
  * A thin proxy, like every other verb here: the service-management logic stays
  * in the runtime, which is the only component that knows its own service label
  * on each platform.
+ *
+ * WITH ONE ADDITION: it fetches the runtime first when there isn't one.
+ *
+ * Before that, this command refused with "install it with brew" whenever
+ * `skrrd` was absent — so the command whose entire job is to set the machine up
+ * required the machine to already be set up, and onboarding's first step was a
+ * second install from a second distribution channel, before the user had signed
+ * in or seen anything work. npm is the front door: `npm i -g @skrr-ai/cli`
+ * gives you `skrr`, and `skrr daemon install` gets the daemon.
+ *
+ * The download is verified against the same pinned ed25519 keys the daemon's
+ * own self-updater uses — see `daemon-installer.ts`. It is deliberately NOT a
+ * silent side effect: the fetch is announced, because a command that installs
+ * an executable should say so.
  */
 class DaemonInstall extends core_1.Command {
     // `skrr daemons <sub>` — the plural is advertised as an alias for the
@@ -34,6 +49,24 @@ class DaemonInstall extends core_1.Command {
         // own comment records `skrr code run -m <model>` dying the same way. Same
         // mistake, one directory over.
         const argv = this.argv;
+        // Bootstrap only when there is nothing to forward to. An existing runtime —
+        // brew, the script installer, a dev checkout — is left exactly alone; this
+        // is a floor under the missing case, not a second update channel competing
+        // with the daemon's own.
+        if (!(0, exec_oversky_1.findOverskyBinary)()) {
+            this.log('No local skrr runtime found. Fetching the signed release...');
+            const outcome = await (0, daemon_installer_1.installDaemon)();
+            if (!outcome.ok) {
+                this.log('');
+                this.log(`  Could not install the runtime: ${outcome.error}`);
+                this.log('');
+                this.log('  You can install it directly instead:');
+                this.log('    macOS:   brew install dush1023/oversky/oversky');
+                this.log('    Linux:   curl -fsSL https://raw.githubusercontent.com/dush1023/OverSky/main/scripts/install-daemon.sh | bash');
+                this.exit(1);
+            }
+            this.log(`  Installed skrrd ${outcome.version} (${outcome.platformKey}) at ${outcome.binaryPath}`);
+        }
         try {
             // Bind the new daemon to the deployment and profile the CLI is on,
             // for whichever of those the user did not state. Installing is the
@@ -45,7 +78,10 @@ class DaemonInstall extends core_1.Command {
         }
         catch (err) {
             if (err.message === 'oversky-not-installed') {
-                this.log((0, exec_oversky_1.notInstalledMessage)());
+                // Reachable only if the runtime vanished between the bootstrap above
+                // and this line. Saying so beats repeating install instructions for
+                // something that was just installed.
+                this.log('The skrr runtime disappeared between installing it and running it.');
                 this.exit(127);
             }
             throw err;

package/dist/commands/login.js

@@ -5,6 +5,7 @@ const data_provider_1 = require("@skrr-ai/data-provider");
 const auth_core_1 = require("@skrr-ai/auth-core");
 const base_command_1 = require("../base-command");
 const daemonHandoff_1 = require("../lib/daemonHandoff");
+const daemon_setup_1 = require("../lib/daemon-setup");
 const config_1 = require("../lib/config");
 const keychain_1 = require("../lib/keychain");
 const login_1 = require("../lib/login");
@@ -179,7 +180,29 @@ class Login extends base_command_1.BaseCommand {
                 // and a failure here must not fail it or discard what the user just earned.
                 // It degrades to exactly the old behaviour, with a hint naming the command
                 // that finishes the job.
-                const handoff = await (0, daemonHandoff_1.handOffToLocalDaemon)(process.env, { loginFlow: result.flow });
+                let handoff = await (0, daemonHandoff_1.handOffToLocalDaemon)(process.env, { loginFlow: result.flow });
+                // Nothing to hand a credential TO. This is the first moment we can fix
+                // that correctly — installing the daemon binds it to a deployment and a
+                // profile, and until this login there was no session to take them from.
+                // Keyed off `reason` rather than the sentence in `detail`, which is
+                // written for a person and expected to be reworded.
+                if (handoff.reason === 'no-binary' || handoff.reason === 'no-service') {
+                    const setup = await (0, daemon_setup_1.offerDaemonSetup)({
+                        binaryPresent: handoff.reason === 'no-service',
+                        log: (line) => this.log(line),
+                    });
+                    if (setup.status === 'installed') {
+                        // Re-run rather than duplicating the mint here: it is the same act
+                        // it always was, and now it has somewhere to land.
+                        handoff = await (0, daemonHandoff_1.handOffToLocalDaemon)(process.env, { loginFlow: result.flow });
+                    }
+                    else if (setup.status === 'failed') {
+                        this.log(`Could not set up the runtime: ${setup.detail}.`);
+                    }
+                    else {
+                        this.log(`This machine is not set up — ${setup.detail}.`);
+                    }
+                }
                 if (handoff.status === 'delivered') {
                     this.log(`The local daemon was signed in too — ${handoff.detail}.`);
                 }

package/dist/lib/daemon-installer.d.ts

@@ -0,0 +1,62 @@
+import { type DaemonVersionManifest, type ReleaseKey } from '@skrr-ai/auth-core';
+/** Public CloudFront feed. Mirrors the daemon's own `CLOUDFRONT_FEED_BASE`. */
+export declare const DEFAULT_DAEMON_FEED_BASE = "https://updates.oversky.ai/daemon";
+/** Same override the daemon honours, so one env var steers both. */
+export declare const DAEMON_FEED_BASE_ENV = "OVERSKY_DAEMON_UPDATE_FEED_BASE";
+export type DaemonInstallFailureCode = 'unsupported_platform' | 'manifest_unreachable' | 'manifest_malformed' | 'manifest_unsigned' | 'platform_missing' | 'untrusted_artifact_origin' | 'download_failed' | 'checksum_mismatch' | 'artifact_unsigned' | 'write_failed';
+export type DaemonInstallResult = {
+    ok: true;
+    version: string;
+    platformKey: string;
+    binaryPath: string;
+} | {
+    ok: false;
+    code: DaemonInstallFailureCode;
+    error: string;
+};
+export interface DaemonInstallOptions {
+    env?: NodeJS.ProcessEnv;
+    /** Override the feed root. Tests point this at a local fixture server. */
+    feedBase?: string;
+    /** Injected for tests; defaults to global fetch. */
+    fetchImpl?: typeof fetch;
+    /**
+     * Trust anchors. Defaults to the pinned production set; tests substitute a
+     * generated keypair, exactly as the sky-code installer does. Passing an EMPTY
+     * set does not disable verification here — every non-`ok` verdict is a
+     * refusal, so an unconfigured trust root turns installs off rather than
+     * turning checking off.
+     */
+    keys?: readonly ReleaseKey[];
+}
+export declare function daemonFeedBase(env?: NodeJS.ProcessEnv): string;
+/**
+ * Where the fetched binary lands. `exec-oversky.ts` already looks here, so a
+ * daemon installed by this path is found by every `skrr daemon *` command
+ * without the user touching PATH.
+ */
+export declare function daemonBinaryPath(env?: NodeJS.ProcessEnv): string;
+/**
+ * `<platform>-<arch>`, the manifest's `platforms` key. Returns null for a
+ * combination the release does not build, which is a clearer refusal than a
+ * missing-key lookup one step later.
+ */
+export declare function daemonPlatformKey(platform?: string, arch?: string): string | null;
+/**
+ * True when `candidate` may serve an artifact for a feed rooted at `feedBase`.
+ * Same rule as the daemon's `isTrustedArtifactOrigin`: a signed manifest still
+ * does not get to point the download at another origin.
+ */
+export declare function isTrustedArtifactOrigin(candidate: string, feedBase: string): boolean;
+/** Fetch `<feedBase>/latest/daemon-version.json` and verify its signature. */
+export declare function fetchVerifiedDaemonManifest(opts?: DaemonInstallOptions): Promise<{
+    ok: true;
+    manifest: DaemonVersionManifest;
+} | (DaemonInstallResult & {
+    ok: false;
+})>;
+/**
+ * Download, verify and install the daemon binary. Returns a tagged result; it
+ * never throws, so the caller can render one refusal for every failure mode.
+ */
+export declare function installDaemon(opts?: DaemonInstallOptions): Promise<DaemonInstallResult>;

package/dist/lib/daemon-installer.js

@@ -0,0 +1,247 @@
+"use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.DAEMON_FEED_BASE_ENV = exports.DEFAULT_DAEMON_FEED_BASE = void 0;
+exports.daemonFeedBase = daemonFeedBase;
+exports.daemonBinaryPath = daemonBinaryPath;
+exports.daemonPlatformKey = daemonPlatformKey;
+exports.isTrustedArtifactOrigin = isTrustedArtifactOrigin;
+exports.fetchVerifiedDaemonManifest = fetchVerifiedDaemonManifest;
+exports.installDaemon = installDaemon;
+/**
+ * daemon-installer.ts — fetch, verify and place the signed `skrrd` binary.
+ *
+ * ## Why this exists
+ *
+ * `skrr daemon install` forwarded to `skrrd install`, and `findOverskyBinary()`
+ * refused with "install it with brew" when there was no `skrrd` to forward to.
+ * So the one command whose job is to set the machine up required the machine to
+ * already be set up, and onboarding's first step was a second install from a
+ * second distribution channel — before the user had signed in or seen anything
+ * work.
+ *
+ * npm is the front door now. `npm i -g @skrr-ai/cli` gives you `skrr`, and
+ * `skrr daemon install` gets the daemon itself.
+ *
+ * ## Why it downloads a binary instead of shipping one
+ *
+ * The daemon is a compiled per-platform executable that is codesigned,
+ * notarized, and auto-updates itself in the field from a signed CloudFront feed
+ * with rollout cohorts. Vendoring five platform binaries into an npm tarball
+ * would bloat every install to serve one platform, and — worse — would freeze a
+ * copy that the daemon's own updater cannot replace, because that updater swaps
+ * a binary in its release slot, not a file inside a node_modules tree. Fetching
+ * from the same feed the updater uses keeps ONE distribution channel for the
+ * daemon and leaves its update story intact.
+ *
+ * ## Trust
+ *
+ * This is the CLI downloading an executable and putting it on disk, so every
+ * gate the daemon's own self-updater applies is applied here too, against the
+ * SAME pinned keys (`@skrr-ai/auth-core`, moved there for this reason — a
+ * mirrored trust root is a second array that can be emptied):
+ *
+ *   1. the manifest's ed25519 signature, fail-closed;
+ *   2. the artifact URL must share the feed's origin. The signature already
+ *      covers the URL, so this is not about forgery — it bounds where a
+ *      LEGITIMATELY signed manifest can send us, which is what protects against
+ *      operator error and against a signer coerced into signing a redirect;
+ *   3. sha256 of the received bytes;
+ *   4. the artifact's own ed25519 signature over (platform, version, sha256, url).
+ *
+ * TLS alone is explicitly not enough: the sha256 travels in the same document
+ * over the same channel, so it defends against corruption in transit, not
+ * against a spoofed feed. (3) without (4) would be the same mistake.
+ *
+ * The write is staged then renamed, so an interrupted download can never leave
+ * a half-written executable at the path the CLI will later exec.
+ */
+const node_crypto_1 = require("node:crypto");
+const node_fs_1 = require("node:fs");
+const node_os_1 = __importDefault(require("node:os"));
+const node_path_1 = __importDefault(require("node:path"));
+const auth_core_1 = require("@skrr-ai/auth-core");
+/** Public CloudFront feed. Mirrors the daemon's own `CLOUDFRONT_FEED_BASE`. */
+exports.DEFAULT_DAEMON_FEED_BASE = 'https://updates.oversky.ai/daemon';
+/** Same override the daemon honours, so one env var steers both. */
+exports.DAEMON_FEED_BASE_ENV = 'OVERSKY_DAEMON_UPDATE_FEED_BASE';
+/** Refuse a manifest larger than this. It is a small JSON document. */
+const MAX_MANIFEST_BYTES = 1_024 * 1_024;
+/** Refuse an artifact larger than this regardless of what the manifest claims. */
+const MAX_ARTIFACT_BYTES = 256 * 1_024 * 1_024;
+const MANIFEST_TIMEOUT_MS = 30_000;
+const ARTIFACT_TIMEOUT_MS = 10 * 60_000;
+function daemonFeedBase(env = process.env) {
+    return (env[exports.DAEMON_FEED_BASE_ENV]?.trim() || exports.DEFAULT_DAEMON_FEED_BASE).replace(/\/+$/, '');
+}
+/**
+ * Where the fetched binary lands. `exec-oversky.ts` already looks here, so a
+ * daemon installed by this path is found by every `skrr daemon *` command
+ * without the user touching PATH.
+ */
+function daemonBinaryPath(env = process.env) {
+    const home = env.HOME || env.USERPROFILE || node_os_1.default.homedir();
+    const exe = process.platform === 'win32' ? 'skrrd.exe' : 'skrrd';
+    return node_path_1.default.join(home, '.skrr', 'bin', exe);
+}
+/**
+ * `<platform>-<arch>`, the manifest's `platforms` key. Returns null for a
+ * combination the release does not build, which is a clearer refusal than a
+ * missing-key lookup one step later.
+ */
+function daemonPlatformKey(platform = process.platform, arch = process.arch) {
+    const supported = new Set([
+        'darwin-arm64',
+        'darwin-x64',
+        'linux-arm64',
+        'linux-x64',
+        'win32-x64',
+    ]);
+    const key = `${platform}-${arch}`;
+    return supported.has(key) ? key : null;
+}
+/**
+ * True when `candidate` may serve an artifact for a feed rooted at `feedBase`.
+ * Same rule as the daemon's `isTrustedArtifactOrigin`: a signed manifest still
+ * does not get to point the download at another origin.
+ */
+function isTrustedArtifactOrigin(candidate, feedBase) {
+    try {
+        return new URL(candidate).origin === new URL(feedBase).origin;
+    }
+    catch {
+        return false;
+    }
+}
+function fail(code, error) {
+    return { ok: false, code, error };
+}
+async function getWithTimeout(url, timeoutMs, fetchImpl) {
+    const controller = new AbortController();
+    const timer = setTimeout(() => controller.abort(), timeoutMs);
+    try {
+        return await fetchImpl(url, {
+            signal: controller.signal,
+            headers: { 'User-Agent': 'skrr-cli (daemon install)' },
+        });
+    }
+    finally {
+        clearTimeout(timer);
+    }
+}
+/** Fetch `<feedBase>/latest/daemon-version.json` and verify its signature. */
+async function fetchVerifiedDaemonManifest(opts = {}) {
+    const env = opts.env ?? process.env;
+    const feedBase = opts.feedBase ?? daemonFeedBase(env);
+    const fetchImpl = opts.fetchImpl ?? fetch;
+    const keys = opts.keys ?? auth_core_1.OVERSKY_RELEASE_PUBLIC_KEYS;
+    const url = `${feedBase}/latest/daemon-version.json`;
+    let res;
+    try {
+        res = await getWithTimeout(url, MANIFEST_TIMEOUT_MS, fetchImpl);
+    }
+    catch (err) {
+        return fail('manifest_unreachable', `${url}: ${err.message}`);
+    }
+    if (!res.ok) {
+        return fail('manifest_unreachable', `${url} returned HTTP ${res.status}`);
+    }
+    const text = await res.text();
+    if (text.length > MAX_MANIFEST_BYTES) {
+        return fail('manifest_malformed', 'release manifest is implausibly large');
+    }
+    let manifest;
+    try {
+        manifest = JSON.parse(text);
+    }
+    catch {
+        return fail('manifest_malformed', `${url} did not return JSON`);
+    }
+    if (!manifest || typeof manifest.version !== 'string' || !manifest.platforms) {
+        return fail('manifest_malformed', 'release manifest is missing version/platforms');
+    }
+    // Fail-closed by construction: the pinned key set is non-empty, so `disabled`
+    // cannot be reached here. Treating it as a refusal anyway means emptying that
+    // array turns installs OFF rather than turning verification off silently.
+    const verdict = (0, auth_core_1.verifyManifest)(manifest, keys);
+    if (!('ok' in verdict) || verdict.ok !== true) {
+        const reason = 'reason' in verdict ? verdict.reason : 'no release signing key is pinned';
+        return fail('manifest_unsigned', `release manifest failed verification: ${reason}`);
+    }
+    return { ok: true, manifest };
+}
+/**
+ * Download, verify and install the daemon binary. Returns a tagged result; it
+ * never throws, so the caller can render one refusal for every failure mode.
+ */
+async function installDaemon(opts = {}) {
+    const env = opts.env ?? process.env;
+    const feedBase = opts.feedBase ?? daemonFeedBase(env);
+    const fetchImpl = opts.fetchImpl ?? fetch;
+    const keys = opts.keys ?? auth_core_1.OVERSKY_RELEASE_PUBLIC_KEYS;
+    const platformKey = daemonPlatformKey();
+    if (!platformKey) {
+        return fail('unsupported_platform', `no daemon build for ${process.platform}-${process.arch}`);
+    }
+    const fetched = await fetchVerifiedDaemonManifest({ env, feedBase, fetchImpl, keys });
+    if (!('manifest' in fetched))
+        return fetched;
+    const { manifest } = fetched;
+    const artifact = manifest.platforms[platformKey];
+    if (!artifact?.url || !artifact.sha256) {
+        return fail('platform_missing', `release ${manifest.version} publishes no artifact for ${platformKey}`);
+    }
+    if (!isTrustedArtifactOrigin(artifact.url, feedBase)) {
+        return fail('untrusted_artifact_origin', `manifest points ${platformKey} at ${artifact.url}, which is not on the feed's origin`);
+    }
+    const artifactVerdict = (0, auth_core_1.verifyArtifact)(platformKey, manifest.version, artifact, keys);
+    if (!('ok' in artifactVerdict) || artifactVerdict.ok !== true) {
+        const reason = 'reason' in artifactVerdict ? artifactVerdict.reason : 'no key pinned';
+        return fail('artifact_unsigned', `${platformKey} artifact failed verification: ${reason}`);
+    }
+    if (typeof artifact.size === 'number' && artifact.size > MAX_ARTIFACT_BYTES) {
+        return fail('download_failed', `manifest declares an implausible size (${artifact.size} bytes)`);
+    }
+    let bytes;
+    try {
+        const res = await getWithTimeout(artifact.url, ARTIFACT_TIMEOUT_MS, fetchImpl);
+        if (!res.ok) {
+            return fail('download_failed', `${artifact.url} returned HTTP ${res.status}`);
+        }
+        const buf = Buffer.from(await res.arrayBuffer());
+        if (buf.byteLength > MAX_ARTIFACT_BYTES) {
+            return fail('download_failed', 'downloaded artifact exceeds the size ceiling');
+        }
+        bytes = buf;
+    }
+    catch (err) {
+        return fail('download_failed', `${artifact.url}: ${err.message}`);
+    }
+    const actual = (0, node_crypto_1.createHash)('sha256').update(bytes).digest('hex');
+    if (actual !== artifact.sha256.toLowerCase()) {
+        return fail('checksum_mismatch', `sha256 mismatch for ${platformKey}: expected ${artifact.sha256}, received ${actual}`);
+    }
+    // Staged then renamed. A rename within one directory is atomic, so the path
+    // the CLI later execs is either the previous binary or the fully-written new
+    // one — never a truncated download wearing the executable bit.
+    const binaryPath = daemonBinaryPath(env);
+    const stagingPath = `${binaryPath}.staging-${process.pid}`;
+    try {
+        (0, node_fs_1.mkdirSync)(node_path_1.default.dirname(binaryPath), { recursive: true });
+        (0, node_fs_1.writeFileSync)(stagingPath, bytes, { mode: 0o755 });
+        (0, node_fs_1.chmodSync)(stagingPath, 0o755);
+        (0, node_fs_1.renameSync)(stagingPath, binaryPath);
+    }
+    catch (err) {
+        try {
+            (0, node_fs_1.rmSync)(stagingPath, { force: true });
+        }
+        catch {
+            /* best-effort staging cleanup */
+        }
+        return fail('write_failed', `could not install to ${binaryPath}: ${err.message}`);
+    }
+    return { ok: true, version: manifest.version, platformKey, binaryPath };
+}

package/dist/lib/daemon-setup.d.ts

@@ -0,0 +1,49 @@
+/**
+ * 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.
+ */
+import { confirm } from './prompt';
+export interface DaemonSetupOutcome {
+    status: 'installed' | 'declined' | 'skipped' | 'failed';
+    detail: string;
+}
+export interface DaemonSetupOptions {
+    env?: NodeJS.ProcessEnv;
+    /** True when only the OS service is missing and the binary is already here. */
+    binaryPresent?: boolean;
+    /** Injected by tests. */
+    confirmImpl?: typeof confirm;
+    interactive?: boolean;
+    log?: (line: string) => void;
+}
+/**
+ * Ask, then install. Returns without touching anything when there is nobody to
+ * ask or the operator has opted out.
+ */
+export declare function offerDaemonSetup(opts?: DaemonSetupOptions): Promise<DaemonSetupOutcome>;

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/daemonHandoff.d.ts

@@ -32,6 +32,15 @@
 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;

package/dist/lib/daemonHandoff.js

@@ -173,7 +173,11 @@ async function handOffToLocalDaemon(env = process.env, opts = {}) {
     // 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', detail: 'skipped by OVERSKY_SKIP_DAEMON_HANDOFF' };
+        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.
@@ -186,12 +190,13 @@ async function handOffToLocalDaemon(env = process.env, opts = {}) {
     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', detail: 'no local daemon installed' };
+        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
@@ -201,6 +206,7 @@ async function handOffToLocalDaemon(env = process.env, opts = {}) {
     if (supported === false) {
         return {
             status: 'skipped',
+            reason: 'unsupported-daemon',
             detail: 'the installed daemon predates `accept-handoff`; run `skrr daemon login` once',
         };
     }
@@ -233,6 +239,7 @@ async function handOffToLocalDaemon(env = process.env, opts = {}) {
     if (idSource === 'cwd') {
         return {
             status: 'skipped',
+            reason: 'no-service',
             detail: 'no daemon service is installed on this machine',
         };
     }

package/dist/node_modules/@skrr-ai/auth-core/dist/cjs/index.d.ts

@@ -36,4 +36,6 @@ export { sanitizeSpawnEnv, SENSITIVE_ENV_VARS, SENSITIVE_ENV_PREFIXES, SENSITIVE
 export { CONFIG_DIR_NAME, LEGACY_CONFIG_DIR_NAMES, NATIVE_ID_PREFIX, LEGACY_NATIVE_ID_PREFIXES, DEFAULT_BINARY_NAME, } from './localIdentity.js';
 export { findLegacyLocalState, describeLegacyState, type LegacyStateFinding, type LegacyStateReport, } from './legacyStatePreflight.js';
 export { DEFAULT_SKY_CODE_CHANNEL, DEFAULT_SKY_CODE_FEED_BASE, SKY_CODE_CHANNELS, SKY_CODE_CHANNEL_ENV, SKY_CODE_MANIFEST_FILE, isSkyCodeChannel, resolveChannelManifestUrl, resolveSkyCodeChannel, skyCodeChannelPrefix, skyCodeFeedBase, SKY_CODE_FEED_BASE_ENV, type SkyCodeChannel, } from './skyCodeChannels.js';
+export { OVERSKY_RELEASE_PUBLIC_KEYS, type ReleaseKey } from './releaseKeys.js';
+export { MAX_SIGS, buildArtifactMessage, buildManifestMessage, getDeltaFor, verifyArtifact, verifyManifest, type DaemonVersionManifest, type DeltaDescriptor, type ManifestSignature, type PlatformArtifact, type VerifyResult, } from './releaseManifest.js';
 export { resolveConfigRoot, configRootPath, isConfigRootOverridden } from './configRoot.js';