@skrr-ai/cli 0.1.114 → 0.1.116

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

@@ -1,159 +1,83 @@
 "use strict";
-/**
- * First-party harness update channels and feed resolution — the vocabulary, in
- * the ONE place both readers resolve.
- *
- * It lived in `daemon/src/sky-code/channels.ts`, whose only importer was the
- * daemon's own installer. That was fine while the daemon was the only thing that
- * needed it, and it stopped being fine the moment a user could be told to go
- * looking: `skrr code`'s not-installed message promised that `skrr code doctor`
- * would name "which channel this machine follows and whether that channel has a
- * published release", and the CLI had no access to any of it — so the sentence
- * described a diagnosis nobody had written (dogfood OSK-274).
- *
- * A MIRROR in the CLI was the obvious alternative and is the wrong answer here,
- * with precedent: OSK-3894 shipped exactly that for the harness trust tiers and
- * OSK-3897 removed it, because a mirror proves two copies agree rather than
- * proving there is one copy. `harnessTrust.ts` moved into this package for that
- * reason, the daemon re-exports it, and a static check keeps the daemon from
- * quietly redeclaring. This follows that road rather than reopening the one it
- * replaced.
- *
- * Channel vocabulary stays here. The shared signed installer lives beside it
- * in firstPartyHarnessUpdater.ts, used by CLI, Daemon and Desktop so updating
- * a local engine needs neither a running daemon nor an account.
- *
- * Every product-named value comes from `firstPartyHarness.ts`; nothing in this
- * file spells the product.
- */
-Object.defineProperty(exports, "__esModule", { value: true });
-exports.DEFAULT_FIRST_PARTY_HARNESS_CHANNEL = exports.FIRST_PARTY_HARNESS_CHANNELS = void 0;
-exports.isFirstPartyHarnessChannel = isFirstPartyHarnessChannel;
-exports.resolveFirstPartyHarnessChannel = resolveFirstPartyHarnessChannel;
-exports.firstPartyHarnessChannelPrefix = firstPartyHarnessChannelPrefix;
-exports.resolveChannelManifestUrl = resolveChannelManifestUrl;
-exports.firstPartyHarnessFeedBase = firstPartyHarnessFeedBase;
-exports.firstPartyHarnessFeedCandidates = firstPartyHarnessFeedCandidates;
-const firstPartyHarness_js_1 = require("./firstPartyHarness.js");
-/** Channels in promotion order. Index order IS the promotion order. */
-exports.FIRST_PARTY_HARNESS_CHANNELS = ['internal', 'canary', 'beta', 'stable'];
-/**
- * The channel a build without an explicit setting follows.
- *
- * `stable`, and never inferred from anything else. A default that drifted with
- * the build (say, dev builds silently on `canary`) would mean a user's update
- * path depended on how their binary happened to be produced.
- */
-exports.DEFAULT_FIRST_PARTY_HARNESS_CHANNEL = 'stable';
+var __defProp = Object.defineProperty;
+var __getOwnPropDesc = Object.getOwnPropertyDescriptor;
+var __getOwnPropNames = Object.getOwnPropertyNames;
+var __hasOwnProp = Object.prototype.hasOwnProperty;
+var __export = (target, all) => {
+  for (var name in all)
+    __defProp(target, name, { get: all[name], enumerable: true });
+};
+var __copyProps = (to, from, except, desc) => {
+  if (from && typeof from === "object" || typeof from === "function") {
+    for (let key of __getOwnPropNames(from))
+      if (!__hasOwnProp.call(to, key) && key !== except)
+        __defProp(to, key, { get: () => from[key], enumerable: !(desc = __getOwnPropDesc(from, key)) || desc.enumerable });
+  }
+  return to;
+};
+var __toCommonJS = (mod) => __copyProps(__defProp({}, "__esModule", { value: true }), mod);
+var firstPartyHarnessChannels_exports = {};
+__export(firstPartyHarnessChannels_exports, {
+  DEFAULT_FIRST_PARTY_HARNESS_CHANNEL: () => DEFAULT_FIRST_PARTY_HARNESS_CHANNEL,
+  FIRST_PARTY_HARNESS_CHANNELS: () => FIRST_PARTY_HARNESS_CHANNELS,
+  firstPartyHarnessChannelPrefix: () => firstPartyHarnessChannelPrefix,
+  firstPartyHarnessFeedBase: () => firstPartyHarnessFeedBase,
+  firstPartyHarnessFeedCandidates: () => firstPartyHarnessFeedCandidates,
+  isFirstPartyHarnessChannel: () => isFirstPartyHarnessChannel,
+  resolveChannelManifestUrl: () => resolveChannelManifestUrl,
+  resolveFirstPartyHarnessChannel: () => resolveFirstPartyHarnessChannel
+});
+module.exports = __toCommonJS(firstPartyHarnessChannels_exports);
+var import_firstPartyHarness = require("./firstPartyHarness.js");
+const FIRST_PARTY_HARNESS_CHANNELS = ["internal", "canary", "beta", "stable"];
+const DEFAULT_FIRST_PARTY_HARNESS_CHANNEL = "stable";
 function isFirstPartyHarnessChannel(value) {
-    return (typeof value === 'string' && exports.FIRST_PARTY_HARNESS_CHANNELS.includes(value));
+  return typeof value === "string" && FIRST_PARTY_HARNESS_CHANNELS.includes(value);
 }
