@featherk/icons 0.16.0 → 0.16.1

package/README.md

@@ -17,7 +17,7 @@ const icon = getCustomIcon("search");
 
 - `CustomIcon`: union of supported icon identifier strings (see `packages/icons/src/custom-icon.ts`).
 - `GetCustomIconOptions`: `{ viewBox?: string; color?: string }` —
-	`viewBox` overrides the SVG viewBox; `color` replaces `currentColor` fills/strokes.
+  `viewBox` overrides the SVG viewBox; `color` replaces `currentColor` fills/strokes.
 
 Example — type an icon name:
 
@@ -45,17 +45,17 @@ Example — change viewBox and color:
   <SvgIcon :icon="successIcon" />
 </template>
 <script setup lang="ts">
-import { SvgIcon } from "@progress/kendo-vue-common";
-import { getCustomIcon } from "@featherk/icons";
+  import { SvgIcon } from "@progress/kendo-vue-common";
+  import { getCustomIcon } from "@featherk/icons";
 
-const helpIcon = getCustomIcon("help", {
-  viewBox: "0 0 28 28",
-  color: "var(--kendo-color-primary)",
-});
+  const helpIcon = getCustomIcon("help", {
+    viewBox: "0 0 28 28",
+    color: "var(--kendo-color-primary)",
+  });
 
-const successIcon = getCustomIcon("check", {
-  color: "var(--kendo-color-success)",
-});
+  const successIcon = getCustomIcon("check", {
+    color: "var(--kendo-color-success)",
+  });
 </script>
 ```
 

package/dist/docs-manifest.js

@@ -1,7 +1,7 @@
 // Generated by scripts/generate-docs-manifest.mjs. Do not edit.
 export const packageName = "@featherk/icons";
 
-export const version = "0.16.0";
+export const version = "0.16.1";
 
 export const paths = {
   CreateFontAwesomeManifest: "fontawesome/CreateFontAwesomeManifest.md",
@@ -12,11 +12,11 @@ export const paths = {
 };
 
 export const docs = {
-  CreateFontAwesomeManifest: "https://cdn.jsdelivr.net/npm/@featherk/icons@0.16.0/docs/fontawesome/CreateFontAwesomeManifest.md",
-  FontAwesome: "https://cdn.jsdelivr.net/npm/@featherk/icons@0.16.0/docs/fontawesome/FontAwesome.md",
-  FontAwesomeCLI: "https://cdn.jsdelivr.net/npm/@featherk/icons@0.16.0/docs/fontawesome/FontAwesomeCLI.md",
-  FontAwesomeDeveloperSetup: "https://cdn.jsdelivr.net/npm/@featherk/icons@0.16.0/docs/fontawesome/FontAwesomeDeveloperSetup.md",
-  LICENSING: "https://cdn.jsdelivr.net/npm/@featherk/icons@0.16.0/docs/fontawesome/LICENSING.md",
+  CreateFontAwesomeManifest: "https://cdn.jsdelivr.net/npm/@featherk/icons@0.16.1/docs/fontawesome/CreateFontAwesomeManifest.md",
+  FontAwesome: "https://cdn.jsdelivr.net/npm/@featherk/icons@0.16.1/docs/fontawesome/FontAwesome.md",
+  FontAwesomeCLI: "https://cdn.jsdelivr.net/npm/@featherk/icons@0.16.1/docs/fontawesome/FontAwesomeCLI.md",
+  FontAwesomeDeveloperSetup: "https://cdn.jsdelivr.net/npm/@featherk/icons@0.16.1/docs/fontawesome/FontAwesomeDeveloperSetup.md",
+  LICENSING: "https://cdn.jsdelivr.net/npm/@featherk/icons@0.16.1/docs/fontawesome/LICENSING.md",
 };
 
 export const docUrl = (name, host = "https://cdn.jsdelivr.net/npm") =>

package/dist/fontawesome/chunks/{manifest-CSRIDvaR.mjs → manifest-CF473fsM.mjs}

@@ -40,7 +40,12 @@ function fontAwesomeManifestKeys(manifest) {
 function selectFontAwesomeManifestKeys(manifest, root) {
   const keys = fontAwesomeManifestKeys(manifest);
   if (!isFontAwesomeIsolated(root)) {
-    return { keys, allowPro: true };
+    if (manifest.pro.length) {
+      throw new Error(
+        `Font Awesome manifest has Pro keys, but ${fontAwesomeProSourcesDir}/ was not found. Run "featherk-fontawesome-setup --manifest <manifest>" to create it.`
+      );
+    }
+    return { keys, allowPro: false };
   }
   if (!isFontAwesomeProInstalled(root)) {
     return { keys: manifest.free, allowPro: false };

package/dist/fontawesome/chunks/{manifest-Yjw62jxG.cjs → manifest-DEhGKvmi.cjs}

@@ -41,7 +41,12 @@ function fontAwesomeManifestKeys(manifest) {
 function selectFontAwesomeManifestKeys(manifest, root) {
   const keys = fontAwesomeManifestKeys(manifest);
   if (!isFontAwesomeIsolated(root)) {
-    return { keys, allowPro: true };
+    if (manifest.pro.length) {
+      throw new Error(
+        `Font Awesome manifest has Pro keys, but ${fontAwesomeProSourcesDir}/ was not found. Run "featherk-fontawesome-setup --manifest <manifest>" to create it.`
+      );
+    }
+    return { keys, allowPro: false };
   }
   if (!isFontAwesomeProInstalled(root)) {
     return { keys: manifest.free, allowPro: false };

package/dist/fontawesome/cli.cjs

@@ -3,14 +3,14 @@ Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
 const node_path = require("node:path");
 const node_util = require("node:util");
 const generate = require("./chunks/generate-B_FxftR7.cjs");
-const manifest = require("./chunks/manifest-Yjw62jxG.cjs");
+const manifest = require("./chunks/manifest-DEhGKvmi.cjs");
 const usage = `Usage: featherk-fontawesome --manifest <icons.json> [--root <project>] [--out <icons.mjs>] [--virtual-types <types.d.ts>]
 
 The JSON manifest contains { "free": [keys], "pro": [keys] }, the same file
 used by featherk-fontawesome-setup and the Vite plugin.
-When the project has a ${manifest.fontAwesomeProSourcesDir}/ source project (the
-default setup), Pro keys are generated from it only when it is installed.
-Otherwise all keys are generated from the project's own installed sources.
+Free keys are generated from the project's own installed packages. Pro keys
+are generated from the ${manifest.fontAwesomeProSourcesDir}/ source project, only when
+it is installed.
 Provide --out, --virtual-types, or both. Paths are relative to the project root.
 This command does not download assets or authenticate; install licensed packages first.
 Generated assets belong to the consuming project, never the @featherk/icons package.`;

package/dist/fontawesome/cli.mjs

@@ -1,14 +1,14 @@
 import { resolve } from "node:path";
 import { parseArgs } from "node:util";
 import { g as generateFaIcons, s as summarizeFaIcons } from "./chunks/generate-DF9R65sV.mjs";
-import { f as fontAwesomeProSourcesDir, r as readFontAwesomeManifest, s as selectFontAwesomeManifestKeys } from "./chunks/manifest-CSRIDvaR.mjs";
+import { f as fontAwesomeProSourcesDir, r as readFontAwesomeManifest, s as selectFontAwesomeManifestKeys } from "./chunks/manifest-CF473fsM.mjs";
 const usage = `Usage: featherk-fontawesome --manifest <icons.json> [--root <project>] [--out <icons.mjs>] [--virtual-types <types.d.ts>]
 
 The JSON manifest contains { "free": [keys], "pro": [keys] }, the same file
 used by featherk-fontawesome-setup and the Vite plugin.
