@maccesar/titools 5.0.0 → 5.1.0

package/skills/purgetss/references/grid-layout.md

@@ -83,31 +83,28 @@ The official source organizes the grid utilities into these categories. The stru
 
 ### Row Placement Utilities
 
-Control horizontal placement of children inside a row:
+The official docs list these as `start`, `end`, and `center`, but no classes with those names exist in `utilities.tss`. The grid alignment classes PurgeTSS generates are:
 
-| Class    | Effect                            |
-| -------- | --------------------------------- |
-| `start`  | Align to the start of the row     |
-| `end`    | Align to the end of the row       |
-| `center` | Align to the center of the row    |
+| Class          | Generated rule                                  |
+| -------------- | ----------------------------------------------- |
+| `items-start`  | `{ top: 0 }`                                    |
+| `items-end`    | `{ bottom: 0 }`                                 |
+| `items-center` | `{ width: Ti.UI.FILL, height: Ti.UI.FILL }`     |
 
-These apply to child views inside a `grid-cols-*` container and control horizontal placement within the grid cell.
+## Row Span Use Cases
 
-## Row Placement Use Cases
+`grid-rows-{n}` and `row-span-{n}` both set a percentage `height` on the view that carries them; neither one declares a row count for its children. `grid-rows-{n}` gives `100/n %` (`grid-rows-2` → `50%`), and `row-span-{n}` always gives `n/12` of the parent (`row-span-3` → `25%`), whatever `grid-rows-*` class appears elsewhere. To stack the children vertically, give the parent `grid-flow-row` (`layout: 'vertical'`, `height: '100%'`).
 
-Combining `row-span-{n}` with `grid-rows-{n}` lets you describe how an element occupies vertical space inside a grid column. The table below covers the most common combinations a Titanium UI tends to need. Every entry is verified against the `grid-rows-{n}` and `row-span-{n}` utilities described in the official source.
-
-| Pattern                                  | Example classes                          | Result                                                                                                  |
-| ---------------------------------------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------- |
-| Full-height column item                  | `grid-rows-1` + `row-span-1`             | One element fills the entire vertical space of the column.                                              |
-| Two equal stacked items                  | `grid-rows-2` + two children no span     | Two views stack vertically, each taking 50% of the column height.                                       |
-| Tall hero on top, short footer at bottom | `grid-rows-12` + `row-span-9`, `row-span-3` | Hero takes 75% of the column height, footer takes 25%.                                                  |
-| 3-6-3 vertical split                     | `grid-rows-12` + `row-span-3`, `row-span-6`, `row-span-3` | Header / body / footer split. Mirrors the 3-6-3 horizontal split shown for `col-span-{n}`.              |
-| Sidebar that spans every row             | `grid-rows-4` + child with `row-span-4`  | Element occupies the full height of a 4-row column. Useful for vertical separators or full-height nav.  |
-| Two short rows above a tall row          | `grid-rows-12` + `row-span-3`, `row-span-3`, `row-span-6` | Two preview cards above a larger detail panel.                                                          |
+| Pattern                                  | Children of a `grid-flow-row` parent            | Result                          |
+| ---------------------------------------- | ----------------------------------------------- | ------------------------------- |
+| Full-height item                         | `grid-rows-1` or `row-span-12`                  | One view at `100%`              |
+| Two equal stacked items                  | `grid-rows-2` on each child                     | `50%` + `50%`                   |
+| Tall hero on top, short footer at bottom | `row-span-9`, `row-span-3`                      | `75%` + `25%`                   |
+| 3-6-3 vertical split                     | `row-span-3`, `row-span-6`, `row-span-3`        | `25%` + `50%` + `25%`           |
+| Two short rows above a tall row          | `row-span-3`, `row-span-3`, `row-span-6`        | `25%` + `25%` + `50%`           |
 
 > **Note**
-> Just like `col-span-{n}`, the spans you write must add up to the value declared in `grid-rows-{n}` for the layout to fill the column without leftover space.
+> Just like `col-span-{n}` in a row, the `row-span-{n}` values in a column must add up to 12 to fill it without leftover space.
 
 ## Community-Discovered Patterns
 
@@ -118,8 +115,8 @@ The following notes come from community experience using the PurgeTSS grid syste
 
 ### Common Use Cases for Row Placement
 
-| Class    | Use case                          |
-| -------- | --------------------------------- |
-| `start`  | Left-aligned content              |
-| `end`    | Right-aligned buttons or labels   |
-| `center` | Centered content blocks           |
+| Class          | Use case                                                        |
+| -------------- | --------------------------------------------------------------- |
+| `items-start`  | Pin a view to the top of its cell (`top: 0`)                    |
+| `items-end`    | Pin a view to the bottom of its cell (`bottom: 0`)              |
+| `items-center` | Fill the cell (`width` and `height` set to `Ti.UI.FILL`)        |

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

