@maccesar/titools 4.23.0 → 5.0.0

package/README.md

@@ -191,7 +191,7 @@ Notes:
 - `ti-reuse-first` runs before the others. It asks whether a thing needs to exist and what already does it — a search order that stops at the first rung that holds — and sweeps an existing `app/` for near-identical controllers, single-listener events, wrappers around one call, and layout recomputed in JavaScript. It is deliberately two-sided: it says when adding a module or a Widget is the right answer, so the bias does not simply invert.
 - `ti-game` documents the `ti.game` native module (2D sprite engine on OpenGL ES 2.0, Android and iOS). Its API reference was verified against the module source and tracks upstream `main` (the module ships features ahead of its manifest version); it applies to Alloy and Classic projects alike and does not depend on PurgeTSS.
 - `ti-synthengine` translates aesthetic sound requests into strict, production-ready JavaScript for the cross-platform `ti.synthengine` 1.0.0 module. Seven references preserve the official documentation and an eighth adds curated retro, xylophone, memory-pad, polyphony and timer-ownership recipes; the API contract was cross-checked against both native implementations.
-- The latter five are documentation-mirror skills sourced from the official Titanium SDK docs (`tidev/titanium-docs`) and audited against them via the internal `titools-skill-auditor`.
+- The latter five are documentation-mirror skills, audited via the internal `titools-skill-auditor` against three sources: `ti-api` against the API definitions in `tidev/titanium-sdk` (`apidoc/`, anchored to the newest GA tag), the guide skills against the rewritten guides in `tidev/titaniumsdk.com` (`content/docs/`), and both against the frozen `tidev/titanium-docs` corpus as an archive. The archive is additive: TiDev condensed 336 legacy pages into 62, and the material it left behind is kept here rather than deleted.
 - `purgetss` reference files are audited against the official PurgeTSS documentation, but its workflow conventions are opinionated.
 
 ---

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@maccesar/titools",
-  "version": "4.23.0",
+  "version": "5.0.0",
   "description": "Titanium SDK skills and agents for AI coding assistants, including native game and sound synthesis modules",
   "main": "lib/index.js",
   "type": "module",

package/skills/alloy-guides/references/MODELS.md

@@ -291,7 +291,7 @@ In Alloy, collection data can be synchronized to a view object, or a single mode
 
 #### Collection-View Binding
 