-/**
- * The channel this process should follow.
- *
- * An unrecognised value falls back to the default rather than throwing. A
- * typo'd channel must not brick updates altogether — that turns a harmless
- * mistake into an un-updatable machine, which is the failure the updater exists
- * to prevent. The caller is handed `invalid` so it can say so out loud, and
- * `source` so it can name the variable it read.
- */
 function resolveFirstPartyHarnessChannel(env = process.env) {
-    const reading = (0, firstPartyHarness_js_1.readFirstPartyHarnessEnv)(env, 'channel');
-    if (!reading.value)
-        return { channel: exports.DEFAULT_FIRST_PARTY_HARNESS_CHANNEL };
-    if (isFirstPartyHarnessChannel(reading.value)) {
-        return { channel: reading.value, source: reading.name };
-    }
-    return {
-        channel: exports.DEFAULT_FIRST_PARTY_HARNESS_CHANNEL,
-        invalid: reading.value,
-        source: reading.name,
-    };
+  const reading = (0, import_firstPartyHarness.readFirstPartyHarnessEnv)(env, "channel");
+  if (!reading.value)
+    return { channel: DEFAULT_FIRST_PARTY_HARNESS_CHANNEL };
+  if (isFirstPartyHarnessChannel(reading.value)) {
+    return { channel: reading.value, source: reading.name };
+  }
+  return {
+    channel: DEFAULT_FIRST_PARTY_HARNESS_CHANNEL,
+    invalid: reading.value,
+    source: reading.name
+  };
 }
-/**
- * Where a channel's signed manifest lives, relative to a feed base.
- *
- * `stable` is NOT special-cased to `latest/`. Two paths that must always agree
- * is a pair that eventually will not, and the one that disagrees silently is
- * the one serving production. `latest/` remains for the daemon feed and for
- * anything already pointing at it; first-party harness channel clients read
- * `channels/<name>/` uniformly.
- */
 function firstPartyHarnessChannelPrefix(channel) {
-    return `channels/${channel}/`;
+  return `channels/${channel}/`;
 }
-/**
- * Manifest URL for a channel, or for a pinned version.
- *
- * A pinned version wins over the channel and reads its immutable per-release
- * copy: pinning means "this exact build", and a channel pointer that moved
- * underneath would make the pin a suggestion.
- *
- * Builds only MANIFEST urls, never artifact ones. `buildManifestMessage` signs
- * version, minimum, forceUpdate and the per-platform sha256s; `buildArtifactMessage`
- * signs the artifact URL. Neither signs a channel — so artifact URLs stay
- * channel-independent and promotion is a COPY OF AN ALREADY-SIGNED OBJECT that
- * never needs the release key. Put the channel in the artifact URL instead and
- * every promotion becomes a re-signing ceremony, which decides whether the
- * ed25519 key has to be reachable from routine automation. A helper here that
- * adjusted artifact urls would silently reintroduce exactly that coupling.
- *
- * The same property is what lets one signed manifest be served under every
- * spelling's prefix: the manifest's own path is not inside the signature.
- */
 function resolveChannelManifestUrl(input) {
-    const base = input.base.replace(/\/+$/, '');
-    if (input.pinnedVersion) {
-        return `${base}/releases/${input.pinnedVersion}/${input.manifestFilename}`;
-    }
-    return `${base}/${firstPartyHarnessChannelPrefix(input.channel)}${input.manifestFilename}`;
+  const base = input.base.replace(/\/+$/, "");
+  if (input.pinnedVersion) {
+    return `${base}/releases/${input.pinnedVersion}/${input.manifestFilename}`;
+  }
+  return `${base}/${firstPartyHarnessChannelPrefix(input.channel)}${input.manifestFilename}`;
 }
