wyvrnpm 2.11.0 → 2.12.2

package/src/conf/namespaces.js

@@ -1,94 +1,94 @@
-'use strict';
-
-// Allow-list of recognised `conf` namespaces (PLAN-CONF.md §4.1).
-//
-// Adding a new namespace is an intentional act — the plan commits to
-// expanding this file only when a concrete use case lands, not
-// speculatively. Phase 1 ships `cmake.cache.*` only; every other
-// namespace (env.*, build.*, tool.*) is reserved but not yet valid.
-//
-// Each entry describes how leaf names under that namespace are
-// validated. A namespace with `leaf: true` accepts any non-empty leaf
-// name; a namespace with `leaf: /regex/` enforces the regex at load
-// time. The regex only validates the leaf name — leaf VALUES are
-// normalised separately in ../conf/index.js.
-
-/**
- * @typedef {Object} NamespaceSpec
- * @property {RegExp} leaf
- *   Pattern that every leaf name under this namespace must satisfy.
- * @property {string} description
- *   Human-readable one-liner shown in error messages.
- */
-
-/** @type {Record<string, NamespaceSpec>} */
-const NAMESPACES = {
-  'cmake.cache': {
-    // CMake variable names: C/C++ identifier rules, no hyphens.
-    leaf:        /^[A-Za-z_][A-Za-z0-9_]*$/,
-    description: 'CMake cache variables — baked into CMakePresets.json cacheVariables.',
-  },
-};
-
-/**
- * Parse a full dotted conf key (e.g. `cmake.cache.CHROMA_ENABLE_TEST`)
- * into its namespace prefix and leaf name. The namespace is the
- * longest matching prefix registered in NAMESPACES; anything after is
- * the leaf.
- *
- * Returns `{ namespace, leaf }` on success, `null` when the key does
- * not belong to any registered namespace or has no leaf component.
- *
- * @param {string} key
- * @returns {{ namespace: string, leaf: string } | null}
- */
-function splitKey(key) {
-  // Try longer namespaces first so "a.b.c" prefers namespace "a.b"
-  // over a hypothetical namespace "a".
-  const known = Object.keys(NAMESPACES).sort((a, b) => b.length - a.length);
-  for (const ns of known) {
-    const prefix = `${ns}.`;
-    if (key.startsWith(prefix)) {
-      const leaf = key.slice(prefix.length);
-      if (leaf.length === 0) return null;
-      return { namespace: ns, leaf };
-    }
-  }
-  return null;
-}
-
-/**
- * Validate a flat `{key: value}` map against the namespace allow-list.
- * Throws on the first offender (fail-fast, matches the Zip Slip
- * validator's style). Leaf VALUES are not type-checked here — values
- * arrive as strings from the CLI, normalised from JSON elsewhere; type
- * enforcement happens in ../conf/index.js at merge time.
- *
- * @param {Record<string, string>} flatConf
- * @throws {Error} if any key's namespace or leaf is rejected.
- */
-function validateFlatConfKeys(flatConf) {
-  const knownList = Object.keys(NAMESPACES).sort().join(', ');
-  for (const key of Object.keys(flatConf)) {
-    const parts = splitKey(key);
-    if (!parts) {
-      throw new Error(
-        `unknown conf namespace in ${JSON.stringify(key)} — ` +
-        `phase-1 allow-list: [${knownList}]`,
-      );
-    }
-    const spec = NAMESPACES[parts.namespace];
-    if (!spec.leaf.test(parts.leaf)) {
-      throw new Error(
-        `invalid leaf name ${JSON.stringify(parts.leaf)} for conf namespace ` +
-        `"${parts.namespace}" — ${spec.description}`,
-      );
-    }
-  }
-}
-
-module.exports = {
-  NAMESPACES,
-  splitKey,
-  validateFlatConfKeys,
-};
+'use strict';
+
+// Allow-list of recognised `conf` namespaces (PLAN-CONF.md §4.1).
+//
+// Adding a new namespace is an intentional act — the plan commits to
+// expanding this file only when a concrete use case lands, not
+// speculatively. Phase 1 ships `cmake.cache.*` only; every other
+// namespace (env.*, build.*, tool.*) is reserved but not yet valid.
+//
+// Each entry describes how leaf names under that namespace are
+// validated. A namespace with `leaf: true` accepts any non-empty leaf
+// name; a namespace with `leaf: /regex/` enforces the regex at load
+// time. The regex only validates the leaf name — leaf VALUES are
+// normalised separately in ../conf/index.js.
+
+/**
+ * @typedef {Object} NamespaceSpec
+ * @property {RegExp} leaf
+ *   Pattern that every leaf name under this namespace must satisfy.
+ * @property {string} description
+ *   Human-readable one-liner shown in error messages.
+ */
+
+/** @type {Record<string, NamespaceSpec>} */
+const NAMESPACES = {
+  'cmake.cache': {
+    // CMake variable names: C/C++ identifier rules, no hyphens.
+    leaf:        /^[A-Za-z_][A-Za-z0-9_]*$/,
+    description: 'CMake cache variables — baked into CMakePresets.json cacheVariables.',
+  },
+};
+
+/**
+ * Parse a full dotted conf key (e.g. `cmake.cache.CHROMA_ENABLE_TEST`)
+ * into its namespace prefix and leaf name. The namespace is the
+ * longest matching prefix registered in NAMESPACES; anything after is
+ * the leaf.
+ *
+ * Returns `{ namespace, leaf }` on success, `null` when the key does
+ * not belong to any registered namespace or has no leaf component.
+ *
+ * @param {string} key
+ * @returns {{ namespace: string, leaf: string } | null}
+ */
+function splitKey(key) {
+  // Try longer namespaces first so "a.b.c" prefers namespace "a.b"
+  // over a hypothetical namespace "a".
+  const known = Object.keys(NAMESPACES).sort((a, b) => b.length - a.length);
+  for (const ns of known) {
+    const prefix = `${ns}.`;
+    if (key.startsWith(prefix)) {
+      const leaf = key.slice(prefix.length);
+      if (leaf.length === 0) return null;
+      return { namespace: ns, leaf };
+    }
+  }
+  return null;
+}
+
+/**
+ * Validate a flat `{key: value}` map against the namespace allow-list.
+ * Throws on the first offender (fail-fast, matches the Zip Slip
+ * validator's style). Leaf VALUES are not type-checked here — values
+ * arrive as strings from the CLI, normalised from JSON elsewhere; type
+ * enforcement happens in ../conf/index.js at merge time.
+ *
+ * @param {Record<string, string>} flatConf
+ * @throws {Error} if any key's namespace or leaf is rejected.
+ */
+function validateFlatConfKeys(flatConf) {
+  const knownList = Object.keys(NAMESPACES).sort().join(', ');
+  for (const key of Object.keys(flatConf)) {
+    const parts = splitKey(key);
+    if (!parts) {
+      throw new Error(
+        `unknown conf namespace in ${JSON.stringify(key)} — ` +
+        `phase-1 allow-list: [${knownList}]`,
+      );
+    }
+    const spec = NAMESPACES[parts.namespace];
+    if (!spec.leaf.test(parts.leaf)) {
+      throw new Error(
+        `invalid leaf name ${JSON.stringify(parts.leaf)} for conf namespace ` +
+        `"${parts.namespace}" — ${spec.description}`,
+      );
+    }
+  }
+}
+
+module.exports = {
+  NAMESPACES,
+  splitKey,
+  validateFlatConfKeys,
+};