-When the project has a ${fontAwesomeProSourcesDir}/ source project (the
-default setup), Pro keys are generated from it only when it is installed.
-Otherwise all keys are generated from the project's own installed sources.
+Free keys are generated from the project's own installed packages. Pro keys
+are generated from the ${fontAwesomeProSourcesDir}/ source project, only when
+it is installed.
 Provide --out, --virtual-types, or both. Paths are relative to the project root.
 This command does not download assets or authenticate; install licensed packages first.
 Generated assets belong to the consuming project, never the @featherk/icons package.`;

package/dist/fontawesome/manifest.d.ts

@@ -39,12 +39,11 @@ export declare function fontAwesomeManifestKeys(manifest: FontAwesomeKeysManifes
 /**
  * Selects the manifest keys for one build of the application at `root`.
  *
- * In the isolated layout, the `pro` keys are selected, and resolved from
- * `fontawesome-pro-sources`, only when that project is installed; otherwise
- * the build is Free-only and never reads it. Without the isolated project,
- * the application installed its own sources, so every key is selected; a
- * Free-only manifest has no `pro` keys.
+ * The `free` keys are always selected. The `pro` keys are selected, and
+ * resolved from `fontawesome-pro-sources`, only when that project is
+ * installed; otherwise the build is Free-only and never reads it.
  *
- * @throws If a Pro-tier key is listed under `free`.
+ * @throws If a Pro-tier key is listed under `free`, or the manifest has `pro`
+ * keys but the application has no `fontawesome-pro-sources` project.
  */
 export declare function selectFontAwesomeManifestKeys(manifest: FontAwesomeKeysManifest, root: string): FontAwesomeManifestSelection;

package/dist/fontawesome/setup.cjs

@@ -6,7 +6,7 @@ const node_path = require("node:path");
 const node_readline = require("node:readline");
 const node_util = require("node:util");
 const fontawesome_catalog = require("./catalog.cjs");
-const manifest = require("./chunks/manifest-Yjw62jxG.cjs");
+const manifest = require("./chunks/manifest-DEhGKvmi.cjs");
 const tokenVariable = "FONTAWESOME_PACKAGE_TOKEN";
 const tokenPlaceholder = `\${${tokenVariable}}`;
 const registry = "https://npm.fontawesome.com/";
@@ -25,7 +25,7 @@ const workspaceVariables = [
   "NPM_CONFIG_WORKSPACES"
 ];
 const usage = `Usage:
-  featherk-fontawesome-setup --manifest <icons.json> [--free-only | --pro-in-app]
+  featherk-fontawesome-setup --manifest <icons.json> [--free-only]
   featherk-fontawesome-setup
 
 Run from the application root. The manifest contains
@@ -44,12 +44,6 @@ lockfile with the token, for CI and fresh clones. Run it after the app's own
 
 --free-only: Free keys only from public npm. No token, no source project.
 
---pro-in-app: installs Free and Pro pins into the app's own devDependencies
-and routes @fortawesome to the Pro registry in the app's .npmrc (token
-placeholder only). Every install of the app, including CI, then needs the
-token for "npm ci --ignore-scripts". Use only when the isolated project is not
-an option.
-
 The token comes from ${tokenVariable} or a hidden prompt in an interactive
 terminal. --manifest setup changes package.json and is refused in CI
 (CI, TEAMCITY_VERSION, or GITHUB_ACTIONS is set). Do not export the token
@@ -193,11 +187,10 @@ function checkNpmrc(config, file) {
   }
   return { fontAwesomeRegistry, hasAuth };
 }