-/**
- * The feed base this process uses for the CANONICAL spelling.
- *
- * Explicit-only override: a production user must never be silently enrolled
- * onto a different feed. Selecting a feed changes WHICH signed manifest is read,
- * never WHETHER the signature is checked — every artifact is verified against
- * the pinned keys regardless of where it came from.
- */
 function firstPartyHarnessFeedBase(env = process.env) {
-    const override = (0, firstPartyHarness_js_1.readFirstPartyHarnessEnv)(env, 'updateFeedBase').value;
-    return (override || (0, firstPartyHarness_js_1.firstPartyHarnessDefaultFeedBase)()).replace(/\/+$/, '');
+  const override = (0, import_firstPartyHarness.readFirstPartyHarnessEnv)(env, "updateFeedBase").value;
+  return (override || (0, import_firstPartyHarness.firstPartyHarnessDefaultFeedBase)()).replace(/\/+$/, "");
 }
-/**
- * Every place a manifest may be published, in the order an installer should
- * try them: the canonical spelling first, then each alias.
- *
- * Why a list: publishing writes every accepted spelling, but an installer can
- * ship before the first release that does, and a machine can point at a feed
- * published by an older pipeline. An installer that asked only for the canonical
- * path would then find NOTHING and report "no release" on a feed that has one.
- * Trying the aliases on not-found closes that window in both directions without
- * anyone having to deploy in a particular order.
- *
- * WHICH spellings depends on what is being read, and the difference is the
- * point:
- *
- *   - a CHANNEL pointer (`pinnedRelease` false) is current state. Only the
- *     accepted spellings are tried: a former spelling's pointer stopped moving
- *     when publishing stopped writing it, so falling back to one would install
- *     whatever that channel named on the day of contract — a silent downgrade.
- *   - a PINNED release (`pinnedRelease` true) is an immutable artifact. Former
- *     spellings are tried too: a release published before the canonical prefix
- *     existed lives only under the old one, and its signed bytes — artifact URLs
- *     included — are the same wherever they are found.
- *
- * An operator override keeps its base and still tries each manifest filename,
- * since a dev feed staged by an older script names the file the old way.
- */
 function firstPartyHarnessFeedCandidates(env = process.env, options = {}) {
-    const override = (0, firstPartyHarness_js_1.readFirstPartyHarnessEnv)(env, 'updateFeedBase').value?.replace(/\/+$/, '');
-    const spellings = options.pinnedRelease
-        ? (0, firstPartyHarness_js_1.firstPartyHarnessArtifactSpellings)()
-        : (0, firstPartyHarness_js_1.firstPartyHarnessSpellings)();
-    return spellings.map((provider) => ({
-        base: override || (0, firstPartyHarness_js_1.firstPartyHarnessDefaultFeedBase)(provider),
-        manifestFilename: (0, firstPartyHarness_js_1.firstPartyHarnessManifestFile)(provider),
-        provider,
-    }));
+  const override = (0, import_firstPartyHarness.readFirstPartyHarnessEnv)(env, "updateFeedBase").value?.replace(/\/+$/, "");
+  const spellings = options.pinnedRelease ? (0, import_firstPartyHarness.firstPartyHarnessArtifactSpellings)() : (0, import_firstPartyHarness.firstPartyHarnessSpellings)();
+  return spellings.map((provider) => ({
+    base: override || (0, import_firstPartyHarness.firstPartyHarnessDefaultFeedBase)(provider),
+    manifestFilename: (0, import_firstPartyHarness.firstPartyHarnessManifestFile)(provider),
+    provider
+  }));
 }
+// Annotate the CommonJS export names for ESM import in node:
+0 && (module.exports = {
+  DEFAULT_FIRST_PARTY_HARNESS_CHANNEL,
+  FIRST_PARTY_HARNESS_CHANNELS,
+  firstPartyHarnessChannelPrefix,
+  firstPartyHarnessFeedBase,
+  firstPartyHarnessFeedCandidates,
+  isFirstPartyHarnessChannel,
+  resolveChannelManifestUrl,
+  resolveFirstPartyHarnessChannel
+});