@skrr-ai/auth-core 0.1.3 → 0.1.5

package/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/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/cjs/index.d.ts

@@ -36,3 +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';

package/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.verifyManifest = exports.verifyArtifact = exports.getDeltaFor = exports.buildManifestMessage = exports.buildArtifactMessage = exports.MAX_SIGS = exports.OVERSKY_RELEASE_PUBLIC_KEYS = 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,23 @@ 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; } });
+// 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
+// same manifest against the same root. See releaseManifest.ts for why a mirror
+// would be the wrong shape here.
+var releaseKeys_js_1 = require("./releaseKeys.js");
+Object.defineProperty(exports, "OVERSKY_RELEASE_PUBLIC_KEYS", { enumerable: true, get: function () { return releaseKeys_js_1.OVERSKY_RELEASE_PUBLIC_KEYS; } });
+var releaseManifest_js_1 = require("./releaseManifest.js");
+Object.defineProperty(exports, "MAX_SIGS", { enumerable: true, get: function () { return releaseManifest_js_1.MAX_SIGS; } });
+Object.defineProperty(exports, "buildArtifactMessage", { enumerable: true, get: function () { return releaseManifest_js_1.buildArtifactMessage; } });
+Object.defineProperty(exports, "buildManifestMessage", { enumerable: true, get: function () { return releaseManifest_js_1.buildManifestMessage; } });
+Object.defineProperty(exports, "getDeltaFor", { enumerable: true, get: function () { return releaseManifest_js_1.getDeltaFor; } });
+Object.defineProperty(exports, "verifyArtifact", { enumerable: true, get: function () { return releaseManifest_js_1.verifyArtifact; } });
+Object.defineProperty(exports, "verifyManifest", { enumerable: true, get: function () { return releaseManifest_js_1.verifyManifest; } });
+// 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/cjs/releaseKeys.d.ts