package/src/context.js

@@ -1,230 +1,230 @@
-'use strict';
-
-/**
- * CommandContext — the shared per-invocation state every command consumes.
- *
- * Commands used to each re-read the manifest, re-resolve the profile name,
- * re-read config, re-resolve auth, and each toggle JSON mode on the logger.
- * The divergence was cheap at 11 commands; it starts costing real bugs
- * once F3 (`tool_requires`) and F4 (build/host profile split) double the
- * flag surface. See [claude/PLAN-COMMAND-CONTEXT.md](../claude/PLAN-COMMAND-CONTEXT.md).
- *
- * `buildContext(argv)` runs once at the top of each command. It:
- *   - resolves filesystem anchors (rootDir, manifestPath)
- *   - reads config once
- *   - resolves the profile-name fallback chain + loads the profile
- *   - parses CLI options + conf (format-level only; namespace allow-
- *     listing happens later in the sinks that need it)
- *   - sets JSON mode on the logger if --format=json
- *   - exposes an auth helper pre-curried with CLI --token / --token-env
- *   - exposes a lazy manifest getter (show never reads the manifest)
- *
- * `buildContext` does NOT do source filtering — each command has subtly
- * different CLI shape there (publish takes name-or-URL, install/show
- * take URL arrays, pin-resolution only matters for install). That
- * stays per-command until a second feature shows the same duplication.
- *
- * Errors: `buildContext` THROWS on all input-validation failures. Each
- * command wraps the call in one try/catch that does `log.error + exit`.
- * This keeps buildContext unit-testable; behaviour from the user's
- * point of view is unchanged.
- */
-
-const fs   = require('fs');
-const path = require('path');
-
-const { readConfig }        = require('./config');
-const { loadProfile }       = require('./profile');
-const { readManifest }      = require('./manifest');
-const { resolveSourceAuth } = require('./auth');
-const { parseCliOptions }   = require('./options');
-const { parseCliConf }      = require('./conf');
-const log                   = require('./logger');
-
-// ---------------------------------------------------------------------------
-// Internal helpers
-// ---------------------------------------------------------------------------
-
-/**
- * Resolve the active profile name per the long-standing precedence:
- *   --profile > config.defaultProfile > 'default'
- */
-function resolveProfileName(argv, config) {
-  if (typeof argv.profile === 'string' && argv.profile.length > 0) {
-    return argv.profile;
-  }
-  if (typeof config.defaultProfile === 'string' && config.defaultProfile.length > 0) {
-    return config.defaultProfile;
-  }
-  return 'default';
-}
-
-/**
- * Normalise CLI flags into the stable `ctx.flags` shape. Centralising
- * defaults here means individual commands don't each re-apply
- * `?? 'never'` / `?? 'Release'` / etc.
- *
- * Flags that are command-specific (argv.preset, argv.pkg, argv.clean,
- * argv.verbose, argv.generator, argv.install, argv.installPrefix,
- * argv.uploadSource, argv.autoInstall, argv.noGpgSign, ...) stay on
- * argv and commands read them there. `ctx.argv` is the escape hatch.
- */
-function normaliseFlags(argv) {
-  return {
-    format:      argv.format === 'json' ? 'json' : 'text',
-    dryRun:      argv.dryRun === true,
-    build:       argv.build ?? 'never',
-    uploadBuilt: argv.uploadBuilt === true,
-    force:       argv.force === true,
-    platform:    argv.platform ?? defaultPlatform(),
-    timeout:     typeof argv.timeout === 'number' ? argv.timeout : 300,
-  };
-}
-
-/**
- * Default platform string when --platform is absent. Mirrors what
- * bin/wyvrn.js passes when yargs applies its own default — keeping
- * it here makes context.js testable without exercising the CLI layer.
- */
-function defaultPlatform() {
-  if (process.platform === 'win32') {
-    return process.arch === 'ia32' ? 'win_x86' : 'win_x64';
-  }
-  if (process.platform === 'darwin') return 'macos';
-  return 'linux';
-}
-
-/**
- * Produce a frozen `{ host, build }` profile pair. Today both point at
- * the same resolved object — when F4 (build/host profile split) lands,
- * only this function changes; every command reading `ctx.profiles.host`
- * or `ctx.profiles.build` continues to work.
- *
- * The two sub-objects share a reference today. A regression test in
- * tests/context.test.js asserts `ctx.profiles.host === ctx.profiles.build`
- * — that test is expected to be removed (not fixed) when F4 makes them
- * legitimately distinct.
- */
-function resolveProfiles(argv, config) {
-  const name = resolveProfileName(argv, config);
-  const { profile, fromFile } = loadProfile(name);
-  const entry = Object.freeze({ name, profile, fromFile });
-  return Object.freeze({ host: entry, build: entry });
-}
-
-// ---------------------------------------------------------------------------
-// buildContext
-// ---------------------------------------------------------------------------
-
-/**
- * Build the per-invocation CommandContext.
- *
- * @param {object} argv - yargs-parsed argument map. Fields read:
- *   root, manifest, profile, format, dryRun, build, uploadBuilt,
- *   force, platform, timeout, token, tokenEnv, option, conf.
- *   Command-specific fields pass through on ctx.argv unchanged.
- *
- * @returns {CommandContext}
- *
- * @throws on:
- *   - parseCliOptions: malformed `-o pkg:name=value`
- *   - parseCliConf:    malformed `--conf KEY=VALUE`
- *   - loadProfile:     malformed profile JSON, cycle in `extends`, etc.
- *
- * Does NOT throw on:
- *   - missing manifest (lazy — throws at first ctx.manifest access)
- *   - missing config   (readConfig returns empty defaults)
- *   - missing profile  (loadProfile falls back to detectProfile())
- *   - missing --token-env value (resolveSourceAuth throws at ctx.auth.for time)
- */
-function buildContext(argv = {}) {
-  // 1. Filesystem anchors — pure path math, no I/O.
-  const rootDir = path.resolve(argv.root ?? '.');
-  const manifestPath = path.resolve(
-    argv.manifest ?? path.join(rootDir, 'wyvrn.json'),
-  );
-
-  // 2. Config — sync, small file, every command needs at least .defaultProfile.
-  const config = readConfig();
-
-  // 3. Profile (F4-ready shape).
-  const profiles = resolveProfiles(argv, config);
-
-  // 4. CLI auth, kept as the raw pair. Actual token lookup happens
-  //    through ctx.auth.for(sourceEntry), which runs resolveSourceAuth
-  //    each time so --token-env misses surface at use (same as today).
-  const authCli = Object.freeze({
-    token:    typeof argv.token    === 'string' ? argv.token    : undefined,
-    tokenEnv: typeof argv.tokenEnv === 'string' ? argv.tokenEnv : undefined,
-  });
-
-  // 5. CLI options + conf — format-level parsing only. Namespace
-  //    allow-listing for conf happens later in resolveEffectiveConf;
-  //    options validation against the recipe's declared `allowed` set
-  //    happens at resolveEffectiveOptions time.
-  //    Both can throw — that's the contract: buildContext surfaces
-  //    input-level errors up front.
-  const cliOptions = parseCliOptions(argv.option);
-  const cliConf    = parseCliConf(argv.conf);
-
-  // 6. Flags.
-  const flags = normaliseFlags(argv);
-
-  // 7. JSON mode — side effect that must happen before the command
-  //    starts logging. Flipping the logger here means every command
-  //    that constructs a ctx gets JSON mode right automatically.
-  if (flags.format === 'json') log.setJsonMode(true);
-
-  // 8. Assemble.
-  const ctx = {
-    rootDir,
-    manifestPath,
-    cwd: process.cwd(),
-    profiles,
-    config,
-    auth: Object.freeze({
-      cli: authCli,
-      for: (sourceEntry) => resolveSourceAuth(authCli, sourceEntry ?? null),
-    }),
-    cliOptions,
-    cliConf,
-    flags,
-    argv,
-  };
-
-  // 9. Lazy manifest getter. Most commands need it; `show` does not.
-  //    Defining as a getter means:
-  //      - show pays nothing.
-  //      - other commands pay once, cached.
-  //      - an invalid manifest surfaces at first use, not at ctx
-  //        construction — so `show` never trips over it.
-  let manifestCache = null;
-  let manifestLoaded = false;
-  Object.defineProperty(ctx, 'manifest', {
-    configurable: false,
-    enumerable:   true,
-    get() {
-      if (!manifestLoaded) {
-        if (!fs.existsSync(manifestPath)) {
-          throw new Error(`Manifest not found: ${manifestPath}`);
-        }
-        manifestCache = readManifest(manifestPath);
-        manifestLoaded = true;
-      }
-      return manifestCache;
-    },
-  });
-
-  return ctx;
-}
-
-module.exports = {
-  buildContext,
-  // Exported for unit tests — kept out of the default import surface.
-  _helpers: {
-    resolveProfileName,
-    normaliseFlags,
-    defaultPlatform,
-    resolveProfiles,
-  },
-};
+'use strict';
+
+/**
+ * CommandContext — the shared per-invocation state every command consumes.
+ *
+ * Commands used to each re-read the manifest, re-resolve the profile name,
+ * re-read config, re-resolve auth, and each toggle JSON mode on the logger.
+ * The divergence was cheap at 11 commands; it starts costing real bugs
+ * once F3 (`tool_requires`) and F4 (build/host profile split) double the
+ * flag surface. See [claude/PLAN-COMMAND-CONTEXT.md](../claude/PLAN-COMMAND-CONTEXT.md).
+ *
+ * `buildContext(argv)` runs once at the top of each command. It:
+ *   - resolves filesystem anchors (rootDir, manifestPath)
+ *   - reads config once
+ *   - resolves the profile-name fallback chain + loads the profile
+ *   - parses CLI options + conf (format-level only; namespace allow-
+ *     listing happens later in the sinks that need it)
+ *   - sets JSON mode on the logger if --format=json
+ *   - exposes an auth helper pre-curried with CLI --token / --token-env
+ *   - exposes a lazy manifest getter (show never reads the manifest)
+ *
+ * `buildContext` does NOT do source filtering — each command has subtly
+ * different CLI shape there (publish takes name-or-URL, install/show
+ * take URL arrays, pin-resolution only matters for install). That
+ * stays per-command until a second feature shows the same duplication.
+ *
+ * Errors: `buildContext` THROWS on all input-validation failures. Each
+ * command wraps the call in one try/catch that does `log.error + exit`.
+ * This keeps buildContext unit-testable; behaviour from the user's
+ * point of view is unchanged.
+ */
+
+const fs   = require('fs');
+const path = require('path');
+
+const { readConfig }        = require('./config');
+const { loadProfile }       = require('./profile');
+const { readManifest }      = require('./manifest');
+const { resolveSourceAuth } = require('./auth');
+const { parseCliOptions }   = require('./options');
+const { parseCliConf }      = require('./conf');
+const log                   = require('./logger');
+
+// ---------------------------------------------------------------------------
+// Internal helpers
+// ---------------------------------------------------------------------------
+
+/**
+ * Resolve the active profile name per the long-standing precedence:
+ *   --profile > config.defaultProfile > 'default'
+ */
+function resolveProfileName(argv, config) {
+  if (typeof argv.profile === 'string' && argv.profile.length > 0) {
+    return argv.profile;
+  }
+  if (typeof config.defaultProfile === 'string' && config.defaultProfile.length > 0) {
+    return config.defaultProfile;
+  }
+  return 'default';
+}
+
+/**
+ * Normalise CLI flags into the stable `ctx.flags` shape. Centralising
+ * defaults here means individual commands don't each re-apply
+ * `?? 'never'` / `?? 'Release'` / etc.
+ *
+ * Flags that are command-specific (argv.preset, argv.pkg, argv.clean,
+ * argv.verbose, argv.generator, argv.install, argv.installPrefix,
+ * argv.uploadSource, argv.autoInstall, argv.noGpgSign, ...) stay on
+ * argv and commands read them there. `ctx.argv` is the escape hatch.
+ */
+function normaliseFlags(argv) {
+  return {
+    format:      argv.format === 'json' ? 'json' : 'text',
+    dryRun:      argv.dryRun === true,
+    build:       argv.build ?? 'never',
+    uploadBuilt: argv.uploadBuilt === true,
+    force:       argv.force === true,
+    platform:    argv.platform ?? defaultPlatform(),
+    timeout:     typeof argv.timeout === 'number' ? argv.timeout : 300,
+  };
+}
+
+/**
+ * Default platform string when --platform is absent. Mirrors what
+ * bin/wyvrnpm.js passes when yargs applies its own default — keeping
+ * it here makes context.js testable without exercising the CLI layer.
+ */
+function defaultPlatform() {
+  if (process.platform === 'win32') {
+    return process.arch === 'ia32' ? 'win_x86' : 'win_x64';
+  }
+  if (process.platform === 'darwin') return 'macos';
+  return 'linux';
+}
+
+/**
+ * Produce a frozen `{ host, build }` profile pair. Today both point at
+ * the same resolved object — when F4 (build/host profile split) lands,
+ * only this function changes; every command reading `ctx.profiles.host`
+ * or `ctx.profiles.build` continues to work.
+ *
+ * The two sub-objects share a reference today. A regression test in
+ * tests/context.test.js asserts `ctx.profiles.host === ctx.profiles.build`
+ * — that test is expected to be removed (not fixed) when F4 makes them
+ * legitimately distinct.
+ */
+function resolveProfiles(argv, config) {
+  const name = resolveProfileName(argv, config);
+  const { profile, fromFile } = loadProfile(name);
+  const entry = Object.freeze({ name, profile, fromFile });
+  return Object.freeze({ host: entry, build: entry });
+}
+
+// ---------------------------------------------------------------------------
+// buildContext
+// ---------------------------------------------------------------------------
+
+/**
+ * Build the per-invocation CommandContext.
+ *
+ * @param {object} argv - yargs-parsed argument map. Fields read:
+ *   root, manifest, profile, format, dryRun, build, uploadBuilt,
+ *   force, platform, timeout, token, tokenEnv, option, conf.
+ *   Command-specific fields pass through on ctx.argv unchanged.
+ *
+ * @returns {CommandContext}
+ *
+ * @throws on:
+ *   - parseCliOptions: malformed `-o pkg:name=value`
+ *   - parseCliConf:    malformed `--conf KEY=VALUE`
+ *   - loadProfile:     malformed profile JSON, cycle in `extends`, etc.
+ *
+ * Does NOT throw on:
+ *   - missing manifest (lazy — throws at first ctx.manifest access)
+ *   - missing config   (readConfig returns empty defaults)
+ *   - missing profile  (loadProfile falls back to detectProfile())
+ *   - missing --token-env value (resolveSourceAuth throws at ctx.auth.for time)
+ */
+function buildContext(argv = {}) {
+  // 1. Filesystem anchors — pure path math, no I/O.
+  const rootDir = path.resolve(argv.root ?? '.');
+  const manifestPath = path.resolve(
+    argv.manifest ?? path.join(rootDir, 'wyvrn.json'),
+  );
+
+  // 2. Config — sync, small file, every command needs at least .defaultProfile.
+  const config = readConfig();
+
+  // 3. Profile (F4-ready shape).
+  const profiles = resolveProfiles(argv, config);
+
+  // 4. CLI auth, kept as the raw pair. Actual token lookup happens
+  //    through ctx.auth.for(sourceEntry), which runs resolveSourceAuth
+  //    each time so --token-env misses surface at use (same as today).
+  const authCli = Object.freeze({
+    token:    typeof argv.token    === 'string' ? argv.token    : undefined,
+    tokenEnv: typeof argv.tokenEnv === 'string' ? argv.tokenEnv : undefined,
+  });
+
+  // 5. CLI options + conf — format-level parsing only. Namespace
+  //    allow-listing for conf happens later in resolveEffectiveConf;
+  //    options validation against the recipe's declared `allowed` set
+  //    happens at resolveEffectiveOptions time.
+  //    Both can throw — that's the contract: buildContext surfaces
+  //    input-level errors up front.
+  const cliOptions = parseCliOptions(argv.option);
+  const cliConf    = parseCliConf(argv.conf);
+
+  // 6. Flags.
+  const flags = normaliseFlags(argv);
+
+  // 7. JSON mode — side effect that must happen before the command
+  //    starts logging. Flipping the logger here means every command
+  //    that constructs a ctx gets JSON mode right automatically.
+  if (flags.format === 'json') log.setJsonMode(true);
+
+  // 8. Assemble.
+  const ctx = {
+    rootDir,
+    manifestPath,
+    cwd: process.cwd(),
+    profiles,
+    config,
+    auth: Object.freeze({
+      cli: authCli,
+      for: (sourceEntry) => resolveSourceAuth(authCli, sourceEntry ?? null),
+    }),
+    cliOptions,
+    cliConf,
+    flags,
+    argv,
+  };
+
+  // 9. Lazy manifest getter. Most commands need it; `show` does not.
+  //    Defining as a getter means:
+  //      - show pays nothing.
+  //      - other commands pay once, cached.
+  //      - an invalid manifest surfaces at first use, not at ctx
+  //        construction — so `show` never trips over it.
+  let manifestCache = null;
+  let manifestLoaded = false;
+  Object.defineProperty(ctx, 'manifest', {
+    configurable: false,
+    enumerable:   true,
+    get() {
+      if (!manifestLoaded) {
+        if (!fs.existsSync(manifestPath)) {
+          throw new Error(`Manifest not found: ${manifestPath}`);
+        }
+        manifestCache = readManifest(manifestPath);
+        manifestLoaded = true;
+      }
+      return manifestCache;
+    },
+  });
+
+  return ctx;
+}
+
+module.exports = {
+  buildContext,
+  // Exported for unit tests — kept out of the default import surface.
+  _helpers: {
+    resolveProfileName,
+    normaliseFlags,
+    defaultPlatform,
+    resolveProfiles,
+  },
+};