@skrr-ai/cli 0.1.42 → 0.1.44

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

@@ -20,9 +20,15 @@
  *      leave the legacy name as a relative symlink. (No legacy app name exists
  *      yet; this step is what an engine-namespace rename will use.)
  *   2. The BINARY follows the provider. Inside `<home>/bin`, if the canonical
- *      binary does not exist and an alias binary is a real file, rename it and
- *      each companion (rollback copy, provenance sidecar), leaving a relative
- *      symlink at every old name.
+ *      binary does not exist and a binary under an older spelling is a real
+ *      file, rename it and each companion (rollback copy, provenance sidecar),
+ *      leaving a relative symlink at every old name.
+ *
+ * "Older spelling" means every ARTIFACT spelling that is not canonical — the
+ * aliases AND the former spellings (`firstPartyHarnessArtifactSpellings`). An
+ * installed binary is an artifact: a machine that never ran a post-rename client
+ * still has its engine under the old name after that name stops being accepted
+ * anywhere, and it must still be moved rather than reinstalled beside.
  *
  * The two follow different names on purpose: the home is shared with the
  * engine, which reads its config and managed `AGENTS.md` from it, so it can only
@@ -73,7 +79,9 @@ export interface FirstPartyHarnessHomeFs {
  * Move a legacy engine home and binary onto the canonical names. See the file
  * header for the exact contract. Returns what it did; never throws.
  *
- * Inside `<home>/bin` it resolves the three layouts a rename can leave:
+ * Inside `<home>/bin` it resolves the three layouts a rename can leave. An
+ * "alias" below is any non-canonical artifact spelling — an accepted alias or a
+ * former spelling alike, since the file on disk does not know which it is now:
  *
  *   - canonical ABSENT, an alias is a real file — the ordinary legacy install.
  *     The alias moves to canonical and a link is left at its name.
@@ -96,13 +104,17 @@ export declare function migrateFirstPartyHarnessHome(options?: {
     fs?: FirstPartyHarnessHomeFs;
 }): FirstPartyHarnessHomeMigration;
 /**
- * Leave a relative symlink at every alias name — binary and provenance sidecar —
+ * Leave a relative symlink at every older name — binary and provenance sidecar —
  * that does not exist yet, pointing at the canonical file.
  *
  * Call after installing the canonical binary. A platform CLI or daemon installed
  * before a rename resolves the legacy name; the link keeps it on the current
- * engine. It never replaces anything that exists, whether a real file (an older
- * engine someone may still run) or a link someone else placed. Never throws.
+ * engine. "Older" includes FORMER spellings, not only aliases: an installed CLI
+ * cannot be telemetry-gated the way a connected daemon can, and it does not stop
+ * existing when its spelling stops being accepted, so the link outlives the
+ * alias window (`firstPartyHarnessBinaryNames`). It never replaces anything that
+ * exists, whether a real file (an older engine someone may still run) or a link
+ * someone else placed. Never throws.
  */
 export declare function linkFirstPartyHarnessAliases(options?: {
     env?: NodeJS.ProcessEnv;

package/dist/node_modules/@skrr-ai/auth-core/dist/esm/firstPartyHarnessHome.js

@@ -20,9 +20,15 @@
  *      leave the legacy name as a relative symlink. (No legacy app name exists
  *      yet; this step is what an engine-namespace rename will use.)
  *   2. The BINARY follows the provider. Inside `<home>/bin`, if the canonical
- *      binary does not exist and an alias binary is a real file, rename it and
- *      each companion (rollback copy, provenance sidecar), leaving a relative
- *      symlink at every old name.
+ *      binary does not exist and a binary under an older spelling is a real
+ *      file, rename it and each companion (rollback copy, provenance sidecar),
+ *      leaving a relative symlink at every old name.
+ *
+ * "Older spelling" means every ARTIFACT spelling that is not canonical — the
+ * aliases AND the former spellings (`firstPartyHarnessArtifactSpellings`). An
+ * installed binary is an artifact: a machine that never ran a post-rename client
+ * still has its engine under the old name after that name stops being accepted
+ * anywhere, and it must still be moved rather than reinstalled beside.
  *
  * The two follow different names on purpose: the home is shared with the
  * engine, which reads its config and managed `AGENTS.md` from it, so it can only
@@ -42,7 +48,11 @@
 import { lstatSync, readlinkSync, renameSync, symlinkSync } from 'node:fs';
 import path from 'node:path';
 import { resolveConfigRoot } from './configRoot.js';
-import { FIRST_PARTY_HARNESS, FIRST_PARTY_HARNESS_ENGINE, firstPartyHarnessBinaryName, firstPartyHarnessHomeDirname, } from './firstPartyHarness.js';
+import { FIRST_PARTY_HARNESS, FIRST_PARTY_HARNESS_ENGINE, firstPartyHarnessArtifactSpellings, firstPartyHarnessBinaryName, firstPartyHarnessHomeDirname, } from './firstPartyHarness.js';
+/** Every artifact spelling except the canonical one, newest first. */
+function olderSpellings() {
+    return firstPartyHarnessArtifactSpellings().filter((spelling) => spelling !== FIRST_PARTY_HARNESS.provider);
+}
 /** Suffix of the rollback copy the installer keeps beside the binary. */
 export const FIRST_PARTY_HARNESS_PREVIOUS_SUFFIX = '.previous';
 /**
@@ -108,7 +118,9 @@ const NEWER_THRESHOLD_MS = 1000;
  * Move a legacy engine home and binary onto the canonical names. See the file
  * header for the exact contract. Returns what it did; never throws.
  *
- * Inside `<home>/bin` it resolves the three layouts a rename can leave:
+ * Inside `<home>/bin` it resolves the three layouts a rename can leave. An
+ * "alias" below is any non-canonical artifact spelling — an accepted alias or a
+ * former spelling alike, since the file on disk does not know which it is now:
  *
  *   - canonical ABSENT, an alias is a real file — the ordinary legacy install.
  *     The alias moves to canonical and a link is left at its name.
@@ -171,7 +183,7 @@ export function migrateFirstPartyHarnessHome(options = {}) {
     const canonicalName = firstPartyHarnessBinaryName(canonical, platform);
     const canonicalBinary = path.join(binDir, canonicalName);
     const canonicalStat = fs.lstat(canonicalBinary);
-    const aliasNames = FIRST_PARTY_HARNESS.aliases.map((alias) => firstPartyHarnessBinaryName(alias, platform));
+    const aliasNames = olderSpellings().map((spelling) => firstPartyHarnessBinaryName(spelling, platform));
     /** Move `<from><suffix>` onto `<to><suffix>` and leave a link; `replaceable` says what may sit at the target. */
     const relocate = (fromName, suffix, replaceable) => {
         const from = path.join(binDir, `${fromName}${suffix}`);
@@ -260,13 +272,17 @@ export function migrateFirstPartyHarnessHome(options = {}) {
     return { moved, errors };
 }
 /**
- * Leave a relative symlink at every alias name — binary and provenance sidecar —
+ * Leave a relative symlink at every older name — binary and provenance sidecar —
  * that does not exist yet, pointing at the canonical file.
  *
  * Call after installing the canonical binary. A platform CLI or daemon installed
  * before a rename resolves the legacy name; the link keeps it on the current
- * engine. It never replaces anything that exists, whether a real file (an older
- * engine someone may still run) or a link someone else placed. Never throws.
+ * engine. "Older" includes FORMER spellings, not only aliases: an installed CLI
+ * cannot be telemetry-gated the way a connected daemon can, and it does not stop
+ * existing when its spelling stops being accepted, so the link outlives the
+ * alias window (`firstPartyHarnessBinaryNames`). It never replaces anything that
+ * exists, whether a real file (an older engine someone may still run) or a link
+ * someone else placed. Never throws.
  */
 export function linkFirstPartyHarnessAliases(options = {}) {
     const env = options.env ?? process.env;
@@ -282,8 +298,8 @@ export function linkFirstPartyHarnessAliases(options = {}) {
     if (!isRealFile(fs.lstat(path.join(binDir, canonicalName)))) {
         return { moved, errors };
     }
-    for (const alias of FIRST_PARTY_HARNESS.aliases) {
-        const aliasName = firstPartyHarnessBinaryName(alias, platform);
+    for (const spelling of olderSpellings()) {
+        const aliasName = firstPartyHarnessBinaryName(spelling, platform);
         // Sidecar FIRST: a verifier that finds the binary link must find its record.
         for (const suffix of [FIRST_PARTY_HARNESS_PROVENANCE_SUFFIX, '']) {
             const target = `${canonicalName}${suffix}`;

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

@@ -49,11 +49,15 @@ export type HarnessTrustTier = 1 | 2 | 3;
  * in `daemon/src/harness-trust.ts` beside the gates that read it — the argument
  * belongs where the enforcement is, not in a shared vocabulary module.
  *
- * It is entered under EVERY spelling (`firstPartyHarnessSpellings`), not only the
- * canonical one. A backend name reaches this lookup from a daemon of any version,
- * and an alias that fell through to the Tier 3 default would silently strip the
- * harness of the trust the owner granted it — a failure that looks like a
- * permission prompt storm, not like a rename.
+ * It is entered under every ACCEPTED spelling (`firstPartyHarnessSpellings`), not
+ * only the canonical one. During a rename a backend name reaches this lookup from
+ * a daemon of any version, and an alias that fell through to the Tier 3 default
+ * would silently strip the harness of the trust the owner granted it — a failure
+ * that looks like a permission prompt storm, not like a rename.
+ *
+ * A FORMER spelling is deliberately absent. Nothing dispatches under one after
+ * contract, and a name that is not accepted must never inherit Tier 1 by being
+ * remembered: it falls to the default like any unknown backend.
  */
 export declare const HARNESS_TIERS: Readonly<Record<string, HarnessTrustTier>>;
 /**

package/dist/node_modules/@skrr-ai/auth-core/dist/esm/harnessTrust.js

@@ -48,11 +48,15 @@ import { firstPartyHarnessSpellings } from './firstPartyHarness.js';
  * in `daemon/src/harness-trust.ts` beside the gates that read it — the argument
  * belongs where the enforcement is, not in a shared vocabulary module.
  *
- * It is entered under EVERY spelling (`firstPartyHarnessSpellings`), not only the
- * canonical one. A backend name reaches this lookup from a daemon of any version,
- * and an alias that fell through to the Tier 3 default would silently strip the
- * harness of the trust the owner granted it — a failure that looks like a
- * permission prompt storm, not like a rename.
+ * It is entered under every ACCEPTED spelling (`firstPartyHarnessSpellings`), not
+ * only the canonical one. During a rename a backend name reaches this lookup from
+ * a daemon of any version, and an alias that fell through to the Tier 3 default
+ * would silently strip the harness of the trust the owner granted it — a failure
+ * that looks like a permission prompt storm, not like a rename.
+ *
+ * A FORMER spelling is deliberately absent. Nothing dispatches under one after
+ * contract, and a name that is not accepted must never inherit Tier 1 by being
+ * remembered: it falls to the default like any unknown backend.
  */
 export const HARNESS_TIERS = Object.freeze({
     // --- Tier 1: vendor first-party / audited ---

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

@@ -37,7 +37,7 @@ export { CONFIG_DIR_NAME, LEGACY_CONFIG_DIR_NAMES, NATIVE_ID_PREFIX, LEGACY_NATI
 export { findLegacyLocalState, describeLegacyState, type LegacyStateFinding, type LegacyStateReport, } from './legacyStatePreflight.js';
 export * from './firstPartyHarness.js';
 export { FIRST_PARTY_HARNESS_PREVIOUS_SUFFIX, FIRST_PARTY_HARNESS_PROVENANCE_SUFFIX, firstPartyHarnessBinDir, firstPartyHarnessHomeDir, firstPartyHarnessInstalledBinaryPath, linkFirstPartyHarnessAliases, migrateFirstPartyHarnessHome, type FirstPartyHarnessHomeFs, type FirstPartyHarnessHomeMigration, } from './firstPartyHarnessHome.js';
-export { DEFAULT_FIRST_PARTY_HARNESS_CHANNEL, FIRST_PARTY_HARNESS_CHANNELS, firstPartyHarnessChannelPrefix, firstPartyHarnessFeedBase, firstPartyHarnessFeedCandidates, isFirstPartyHarnessChannel, resolveChannelManifestUrl, resolveFirstPartyHarnessChannel, type FirstPartyHarnessChannel, type FirstPartyHarnessFeedCandidate, DEFAULT_SKY_CODE_CHANNEL, DEFAULT_SKY_CODE_FEED_BASE, SKY_CODE_CHANNELS, SKY_CODE_CHANNEL_ENV, SKY_CODE_MANIFEST_FILE, isSkyCodeChannel, resolveSkyCodeChannel, skyCodeChannelPrefix, skyCodeFeedBase, SKY_CODE_FEED_BASE_ENV, type SkyCodeChannel, } from './firstPartyHarnessChannels.js';
+export { DEFAULT_FIRST_PARTY_HARNESS_CHANNEL, FIRST_PARTY_HARNESS_CHANNELS, firstPartyHarnessChannelPrefix, firstPartyHarnessFeedBase, firstPartyHarnessFeedCandidates, isFirstPartyHarnessChannel, resolveChannelManifestUrl, resolveFirstPartyHarnessChannel, type FirstPartyHarnessChannel, type FirstPartyHarnessFeedCandidate, } from './firstPartyHarnessChannels.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';

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

@@ -149,10 +149,7 @@ export * from './firstPartyHarness.js';
 // Where the first-party harness lives under the skrr root, and the one-time move
 // that keeps legacy installs working across a rename. Node-only.
 export { FIRST_PARTY_HARNESS_PREVIOUS_SUFFIX, FIRST_PARTY_HARNESS_PROVENANCE_SUFFIX, firstPartyHarnessBinDir, firstPartyHarnessHomeDir, firstPartyHarnessInstalledBinaryPath, linkFirstPartyHarnessAliases, migrateFirstPartyHarnessHome, } from './firstPartyHarnessHome.js';
-export { DEFAULT_FIRST_PARTY_HARNESS_CHANNEL, FIRST_PARTY_HARNESS_CHANNELS, firstPartyHarnessChannelPrefix, firstPartyHarnessFeedBase, firstPartyHarnessFeedCandidates, isFirstPartyHarnessChannel, resolveChannelManifestUrl, resolveFirstPartyHarnessChannel, 
-// Deprecated names kept for installed CLIs that resolve this published package
-// with a caret range. Removed in the contract phase with a minor bump.
-DEFAULT_SKY_CODE_CHANNEL, DEFAULT_SKY_CODE_FEED_BASE, SKY_CODE_CHANNELS, SKY_CODE_CHANNEL_ENV, SKY_CODE_MANIFEST_FILE, isSkyCodeChannel, resolveSkyCodeChannel, skyCodeChannelPrefix, skyCodeFeedBase, SKY_CODE_FEED_BASE_ENV, } from './firstPartyHarnessChannels.js';
+export { DEFAULT_FIRST_PARTY_HARNESS_CHANNEL, FIRST_PARTY_HARNESS_CHANNELS, firstPartyHarnessChannelPrefix, firstPartyHarnessFeedBase, firstPartyHarnessFeedCandidates, isFirstPartyHarnessChannel, resolveChannelManifestUrl, resolveFirstPartyHarnessChannel, } from './firstPartyHarnessChannels.js';
 // Daemon release trust: the pinned ed25519 keys and the canonical signature
 // messages. Shared because BOTH the daemon (self-update) and the CLI
 // (`skrr daemon install`, which runs when there is no daemon to ask) verify the

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

@@ -55,4 +55,24 @@ export interface LegacyStateReport {
  * real `~` passes or fails based on who runs it.
  */
 export declare function findLegacyLocalState(home?: string): LegacyStateReport;
-export declare function describeLegacyState(report: LegacyStateReport, binaryName: string): string;
+/**
+ * Where the full procedure lives, by repository path. The refusal used to say
+ * "follow the team cutover runbook" without naming one, which stopped a person
+ * at a pointer they could not follow (OSK-6895). The steps the refusal prints
+ * are the runbook's own, so the path is for the parts a terminal message cannot
+ * carry: Linux and Windows service removal, Keychain entries, the old app.
+ */
+export declare const LEGACY_CUTOVER_RUNBOOK = "docs/runbooks/skrr-cutover-dev-machine.md";
+/**
+ * The message shown when preflight refuses.
+ *
+ * Written for someone who has just been stopped and wants to know why and what
+ * to do — so it names the exact paths, says explicitly that nothing was touched,
+ * and prints the cutover as commands to run rather than a pointer to follow. It
+ * does NOT offer a `--force`: the operator's next step is the backup, and a flag
+ * that skips a safety check is the flag everyone learns to paste.
+ *
+ * `command` is what the operator re-runs to install — `skrrd` when the runtime
+ * refused, `skrr daemon` when the CLI refused before fetching one.
+ */
+export declare function describeLegacyState(report: LegacyStateReport, command: string, platform?: NodeJS.Platform): string;

package/dist/node_modules/@skrr-ai/auth-core/dist/esm/legacyStatePreflight.js

@@ -43,22 +43,69 @@ export function findLegacyLocalState(home = os.homedir()) {
     return { findings, hasLegacyState: findings.length > 0 };
 }
 /**
- * The message shown when preflight refuses.
- *
- * Written for someone who has just been stopped and wants to know why and what
- * to do — so it names the exact paths, says explicitly that nothing was touched,
- * and points at the runbook rather than improvising a fix. It does NOT offer a
- * `--force`: the operator's next step is the backup the runbook specifies, and
- * a flag that skips a safety check is the flag everyone learns to paste.
- */
-/**
- * The pre-rename runtime binary. Named in the refusal above because deregistering
+ * The pre-rename runtime binary. Named in the refusal below because deregistering
  * the OLD service is the one step the NEW binary cannot do: `uninstall` resolves
  * the current profile's label (`ai.skrr.daemon.*`), and the legacy sweep is wired
  * only into the install path.
  */
 const LEGACY_BINARY_NAME = 'oversky';
-export function describeLegacyState(report, binaryName) {
+/**
+ * Where the full procedure lives, by repository path. The refusal used to say
+ * "follow the team cutover runbook" without naming one, which stopped a person
+ * at a pointer they could not follow (OSK-6895). The steps the refusal prints
+ * are the runbook's own, so the path is for the parts a terminal message cannot
+ * carry: Linux and Windows service removal, Keychain entries, the old app.
+ */
+export const LEGACY_CUTOVER_RUNBOOK = 'docs/runbooks/skrr-cutover-dev-machine.md';
+/** Credential file patterns the runbook strips from its backup (§5.5). */
+const BACKUP_CREDENTIAL_PATTERNS = ['auth.json', 'cli-auth.json', '*token*'];
+function posixQuote(value) {
+    return `'${value.split("'").join(`'\\''`)}'`;
+}
+function powershellQuote(value) {
+    return `'${value.split("'").join("''")}'`;
+}
+/**
+ * The commands for the three steps a person runs by hand, in the shell they are
+ * actually in. A POSIX `rm -rf` pasted into PowerShell is not an instruction.
+ */
+function cutoverCommands(paths, platform) {
+    if (platform === 'win32') {
+        const backupDir = '"$HOME\\skrr-cutover-backup"';
+        return {
+            backup: [
+                `New-Item -ItemType Directory -Force ${backupDir} | Out-Null`,
+                ...paths.map((p) => `Copy-Item -Recurse ${powershellQuote(p)} ${backupDir}`),
+                `Get-ChildItem -Recurse -File ${backupDir} -Include ${BACKUP_CREDENTIAL_PATTERNS.join(',')} | Remove-Item`,
+            ],
+            remove: paths.map((p) => `Remove-Item -Recurse -Force ${powershellQuote(p)}`),
+        };
+    }
+    const names = BACKUP_CREDENTIAL_PATTERNS.map((n) => `-name '${n}'`).join(' -o ');
+    return {
+        backup: [
+            'mkdir -p ~/skrr-cutover-backup && chmod 700 ~/skrr-cutover-backup',
+            `cp -a ${paths.map(posixQuote).join(' ')} ~/skrr-cutover-backup/`,
+            `find ~/skrr-cutover-backup -type f \\( ${names} \\) -delete`,
+        ],
+        remove: [`rm -rf ${paths.map(posixQuote).join(' ')}`],
+    };
+}
+/**
+ * The message shown when preflight refuses.
+ *
+ * Written for someone who has just been stopped and wants to know why and what
+ * to do — so it names the exact paths, says explicitly that nothing was touched,
+ * and prints the cutover as commands to run rather than a pointer to follow. It
+ * does NOT offer a `--force`: the operator's next step is the backup, and a flag
+ * that skips a safety check is the flag everyone learns to paste.
+ *
+ * `command` is what the operator re-runs to install — `skrrd` when the runtime
+ * refused, `skrr daemon` when the CLI refused before fetching one.
+ */
+export function describeLegacyState(report, command, platform = process.platform) {
+    const paths = report.findings.map((f) => f.path);
+    const { backup, remove } = cutoverCommands(paths, platform);
     const lines = [];
     lines.push('Found state from the previous product identity on this machine:');
     lines.push('');
@@ -69,20 +116,28 @@ export function describeLegacyState(report, binaryName) {
     lines.push('Installing beside it risks two runtimes holding two different service');
     lines.push('labels, each believing it owns the single-instance lock.');
     lines.push('');
-    lines.push('Nothing above has been read, copied or removed. Follow the team cutover');
-    lines.push('runbook — it takes a backup first — and then run this again:');
+    lines.push('Nothing above has been read, copied or removed, and no service was registered.');
+    lines.push('To finish the cutover:');
     lines.push('');
+    lines.push('  1. Keep a copy, with its credentials removed, in case you need an old setting:');
+    for (const line of backup)
+        lines.push(`       ${line}`);
     // The OLD binary, deliberately: it is the one that knows the old service
     // label. `<current> uninstall` resolves the CURRENT profile's label and would
     // report success while leaving the pre-rename service registered. Guarded by
     // "only if" rather than omitted, because this module inspects directories and
     // has no way to know whether that binary is still on PATH.
-    lines.push(`  ${LEGACY_BINARY_NAME} uninstall     # only if the old runtime is still installed —`);
-    lines.push(`                        # it is the one that knows the old service label`);
-    lines.push('  # then remove the directories listed above, per the runbook');
+    lines.push('  2. If the old runtime is still installed, deregister it with the old binary —');
+    lines.push('     it is the one that knows the old service label:');
+    lines.push(`       ${LEGACY_BINARY_NAME} uninstall`);
+    lines.push('  3. Remove the directories listed above:');
+    for (const line of remove)
+        lines.push(`       ${line}`);
+    lines.push('  4. Run this again:');
+    lines.push(`       ${command} install`);
     lines.push('');
-    lines.push(`Any pre-rename service still registered is swept by \`${binaryName} install\``);
-    lines.push('once those directories are gone, so re-running the install completes the');
-    lines.push('cutover either way.');
+    lines.push(`Any pre-rename service still registered is swept by \`${command} install\``);
+    lines.push('once those directories are gone, so step 4 completes the cutover either way.');
+    lines.push(`Full runbook, including Keychain entries and the old app: ${LEGACY_CUTOVER_RUNBOOK}`);
     return lines.join('\n');
 }

package/dist/node_modules/@skrr-ai/auth-core/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skrr-ai/auth-core",
-  "version": "0.2.2",
+  "version": "0.4.0",
   "main": "dist/cjs/index.js",
   "types": "dist/esm/index.d.ts",
   "exports": {