@skrr-ai/cli 0.1.47 → 0.1.48

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

@@ -29,28 +29,34 @@
  * never rename in place.
  */
 /**
- * The canonical daemon scope vocabulary. Six strings, frozen.
+ * The canonical daemon scope vocabulary. Seven strings, append-only.
  *
  *   - `daemon:tools:bash`        — bash tool execution
  *   - `daemon:tools:fs:read`     — Read tool (file read)
  *   - `daemon:tools:fs:write`    — Write + Edit tools (file mutation)
  *   - `daemon:browser:cdp`       — browser automation via CDP (reserved)
+ *   - `daemon:native-ui:control` — native app GUI control via the helper
  *   - `daemon:session:replay`    — `daemon:session:replay` socket event
  *   - `daemon:offline-queue`     — daemon-initiated offline queue
  *
  * Order is the consent-screen render order: tools-first, I/O second,
  * control-flow last.
+ *
+ * `daemon:native-ui:control` is deliberately NOT folded into
+ * `daemon:tools:bash`: a token minted to run shell commands must not
+ * thereby be able to click around the user's desktop (OSK-11009).
  */
 export const SCOPES = Object.freeze({
     TOOLS_BASH: 'daemon:tools:bash',
     TOOLS_FS_READ: 'daemon:tools:fs:read',
     TOOLS_FS_WRITE: 'daemon:tools:fs:write',
     BROWSER_CDP: 'daemon:browser:cdp',
+    NATIVE_UI_CONTROL: 'daemon:native-ui:control',
     SESSION_REPLAY: 'daemon:session:replay',
     OFFLINE_QUEUE: 'daemon:offline-queue',
 });
 /**
- * The six daemon scopes in canonical order. Frozen so consumers can
+ * The seven daemon scopes in canonical order. Frozen so consumers can
  * pass it directly to OAuth `scope` parameters without defensive
  * copies.
  */
@@ -59,6 +65,7 @@ export const ALL_DAEMON_SCOPES = Object.freeze([
     SCOPES.TOOLS_FS_READ,
     SCOPES.TOOLS_FS_WRITE,
     SCOPES.BROWSER_CDP,
+    SCOPES.NATIVE_UI_CONTROL,
     SCOPES.SESSION_REPLAY,
     SCOPES.OFFLINE_QUEUE,
 ]);
