@skrr-ai/cli 0.1.10 → 0.1.11

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}`,

package/dist/lib/format.d.ts

@@ -34,6 +34,13 @@ export declare function truncate(s: string, max: number): string;
  * reads as missing instead of as the string `undefined`.
  */
 export declare function formatCell(value: unknown, placeholder?: string): string;
+/**
+ * Collapse newlines/runs of whitespace so a value cannot break the table grid.
+ *
+ * Exported because `renderTable` applies it to EVERY cell, not just the ones
+ * that happened to come through `formatCell`.
+ */
+export declare function collapseWhitespace(value: string): string;
 /**
  * Render an array of row objects as a column-aligned table.
  *

package/dist/lib/format.js

@@ -4,6 +4,7 @@ exports.displayWidth = displayWidth;
 exports.pad = pad;
 exports.truncate = truncate;
 exports.formatCell = formatCell;
+exports.collapseWhitespace = collapseWhitespace;
 exports.renderTable = renderTable;
 exports.localStamp = localStamp;
 exports.localZone = localZone;
@@ -141,28 +142,49 @@ function stringifyCell(value, depth) {
         .filter(Boolean)
         .join(' ');
 }
-/** Collapse newlines/runs of whitespace so a value cannot break the table grid. */
+/**
+ * Collapse newlines/runs of whitespace so a value cannot break the table grid.
+ *
+ * Exported because `renderTable` applies it to EVERY cell, not just the ones
+ * that happened to come through `formatCell`.
+ */
 function collapseWhitespace(value) {
     return value.replace(/\s+/g, ' ').trim();
 }
 function renderTable(rows, columns, log) {
     if (rows.length === 0)
         return;
+    // Every cell is collapsed ONCE, here, before anything measures it. A
+    // fixed-width cell cannot legally contain a newline, and the table is the
+    // only place that knows that — a caller passing `String(item.preview)` has
+    // no idea whether the API's preview is one line or twelve.
+    //
+    // It has to happen before the width pass, not just at render: `displayWidth`
+    // counts a newline as one column, so an embedded one made the measurement
+    // wrong as well as the output. `tasks complete` writes a multi-line
+    // `---TASK_OUTPUT---` comment, so `tasks timeline` exploded one row across
+    // three physical lines and lost column alignment for everything after it —
+    // on every task that had been completed, which is all of them.
+    //
+    // `verbatim` is exempt from CLIPPING, not from this: an unclipped newline
+    // breaks the grid exactly as badly, and an id column never contains one.
+    const cells = rows.map((row) => Object.fromEntries(columns.map((col) => [String(col.key), collapseWhitespace(String(row[col.key] ?? ''))])));
     const widths = {};
     for (const col of columns) {
         const key = String(col.key);
         const headerWidth = displayWidth(col.header);
-        const dataWidth = Math.max(...rows.map((r) => displayWidth(String(r[col.key] ?? ''))));
+        const dataWidth = Math.max(0, ...cells.map((r) => displayWidth(r[key])));
         const natural = Math.max(headerWidth, dataWidth);
         widths[key] = col.maxWidth && !col.verbatim ? Math.min(natural, col.maxWidth) : natural;
     }
     const header = columns.map((col) => pad(col.header, widths[String(col.key)])).join('  ');
     log(header);
-    for (const row of rows) {
+    for (const row of cells) {
         const line = columns
             .map((col) => {
-            const raw = String(row[col.key] ?? '');
-            const width = widths[String(col.key)];
+            const key = String(col.key);
+            const raw = row[key];
+            const width = widths[key];
             return pad(col.verbatim ? raw : truncate(raw, width), width);
         })
             .join('  ');

package/dist/lib/login.js

@@ -52,6 +52,8 @@ async function cliLogin(opts = {}) {
     }
     const envForce = isTruthy(process.env.OVERSKY_FORCE_DEVICE_CODE);
     const ssh = (0, ssh_detect_1.detectSshSession)();
+    /** Set when the broker was refused for a reason that WAITING fixes. */
+    let brokerRateLimited = false;
     // --- Daemon-as-broker pre-flight ---------------------------------------
     // When the local `oversky` daemon is already authenticated for this user
     // on this machine, the cleanest UX is no second browser flow at all:
@@ -114,6 +116,20 @@ async function cliLogin(opts = {}) {
         // the PKCE flow opens a browser to a different URL than the
         // daemon. Continues to PKCE below — that's the right fallback for
         // "I'm logging into a different server than the daemon".
+        // Transient by construction — the ceiling is per 15-minute window — so the
+        // useful thing to say is "wait", not "here is a browser". An interactive
+        // user still gets the browser, because that genuinely works for them; the
+        // note exists so a surprise browser has a stated cause. Non-interactive
+        // callers get the real reason from the throw below instead of a sentence
+        // about terminals.
+        if (brokerResult.reason === 'rate_limited') {
+            brokerRateLimited = true;
+            if (!(0, ssh_detect_1.isNonInteractive)()) {
+                console.log('');
+                console.log('  The local skrr runtime has brokered several logins recently and the server is ' +
+                    'rate-limiting them. Falling back to the browser flow.');
+            }
+        }
         if (brokerResult.reason === 'base_url_mismatch' && brokerResult.daemonServerUrl) {
             console.log('');
             console.log(`  The local skrr runtime is logged in to ${brokerResult.daemonServerUrl}, but skrr is configured for ${serverUrl}.`);
@@ -121,8 +137,12 @@ async function cliLogin(opts = {}) {
         }
     }
     if ((0, ssh_detect_1.isNonInteractive)()) {
-        throw new Error('skrr login requires an interactive terminal or an SSH session. ' +
-            'For CI, use `skrr create-token` and set OVERSKY_TOKEN=osk_ci_...');
+        throw new Error(brokerRateLimited
+            ? 'The local skrr runtime is being rate-limited while brokering logins, and this ' +
+                'shell cannot run the browser flow instead. The limit is per 15-minute window — ' +
+                'retry shortly. For CI, use `skrr create-token` and set OVERSKY_TOKEN=osk_ci_...'
+            : 'skrr login requires an interactive terminal or an SSH session. ' +
+                'For CI, use `skrr create-token` and set OVERSKY_TOKEN=osk_ci_...');
     }
     // --- Decision tree (first match wins) ---
     if (opts.forceDeviceCode) {

package/dist/lib/sky-code.js

@@ -91,7 +91,7 @@ function managedEnginePath(exeName, env = process.env) {
  * hard-coded home would defeat the pinning {@link engineHome} relies on.
  */
 function legacyManagedEnginePath(exeName, env = process.env) {
-    if (env.OVERSKY_CONFIG_DIR?.trim())
+    if ((0, auth_core_1.isConfigRootOverridden)(env))
         return null;
     return node_path_1.default.join((0, node_os_1.homedir)(), '.oversky', 'sky-code', 'bin', exeName);
 }

package/dist/lib/task-transcript.d.ts

@@ -23,6 +23,15 @@ export type TaskOutputComment = {
     parsed: ParsedTaskOutput;
     /** Block lines the field parser could not attribute — see `unattributedBlockLines`. */
     unattributed: string[];
+    /**
+     * How many OLDER TASK_OUTPUT blocks this one supersedes.
+     *
+     * `tasks complete` can run twice on an already-done task, and each run posts
+     * its own block. Callers render the newest, so without this count a screen
+     * built from several completions is indistinguishable from one built from a
+     * single completion.
+     */
+    supersededCount: number;
 };
 /**
  * Mirror of `api/server/services/taskCompletionFormatting.js:parseTaskOutputBlock`.

package/dist/lib/task-transcript.js

@@ -130,21 +130,32 @@ async function fetchLatestTaskOutputComment(taskId, limit = 50) {
     const comments = response?.data ?? [];
     // listTaskComments returns newest-first; take the first parseable block so a
     // later "action items tracked" follow-up comment doesn't mask the real output.
+    // Keep walking after finding it, though — the REST are earlier completions,
+    // and their number is the only signal a caller has that the newest block is
+    // not the whole story.
+    let newest = null;
+    let blocks = 0;
     for (const comment of comments) {
         const body = String(comment.body ?? comment.content ?? '');
         const parsed = parseTaskOutputBlock(body);
         if (!parsed)
             continue;
-        return {
+        blocks += 1;
+        if (newest)
+            continue;
+        newest = {
             commentId: String(comment.id ?? comment._id ?? '-'),
             createdAt: comment.createdAt ? String(comment.createdAt) : null,
             author: String(comment.authorAgentId ?? comment.authorUserId ?? comment.author ?? '-'),
             body,
             parsed,
             unattributed: unattributedBlockLines(body),
+            supersededCount: 0,
         };
     }
-    return null;
+    if (newest)
+        newest.supersededCount = blocks - 1;
+    return newest;
 }
 /** Last message the agent (not the user) produced in the execution conversation. */
 function lastAssistantMessage(messages) {

package/dist/lib/tasks.d.ts

@@ -194,3 +194,37 @@ export declare function normalizeBulkUpdateInput(input: unknown): Array<{
     id: string;
     patch: TaskRecord;
 }>;
+/**
+ * Verdict strings the server recognises on a task completion.
+ *
+ * `--verdict` is free text: `skrr tasks complete <id> --verdict banana`
+ * succeeds and the value is permanently recorded, while `--status` beside it
+ * is enumerated and rejects a typo. So `--verdict aproved` closes a task with
+ * a verdict nothing matches, quietly.
+ *
+ * It cannot simply be enumerated, and that is the point worth recording:
+ *
+ *  - A REVIEWER task legitimately passes a JSON object
+ *    (`{"posture":"request_changes","confidence":0.82,"criteria":[…]}`) —
+ *    documented in the task-execution prompt and consumed by
+ *    `normalizeReviewPosture`. `options:` on the flag would refuse it.
+ *  - That normaliser accepts synonyms, and when it recognises NOTHING it does
+ *    not fail — it derives the posture from the criteria instead. So a typo
+ *    silently becomes whatever the criteria imply.
+ *
+ * Hence a warning, not a refusal, over the set the server actually matches.
+ * Mirrored from `normalizeReviewPosture` in
+ * `api/server/services/TasksMCP/taskExecutionHelpers.js` and pinned against it
+ * by `task-verdict-parity.spec.ts`, the same way TASK_WORK_EVENT_KINDS is.
+ */
+export declare const RECOGNIZED_TASK_VERDICTS: readonly ["request_changes", "changes_requested", "needs_changes", "needs_revision", "approved", "approve", "pass", "passed", "blocked"];
+/** The server's own normalisation, so the same spellings match here. */
+export declare function normalizeVerdict(value: string): string;
+/**
+ * Does this verdict mean anything to the server?
+ *
+ * `UNVERIFIED` is platform-stamped rather than user-supplied, and a JSON
+ * verdict is the reviewer shape — both are legitimate and neither is in the
+ * synonym list.
+ */
+export declare function verdictIsRecognized(value: string | undefined): boolean;

package/dist/lib/tasks.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.TASK_WORK_EVENT_KINDS = exports.TASK_PRIORITIES = void 0;
+exports.RECOGNIZED_TASK_VERDICTS = exports.TASK_WORK_EVENT_KINDS = exports.TASK_PRIORITIES = void 0;
 exports.releasePinRepairGuard = releasePinRepairGuard;
 exports.taskUpdateMutationGuard = taskUpdateMutationGuard;
 exports.executionIsolationFromWorktreeFlag = executionIsolationFromWorktreeFlag;
@@ -27,6 +27,8 @@ exports.formatTaskLabel = formatTaskLabel;
 exports.hasTaskAssignee = hasTaskAssignee;
 exports.normalizeTaskUpdateEntry = normalizeTaskUpdateEntry;
 exports.normalizeBulkUpdateInput = normalizeBulkUpdateInput;
+exports.normalizeVerdict = normalizeVerdict;
+exports.verdictIsRecognized = verdictIsRecognized;
 const data_provider_1 = require("@skrr-ai/data-provider");
 const prompt_1 = require("./prompt");
 const projects_1 = require("./projects");
@@ -715,3 +717,70 @@ function formatApiError(err) {
         return err.message;
     return String(err);
 }
+/**
+ * Verdict strings the server recognises on a task completion.
+ *
+ * `--verdict` is free text: `skrr tasks complete <id> --verdict banana`
+ * succeeds and the value is permanently recorded, while `--status` beside it
+ * is enumerated and rejects a typo. So `--verdict aproved` closes a task with
+ * a verdict nothing matches, quietly.
+ *
+ * It cannot simply be enumerated, and that is the point worth recording:
+ *
+ *  - A REVIEWER task legitimately passes a JSON object
+ *    (`{"posture":"request_changes","confidence":0.82,"criteria":[…]}`) —
+ *    documented in the task-execution prompt and consumed by
+ *    `normalizeReviewPosture`. `options:` on the flag would refuse it.
+ *  - That normaliser accepts synonyms, and when it recognises NOTHING it does
+ *    not fail — it derives the posture from the criteria instead. So a typo
+ *    silently becomes whatever the criteria imply.
+ *
+ * Hence a warning, not a refusal, over the set the server actually matches.
+ * Mirrored from `normalizeReviewPosture` in
+ * `api/server/services/TasksMCP/taskExecutionHelpers.js` and pinned against it
+ * by `task-verdict-parity.spec.ts`, the same way TASK_WORK_EVENT_KINDS is.
+ */
+exports.RECOGNIZED_TASK_VERDICTS = [
+    'request_changes',
+    'changes_requested',
+    'needs_changes',
+    'needs_revision',
+    'approved',
+    'approve',
+    'pass',
+    'passed',
+    'blocked',
+];
+/** The server's own normalisation, so the same spellings match here. */
+function normalizeVerdict(value) {
+    return String(value ?? '')
+        .trim()
+        .toLowerCase()
+        .replace(/[\s-]+/g, '_');
+}
+/**
+ * Does this verdict mean anything to the server?
+ *
+ * `UNVERIFIED` is platform-stamped rather than user-supplied, and a JSON
+ * verdict is the reviewer shape — both are legitimate and neither is in the
+ * synonym list.
+ */
+function verdictIsRecognized(value) {
+    if (!value)
+        return true;
+    const raw = value.trim();
+    if (!raw)
+        return true;
+    if (raw.toUpperCase() === 'UNVERIFIED')
+        return true;
+    if (raw.startsWith('{') || raw.startsWith('[')) {
+        try {
+            JSON.parse(raw);
+            return true;
+        }
+        catch {
+            return false;
+        }
+    }
+    return exports.RECOGNIZED_TASK_VERDICTS.includes(normalizeVerdict(raw));
+}

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

@@ -0,0 +1,50 @@
+/**
+ * The skrr root — the single definition of where this machine keeps its skrr
+ * state.
+ *
+ * It lives here because BOTH binaries need the same answer and neither owns it.
+ * `skrr` and `skrrd` keep separate credentials on purpose, but they share one
+ * root, and every place that re-derived it became a place they could disagree.
+ * They did, twice in one day:
+ *
+ *   - The CLI's engine path honoured `OVERSKY_CONFIG_DIR` while its config did
+ *     not, so a relocated root moved the engine and left the credentials in
+ *     `$HOME`. Fixed by teaching `config.ts` the variable — which promptly
+ *     re-created the split in the mirror image, because `sky-code.ts` still read
+ *     only the old name.
+ *   - The daemon then had the same shape, and fixing the CLI's half turned it
+ *     into a CLI/daemon divergence: with the variable set, the two halves of one
+ *     product disagreed about where the credentials live.
+ *
+ * Each of those was a correct local fix that created the next defect, because
+ * the root was being DERIVED rather than READ. Teaching every site the same list
+ * of variable names only defers the problem to whenever the list changes again —
+ * which is exactly what `SKRR_CONFIG_DIR` did.
+ *
+ * So: one function, and a boundary test that fails if anything re-derives it.
+ *
+ * `SKRR_CONFIG_DIR` is the spelling for anything new (root `CLAUDE.md`) and wins
+ * when both are set. `OVERSKY_CONFIG_DIR` keeps working because existing installs,
+ * the engine resolver and the daemon all read it, and breaking a documented
+ * override to tidy a name would be a worse trade than carrying two.
+ *
+ * Takes `env` rather than reading the global so a caller can resolve a root for a
+ * child process it is about to spawn, and so tests need no process-wide mutation.
+ */
+export declare function resolveConfigRoot(env?: NodeJS.ProcessEnv): string;
+/** A path under the skrr root, e.g. `configRootPath(env, 'sky-code', 'bin')`. */
+export declare function configRootPath(env: NodeJS.ProcessEnv, ...segments: string[]): string;
+/**
+ * Has the operator explicitly relocated the root?
+ *
+ * A distinct question from "what is the root", and it has a real caller: the
+ * legacy-location fallbacks exist to find state left by an older layout under
+ * `$HOME`, and once someone has POINTED the root somewhere, guessing at
+ * `$HOME` is no longer a helpful fallback — it is a different machine's data.
+ *
+ * Shared for the same reason as `resolveConfigRoot`: this check was copied to
+ * three call sites, each spelling the variable list itself, so adding
+ * `SKRR_CONFIG_DIR` to the resolver silently left the copies answering the old
+ * question.
+ */
+export declare function isConfigRootOverridden(env?: NodeJS.ProcessEnv): boolean;

package/dist/node_modules/@skrr-ai/auth-core/dist/cjs/configRoot.js

@@ -0,0 +1,67 @@
+"use strict";
+var __importDefault = (this && this.__importDefault) || function (mod) {
+    return (mod && mod.__esModule) ? mod : { "default": mod };
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.resolveConfigRoot = resolveConfigRoot;
+exports.configRootPath = configRootPath;
+exports.isConfigRootOverridden = isConfigRootOverridden;
+const node_os_1 = require("node:os");
+const node_path_1 = __importDefault(require("node:path"));
+/**
+ * The skrr root — the single definition of where this machine keeps its skrr
+ * state.
+ *
+ * It lives here because BOTH binaries need the same answer and neither owns it.
+ * `skrr` and `skrrd` keep separate credentials on purpose, but they share one
+ * root, and every place that re-derived it became a place they could disagree.
+ * They did, twice in one day:
+ *
+ *   - The CLI's engine path honoured `OVERSKY_CONFIG_DIR` while its config did
+ *     not, so a relocated root moved the engine and left the credentials in
+ *     `$HOME`. Fixed by teaching `config.ts` the variable — which promptly
+ *     re-created the split in the mirror image, because `sky-code.ts` still read
+ *     only the old name.
+ *   - The daemon then had the same shape, and fixing the CLI's half turned it
+ *     into a CLI/daemon divergence: with the variable set, the two halves of one
+ *     product disagreed about where the credentials live.
+ *
+ * Each of those was a correct local fix that created the next defect, because
+ * the root was being DERIVED rather than READ. Teaching every site the same list
+ * of variable names only defers the problem to whenever the list changes again —
+ * which is exactly what `SKRR_CONFIG_DIR` did.
+ *
+ * So: one function, and a boundary test that fails if anything re-derives it.
+ *
+ * `SKRR_CONFIG_DIR` is the spelling for anything new (root `CLAUDE.md`) and wins
+ * when both are set. `OVERSKY_CONFIG_DIR` keeps working because existing installs,
+ * the engine resolver and the daemon all read it, and breaking a documented
+ * override to tidy a name would be a worse trade than carrying two.
+ *
+ * Takes `env` rather than reading the global so a caller can resolve a root for a
+ * child process it is about to spawn, and so tests need no process-wide mutation.
+ */
+function resolveConfigRoot(env = process.env) {
+    const override = (env.SKRR_CONFIG_DIR || env.OVERSKY_CONFIG_DIR)?.trim();
+    return override || node_path_1.default.join((0, node_os_1.homedir)(), '.skrr');
+}
+/** A path under the skrr root, e.g. `configRootPath(env, 'sky-code', 'bin')`. */
+function configRootPath(env, ...segments) {
+    return node_path_1.default.join(resolveConfigRoot(env), ...segments);
+}
+/**
+ * Has the operator explicitly relocated the root?
+ *
+ * A distinct question from "what is the root", and it has a real caller: the
+ * legacy-location fallbacks exist to find state left by an older layout under
+ * `$HOME`, and once someone has POINTED the root somewhere, guessing at
+ * `$HOME` is no longer a helpful fallback — it is a different machine's data.
+ *
+ * Shared for the same reason as `resolveConfigRoot`: this check was copied to
+ * three call sites, each spelling the variable list itself, so adding
+ * `SKRR_CONFIG_DIR` to the resolver silently left the copies answering the old
+ * question.
+ */
+function isConfigRootOverridden(env = process.env) {
+    return Boolean((env.SKRR_CONFIG_DIR || env.OVERSKY_CONFIG_DIR)?.trim());
+}

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

@@ -36,3 +36,4 @@ 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 { resolveConfigRoot, configRootPath, isConfigRootOverridden } from './configRoot.js';

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

@@ -11,7 +11,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.challenge = exports.generateVerifier = exports.invalidateHeadersHelperCache = exports.runHeadersHelper = exports.SENTINEL_TRIGGERING_FAILURES = exports.__resetAuthHelperFailureReasonForTest = exports.getLastAuthHelperFailureReason = exports.getDefaultHelperTtlMs = exports.invokeAuthHelper = exports.AuthHelperUnavailableError = exports.AuthHelperUntrustedError = exports.CI_TOKEN_PREFIX = exports.classifyTokenKind = exports.invalidateAuthHelperCache = exports.__resetCredentialResolverForTest = exports.CREDENTIAL_PRECEDENCE = exports.CredentialResolver = exports.__setFdReaderForTest = exports.readAuthFromFd = exports.createRefreshScheduler = exports.UNKNOWN_401_BUDGET = exports.__resetUnknown401StreaksForTest = exports.__refreshDiagnostics = exports.installLockExitHandlers = exports.clearReauthState = exports.needsReauthState = exports.persistReauthState = exports.withAuthLock = exports.revokeDaemonRefreshSession = exports.refreshDaemonToken = exports.classifyRefreshResponse = exports.EXIT_NEEDS_REAUTH = exports.formatReauthMessage = exports.handleMidStreamAuthExpiry = exports.isAuthExpiredSseEvent = exports.decodeJwtPayload = exports.decodeJwtExpiry = exports.TransientAuthFailure = exports.PermanentAuthFailure = exports.emitAuthTelemetry = exports.getAuthBinaryName = exports.getAuthKillSwitches = exports.getAuthConfigDir = exports.getAuthLogger = exports.configureAuthCore = exports.OAUTH_CLI_SCOPE = exports.isDaemonScope = exports.VALID_DAEMON_SCOPE_SET = exports.ALL_DAEMON_SCOPES = exports.SCOPES = void 0;
 exports.tokenHash = exports.publicJwkFromX = exports.normalizeHtu = exports.jwkThumbprint = exports.generateDeviceKeyPair = exports.buildDeviceProof = exports.zeroizeKekCaches = exports.WindowsKek = exports.registerZeroizeHook = exports.MacosKek = exports.LinuxKek = exports.KekUnavailableError = exports.UnavailableKek = exports.InMemoryKek = exports.getKekStrategy = exports.__setKekStrategyForTest = exports.credEnvelopeWrap = exports.credEnvelopeUnwrap = exports.credEnvelopeSerialize = exports.credSealBuffer = exports.credOpenBuffer = exports.CRED_KEY_LEN = exports.isCredEnvelopeString = exports.generateDek = exports.CRED_ENVELOPE_MAGIC = exports.credEnvelopeEncrypt = exports.credEnvelopeDeserialize = exports.credEnvelopeDecrypt = exports.buildCredentialAad = exports.isValidRecoveryCode = exports.normalizeRecoveryCode = exports.parseRecoveryCode = exports.formatRecoveryCode = exports.MAX_TTL_DAYS = exports.MIN_TTL_DAYS = exports.parseTtlDays = exports.LoginExchangeError = exports.LoginInitError = exports.loginWithLocalhost = exports.LocalCallbackMalformedError = exports.LocalCallbackDeniedError = exports.LocalCallbackStateMismatchError = exports.LocalCallbackTimeoutError = exports.LocalCallbackBindError = exports.LocalCallbackError = exports.DEFAULT_LOGIN_TIMEOUT_MS = exports.startLocalCallback = exports.verifyChallenge = exports.safeEqual = exports.generateState = void 0;
 exports.getHarnessTier = exports.HARNESS_TIERS = exports.pairUint8ArrayToBase64Url = exports.pairUint8ArrayToBase64 = exports.parsePairUrl = exports.parsePairPlaintext = exports.parsePairBundle = exports.openPairBundleBase64 = exports.generatePairKeyPair = exports.buildPairUrl = exports.buildPairAad = exports.pairBase64UrlToUint8Array = exports.pairBase64ToUint8Array = exports.assemblePairBundleBase64 = exports.PairBundleError = exports.PAIR_SECRET_LEN = exports.PAIR_PUBKEY_LEN = exports.PAIR_NONCE_LEN = exports.PAIR_BUNDLE_MAX_BASE64_LEN = exports.PAIR_AAD_MAX_LEN = exports.PAIR_AAD_PREFIX = exports.__resetCachedDaemonIdForTest = exports.legacyDaemonUuids = exports.ensureMachineDaemonId = exports.__getDeviceIdentityStateForTest = exports.__setDeviceIdentityStateForTest = exports.__enrollmentBackoffPathForTest = exports.__enrollmentMarkerPathForTest = exports.__privateKeyPathForTest = exports.__publicKeyPathForTest = exports.describeDeviceIdentityState = exports.getDevicePublicKey = exports.isDeviceIdentityActive = exports.clearEnrollmentMarker = exports.enrollWithServer = exports.signServerRequest = exports.resetDeviceIdentity = exports.initDeviceIdentity = exports.__resetShutdownGuardForTest = exports.__getCredEnvelopeStateForTest = exports.__setCredEnvelopeStateForTest = exports.__wrappedDekFilePathForTest = exports.maybeDecryptOnRead = exports.maybeEncryptForWrite = exports.describeCredEnvelopeState = exports.isCredEnvelopeActive = exports.shutdownCredEnvelope = exports.resetCredEnvelope = exports.initCredEnvelope = exports.verifyDeviceProof = void 0;
-exports.SKY_CODE_FEED_BASE_ENV = exports.skyCodeFeedBase = exports.skyCodeChannelPrefix = exports.resolveSkyCodeChannel = exports.resolveChannelManifestUrl = exports.isSkyCodeChannel = exports.SKY_CODE_MANIFEST_FILE = exports.SKY_CODE_CHANNEL_ENV = exports.SKY_CODE_CHANNELS = exports.DEFAULT_SKY_CODE_FEED_BASE = exports.DEFAULT_SKY_CODE_CHANNEL = exports.describeLegacyState = exports.findLegacyLocalState = exports.DEFAULT_BINARY_NAME = exports.LEGACY_NATIVE_ID_PREFIXES = exports.NATIVE_ID_PREFIX = exports.LEGACY_CONFIG_DIR_NAMES = exports.CONFIG_DIR_NAME = exports.SENSITIVE_ENV_PREFIX_EXCEPTIONS = exports.SENSITIVE_ENV_SUFFIXES = exports.SENSITIVE_ENV_PREFIXES = exports.SENSITIVE_ENV_VARS = exports.sanitizeSpawnEnv = exports.tierPermitsConfiguredAutoMode = exports.credentialPolicyForTier = void 0;
+exports.isConfigRootOverridden = exports.configRootPath = exports.resolveConfigRoot = exports.SKY_CODE_FEED_BASE_ENV = exports.skyCodeFeedBase = exports.skyCodeChannelPrefix = exports.resolveSkyCodeChannel = exports.resolveChannelManifestUrl = exports.isSkyCodeChannel = exports.SKY_CODE_MANIFEST_FILE = exports.SKY_CODE_CHANNEL_ENV = exports.SKY_CODE_CHANNELS = exports.DEFAULT_SKY_CODE_FEED_BASE = exports.DEFAULT_SKY_CODE_CHANNEL = exports.describeLegacyState = exports.findLegacyLocalState = exports.DEFAULT_BINARY_NAME = exports.LEGACY_NATIVE_ID_PREFIXES = exports.NATIVE_ID_PREFIX = exports.LEGACY_CONFIG_DIR_NAMES = exports.CONFIG_DIR_NAME = exports.SENSITIVE_ENV_PREFIX_EXCEPTIONS = exports.SENSITIVE_ENV_SUFFIXES = exports.SENSITIVE_ENV_PREFIXES = exports.SENSITIVE_ENV_VARS = exports.sanitizeSpawnEnv = exports.tierPermitsConfiguredAutoMode = exports.credentialPolicyForTier = void 0;
 // Daemon scope vocabulary — single source of truth for non-Mongoose tiers
 // (daemon, desktop, cli). Schema-bound canonical lives in
 // `@skrr-ai/data-schemas/common/daemonScopes`; the two are kept byte-equal
@@ -315,3 +315,9 @@ Object.defineProperty(exports, "resolveSkyCodeChannel", { enumerable: true, get:
 Object.defineProperty(exports, "skyCodeChannelPrefix", { enumerable: true, get: function () { return skyCodeChannels_js_1.skyCodeChannelPrefix; } });
 Object.defineProperty(exports, "skyCodeFeedBase", { enumerable: true, get: function () { return skyCodeChannels_js_1.skyCodeFeedBase; } });
 Object.defineProperty(exports, "SKY_CODE_FEED_BASE_ENV", { enumerable: true, get: function () { return skyCodeChannels_js_1.SKY_CODE_FEED_BASE_ENV; } });
+// The one definition of the skrr root, shared by `skrr` and `skrrd`. See the
+// module for why re-deriving it kept producing divergences.
+var configRoot_js_1 = require("./configRoot.js");
+Object.defineProperty(exports, "resolveConfigRoot", { enumerable: true, get: function () { return configRoot_js_1.resolveConfigRoot; } });
+Object.defineProperty(exports, "configRootPath", { enumerable: true, get: function () { return configRoot_js_1.configRootPath; } });
+Object.defineProperty(exports, "isConfigRootOverridden", { enumerable: true, get: function () { return configRoot_js_1.isConfigRootOverridden; } });

package/dist/node_modules/@skrr-ai/auth-core/dist/esm/configRoot.d.ts

@@ -0,0 +1,50 @@
+/**
+ * The skrr root — the single definition of where this machine keeps its skrr
+ * state.
+ *
+ * It lives here because BOTH binaries need the same answer and neither owns it.
+ * `skrr` and `skrrd` keep separate credentials on purpose, but they share one
+ * root, and every place that re-derived it became a place they could disagree.
+ * They did, twice in one day:
+ *
+ *   - The CLI's engine path honoured `OVERSKY_CONFIG_DIR` while its config did
+ *     not, so a relocated root moved the engine and left the credentials in
+ *     `$HOME`. Fixed by teaching `config.ts` the variable — which promptly
+ *     re-created the split in the mirror image, because `sky-code.ts` still read
+ *     only the old name.
+ *   - The daemon then had the same shape, and fixing the CLI's half turned it
+ *     into a CLI/daemon divergence: with the variable set, the two halves of one
+ *     product disagreed about where the credentials live.
+ *
+ * Each of those was a correct local fix that created the next defect, because
+ * the root was being DERIVED rather than READ. Teaching every site the same list
+ * of variable names only defers the problem to whenever the list changes again —
+ * which is exactly what `SKRR_CONFIG_DIR` did.
+ *
+ * So: one function, and a boundary test that fails if anything re-derives it.
+ *
+ * `SKRR_CONFIG_DIR` is the spelling for anything new (root `CLAUDE.md`) and wins
+ * when both are set. `OVERSKY_CONFIG_DIR` keeps working because existing installs,
+ * the engine resolver and the daemon all read it, and breaking a documented
+ * override to tidy a name would be a worse trade than carrying two.
+ *
+ * Takes `env` rather than reading the global so a caller can resolve a root for a
+ * child process it is about to spawn, and so tests need no process-wide mutation.
+ */
+export declare function resolveConfigRoot(env?: NodeJS.ProcessEnv): string;
+/** A path under the skrr root, e.g. `configRootPath(env, 'sky-code', 'bin')`. */
+export declare function configRootPath(env: NodeJS.ProcessEnv, ...segments: string[]): string;
+/**
+ * Has the operator explicitly relocated the root?
+ *
+ * A distinct question from "what is the root", and it has a real caller: the
+ * legacy-location fallbacks exist to find state left by an older layout under
+ * `$HOME`, and once someone has POINTED the root somewhere, guessing at
+ * `$HOME` is no longer a helpful fallback — it is a different machine's data.
+ *
+ * Shared for the same reason as `resolveConfigRoot`: this check was copied to
+ * three call sites, each spelling the variable list itself, so adding
+ * `SKRR_CONFIG_DIR` to the resolver silently left the copies answering the old
+ * question.
+ */
+export declare function isConfigRootOverridden(env?: NodeJS.ProcessEnv): boolean;