@@ -27,10 +27,25 @@ Each family ships one or more variant classes, each pointing to a specific font
 | Font Awesome | Regular | `.far` | `FontAwesome7Free-Regular` |
 | Font Awesome | Brands | `.fab` | `FontAwesome7Brands-Regular` |
 | **Material Icons** | Regular | `.mi` | `MaterialIcons-Regular` |
+| Material Icons | Round | `.mir` | `MaterialIconsRound-Regular` |
+| Material Icons | Sharp | `.mis` | `MaterialIconsSharp-Regular` |
+| Material Icons | Two Tone | `.mit` | `MaterialIconsTwoTone-Regular` |
+| Material Icons | Outlined | `.mio` | `MaterialIconsOutlined-Regular` |
 | **Framework 7** | Regular | `.f7` | `Framework7-Icons` |
 
 > 💡 **TIP — Icon class names**
 > Across a family, the icon class is shared by every variant. For Material Symbols, there is one `ms-home` class; pair it with `.ms`, `.mso`, `.msr`, or `.mss` to pick the shape (outlined, rounded, or sharp). FontAwesome works the same way: `fa-home` pairs with `.fa`/`.fas` (Solid) or `.far` (Regular), while brand icons like `fa-github` need `.fab`. **The variant class chooses the font file. The icon class chooses the glyph.**
+>
+> Long-form aliases set the same `fontFamily`: `.fa-solid`, `.fa-regular`, `.fa-brands`, `.fontawesome`, `.fontawesome-solid`, `.fontawesome-regular`, `.fontawesome-brands`; `.material-icons`, `.material-icons-round`, `.material-icons-sharp`, `.material-icons-two-tone`, `.material-icons-outlined`; `.materialsymbol`, `.materialsymbol-rounded`, `.materialsymbol-sharp`, `.materialsymbol-outlined` (and the same names spelled `.material-symbol*`); `.f7i` and `.framework7`.
+
+### Size and color helpers
+
+| Family | Classes |
+|---|---|
+| Font Awesome | `.fa-xs` (12), `.fa-sm` (14), `.fa-1x` (16), `.fa-lg` (21), `.fa-2x` … `.fa-10x` (32 … 160, in steps of 16) |
+| Material Icons | `.mi-18`, `.mi-24`, `.mi-36`, `.mi-48`; `.mi-dark`, `.mi-dark-inactive`, `.mi-light`, `.mi-light-inactive` |
+| Material Symbols | `.ms-18`, `.ms-24`, `.ms-36`, `.ms-48`; `.ms-dark`, `.ms-dark-inactive`, `.ms-light`, `.ms-light-inactive` |
+| Framework 7 | `.size-14`, `.size-20`, `.size-24`, `.size-28`, `.size-32`, `.size-56`, `.size-112` |
 
 ### Full class lists
 
@@ -83,7 +98,7 @@ $ purgetss il -m -s
 
 ### CommonJS modules in Classic
 
-Each module exposes its existing icon lookup API plus a `families` object with `families.default`. Direct aliases are also available:
+Each module exposes an `icons` map with camel-cased keys (`icons.home`, `icons.arrowLeft`), the helpers `getIcon(name)`, `setText(name, view)`, `setTitle(name, view)`, `getRandomKey()`, and `getRandomValue()`, plus a `families` object with `families.default`. `getIcon`, `setText`, and `setTitle` fall back to `'N/A'` for an unknown name. Direct aliases are also available:
 
 | Module | Direct aliases |
 | --- | --- |
@@ -188,27 +203,27 @@ To use this file:
 
 Generated `app.tss` excerpt:
 ```css
-// PurgeTSS v7.10.2
+// PurgeTSS v7.17.1
 // Created by César Estrada
 // https://purgetss.com
 
-/* Ti Elements */
+// Ti Elements
 'View': { width: Ti.UI.SIZE, height: Ti.UI.SIZE }
 'Window': { backgroundColor: '#FFFFFF' }
 
-/* Default Font Awesome */
+// Default Font Awesome
 '.fa': { font: { fontFamily: 'FontAwesome7Free-Solid' } }
-'.fa-home': { text: '', title: '' }
+'.fa-home': { text: '\uf015', title: '\uf015' }
 
-/* Material Icons */
+// Material Icons
 '.mi': { font: { fontFamily: 'MaterialIcons-Regular' } }
-'.mi-home': { text: '', title: '' }
+'.mi-home': { text: '\ue88a', title: '\ue88a' }
 
-/* Material Symbols */
+// Material Symbols
 '.ms': { font: { fontFamily: 'MaterialSymbolsOutlined-Regular' } }
-'.ms-home': { text: '', title: '' }
+'.ms-home': { text: '\ue88a', title: '\ue88a' }
 
-/* Framework7 */
+// Framework7
 '.f7': { font: { fontFamily: 'Framework7-Icons' } }
 '.f7-house': { text: 'house', title: 'house' }
 ```