@@ -72,7 +79,7 @@ export function isDaemonScope(s) {
 }
 /**
  * `cli` — REST-only sign-in grant for first-party CLI clients. Peer
- * to the six daemon scopes; lives on `OAuthClient.allowedScopes` for
+ * to the daemon scopes; lives on `OAuthClient.allowedScopes` for
  * the `oversky-cli` client. See the data-schemas canonical for the
  * full reasoning behind keeping this OUT of `ALL_DAEMON_SCOPES` (the
  * grandfather sentinel `expandScopes(undefined)` would over-grant).

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

@@ -11,7 +11,7 @@ export { configureAuthCore, getAuthLogger, getAuthConfigDir, getAuthKillSwitches
 export { PermanentAuthFailure, TransientAuthFailure, type PermanentAuthReason, type ReauthState, type TokenPair, } from './types.js';
 export { decodeJwtExpiry, decodeJwtPayload } from './jwtUtils.js';
 export { isAuthExpiredSseEvent, handleMidStreamAuthExpiry, type ParsedSseLike, type AuthExpiredCallbacks, type HandleMidStreamAuthExpiryResult, } from './authExpiredDetector.js';
-export { formatReauthMessage, EXIT_NEEDS_REAUTH, type AuthFailureReason } from './messages.js';
+export { formatReauthMessage, reauthCommand, EXIT_NEEDS_REAUTH, type AuthFailureReason, } from './messages.js';
 export { classifyRefreshResponse, type RefreshResponseShape, type ClassifiedRefreshResult, type ClassifiedRefreshSuccess, type ClassifiedRefreshFailure, } from './refreshClassification.js';
 export { refreshDaemonToken, revokeDaemonRefreshSession, withAuthLock, persistReauthState, needsReauthState, clearReauthState, installLockExitHandlers, __refreshDiagnostics, __resetUnknown401StreaksForTest, UNKNOWN_401_BUDGET, } from './refresh.js';
 export { createRefreshScheduler, type RefreshScheduler, type RefreshSchedulerOptions, } from './refreshScheduler.js';

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

@@ -23,7 +23,7 @@ export { decodeJwtExpiry, decodeJwtPayload } from './jwtUtils.js';
 // header.
 export { isAuthExpiredSseEvent, handleMidStreamAuthExpiry, } from './authExpiredDetector.js';
 // Reauth messaging
-export { formatReauthMessage, EXIT_NEEDS_REAUTH } from './messages.js';
+export { formatReauthMessage, reauthCommand, EXIT_NEEDS_REAUTH, } from './messages.js';
 // Pure HTTP→{Permanent, Transient, Success} response classification —
 // exposed so RN-side clients can apply the same mapping daemon uses.
 export { classifyRefreshResponse, } from './refreshClassification.js';

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

@@ -1,4 +1,20 @@
 export type AuthFailureReason = 'REFRESH_INVALID' | 'REFRESH_REUSED' | 'REFRESH_EXPIRED' | 'SESSION_REVOKED' | 'TOKEN_EXPIRED' | 'TOKEN_INVALID' | 'UNKNOWN_401' | 'UNKNOWN';
+/**
+ * The command that recovers this process from a re-auth latch.
+ *
+ * ONE function owns this, because the answer is printed twice in the same
+ * millisecond — once in the human block below and once on the machine-readable
+ * `[oversky-reauth]` line a log scraper pages on — and the two used to be
+ * written independently. They disagreed: the block said `skrrd login --device`
+ * while the error line said `skrr login`, naming a different binary and
+ * different flags for one action, so an operator reading either one did
+ * something the other did not describe (OSK-10224).
+ *
+ * The binary is whatever the consumer registered with
+ * `configureAuthCore({ binaryName })` — the binary the user actually typed —
+ * and `--device` is added only when there is no TTY to open a browser from.
+ */
+export declare function reauthCommand(): string;
 export declare function formatReauthMessage(reason: AuthFailureReason | string): string;
 /**
  * Exit code for "permanent auth failure during initial connect" — picked to

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

@@ -17,17 +17,33 @@ const REASON_HUMAN = {
     UNKNOWN_401: 'skrr needs you to sign in again.',
     UNKNOWN: 'skrr needs you to sign in again.',
 };
+/**
+ * The command that recovers this process from a re-auth latch.
+ *
+ * ONE function owns this, because the answer is printed twice in the same
+ * millisecond — once in the human block below and once on the machine-readable
+ * `[oversky-reauth]` line a log scraper pages on — and the two used to be
+ * written independently. They disagreed: the block said `skrrd login --device`
+ * while the error line said `skrr login`, naming a different binary and
+ * different flags for one action, so an operator reading either one did
+ * something the other did not describe (OSK-10224).
+ *
+ * The binary is whatever the consumer registered with
+ * `configureAuthCore({ binaryName })` — the binary the user actually typed —
+ * and `--device` is added only when there is no TTY to open a browser from.
+ */
+export function reauthCommand() {
+    const bin = getAuthBinaryName();
+    return process.stdout.isTTY ? `${bin} login` : `${bin} login --device`;
+}
 export function formatReauthMessage(reason) {
     const norm = REASON_HUMAN[reason] || REASON_HUMAN.UNKNOWN;
-    const isHeadless = !process.stdout.isTTY;
-    const bin = getAuthBinaryName();
-    const cmd = isHeadless ? `${bin} login --device` : `${bin} login`;
     return [
         '',
         'skrr cannot connect — re-authentication required.',
         `  Reason: ${norm}`,
         '',
-        `  To continue, run:  ${cmd}`,
+        `  To continue, run:  ${reauthCommand()}`,
         '',
     ].join('\n');
 }

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