-function installIntoApp(pins, pro, token, context) {
+function installFreeIntoApp(pins, context) {
   const npmCli = requireNpm(context);
   const environment = { ...context.env };
   delete environment[tokenVariable];
-  if (pro && token) environment[tokenVariable] = token;
   const specs = [...pins].map(([name, pin]) => `${name}@${pin.spec}`);
   const status = context.runNpm({
     npmCli,
@@ -208,7 +201,6 @@ function installIntoApp(pins, pro, token, context) {
       "--ignore-scripts",
       "--no-audit",
       "--no-fund",
-      ...pro ? [pinRegistry] : [],
       ...specs
     ],
     cwd: context.cwd,
@@ -311,15 +303,14 @@ async function installSourceProject(sourceRoot, token, context) {
   context.log(
     locked ? `Pro sources installed from ${lockfile}.` : `Pro sources installed. Review and commit ${lockfile}.`
   );
+  context.log(
+    "Restart any running Vite dev server so it includes the installed Pro icons."
+  );
   return 0;
 }
 async function setupFromManifest(values, context) {
   const { log } = context;
   const freeOnly = Boolean(values["free-only"]);
-  const proInApp = Boolean(values["pro-in-app"]);
-  if (freeOnly && proInApp) {
-    throw new Error("Use either --free-only or --pro-in-app, not both.");
-  }
   if (context.isCi) {
     throw new Error(
       `--manifest setup changes package.json and is a local step. In CI, run the app's own "npm ci", then featherk-fontawesome-setup without arguments to install ${manifest.fontAwesomeProSourcesDir}/.`
@@ -344,17 +335,12 @@ async function setupFromManifest(values, context) {
   }
   const npmrcPath = node_path.resolve(appRoot, ".npmrc");
   const config = node_fs.existsSync(npmrcPath) ? node_fs.readFileSync(npmrcPath, "utf8") : "";
-  const { fontAwesomeRegistry, hasAuth } = checkNpmrc(config, ".npmrc");
+  const { fontAwesomeRegistry } = checkNpmrc(config, ".npmrc");
   const sourceRoot = node_path.resolve(appRoot, manifest.fontAwesomeProSourcesDir);
   const isolated = manifest.isFontAwesomeIsolated(appRoot);
-  if (proInApp && isolated) {
-    throw new Error(
-      `${manifest.fontAwesomeProSourcesDir}/ exists, so this app keeps Pro in the isolated source project. Run without --pro-in-app, or remove ${manifest.fontAwesomeProSourcesDir}/ first.`
-    );
-  }
-  if (!proInApp && fontAwesomeRegistry) {
+  if (fontAwesomeRegistry) {
     throw new Error(
-      `.npmrc routes @fortawesome to ${fontAwesomeRegistry}, so this app installs Pro in the app itself. Rerun with --pro-in-app.`
+      `.npmrc routes @fortawesome to ${fontAwesomeRegistry}, which installs Pro packages in the app itself; that layout is not supported. Remove the Font Awesome lines from .npmrc and any @fortawesome/pro-* packages from the app's devDependencies, then rerun.`
     );
   }
   if (freeOnly && isolated) {
@@ -362,34 +348,8 @@ async function setupFromManifest(values, context) {
       `${manifest.fontAwesomeProSourcesDir}/ exists, so this app uses Pro. Run without --free-only, or remove ${manifest.fontAwesomeProSourcesDir}/ first.`
     );
   }
-  if (proInApp) {
-    const token = proPins.size ? await readToken(context) : void 0;
-    if (proPins.size) {
-      const missing = [];
-      if (!fontAwesomeRegistry) missing.push(npmrcLines[0], npmrcLines[1]);
-      if (!hasAuth) missing.push(npmrcLines[2], npmrcLines[3]);
-      if (missing.length) {
-        const separator = config && !config.endsWith("\n") ? "\n" : "";
-        node_fs.writeFileSync(
-          npmrcPath,
-          `${config}${separator}${missing.join("\n")}
-`
-        );
-        log(
-          `${config ? "Updated" : "Created"} .npmrc with the Font Awesome registry and token placeholder.`
-        );
-      }
-    }
-    const status2 = installIntoApp(pins, proPins.size > 0, token, context);
-    if (status2 !== 0) return status2;
-    log(lifecycleNote);
-    log(
-      `Next: commit .npmrc, package.json, and package-lock.json. Configure the Vite plugin with { manifest }. Every later install, including CI, gives ${tokenVariable} only to "npm ci --ignore-scripts"; run needed install scripts and builds without it.`
-    );
-    return 0;
-  }
   if (freePins.size) {
-    const status2 = installIntoApp(freePins, false, void 0, context);
+    const status2 = installFreeIntoApp(freePins, context);
     if (status2 !== 0) return status2;
     log(lifecycleNote);
   }
@@ -433,20 +393,23 @@ async function runFontAwesomeSetup(args, io = {}) {
     promptForToken: io.promptForToken ?? promptForTerminalToken,
     runNpm: io.runNpm ?? spawnNpm
   };
+  const hasFlag = (flag) => args.some((arg) => arg === flag || arg.startsWith(`${flag}=`));
   try {
-    const removed = removedFlags.find(
-      (flag) => args.some((arg) => arg === flag || arg.startsWith(`${flag}=`))
-    );
+    const removed = removedFlags.find(hasFlag);
     if (removed) {
       throw new Error(
         `${removed} was removed in 0.16.0. Run setup with --manifest; Pro sources always live in ${manifest.fontAwesomeProSourcesDir}/, and rerunning with --manifest updates them. Use --help for usage.`
       );
     }
+    if (hasFlag("--pro-in-app")) {
+      throw new Error(
+        `--pro-in-app was removed. Pro packages always install into ${manifest.fontAwesomeProSourcesDir}/, so the app's own install never needs the token. Run setup with --manifest.`
+      );
+    }
     const { values } = node_util.parseArgs({
       args: [...args],
       options: {
         "free-only": { type: "boolean" },
-        "pro-in-app": { type: "boolean" },
         manifest: { type: "string" },
         help: { type: "boolean", short: "h" }
       },
@@ -460,8 +423,8 @@ async function runFontAwesomeSetup(args, io = {}) {
     if (values.manifest !== void 0) {
       return await setupFromManifest(values, context);
     }
-    if (values["free-only"] || values["pro-in-app"]) {
-      throw new Error("--free-only and --pro-in-app require --manifest.");
+    if (values["free-only"]) {
+      throw new Error("--free-only requires --manifest.");
     }
     if (!manifest.isFontAwesomeIsolated(cwd)) {
       throw new Error(

package/dist/fontawesome/setup.mjs

@@ -1,10 +1,10 @@
 import { spawnSync } from "node:child_process";
-import { existsSync, readFileSync, writeFileSync, mkdirSync, rmSync } from "node:fs";
+import { existsSync, readFileSync, mkdirSync, writeFileSync, rmSync } from "node:fs";
 import { resolve } from "node:path";
 import { emitKeypressEvents } from "node:readline";
 import { parseArgs } from "node:util";
 import { fontAwesomeCatalog, resolveFontAwesomeKeys } from "./catalog.mjs";
-import { f as fontAwesomeProSourcesDir, i as isFontAwesomeIsolated, r as readFontAwesomeManifest, a as fontAwesomeManifestKeys } from "./chunks/manifest-CSRIDvaR.mjs";
+import { f as fontAwesomeProSourcesDir, i as isFontAwesomeIsolated, r as readFontAwesomeManifest, a as fontAwesomeManifestKeys } from "./chunks/manifest-CF473fsM.mjs";
 const tokenVariable = "FONTAWESOME_PACKAGE_TOKEN";
 const tokenPlaceholder = `\${${tokenVariable}}`;
 const registry = "https://npm.fontawesome.com/";
@@ -23,7 +23,7 @@ const workspaceVariables = [
   "NPM_CONFIG_WORKSPACES"
 ];
 const usage = `Usage:
-  featherk-fontawesome-setup --manifest <icons.json> [--free-only | --pro-in-app]
+  featherk-fontawesome-setup --manifest <icons.json> [--free-only]
   featherk-fontawesome-setup
 
 Run from the application root. The manifest contains
@@ -42,12 +42,6 @@ lockfile with the token, for CI and fresh clones. Run it after the app's own
 
 --free-only: Free keys only from public npm. No token, no source project.
 
---pro-in-app: installs Free and Pro pins into the app's own devDependencies
-and routes @fortawesome to the Pro registry in the app's .npmrc (token
-placeholder only). Every install of the app, including CI, then needs the
-token for "npm ci --ignore-scripts". Use only when the isolated project is not
-an option.
-
 The token comes from ${tokenVariable} or a hidden prompt in an interactive
 terminal. --manifest setup changes package.json and is refused in CI
 (CI, TEAMCITY_VERSION, or GITHUB_ACTIONS is set). Do not export the token
@@ -191,11 +185,10 @@ function checkNpmrc(config, file) {
   }
   return { fontAwesomeRegistry, hasAuth };
 }
-function installIntoApp(pins, pro, token, context) {
+function installFreeIntoApp(pins, context) {
   const npmCli = requireNpm(context);
   const environment = { ...context.env };
   delete environment[tokenVariable];
-  if (pro && token) environment[tokenVariable] = token;
   const specs = [...pins].map(([name, pin]) => `${name}@${pin.spec}`);
   const status = context.runNpm({
     npmCli,
@@ -206,7 +199,6 @@ function installIntoApp(pins, pro, token, context) {
       "--ignore-scripts",
       "--no-audit",
       "--no-fund",
-      ...pro ? [pinRegistry] : [],
       ...specs
     ],
     cwd: context.cwd,
@@ -309,15 +301,14 @@ async function installSourceProject(sourceRoot, token, context) {
   context.log(
     locked ? `Pro sources installed from ${lockfile}.` : `Pro sources installed. Review and commit ${lockfile}.`
   );
+  context.log(
+    "Restart any running Vite dev server so it includes the installed Pro icons."
+  );
   return 0;
 }
 async function setupFromManifest(values, context) {
   const { log } = context;
   const freeOnly = Boolean(values["free-only"]);
-  const proInApp = Boolean(values["pro-in-app"]);
-  if (freeOnly && proInApp) {
-    throw new Error("Use either --free-only or --pro-in-app, not both.");
-  }
   if (context.isCi) {
     throw new Error(
       `--manifest setup changes package.json and is a local step. In CI, run the app's own "npm ci", then featherk-fontawesome-setup without arguments to install ${fontAwesomeProSourcesDir}/.`
@@ -342,17 +333,12 @@ async function setupFromManifest(values, context) {
   }
   const npmrcPath = resolve(appRoot, ".npmrc");
   const config = existsSync(npmrcPath) ? readFileSync(npmrcPath, "utf8") : "";
-  const { fontAwesomeRegistry, hasAuth } = checkNpmrc(config, ".npmrc");
+  const { fontAwesomeRegistry } = checkNpmrc(config, ".npmrc");
   const sourceRoot = resolve(appRoot, fontAwesomeProSourcesDir);
   const isolated = isFontAwesomeIsolated(appRoot);
-  if (proInApp && isolated) {
-    throw new Error(
-      `${fontAwesomeProSourcesDir}/ exists, so this app keeps Pro in the isolated source project. Run without --pro-in-app, or remove ${fontAwesomeProSourcesDir}/ first.`
-    );
-  }
-  if (!proInApp && fontAwesomeRegistry) {
+  if (fontAwesomeRegistry) {
     throw new Error(
-      `.npmrc routes @fortawesome to ${fontAwesomeRegistry}, so this app installs Pro in the app itself. Rerun with --pro-in-app.`
+      `.npmrc routes @fortawesome to ${fontAwesomeRegistry}, which installs Pro packages in the app itself; that layout is not supported. Remove the Font Awesome lines from .npmrc and any @fortawesome/pro-* packages from the app's devDependencies, then rerun.`
     );
   }
   if (freeOnly && isolated) {
@@ -360,34 +346,8 @@ async function setupFromManifest(values, context) {
       `${fontAwesomeProSourcesDir}/ exists, so this app uses Pro. Run without --free-only, or remove ${fontAwesomeProSourcesDir}/ first.`
     );
   }
-  if (proInApp) {
-    const token = proPins.size ? await readToken(context) : void 0;
-    if (proPins.size) {
-      const missing = [];
-      if (!fontAwesomeRegistry) missing.push(npmrcLines[0], npmrcLines[1]);
-      if (!hasAuth) missing.push(npmrcLines[2], npmrcLines[3]);
-      if (missing.length) {
-        const separator = config && !config.endsWith("\n") ? "\n" : "";
-        writeFileSync(
-          npmrcPath,
-          `${config}${separator}${missing.join("\n")}
-`
-        );
-        log(
-          `${config ? "Updated" : "Created"} .npmrc with the Font Awesome registry and token placeholder.`
-        );
-      }
-    }
-    const status2 = installIntoApp(pins, proPins.size > 0, token, context);
-    if (status2 !== 0) return status2;
-    log(lifecycleNote);
-    log(
-      `Next: commit .npmrc, package.json, and package-lock.json. Configure the Vite plugin with { manifest }. Every later install, including CI, gives ${tokenVariable} only to "npm ci --ignore-scripts"; run needed install scripts and builds without it.`
-    );
-    return 0;
-  }
   if (freePins.size) {
-    const status2 = installIntoApp(freePins, false, void 0, context);
+    const status2 = installFreeIntoApp(freePins, context);
     if (status2 !== 0) return status2;
     log(lifecycleNote);
   }
@@ -431,20 +391,23 @@ async function runFontAwesomeSetup(args, io = {}) {
     promptForToken: io.promptForToken ?? promptForTerminalToken,
     runNpm: io.runNpm ?? spawnNpm
   };
+  const hasFlag = (flag) => args.some((arg) => arg === flag || arg.startsWith(`${flag}=`));
   try {
-    const removed = removedFlags.find(
-      (flag) => args.some((arg) => arg === flag || arg.startsWith(`${flag}=`))
-    );
+    const removed = removedFlags.find(hasFlag);
     if (removed) {
       throw new Error(
         `${removed} was removed in 0.16.0. Run setup with --manifest; Pro sources always live in ${fontAwesomeProSourcesDir}/, and rerunning with --manifest updates them. Use --help for usage.`
       );
     }
+    if (hasFlag("--pro-in-app")) {
+      throw new Error(
+        `--pro-in-app was removed. Pro packages always install into ${fontAwesomeProSourcesDir}/, so the app's own install never needs the token. Run setup with --manifest.`
+      );
+    }
     const { values } = parseArgs({
       args: [...args],
       options: {
         "free-only": { type: "boolean" },
-        "pro-in-app": { type: "boolean" },
         manifest: { type: "string" },
         help: { type: "boolean", short: "h" }
       },
@@ -458,8 +421,8 @@ async function runFontAwesomeSetup(args, io = {}) {
     if (values.manifest !== void 0) {
       return await setupFromManifest(values, context);
     }
-    if (values["free-only"] || values["pro-in-app"]) {
-      throw new Error("--free-only and --pro-in-app require --manifest.");
+    if (values["free-only"]) {
+      throw new Error("--free-only requires --manifest.");
     }
     if (!isFontAwesomeIsolated(cwd)) {
       throw new Error(

package/dist/fontawesome/vite.cjs

@@ -3,7 +3,7 @@ Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
 const node_path = require("node:path");
 const promises = require("node:fs/promises");
 const generate = require("./chunks/generate-B_FxftR7.cjs");
-const manifest = require("./chunks/manifest-Yjw62jxG.cjs");
+const manifest = require("./chunks/manifest-DEhGKvmi.cjs");
 const virtualId = "virtual:featherk/fontawesome";
 const resolvedId = `\0${virtualId}`;
 function dependencyKey(file) {

package/dist/fontawesome/vite.d.ts

@@ -4,10 +4,9 @@ import type { Plugin } from "vite";
  * from the same keys-only `{ free, pro }` manifest used by
  * `featherk-fontawesome-setup`.
  *
- * When the project has a `fontawesome-pro-sources/` source project (the
- * default setup), the manifest's `pro` keys are generated from it only in
- * builds where that project is installed. Otherwise every key comes from the
- * project's own installed packages.
+ * The `free` keys come from the project's own installed packages. The `pro`
+ * keys are generated from the `fontawesome-pro-sources/` source project, only
+ * in builds where that project is installed.
  */
 export interface FontAwesomeViteOptions {
     /** Keys-only manifest path, relative to the project root. */

package/dist/fontawesome/vite.mjs

@@ -1,7 +1,7 @@
 import { resolve, relative } from "node:path";
 import { realpath } from "node:fs/promises";
 import { g as generateFaIcons, s as summarizeFaIcons } from "./chunks/generate-DF9R65sV.mjs";
-import { f as fontAwesomeProSourcesDir, r as readFontAwesomeManifest, s as selectFontAwesomeManifestKeys } from "./chunks/manifest-CSRIDvaR.mjs";
+import { f as fontAwesomeProSourcesDir, r as readFontAwesomeManifest, s as selectFontAwesomeManifestKeys } from "./chunks/manifest-CF473fsM.mjs";
 const virtualId = "virtual:featherk/fontawesome";
 const resolvedId = `\0${virtualId}`;
 function dependencyKey(file) {

package/docs/ADDING-ICONS.md

@@ -10,8 +10,8 @@ iconography repository provides validation tools for its source assets.
 
 Keep the category directory and filename when copying an icon:
 
-| Source in `iconography` | Destination in this repository |
-| --- | --- |
+| Source in `iconography`            | Destination in this repository               |
+| ---------------------------------- | -------------------------------------------- |
 | `src/icons/<category>/ic_Name.svg` | `packages/icons/icon/<category>/ic_Name.svg` |
 
 For example, copy `src/icons/action/ic_Edit.svg` to
@@ -35,6 +35,7 @@ entire iconography repository.
    missing IDs, and duplicate filenames. The full check also enforces the 5 KB
    file-size limit. After changing the source inventory, refresh it with
    `npm run document:icons`.
+
 3. Copy the selected SVG files unchanged into the matching category directories
    under `packages/icons/icon/`. Create the destination category directory if
    needed. Do not copy generated package output in place of the SVG source
@@ -55,4 +56,4 @@ entire iconography repository.
 The package generator derives each public icon name from its filename by
 removing the `ic_` prefix and `.svg` extension, then lowercasing the remainder.
 For example, `ic_User_Profile.svg` becomes `user_profile`. Keep filenames
-unique across categories; the iconography validator checks this requirement.
+unique across categories; the iconography validator checks this requirement.

package/docs/COMING-SOON.md

@@ -6,12 +6,13 @@ notice. They were moved out of the main README to keep the public surface area
 stable while we iterate on behaviour and naming.
 
 Quick summary:
+
 - `getIconCssUrl` / `getIconCssUrlBase64` — convenience helpers that return a
-	wrapped `url("...")` string suitable for assigning directly to CSS
-	`background-image` (UTF‑8 and base64 variants respectively).
+  wrapped `url("...")` string suitable for assigning directly to CSS
+  `background-image` (UTF‑8 and base64 variants respectively).
 - `getIconDataUrlBase64` — base64-encoded data URL variant of `getIconDataUrl`.
 - Usage examples and small CSS snippets that simplify embedding icons as
-	backgrounds or masks in styles.
+  backgrounds or masks in styles.
 
 Please treat these helpers as unstable. If you rely on them, expect possible
 breaking changes in future releases and prefer the lower-level `getIconDataUrl`
@@ -30,20 +31,23 @@ import { getCustomIcon, getIconDataUrl } from "@featherk/icons";
 const search = getCustomIcon("search");
 const searchIconUrl = getIconDataUrl(search);
 // Provide it to CSS via a custom property (example only)
-document.documentElement.style.setProperty("--search-icon", `url("${searchIconUrl}")`);
+document.documentElement.style.setProperty(
+  "--search-icon",
+  `url("${searchIconUrl}")`,
+);
 ```
 
 ```css
 .button::after {
- content: "";
- display: inline-block;
- width: 1em;
- height: 1em;
- background: no-repeat center/contain var(--search-icon);
- /* Alternatively, to tint using current text color:
+  content: "";
+  display: inline-block;
+  width: 1em;
+  height: 1em;
+  background: no-repeat center/contain var(--search-icon);
+  /* Alternatively, to tint using current text color:
 	 mask: var(--search-icon) no-repeat center / contain;
 	 background-color: currentColor; */
- margin-left: 0.25rem;
+  margin-left: 0.25rem;
 }
 ```
 
@@ -53,7 +57,11 @@ If you prefer a ready-to-use CSS value, use `getIconCssUrl` (UTF‑8) or
 `getIconCssUrlBase64` (base64). Both return a wrapped `url("...")` string.
 
 ```ts
-import { getCustomIcon, getIconCssUrl, getIconCssUrlBase64 } from "@featherk/icons";
+import {
+  getCustomIcon,
+  getIconCssUrl,
+  getIconCssUrlBase64,
+} from "@featherk/icons";
 
 const arrowLeft = getCustomIcon("arrow_left");
 const arrowLeftBg = getIconCssUrl(arrowLeft);
@@ -74,6 +82,8 @@ import { getCustomIcon, getIconDataUrlBase64 } from "@featherk/icons";
 const search = getCustomIcon("search");
 const searchIconUrlBase64 = getIconDataUrlBase64(search);
 // Example: set as CSS background
-document.documentElement.style.setProperty("--search-icon", `url("${searchIconUrlBase64}")`);
+document.documentElement.style.setProperty(
+  "--search-icon",
+  `url("${searchIconUrlBase64}")`,
+);
 ```
-

package/docs/ICONS.md

@@ -211,4 +211,4 @@
 |rating_star_selected|switch_left|switch_off|switch_on|switch_right| |
 <!-- markdownlint-enable MD033-->
 
-> Generated: 2026-10-15T21:01:16.022Z
+> Generated: 2026-10-16T17:15:34.562Z

package/docs/fontawesome/CreateFontAwesomeManifest.md

@@ -13,17 +13,17 @@ The steps below help UX/Design create a precise handoff. Do not assume every ico
 
 ## Where Each Field Comes From
 
-| Catalog field | Who supplies it                         | Meaning                                                                                                             |
-| ------------- | --------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
-| `key`         | UX/Design Engineer                     | Stable, globally unique lookup key for exactly one catalog variant; supplied to Vite/CLI by the consumer            |
-| `name`        | Font Awesome catalog                    | Canonical icon name, such as `house`, without the `fa-` CSS prefix                                                  |
-| `version`     | UX and release approval                 | Exact source-package release, such as `7.0.0`, not `latest`, a range, or the first version that introduced the icon |
-| `family`      | UX/design selection                     | Supported family identifier, such as `classic` or `sharp`                                                           |
-| `style`       | UX/design selection                     | Supported style identifier, such as `solid`, `regular`, or `light`                                                  |
-| `package`     | UX/Design Engineer                      | Exact installed dependency name; may be an npm alias such as `fa-solid-v5`                                          |
-| `registryPackage` | UX/Design Engineer                  | Canonical npm package name targeted by `package` and checked against installed package metadata                    |
-| `exportName`  | UX/Design Engineer                      | Exact individual icon export in the source package                                                                 |
-| `tier`        | UX/Design Engineer                      | `free` or `pro` classification for the exact variant; descriptive only, not proof of entitlement                   |
+| Catalog field     | Who supplies it         | Meaning                                                                                                             |
+| ----------------- | ----------------------- | ------------------------------------------------------------------------------------------------------------------- |
+| `key`             | UX/Design Engineer      | Stable, globally unique lookup key for exactly one catalog variant; supplied to Vite/CLI by the consumer            |
+| `name`            | Font Awesome catalog    | Canonical icon name, such as `house`, without the `fa-` CSS prefix                                                  |
+| `version`         | UX and release approval | Exact source-package release, such as `7.0.0`, not `latest`, a range, or the first version that introduced the icon |
+| `family`          | UX/design selection     | Supported family identifier, such as `classic` or `sharp`                                                           |
+| `style`           | UX/design selection     | Supported style identifier, such as `solid`, `regular`, or `light`                                                  |
+| `package`         | UX/Design Engineer      | Exact installed dependency name; may be an npm alias such as `fa-solid-v5`                                          |
+| `registryPackage` | UX/Design Engineer      | Canonical npm package name targeted by `package` and checked against installed package metadata                     |
+| `exportName`      | UX/Design Engineer      | Exact individual icon export in the source package                                                                  |
+| `tier`            | UX/Design Engineer      | `free` or `pro` classification for the exact variant; descriptive only, not proof of entitlement                    |
 
 Each catalog key identifies one exact name/version/family/style/package/export variant. Different styles or releases require different keys. Catalog records are maintained and published by FeatherK; consuming applications do not copy these fields into their selection manifest. `tier` describes the Font Awesome product tier only; it does not grant access or establish license coverage. Package availability and Pro entitlement must still be confirmed independently.
 

package/docs/fontawesome/FontAwesome.md

@@ -30,7 +30,7 @@ One keys-only manifest drives everything: the setup command installs exactly wha
    featherkFontAwesome({ manifest: "fontawesome.keys.json" });
    ```
 
-4. **Build** with the application's normal `dev` and `build` scripts. Wherever `fontawesome-pro-sources/` is installed (step 2 locally, or the token-scoped install step in CI), builds include the Pro icons. Where it isn't installed, builds include only the Free icons.
+4. **Build** with the application's normal `dev` and `build` scripts. Wherever `fontawesome-pro-sources/` is installed (step 2 locally, or the `npx featherk-fontawesome-setup` step in CI), builds include the Pro icons. Where it isn't installed, builds include only the Free icons.
 5. **Render icons** from the virtual module; see the [rendering example](#render-the-selected-key).
 6. **Preserve license notices** in application distribution; see [Preserve license notices](#preserve-license-notices).
 
@@ -49,7 +49,7 @@ The repository's Pro demo selects Classic Light `house` from Font Awesome Pro 7
 
 This follows the demo's Vite virtual-module flow. The Pro page filters generated provenance for `pro-` keys and passes the choices to its shared renderer; an application can also render this selected icon directly:
 
-```vue
+```html
 <template>
   <SvgIcon :icon="houseIcon" />
 </template>
@@ -94,7 +94,7 @@ npm install --save-dev @featherk/icons vite@^7.0.0
 
 ## Install Source Packages
 
-Run `featherk-fontawesome-setup --manifest fontawesome.keys.json` from the application root (Quick Start step 2). The catalog maps each key to its local dependency name, canonical registry package, export, and exact version, and the command installs only the packages the manifest needs, pinned to those versions, including npm aliases where one release must sit beside another (see [alias details](#about-aliases-and-why-use-them)). Free packages go into the application's `devDependencies`. Pro packages go into `fontawesome-pro-sources/`, whose `.npmrc` holds only a token placeholder, and the token is passed only to npm. On a fresh clone or in CI, run `npx featherk-fontawesome-setup` without arguments after the application's `npm ci` to install that project from its lockfile. See [Pro licensing and setup](LICENSING.md#consuming-applications) for the token, CI, TeamCity, and the `--pro-in-app` exception. Never put a Pro token in a command or commit it.
+Run `featherk-fontawesome-setup --manifest fontawesome.keys.json` from the application root (Quick Start step 2). The catalog maps each key to its local dependency name, canonical registry package, export, and exact version, and the command installs only the packages the manifest needs, pinned to those versions, including npm aliases where one release must sit beside another (see [alias details](#about-aliases-and-why-use-them)). Free packages go into the application's `devDependencies`. Pro packages go into `fontawesome-pro-sources/`, whose `.npmrc` holds only a token placeholder, and the token is passed only to npm. On a fresh clone or in CI, run `npx featherk-fontawesome-setup` without arguments after the application's `npm ci` to install that project from its lockfile. See [Pro licensing and setup](LICENSING.md#consuming-applications) for the token, CI, TeamCity, and the `--free-only` exception. Never put a Pro token in a command or commit it.
 
 During generation, the installed package's declared name is checked against `registryPackage` and its version against the catalog before the icon module is loaded. When a package is missing, generation fails with a message that points to the setup command; nobody installs Font Awesome packages by hand. At the end of each build, Vite logs the source packages the icons came from, for information only. The setup command is not a license or access check.
 
@@ -112,15 +112,15 @@ export default defineConfig({
 });
 ```
 
-The plugin reads the manifest relative to the Vite project root and validates every key through the catalog. It always generates the `free` keys. When the project has `fontawesome-pro-sources/`, it adds the `pro` keys, resolved from that project, only when that project is installed (its `node_modules` exists); otherwise it never reads it. A build where the install was skipped is Free-only, and code that uses a Pro key then fails type checking, because the generated key union contains only Free keys. An application set up with `--pro-in-app` has no such directory, so every build includes its `pro` keys from the application's own packages. A Pro-tier key listed under `free` is rejected with a message to move it to `pro`. Selecting keys this way is not license authorization. The plugin watches the manifest and reloads the dev server when it changes. The catalog supplies exact metadata, and the generator validates installed source versions and identities at runtime.
+The plugin reads the manifest relative to the Vite project root and validates every key through the catalog. It always generates the `free` keys. When the project has `fontawesome-pro-sources/`, it adds the `pro` keys, resolved from that project, only when that project is installed (its `node_modules` exists); otherwise it never reads it. A build where the install was skipped is Free-only, and code that uses a Pro key then fails type checking, because the generated key union contains only Free keys. A manifest with `pro` keys in a project without `fontawesome-pro-sources/` fails with a message to run the setup command. A Pro-tier key listed under `free` is rejected with a message to move it to `pro`. Selecting keys this way is not license authorization. The plugin watches the manifest and reloads the dev server when it changes. The catalog supplies exact metadata, and the generator validates installed source versions and identities at runtime.
 
 ### Upgrading from 0.15
 
-0.16.0 removed the plugin's `keys`, `allowPro`, and `sourceRoot` options; the setup command's `--keys`, `--source-root`, `--init`, `--force`, and `--refresh-lock`; and the CLI's `--allow-pro` and `--source-root`. Passing them fails with a message that explains the replacement. Move the keys into the manifest, pass `{ manifest }`, and rerun `featherk-fontawesome-setup --manifest fontawesome.keys.json`, which moves Pro packages into `fontawesome-pro-sources/`. An application that installed Pro into its own dependencies keeps that layout with `--pro-in-app`.
+0.16.0 removed the plugin's `keys`, `allowPro`, and `sourceRoot` options; the setup command's `--keys`, `--source-root`, `--init`, `--force`, and `--refresh-lock`; and the CLI's `--allow-pro` and `--source-root`. Passing them fails with a message that explains the replacement. Move the keys into the manifest, pass `{ manifest }`, and rerun `featherk-fontawesome-setup --manifest fontawesome.keys.json`, which moves Pro packages into `fontawesome-pro-sources/`. Pro packages always live in `fontawesome-pro-sources/`; installing them into the application itself is not supported.
 
 ### Render the Selected Key
 
-```vue
+```html
 <template>
   <!-- Step 5: Render the generated descriptor directly through Kendo. -->
   <SvgIcon :icon="userIcon" />
@@ -173,8 +173,7 @@ The real `content` contains the complete path data; the abbreviated example is n
 While viewing the application on a running Vite dev server, inspect a descriptor from the browser console:
 
 ```js
-const { getFaIcon } =
-  await import("/@id/__x00__virtual:featherk/fontawesome");
+const { getFaIcon } = await import("/@id/__x00__virtual:featherk/fontawesome");
 
 console.log(getFaIcon("rocket"));
 ```
@@ -213,10 +212,6 @@ In the FeatherK monorepo, the exact root-relative pattern is `demos/src/featherk
 
 Most applications need only the [Quick Start](#quick-start). Use these only when it doesn't fit.
 
-### Pro in the Application
-
-An application whose tooling cannot use the separate `fontawesome-pro-sources/` project can install Pro packages into its own dependencies with `featherk-fontawesome-setup --manifest fontawesome.keys.json --pro-in-app` (see [Exception: Pro in the Application](LICENSING.md#exception-pro-in-the-application)). The plugin options stay `{ manifest }`, and every build includes the Pro keys. The cost is that every install of the application, by every developer and CI job, then needs the token. Use it only with a real reason.
-
 ### Type Checks Before Vite, and Non-Vite Projects
 
 The plugin writes its declarations when Vite starts, which is too late for a `vue-tsc` or `tsc` step that runs first. Projects in that situation, and projects that don't use Vite, generate with the `featherk-fontawesome` CLI from the same manifest; see [CLI and non-Vite setup](FontAwesomeCLI.md). Custom Node tooling can call `generateFaIcons` from `@featherk/icons/fontawesome/build`, which takes resolved keys instead of a manifest.

package/docs/fontawesome/FontAwesomeCLI.md

@@ -5,7 +5,7 @@ This is an advanced supplement. Most applications need only the Vite plugin; sta
 The CLI reads the same keys-only manifest as the setup command and the Vite plugin, and selects keys the same way:
 
 - When the project has `fontawesome-pro-sources/` (the [default setup](LICENSING.md#default-isolated-pro-sources)), it generates the `pro` keys from that project only when it is installed. Otherwise it generates the `free` keys alone.
-- Without `fontawesome-pro-sources/` (Free-only or `--pro-in-app` setups), it generates every manifest key from the application's installed packages.
+- Without `fontawesome-pro-sources/` (a Free-only setup), it generates the `free` keys; a manifest with `pro` keys then fails with a message to run the setup command.
 
 Install source packages first with `featherk-fontawesome-setup --manifest fontawesome.keys.json` ([Install Source Packages](FontAwesome.md#install-source-packages)). The CLI validates the installed packages; it does not install them or authenticate with a registry.
 

package/docs/fontawesome/FontAwesomeDeveloperSetup.md

@@ -1,6 +1,6 @@
 # FeatherK FontAwesome Developer Setup
 
-This is the step-by-step setup for a developer adding Font Awesome icons to an application with `@featherk/icons`, on a local machine and in CI. It covers the default layout every team uses: Free packages in the application, Pro packages in a private `fontawesome-pro-sources/` project. For background, see [Font Awesome Build Integration](FontAwesome.md). For licensing, token handling, and the `--free-only` and `--pro-in-app` exceptions, see [Font Awesome Pro Licensing and Setup](LICENSING.md).
+This is the step-by-step setup for a developer adding Font Awesome icons to an application with `@featherk/icons`, on a local machine and in CI. It covers the default layout every team uses: Free packages in the application, Pro packages in a private `fontawesome-pro-sources/` project. For background, see [Font Awesome Build Integration](FontAwesome.md). For licensing, token handling, and the `--free-only` exception, see [Font Awesome Pro Licensing and Setup](LICENSING.md).
 
 ## Before You Start
 

package/docs/fontawesome/LICENSING.md

@@ -52,9 +52,9 @@ npm run dev --workspace=@featherk/demos
 npm run build --workspace=@featherk/demos
 ```
 
-`setup:fontawesome:pro` runs `featherk-fontawesome-setup` without arguments, which installs `demos/fontawesome-pro-sources` from its committed lockfile with `npm ci`. The installer checks for the token without printing it. Review and commit dependency/integrity metadata for reproducible CI, ensuring it contains no credentials. Source `node_modules` and application artifacts remain ignored. No paid installation has been performed as part of implementing this setup.
+`setup:fontawesome:pro` runs `featherk-fontawesome-setup` without arguments, which installs `demos/fontawesome-pro-sources` from its committed lockfile with `npm ci`. The installer checks for the token without printing it. Review and commit dependency/integrity metadata for reproducible CI, ensuring it contains no credentials. Source `node_modules` and application artifacts remain ignored.
 
-The UX-approved Pro manifest requests Regular Rocket, Light Feather, and Light Heart. These pins are requested examples, not verified downloads. If entitlement, releases, or exports are unavailable, Dev must stop installation/generation and return to UX/Design for approval before changing the manifest or dependencies; never substitute silently.
+The UX-approved Pro manifest requests Regular Rocket, Light Feather, Light Heart, and Light House (`pro-rocket-regular`, `pro-feather-light`, `pro-heart-light`, `pro-house-light`). An authorized installation of these pins succeeded on October 15, 2026 (see [Validation Boundary](#validation-boundary)). If entitlement, releases, or exports later become unavailable, Dev must stop installation/generation and return to UX/Design for approval before changing the manifest or dependencies; never substitute silently.
 
 The demo has no separate Pro scripts: its normal `dev` and `build` include the Pro icons once `demos/fontawesome-pro-sources` is installed, and only the Free icons otherwise. `demos/turbo.json` adds `fontawesome-pro-sources/node_modules/.package-lock.json`, which npm writes on install, to the build's cache inputs, so the root Turborepo build never replays a Free build where Pro sources are installed, or the reverse. Do not put paid outputs into shared or remote caches.
 
@@ -154,7 +154,7 @@ Without arguments, the command runs `npm ci` in `fontawesome-pro-sources/` with
 
 ### Setup Safety Checks
 
-Before supplying the token, the command checks the `.npmrc` it will install with: the application's for `--pro-in-app`, and `fontawesome-pro-sources/.npmrc` for the default layout. It refuses any of the following:
+Before supplying the token, the command checks `fontawesome-pro-sources/.npmrc`. It refuses any of the following:
 
 - a `@fortawesome` registry other than `https://npm.fontawesome.com/`
 - any reference to `FONTAWESOME_PACKAGE_TOKEN` outside `//npm.fontawesome.com/:_authToken`
@@ -162,7 +162,9 @@ Before supplying the token, the command checks the `.npmrc` it will install with
 
 It also pins the Font Awesome registry on the npm command line, which overrides other npm configuration, so the token can only be sent to Font Awesome. It installs with `--ignore-scripts`, so lifecycle scripts never run while the token is present, passes the token only to that npm process, and never prints it. Setup with `--manifest` changes `package.json`, so it refuses to run in CI.
 
-The layouts cannot be mixed in one application. The default setup refuses an application whose `.npmrc` already routes `@fortawesome` to the Pro registry, and `--pro-in-app` refuses an application that has `fontawesome-pro-sources/`.
+`npm ci` lifecycle scripts and build tools run arbitrary Node code that can read any token in their environment, and log masking does not prevent that. Give the token only to `featherk-fontawesome-setup`, never to the application's `npm ci`, its build, or a whole CI job, and do not export it persistently.
+
+The application's own `.npmrc` must not route `@fortawesome` to a registry: Free packages come from public npm, and Pro packages only from `fontawesome-pro-sources/`. Setup refuses an application whose `.npmrc` does. That includes an application set up with the `--pro-in-app` option, which shipped in 0.16.0 and was then removed; remove the Font Awesome lines from its `.npmrc` and any `@fortawesome/pro-*` packages from its `devDependencies`, then rerun setup with `--manifest`.
 
 ### Exception: Free Only
 
@@ -174,55 +176,6 @@ npx featherk-fontawesome-setup --manifest fontawesome.keys.json --free-only
 
 Free packages come from public npm. The command needs no token or CI configuration and creates no source project. The default command behaves the same way for a manifest without Pro keys; `--free-only` also guarantees it, failing if the manifest contains Pro keys, if `fontawesome-pro-sources/` exists, or if `.npmrc` routes `@fortawesome` to a registry. Configure the Vite plugin with `{ manifest: "fontawesome.keys.json" }`. To add Pro later, add the keys to the manifest and rerun without `--free-only`.
 
-### Exception: Pro in the Application
-
-Use this only when an isolated source project is not an option, for example when the application's toolchain cannot resolve packages from the separate `fontawesome-pro-sources/` project:
-
-```sh
-npx featherk-fontawesome-setup --manifest fontawesome.keys.json --pro-in-app
-```
-
-The command adds the two Font Awesome lines shown above to the application's own `.npmrc`, creating it if needed (existing settings are kept, and the lines are not duplicated on later runs), then installs the exact Free and Pro pins into the application's `devDependencies` with the token. Commit `.npmrc`, `package.json`, and `package-lock.json`, and configure the Vite plugin with `{ manifest: "fontawesome.keys.json" }`. Without `fontawesome-pro-sources/`, every build includes the Pro keys.
-
-The cost is that the scope line routes **all** `@fortawesome` packages, Free included, to the Font Awesome registry. Every install of the application, by every developer and CI job, then needs `FONTAWESOME_PACKAGE_TOKEN` and an applicable seat.
-
-#### Token-Scoped Installs
-
-`npm ci` runs lifecycle scripts from the application and every dependency, and later build tools run arbitrary Node code. Any of them can read a token in their environment. Log masking and Vite's `VITE_` client-variable filter do not prevent this. Do not export the token persistently or for a whole CI build. In a Pro-in-the-application setup, give it only to an install that skips scripts, then run anything that needs scripts without it:
-
-1. With the token: `npm ci --ignore-scripts`.
-2. Without the token, run any install scripts the application needs:
-   - `npm rebuild` runs the dependency install scripts that step 1 skipped. On npm 12 and later, dependency scripts run only when approved in the application's `allowScripts` (`npm install-scripts approve <pkg>`), and `npm rebuild` follows the same approvals. Older npm versions run all of them.
-   - `npm rebuild` does not run the application's own lifecycle scripts. Run those explicitly, for example `npm run prepare --if-present`.
-3. Without the token: `npm run dev`, `npm run build`, tests, and deployment. npm runs normally when the `.npmrc` placeholder is unset; only `@fortawesome` registry requests need it.
-
-Git Bash:
-
-```bash
-read -r -s -p "Font Awesome package token: " fa_token; echo
-FONTAWESOME_PACKAGE_TOKEN="$fa_token" npm ci --ignore-scripts
-install_status=$?
-unset fa_token
-[[ $install_status -eq 0 ]] && npm rebuild
-```
-
-PowerShell:
-
-```powershell
-$env:FONTAWESOME_PACKAGE_TOKEN = [System.Net.NetworkCredential]::new(
-  "", (Read-Host "Font Awesome package token" -AsSecureString)
-).Password
-try {
-  npm ci --ignore-scripts
-  if ($LASTEXITCODE -ne 0) { throw "Font Awesome package installation failed." }
-} finally {
-  Remove-Item Env:FONTAWESOME_PACKAGE_TOKEN -ErrorAction SilentlyContinue
-}
-npm rebuild
-```
-
-The default layout needs none of this: the application's `npm ci` has no token, and `featherk-fontawesome-setup` already installs the source project with `--ignore-scripts`.
-
 ### Generation and Licensing Boundaries
 
 Keep Pro keys in the manifest's `pro` group. Public or uncredentialed builds must not include paid inputs: run them where `fontawesome-pro-sources/` is not installed.
@@ -233,7 +186,7 @@ For non-Vite applications or declaration generation before a standalone type che
 
 FeatherK and `feather-k-<demo-name>` repositories use GitHub Actions. TeamCity applies only to enterprise apps using that platform.
 
-In the default layout, a Pro build has three steps: the application's normal `npm ci` without the token, a token-scoped `npx featherk-fontawesome-setup` that installs `fontawesome-pro-sources/` from its lockfile, and the application's normal build without the token. Builds that don't need Pro icons skip the middle step and come out Free-only.
+A build that includes Pro icons has three steps: the application's normal `npm ci` without the token, a token-scoped `npx featherk-fontawesome-setup` that installs `fontawesome-pro-sources/` from its lockfile, and the application's normal build without the token. Builds that don't need Pro icons skip the middle step and come out Free-only.
 
 Use a dedicated trusted Actions job with a protected Environment and approval/branch rules. Supply the token only to source installation, not public publishing or client compilation. After checkout and Node/root dependency setup:
 
@@ -247,7 +200,7 @@ Use a dedicated trusted Actions job with a protected Environment and approval/br
   run: npm run build --workspace=@featherk/demos
 ```
 
-In CI, detected from `CI`, `TEAMCITY_VERSION`, or `GITHUB_ACTIONS`, the setup command refuses `--manifest` setup, and the source-project install requires the committed `package-lock.json`. Unattended jobs therefore only run a locked `npm ci` and never resolve new versions. In every layout, supply the token only to the install step that skips lifecycle scripts, never to the whole job. With no token and no interactive terminal, the command fails instead of prompting.
+In CI, detected from `CI`, `TEAMCITY_VERSION`, or `GITHUB_ACTIONS`, the setup command refuses `--manifest` setup, and the source-project install requires the committed `package-lock.json`. Unattended jobs therefore only run a locked `npm ci` and never resolve new versions. Supply the token only to the `featherk-fontawesome-setup` step, never to the whole job. With no token and no interactive terminal, the command fails instead of prompting.
 
 Configure the protected Environment separately; this fragment grants no license rights. Restrict paid caches/archives/artifacts, and never execute untrusted PR code with the token, including via `pull_request_target`. Normal public FeatherK publishing must not receive Pro credentials or use the licensed profile.
 
@@ -258,7 +211,7 @@ Do not define the token as an `env.` parameter. TeamCity passes `env.` parameter
 1. In the build configuration, add a parameter named `fontawesome.package.token` with type **Password**. Use no `env.` prefix, so TeamCity does not export it to the steps' environment.
 2. Add a Command Line step that sets the variable for one command only. Each Command Line step runs in its own process, so the variable does not carry into later steps.
 
-   For the [default layout](#default-isolated-pro-sources), leave the application's existing `npm ci` step unchanged and add this step after it:
+   Leave the application's existing `npm ci` step unchanged and add this step after it:
 
    ```sh
    # Linux agent
@@ -273,21 +226,6 @@ Do not define the token as an `env.` parameter. TeamCity passes `env.` parameter
 
    Leave the build step unchanged: with the sources installed, the normal build includes the Pro icons.
 
-   For [Pro in the application](#exception-pro-in-the-application), change the existing install step instead:
-
-   ```sh
-   # Linux agent
-   FONTAWESOME_PACKAGE_TOKEN='%fontawesome.package.token%' npm ci --ignore-scripts
-   ```
-
-   ```bat
-   rem Windows agent
-   set "FONTAWESOME_PACKAGE_TOKEN=%fontawesome.package.token%"
-   npm ci --ignore-scripts
-   ```
-
-   If the application or its dependencies need install scripts, add a step without the token. Use `npm rebuild` for dependency scripts, which follows `allowScripts` approvals on npm 12 and later. Run the application's own scripts explicitly, for example `npm run prepare --if-present`, because `npm rebuild` does not run them. See [Token-Scoped Installs](#token-scoped-installs).
-
 3. Leave the build, test, and deploy steps free of the parameter. They never reference it.
 
 Password parameters are masked in build logs, but masking does not stop code running in a step from reading the value. TeamCity also writes the step script, with the substituted value, to a temporary file on the agent. Limit the parameter to trusted build configurations and agents, and never run untrusted pull-request code in a build that defines it. Build agents must be able to reach `npm.fontawesome.com`. [Free-only](#exception-free-only) applications need no TeamCity configuration.
@@ -300,6 +238,6 @@ Enterprise Pages must enforce authentication on deployed URLs/static assets; rep
 
 Public `@featherk/icons` artifacts contain tooling and owned icons only: no paid dependencies/artwork, source caches, credentials, or generated paid-icon collections. Private distribution alone does not establish entitlement.
 
-Isolated-source resolution uses synthetic tests. Free generation and Pro-unavailable UI can be checked without secrets. Real paid exports, license notices, and enabled Pro rendering remain unverified until an authorized installation succeeds. Pro+ collections requiring Kits remain outside this no-Kit implementation.
+Automated tests use synthetic packages, so public CI needs no secrets. On October 15, 2026, an authorized installation of `demos/fontawesome-pro-sources` was checked locally: `npm run verify:fontawesome --workspace=@featherk/demos` verified all 14 demo selections, including the four Pro exports, against the installed packages (path data, viewBox, version, and style), and the build emitted both the Free and Pro license notices. Rendering of the Pro page in a browser was not part of that check. Re-run the verification after changing pins. Pro+ collections requiring Kits remain outside this no-Kit implementation.
 
-References: [package authentication](https://docs.fontawesome.com/web/setup/packages), [Pro license](https://fontawesome.com/license), and [Font Awesome account](https://fontawesome.com/account).
+References: [package authentication](https://docs.fontawesome.com/web/setup/packages), [Pro license](https://fontawesome.com/license), and [Font Awesome account](https://fontawesome.com/account).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@featherk/icons",
-  "version": "0.16.0",
+  "version": "0.16.1",
   "main": "dist/featherk-icons.umd.js",
   "module": "dist/featherk-icons.es.js",
   "types": "dist/index.d.ts",