@maccesar/titools 5.1.0 → 5.2.0

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

@@ -1,6 +1,6 @@
 # Migration Guide
 
-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.
+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.18.0, flags breaking changes, and links each section to the reference files that cover the new surface area in depth.
 
 Changelog source of truth: [CHANGELOG.md](https://github.com/macCesar/purgetss/blob/main/CHANGELOG.md).
 
@@ -9,6 +9,7 @@ Changelog source of truth: [CHANGELOG.md](https://github.com/macCesar/purgetss/b
 <!-- TOC-START -->
 ## Contents
 
+- [Upgrade to v7.18.0](#upgrade-to-v7180)
 - [Upgrade to v7.17.x](#upgrade-to-v717x)
 - [Upgrade to v7.16.x](#upgrade-to-v716x)
 - [Upgrade to v7.15.0](#upgrade-to-v7150)
@@ -33,6 +34,35 @@ Changelog source of truth: [CHANGELOG.md](https://github.com/macCesar/purgetss/b
 
 <!-- TOC-END -->
 
+## Upgrade to v7.18.0
+
+v7.18.0 fixes the defects an audit of the CLI found, and removes three things that never worked. Full release notes in [`version-history.md`](./version-history.md).
+
+### Removed
+
+- **The `(Npx)` check.** `w-(100px)` is valid again and generates `width: '100px'`, explicit pixels. A unitless `w-(100)` still follows `ti.ui.defaultunit`. The pre-validator now catches four patterns. See [`arbitrary-values.md`](./arbitrary-values.md#class-syntax-pre-validation).
+- **`snap-magnet` and `snap-magnet-false`.** The animation module never read `snap.magnet`.
+- **`init --all`.** Declared in 7.0.0, never implemented. The root `purgetss --all` is unaffected.
+
+### Fixed
+
+- **Stacked modifiers** such as `ios:tablet:bg-red-500` are generated, with every condition in one bracket. See [`platform-modifiers.md`](./platform-modifiers.md#combining-a-platform-and-a-device).
+- **Icon classes written only with a modifier** (`android:ms-home`) are generated.
+- **`bg-from-(#hex)`** writes a gradient instead of a literal `{value1}`.
+- **Font Awesome Pro/Beta:** `purgetss build` no longer fails with `ENOENT`, and `icon-library --module` / `--styles` build the files instead of printing a placeholder.
+- **`icon-library --vendor`** accepts `materialsymbols`; an unknown value stops the command before it writes anything.
+- **The nine `*-keyboard-type-appearance*` classes are gone.** They assigned an appearance constant to `keyboardType`; use `keyboard-appearance-*`.
+- **`images --width`** accepts 1 to 1024; above 1024 it used to write some densities and then fail at the 4096 px cap.
+- **`images`** detects Alloy from `app/views/`, like every other command.
+- **`swap()`** reads the source view's position from `rect` when it has no `top`/`left`.
+
+### What to review
+
+- Replace any `snap-magnet`, `*-keyboard-type-appearance*` or `init --all` in your project or scripts.
+- Anything you rewrote from `(Npx)` to a unitless value to get past the check now uses `dp` instead of pixels; restore the `px` if pixels are what you meant.
+
+---
+
 ## 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).
@@ -328,11 +358,11 @@ Five patterns are now caught and reported with file + line + suggested fix:
 | Whitespace inside parentheses | `wh-( 200 )` | `wh-(200)` |
 | Redundant `px` unit | `top-(10px)` | `top-(10)` |
 
-All offenders are reported in a single run. Generic unknown classes — typos, vendor utilities not enabled, custom classes not declared yet — continue to flow into `// Unused or unsupported classes`. See [`arbitrary-values.md` → Class syntax pre-validation](./arbitrary-values.md#class-syntax-pre-validation).
+v7.18.0 removed the redundant-`px` pattern (see [Upgrade to v7.18.0](#upgrade-to-v7180)). All offenders are reported in a single run. Generic unknown classes — typos, vendor utilities not enabled, custom classes not declared yet — continue to flow into `// Unused or unsupported classes`. See [`arbitrary-values.md` → Class syntax pre-validation](./arbitrary-values.md#class-syntax-pre-validation).
 
 ### Added — `purgetss images --width <n>` (v7.8.0)
 
-Pins Android `mdpi` (= iPhone `@1x`) to `<n>` pixels wide. Larger scales derive as ×1.5, ×2, ×3, ×4 from that base. Range `[1, 8192]`. Most useful for SVG sources from vector editors (Affinity, Illustrator) with disproportionate viewBoxes. CLI-only — width is per-asset, not a project-wide setting. See [`multi-density-images.md`](./multi-density-images.md#pinning-the-output-width-with---width).
+Pins Android `mdpi` (= iPhone `@1x`) to `<n>` pixels wide. Larger scales derive as ×1.5, ×2, ×3, ×4 from that base. Range `[1, 8192]` (v7.18.0 narrowed it to `[1, 1024]`). Most useful for SVG sources from vector editors (Affinity, Illustrator) with disproportionate viewBoxes. CLI-only — width is per-asset, not a project-wide setting. See [`multi-density-images.md`](./multi-density-images.md#pinning-the-output-width-with---width).
 
 ### Fixed in v7.8.0
 
@@ -498,7 +528,7 @@ v7.4.0 is the **Animation module expansion**. Nine new methods bring the Animati
 ### Added
 
 - **New methods**: `transition`, `pulse`, `sequence`, `swap`, `shake`, `snapTo`, `reorder`, `undraggable`, `detectCollisions`.
-- **New utility classes**: `snap-back`, `snap-center`, `snap-magnet`, `keep-z-index`.
+- **New utility classes**: `snap-back`, `snap-center`, `snap-magnet`, `keep-z-index` (`snap-magnet` was removed in v7.18.0).
 - **Delta-based drag for transformed views** — drag math now works correctly when the view already has a 2D transform applied.
 - **Position normalization** and **property inheritance** from the Animation object — reduces boilerplate when sequencing multiple animations on the same view.
 

package/skills/purgetss/references/multi-density-images.md

@@ -156,20 +156,20 @@ The pinned width drives the scale for every density:
 
 ### Validation
 
-`--width` accepts integers in `[1, 8192]`. Out-of-range values are rejected immediately and the command exits without writing anything:
+`--width` accepts integers in `[1, 1024]` (v7.18.0; earlier versions accepted up to 8192 and then failed on the 4096 px cap). Out-of-range values are rejected immediately and the command exits without writing anything:
 
 ```bash
 purgetss images logo.svg --width 0
-# Invalid --width '0'. Must be an integer between 1 and 8192.
+# Invalid --width '0'. Must be an integer between 1 and 1024.
 
 purgetss images logo.svg --width 9000
-# Invalid --width '9000'. Must be an integer between 1 and 8192.
+# Invalid --width '9000'. Must be an integer between 1 and 1024.
 
 purgetss images logo.svg --width abc
-# Invalid --width 'NaN'. Must be an integer between 1 and 8192.
+# Invalid --width 'NaN'. Must be an integer between 1 and 1024.
 ```
 
-Passing validation does not guarantee a run: every output is capped at 4096 px per side, and `xxxhdpi` is 4× the pinned width, so any `--width` above `1024` aborts with `… exceeds the 4096px cap`.
+Passing validation does not guarantee a run: every output is capped at 4096 px per side, width and height, and the height follows the source's aspect ratio. A source taller than it is wide can still abort at `xxxhdpi` with `… exceeds the 4096px cap`.
 
 ### The hint message for unflagged SVGs
 
@@ -531,7 +531,7 @@ Classic projects have no PurgeTSS build step: generate the images, then run `ti
 | --- | --- |
 | `--format <ext>` | Convert all outputs to: `webp`, `jpeg`, `png`, `avif`, `gif`, `tiff`. Default: keep source format. |
 | `--quality <n>` | Quality `0–100` for `webp`, `jpeg`, `avif` and `tiff`. PNG and GIF ignore it. Default `85`. |
-| `--width <n>` | (v7.8.0) Pin `mdpi` / `@1x` output width to `n` pixels; validated to `[1, 8192]`, but outputs are capped at 4096 px so values above `1024` abort. Other densities derive from this base (×1.5 / ×2 / ×3 / ×4). Most useful for SVG sources with non-standard viewBoxes. CLI-only — no `config.cjs` equivalent because width is per-asset. |
+| `--width <n>` | (v7.8.0) Pin `mdpi` / `@1x` output width to `n` pixels; validated to `[1, 1024]`, because `xxxhdpi` renders at 4× and outputs are capped at 4096 px. Other densities derive from this base (×1.5 / ×2 / ×3 / ×4). Most useful for SVG sources with non-standard viewBoxes. CLI-only — no `config.cjs` equivalent because width is per-asset. |
 | `--opacity <n>` | (v7.10.0) Multiply the alpha channel of every generated density by `n/100`. Range `[0, 100]`. Combine with `--format jpeg` and the alpha is flattened on white instead of producing a transparent JPEG. CLI-only. |
 | `--padding <n>` | (v7.10.0) Shrink the rendered image inside each density canvas by `n%` symmetric borders. Range `[0, 40]`. CLI-only. |
 | `--output <relpath>` | (v7.10.0) Override the basename and subpath relative to each platform's `images/` root. Lets a source from outside `purgetss/images/` (e.g. `purgetss/brand/`) write into a custom output folder like `images/logos/`. CLI-only. |

package/skills/purgetss/references/platform-modifiers.md

@@ -43,6 +43,27 @@ You can set different background colors and font sizes per platform and device,
 '.tablet:bg-green-500[formFactor=tablet]': { backgroundColor: '#22c55e' }
 ```
 
+## Combining a platform and a device
+
+Since v7.18.0, stack one platform modifier and one device modifier, in either order. Both conditions go in a single bracket, because Alloy's styler keeps only the last `[...]` of a selector.
+
+```xml
+<View class="ios:tablet:bg-red-500 tablet:ios:mt-4" />
+```
+
+```tss
+'.ios:tablet:bg-red-500[platform=ios formFactor=tablet]': { backgroundColor: '#ef4444' }
+'.tablet:ios:mt-4[formFactor=tablet platform=ios]': { top: 16 }
+```
+
+A platform modifier that contradicts a platform-scoped class generates nothing and leaves a comment in `app.tss`:
+
+```tss
+// Conflicting modifiers, class not generated: '.android:status-bar-dark' (platform is already ios)
+```
+
+Before v7.18.0, a stacked class was not generated, and `tablet:` on an iOS-only class produced `[platform=ios][formFactor=tablet]`, which Alloy read as tablet-only on both platforms.
+
 ## Community-Discovered Patterns
 
 The following guidance comes from community experience combining platform modifiers with platform-specific Titanium constants.

package/skills/purgetss/references/ui-ux-design.md

@@ -169,7 +169,7 @@ The catalog below collects real-world UI patterns verified against Titanium's co
 ```
 
 > **⚠️ Input Padding**
-> Padding utilities (`p-`, `px-`, `py-`) set the `padding` property, which the Titanium API defines only on `TextField` and `TextArea` (Android and iOS; `TextArea` honors left and right only) and `Ti.UI.Android.CardView` (apidoc 13_4_1_GA). `utilities.tss` labels the block "Android Only", which is inaccurate for the two text inputs. They are NOT for `Button` (especially iOS/Mac) and NOT on container views (`View`, `Window`, `ScrollView`, `TableView`). Use margins on children to simulate internal spacing on containers.
+> Padding utilities (`p-`, `px-`, `py-`) set the `padding` property, which the Titanium API defines only on `TextField` and `TextArea` (Android and iOS; `TextArea` honors left and right only) and `Ti.UI.Android.CardView` (apidoc 13_4_1_GA). They are NOT for `Button` (especially iOS/Mac) and NOT on container views (`View`, `Window`, `ScrollView`, `TableView`). Use margins on children to simulate internal spacing on containers.
 
 ## Buttons
 

package/skills/purgetss/references/version-history.md

@@ -8,7 +8,12 @@ When in doubt about whether a class, flag, or config key exists in the user's in
 
 ---
 
-## Unreleased (after v7.17.1)
+## v7.18.0
+- **`(Npx)` is valid again.** The redundant-`px` check is gone: `w-(100px)` generates `width: '100px'`, explicit pixels; unitless values follow `ti.ui.defaultunit`. The pre-validator catches 4 patterns. See [arbitrary-values.md](arbitrary-values.md).
+- Stacked modifiers (`ios:tablet:`, either order) generate one bracket, `[platform=ios formFactor=tablet]`; a contradicting modifier leaves a comment in `app.tss`. See [platform-modifiers.md](platform-modifiers.md).
+- Removed: `snap-magnet` / `snap-magnet-false`, the nine `*-keyboard-type-appearance*` classes, and `init --all`.
+- Fixed: `bg-from-(#hex)`, icon classes written only with a modifier, Font Awesome Pro/Beta in `build` and `icon-library -m/-s`, `icon-library --vendor=materialsymbols` (unknown vendors now abort), `images --width` limited to 1–1024, one `detectProjectType()`, `swap()` falling back to `rect`.
+- The `padding` block in `utilities.tss` is no longer labeled Android-only.
 - The comment above the opt-in pieces in the generated config now names each consumer instead of claiming both are inert without hand-edited XML. Only `splash_icon` is.
 
 ## v7.17.1
@@ -108,7 +113,7 @@ When in doubt about whether a class, flag, or config key exists in the user's in
 
 ## v7.8.0
 - `purgetss images --width <n>` pins Android `mdpi` / iPhone `@1x` to `<n>` pixels for SVG sources with disproportionate viewBoxes (Affinity, Illustrator). CLI-only.
-- Class syntax pre-validation emits `Class Syntax Error` blocks for 5 patterns: inverted negative (`top-(-10)` → `-top-(10)`), brackets (`top-[10px]` → `top-(10px)`), empty parens (`wh-()`), whitespace in parens, redundant `px` unit. Generic unknown classes still flow into `// Unused or unsupported classes`.
+- Class syntax pre-validation emits `Class Syntax Error` blocks for 5 patterns: inverted negative (`top-(-10)` → `-top-(10)`), brackets (`top-[10px]` → `top-(10px)`), empty parens (`wh-()`), whitespace in parens, redundant `px` unit (removed in v7.18.0). Generic unknown classes still flow into `// Unused or unsupported classes`.
 
 ## v7.7.0
 - `brand:` config restructured into grouped sections: `brand.logos`, `brand.padding`, `brand.android`, `brand.ios`, `brand.colors`. Old projects keep working; new configs use grouped form. See [app-branding.md](app-branding.md).
@@ -129,7 +134,7 @@ When in doubt about whether a class, flag, or config key exists in the user's in
 
 ## v7.5.1
 - Fix: `dist/purgetss.ui.js` shipped in v7.5.0 without `pulse()`, the latest `transition()` improvements, and delta-based drag for transformed views; rebuilt from the template. Re-run `purgetss module` to get them.
-- Fix: `snap-back`, `snap-center`, `snap-magnet`, and `keep-z-index` classes are now generated in `utilities.tss`.
+- Fix: `snap-back`, `snap-center`, `snap-magnet`, and `keep-z-index` classes are now generated in `utilities.tss` (`snap-magnet` was removed in v7.18.0).
 - Font Awesome updated to 7.2.0.
 
 ## v7.5.0
@@ -140,7 +145,7 @@ When in doubt about whether a class, flag, or config key exists in the user's in
 
 ## v7.4.0
 - Animation module: 9 new methods (`transition`, `pulse`, `sequence`, `swap`, `shake`, `snapTo`, `reorder`, `undraggable`, `detectCollisions`). 15 methods total. See [animation-system.md](animation-system.md).
-- New utility classes: `snap-back`, `snap-center`, `snap-magnet`, `keep-z-index`.
+- New utility classes: `snap-back`, `snap-center`, `snap-magnet`, `keep-z-index` (`snap-magnet` removed in v7.18.0).
 - Delta-based drag for transformed views; property inheritance from Animation object.
 
 ## v7.3.1

package/skills/ti-admob-unified/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: ti-admob-unified
+description: "Use when a Titanium app declares ti.admob.unified or its mediation complements, imports require('ti.admob.unified'), or asks to integrate/configure AdMob banners, interstitials, rewarded or app-open ads, UMP/ATT, privacy options, lifecycle, ad frequency or AppLovin, Meta, InMobi, Unity and Liftoff mediation with this module. Applies to Alloy and Classic on Android/iOS."
+---
+
+# ti.admob.unified — ads, privacy and providers
+
+Integrate César's unified Titanium module using its official documentation and maintained application library. The local **1.0.0** contract is preparing for its first public release; do not claim a public release or usable production demand from these snapshots. Sources are pinned to **`5b4cbf9347a51c4f959dc262ac1500f82f28b4a0`**, copied 2026-10-11. See `references/source-snapshot.json` for paths/hashes and [references/source-notes.md](references/source-notes.md) for provenance and update checks. Check the installed build and current sources when behavior differs.
+
+## Required workflow
+
+Read the relevant references before proposing calls or configuration. Do not infer this API from old `ti.admob`, `ti.android.admob` or raw Google SDK examples.
+
+| Task | Read first |
+| --- | --- |
+| Install artifacts, app IDs, platform settings, first test request | [references/getting-started.md](references/getting-started.md) |
+| Ownership, navigation, layout, refresh, Alloy/Classic integration | [references/integration.md](references/integration.md), [references/library.md](references/library.md) |
+| Exact factories/methods/options/events/constants/payloads | [references/api-reference.md](references/api-reference.md) |
+| Consent-first startup, ATT, privacy options, request eligibility | [references/privacy.md](references/privacy.md) |
+| Fixed/adaptive banners, real reserved layout and pause/cleanup | [references/banners.md](references/banners.md) |
+| Interstitial/rewarded/app-open load/show, rewards and cleanup | [references/fullscreen.md](references/fullscreen.md) |
+| Select/install providers, publisher accounts, mappings, diagnostics | [references/mediation.md](references/mediation.md), [references/dependencies.md](references/dependencies.md) |
+| Replace legacy modules or internal builds | [references/migration.md](references/migration.md) |
+| Unsupported formats, extending providers, license/distribution | [references/roadmap.md](references/roadmap.md), [references/contributing.md](references/contributing.md), [references/third-party-notices.md](references/third-party-notices.md) |
+| Game experience and frequency decisions | [references/game-monetization.md](references/game-monetization.md), plus fullscreen/privacy |
+
+Cite factual guidance with `[source: references/<file>.md]`. If the relevant source is unavailable, mark the claim `FROM_MEMORY (unverified):` and do not invent a method or provider setting.
+
+## Integration invariants
+
+- Inspect `tiapp.xml`, installed artifacts, project type and existing ad owner before adding another boundary. Use `ti-guides`/`ti-howtos`, Alloy or UI skills as applicable.
+- Prefer the official copy-ready `assets/example/lib/ads.js`: copy unchanged to Alloy `app/lib/ads.js` or Classic `Resources/lib/ads.js`. Its documentation imports `require('lib/ads')`; preserve its path and provenance. `assets/example/library-usage.js` and `assets/example/app.js` are official integration evidence, not navigation templates to paste wholesale.
+- Follow the documented UMP → request eligibility → initialization sequence. `canRequestAds()` is the gate, not ATT status or a guessed personalization flag. Resolve requested ATT separately; do not request it without an actual use case. Preserve privacy options and named-listener cleanup.
+- Application IDs and ad-unit IDs are different. Use documented test IDs during development; do not switch to production IDs as an incidental fix.
+- Native activity/app lifecycle and SDK banner refresh belong to the module/Google. The app owns tab/window coverage and reserved layout. Do not add refresh timers or duplicate background handlers for banners.
+- Separate loading from deliberate fullscreen presentation. Do not show from a load callback. Coordinate game clock/audio/inputs and ad ownership; handle no-fill, failed presentation, actual close and destroyed screens without repeated ads or late navigation.
+- Install only selected mediation complements on each target platform. All application calls use `ti.admob.unified`. Configure provider accounts and AdMob mappings; neither a packaged adapter nor `ready` diagnostics nor a Google test ad proves provider delivery. Do not invent placeholder keys, manual provider initializers or an `enableMediation` option.
+- Consult the roadmap before suggesting native ads, rewarded interstitial or a network outside the distributed set. Supporting several formats does not justify enabling all of them in a game.
+
+## Acceptance
+
+Report separately: source/contract review, configuration/build/linking, Google test-ad behavior, each selected provider's own test delivery, and physical-device lifecycle/layout/visual acceptance. Use Ad Inspector as documented and re-check current Google/provider setup guidance before live configuration. A reported impression or passing stand-in test does not certify visible creative content or consent propagation. Do not click production ads to test delivery. No account creation, credentials, live ad activation or publishing is implied by ordinary integration work.
+
+For games, use `ti-game` for native pause/cleanup and `ti-game-assets` for audiovisual assets. Respect the existing game's presentation policy; defaults and quotas are product choices to measure, not optimal values certified by this module.

package/skills/ti-admob-unified/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Ti AdMob Unified"
+  short_description: "Configure ads, privacy and mediation in Titanium"
+  default_prompt: "Use $ti-admob-unified to integrate ads and configure the selected mediation providers for my Titanium app."