@@ -268,20 +283,22 @@ For the underlying mechanics (how `build-fonts` reads the `.css`, options like `
 '.boxicons': { font: { fontFamily: 'boxicons' } }
 '.lineicons': { font: { fontFamily: 'LineIcons' } }
 
-/* Unicode Characters */
-/* To use your Icon Fonts in Buttons AND Labels each class sets 'text' and 'title' properties */
+// Unicode Characters
+// To use your Icon Fonts in Buttons AND Labels each class sets 'text' and 'title' properties
 
-/* boxicons.css */
-'.bxl-meta': { text: '', title: '' }
-'.bx-lemon': { text: '', title: '' }
-/* ... */
+// boxicons.css
+'.bxl-meta': { text: '\uef27', title: '\uef27' }
+'.bx-lemon': { text: '\uef28', title: '\uef28' }
+// ...
 
-/* lineicons.css */
-'.lni-500px': { text: '', title: '' }
-'.lni-add-files': { text: '', title: '' }
-/* ... */
+// lineicons.css
+'.lni-500px': { text: '\uea03', title: '\uea03' }
+'.lni-add-files': { text: '\uea01', title: '\uea01' }
+// ...
 ```
 
+The codepoints come from whatever `.css` you place in the folder; the values above are from Boxicons 2.1.4 and LineIcons 3.0.
+
 ## Community-Discovered Patterns
 
 The following note reflects community experience working with icon fonts that depend on multiple glyphs per icon.

package/skills/purgetss/references/installation-setup.md

@@ -210,7 +210,7 @@ To use the example files:
 '.fas': { font: { fontFamily: 'FontAwesome7Free-Solid' } }
 ```
 
-More examples in the [Tailwind TSS Sample App](https://github.com/macCesar/utilities.tss-sample-app).
+More examples in the [Utilities TSS Sample App](https://github.com/macCesar/tailwind.tss-sample-app).
 
 > **WARNING: `Label`, `Button`, and `Switch` with opposite margins**
 > In Titanium, `Label`, `Button`, and `Switch` can stretch when opposite margins pin both sides of the same axis and the dimension is still implicit.

package/skills/purgetss/references/ios-large-titles.md

@@ -4,11 +4,10 @@ Enabling Large Titles on a Window is not a single-property change. When you pair
 
 ## The problem
 
-Setting `largeTitleEnabled: true` in isolation looks like it should be enough — Apple's docs suggest a single switch. In practice, omitting the two companion properties produces three distinct visual bugs that are easy to attribute to "iOS being weird" but really come from the layout engine not having enough information:
+On iOS, enabling `largeTitleEnabled` by itself can cause two issues:
 
 1. **Content overlaps behind the nav bar.** The ScrollView starts at `y=0`, hidden under the translucent navigation bar. Users see the top of the list cut off and assume content is missing. This happens when `largeTitleEnabled` is set but `autoAdjustScrollViewInsets` is not.
-2. **The large title flashes / renders with a delay.** On window open, the nav bar region paints empty for a frame or two, then the title pops in. With all three properties present, iOS has the layout it needs *before* the first paint, so the title is there from frame zero. Without `extendEdges`, there is a measurable shadow flash as the system recomputes the layout.
-3. **Collapse glitches on scroll.** The large title shrinks to standard size as the user scrolls down — that is the whole point. But if `extendEdges` is missing, the collapse animation can stutter or skip frames because iOS has to recompute the safe-area inset for every scroll event instead of treating the nav bar as part of the content area.
+2. **The large title renders with a visible delay.** On window open, the nav bar area appears empty for a moment before the title draws. With all three properties present, iOS calculates the layout before displaying the window.
 
 The fix is not to pick the "right" property. It is to set all three together.
 
@@ -17,14 +16,14 @@ The fix is not to pick the "right" property. It is to set all three together.
 | Property                     | Value                     | What it does                                                                                                                                |
 | ---------------------------- | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
 | `autoAdjustScrollViewInsets` | `true`                    | iOS automatically adjusts the ScrollView content insets so content starts below the nav bar instead of behind it. Without this, the ScrollView's first item sits hidden behind the translucent nav bar. |
-| `extendEdges`                | `[Ti.UI.EXTEND_EDGE_ALL]` | Content extends under the nav and tab bars, producing the translucent blur/refraction effect Large Titles depend on. Skipping this causes the shadow flash on open and stutters the collapse animation. |
+| `extendEdges`                | `[Ti.UI.EXTEND_EDGE_ALL]` | Content extends behind the bars, creating the blur/translucent effect. Without it (and `autoAdjustScrollViewInsets`), the large title renders with a visible delay. |
 | `largeTitleEnabled`          | `true`                    | Shows the oversized title in the navigation bar that collapses to standard size as the user scrolls. This is the master switch — the other two are required for it to render correctly. |
 
 Without `autoAdjustScrollViewInsets`, `extendEdges` pushes the content behind the nav bar without compensating the ScrollView insets. Without `extendEdges` + `autoAdjustScrollViewInsets`, using only `largeTitleEnabled` causes the large title to render with a visible delay: the empty nav bar area appears first, then the title draws. With all three properties, iOS calculates the layout before displaying the window.
 
 ## iOS-only — use the `ios:` modifier
 
-Large Title properties are iOS-only. On Android they either do nothing or raise compile-time errors. Always scope them with the `ios:` platform block in `config.cjs`, not as defaults that leak to Android.
+Large Title properties are iOS-only. Scope them with the `ios:` platform block in `config.cjs`, as the official recipe does, so they are not emitted as defaults for Android.
 
 ## Global defaults in `config.cjs`
 
@@ -51,7 +50,7 @@ Generated style in `./purgetss/styles/utilities.tss`:
 
 Individual windows now only need to override `largeTitleDisplayMode` when they want different collapse behavior (e.g. detail windows).
 
-> **Why an `ios:` block and not an inline `ios:` prefix?** `auto-adjust-scroll-view-insets` and `extend-edges-all` are platform-specific classes — they only exist with `[platform=ios]` suffix in `utilities.tss`. The `ios:` block ensures PurgeTSS resolves the platform-suffixed version. See [apply-directive.md](./apply-directive.md) → "Platform-Specific Classes".
+> **Why an `ios:` block?** The block is what produces the `'Window[platform=ios]'` selector above. The three classes themselves carry no platform suffix in `utilities.tss` (`'.auto-adjust-scroll-view-insets'`, `'.extend-edges-all'`, `'.large-title-enabled'`), so without the block the defaults would apply to every platform. Only the `large-title-display-mode-*` classes ship with `[platform=ios]`. See [apply-directive.md](./apply-directive.md) → "Platform-Specific Classes".
 
 ## NavigationWindow example
 
@@ -113,7 +112,7 @@ This overrides only the display mode, so the window still benefits from the inhe
 
 ## ScrollView pairing: `content-w-screen content-h-auto`
 
-When Large Titles are active, the paired ScrollView needs its content area sized so iOS can shrink/grow the title as the user scrolls. The canonical pattern:
+The official NavigationWindow and TabGroup examples pair the Window with this ScrollView:
 
 ```xml
 <ScrollView class="vertical content-w-screen content-h-auto">
@@ -124,17 +123,19 @@ When Large Titles are active, the paired ScrollView needs its content area sized
 - `content-w-screen` → `contentWidth: Ti.UI.FILL`
 - `content-h-auto` → `contentHeight: Ti.UI.SIZE`
 
-Sizing the content height to `Ti.UI.SIZE` is what lets iOS determine whether there is enough content to allow the large title to collapse on scroll.
-
 ## Quick reference — class to property map
 
 | Class | Property | Value |
 | --- | --- | --- |
 | `auto-adjust-scroll-view-insets` | `autoAdjustScrollViewInsets` | `true` |
+| `auto-adjust-scroll-view-insets-false` | `autoAdjustScrollViewInsets` | `false` |
 | `extend-edges-all` | `extendEdges` | `[Ti.UI.EXTEND_EDGE_ALL]` |
+| `extend-edges-none` | `extendEdges` | `[Ti.UI.EXTEND_EDGE_NONE]` |
 | `large-title-enabled` | `largeTitleEnabled` | `true` |
 | `large-title-enabled-false` | `largeTitleEnabled` | `false` |
-| `large-title-display-mode-never` | `largeTitleDisplayMode` | `Ti.UI.iOS.LARGE_TITLE_DISPLAY_MODE_NEVER` |
+| `large-title-display-mode-automatic` (iOS only) | `largeTitleDisplayMode` | `Ti.UI.iOS.LARGE_TITLE_DISPLAY_MODE_AUTOMATIC` |
+| `large-title-display-mode-always` (iOS only) | `largeTitleDisplayMode` | `Ti.UI.iOS.LARGE_TITLE_DISPLAY_MODE_ALWAYS` |
+| `large-title-display-mode-never` (iOS only) | `largeTitleDisplayMode` | `Ti.UI.iOS.LARGE_TITLE_DISPLAY_MODE_NEVER` |
 | `content-w-screen` | `contentWidth` | `Ti.UI.FILL` |
 | `content-h-auto` | `contentHeight` | `Ti.UI.SIZE` |
 
@@ -150,7 +151,7 @@ A recurring source of confusion: iOS `TabGroup` already wraps each `Tab` in an i
 
 ### Detail windows should opt out, not opt in
 
-When `theme.Window.ios.apply` sets `large-title-enabled` as a default, every pushed window inherits it. Apply `large-title-display-mode-never` on detail windows pushed via `openWindow()` so the parent keeps the collapse animation while detail screens render with a standard title. This mirrors Apple's own first-party app conventions (Settings, Mail).
+When `theme.Window.ios.apply` sets `large-title-enabled` as a default, every pushed window inherits it. Apply `large-title-display-mode-never` on detail windows pushed via `openWindow()` so the parent keeps the collapse animation while detail screens render with a standard title.
 
 ### Cross-reference
 

package/skills/purgetss/references/migration-guide.md

@@ -1,14 +1,18 @@
 # Migration Guide
 
-This guide mirrors the official PurgeTSS changelog (see the project `README.md` / `docs/index.md`). It walks through the upgrade-relevant changes from v7.2.6 through v7.13.x, flags breaking changes, and links each section to the reference files that cover the new surface area in depth.
+This guide summarizes the official PurgeTSS changelog: `CHANGELOG.md` in the package repository and the docs changelog page (`src/pages/changelog.md`, published at <https://purgetss.com/changelog>). It walks through the upgrade-relevant changes from v7.2.6 through v7.17.1, flags breaking changes, and links each section to the reference files that cover the new surface area in depth.
 
-Changelog source of truth: [https://github.com/macCesar/purgeTSS](https://github.com/macCesar/purgeTSS).
+Changelog source of truth: [CHANGELOG.md](https://github.com/macCesar/purgetss/blob/main/CHANGELOG.md).
 
 ---
 
 <!-- TOC-START -->
 ## Contents
 
+- [Upgrade to v7.17.x](#upgrade-to-v717x)
+- [Upgrade to v7.16.x](#upgrade-to-v716x)
+- [Upgrade to v7.15.0](#upgrade-to-v7150)
+- [Upgrade to v7.14.0](#upgrade-to-v7140)
 - [Upgrade to v7.13.x](#upgrade-to-v713x)
 - [Upgrade to v7.12.x](#upgrade-to-v712x)
 - [Upgrade to v7.11.x](#upgrade-to-v711x)
@@ -16,6 +20,7 @@ Changelog source of truth: [https://github.com/macCesar/purgeTSS](https://github
 - [Upgrade to v7.9.0](#upgrade-to-v790)
 - [Upgrade to v7.8.0](#upgrade-to-v780)
 - [Upgrade to v7.7.0](#upgrade-to-v770)
+- [Upgrade to v7.6.1 and v7.6.2](#upgrade-to-v761-and-v762)
 - [Upgrade to v7.6.0](#upgrade-to-v760)
 - [Upgrade to v7.5.3](#upgrade-to-v753)
 - [Upgrade to v7.5.0](#upgrade-to-v750)
@@ -28,9 +33,76 @@ Changelog source of truth: [https://github.com/macCesar/purgeTSS](https://github
 
 <!-- TOC-END -->
 
+## Upgrade to v7.17.x
+
+v7.17.0 and v7.17.1 change two things an existing project can trip over: unknown keys in `images:` now abort the run, and the notification icon has a new filename. Full release notes in [`version-history.md`](./version-history.md).
+
+### Changed in v7.17.1 — `notificationicon.png` replaces `ic_stat_notify.png`
+
+The `notification-icon` piece now writes `notificationicon.png`. `firebase.cloudmessaging` hardcodes that name (`getResource("notificationicon")`) and falls back to the opaque `appicon` when it is missing, which the status bar renders as a white blob. The meta-data snippet printed after a run now points at `@drawable/notificationicon`. See [`app-branding.md` → FCM notification icon](./app-branding.md#fcm-notification-icon).
+
+### Added in v7.17.0 — `images:` rejects unknown keys
+
+The section accepts exactly five top-level keys (`quality`, `format`, `autoSync`, `confirmOverwrites`, `files`) and three keys inside each `files[]` entry (`filename`, `width`, `height`, with `filename` required). Any other key, including `width`, `opacity`, `padding` or `output` (which are CLI flags), aborts the run before anything is generated. See [`multi-density-images.md` → Unknown keys are an error](./multi-density-images.md#unknown-keys-are-an-error-v7170).
+
+### Fixed in v7.17.0 — ESLint scaffolding
+
+`install-dependencies` and `create --dependencies` now install only `eslint` and `@eslint/js` and copy a flat `eslint.config.mjs`. The previous `.eslintrc.js` extending `eslint-config-axway/env-alloy` could not run under ESLint 9, so projects scaffolded since December 2025 had a lint that never ran. See [`cli-commands.md` → install-dependencies](./cli-commands.md#install-dependencies-command).
+
+### What to review
+
+- If you wired `@drawable/ic_stat_notify` into `tiapp.xml` by hand, change that meta-data line to `@drawable/notificationicon` and delete the five stale `ic_stat_notify.png` files.
+- Remove any misspelled or unsupported key from `images:` in `config.cjs`; the next `purgetss images` run lists every problem in one pass.
+- In Alloy projects with the old `.eslintrc.js`, re-run `purgetss install-dependencies` to replace it.
+
+---
+
+## Upgrade to v7.16.x
+
+v7.16.0 through v7.16.2 are additive — **no breaking changes**. Full release notes in [`version-history.md`](./version-history.md).
+
+- **Rounded non-icon artwork (v7.16.0).** `brand.artworkCornerRadius` (default `'0%'`, which keeps previous output unchanged) rounds the iPhone launch images, Android legacy splashes, Feature Graphic and LaunchLogo; those four pieces also accept `cornerRadius`, and `brand.splashCornerRadius` is a splash-only shared override. Six matching CLI flags exist. `cornerRadius` on any other piece, or outside `0–50`, stops the run before writing. See [`cli-commands.md` → brand](./cli-commands.md#brand-command).
+- **`--appicon-padding <n>` (v7.16.0)** — one-run override for `brand.appicon.padding` (default `10%`).
+- **Alloy hook diagnostics (v7.16.1).** The synchronous `alloy.jmk` hook inherits PurgeTSS output, so validation details appear before Alloy's generic `Command failed: purgetss`, followed by a hint to run `purgetss` from the project root. Existing active or disabled hooks are updated automatically without changing their enabled state.
+- **`build-fonts --module` (v7.16.2)** exports every processed TTF/OTF PostScript name through `families`, including text-only collections. See [`custom-fonts.md` → Using `--module`](./custom-fonts.md#using---module).
+- **Classic color commands (v7.16.2)** — `shades` and `color-module` no longer create empty `purgetss/brand/`, `purgetss/fonts/`, or `purgetss/images/` folders in Classic.
+
+---
+
+## Upgrade to v7.15.0
+
+v7.15.0 opens the standalone commands to Titanium Classic and changes one default for `images`. Full release notes in [`version-history.md`](./version-history.md).
+
+- **Classic support** — `images`, `semantic`, `shades`, `color-module`, `module`, `icon-library`, and `build-fonts` detect the project layout and write to native `Resources/` paths without installing the Alloy hook. See [`classic-projects.md`](./classic-projects.md).
+- **Behavior change — `images` follows `<deployment-targets>` in `tiapp.xml`.** A normal run skips disabled platforms; `--android` and `--ios` remain explicit overrides.
+- **Icon-font modules expose font-family aliases** — every module exports `families.default` plus variant aliases; existing `icons`, `getIcon`, `setText` APIs are unchanged. See [`icon-fonts.md`](./icon-fonts.md).
+
+### What to review
+
+- If a project disables one platform in `tiapp.xml` but relied on `purgetss images` generating both, pass `--android` or `--ios` explicitly.
+
+---
+
+## Upgrade to v7.14.0
+
+v7.14.0 changes generated icon output on upgrade. Full release notes in [`version-history.md`](./version-history.md).
+
+- **Behavior change — square iOS/store artwork is full-bleed by default.** `icon`, `dark`, `tinted` and `marketplace` now default to `0%` padding instead of `4%`. `--ios-padding` still adjusts all four.
+- **Fix that changes output — `brand.legacyIcon.padding` is the real per-side inset.** The generator used to multiply the value by 60%, so the documented `10%` rendered as `6%`.
+- **Fix that changes output — `DefaultIcon.png` uses `brand.icon.padding`** instead of inheriting the adaptive `18%`; both root icon files are flattened to opaque output.
+- **Behavior change — `brand` follows `<deployment-targets>` in `tiapp.xml`.** iOS pieces are skipped when both `iphone` and `ipad` are disabled, Android pieces when `android` is disabled; `--only` remains an explicit override.
+- **Standalone Classic `brand`** creates `purgetss/config.cjs` when missing, and Classic Android keeps the 11 `Resources/android/images/res-*` splash variants.
+- **Visible-frame warning** when a padded icon piece would expose a background that contrasts with the artwork's edge.
+
+### What to review
+
+- Compare regenerated `DefaultIcon*.png`, `iTunesConnect.png`, `MarketplaceArtwork.png` and `ic_launcher.png` against the previous set. If your iOS source is a logo that needs breathing room, raise `brand.icon.padding` or pass `--ios-padding`.
+
+---
+
 ## Upgrade to v7.13.x
 
-**This is the one release in the 7.x line with breaking changes.** They are confined to `purgetss brand`: its flags, the names of the files in `purgetss/brand/`, and the shape of the `brand:` config block. Nothing outside branding is affected — utility classes, `apply:`, `theme`, `images` and the SVG pipeline are untouched. Full release notes in [`version-history.md`](./version-history.md).
+**Breaking changes, confined to `purgetss brand`:** its flags, the names of the files in `purgetss/brand/`, and the shape of the `brand:` config block. Nothing outside branding is affected — utility classes, `apply:`, `theme`, `images` and the SVG pipeline are untouched. Full release notes in [`version-history.md`](./version-history.md).
 
 ### Breaking — `brand` flags renamed, no aliases kept
 
@@ -317,6 +389,21 @@ brand: {
 
 ---
 
+## Upgrade to v7.6.1 and v7.6.2
+
+Both releases are additive — **no breaking changes**.
+
+- **Confirmation prompt (v7.6.1).** `brand` and `images` ask `Continue? [y/N/a]` before overwriting project files. `a` persists `confirmOverwrites: false` in the matching config section; the prompt is skipped when `stdin` is not a TTY, with `-y` / `--yes`, or with `PURGETSS_YES=1`.
+- **Disproportionate-viewBox warning (v7.6.1)** for SVGs above 4096 pt on any side, with adaptive rasterization density so Affinity/Illustrator exports no longer exceed Sharp's pixel limit.
+- **`init` creates `purgetss/{fonts,brand,images}/` (v7.6.1)** from the first run.
+- **`semantic` works in Classic (v7.6.2)** — writes `Resources/semantic.colors.json`; Alloy keeps `app/assets/semantic.colors.json`. Unrelated existing entries are preserved.
+
+### What to review
+
+- CI jobs or scripts that run `brand` or `images` in a TTY need `-y` or `PURGETSS_YES=1` to avoid waiting on the prompt.
+
+---
+
 ## Upgrade to v7.6.0
 
 v7.6.0 introduces three new CLI commands for app-asset generation plus two new `config.cjs` sections. None of the additions are breaking — existing projects continue to work untouched, and the new config sections are auto-injected on first run.
@@ -331,8 +418,8 @@ v7.6.0 introduces three new CLI commands for app-asset generation plus two new `
 
 ### New `config.cjs` sections
 
-- **`brand:` section** — configures padding percentages, background colors, and platform targets for the `brand` command.
-- **`images:` section** — configures scale factors and output density mapping for the `images` command.
+- **`brand:` section** — configures padding percentages, background colors, the dark-icon background, and the opt-in splash and notification icons for the `brand` command.
+- **`images:` section** — configures output `quality` and `format` for the `images` command.
 
 Percentages can be written as self-documenting strings (e.g. `'15%'`) or plain numbers. Both are accepted. These sections are auto-injected into older `config.cjs` files on the first run of v7.6.0.
 
@@ -348,7 +435,7 @@ Percentages can be written as self-documenting strings (e.g. `'15%'`) or plain n
 - [`semantic-colors.md`](./semantic-colors.md) — palette vs single-color modes, alpha handling, and config mapping.
 - [`cli-commands.md#brand-command`](./cli-commands.md#brand-command)
 - [`cli-commands.md#images-command`](./cli-commands.md#images-command)
-- [`cli-commands.md#semantic-command`](./cli-commands.md#semantic-command)
+- [`color-commands.md#semantic-command`](./color-commands.md#semantic-command)
 
 ---
 
@@ -359,7 +446,7 @@ v7.5.3 is a feature-and-polish release. No breaking changes.
 ### Added
 
 - **Appearance module** — a new `Appearance` export for Light/Dark/System mode switching with persistence. Exposed methods: `init()`, `set(mode)`, `get()`, `toggle()`.
-- **Default font family classes** — `font-sans`, `font-serif`, and `font-mono` are generated automatically with platform-appropriate values (system sans, serif, and monospace stacks for iOS and Android).
+- **Default font family classes** — `font-sans`, `font-serif`, and `font-mono` are generated automatically with platform-appropriate values (`Helvetica Neue` / `sans-serif`, `Georgia` / `serif`, and `monospace` on iOS / Android).
 - **XML validation** — the pre-validation pass now detects illegal `--` sequences inside XML comments, which previously produced cryptic downstream errors.
 
 ### What to review
@@ -379,7 +466,7 @@ v7.5.0 adds `extend` support for component defaults and improves how `apply` dir
 
 ### Added
 
-- **`extend` support for Window, View, and ImageView** — customize component defaults from `theme.extend` in `config.cjs`. Previously only a subset of components supported `extend`.
+- **`extend` support for Window, View, and ImageView** — customize component defaults from `theme.extend` in `config.cjs`. Previously `theme.extend.Window` (and `View`, `ImageView`) was silently ignored; only `theme.Window` worked.
 - **Shorthand `apply`** — `{ apply: '...' }` is automatically normalized, so the `default:` wrapper is now optional.
 - **Property deduplication** — values pulled in via `apply` now win over static defaults instead of producing duplicate property entries in the generated TSS.
 - **Automatic platform resolution** — classes referenced inside `ios:` / `android:` blocks automatically find their platform-specific version instead of requiring explicit disambiguation.
@@ -516,16 +603,20 @@ If you previously worked around this by inlining the gradient directly in TSS, r
 ## Quick Checklist
 
 - Replace every legacy `tailwind.tss` reference with `utilities.tss`.
-- Verify Node.js 20+ before upgrading past v7.3.0.
+- Verify Node.js 20+ before upgrading to v7.2.7 or later.
 - Rebuild after updating `config.cjs` or custom gradient rules.
 - Re-test any Classic Titanium code that depends on `deviceInfo()`.
 - After v7.5.0: diff generated `utilities.tss` to confirm property deduplication produces the expected output.
 - After v7.5.3: consider wiring `Appearance.init()` at app boot if you want runtime Light/Dark switching.
 - After v7.6.0: run `brand`, `images`, and `semantic` once in a scratch project before pointing them at production assets, so you can preview the output layout.
 - After v7.7.0: migrate the `brand:` block in `config.cjs` to the grouped schema (`logos`, `padding`, `android`, `ios`, `colors`). v7.10.2 auto-migrates flat configs in memory. Moot from v7.13.0, which rewrites the block on disk to the per-piece structure by itself.
-- After v7.8.0: run the build once and address every `Class Syntax Error` it surfaces. Update CI to handle the new hard-fail on malformed class names. Migrate any `top-[10px]` style square brackets to `top-(10px)` parentheses.
+- After v7.8.0: run the build once and address every `Class Syntax Error` it surfaces. Update CI to handle the new hard-fail on malformed class names. Migrate any `top-[10px]` style square brackets to unitless parentheses, `top-(10)`.
 - After v7.9.0: search for any `purgetss/experimental/tailwind-classes/` references in tooling/CI and update to `purgetss/glossary/tailwind-classes/`. If a project used top-level `theme.Window` / `View` / `ImageView` and depended on framework defaults being merged in, decide between moving the config under `theme.extend.*` or adding the previously-implicit utilities to the `apply` string.
 - After v7.10.0: deeply nested color families (`theme.extend.colors.brand.primary.500`) now emit recursively — restructure by domain if it improves readability. `apply:` with bundled icon fonts (`fas`, `mi-*`, `ms-*`, `f7-*`) no longer requires `build-fonts` first. The Google Play Feature Graphic ships automatically with `purgetss brand`.
 - After v7.11.0: reference `.svg` images with numeric `w-*`/`h-*` classes to opt into the compile-time SVG pipeline (add `purgetss/.cache/` to `.gitignore`). Ensure every `theme.fontFamily.*` value is a string, not a Tailwind-style array, or the new config validator hard-fails. Use `images.files` to pin per-file sizes and `images.autoSync: false` to stop the pipeline writing back to `config.cjs`.
 - After v7.12.1: re-run `purgetss brand --notes` if you had copied an earlier Android splash snippet — the theme now belongs on the launcher Activity, not on `<application>`. Run `purgetss icon-library -v=fa` to pick up Font Awesome 7.3.1.
 - After v7.13.0: grep build scripts, `alloy.jmk` and CI for the renamed `brand` flags (`--splash`, `--notification`, `--splash-logo`, `--feature-logo`, `--legacy-splash`) — no aliases were kept. Rename any `logo-icon.*` used as the Android launcher mark to `logo-adaptive.*`, or the launcher icons silently fall back to the main logo. Let `config.cjs` rewrite its own `brand:` block, then read the diff.
+- After v7.14.0: compare the regenerated iOS/store icons (now full-bleed `0%`) and `ic_launcher.png` (real `10%` inset) against the previous set.
+- After v7.15.0: if one platform is disabled in `tiapp.xml`, pass `--android` or `--ios` to `purgetss images` when you still need that platform's densities.
+- After v7.17.0: remove unknown keys from `images:` and re-run `purgetss install-dependencies` in Alloy projects that still have `.eslintrc.js`.
+- After v7.17.1: point the FCM meta-data at `@drawable/notificationicon` and delete the old `ic_stat_notify.png` files.