@@ -75,7 +75,7 @@ export declare const SENSITIVE_ENV_SUFFIXES: readonly string[];
  * `SECRETARY` untouched.
  */
 export declare const SENSITIVE_ENV_NAME_TOKENS: readonly string[];
-/** Specific OVERSKY_ vars to keep (the prefix sweep is broad on purpose). */
+/** Specific names to keep — the prefix sweeps are broad on purpose. */
 export declare const SENSITIVE_ENV_PREFIX_EXCEPTIONS: ReadonlySet<string>;
 /**
  * Build a sanitized snapshot of the parent's own env for a spawned

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

@@ -57,6 +57,9 @@
 export const SENSITIVE_ENV_VARS = new Set([
     'CLAUDE_CODE_OAUTH_TOKEN',
     'OVERSKY_TOKEN',
+    // The renamed credential alias (cli/src/lib/config.ts honors both spellings).
+    // Same double coverage as OVERSKY_TOKEN — name AND the SKRR_ prefix below.
+    'SKRR_TOKEN',
     'AWS_ACCESS_KEY_ID',
     'AWS_SECRET_ACCESS_KEY',
     'AWS_SESSION_TOKEN',
@@ -87,7 +90,16 @@ export const SENSITIVE_ENV_VARS = new Set([
     'LD_PRELOAD',
 ]);
 /** Variable name prefixes that should be stripped (catches families like AWS_*). */
-export const SENSITIVE_ENV_PREFIXES = ['AWS_', 'OVERSKY_'];
+export const SENSITIVE_ENV_PREFIXES = [
+    'AWS_',
+    'OVERSKY_',
+    // The renamed product namespace: SKRR_TOKEN, SKRR_REFRESH_TOKEN, the
+    // session-authority aliases (SKRR_SESSION_*, SKRR_BASE_URL), and the
+    // daemon's control-plane identity (SKRR_MACHINE_UUID, SKRR_LEASE_GENERATION)
+    // all carry authority a model-driven child must not inherit. Non-secret
+    // lane essentials live in SENSITIVE_ENV_PREFIX_EXCEPTIONS below.
+    'SKRR_',
+];
 /**
  * Credential-shaped suffixes are also forbidden. A fixed provider list is
  * never complete: a newly configured provider would otherwise leak its key
@@ -116,7 +128,7 @@ export const SENSITIVE_ENV_SUFFIXES = [
  * `SECRETARY` untouched.
  */
 export const SENSITIVE_ENV_NAME_TOKENS = ['SECRET'];
-/** Specific OVERSKY_ vars to keep (the prefix sweep is broad on purpose). */
+/** Specific names to keep — the prefix sweeps are broad on purpose. */
 export const SENSITIVE_ENV_PREFIX_EXCEPTIONS = new Set([
     // Headless flag is read by spawned tools to know they're inside the daemon —
     // not a secret. Add more here if a tool legitimately needs an OVERSKY_ var.
@@ -126,6 +138,16 @@ export const SENSITIVE_ENV_PREFIX_EXCEPTIONS = new Set([
     // know they're inside a supervised daemon on Linux/Windows in addition
     // to macOS launchd. Not a secret.
     'OVERSKY_SUPERVISOR',
+    // A deployment URL, not a credential. The rename to SKRR_SERVER_URL was
+    // chosen precisely because it survives the sanitizer
+    // (daemon/src/dedicated-tenant-env.ts), so a spawned lane's `skrr` reaches
+    // the deployment this machine is registered with.
+    'SKRR_SERVER_URL',
+    // The Dedicated Runtime workload marker the exec wrapper stamps into every
+    // tenant lane; grandchildren spawned from a lane (e.g. `skrr code` → the
+    // engine) must keep it to detect they already run as the workload uid. Not
+    // a secret — it authorizes nothing without the matching real uid.
+    'SKRR_WORKLOAD_UID',
 ]);
 /**
  * Build a sanitized snapshot of the parent's own env for a spawned

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

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