@@ -0,0 +1,87 @@
+/**
+ * releaseKeys.ts — ed25519 public keys pinned into the daemon binary AND the
+ * CLI that installs it.
+ *
+ * These are the trust anchors the self-updater (`update.ts`) uses to verify
+ * the signed release manifest (`daemon/latest/daemon-version.json`) and the
+ * downloaded binary artifact OFFLINE, before swapping its own binary. The
+ * matching PRIVATE half lives ONLY in CI as the Secrets Manager secret
+ * `OVERSKY_RELEASE_SIGNING_KEY` (ed25519, base64 PKCS8) — it is never checked
+ * into the repo and never shipped in the binary.
+ *
+ * CURRENT STATE: a key is pinned (`daemon-2026-07`, provisioned 2026-07-13), so
+ * self-update signature verification is FAIL-CLOSED — an unsigned or
+ * badly-signed manifest or binary aborts the update.
+ *
+ * READ THE NEXT PARAGRAPH BEFORE EMPTYING THIS ARRAY.
+ *
+ * The empty array is not a safe default; it is a DISABLED SECURITY CONTROL.
+ * With no key pinned, `update.ts` logs a warning and proceeds on TLS + SHA256
+ * only — and the SHA256 comes from the same manifest fetched over the same
+ * channel, so it defends against corruption in transit, not against a
+ * compromised or spoofed update feed. That posture (mirrored from the desktop
+ * `MANIFEST_PUBLIC_KEY=''` default) existed because the keypair had not been
+ * minted yet. It has been minted. Removing the last entry below silently
+ * re-disables offline verification on every daemon that ships the change, and
+ * nothing in the build fails to tell you.
+ *
+ * To add a key (rotation, or re-provisioning after a compromise) run
+ * `node scripts/generate-release-keypair.mjs`. It mints the ed25519 keypair,
+ * prints the ready-to-paste `{ keyId, publicKeySpkiB64 }` line for the array
+ * below, and prints the commands to store the PRIVATE half in the GitHub
+ * secret `OVERSKY_RELEASE_SIGNING_KEY` + AWS Secrets Manager. Never commit the
+ * private half; the CI signer reads `OVERSKY_RELEASE_SIGNING_KEY` and MUST
+ * import `buildArtifactMessage` / `buildManifestMessage` from
+ * `release-manifest.ts` rather than reimplementing them, so signer and verifier
+ * can never drift. Add the *next* key alongside the current one BEFORE
+ * rotating, so an in-flight rotation verifies against either — the full
+ * procedure is the rotation runbook on the array below.
+ */
+export interface ReleaseKey {
+    /** Human-readable key identifier, e.g. `daemon-2026-07`. Mirrors manifest `keyId`. */
+    keyId: string;
+    /** base64-encoded DER-SPKI ed25519 public key. */
+    publicKeySpkiB64: string;
+}
+/**
+ * Pinned release-signing public keys, newest first. Verification tries each
+ * key in turn (key rotation: keep current + next together during a rotation
+ * window). Non-empty → fail-closed, which is the state today. Empty →
+ * verification DISABLED with only a logged warning; see the file header before
+ * ever letting this array become empty.
+ *
+ * ZERO-DOWNTIME KEY-ROTATION RUNBOOK (config-only, no code change):
+ *   1. Mint the next keypair: `node scripts/generate-release-keypair.mjs --force`.
+ *   2. Pin its public half ABOVE the current key in the array below, and ship
+ *      that daemon build so the fleet trusts BOTH keys.
+ *   3. Store the new private half as the GH Actions secret
+ *      OVERSKY_RELEASE_SIGNING_KEY_NEXT (+ optional OVERSKY_RELEASE_KEY_ID_NEXT
+ *      label) — the signer then DUAL-SIGNS every release, emitting the additive
+ *      v2 `sigs[]` envelope (scalar `sig` stays = the current/primary key so
+ *      daemons that haven't picked up step 2 yet still verify).
+ *   4. Cut one release during the overlap window; it verifies for daemons
+ *      pinning the old key, the new key, or both (see release-manifest.test.ts
+ *      "ROTATION headroom").
+ *   5. Once the new-key build has saturated the fleet: promote NEXT→primary
+ *      (rename the secret to OVERSKY_RELEASE_SIGNING_KEY), drop the old key from
+ *      the array, and remove OVERSKY_RELEASE_SIGNING_KEY_NEXT. No downtime, and
+ *      no further code change — the multi-sig machinery is already shipped.
+ */
+/**
+ * NOT ROTATED FOR THE skrr RENAME. Owner decision, 2026-08-31.
+ *
+ * A rename is not a compromise. Custody is already established (GH Actions
+ * secret `OVERSKY_RELEASE_SIGNING_KEY` + AWS Secrets Manager), the keyId
+ * `daemon-2026-07` is a date, not a brand, and no user ever sees any of it.
+ *
+ * The rotation procedure documented above is shipped and correct — it just has
+ * nothing to do here. Running it would cost a fleet-saturation window (step 5)
+ * and buy nothing, and the window is exactly when a self-update path is most
+ * fragile. Rotate on a compromise or an expiry, not on a rename.
+ *
+ * The signed message prefix (`oversky-daemon-manifest`) stays for the same
+ * reason: it lives inside the signed bytes, so changing it breaks verification
+ * between old and new peers with zero user-visible benefit — the same call made
+ * for `X-Oversky-Origin`.
+ */
+export declare const OVERSKY_RELEASE_PUBLIC_KEYS: ReleaseKey[];

package/dist/cjs/releaseKeys.js

