@maccesar/titools 4.17.1 → 4.19.0

package/skills/purgetss/references/cli-commands.md

@@ -5,11 +5,7 @@ This page lists the commands available in PurgeTSS. For release-by-release featu
 <!-- TOC-START -->
 ## Contents
 
-- [Setup Commands](#setup-commands)
-- [Development Commands](#development-commands)
-- [Asset Commands](#asset-commands)
-- [Utility Commands](#utility-commands)
-- [Maintenance Commands](#maintenance-commands)
+- [Alloy and Classic Compatibility](#alloy-and-classic-compatibility)
 - [`init` Command](#init-command)
 - [`create` Command](#create-command)
 - [`brand` Command](#brand-command)
@@ -29,34 +25,21 @@ This page lists the commands available in PurgeTSS. For release-by-release featu
 
 <!-- TOC-END -->
 
-## Setup Commands
+## Alloy and Classic Compatibility
 
-- `init`: Initializes PurgeTSS on an existing Alloy project.
-- `create`: Creates a new Alloy project with PurgeTSS already set up.
-- `brand`: Generates the Titanium branding set from a single logo. See [`brand` Command](#brand-command).
-- `images`: Generates multi-density UI images from sources in `./purgetss/images/`. See [`images` Command](#images-command).
+The utility-class lifecycle remains Alloy-only. Classic projects can use independent asset and CommonJS commands without installing an `alloy.jmk` hook or adding PurgeTSS to their compilation flow.
 
-## Development Commands
+| Command | Alloy | Classic | Classic behavior |
+| --- | :---: | :---: | --- |
+| `brand` | yes | yes | Uses Classic asset paths and follows `tiapp.xml` deployment targets; `--only` is an explicit override. |
+| `images` | yes | yes | Writes under `Resources/` and follows deployment targets unless `--android` or `--ios` is explicit. |
+| `semantic` | yes | yes | Writes only `Resources/semantic.colors.json`; no utility setup is created. |
+| `shades` | yes | yes | Console modes work anywhere; saving creates or updates development-time `purgetss/config.cjs`. |
+| `color-module`, `module` | yes | yes | Writes CommonJS modules to `app/lib/` or `Resources/lib/`. |
+| `icon-library`, `build-fonts` | yes | yes | Writes fonts to `Resources/fonts/` and optional modules to `Resources/lib/`; Classic receives no TSS. |
+| Root `purgetss`, `--all`, `init`, `create`, `install-dependencies`, `build`, `watch` | yes | no | Alloy utility-class lifecycle only. |
 
-- `build`: Generates `utilities.tss` from `config.cjs`.
-- `watch`: Runs `purgetss` automatically on each project compile (defaults to `--on`).
-
-## Asset Commands
-
-- `icon-library`: Copies the official icon fonts into `./app/assets/fonts`.
-- `build-fonts`: Generates `./purgetss/styles/fonts.tss` with class definitions and `fontFamily` selectors for custom fonts.
-
-## Utility Commands
-
-- `shades`: Generates shades and tints for a color and writes the palette to `config.cjs`.
-- `semantic`: Generates Titanium semantic colors (Light/Dark) into `app/assets/semantic.colors.json`. See [`semantic` Command](#semantic-command).
-- `color-module`: Creates `./app/lib/purgetss.colors.js` with the colors defined in `config.cjs`.
-- `module`: Installs `purgetss.ui.js` in the `lib` folder.
-
-## Maintenance Commands
-
-- `update`: Updates PurgeTSS to the latest version.
-- `sudo-update`: Updates PurgeTSS using `sudo` to install npm modules if needed.
+See [Classic Project Support](./classic-projects.md) for the complete boundary and audit checklist.
 
 ## `init` Command
 
@@ -87,16 +70,17 @@ module.exports = {
     }
   },
   brand: {
-    background: '#FFFFFF',   // inherited by every piece that doesn't set its own
-    confirmOverwrites: true, // prompt before overwriting files (set false to skip)
-    optimize: false,         // true = quantize the generated PNGs to a palette (lossy)
+    background: '#FFFFFF',      // inherited by every piece that doesn't set its own
+    artworkCornerRadius: '0%',  // splashes, Feature Graphic and LaunchLogo
+    confirmOverwrites: true,    // prompt before overwriting files (set false to skip)
+    optimize: false,            // true = quantize the generated PNGs to a palette (lossy)
 
     // One block per piece — see the `brand` Command section for the full list.
-    icon: { padding: '4%' }, dark: { background: null }, tinted: {},
+    icon: { padding: '0%' }, dark: { background: null }, tinted: {},
     iosSplash: { padding: '26%' }, launchLogo: { padding: '12%' },
     marketplace: {}, featureGraphic: { padding: '12%' },
     adaptive: { padding: '18%' }, legacyIcon: { padding: '10%' },
-    appicon: {}, androidSplash: { padding: '26%' },
+    appicon: { padding: '10%' }, androidSplash: { padding: '26%' },
 
     // Opt-in: inert until you edit the Android theme / FCM meta-data by hand.
     splashIcon: { enabled: false }, notificationIcon: { enabled: false },
@@ -191,7 +175,7 @@ Recommended VSCode extensions:
 
 ## `brand` Command
 
-Introduced in v7.6.0, grouped config in v7.7.0, restructured into per-piece blocks in v7.13.0. Regenerates **every image the Titanium template ships**, from one main logo: launcher icons, adaptive icons, iOS 18+ Dark/Tinted variants, marketplace artwork, and both the iOS and Android splash sets. The rule is *if the template ships the file, `brand` updates it*. Each piece can take its own artwork, and `--only` narrows a run to the pieces you name. Alloy and Classic projects are auto-detected.
+Introduced in v7.6.0 and fully standalone in Classic since v7.14.0. Generates the complete Titanium branding set from one main logo: launcher icons, adaptive icons, iOS 18+ Dark/Tinted variants, marketplace artwork, and both splash sets. Alloy and Classic projects are auto-detected. A normal run follows `<deployment-targets>` in `tiapp.xml`; explicit `--only` intentionally overrides that filter.
 
 > **Tip**
 > This is a quick reference. See [app-branding.md](./app-branding.md) for the complete guide — workflow, padding guidance, Android dark mode, iOS 18+ variants, the launch-background setup, and troubleshooting. It also carries the full `brand:` config reference.
@@ -228,15 +212,20 @@ The 14 pieces, their config keys and what each one writes are tabulated in [app-
 | `--padding <n>` | Shortcut: sets both Android launcher paddings to the same value for one run. |
 | `--android-adaptive-padding <n>` | Adaptive icon safe-zone % (default `18`). |
 | `--android-legacy-padding <n>` | Legacy `ic_launcher.png` padding % (default `10`). |
-| `--ios-padding <n>` | Padding % for the four square iOS/marketplace pieces — `icon`, `dark`, `tinted`, `marketplace` (range `2-8`, default `4`). |
+| `--appicon-padding <n>` | `appicon.png` padding % (default `10`). |
+| `--ios-padding <n>` | Padding % for the four square iOS/marketplace pieces — `icon`, `dark`, `tinted`, `marketplace` (default `0`, full-bleed). |
 | `--feature-graphic-padding <n>` | Vertical padding % for `MarketplaceArtworkFeature.png` (range `0-40`, default `12`). |
 | `--launch-logo-padding <n>` | Padding % for `LaunchLogo.png` (default `12`). |
 | `--splash-padding <n>` | Shortcut: sets both splash paddings to the same value for one run. |
 | `--android-splash-padding <n>` | Padding % for `default.png` and the 11 `res-*` splashes (default `26`). |
 | `--ios-splash-padding <n>` | Padding % for the 16 iPhone launch images (default `26`). |
+| `--artwork-corner-radius <n>` / `--splash-corner-radius <n>` | Shared non-icon radius, or a splash-only one-run override (range `0-50`, default `0`). |
+| `--ios-splash-corner-radius <n>` / `--android-splash-corner-radius <n>` | Per-platform legacy splash artwork radius (range `0-50`). |
+| `--feature-graphic-corner-radius <n>` / `--launch-logo-corner-radius <n>` | Per-piece Feature Graphic or LaunchLogo artwork radius (range `0-50`). |
 
 Splash padding is a share of the canvas's **shorter** side, so one number keeps the logo at the same visual weight in portrait and in landscape: the `26%` default leaves it at 48% of the shorter side.
 
+Radius precedence and the outputs intentionally left unmasked are documented in [Rounded non-icon artwork](./app-branding.md#rounded-non-icon-artwork). Normal and `--dry-run` summaries report effective padding and radius.
 **Optional asset types**
 
 | Flag | Purpose |
@@ -244,7 +233,6 @@ Splash padding is a share of the canvas's **shorter** side, so one number keeps
 | `--notification-icon` | Also emit `ic_stat_notify.png × 5`. |
 | `--splash-icon` | Also emit `splash_icon.png × 5`. |
 | `--nine-patch` | Declared but not implemented yet; prints a warning and writes nothing. |
-
 **Logo variants & overrides**
 
 Every piece has a `--<piece>-logo <path>` flag — with no exceptions since v7.13.0 — each overriding the matching `purgetss/brand/logo-<piece>.{svg,png}`:
@@ -252,7 +240,6 @@ Every piece has a `--<piece>-logo <path>` flag — with no exceptions since v7.1
 `--icon-logo`, `--dark-logo`, `--tinted-logo`, `--ios-splash-logo`, `--launch-logo`, `--marketplace-logo`, `--feature-graphic-logo`, `--adaptive-logo`, `--legacy-icon-logo`, `--appicon-logo`, `--android-splash-logo`, `--splash-icon-logo`, `--notification-icon-logo`.
 
 `--launch-logo` is the one that also **activates** its piece. Two more sources are not pieces: `--monochrome-logo <path>` (the silhouette shared by the adaptive monochrome layer and the notification icons, `logo-mono.{svg,png}`) and the positional `<logo>` argument (the main logo).
-
 **Output size**
 
 | Flag | Purpose |
@@ -284,20 +271,18 @@ Every piece has a `--<piece>-logo <path>` flag — with no exceptions since v7.1
 
 > **Warning**
 > Breaking renames in v7.13.0: `--splash` → `--splash-icon`, `--notification` → `--notification-icon`, `--splash-logo` → `--splash-icon-logo`, `--feature-logo` → `--feature-graphic-logo`. `--icon-logo` now feeds the `icon` piece; the Android launcher source is `--adaptive-logo`. `--legacy-splash` is gone. **No aliases were kept.**
->
-> Also note `purgetss brand --help` still prints `default: 19` for `--android-adaptive-padding` and `default: 20` for the two splash paddings. Those help strings are stale — the pipeline applies `18`, `26` and `26`.
 
 ### Positional argument
 
-- `[logo-path]` (optional) — overrides auto-discovery of `purgetss/brand/logo.{svg,png}`. It is the main logo, source for every piece that has no override.
+- `[logo-path]` (optional) — main source for every piece without an override. In a standalone Classic first run, when no canonical logo exists, PurgeTSS moves this source to `purgetss/brand/logo.{svg,png}` after confirmation and reports the destination.
 
 ### Config block (v7.13.0 per-piece structure)
 
-Defaults live under `brand:` in `purgetss/config.cjs` and are injected automatically. The block has **one entry per piece**; each accepts the same four keys where they apply: `logo`, `padding` (never inherited), `background` (inherited from `brand.background`), `enabled`. Top-level: `background`, `confirmOverwrites`, `optimize`, `logo`, `monochromeLogo`.
+Defaults live under `brand:` in `purgetss/config.cjs`. Since v7.14.0, a standalone Classic run creates it when missing. Each piece accepts `logo`, `padding`, `cornerRadius`, `background`, and `enabled` where applicable; radius is valid only for the two legacy splashes, Feature Graphic, and LaunchLogo. Top-level settings include shared `artworkCornerRadius`, optional `splashCornerRadius`, background, persistence, optimization, and logo values.
 
 An unknown key aborts the run before a single file is written. A `brand:` block written for an older PurgeTSS is **rewritten on disk** on the next run, carrying over every customized value.
 
-Full annotated block and per-key reference: [app-branding.md → The `brand:` config section](./app-branding.md#the-brand-config-section) and [Older configs update themselves](./app-branding.md#older-configs-update-themselves). The recommended workflow is convention-first: drop files in `purgetss/brand/`, let auto-discovery pick them up, and use `config.cjs` only for a persistent override.
+Full annotated block and per-key reference: [app-branding.md → The `brand:` config section](./app-branding.md#the-brand-config-section). Use flags for one-run sources, geometry, selection, activation, background, or optimization; keep persistent preferences in `config.cjs`.
 
 ### Confirmation prompt
 
@@ -314,12 +299,12 @@ purgetss brand --adaptive-logo ./docs/app-icon.svg        # dedicated square And
 purgetss brand --splash-icon --splash-icon-logo ./docs/splash.svg  # custom Android 12+ splash artwork
 purgetss brand --launch-logo ./docs/wordmark.svg          # iOS launch screen logotype
 purgetss brand --feature-graphic-logo ./docs/feature.svg  # custom Google Play Feature Graphic
-purgetss brand --feature-graphic-padding 8                # tighter Feature Graphic padding
+purgetss brand --artwork-corner-radius 22                 # round supported non-icon artwork
+purgetss brand --splash-corner-radius 18                  # override both legacy splash sets
+purgetss brand --appicon-padding 14                       # temporary appicon.png inset
 purgetss brand --notification-icon --splash-icon          # add notification + splash icons
-purgetss brand --no-tinted                                # skip iOS 18+ tinted variant
 purgetss brand --optimize                                 # quantize the generated PNGs
 purgetss brand --dry-run                                  # preview without writing
-purgetss brand --cleanup-legacy --dry-run                 # preview legacy cleanup
 ```
 
 ### Android output groups
@@ -328,7 +313,7 @@ purgetss brand --cleanup-legacy --dry-run                 # preview legacy clean
 
 ## `images` Command
 
-Introduced in v7.6.0. Generates multi-density variants of your UI images (buttons, illustrations, logos, screen graphics) from a single high-resolution source per image. Alloy and Classic projects are auto-detected.
+Introduced in v7.6.0 and standalone in Classic since v7.15.0. Generates multi-density variants of UI images from one high-resolution source. Alloy and Classic projects are auto-detected. With neither platform flag, the command follows `<deployment-targets>` in `tiapp.xml`; `--android` and `--ios` are explicit overrides.
 
 > **Tip**
 > This is a quick reference. See [multi-density-images.md](./multi-density-images.md) for the complete guide — 4× source convention, re-processing single files, format conversion, subdirectory preservation, and troubleshooting.
@@ -360,6 +345,8 @@ purgetss images background/                           # re-process one subfolder
 
 - `[source]` (optional) — path to override auto-discovery. Resolves first against `purgetss/images/` (short paths like `buttons/btn.png`), then against cwd.
 
+Alloy outputs go under `app/assets/{android,iphone}/images/`; Classic outputs go under `Resources/{android,iphone}/images/`. Passing an existing external source in Classic does not bootstrap an empty `purgetss/images/` folder or config file.
+
 ### When to use `--width`
 
 Use `--width <n>` for SVG sources from vector editors with disproportionate viewBoxes — common in Affinity, Illustrator, and other design tools where the viewBox does not match the intended display size. Without the flag, every scale derives from the source's natural pixel size as a 4× master, which can produce unexpected output sizes.
@@ -409,14 +396,14 @@ purgetss images --dry-run                              # preview
 
 ## `semantic` Command
 
-Introduced in v7.6.0. Generates Titanium semantic colors (Light/Dark mode aware) into `app/assets/semantic.colors.json`. The command dispatches between two distinct modes based on whether `--single` is passed.
+Introduced in v7.6.0. Generates Titanium semantic colors with Light/Dark support. Alloy writes `app/assets/semantic.colors.json` and utility mappings; Classic writes only `Resources/semantic.colors.json` and does not create `purgetss/`, `config.cjs`, TSS, `app/`, or a hook. The command dispatches between two modes based on `--single`.
 
 > **Tip**
 > This is a quick reference. See [semantic-colors.md](./semantic-colors.md) for the complete guide — mirror inversion math, Titanium semantic color spec, class mapping conventions, and strategies for purpose-based design systems.
 
 ### Palette mode (no `--single`)
 
-One base hex, 11-shade tonal palette with mirror-by-index Light/Dark inversion anchored at shade `500`. Writes both files in one step: the JSON gets 11 entries, and `config.cjs` gets the family mapped to those semantic keys.
+One base hex, 11-shade tonal palette with mirror-by-index Light/Dark inversion anchored at shade `500`. Alloy writes the JSON plus the utility mapping in `config.cjs`; Classic writes only the native JSON entries.
 
 ```bash
 purgetss semantic <hex> <name>
@@ -427,7 +414,7 @@ Usage produces classes like `bg-amazon-50`, `text-amazon-500`, `border-amazon-95
 
 ### Single mode (`--single`)
 
-Explicit per-mode hex values for purpose-based semantic colors (`surfaceColor`, `textColor`, `borderColor`, `overlayColor`, etc.). Writes the JSON entry AND auto-maps it to a class in `config.cjs` by stripping the conventional `Color` suffix (e.g. `surfaceColor` → class `surface`).
+Explicit per-mode hex values for purpose-based semantic colors (`surfaceColor`, `textColor`, `borderColor`, `overlayColor`, etc.). Alloy writes the JSON entry and maps it to a utility class in `config.cjs`; Classic writes only the native JSON entry and uses its key directly in Titanium color properties.
 
 ```bash
 purgetss semantic --single <hex> <name> [--dark <hex>] [--alpha <0-100>]
@@ -479,13 +466,13 @@ Re-running on the same palette family fully replaces it: PurgeTSS strips prior k
 | `-a, --alpha <0-100>` | With `--single`, wraps both modes in `{ color, alpha }` per the Titanium spec. |
 | `-n, --name <name>` | Specify the name (alternative to the positional argument). |
 | `-r, --random` | Palette mode — use a random base color. |
-| `-o, --override` | Place the mapping in `theme.colors` instead of `theme.extend.colors`. |
-| `-q, --quotes` | Keep double quotes in `config.cjs`. |
+| `-o, --override` | Alloy only: place the mapping in `theme.colors` instead of `theme.extend.colors`. Ignored in Classic. |
+| `-q, --quotes` | Alloy only: keep double quotes in `config.cjs`. Ignored in Classic. |
 | `-l, --log` | Preview the JSON without writing any files. |
 
 ## `install-dependencies` Command
 
-This command installs dev dependencies and configuration files in existing PurgeTSS projects, and sets up Visual Studio Code support.
+This Alloy-only command installs dev dependencies and configuration files for the utility-class workflow and sets up Visual Studio Code support. Do not run it in Classic.
 
 ```bash
 purgetss install-dependencies
@@ -499,7 +486,7 @@ purgetss id
 
 ## `icon-library` Command
 
-Copies the bundled free font files (Font Awesome 7, Material Icons, Material Symbols, Framework7 Icons) into `./app/assets/fonts/`. Once the fonts are in place, every official icon class (`fa-home`, `ms-home`, `mi-home`, `f7-house`, etc.) works out of the box — PurgeTSS resolves them at compile time from its own bundled `dist/` files.
+Copies the bundled free font files (Font Awesome 7, Material Icons, Material Symbols, Framework7 Icons) to `app/assets/fonts/` in Alloy or `Resources/fonts/` in Classic. Alloy resolves the official utility classes at compile time; Classic uses the installed `fontFamily` plus Unicode directly or through the optional CommonJS module.
 
 ```bash
 purgetss icon-library [--vendor=fa,mi,ms,f7] [--module] [--styles]
@@ -513,17 +500,19 @@ purgetss il [-v=fa,mi,ms,f7] [-m] [-s]
 | Flag | Purpose |
 | --- | --- |
 | `-v, --vendor [fa,mi,ms,f7]` | Copy specific font vendors only (default copies all four). |
-| `-m, --module` | Copy the matching CommonJS module into `./app/lib/` so you can reference icons by name from controllers (`icons.fa.home`). |
-| `-s, --styles` | Copy the official `.tss` source files into `./purgetss/styles/` for reference only — not needed for the classes to work. |
+| `-m, --module` | Copy the matching CommonJS module into `app/lib/` (Alloy) or `Resources/lib/` (Classic). |
+| `-s, --styles` | Alloy only: copy official `.tss` sources into `purgetss/styles/` for reference. Classic skips this output. |
 
 Vendor aliases: `fa`/`fontawesome`, `mi`/`materialicons`, `ms`/`materialsymbol`, `f7`/`framework7`.
 
+Every installed module exposes `families.default`. Direct variant aliases are `solid`/`regular`/`brands` for Font Awesome; `regular`/`outlined`/`round`/`sharp`/`twoTone` for Material Icons; `outlined`/`rounded`/`sharp` for Material Symbols; and `fontFamily` for Framework7.
+
 > **Tip**
 > This is a quick reference. See [Icon Fonts](./icon-fonts.md) for the complete guide — variant tables (`.ms`/`.mso`/`.msr`/`.mss`, `.fa`/`.fas`/`.far`/`.fab`), XML usage patterns, the side-by-side four-family example, Font Awesome Pro / Beta workflow, and instructions for recreating removed libraries.
 
 ## `build-fonts` Command
 
-Generates `./purgetss/styles/fonts.tss` with class definitions and `fontFamily` selectors for any user-defined fonts dropped into `./purgetss/fonts/` (Google Fonts, brand typefaces, community icon libraries with `.ttf` + `.css` pairs).
+Installs user-defined fonts dropped into `purgetss/fonts/`. Alloy also generates `purgetss/styles/fonts.tss`; Classic copies only native fonts to `Resources/fonts/` and generates no TSS or utility definitions.
 
 ```bash
 purgetss build-fonts [-m] [-f]
@@ -536,13 +525,14 @@ purgetss bf [-m] [-f]
 
 | Flag | Purpose |
 | --- | --- |
-| `-m, --module` | Also generates a CommonJS module in `./app/lib/purgetss.fonts.js` exposing `exports.icons` and `exports.families` for use from controllers. |
+| `-m, --module` | Also generates `app/lib/purgetss.fonts.js` (Alloy) or `Resources/lib/purgetss.fonts.js` (Classic). `exports.families` contains every processed TTF/OTF PostScript name; icon CSS additionally populates `exports.icons`. |
 | `-f, --font-class-from-filename` | Uses the font filename as the class name and icon prefix instead of the font family. Replaces the old `-p` flag. |
 
 ### What it does
 
-1. Creates `./purgetss/styles/fonts.tss` with one `fontFamily` class per file.
-2. Copies the font files into `./app/assets/fonts/`, renamed to their PostScript names so they work on both iOS and Android.
+1. Copies font files to `app/assets/fonts/` (Alloy) or `Resources/fonts/` (Classic), renamed to their PostScript names.
+2. In Alloy only, creates `purgetss/styles/fonts.tss` with the TSS class definitions.
+3. With `--module`, creates the CommonJS module even for text-only font collections. Classic loads it with `require('lib/purgetss.fonts')`; see the [Classic module path table](./classic-projects.md#loading-generated-modules-in-classic).
 
 > **Tip**
 > This is a quick reference. See [Custom Fonts](./custom-fonts.md) for the complete guide — folder organization, class renaming, adding icon libraries, the `--module` output structure, and `--font-class-from-filename` workflow.
@@ -554,6 +544,8 @@ purgetss bf [-m] [-f]
 
 The `shades` command generates shades and tints for a given color and writes the palette to `config.cjs`.
 
+Saving works in Alloy and Classic. In Classic, `config.cjs` is only a development-time color source for commands such as `color-module`; it does not install the PurgeTSS utility lifecycle or create empty brand, font, or image source folders. If `Resources/lib/purgetss.colors.js` already exists, saving refreshes it. `--log`, `--json`, and `--tailwind` write nothing and work outside a project.
+
 ```bash
 purgetss shades [hexcode] [name]
 
@@ -654,7 +646,9 @@ purgetss s '#65e92c' -j
 
 ## `color-module` Command
 
-This command creates `purgetss.colors.js` in the `lib` folder with all colors defined in `config.cjs`.
+This command creates `purgetss.colors.js` with all colors defined in `config.cjs`: `app/lib/` in Alloy or `Resources/lib/` in Classic. A missing config is created as the color source, but Classic receives no empty `purgetss/brand/`, `purgetss/fonts/`, or `purgetss/images/` folders, Alloy hook, or TSS.
+
+Classic loads the result with `require('lib/purgetss.colors')`; see [Classic module paths](./classic-projects.md#loading-generated-modules-in-classic).
 
 ```bash
 purgetss color-module
@@ -687,7 +681,7 @@ This is handy for using colors in code without hardcoding values in multiple pla
 
 ## `build` Command
 
-The `build` command generates `utilities.tss` from `config.cjs`. Run it after you change `config.cjs`.
+The Alloy-only `build` command generates `utilities.tss` from `config.cjs`. It is not part of a Classic standalone workflow.
 
 ```bash
 purgetss build
@@ -704,7 +698,7 @@ When `purgetss` runs (manually or via `watch`), it checks for changes in `config
 
 ## `watch` Command
 
-The `watch` command runs PurgeTSS on each project compile. You do not need to run `build` manually after each change.
+The Alloy-only `watch` command runs PurgeTSS on each Alloy project compile. Classic projects do not install this hook.
 
 ```bash
 purgetss watch
@@ -719,12 +713,17 @@ The command installs a task in `alloy.jmk`:
 
 ```javascript
 task('pre:compile', (event, logger) => {
-  require('child_process').execSync('purgetss', logger.warn('::PurgeTSS:: Auto-Purging ' + event.dir.project));
-});
+  logger.warn(`::PurgeTSS:: Auto-Purging ${event.dir.project}`)
+  try {
+    require('child_process').execSync('purgetss', { stdio: 'inherit' })
+  } catch (error) {
+    logger.error('::PurgeTSS:: Auto-Purge failed. Run `purgetss` from the project root to see the cause.')
+    throw error
+  }
+})
 ```
 
-> **Info**
-> This feature works with standard Alloy projects compiled using `ti build`. It has not been tested with project types built using Webpack or Vue.
+The default synchronous hook inherits CLI output so validation details appear before Alloy's generic failure. Async mode forwards `stdout` and `stderr` and prints the same final hint. `init` refreshes old active or disabled hooks without changing their state; invoking `watch` normally enables a disabled hook.
 
 To deactivate it, use `--off`.
 
@@ -746,7 +745,9 @@ purgetss w -d
 
 ## `module` Command
 
-The `module` command installs `purgetss.ui.js` in the `lib` folder.
+The `module` command installs the self-contained `purgetss.ui.js` in `app/lib/` (Alloy) or `Resources/lib/` (Classic). Classic executes that generated file but needs no PurgeTSS CLI/package at build time or as an app dependency.
+
+Classic loads it with `require('lib/purgetss.ui')`; see [Classic module paths](./classic-projects.md#loading-generated-modules-in-classic).
 
 ```bash
 purgetss module
@@ -755,11 +756,7 @@ purgetss module
 purgetss m
 ```
 
-The PurgeTSS module includes:
-
-- Animation: Methods for playing or applying basic animations and transformations to Alloy objects.
-
-See [Animation System](./animation-system.md) for details.
+The module exports `AnimationProperties`, `createAnimation(args)`, `Appearance`, `deviceInfo()`, and `saveComponent()`. Its animation object exposes 15 state, drag, collision, position, feedback, and layout methods. See [Animation System](./animation-system.md) for Alloy or [`purgetss.ui` in Classic](./purgetss-ui-classic.md) for native JavaScript.
 
 ## `update` Command
 

package/skills/purgetss/references/custom-fonts.md

@@ -1,9 +1,29 @@
 # Custom Fonts
 
-Use the `purgetss/fonts/` folder and the `build-fonts` command to register any font in your Titanium app: brand typefaces, custom icon fonts, or community icon libraries that PurgeTSS no longer bundles.
+Use the `purgetss/fonts/` folder and the `build-fonts` command to register any font in Alloy or Classic: brand typefaces, custom icon fonts, or community icon libraries that PurgeTSS no longer bundles.
+
+| Output | Alloy | Classic |
+| --- | --- | --- |
+| Font files | `app/assets/fonts/` | `Resources/fonts/` |
+| Generated TSS classes | `purgetss/styles/fonts.tss` | Not generated |
+| `--module` output | `app/lib/purgetss.fonts.js` | `Resources/lib/purgetss.fonts.js` |
+
+Classic receives only native Titanium resources and optional CommonJS output. It does not receive `app/`, TSS, or an Alloy build hook.
 
 For the 4 official icon families that ship with PurgeTSS (Font Awesome 7, Material Icons, Material Symbols, Framework7), see [Icon Fonts](./icon-fonts.md) — they use the `icon-library` command and do **not** require `build-fonts`.
 
+<!-- TOC-START -->
+## Contents
+
+- [The `fonts` folder](#the-fonts-folder)
+- [The `build-fonts` command](#the-build-fonts-command)
+- [Adding icon fonts](#adding-icon-fonts)
+- [Options](#options)
+- [Custom proprietary icon fonts](#custom-proprietary-icon-fonts)
+- [Community-Discovered Patterns](#community-discovered-patterns)
+
+<!-- TOC-END -->
+
 ## The `fonts` folder
 
 Place `.ttf` or `.otf` files in `./purgetss/fonts/`. For icon fonts, also include the `.css` file that ships with the library. PurgeTSS reads it to extract the Unicode characters for each icon class.
@@ -49,13 +69,15 @@ $ purgetss build-fonts [-m] [-f]
 $ purgetss bf [-m] [-f]
 ```
 
-What it does:
+In Alloy it:
 
 1. Creates `./purgetss/styles/fonts.tss` with one `fontFamily` class per file.
 2. Copies the font files into `./app/assets/fonts/`, renamed to their PostScript names so they work on both iOS and Android.
 
+In Classic it copies the renamed font files into `Resources/fonts/` and deliberately skips TSS and utility definitions. Use each PostScript name directly through Titanium's `fontFamily` property.
+
 > ℹ️ **INFO — How this differs from the official icon fonts**
-> Unlike the [official icon fonts](./icon-fonts.md), which PurgeTSS resolves automatically from its own bundled files and need no `.tss` in your project, custom fonts **do** generate `./purgetss/styles/fonts.tss`. That file is then folded into the generated `app/styles/app.tss` when you run `purgetss` (or compile your app) — that is where the final classes used by Alloy live.
+> In Alloy, unlike the [official icon fonts](./icon-fonts.md), custom fonts generate `purgetss/styles/fonts.tss`, which is folded into generated `app/styles/app.tss`. Classic skips this class-generation step.
 
 After running `purgetss build-fonts` with the Bevan and Dancing Script example above:
 
@@ -156,7 +178,7 @@ After `purgetss build-fonts`, the generated `fonts.tss` includes the family clas
 
 Two optional flags adjust what `build-fonts` generates:
 
-- `-m, --module`: generates a CommonJS module in `./app/lib/purgetss.fonts.js` that exposes each icon's Unicode string to JavaScript. Handy when you set `label.text` from a controller.
+- `-m, --module`: generates a CommonJS module in `app/lib/purgetss.fonts.js` (Alloy) or `Resources/lib/purgetss.fonts.js` (Classic). Its `families` object exposes the PostScript name of every processed TTF/OTF; icon CSS additionally populates `icons` with Unicode strings.
 - `-f, --font-class-from-filename`: uses the font's filename as the font class name and icon prefix instead of the font family name. Useful when you want shorter prefixes. Replaces the old `-p` flag.
 
 ### Using `--module`
@@ -168,9 +190,9 @@ $ purgetss build-fonts --module
 $ purgetss bf -m
 ```
 
-To avoid prefix conflicts between libraries, each icon keeps its prefix as a nested object. Both `icons` and `families` are exported:
+The module is generated for text-only font collections too. By default, every TTF/OTF contributes a camel-cased PostScript-name key to `families`; with `--font-class-from-filename`, that key comes from the filename instead. Icon CSS can add a shorter family alias and a nested `icons` map. Both singular and plural export names remain available.
 
-`./app/lib/purgetss.fonts.js`
+`app/lib/purgetss.fonts.js` (Alloy) or `Resources/lib/purgetss.fonts.js` (Classic)
 ```javascript
 const icons = {
   // map-icons/map-icons.css
@@ -190,17 +212,40 @@ const icons = {
     // ...
   }
 };
+exports.icon = icons;
 exports.icons = icons;
 
 const families = {
+  'bevanItalic': 'Bevan-Italic',
+  'bevanRegular': 'Bevan-Regular',
+  'dancingScriptBold': 'DancingScript-Bold',
+  'dancingScriptMedium': 'DancingScript-Medium',
+  'dancingScriptRegular': 'DancingScript-Regular',
+  'dancingScriptSemiBold': 'DancingScript-SemiBold',
+  'mapIcons': 'map-icons',
+  'microns': 'microns',
   // map-icons/map-icons.css
   'mapIcon': 'map-icons',
   // microns/microns.css
   'mu': 'microns'
 };
+exports.family = families;
 exports.families = families;
 ```
 
+In Classic, load the generated file relative to `Resources/`:
+
+```javascript
+const customFonts = require('lib/purgetss.fonts')
+
+const heading = Ti.UI.createLabel({
+  text: 'Custom typography',
+  font: { fontFamily: customFonts.families.dancingScriptSemiBold, fontSize: 28 }
+})
+```
+
+See the complete [Classic module path table](./classic-projects.md#loading-generated-modules-in-classic).
+
 ### Using `--font-class-from-filename`
 
 When you want the class name and the icon prefix to come from the **filename** of the `.ttf` and `.css` instead of the font family, use `-f`.
@@ -240,7 +285,7 @@ purgetss
 /* ... */
 ```
 
-`./app/lib/purgetss.fonts.js`
+`app/lib/purgetss.fonts.js` (Alloy) or `Resources/lib/purgetss.fonts.js` (Classic)
 ```javascript
 const icons = {
   // map-icons/mp.css
@@ -260,14 +305,18 @@ const icons = {
     // ...
   }
 };
+exports.icon = icons;
 exports.icons = icons;
 
 const families = {
+  'map': 'map-icons',
+  'mic': 'microns',
   // map-icons/mp.css
   'mp': 'map-icons',
   // microns/mc.css
   'mc': 'microns'
 };
+exports.family = families;
 exports.families = families;
 ```
 
@@ -283,7 +332,7 @@ If your design system ships its own icon font, treat it like any other icon libr
 The following notes reflect community experience with `build-fonts` against real-world Titanium projects.
 
 > **💡 PostScript renaming**
-> `build-fonts` copies `.ttf`/`.otf` files into `./app/assets/fonts/` renamed to their **PostScript names**. iOS reads PostScript names while Android tolerates filenames; by renaming both platforms work from the same `fontFamily` value.
+> `build-fonts` copies `.ttf`/`.otf` files into `app/assets/fonts/` (Alloy) or `Resources/fonts/` (Classic), renamed to their **PostScript names**. iOS reads PostScript names while Android tolerates filenames; by renaming both platforms work from the same `fontFamily` value.
 
 > **🛑 Font Awesome Duotone**
 > Titanium cannot render Font Awesome duotone icons because each icon uses two glyphs. If you work with Font Awesome Pro, avoid documenting duotone as supported.

package/skills/purgetss/references/customization-deep-dive.md

@@ -50,13 +50,15 @@ module.exports = {
     }
   },
   brand: {
-    background: '#FFFFFF',   // inherited by every piece that doesn't set its own
-    confirmOverwrites: true, // prompt before overwriting files (set false to skip)
-    optimize: false,         // true = quantize the generated PNGs to a palette (lossy, ~71% smaller)
+    background: '#FFFFFF',      // inherited by every piece that doesn't set its own
+    artworkCornerRadius: '0%',  // rounded non-icon artwork: splashes, Feature Graphic and LaunchLogo
+    confirmOverwrites: true,    // prompt before overwriting files (set false to skip)
+    optimize: false,            // true = quantize the generated PNGs to a palette (lossy, ~71% smaller)
 
     // One block per piece. Artwork comes from purgetss/brand/logo-<piece>.{svg,png};
     // these keys are for numbers, colors and activation. Padding is never inherited.
-    icon:             { padding: '4%' },    // DefaultIcon.png + DefaultIcon-ios.png
+    // Only iosSplash, androidSplash, featureGraphic and launchLogo accept cornerRadius.
+    icon:             { padding: '0%' },    // DefaultIcon.png + DefaultIcon-ios.png
     dark:             { background: null }, // DefaultIcon-Dark.png
     tinted:           {},                   // DefaultIcon-Tinted.png
     iosSplash:        { padding: '26%' },   // assets/iphone/Default*.png × 16
@@ -65,7 +67,7 @@ module.exports = {
     featureGraphic:   { padding: '12%' },   // MarketplaceArtworkFeature.png (1024×500)
     adaptive:         { padding: '18%' },   // ic_launcher_{foreground,background,monochrome}.png × 5 + ic_launcher.xml
     legacyIcon:       { padding: '10%' },   // ic_launcher.png × 5
-    appicon:          {},                   // appicon.png (128×128)
+    appicon:          { padding: '10%' },   // appicon.png (128×128)
     androidSplash:    { padding: '26%' },   // assets/android/default.png + images/res-*/default.png × 11
 
     // Opt-in: inert until you edit the Android theme / FCM meta-data by hand.
@@ -98,14 +100,17 @@ The config file has four main sections: `purge`, `brand`, `images`, and `theme`.
 
 `brand:` and `images:` configure the matching CLI commands — see [CLI Commands: `brand`](./cli-commands.md#brand-command) and [CLI Commands: `images`](./cli-commands.md#images-command) for the full option lists. The rest of this page covers `purge` and `theme`.
 
-For `brand`, the structure is **one block per piece of artwork** (v7.13.0), each accepting the same four keys where they apply:
+For `brand`, the structure is **one block per piece of artwork** (v7.13.0), each accepting the same five keys where they apply:
 
 - `logo`: path to this piece's artwork, when it lives outside `purgetss/brand/`
 - `padding`: inset per side, as a number or a percentage string like `'19%'` — **never inherited**
+- `cornerRadius`: integer or percentage string from `0` through `50`, valid only in `iosSplash`, `androidSplash`, `featureGraphic`, and `launchLogo`
 - `background`: hex color, or `null` for transparent — inherited from `brand.background`
 - `enabled`: `false` turns a default piece off, `true` turns an opt-in piece on
 
-Plus `brand.background`, `brand.confirmOverwrites`, `brand.optimize`, `brand.logo` (the main logo) and `brand.monochromeLogo`.
+Plus `brand.background`, shared `brand.artworkCornerRadius` (default `'0%'`), optional splash-only `brand.splashCornerRadius`, `brand.confirmOverwrites`, `brand.optimize`, `brand.logo` (the main logo) and `brand.monochromeLogo`.
+
+Use flags for temporary artwork, geometry, the shared background, selection, activation, and optimization. Keep `confirmOverwrites`, permanent `enabled` values, and exceptional per-piece backgrounds in config. For radius, a piece-specific flag wins over the splash shortcut when applicable, then `--artwork-corner-radius`, piece config, `brand.splashCornerRadius` for splashes, `brand.artworkCornerRadius`, and `0%`.
 
 > **INFO — Older `brand:` blocks update themselves**
 > A `brand:` block written for an earlier PurgeTSS is rewritten **on disk** to this structure on the next run, carrying over every value that had been customized and printing each one it moved. Both earlier shapes are recognized: the original flat keys and the v7.7.0 grouped sections (`logos` / `padding` / `android` / `ios` / `colors`). This replaced the in-memory translation used from v7.10.2 to v7.12.1. A key that belongs to no structure at all — a typo — aborts the run with the list of valid ones instead of being ignored. See [App Icons & Branding → Older configs update themselves](./app-branding.md#older-configs-update-themselves).

package/skills/purgetss/references/dynamic-component-creation.md

@@ -2,7 +2,7 @@
 
 > **SCOPE NOTE**
 >
-> This reference covers dynamic component creation using **Alloy's `$.UI.create()` helper** and **`Alloy.createStyle()` + `applyProperties()`**, both combined with PurgeTSS utility classes. It is an Alloy + PurgeTSS integration guide, **not** documentation for the `purgetss.ui` native module (see [animation-system.md](./animation-system.md) and [animation-advanced.md](./animation-advanced.md) for that module).
+> This reference covers dynamic component creation using **Alloy's `$.UI.create()` helper** and **`Alloy.createStyle()` + `applyProperties()`**, both combined with PurgeTSS utility classes. It is an Alloy + PurgeTSS integration guide, **not** documentation for the `purgetss.ui` native module (see [animation-system.md](./animation-system.md) and [animation-advanced.md](./animation-advanced.md) for Alloy animation usage, or [purgetss-ui-classic.md](./purgetss-ui-classic.md) for the generated Classic runtime).
 >
 > For general Alloy controller and view patterns, refer to the `alloy-guides` and `alloy-howtos` skills.