chore: FA Pro kit — add @awesome.me scope to .npmrc, update plan

User created an FA Pro kit, so the icons come from the kit npm package
(@awesome.me/kit-<id>), not @fortawesome/pro-*-svg-icons. Added the @awesome.me
scope to .npmrc (same FA registry + env-var token); plan note updated accordingly.

.npmrc

@@ -6,4 +6,5 @@
 ;
 ; Do NOT paste the raw token into this file.
 @fortawesome:registry=https://npm.fontawesome.com/
+@awesome.me:registry=https://npm.fontawesome.com/
 //npm.fontawesome.com/:_authToken=${FONTAWESOME_NPM_TOKEN}

_claude/notes/upgrade-plan.md

@@ -116,10 +116,12 @@ font + ~2000 CSS rules + the npm dep all gone). `v4-style.min.css` **472 → 393
 - **Icons = SVG, tree-shaken, never the webfont.** One pipeline: npm SVG source → a build-time
   **SVG sprite** (`<symbol>` + `<svg><use href="#…">`) of only-used icons, referenced identically
   in classic PHP and block templates. (~40 distinct icons reused 134× → sprite beats inlining.)
-- **Font Awesome → FA Pro via npm** (user has a Pro license): install the **SVG** packages
-  (`@fortawesome/pro-*-svg-icons` / a kit) from FA's authed registry — **not** the webfont —
-  and feed them through the sprite. Swapping sets later = change the package + regenerate.
-  Replaces FA-font **and** FontMfizz.
+- **Font Awesome → FA Pro KIT via npm** (user created a project kit): install the kit's own npm
+  package **`@awesome.me/kit-<id>`** (NOT `@fortawesome/pro-*-svg-icons` — that's the whole style;
+  the kit is the curated set) and import only the icons used → tree-shaken into the sprite, **not**
+  the webfont. Curate the icon set in the FA dashboard; swap/extend = update the kit + reinstall.
+  Replaces FA-font **and** FontMfizz. (`.npmrc` has both `@fortawesome` + `@awesome.me` scopes →
+  FA registry; grab the exact install line + import paths from the kit's "Set Up" page.)
   - **Secret (DONE 2026-06-21):** committed **`.npmrc`** holds the registry + an env-var
     ref `_authToken=${FONTAWESOME_NPM_TOKEN}` (no token in the file, so it's safe to commit);
     the actual token lives in the shell env (`export FONTAWESOME_NPM_TOKEN=…` in `~/.zprofile`).