@@ -0,0 +1,94 @@
+"use strict";
+/**
+ * releaseKeys.ts — ed25519 public keys pinned into the daemon binary AND the
+ * CLI that installs it.
+ *
+ * These are the trust anchors the self-updater (`update.ts`) uses to verify
+ * the signed release manifest (`daemon/latest/daemon-version.json`) and the
+ * downloaded binary artifact OFFLINE, before swapping its own binary. The
+ * matching PRIVATE half lives ONLY in CI as the Secrets Manager secret
+ * `OVERSKY_RELEASE_SIGNING_KEY` (ed25519, base64 PKCS8) — it is never checked
+ * into the repo and never shipped in the binary.
+ *
+ * CURRENT STATE: a key is pinned (`daemon-2026-07`, provisioned 2026-07-13), so
+ * self-update signature verification is FAIL-CLOSED — an unsigned or
+ * badly-signed manifest or binary aborts the update.
+ *
+ * READ THE NEXT PARAGRAPH BEFORE EMPTYING THIS ARRAY.
+ *
+ * The empty array is not a safe default; it is a DISABLED SECURITY CONTROL.
+ * With no key pinned, `update.ts` logs a warning and proceeds on TLS + SHA256
+ * only — and the SHA256 comes from the same manifest fetched over the same
+ * channel, so it defends against corruption in transit, not against a
+ * compromised or spoofed update feed. That posture (mirrored from the desktop
+ * `MANIFEST_PUBLIC_KEY=''` default) existed because the keypair had not been
+ * minted yet. It has been minted. Removing the last entry below silently
+ * re-disables offline verification on every daemon that ships the change, and
+ * nothing in the build fails to tell you.
+ *
+ * To add a key (rotation, or re-provisioning after a compromise) run
+ * `node scripts/generate-release-keypair.mjs`. It mints the ed25519 keypair,
+ * prints the ready-to-paste `{ keyId, publicKeySpkiB64 }` line for the array
+ * below, and prints the commands to store the PRIVATE half in the GitHub
+ * secret `OVERSKY_RELEASE_SIGNING_KEY` + AWS Secrets Manager. Never commit the
+ * private half; the CI signer reads `OVERSKY_RELEASE_SIGNING_KEY` and MUST
+ * import `buildArtifactMessage` / `buildManifestMessage` from
+ * `release-manifest.ts` rather than reimplementing them, so signer and verifier
+ * can never drift. Add the *next* key alongside the current one BEFORE
+ * rotating, so an in-flight rotation verifies against either — the full
+ * procedure is the rotation runbook on the array below.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.OVERSKY_RELEASE_PUBLIC_KEYS = void 0;
+/**
+ * Pinned release-signing public keys, newest first. Verification tries each
+ * key in turn (key rotation: keep current + next together during a rotation
+ * window). Non-empty → fail-closed, which is the state today. Empty →
+ * verification DISABLED with only a logged warning; see the file header before
+ * ever letting this array become empty.
+ *
+ * ZERO-DOWNTIME KEY-ROTATION RUNBOOK (config-only, no code change):
+ *   1. Mint the next keypair: `node scripts/generate-release-keypair.mjs --force`.
+ *   2. Pin its public half ABOVE the current key in the array below, and ship
+ *      that daemon build so the fleet trusts BOTH keys.
+ *   3. Store the new private half as the GH Actions secret
+ *      OVERSKY_RELEASE_SIGNING_KEY_NEXT (+ optional OVERSKY_RELEASE_KEY_ID_NEXT
+ *      label) — the signer then DUAL-SIGNS every release, emitting the additive
+ *      v2 `sigs[]` envelope (scalar `sig` stays = the current/primary key so
+ *      daemons that haven't picked up step 2 yet still verify).
+ *   4. Cut one release during the overlap window; it verifies for daemons
+ *      pinning the old key, the new key, or both (see release-manifest.test.ts
+ *      "ROTATION headroom").
+ *   5. Once the new-key build has saturated the fleet: promote NEXT→primary
+ *      (rename the secret to OVERSKY_RELEASE_SIGNING_KEY), drop the old key from
+ *      the array, and remove OVERSKY_RELEASE_SIGNING_KEY_NEXT. No downtime, and
+ *      no further code change — the multi-sig machinery is already shipped.
+ */
+/**
+ * NOT ROTATED FOR THE skrr RENAME. Owner decision, 2026-08-31.
+ *
+ * A rename is not a compromise. Custody is already established (GH Actions
+ * secret `OVERSKY_RELEASE_SIGNING_KEY` + AWS Secrets Manager), the keyId
+ * `daemon-2026-07` is a date, not a brand, and no user ever sees any of it.
+ *
+ * The rotation procedure documented above is shipped and correct — it just has
+ * nothing to do here. Running it would cost a fleet-saturation window (step 5)
+ * and buy nothing, and the window is exactly when a self-update path is most
+ * fragile. Rotate on a compromise or an expiry, not on a rename.
+ *
+ * The signed message prefix (`oversky-daemon-manifest`) stays for the same
+ * reason: it lives inside the signed bytes, so changing it breaks verification
+ * between old and new peers with zero user-visible benefit — the same call made
+ * for `X-Oversky-Origin`.
+ */
+exports.OVERSKY_RELEASE_PUBLIC_KEYS = [
+    // ── NEXT key goes ABOVE this line during a rotation (newest first). ──
+    // Provisioned 2026-07-13. Private half: GH Actions secret
+    // OVERSKY_RELEASE_SIGNING_KEY + AWS Secrets Manager
+    // (us-east-1: oversky/daemon/release-signing-key). Self-update signature
+    // verification is now FAIL-CLOSED.
+    {
+        keyId: 'daemon-2026-07',
+        publicKeySpkiB64: 'MCowBQYDK2VwAyEA7ArbRnkbRW354XZ4MNS1MRLCwrTFauQzsw4GP27mMfI=',
+    },
+];