-To enable collection-view binding, create a global singleton or controller-specific collection using the [Collection tag](https://titaniumsdk.com/guide/Alloy_Framework/Alloy_Guide/Alloy_Views/Alloy_XML_Markup.html#collection-element) in the XML markup of the main view, then add the view object you want to bind data to. The following Titanium view objects support binding to a Collection:
+To enable collection-view binding, create a global singleton or controller-specific collection using the [Collection tag](https://titaniumsdk.com/docs/alloy/views) in the XML markup of the main view, then add the view object you want to bind data to. The following Titanium view objects support binding to a Collection:
 
 | View Object    | Since Alloy version | Add data binding attributes to...              | Repeater Object to map model attributes to view properties                     |
 | -------------- | ------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------ |
@@ -416,7 +416,7 @@ The application is now setup for basic collection-view binding. When any new dat
 
 #### Model-View Binding
 
-To bind a single model to a component, create a global singleton or controller-specific model using the [Model tag](https://titaniumsdk.com/guide/Alloy_Framework/Alloy_Guide/Alloy_Views/Alloy_XML_Markup.html#model-element) in the XML markup of the main view and map the model attribute to the view component. To map the attribute to the view component, prefix the model name or id to the attribute, then enclose it with curly brackets or braces ('{' and '}').
+To bind a single model to a component, create a global singleton or controller-specific model using the [Model tag](https://titaniumsdk.com/docs/alloy/views) in the XML markup of the main view and map the model attribute to the view component. To map the attribute to the view component, prefix the model name or id to the attribute, then enclose it with curly brackets or braces ('{' and '}').
 
 To do complex transformations on the model attributes, extend the model prototype with a `transform()` function. It should return the modified model as a JSON object.
 

package/skills/alloy-guides/references/MODELS_ADVANCED.md

@@ -33,7 +33,7 @@ In Alloy, a sync adapter allows you to store and load your models to a persisten
 
 #### Backbone Sync
 
-Backbone syncs your models to persistent storage devices based on the implementation of the [Backbone.sync method](https://titaniumsdk.com/guide/Alloy_Framework/Alloy_Guide/Alloy_Models/Alloy_Sync_Adapters_and_Migrations.html). Since Backbone's primary use is for web applications, by default, the Backbone.sync method executes RESTful JSON requests to a URL specified by the Model.urlRoot or Collection.url attribute, when these classes are created.
+Backbone syncs your models to persistent storage devices based on the implementation of the [Backbone.sync method](https://titaniumsdk.com/docs/alloy/models). Since Backbone's primary use is for web applications, by default, the Backbone.sync method executes RESTful JSON requests to a URL specified by the Model.urlRoot or Collection.url attribute, when these classes are created.
 
 Models are accessed from persistent storage based on the `id` attribute. To override this, set the `idAttribute` property of the model. The `cid` (client ID) is a special property of models that is automatically assigned when they are first created. Client IDs are useful when the model has not yet been saved to the server and does not have its real `id` yet.
 

package/skills/alloy-guides/references/VIEWS_XML.md

@@ -584,16 +584,16 @@ If you have a collection of model data that needs to be automatically updated to
 
 Some Titanium view elements use special syntax. Refer to the **Alloy XML Markup** examples in the Titanium API Guides site for the following view objects:
 
-* [AlertDialog](https://titaniumsdk.com/api/titanium/ui/alertdialog.html)
-* [ButtonBar](https://titaniumsdk.com/api/titanium/ui/buttonbar.html)
-* [CoverFlowView](https://titaniumsdk.com/api/titanium/ui/ios/coverflowview.html)
-* [DashboardView](https://titaniumsdk.com/api/titanium/ui/dashboardview.html)
-* [ListView](https://titaniumsdk.com/api/titanium/ui/listview.html)
-* [Map](https://titaniumsdk.com/api/modules/map.html)
-* [Menu](https://titaniumsdk.com/api/titanium/android/menu.html)
-* [OptionBar](https://titaniumsdk.com/api/titanium/ui/optionbar.html)
-* [OptionDialog](https://titaniumsdk.com/api/titanium/ui/optiondialog.html)
-* [Picker](https://titaniumsdk.com/api/titanium/ui/picker.html)
-* [SplitWindow](https://titaniumsdk.com/api/titanium/ui/ios/splitwindow.html)
-* [TabbedBar](https://titaniumsdk.com/api/titanium/ui/ios/tabbedbar.html)
-* [Toolbar](https://titaniumsdk.com/api/titanium/ui/toolbar.html)
+* [AlertDialog](https://titaniumsdk.com/docs/sdk/Titanium.UI.AlertDialog)
+* [ButtonBar](https://titaniumsdk.com/docs/sdk/Titanium.UI.ButtonBar)
+* [CoverFlowView](https://titaniumsdk.com/docs/sdk/Titanium.UI.iOS.CoverFlowView)
+* [DashboardView](https://titaniumsdk.com/docs/sdk/Titanium.UI.DashboardView)
+* [ListView](https://titaniumsdk.com/docs/sdk/Titanium.UI.ListView)
+* [Map](https://titaniumsdk.com/modules/ti.map)
+* [Menu](https://titaniumsdk.com/docs/sdk/Titanium.Android.Menu)
+* [OptionBar](https://titaniumsdk.com/docs/sdk/Titanium.UI.OptionBar)
+* [OptionDialog](https://titaniumsdk.com/docs/sdk/Titanium.UI.OptionDialog)
+* [Picker](https://titaniumsdk.com/docs/sdk/Titanium.UI.Picker)
+* [SplitWindow](https://titaniumsdk.com/docs/sdk/Titanium.UI.iOS.SplitWindow)
+* [TabbedBar](https://titaniumsdk.com/docs/sdk/Titanium.UI.iOS.TabbedBar)
+* [Toolbar](https://titaniumsdk.com/docs/sdk/Titanium.UI.Toolbar)

package/skills/alloy-howtos/references/best_practices.md

@@ -1,6 +1,6 @@
 # Alloy best practices and recommendations
 
-Recommendations for writing Alloy apps. This supplements the Titanium SDK [Best Practices and Recommendations](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_Guide/Best_Practices_and_Recommendations/) guide and focuses on coding style and conventions.
+Recommendations for writing Alloy apps. This supplements the Titanium SDK [Best Practices and Recommendations](https://titaniumsdk.com/docs/build) guide and focuses on coding style and conventions.
 
 ## Titanium-to-Alloy Guidance
 
@@ -29,7 +29,7 @@ Decide whether to adapt Alloy to your existing structure, or to adopt Alloy's st
 ### Naming Conventions
 
 - **Do not use double underscore prefixes** on variables, properties, or function names (e.g., `__foo`). They are reserved for Alloy and may cause conflicts and unexpected behavior.
-- **Do not use JavaScript reserved words as IDs.** See [Titanium SDK Reserved Words](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_Guide/Best_Practices_and_Recommendations/Reserved_Words/) for the complete list.
+- **Do not use JavaScript reserved words as IDs.** See [Titanium SDK Reserved Words](https://titaniumsdk.com/docs/buildReserved_Words/) for the complete list.
 
 ### Global Variables
 

package/skills/alloy-howtos/references/cli_reference.md

@@ -123,7 +123,7 @@ Compiler options reference the `event.alloyConfig` object in [Build Configuratio
 
 ### run
 
-Use `titanium build` command to run Alloy projects. See [Titanium Command-Line Interface Reference](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_Guide/Titanium_Command-Line_Interface_Reference/).
+Use `titanium build` command to run Alloy projects. See [Titanium Command-Line Interface Reference](https://titaniumsdk.com/docs/reference/cli).
 
 > **💡 Common ti build pitfalls**
 >

package/skills/alloy-howtos/references/debugging_troubleshooting.md

@@ -75,4 +75,4 @@ Search [existing issues](https://github.com/tidev/alloy/issues) first to avoid d
 - Include Alloy version (`alloy --version`)
 - Include environment information
 
-For detailed instructions, see [How to Report a Bug or Make a Feature Request](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_Guide/Contributing_to_Titanium/How_to_Report_a_Bug_or_Make_a_Feature_Request/).
+For detailed instructions, see [How to Report a Bug or Make a Feature Request](https://titaniumsdk.com/contribute).

package/skills/purgetss/references/classic-projects.md

@@ -64,7 +64,7 @@ Titanium resolves local CommonJS paths from `Resources/`. Omit both the `Resourc
 | `Resources/lib/materialsymbols.js` | `require('lib/materialsymbols')` |
 | `Resources/lib/framework7icons.js` | `require('lib/framework7icons')` |
 
-This follows Titanium's [CommonJS module path resolution](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_Guide/Best_Practices_and_Recommendations/CommonJS_Modules_in_Titanium.html#javascript-module-path-resolution).
+This follows Titanium's [CommonJS module path resolution](https://titaniumsdk.com/docs/build/modules).
 
 ## Deployment Targets
 

package/skills/ti-api/references/api-data-network.md

@@ -107,7 +107,7 @@ On the iOS platform, closing the database also closes the result set, that is, y
 > Platforms: both
 > Type: module
 
-For examples of using the Filesystem APIs, refer to the [Filesystem Access and Storage guide](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_How-tos/Working_with_Local_Data_Sources/Filesystem_Access_and_Storage.html) as well as the other Filesystem submodule API documentation.
+For examples of using the Filesystem APIs, refer to the [Filesystem Access and Storage guide](https://titaniumsdk.com/docs/build/data) as well as the other Filesystem submodule API documentation.
 
 ### Properties (unique: 11/21)
 | Property | Type | Default | Platform | Description |

package/skills/ti-api/references/api-media.md

@@ -21,7 +21,7 @@
 > Platforms: both
 > Type: module
 
-The Media module is used to access the device's media-related functionality, such as using the device's camera and photo gallery, playing media files, or recording audio or video. For examples of using the Media APIs, refer to the [Working with Media APIs guide](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_How-tos/Working_with_Media_APIs/) in addition to the other media submodule API documentation. **Note**: Some third party Android camera apps may choose to ignore video recording quality settings. If you wish to specifically set the video quality, don't assume `EXTRA_VIDEO_QUALITY` intent will be respected by the camera app and use Titanium's built-in camera window which can be used to assign the `overlay` property when calling the `showCamera()` method.
+The Media module is used to access the device's media-related functionality, such as using the device's camera and photo gallery, playing media files, or recording audio or video. For examples of using the Media APIs, refer to the [Working with Media APIs guide](https://titaniumsdk.com/docs/build/media) in addition to the other media submodule API documentation. **Note**: Some third party Android camera apps may choose to ignore video recording quality settings. If you wish to specifically set the video quality, don't assume `EXTRA_VIDEO_QUALITY` intent will be respected by the camera app and use Titanium's built-in camera window which can be used to assign the `overlay` property when calling the `showCamera()` method.
 
 ### Properties (unique: 28/178)
 | Property | Type | Default | Platform | Description |

package/skills/ti-api/references/api-services.md

@@ -108,15 +108,18 @@ to request runtime permissions.
 
 The API supports retrieving information about the attendee of an event.
 
-### Properties (unique: 6/8)
+The type declares `platforms: [iphone, ipad, macos]`, but four of its properties declare Android as well. Read the per-property column, not the type header.
+
+### Properties (unique: 7/9)
 | Property | Type | Default | Platform | Description |
 |----------|------|---------|----------|-------------|
 | isOrganizer | Boolean | — | ios | Indicates whether this attendee is the event organizer. |
-| name | String | — | ios | The attendee name. |
-| email | String | — | ios | The attendee email. |
+| name | String | — | both | The attendee name. |
+| email | String | — | both | The attendee email. |
+| relationship | Number | — | android | The relationship of the attendee to the user. Read-only. Values come from the `Ti.Calendar.RELATIONSHIP_*` constants. Since 6.2.0. |
 | role | Number | — | ios | The role of the attendee. |
-| type | Number | — | ios | The type of the attendee. |
-| status | Number | — | ios | The status of the attendee. |
+| type | Number | — | both | The type of the attendee. |
+| status | Number | — | both | The status of the attendee. |
 
 
 

package/skills/ti-api/references/api-ui-lists.md

@@ -336,7 +336,7 @@ A `TableView` object is a container for [TableViewSection](Titanium.UI.TableView
 
 Use the <Titanium.UI.createTableView> method or **`<TableView>`** Alloy element to create a `TableView`.
 
-Also see the [TableViews guide](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_How-tos/User_Interface_Deep_Dives/TableViews.html).
+Also see the [TableViews guide](https://titaniumsdk.com/docs/build/ui/lists).
 
 ### Creating Tables
 
@@ -564,12 +564,13 @@ Rows may be created using the properties directly available on the `TableViewRow
 
 
 
-### Events (4)
+### Events (5)
 | Event | Platform | Description |
 |-------|----------|-------------|
 | click | both | Fired when a table row is clicked by the user. |
 | touchcancel | ios | Fired when a touch gesture is interrupted by the device. |
 | touchend | ios | Fired when a touch gesture is complete. |
+| touchmove | ios | Fired as soon as the device detects movement of a touch. A row touch event and a table `scroll` event cannot occur concurrently: if the table begins to scroll during a touch, `touchcancel` fires before `scroll` begins. |
 | touchstart | ios | Fired as soon as the device detects a touch gesture against this view. |
 
 ### Related Types

package/skills/ti-api/references/api-ui-text-input.md

@@ -337,7 +337,7 @@ The AttributedString proxy is created with the <Titanium.UI.createAttributedStri
 
 The `text` property must be set initially in the constructor when creating an attributed string. The [attributes](Titanium.UI.AttributedString.attributes) can either be set in the constructor or after it has been created.
 
-For examples of Attributed Strings, see the [Attributed Strings guide](https://titaniumsdk.com/guide/Titanium_SDK/Titanium_SDK_How-tos/User_Interface_Deep_Dives/Attributed_Strings.html).
+For examples of Attributed Strings, see the [Attributed Strings guide](https://titaniumsdk.com/docs/build/ui).
 
 ### Properties (unique: 2/5)
 | Property | Type | Default | Platform | Description |

package/skills/ti-expert/references/feedback-surfaces.md

@@ -102,7 +102,7 @@ Standardize buttons, cards, badges, chips, skeletons, and coach marks only when
 
 ## References
 
-- [Titanium Alloy Widgets](https://titaniumsdk.com/guide/Alloy_Framework/Alloy_Guide/Alloy_Widgets.html)
+- [Titanium Alloy Widgets](https://titaniumsdk.com/docs/alloy/widgets)
 - [Apple Human Interface Guidelines: Alerts](https://developer.apple.com/design/human-interface-guidelines/alerts)
 - [Apple Human Interface Guidelines: Modality](https://developer.apple.com/design/human-interface-guidelines/modality)
 - [Material Design 3: Snackbar](https://m3.material.io/components/snackbar/overview)

package/skills/ti-expert/references/push-notifications.md

@@ -79,6 +79,26 @@ if (OS_ANDROID) {
 
 **Wrap the listeners.** `Ti.App.addEventListener('resumed', mostrarAviso)` passes the event object as the first argument, and if the function's first parameter is an Intent, the code blows up inside `getStringExtra`. The same trap catches `Alloy.Events.on('algo', unaFuncionConParametros)`.
 
+### Registering on Android: two calls that go quiet
+
+The channel has to exist and be handed to the module **before** asking for the token, and its id has to match the `default_notification_channel_id` meta-data in `tiapp.xml`. Mismatch them and the notification is posted against a channel nobody declared.
+
+```javascript
+modulo.notificationChannel = Ti.Android.NotificationManager.createNotificationChannel({
+  id: 'default_channel',        // the same id tiapp.xml declares
+  name: L('push_channel_name'),
+  importance: Ti.Android.IMPORTANCE_DEFAULT
+})
+
+modulo.registerForPushNotifications()
+
+// Firebase does not announce a token it already had, so didRefreshRegistrationToken
+// may never fire on a device that registered before. Ask for it once, a moment later.
+setTimeout(() => guardarToken(modulo.fcmToken), 4000)
+```
+
+That last line is the one that bites. On a fresh install the event fires and everything looks fine; on a device that already had a token from an earlier run it never fires, the app never sends the token to the server, and every push to that device is addressed to nobody. Make `guardarToken` idempotent — it will be called more than once with the same value.
+
 ## 2. The payload decides how much of the module runs
 
 Android distinguishes a *notification message* from a *data message*, and the difference is not cosmetic.
@@ -151,11 +171,34 @@ Everything above is what the published module needs. A module that fires `didOpe
 Verified on a physical Android 15 phone and an API 35 emulator, each row confirmed by a log line naming the route. The first three ran back to back on one process id with a game in progress, which survived; only the fourth starts a new process.
 
 ```javascript
-modulo.addEventListener('didOpenNotification', (e) => {
-  abrirPanel((e.message && e.message.data) || {})
-})
+if (OS_ANDROID) {
+  // With the runtime alive the launcher Intent is not delivered a second time,
+  // so this event is the only way in.
+  modulo.addEventListener('didOpenNotification', (e) => {
+    abrirPanel((e.message && e.message.data) || {})
+  })
+
+  // On a cold start the module does not exist yet when the notification is
+  // opened, so the payload travels in the Intent. This is that route.
+  const desdeElIntent = (origen) => {
+    const contenido = Ti.Android.rootActivity.intent.getStringExtra('fcm_data')
+
+    if (!contenido) {
+      log.debug(`Nothing in the Intent (${origen})`)
+      return
+    }
+
+    modulo.clearLastData()
+    abrirPanel(JSON.parse(contenido))
+  }
+
+  Ti.App.addEventListener('resumed', () => desdeElIntent('resumed'))
+  desdeElIntent('arranque')
+}
 ```
 
+`resumed` stays even though the event covers the warm tap: it is what catches an Intent the module left behind on a version that still writes one. When the event delivered the payload the Intent is empty and the handler returns without opening anything, which is the exclusivity the section below describes.
+
 The payload sits under `message.data`, the same place `didReceiveMessage` puts it on both its live and its cold-start path, so one accessor covers a tap and an arrival. The first version of the event wrapped it directly in `message`; if the module you have predates 3.6.0, read `e.message` instead, or log the event once and look.
 
 The Intent is still how a cold start arrives, so keep that path. Check `timodule.xml` in your installed module for the event, or just add the listener and watch whether it fires: a module without it ignores the registration silently.
@@ -249,7 +292,15 @@ Verified case by case on an iPad. The third row is the one that does not work on
 
 ```javascript
 Ti.Network.registerForPushNotifications({
-  success: (e) => { enviarTokenAlServidor(e.deviceToken) },
+  success: (e) => {
+    // e.deviceToken is the APNs one. It is not what you send to a server that
+    // pushes through FCM, and Firebase picks it up on its own — see below.
+    log.info(`APNs token: ${e.deviceToken ? 'received' : 'EMPTY'}`)
+
+    modulo.fetchToken((r) => {
+      if (r && r.token) { guardarToken(r.token) }
+    })
+  },
   error: (e) => { log.error(e.error) },
   callback: (e) => {
     // Foreground, background and closed all arrive here.
@@ -274,6 +325,16 @@ if (OS_IOS) {
 }
 ```
 
+**The token comes from `fetchToken`, not from the property.** Right after APNs answers, `modulo.fcmToken` is empty: Firebase still has to exchange the APNs token for its own, and that exchange has no fixed duration. Waiting does not fix it — four seconds was still empty on a device. `fetchToken` calls back when the token exists, which is the only way to know.
+
+```javascript
+// The apnsToken is never assigned by hand. Firebase's swizzling does it, and
+// setting it yourself produces BadDeviceToken when you send.
+modulo.fetchToken((e) => {
+  if (e && e.token) { guardarToken(e.token) }
+})
+```
+
 **A data-only message shows nothing on iOS.** Android reads the text from `data`; iOS reads it from the APNs alert. Send both, they do not interfere:
 
 ```php
@@ -323,3 +384,6 @@ Do not test with the app added to the battery whitelist. That measures a phone y
 | iOS registers but never gets a token | Firebase loaded after APNs answered | Section 8 |
 | iOS receives the push and does nothing when tapped | Empty `callback` | Section 8 |
 | Nothing arrives for twenty minutes, then five at once | OEM battery management | Section 9 |
+| Push works on a fresh install and never on a reinstall | `didRefreshRegistrationToken` does not fire for a token Firebase already had | Section 1 |
+| iOS: `fcmToken` is empty right after the permission is granted | It is; the APNs-for-FCM exchange has no fixed duration. Use `fetchToken` | Section 8 |
+| iOS: `BadDeviceToken` when sending | `apnsToken` was assigned by hand instead of leaving it to the swizzling | Section 8 |

package/skills/ti-guides/references/resources.md

@@ -19,7 +19,7 @@ Community resources, support channels, tools, and learning materials for Titaniu
 ### Documentation
 
 - Titanium SDK Docs: https://titaniumsdk.com/
-- Alloy Framework Docs: https://titaniumsdk.com/guide/Alloy_Framework/
+- Alloy Framework Docs: https://titaniumsdk.com/docs/alloy
 - This skill (`ti-guides`): `../SKILL.md`
 
 ---

package/skills/ti-guides/references/sdk-release-notes.md

@@ -8,11 +8,12 @@ Each GA release desupports the previous patch release. Running an unsupported ve
 ## Contents
 
 - [1. Version timeline](#1-version-timeline)
-- [2. 13.4.0 — Android target SDK 36 groundwork](#2-1340--android-target-sdk-36-groundwork)
-- [3. 13.3.1 — patch](#3-1331--patch)
-- [4. 13.3.0 — Xcode 27, iOS 27, multi-scene](#4-1330--xcode-27-ios-27-multi-scene)
-- [5. 13.2.0 — ViewPager2, keepHardwareMode](#5-1320--viewpager2-keephardwaremode)
-- [6. Bundled module versions](#6-bundled-module-versions)
+- [2. 13.4.1 — patch](#2-1341--patch)
+- [3. 13.4.0 — Android target SDK 36 groundwork](#3-1340--android-target-sdk-36-groundwork)
+- [4. 13.3.1 — patch](#4-1331--patch)
+- [5. 13.3.0 — Xcode 27, iOS 27, multi-scene](#5-1330--xcode-27-ios-27-multi-scene)
+- [6. 13.2.0 — ViewPager2, keepHardwareMode](#6-1320--viewpager2-keephardwaremode)
+- [7. Bundled module versions](#7-bundled-module-versions)
 
 <!-- TOC-END -->
 
@@ -20,6 +21,7 @@ Each GA release desupports the previous patch release. Running an unsupported ve
 
 | Version | Date | Headline |
 |---|---|---|
+| 13.4.1.GA | 25 August 2026 | Patch — BottomNavigation keyboard and androidback (Android), window-open deadlock (iOS) |
 | 13.4.0.GA | 28 July 2026 | Prepares the SDK for Android target SDK 36; v8 memory cleanup |
 | 13.3.1.GA | 20 July 2026 | Patch — iOS restart and LiveView fixes |
 | 13.3.0.GA | 01 July 2026 | Xcode 27 and iOS 27, Hyperloop 8.0.0, iOS multi-scene apps |
@@ -27,7 +29,16 @@ Each GA release desupports the previous patch release. Running an unsupported ve
 | 13.1.0.GA | — | Minor release, high-priority fixes |
 | 13.0.0.GA | — | Major release: iOS 26 / Xcode 26, Android 16 KB page size |
 
-## 2. 13.4.0 — Android target SDK 36 groundwork
+## 2. 13.4.1 — patch
+
+Released 25 August 2026. Two fixes, both to crashes and input handling rather than to any API:
+
+- **Android:** keyboard issues in `BottomNavigation`, and the `androidback` event.
+- **iOS:** a possible deadlock when opening a window.
+
+Desupports 13.4.0. No API surface changed, so code written against 13.4.0 needs no edit.
+
+## 3. 13.4.0 — Android target SDK 36 groundwork
 
 - **Prepares the SDK for Android target SDK 36.** Groundwork only; the compatibility matrix still lists API 35 as the maximum target. See [compatibility-matrix.md](compatibility-matrix.md) § Android.
 - v8 memory cleanup (Android).
@@ -36,11 +47,11 @@ Each GA release desupports the previous patch release. Running an unsupported ve
 - iOS: fixed the dimming area in a TableView SearchBar.
 - The debug-only selector for `Ti.App._restart()` was removed, making the method callable outside debug builds.
 
-## 3. 13.3.1 — patch
+## 4. 13.3.1 — patch
 
 iOS-only fixes: the `restart` method, and LiveView restart. Hyperloop bumped to 8.0.1.
 
-## 4. 13.3.0 — Xcode 27, iOS 27, multi-scene
+## 5. 13.3.0 — Xcode 27, iOS 27, multi-scene
 
 - **Xcode 27 and iOS 27 support.** This postdates the Xcode/iOS rows in the compatibility matrix, which still cap at Xcode 16.x.
 - **iOS multi-scene applications** are supported.
@@ -51,7 +62,7 @@ iOS-only fixes: the `restart` method, and LiveView restart. Hyperloop bumped to
 - `borderWidth` no longer renders at double thickness when `borderRadius` is an array (iOS).
 - Android: Material 3 BottomNavigation theme and dark/light switching fixes, CameraX rotation fix under orientation lock, WebView fix for URLs carrying large GET data, `Ti.Preferences` optimized.
 
-## 5. 13.2.0 — ViewPager2, keepHardwareMode
+## 6. 13.2.0 — ViewPager2, keepHardwareMode
 
 - **ScrollableView moved to ViewPager2 on Android.** A backing-widget swap; verify paging, nested scrolling and any custom paging control against it.
 - **`keepHardwareMode` added to `Ti.UI.View`** (Android) — controls the view's render mode.
@@ -63,7 +74,7 @@ iOS-only fixes: the `restart` method, and LiveView restart. Hyperloop bumped to
 - Node.js 24 support; core-js upgraded, removing the `baseline-browser-mapping` warning.
 - iOS: Mac Catalyst fixes for `Ti.UI.Button` styling and events, and module builds with `mac=true`.
 
-## 6. Bundled module versions
+## 7. Bundled module versions
 
 Versions shipped with each SDK. Unchanged rows are omitted.
 
@@ -72,4 +83,4 @@ Versions shipped with each SDK. Unchanged rows are omitted.
 | facebook | 14.0.0 / 15.0.0 | 15.0.0 / 16.0.0 |
 | hyperloop | 7.1.0 / 7.1.0 | 8.0.1 / 8.0.1 (8.0.0 in 13.3.0) |
 
-Stable across 13.2.0–13.4.0: `ti.map` 5.7.0 / 7.3.1, `ti.webdialog` 2.5.0 / 3.0.2, `ti.playservices` 18.6.0 (Android only), `ti.identity` 3.2.0 / 5.0.0, `urlSession` 4.0.1 (iOS only), `ti.coremotion` 4.0.1 (iOS only), `ti.applesignin` 3.1.2 (iOS only).
+Stable across 13.2.0–13.4.1: `ti.map` 5.7.0 / 7.3.1, `ti.webdialog` 2.5.0 / 3.0.2, `ti.playservices` 18.6.0 (Android only), `ti.identity` 3.2.0 / 5.0.0, `urlSession` 4.0.1 (iOS only), `ti.coremotion` 4.0.1 (iOS only), `ti.applesignin` 3.1.2 (iOS only).

package/skills/ti-howtos/references/extending-titanium.md

@@ -8,6 +8,7 @@
 - [3. Upgrading to SDK 9.0.0+ (Android)](#3-upgrading-to-sdk-900-android)
 - [4. Hyperloop](#4-hyperloop)
 - [3. Native module development](#3-native-module-development)
+  - [Swift Package Manager dependencies (iOS)](#swift-package-manager-dependencies-ios)
 - [4. Choosing between Hyperloop and native modules](#4-choosing-between-hyperloop-and-native-modules)
 - [5. Finding and using third-party modules](#5-finding-and-using-third-party-modules)
 - [Best practices summary](#best-practices-summary)
@@ -601,6 +602,82 @@ View proxies (custom UI components):
 @end
 ```
 
+### Swift Package Manager dependencies (iOS)
+
+Since Titanium SDK 13.1.0, an iOS module declares Swift package dependencies in an `spm.json` file and the CLI wires them into the consuming app. This replaces vendoring pre-built `.xcframework` files in `ios/platform` and replaces the legacy `hooks/ti.spm.js` hook.
+
+Add the package to your module's Xcode project as usual so the module compiles against it, then declare the same package in `spm.json`, next to the module `manifest`:
+
+```
+mymodule/
+└── ios/
+    ├── manifest
+    ├── spm.json
+    ├── MyModule.xcodeproj
+    └── Classes/
+```
+
+```json
+{
+  "dependencies": [
+    {
+      "remotePackageReference": "Parse-SDK-iOS-OSX",
+      "repositoryURL": "https://github.com/parse-community/Parse-SDK-iOS-OSX",
+      "requirementKind": "upToNextMajorVersion",
+      "requirementMinimumVersion": "5.1.1",
+      "products": [
+        { "productName": "ParseObjC", "frameworkName": "ParseObjC", "linkage": "host" },
+        { "productName": "ParseLiveQuery", "frameworkName": "ParseLiveQuery", "linkage": "embedded" }
+      ]
+    }
+  ]
+}
+```
+
+#### Dependency fields
+
+| Field | Required | Default | Description |
+|---|---|---|---|
+| `repositoryURL` | yes | — | Git URL of the Swift package. A dependency without it is skipped with a warning. |
+| `remotePackageReference` | no | last path segment of `repositoryURL` | Reference name in the generated Xcode project. |
+| `requirementKind` | no | `upToNextMajorVersion` | Version resolution rule, e.g. `upToNextMajorVersion`, `upToNextMinorVersion`. |
+| `requirementMinimumVersion` | no | `1.0.0` | Minimum package version to resolve. |
+| `linkage` | no | `embedded` | Default linkage for every product of this dependency. |
+| `products` | yes | — | Non-empty array of products to link. A dependency with no valid product is skipped with a warning. |
+
+#### Product fields
+
+| Field | Required | Default | Description |
+|---|---|---|---|
+| `productName` | yes | — | Product name as the Swift package declares it. |
+| `frameworkName` | no | `productName` | Framework name in the Frameworks build phase, when it differs. |
+| `linkage` | no | the dependency's `linkage` | Per-product override: `embedded` or `host`. |
+
+#### embedded vs host
+
+`embedded` bakes the product into the module binary. The module stays self-contained and the app's Xcode project is untouched. Use it for small, module-private dependencies.
+
+`host` makes the CLI add the package to the app's Xcode project at build time, so the dependency exists once in the app. Use it when several modules share the same package, or when the package ships resources or dynamic frameworks the app must embed.
+
+If two modules request the same package, it is added once. If they request conflicting version requirements, the CLI warns and uses the first requirement it sees.
+
+#### Building
+
+```bash
+cd mymodule/ios
+ti build -p ios --build-only
+```
+
+The zip in `dist/` now carries the package information in its `metadata.json`. App developers install the module normally; nothing extra is required of them. During an app build, lines prefixed with `[SPM]` say what was added:
+
+```
+[INFO]  [SPM] Will add 1 Swift package(s) to the app project
+```
+
+#### Migrating off ti.spm.js
+
+A module that ships both `spm.json` and `hooks/ti.spm.js` has the hook excluded from its packaged zip automatically. A module that still ships only the hook makes the app build log a warning. To migrate, translate the hook's package information into `spm.json`, delete `hooks/ti.spm.js`, and rebuild.
+
 ### Module distribution
 
 #### Packaging