@maccesar/titools 5.2.0 → 5.2.2

package/skills/ti-admob-unified/assets/example/library-usage.js

@@ -7,7 +7,7 @@
  */
 
 const Admob = require('ti.admob.unified')
-const ads = require('lib/ads')
+const ads = require('lib/ads') // Classic; Alloy app/lib/ads.js: require('ads')
 
 const win = Ti.UI.createWindow({ layout: 'composite', backgroundColor: '#ffffff' })
 const content = Ti.UI.createScrollView({ top: 0, left: 0, right: 0, bottom: 0 })
@@ -48,6 +48,12 @@ const rewarded = ads.createRewarded({
   onRewarded: event => grantReward(event.rewardAmount, event.rewardType)
 })
 
+const rewardedInterstitial = ads.createRewardedInterstitial({
+  window: win,
+  adUnitId: Admob.TEST_REWARDED_INTERSTITIAL,
+  onRewarded: event => grantReward(event.rewardAmount, event.rewardType)
+})
+
 const appOpen = ads.createAppOpen({
   window: win,
   adUnitId: Admob.TEST_APP_OPEN,
@@ -66,6 +72,23 @@ function onRewardAccepted() {
   rewarded.show()
 }
 
+// In production, rewardDescription must describe the reward configured for
+// this placement. Only onRewarded above credits the actual SDK-earned reward.
+function onRewardedTransition(rewardDescription) {
+  if (!rewardedInterstitial.isLoaded()) return
+  const intro = Ti.UI.createAlertDialog({
+    title: 'Rewarded interstitial',
+    message: `Complete the ad to earn ${rewardDescription}. You can skip it.`,
+    buttonNames: ['Watch ad', 'Skip'], cancel: 1
+  })
+  function onChoice(event) {
+    intro.removeEventListener('click', onChoice)
+    if (event.index === 0) rewardedInterstitial.show()
+  }
+  intro.addEventListener('click', onChoice)
+  intro.show()
+}
+
 function onApplicationResumed() {
   appOpen.show()
 }
@@ -82,8 +105,13 @@ win.addEventListener('close', event => {
 })
 win.open()
 
+// Start in the active foreground. Enable requestTrackingAuthorization only for
+// a real tracking use case with a localized NSUserTrackingUsageDescription.
+// Keep it false when an AdMob UMP IDFA message already handles ATT.
+Ti.API.info('Current ATT state: ' + JSON.stringify(Admob.getTrackingAuthorizationStatus()))
 ads.start({
   consent: { tagForUnderAgeOfConsent: false },
+  requestTrackingAuthorization: false,
   initialization: {}
 }).then(result => {
   if (!result.initialized) {
@@ -92,7 +120,10 @@ ads.start({
 
   interstitial.load()
   rewarded.load()
+  rewardedInterstitial.load()
   appOpen.load()
+}).catch(error => {
+  Ti.API.warn(`[ads] Startup failed: ${error.message || error}`)
 })
 
 // References kept here to make the intended call sites explicit in this
@@ -100,5 +131,6 @@ ads.start({
 void createAdaptiveBanner
 void onNaturalBreak
 void onRewardAccepted
+void onRewardedTransition
 void onApplicationResumed
 void openChildWindow

package/skills/ti-admob-unified/references/api-reference.md

@@ -1,4 +1,4 @@
-> Source snapshot: official ti.admob.unified 1.0.0 documentation at commit `5b4cbf9` (copied 2026-10-11). Relative links rebased for this skill.
+> Source snapshot: official ti.admob.unified 1.0.0 documentation at release source commit `034843299b2984253988e0ffccb9f6a1c91682c9` (copied 2026-10-24). Relative links rebased for this skill.
 
 # API reference
 
@@ -34,6 +34,7 @@ const Admob = require('ti.admob.unified')
 | `isPrivacyOptionsRequired()`               | iOS, Android | Supported                  |
 | `presentPrivacyOptions(config)`            | iOS, Android | Supported                  |
 | `resetConsent()`                           | iOS, Android | Testing only               |
+| `getTrackingAuthorizationStatus()`        | iOS, Android | Read-only ATT snapshot     |
 | `requestTrackingAuthorization()`           | iOS, Android | Portable                   |
 | `openAdInspector()`                        | iOS, Android | Development diagnostic     |
 | `createBanner(config)`                     | iOS, Android | Supported                  |
@@ -41,6 +42,7 @@ const Admob = require('ti.admob.unified')
 | `createAdaptiveBanner(config)`             | iOS, Android | Supported                  |
 | `createInterstitial(config)`               | iOS, Android | Supported                  |
 | `createRewarded(config)`                   | iOS, Android | Supported                  |
+| `createRewardedInterstitial(config)`       | iOS, Android | Supported                  |
 | `createAppOpen(config)`                    | iOS, Android | Supported                  |
 | `setTestDevice(deviceId)`                  | iOS, Android | Compatibility utility      |
 | `isTestDevice()`                           | iOS, Android | Supported                  |
@@ -50,11 +52,11 @@ const Admob = require('ti.admob.unified')
 | `canShowPersonalizedAds()`                 | iOS, Android | Deprecated; always `false` |
 | `isGDPR()`                                 | iOS, Android | Deprecated diagnostic      |
 
-The four legacy mediation entries are described under [Mediation diagnostics and compatibility](#mediation-diagnostics).
+See [Mediation diagnostics](#mediation-diagnostics) for adapter status and the [migration guide](migration.md#generic-mediation-diagnostics) for removed pre-release helpers.
 
 ### `initialize(config)`
 
-Configures global request settings and initializes Google Mobile Ads.
+Sets global request options and initializes Google Mobile Ads.
 
 ```js
 Admob.initialize({
@@ -64,12 +66,14 @@ Admob.initialize({
 })
 ```
 
+On Android, native request configuration and SDK initialization run on a worker thread; completion is delivered on the UI thread. The call returns before adapter initialization finishes. Wait for `module_initialized` before loading ads.
+
 Accepted properties:
 
 | Property                       | Type     | Description                                                                    |
 | ------------------------------ | -------- | ------------------------------------------------------------------------------ |
 | `testDeviceIds`                | String[] | Google Mobile Ads test-device identifiers.                                     |
-| `ageRestrictedTreatment`       | String   | `CHILD`, `TEEN`, or `UNSPECIFIED` constant value.                              |
+| `ageRestrictedTreatment`       | String   | `child`, `teen`, or `unspecified` constant value.                              |
 | `maxAdContentRating`           | String   | `G`, `PG`, `T`, or `MA` constant value.                                        |
 | `tagForChildDirectedTreatment` | Boolean  | Deprecated compatibility input.                                                |
 | `tagForUnderAgeOfConsent`      | Boolean  | Deprecated initialization input, separate from the UMP property.               |
@@ -95,7 +99,7 @@ Use the exception only when adapters are installed but the application deliberat
 Admob.initialize({ disableMediation: true })
 ```
 
-This calls Google’s global initialization switch on [Android](https://developers.google.com/admob/android/reference/com/google/android/gms/ads/MobileAds) and [iOS](https://developers.google.com/admob/ios/api/reference/Classes/GADMobileAds), before SDK startup. It skips adapter initialization globally; it does not remove dependencies, validate credentials, select individual networks or provide an ad-source allowlist. Do not set it in an app that intends to serve mediated ads. The first accepted initialization configuration wins; repeating `initialize()` cannot toggle mediation later in the session.
+This calls Google's global initialization switch on [Android](https://developers.google.com/admob/android/reference/com/google/android/gms/ads/MobileAds) and [iOS](https://developers.google.com/admob/ios/api/reference/Classes/GADMobileAds), before SDK startup. It skips adapter initialization globally; it does not remove dependencies, validate credentials, select individual networks or provide an ad-source allowlist. Do not set it in an app that intends to serve mediated ads. The first accepted initialization configuration wins; repeating `initialize()` cannot toggle mediation later in the session.
 
 `applicationId` and `debugGeography` are not accepted here.
 
@@ -145,6 +149,19 @@ Returns `void` and resets UMP test state and the module's cached consent operati
 
 Use only during controlled consent testing. For a production privacy entry point, call `presentPrivacyOptions()`.
 
+### `getTrackingAuthorizationStatus()`
+
+Returns `{ status: Number, authorized: Boolean, applicable: Boolean }` synchronously. On iOS it reads the current system ATT status on every call: `0` not determined, `1` restricted, `2` denied, `3` authorized. Only status `3` sets `authorized: true`; `applicable` is always `true` on supported iOS versions.
+
+This query never presents a prompt, emits an event, or initializes an SDK. Re-query after returning from Settings to read a changed permission.
+
+On Android it returns `{ status: 3, authorized: true, applicable: false }`. This portable ATT convention does not grant general tracking permission or replace platform privacy requirements or UMP eligibility.
+
+```js
+const tracking = Admob.getTrackingAuthorizationStatus()
+Ti.API.info(`ATT applies: ${tracking.applicable}; status: ${tracking.status}`)
+```
+
 ### `requestTrackingAuthorization()`
 
 Completes the portable tracking-authorization step and emits `tracking_authorization_completed`. On iOS it requests or retrieves App Tracking Transparency authorization. On Android it completes immediately with `applicable: false`, so consumers do not need a platform condition.
@@ -207,11 +224,15 @@ Returns an interstitial proxy with `load()`, `show()`, `isLoaded()`, and termina
 
 Returns a rewarded proxy with `load()`, `show()`, `isLoaded()`, and terminal `destroy()`. Grant rewards only from the `rewarded` event.
 
+### `createRewardedInterstitial(config)`
+
+Returns a rewarded interstitial proxy with the same methods and configuration as Rewarded, using `adType: 'rewarded_interstitial'`. Explain the reward and offer a skip option before showing it. See [Rewarded interstitial ads](rewarded-interstitial.md).
+
 ### `createAppOpen(config)`
 
 Returns an app open proxy with `load()`, `show()`, `isLoaded()`, and terminal `destroy()`. An app open ad expires four hours after loading completes: past that point `isLoaded()` reports `false` and `show()` emits `failed_to_show` with code `1`. See [The four hour window](fullscreen.md#the-four-hour-window).
 
-See [Fullscreen ads](fullscreen.md) for the three factories.
+See [Fullscreen ads](fullscreen.md) for the four factories.
 
 ### `setTestDevice(deviceId)`
 
@@ -259,7 +280,7 @@ The standard and adaptive proxies expose the same methods:
 | `destroyAdViewAndCancelRequest()` | `void`  | Compatibility alias of `destroy()`.                                                                 |
 | `destoyAdViewAndCancelRequest()`  | `void`  | Deprecated misspelled alias.                                                                        |
 
-The host lifecycle, meaning the Android activity and the iOS application entering the background, pauses banners on its own as a cause independent from these calls. Neither cause resumes the other's pause. See [Who pauses a banner](banners.md#who-pauses-a-banner).
+The host lifecycle also pauses banners: the Android activity pauses, or the iOS application enters the background. That pause is independent of these calls. Neither cause resumes the other's pause. See [Who pauses a banner](banners.md#who-pauses-a-banner).
 
 An Android activity recreation caused by a configuration change is non-terminal. The module preserves the proxy, releases the stale native view without emitting `destroyed`, and reloads after Titanium creates the replacement view.
 
@@ -298,6 +319,8 @@ Banner events:
 | `AD_CLOSED`         | `closed`         | Ad overlay closed.                     |
 | `AD_DESTROYED`      | `destroyed`      | Emitted once per proxy.                |
 
+Both banner types include Boolean `isCollapsible` in `loaded`, reporting the SDK's classification of the received ad. It does not report whether the ad is currently expanded or visibly rendered.
+
 Common payload:
 
 ```js
@@ -326,7 +349,7 @@ All seven keys are present on both platforms. `density` converts points to pixel
 
 ## Fullscreen proxy
 
-Interstitial, rewarded and app open proxies expose:
+Interstitial, rewarded, rewarded interstitial and app open proxies expose:
 
 | Method       | Return  | Description                                                                              |
 | ------------ | ------- | ---------------------------------------------------------------------------------------- |
@@ -339,7 +362,7 @@ Loads are serialized: calls while loading, loaded, or showing are ignored. Commo
 
 ### Fullscreen creation properties
 
-All three factories accept:
+All four factories accept:
 
 | Property       | Type     | Default | Notes                                                  |
 | -------------- | -------- | ------- | ------------------------------------------------------ |
@@ -355,7 +378,7 @@ See [Fullscreen events](fullscreen.md#events).
 
 ## Fullscreen configuration changes
 
-The five configuration properties `adUnitId` (String), `autoReload` (Boolean), `keywords` (String[]), `requestAgent` (String) and `extras` (Object) are readable and writable on both platforms. Changes affect the next load and do not replace an already loaded ad. `autoReload` defaults to `false`; targeting is omitted when unset. Extras retain String, Boolean and numeric primitive values. Internal load/presentation state and native SDK delegate methods are not application APIs.
+The five configuration properties `adUnitId` (String), `autoReload` (Boolean), `keywords` (String[]), `requestAgent` (String) and `extras` (Object) are readable and writable on both platforms. Changes to the four request options affect the next load and do not replace an already loaded ad. `autoReload` defaults to `false` and is read live when the shown ad closes; changing it while an ad is loaded or presented changes whether that close starts a reload. It never automatically presents the replacement or retries a failure. Targeting is omitted when unset. Extras retain String, Boolean and numeric primitive values. Internal load/presentation state and native SDK delegate methods are not application APIs.
 
 ## Module events
 
@@ -437,7 +460,7 @@ On iOS, status values are `0` not determined, `1` restricted, `2` denied, and `3
 | `AD_TYPE_BANNER`                | `"banner"`                | Implemented    |
 | `AD_TYPE_INTERSTITIAL`          | `"interstitial"`          | Implemented    |
 | `AD_TYPE_REWARDED`              | `"rewarded"`              | Implemented    |
-| `AD_TYPE_REWARDED_INTERSTITIAL` | `"rewarded_interstitial"` | No factory     |
+| `AD_TYPE_REWARDED_INTERSTITIAL` | `"rewarded_interstitial"` | Implemented |
 | `AD_TYPE_APP_OPEN`              | `"app_open"`              | Implemented    |
 | `AD_TYPE_NATIVE`                | `"native"`                | No factory     |
 
@@ -472,7 +495,7 @@ The module exports no `COLLAPSIBLE_TOP` or `COLLAPSIBLE_BOTTOM` constant. Pass G
 | `AD_SHOWED_FULLSCREEN_CONTENT` | `"showed_fullscreen_content"` |
 | `AD_DESTROYED`                 | `"destroyed"`                 |
 
-All three fullscreen proxy types (interstitial, rewarded and app open) emit `AD_SHOWED_FULLSCREEN_CONTENT` and `AD_OPENED` on iOS and Android.
+All four fullscreen proxy types (interstitial, rewarded, rewarded interstitial and app open) emit `AD_SHOWED_FULLSCREEN_CONTENT` and `AD_OPENED` on iOS and Android.
 
 ### Consent status
 
@@ -538,13 +561,13 @@ The constant names are portable; their string values are platform-specific:
 | `TEST_INTERSTITIAL`          | `ca-app-pub-3940256099942544/4411468910` | `ca-app-pub-3940256099942544/1033173712` | Interstitial                 | `createInterstitial()`   |
 | `TEST_INTERSTITIAL_VIDEO`    | `ca-app-pub-3940256099942544/5135589807` | `ca-app-pub-3940256099942544/8691691433` | Interstitial, video creative | `createInterstitial()`   |
 | `TEST_REWARDED`              | `ca-app-pub-3940256099942544/1712485313` | `ca-app-pub-3940256099942544/5224354917` | Rewarded                     | `createRewarded()`       |
-| `TEST_REWARDED_INTERSTITIAL` | `ca-app-pub-3940256099942544/6978759866` | `ca-app-pub-3940256099942544/5354046379` | Rewarded interstitial        | None. Reserved           |
+| `TEST_REWARDED_INTERSTITIAL` | `ca-app-pub-3940256099942544/6978759866` | `ca-app-pub-3940256099942544/5354046379` | Rewarded interstitial        | `createRewardedInterstitial()` |
 | `TEST_NATIVE`                | `ca-app-pub-3940256099942544/3986624511` | `ca-app-pub-3940256099942544/2247696110` | Native                       | None. Reserved           |
 | `TEST_APP_OPEN`              | `ca-app-pub-3940256099942544/5575463023` | `ca-app-pub-3940256099942544/9257395921` | App open                     | `createAppOpen()`        |
 
 Use the constant in shared code so it selects the platform value.
 
-The reserved constants allow code targeting future releases to compile, although no current factory accepts them. See [Reserved and unavailable APIs](#reserved-and-unavailable-apis).
+`TEST_NATIVE` remains reserved; no current factory accepts it. See [Reserved and unavailable APIs](#reserved-and-unavailable-apis).
 
 ## Mediation diagnostics
 
@@ -565,7 +588,7 @@ The reserved constants allow code targeting future releases to compile, although
 
 The method reads Google's current public initialization status without starting SDKs or ad requests. During initialization the map can be empty or partial. An absent entry does not prove that a complement is missing. This is not an installed-module inventory, account check, credential check or guarantee of provider delivery. `ready` does not guarantee an ad.
 
-Query after the unchanged `module_initialized` event:
+Query after `module_initialized`:
 
 ```js
 Admob.addEventListener('module_initialized', event => {
@@ -577,8 +600,8 @@ Use UMP, `canRequestAds()` and each selected provider's current privacy requirem
 
 ## Reserved and unavailable APIs
 
-- There is no `createRewardedInterstitial`.
 - There is no `createNative`.
+- There is no server-side verification configuration (`userId` / `customData`), paid-event / impression-level revenue callback, or public response-info API. Arbitrary `extras` do not add these features. Use `rewarded` for client-side rewards and Ad Inspector for request diagnostics.
 
 
 ## Consent compatibility payloads

package/skills/ti-admob-unified/references/banners.md

@@ -1,10 +1,10 @@
-> Source snapshot: official ti.admob.unified 1.0.0 documentation at commit `5b4cbf9` (copied 2026-10-11). Relative links rebased for this skill.
+> Source snapshot: official ti.admob.unified 1.0.0 documentation at release source commit `034843299b2984253988e0ffccb9f6a1c91682c9` (copied 2026-10-24). Relative links rebased for this skill.
 
 # Banner ads
 
 Standard and adaptive banners share one public lifecycle and event contract on iOS and Android.
 
-Both factories return a Titanium `TiViewProxy`, so their creation dictionaries also accept normal Titanium view/layout properties such as `width`, `height`, `top`, `bottom`, `left`, and `right`. The tables below list the AdMob-specific properties.
+Both factories return a Titanium `TiViewProxy`, so their creation dictionaries also accept normal Titanium view/layout properties such as `width`, `height`, `top`, `bottom`, `left`, and `right`. The tables list the AdMob-specific properties.
 
 <!-- TOC-START -->
 ## Contents
@@ -47,7 +47,7 @@ bannerHost.add(banner)
 banner.load()
 ```
 
-The proxy must be in the Titanium view hierarchy before `load()` so its native view can measure the real container width.
+Run these raw API snippets after `module_initialized` succeeds and `canRequestAds()` is true. The proxy must be in the Titanium view hierarchy before `load()` so its native view can measure the real container width. For iOS anchored placements, use the layout-ready pattern under [Full lifecycle example](#full-lifecycle-example), or the [integration library](library.md#banners), rather than calling `load()` immediately after `add()`.
 
 ### Creation properties
 
@@ -169,7 +169,7 @@ function onLoaded(event) {
 
 function onFailed(event) {
   Ti.API.warn(`Banner failed: ${event.error} (${event.code})`)
-  setBannerHeight(0)
+  // Keep the reserved slot stable while a later user action retries.
 }
 
 function onDestroyed() {
@@ -295,7 +295,7 @@ Returns `true` only while the current proxy owns a successfully loaded ad.
 
 Terminal and safe to repeat. It releases the native ad, detaches native delegates/listeners and lifecycle registrations, and emits `destroyed` once.
 
-Never reuse a destroyed banner. Create a new proxy for a new placement or a new width/orientation request.
+Never reuse a destroyed banner. Create a new proxy for a new placement. For a width or orientation change, wait for the host's final positive layout and request the new size; the integration library exposes `rebuild()` for that boundary.
 
 ### Compatibility aliases
 
@@ -347,7 +347,7 @@ An adaptive `loaded` event guarantees:
 }
 ```
 
-Android additionally reports diagnostic size fields:
+Both platforms also report these size fields:
 
 ```js
 {
@@ -416,17 +416,17 @@ Portable fixed sizes, with the device each one was designed for and the height i
 | `FULLBANNER`       | 468×60  | Tablet          |
 | `LEADERBOARD`      | 728×90  | Tablet          |
 
-These device categories come from Google's `GADAdSize.h`. A phone is 360–430 dp wide, so a 468 dp `FULLBANNER` cannot fit at full size regardless of the host height. Use `BANNER` for the fixed phone size, or `customAdSize` with the screen width or an adaptive banner for a full-width strip.
+These device categories come from Google's `GADAdSize.h`. In a portrait placement 360 to 430 dp wide, a 468 dp `FULLBANNER` cannot fit at full size regardless of the host height. Use `BANNER` for the fixed phone size, or `customAdSize` with the screen width or an adaptive banner for a full-width strip.
 
 Give the host the requested height. A `FULLBANNER` in a 50 dp box will be clipped.
 
 Unknown values, including `smart_banner`, fall back to `BANNER`. Google removed smart banners on Android and deprecated them on iOS. The shared fallback avoids selecting a fixed 320×50 banner on one platform and a full-width strip on the other. For full width, use `customAdSize` or `createAdaptiveBanner()` to let Google choose the height.
 
-Changing `adSize` on an existing iOS native banner is not supported. Destroy and recreate the proxy.
+Assign the new `adSize` or `customAdSize`, then call `load()` to apply it on both platforms. The module replaces the native view when needed while retaining the proxy.
 
 ## Refresh behavior
 
-Do not add a JavaScript renewal timer. Google Mobile Ads respects the banner refresh rate configured for the ad unit in AdMob. The application requests the initial load and lets the SDK/ad-unit configuration own later refreshes.
+Do not add a JavaScript renewal timer. Google Mobile Ads respects the banner refresh rate configured for the ad unit in AdMob. The application requests the first load. The SDK and ad-unit configuration control later refreshes.
 
 TiAdMobUnified manages the native banner proxy and its lifecycle without a periodic reload or recreation loop. Google documents that Android automatic refresh requires a visible banner. Set or disable the refresh interval in AdMob, and use screen-level `pause()`/`resume()` when navigation hides or reveals the placement.
 

package/skills/ti-admob-unified/references/contributing.md

@@ -1,8 +1,8 @@
-> Source snapshot: official ti.admob.unified 1.0.0 documentation at commit `5b4cbf9` (copied 2026-10-11). Relative links rebased for this skill.
+> Source snapshot: official ti.admob.unified 1.0.0 documentation at release source commit `034843299b2984253988e0ffccb9f6a1c91682c9` (copied 2026-10-24). Relative links rebased for this skill.
 
 # Contributing to ti.admob.unified
 
-Changes to this native bridge must keep the JavaScript contract consistent with native behavior on both platforms, including cleanup. Tests and documentation must describe that same behavior.
+Keep the JavaScript contract consistent with native behavior on both platforms, including cleanup. Tests and documentation must agree with the implementation.
 
 ## Before opening an issue
 
@@ -21,9 +21,9 @@ For layout issues, include the Titanium proxy, host, and parent dimensions plus
 
 ## Development baseline
 
-- Titanium SDK `13.2.0.GA` or later (build toolchain: `13.4.1.GA`)
+- Titanium SDK `13.4.1.GA` or later (build toolchain: `13.4.1.GA`)
 - iOS `15.0+`
-- Android API `24+`, the floor the Titanium `13.2.0.GA` module template sets
+- Android API `24+`, required by the pinned Google Mobile Ads SDK
 - Node.js with the built-in `node:test` runner
 
 Dependency versions are pinned in [DEPENDENCIES.md](dependencies.md).
@@ -32,12 +32,15 @@ Dependency versions are pinned in [DEPENDENCIES.md](dependencies.md).
 
 Create a focused branch and keep unrelated local changes intact. Before editing a native dependency, establish a recoverable Git baseline and record the upstream source and checksum.
 
-This repository holds the core at its root and five dependency-only complements in `mediation/<network>/`. Each has iOS and Android projects at version `1.0.0`. Scripts discover complement folders and derive archive identity/version from manifests. See [Adding a network](#adding-a-network). Applications call only the core. Both script helpers accept a module directory or `--all`.
+The repository root contains the core. Five dependency-only complements live in `mediation/<network>/`. Each has iOS and Android projects at version `1.0.0`. Scripts discover complement folders and derive archive identity/version from manifests. See [Adding a network](#adding-a-network). Applications call only the core. Both script helpers accept a module directory or `--all`.
 
 Run the static checks from the repository root:
 
 ```sh
 npm test
+python3 tests/native/android.py
+python3 tests/native/initialization.py
+python3 tests/native/run.py
 ./scripts/verify-artifacts.sh
 ./scripts/verify-artifacts.sh --all
 node --check example/app.js
@@ -70,11 +73,11 @@ Complements package existing official Google mediation adapters; writing a new n
 
 ## Platform notes
 
-The native implementations share one JavaScript contract. The notes below describe their source files and platform differences.
+Both native implementations expose the same JavaScript contract. These notes cover their source files and platform differences.
 
 ### iOS
 
-Sources in `ios/Classes/` comprise five proxy pairs and the module:
+The sources in `ios/Classes/` contain six proxy pairs and the module:
 
 | Source                                  | Responsibility                                            |
 | --------------------------------------- | --------------------------------------------------------- |
@@ -83,6 +86,7 @@ Sources in `ios/Classes/` comprise five proxy pairs and the module:
 | `TiAdmobUnifiedAdaptiveBannerAdProxy.*` | Anchored and inline adaptive banner proxy and native view |
 | `TiAdmobUnifiedInterstitialAdProxy.*`   | Interstitial proxy                                        |
 | `TiAdmobUnifiedRewardedAdProxy.*`       | Rewarded proxy                                            |
+| `TiAdmobUnifiedRewardedInterstitialAdProxy.*`       | Rewarded interstitial proxy                                            |
 | `TiAdmobUnifiedAppOpenAdProxy.*`        | App open proxy and the four hour validity window          |
 
 Build from the repository root:
@@ -114,6 +118,7 @@ Sources live in `android/src/ti/admob/unified/`. The banner types split proxy an
 | `TiAdmobUnifiedAdaptiveBannerAdProxy.java` / `…AdView.java` | Adaptive banner proxy and native container           |
 | `TiAdmobUnifiedInterstitialAdProxy.java`                    | Interstitial proxy                                   |
 | `TiAdmobUnifiedRewardedAdProxy.java`                        | Rewarded proxy                                       |
+| `TiAdmobUnifiedRewardedInterstitialAdProxy.java`                        | Rewarded interstitial proxy                                       |
 | `TiAdmobUnifiedAppOpenAdProxy.java`                         | App open proxy and the four hour validity window     |
 
 Maven coordinates are declared in `android/build.gradle`. Build from the module root:
@@ -141,7 +146,7 @@ Do not add a public method or constant on one platform without checking and docu
 For a new or changed method, property, event, payload key, or constant:
 
 1. Define the portable JavaScript contract first.
-2. Implement it on iOS and Android, or document the platform limitation explicitly.
+2. Implement the same JavaScript API on iOS and Android. Document native SDK limitations without adding a public method on only one platform.
 3. Preserve existing supported use cases.
 4. Make cleanup and repeated lifecycle calls deterministic.
 5. Add contract tests for both native sources.
@@ -223,6 +228,6 @@ Contributions are licensed under the [MIT License](module-license.txt).
 
 ### Native wrapper behavior harness
 
-Run `python3 tests/native/android.py` with a JDK, and `python3 tests/native/run.py` on macOS. The Java harness checks percentage validation, the TCF preference store and consent reset ordering. It compiles the current Objective-C method bodies against controlled Foundation-based SDK stand-ins and checks volume validation, load-error mapping, consent retry/reset ordering and delayed reward callbacks. It does not replace a Titanium consumer build, native bridge checks or Google ad presentation tests. `npm test` separately exercises the JavaScript library and example, alongside static contract checks.
+Run `python3 tests/native/android.py` with a JDK, and `python3 tests/native/run.py` on macOS. The Java harness checks percentage validation, the TCF preference store and consent reset ordering. The Objective-C harness compiles the current method bodies against controlled Foundation-based SDK stand-ins and checks volume validation, load-error mapping, consent retry/reset ordering and delayed reward callbacks. It does not replace a Titanium consumer build, native bridge checks or Google ad presentation tests. `npm test` separately exercises the JavaScript library and example, alongside static contract checks.
 
 After individual platform builds, run `python3 scripts/prepare-package-docs.py` before `python3 scripts/verify-packages.py`. Titanium renders guides as HTML without rewriting their Markdown links. The preparation step fixes links between generated guides and includes the linked Markdown sources for offline use. `scripts/build-all.sh` runs both steps automatically.

package/skills/ti-admob-unified/references/dependencies.md

@@ -1,19 +1,23 @@
-> Source snapshot: official ti.admob.unified 1.0.0 documentation at commit `5b4cbf9` (copied 2026-10-11). Relative links rebased for this skill.
+> Source snapshot: official ti.admob.unified 1.0.0 documentation at release source commit `034843299b2984253988e0ffccb9f6a1c91682c9` (copied 2026-10-24). Relative links rebased for this skill.
 
 # Dependency inventory
 
-The core and five optional complements use the published versions verified on September 23, 2026. Each module has its own iOS Podfile, lockfile and framework checksum inventory. Android pins live in each module’s `android/build.gradle`.
+The core and five optional complements use the published SDK and adapter pairs verified on October 23, 2026. Each module has its own iOS Podfile, lockfile and framework checksum inventory. Android pins live in each module's `android/build.gradle`.
+
+The latest published Google adapters determine the network SDK versions. Meta iOS SDK `6.22.1` and InMobi Android SDK `11.5.1` are available independently, but their current Google adapters pin `6.22.0` and `11.5.0` respectively; those tested pairs are retained. Do not replace a network SDK independently of its adapter. InMobi Android adapter `11.5.0.1` is available as an AAR and POM in Google's Maven repository, although its documentation heading still says "In progress".
+
+Google currently lists GMA iOS `13.x` and Android `25.x` as supported. Check both the [iOS sunset schedule](https://developers.google.com/admob/ios/deprecation) and [Android sunset schedule](https://developers.google.com/admob/android/deprecation), plus SDK/provider advisories, before distributing an app update. A supported major version and a store-specific SDK warning are separate checks; review any warning against the final app's resolved dependencies.
 
 ## iOS vendored XCFrameworks: `ti.admob.unified`
 
 | Component               | Framework                           |  Version |
 | ----------------------- | ----------------------------------- | -------: |
-| Google Mobile Ads       | `GoogleMobileAds.xcframework`       | `13.10.0` |
+| Google Mobile Ads       | `GoogleMobileAds.xcframework`       | `13.11.0` |
 | User Messaging Platform | `UserMessagingPlatform.xcframework` |  `3.1.0` |
 
 ## iOS per-network complements
 
-The eleven frameworks are stored without duplication under `mediation/<network>/ios/platform/`: AppLovin (2), Meta (2), InMobi (2), Unity (3), Liftoff (2). Unity Ads 4.20.1 no longer requires IronSourceAdQualitySDK. No ironSource advertising adapter or SDK is distributed.
+The eleven frameworks are stored without duplication under `mediation/<network>/ios/platform/`: AppLovin (2), Meta (2), InMobi (2), Unity (3), Liftoff (2). Unity Ads 4.21.0 no longer requires IronSourceAdQualitySDK. No ironSource advertising adapter or SDK is distributed.
 
 | Component                 | Framework                            |      Version |
 | ------------------------- | ------------------------------------ | -----------: |
@@ -21,15 +25,15 @@ The eleven frameworks are stored without duplication under `mediation/<network>/
 | AppLovin SDK              | `AppLovinSDK.xcframework`            |     `13.6.4` |
 | Meta adapter              | `MetaAdapter.xcframework`            | `6.22.0.0` |
 | Meta Audience Network SDK | `FBAudienceNetwork.xcframework`      |     `6.22.0` |
-| InMobi adapter            | `InMobiAdapter.xcframework`          |   `11.4.1.0` |
-| InMobi SDK                | `InMobiSDK.xcframework`              |     `11.4.1` |
-| Unity adapter             | `UnityAdapter.xcframework`           |   `4.20.1.0` |
-| Unity Ads SDK             | `UnityAds.xcframework`               |     `4.20.1` |
-| Unity support library     | `UnityCoherenceLib.xcframework`      |      `0.1.0` |
-| Liftoff Monetize adapter  | `LiftoffMonetizeAdapter.xcframework` |    `7.7.7.0` |
-| Vungle Ads SDK            | `VungleAdsSDK.xcframework`           |      `7.7.7` |
+| InMobi adapter            | `InMobiAdapter.xcframework`          |   `11.5.0.0` |
+| InMobi SDK                | `InMobiSDK.xcframework`              |     `11.5.0` |
+| Unity adapter             | `UnityAdapter.xcframework`           |   `4.21.0.0` |
+| Unity Ads SDK             | `UnityAds.xcframework`               |     `4.21.0` |
+| Unity support library     | `UnityCoherenceLib.xcframework`      |      `0.2.0` |
+| Liftoff Monetize adapter  | `LiftoffMonetizeAdapter.xcframework` |    `7.7.8.0` |
+| Vungle Ads SDK            | `VungleAdsSDK.xcframework`           |      `7.7.8` |
 
-The version column is the pinned CocoaPods version; lockfiles record the resolved adapter and SDK pair. Meta now uses SDK 6.22.0 on both platforms. Liftoff uses SDK 7.7.7 on iOS and 7.7.8 on Android. The version contract test retains this remaining difference and checks the matching networks.
+The version column is the pinned CocoaPods version; lockfiles record the resolved adapter and SDK pair. Meta now uses SDK 6.22.0 on both platforms. Liftoff uses SDK 7.7.8 on iOS and 7.7.9 on Android. The version contract test records this difference and checks the networks whose versions match.
 
 The official CocoaPods specifications resolve the adapter and matching network SDK pairs. Each module has its own `ios/install_frameworks.sh`: it downloads that module's exact Podfile versions, stages its framework set, verifies its tree hashes, and restores the previous platform directory if validation fails. Run `ios/install_frameworks.sh` for the two core frameworks and `mediation/<network>/ios/install_frameworks.sh` for one complement. Complement installers use `pod install --deployment` to preserve the locked resolution.
 
@@ -48,7 +52,7 @@ Declared in `android/build.gradle`.
 | ------------------------------------------------ | ------: |
 | `com.google.android.gms:play-services-ads`       |  25.5.0 |
 | `com.google.android.ump:user-messaging-platform` |   4.0.0 |
-| `com.google.guava:guava` | 33.7.1-android |
+| `com.google.guava:guava` | 33.7.2-android |
 
 ## Android per-network complements
 
@@ -57,12 +61,14 @@ Declared separately in `mediation/<network>/android/build.gradle`; `meta` uses t
 | Coordinate                          |  Version |
 | ----------------------------------- | -------: |
 | `com.google.ads.mediation:facebook` | 6.22.0.1 |
-| `com.google.ads.mediation:inmobi`   | 11.4.1.2 |
-| `com.google.ads.mediation:unity`    | 4.20.1.0 |
+| `com.google.ads.mediation:inmobi`   | 11.5.0.1 |
+| `com.google.ads.mediation:unity`    | 4.21.0.0 |
 | `com.google.ads.mediation:applovin` | 13.6.4.2 |
-| `com.google.ads.mediation:vungle`   | 7.7.8.1 |
+| `com.google.ads.mediation:vungle`   | 7.7.9.0 |
+
+Each complement declares its adapter coordinate. Unity also explicitly declares `com.unity3d.ads:unity-ads:4.21.0`: Google's adapter POM does not bring the Unity SDK transitively. Both entries must reach the packaged POM and consumer graph. See Google's [Unity Android integration guide](https://developers.google.com/admob/android/mediation/unity).
 
-Each complement declares one adapter coordinate. InMobi and Liftoff also pin OkHttp 4.12.0. This replaces InMobi’s 3.14.9 and lifts Liftoff’s Okio dependency above the affected 3.0.0 release while retaining the okhttp3 API. Generated POMs propagate these versions and the matching network SDK into the consuming application. The core POM declares GMA, UMP and a patched Guava utility dependency. Guava replaces the older transitive version; it adds no ad network. Inspect all six POMs and resolved consumer dependency graphs before release.
+InMobi, Liftoff and Unity also pin `com.squareup.okhttp3:okhttp:5.4.0` and `com.squareup.okio:okio:3.18.2`. OkHttp 5.4.0 requires compile SDK 36, provided by the declared minimum Titanium 13.4.1.GA. OkHttp 5.5.x requires compile SDK 37 and remains incompatible with this stable Titanium toolchain. Okio fixes base64 compatibility with callers compiled against pre-3.18 releases. These utility dependencies add no ad networks. The core pins Guava `33.7.2-android` for its deserialization allocation fix. Unity Ads 4.21.0 requests OkHttp 3.12.13 and Okio 1.15.0 without these overrides; both matched advisories during the isolated-consumer scan. Generated POMs propagate the reviewed versions into consumer applications.
 
 ## Update policy
 
@@ -70,16 +76,16 @@ All six modules remain at version `1.0.0`. Dependency updates require rebuilding
 
 ## Transitive security review
 
-The September 23, 2026 refresh checks resolved dependencies for all eight Android consumer combinations. Updating the ad adapters alone still selected older utility libraries, so the distributed POMs include these corrections:
+The October 23 refresh updates the direct utility overrides as well as the ad SDKs:
 
-| Dependency | Previous resolution | Updated resolution | Where the pin lives |
+| Dependency | Previous pin | Current pin | Modules |
 | --- | --- | --- | --- |
-| Guava | `31.1-android` in core and several combinations | `33.7.1-android` | Core Android module |
-| OkHttp | `3.14.9` with InMobi; `4.10.0` with Liftoff | `4.12.0` | InMobi and Liftoff Android complements |
-| Okio / Okio-jvm | `3.0.0` with Liftoff | At least `3.6.0`, through OkHttp; InMobi selects `3.7.0` | Resolved transitively |
+| Guava | `33.7.1-android` | `33.7.2-android` | Core |
+| OkHttp | `4.12.0` | `5.4.0` | InMobi, Liftoff, Unity |
+| Okio | Transitive, including `3.6.0` / `3.7.0` | `3.18.2` | InMobi, Liftoff, Unity |
 
-Guava's Android variant requires API 24, matching this module's existing floor. [Guava release notes](https://github.com/google/guava/releases/tag/v33.7.1) identify the published Android artifact. [OkHttp 4's compatibility guide](https://lysine.dev/okhttp/changelogs/upgrading_to_okhttp_4/) documents binary compatibility with the okhttp3 API; its [4.x changelog](https://lysine.dev/okhttp/changelogs/changelog_4x/) records the hostname-verification fix and Okio update. These are utility dependencies, not additional ad networks.
+Guava's [33.7.2 release](https://github.com/google/guava/releases/tag/v33.7.2) documents the allocation fix. OkHttp's [changelog](https://lysine.dev/okhttp/changelogs/changelog/) documents later releases, but 5.4.0 is the latest compatible pin because of the Android AAR compile-SDK requirements above. The 5.5.1 certificate-blocklist change is not included in this compatible pin; runtime OS support and compile-SDK requirements are separate constraints. The [Okio changelog](https://lysine.dev/okio/changelog/) describes the 3.18.2 compatibility correction.
 
-The earlier matches were `GHSA-5mg8-w23w-74h3`, `GHSA-7g45-4rm6-3mm3` (Guava), `GHSA-3cqm-mf7h-prrj` (OkHttp) and `GHSA-w33c-445m-f8w7` (Okio). The final [OSV querybatch](https://google.github.io/osv.dev/api/) scan covered 149 distinct Maven name/version pairs across all eight consumer combinations and returned no matches on September 23, 2026. A version scan does not establish provider delivery or prove that every internal SDK path is safe.
+The October 23 [OSV querybatch](https://google.github.io/osv.dev/api/) scan covered 151 distinct resolved Maven name/version pairs across eight configurations: core, each complement, AppLovin + Unity, and all networks. No matches remained after the Unity utility overrides. The earlier September scan describes the old matrix. Dependency scanning and successful linking do not establish provider ad delivery.
 
-Unity `4.20.1.0` includes the adapter consent-forwarding update. Provider-side verification is described in the [mediation guide](mediation.md#unity-consent-with-the-pinned-adapter).
+Unity `4.21.0.0` includes the adapter consent-forwarding update. Provider-side verification is described in the [mediation guide](mediation.md#unity-consent-with-the-pinned-adapter).