package/dist/cjs/releaseManifest.d.ts

@@ -0,0 +1,161 @@
+import { type ReleaseKey } from './releaseKeys.js';
+export type { ReleaseKey } from './releaseKeys.js';
+/**
+ * One entry in a v2 multi-signature envelope. `sig` is a base64 ed25519
+ * signature over the EXACT SAME bytes as the v1 scalar `sig` (buildArtifact/
+ * ManifestMessage) — v2 is an envelope change, not a wire-format change. The
+ * `keyId` is an ADVISORY label only: verification trial-verifies every sig
+ * against every pinned key and NEVER consults keyId, so a mislabeled keyId can
+ * neither grant nor withhold trust (this structurally defeats keyId
+ * substitution). It exists for operator diagnostics ("which key signed this?").
+ */
+export interface ManifestSignature {
+    keyId: string;
+    /** base64 ed25519 signature over the same bytes as the v1 `sig`. */
+    sig: string;
+}
+/**
+ * v-delta (optional): a differential-update patch that transforms a specific
+ * PRIOR version's binary into this release's binary — a brotli-compressed
+ * fossil delta. UNSIGNED, exactly like `keyId`/`size`/`sigs` (NOT part of
+ * buildArtifactMessage/buildManifestMessage), so it never changes the signed
+ * bytes and #782's envelope invariant holds. Trust comes SOLELY from verifying
+ * the RECONSTRUCTED binary against the signed `sha256` + ed25519 gates: a
+ * tampered/garbage delta yields a non-matching binary and the daemon falls back
+ * to the full signed download. `sha256` here is TRANSPORT integrity of the patch
+ * file only — NEVER an install gate.
+ */
+export interface DeltaDescriptor {
+    /** Absolute public URL of the brotli-compressed fossil delta patch. */
+    url: string;
+    /** Lowercase hex sha256 of the patch file — transport integrity, not trust. */
+    sha256: string;
+    /** Size of the patch file in bytes. */
+    size: number;
+}
+/** One downloadable, immutable binary for a single `<platform>-<arch>` target. */
+export interface PlatformArtifact {
+    /** Bare filename, e.g. `oversky-darwin-arm64`. */
+    file: string;
+    /** Absolute public URL under the CloudFront feed. */
+    url: string;
+    /** Lowercase hex sha256 of the binary bytes. */
+    sha256: string;
+    /** Size in bytes. */
+    size: number;
+    /** base64 ed25519 signature over buildArtifactMessage(...) — the PRIMARY key. */
+    sig: string;
+    /**
+     * v2 (optional): EVERY signature (primary + rotation key) over the same
+     * bytes as `sig`. Emitted ONLY during a key-rotation window (>1 signing key);
+     * absent in steady single-key state, so a normal manifest is byte-identical
+     * to v1. When present it is the authoritative set — see verifyWithKeysMulti.
+     */
+    sigs?: ManifestSignature[];
+    /**
+     * v-delta (optional, UNSIGNED): differential-update patches keyed by the
+     * from-version they apply to (e.g. `"0.8.0"`). Absent in steady state. See
+     * DeltaDescriptor — the reconstructed binary is verified against `sha256`
+     * above, so deltas add NO trust surface.
+     */
+    deltas?: Record<string, DeltaDescriptor>;
+}
+/**
+ * The signed release manifest. `platforms` is keyed by `<platform>-<arch>`
+ * (e.g. `darwin-arm64`, `linux-x64`). The top-level `sig` covers
+ * buildManifestMessage(manifest-without-sig).
+ */
+export interface DaemonVersionManifest<TPolicy = unknown> {
+    schemaVersion: number;
+    version: string;
+    minimum: string;
+    forceUpdate: boolean;
+    keyId: string;
+    platforms: Record<string, PlatformArtifact>;
+    /**
+     * base64 ed25519 signature over buildManifestMessage(this-without-sig) — the
+     * PRIMARY key. Kept populated even in v2 so an OLD (v1-only) daemon still
+     * verifies against the key the lagging fleet trusts.
+     */
+    sig: string;
+    /**
+     * v2 (optional): EVERY manifest signature (primary + rotation key). Emitted
+     * ONLY during a rotation window; when present it is authoritative — see
+     * verifyWithKeysMulti. `schemaVersion` stays a reader hint (unsigned, inert);
+     * v2 is detected by `Array.isArray(sigs)`, not by the version number.
+     */
+    sigs?: ManifestSignature[];
+    /**
+     * Independently signed release decision envelope. It is intentionally not
+     * part of the v1 manifest message so existing daemons can ignore it; newer
+     * daemons verify this nested signature before honouring compatibility or
+     * rollout controls.
+     */
+    policy?: TPolicy;
+}
+/**
+ * Canonical bytes signed for a single platform artifact. Newline-joined, fixed
+ * field order, `v1` tag. `sha256` is lowercased so the message is stable
+ * regardless of the hex casing the caller supplies.
+ */
+export declare function buildArtifactMessage(a: {
+    platform: string;
+    version: string;
+    sha256: string;
+    url: string;
+}): string;
+/**
+ * Canonical bytes signed for the whole manifest (excluding the top-level
+ * `sig`). Platform keys are sorted so the message is independent of JSON key
+ * order; each contributes `<platform>=<sha256-lower>`. `forceUpdate` is
+ * serialized strictly (`String(forceUpdate === true)` → `"true"`/`"false"`).
+ */
+export declare function buildManifestMessage(m: {
+    version: string;
+    minimum: string;
+    forceUpdate: boolean;
+    platforms: Record<string, {
+        sha256: string;
+    }>;
+}): string;
+/**
+ * Discriminated verification result:
+ *  - `{ ok: true }`         — signature verified against a pinned key.
+ *  - `{ ok: false, reason }` — keys are present but nothing verified (FAIL-CLOSED).
+ *  - `{ disabled: true }`   — no keys pinned; verification is intentionally off.
+ */
+export type VerifyResult = {
+    ok: true;
+} | {
+    ok: false;
+    reason: string;
+} | {
+    disabled: true;
+};
+/**
+ * Upper bound on signatures we will trial-verify per artifact/manifest. A
+ * rotation window needs at most 2–3 (current + next). `sigs[]` is NOT part of
+ * the signed bytes, so an attacker can pad it; this cap bounds the verify work
+ * they can force to O(MAX_SIGS × pinnedKeys) — a few hundred microseconds even
+ * at the cap. A valid signature placed beyond the cap is treated as absent.
+ */
+export declare const MAX_SIGS = 8;
+/**
+ * Verify a single platform artifact's `sig` over buildArtifactMessage(...).
+ * `platform` is the `<platform>-<arch>` key; `version` is the manifest version
+ * the artifact belongs to. Defaults to the baked-in pinned keys.
+ */
+export declare function verifyArtifact(platform: string, version: string, artifact: PlatformArtifact, keys?: readonly ReleaseKey[]): VerifyResult;
+/**
+ * Verify the manifest's top-level `sig` over buildManifestMessage(this).
+ * Defaults to the baked-in pinned keys.
+ */
+export declare function verifyManifest(manifest: DaemonVersionManifest, keys?: readonly ReleaseKey[]): VerifyResult;
+/**
+ * Look up a delta patch that transforms `fromVersion`'s binary into this
+ * artifact's binary. Returns null when none is advertised or the descriptor is
+ * malformed — the caller then does a full download. PURE; validates shape only
+ * (the delta is UNSIGNED, so trust comes from verifying the RECONSTRUCTED binary
+ * against the signed `artifact.sha256`, not from this metadata).
+ */
+export declare function getDeltaFor(artifact: PlatformArtifact, fromVersion: string): DeltaDescriptor | null;