@maccesar/titools 5.3.0 → 5.4.0

package/skills/ti-api/references/api-xml-global.md

@@ -32,6 +32,8 @@
 <!-- TOC-END -->
 
 ## Ti.XML
+> Full released contract: [Titanium.XML](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML)
+
 > The top level XML module.  The XML module is used for parsing and processing XML-based content.
 > Extends Ti.Module
 > Platforms: both
@@ -48,13 +50,15 @@ Both iOS and Android lack DTD support.
 | Method | Returns | Platform | Description |
 |--------|---------|----------|-------------|
 | parseString(xml) | Ti.XML.Document | both | Parses an XML string into a <Titanium.XML.Document> object. |
-| serializeToString(node) | String | both | Serializes a [Node](Titanium.XML.Node) object into a string. |
+| serializeToString(node) | String | both | Serializes a [Node](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Node) object into a string. |
 
 
 ---
 
 ## Ti.XML.Attr
-> Represents an attribute of an [Element](Titanium.XML.Element).
+> Full released contract: [Titanium.XML.Attr](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Attr)
+
+> Represents an attribute of an [Element](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Element).
 > Extends Ti.XML.Node
 > Platforms: both
 
@@ -74,6 +78,8 @@ Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.htm
 ---
 
 ## Ti.XML.CDATASection
+> Full released contract: [Titanium.XML.CDATASection](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.CDATASection)
+
 > Used to include blocks of literal text containing characters that would otherwise need to be escaped.
 > Extends Ti.XML.Text
 > Platforms: both
@@ -86,6 +92,8 @@ Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.htm
 ---
 
 ## Ti.XML.CharacterData
+> Full released contract: [Titanium.XML.CharacterData](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.CharacterData)
+
 > An interface extending <Titanium.XML.Node> with a set of attributes and methods for accessing character data in the DOM. Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-FF21A306) on Android and iOS. For reasons of compatibility with the JavaScript engine, text is represented by UTF-8 instead of UTF-16 on Android and iOS.
 > Extends Ti.XML.Node
 > Platforms: both
@@ -110,6 +118,8 @@ Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.htm
 ---
 
 ## Ti.XML.Comment
+> Full released contract: [Titanium.XML.Comment](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Comment)
+
 > Represents the contents of an XML comment.
 > Extends Ti.XML.CharacterData
 > Platforms: both
@@ -122,6 +132,8 @@ Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.htm
 ---
 
 ## Ti.XML.DOMImplementation
+> Full released contract: [Titanium.XML.DOMImplementation](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.DOMImplementation)
+
 > The <Titanium.XML.DOMImplementation> interface provides a number of methods for performing operations that are independent of any particular instance of the document object model.Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-102161490) on Android and iOS.
 > Extends Ti.Proxy
 > Platforms: both
@@ -138,6 +150,8 @@ Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.htm
 ---
 
 ## Ti.XML.Document
+> Full released contract: [Titanium.XML.Document](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Document)
+
 > The DOM Document returned from <Titanium.XML.parseString>.
 > Extends Ti.XML.Node
 > Platforms: both
@@ -153,7 +167,7 @@ This has been reported as [Android Issue #7395](http://code.google.com/p/android
 |----------|------|---------|----------|-------------|
 | doctype | Ti.XML.DocumentType | — | both | An interface to the list of entities that are defined for the document, such as… |
 | documentElement | Ti.XML.Element | — | both | Root element of this document. |
-| implementation | Ti.XML.DOMImplementation | — | both | [DOMImplementation](Titanium.XML.DOMImplementation) object associated with this… |
+| implementation | Ti.XML.DOMImplementation | — | both | [DOMImplementation](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.DOMImplementation) object associated with this… |
 
 
 ### Methods (14)
@@ -161,15 +175,15 @@ This has been reported as [Android Issue #7395](http://code.google.com/p/android
 |--------|---------|----------|-------------|
 | createAttribute(name) | Ti.XML.Attr | both | Creates an attribute with the given name. |
 | createAttributeNS(namespaceURI, name) | Ti.XML.Attr | both | Creates an attribute with the given name and namespace. |
-| createCDATASection(data) | Ti.XML.CDATASection | both | Creates and returns a [CDATASection](Titanium.XML.CDATASection). |
-| createComment(data) | Ti.XML.Comment | both | Creates a [Comment](Titanium.XML.Comment) with the supplied string data. |
-| createDocumentFragment(—) | Ti.XML.DocumentFragment | both | Creates an empty [DocumentFragment](Titanium.XML.DocumentFragment). |
+| createCDATASection(data) | Ti.XML.CDATASection | both | Creates and returns a [CDATASection](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.CDATASection). |
+| createComment(data) | Ti.XML.Comment | both | Creates a [Comment](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Comment) with the supplied string data. |
+| createDocumentFragment(—) | Ti.XML.DocumentFragment | both | Creates an empty [DocumentFragment](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.DocumentFragment). |
 | createElement(tagName) | Ti.XML.Element | both | Creates an element with the given tag name. |
 | createElementNS(namespaceURI, name) | Ti.XML.Element | both | Create a new element with the given namespace and name. |
-| createEntityReference(name) | Ti.XML.EntityReference | both | Creates an [EntityReference](Titanium.XML.EntityReference) with the given name. |
+| createEntityReference(name) | Ti.XML.EntityReference | both | Creates an [EntityReference](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.EntityReference) with the given name. |
 | createProcessingInstruction(target, data) | Ti.XML.ProcessingInstruction | both | Creates a processing instruction for inserting into the DOM tree. |
 | createTextNode(data) | Ti.XML.Text | both | Creates a text node. |
-| getElementById(elementId) | Ti.XML.Element | both | Returns an [Element](Titanium.XML.Element) that has an ID attribute with the gi… |
+| getElementById(elementId) | Ti.XML.Element | both | Returns an [Element](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Element) that has an ID attribute with the gi… |
 | getElementsByTagName(tagname) | Ti.XML.NodeList | both | Returns a node list of elements in the document which have the given tag. |
 | getElementsByTagNameNS(namespaceURI, localname) | Ti.XML.NodeList | both | Returns a node list of elements in the document which belong to the given names… |
 | importNode(importedNode, deep) | Ti.XML.Node | both | Imports a node from another document to this document, without altering or remo… |
@@ -178,6 +192,8 @@ This has been reported as [Android Issue #7395](http://code.google.com/p/android
 ---
 
 ## Ti.XML.DocumentFragment
+> Full released contract: [Titanium.XML.DocumentFragment](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.DocumentFragment)
+
 > A lightweight document object used as a container for a group of nodes.
 > Extends Ti.XML.Node
 > Platforms: both
@@ -192,6 +208,8 @@ Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.htm
 ---
 
 ## Ti.XML.DocumentType
+> Full released contract: [Titanium.XML.DocumentType](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.DocumentType)
+
 > Each <Titanium.XML.Document> has a `doctype` attribute whose value is either 'null' or a <Titanium.XML.DocumentType> object.
 > Extends Ti.XML.Node
 > Platforms: both
@@ -216,7 +234,9 @@ As of version 3.1, Android still does not truly support DTDs.  A document with a
 ---
 
 ## Ti.XML.Element
-> Represents an element in a DOM document, a <Titanium.XML.Node> defined by a start-tag and end-tag (or an empty tag). Elements may have [attributes](Titanium.XML.Attr) associated with them. Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-745549614) on Android and iOS with some non-standard extensions.
+> Full released contract: [Titanium.XML.Element](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Element)
+
+> Represents an element in a DOM document, a <Titanium.XML.Node> defined by a start-tag and end-tag (or an empty tag). Elements may have [attributes](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Attr) associated with them. Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-745549614) on Android and iOS with some non-standard extensions.
 > Extends Ti.XML.Node
 > Platforms: both
 
@@ -251,6 +271,8 @@ As of version 3.1, Android still does not truly support DTDs.  A document with a
 ---
 
 ## Ti.XML.Entity
+> Full released contract: [Titanium.XML.Entity](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Entity)
+
 > This interface represents an entity, either parsed or unparsed, in an XML document. Note that this models the entity itself not the entity declaration. The nodeName attribute that is inherited from Node contains the name of the entity. An Entity node does not have any parent. Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-527DCFF2) on Android and iOS.
 > Extends Ti.XML.Node
 > Platforms: both
@@ -268,6 +290,8 @@ As of version 3.1, Android still does not truly support DTDs.  A document with a
 ---
 
 ## Ti.XML.EntityReference
+> Full released contract: [Titanium.XML.EntityReference](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.EntityReference)
+
 > Represents an XML entity reference.
 > Extends Ti.XML.Node
 > Platforms: both
@@ -280,6 +304,8 @@ Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.htm
 ---
 
 ## Ti.XML.NamedNodeMap
+> Full released contract: [Titanium.XML.NamedNodeMap](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.NamedNodeMap)
+
 > A key-value paired map that maps String objects to <Titanium.XML.Node> objects. Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-1780488922) on Android and iOS.
 > Extends Ti.Proxy
 > Platforms: both
@@ -305,13 +331,15 @@ Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.htm
 ---
 
 ## Ti.XML.Node
-> A single node in the [Document](Titanium.XML.Document) tree.
+> Full released contract: [Titanium.XML.Node](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Node)
+
+> A single node in the [Document](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Document) tree.
 > Extends Ti.Proxy
 > Platforms: both
 
 Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-1950641247) on Android and iOS.
 
-Note that on iOS, only [Element](Titanium.XML.Element) nodes are mutable. This means that the methods `appendChild`, `insertBefore`, `removeChild`, and `replaceChild` only work on `Element` objects. If one of these methods is called on another type of node, it throws an exception.
+Note that on iOS, only [Element](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Element) nodes are mutable. This means that the methods `appendChild`, `insertBefore`, `removeChild`, and `replaceChild` only work on `Element` objects. If one of these methods is called on another type of node, it throws an exception.
 
 ### Properties (unique: 16/31)
 | Property | Type | Default | Platform | Description |
@@ -365,6 +393,8 @@ Note that on iOS, only [Element](Titanium.XML.Element) nodes are mutable. This m
 ---
 
 ## Ti.XML.NodeList
+> Full released contract: [Titanium.XML.NodeList](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.NodeList)
+
 > A list of <Titanium.XML.Node> objects. Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-536297177) on Android and iOS.
 > Extends Ti.Proxy
 > Platforms: both
@@ -384,6 +414,8 @@ Note that on iOS, only [Element](Titanium.XML.Element) nodes are mutable. This m
 ---
 
 ## Ti.XML.Notation
+> Full released contract: [Titanium.XML.Notation](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Notation)
+
 > Represents a notation declared in the DTD.  Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-5431D1B9) on Android and iOS.
 > Extends Ti.Proxy
 > Platforms: both
@@ -400,6 +432,8 @@ Note that on iOS, only [Element](Titanium.XML.Element) nodes are mutable. This m
 ---
 
 ## Ti.XML.ProcessingInstruction
+> Full released contract: [Titanium.XML.ProcessingInstruction](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.ProcessingInstruction)
+
 > A way to keep processor-specific information in the text of the document. Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-1004215813) on Android and iOS.
 > Extends Ti.Proxy
 > Platforms: both
@@ -416,6 +450,8 @@ Note that on iOS, only [Element](Titanium.XML.Element) nodes are mutable. This m
 ---
 
 ## Ti.XML.Text
+> Full released contract: [Titanium.XML.Text](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.XML.Text)
+
 > Represents the textual content of an <Titanium.XML.Element> or <Titanium.XML.Attr> Implements the [DOM Level 2 API](https://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-1312295772) on Android and iOS.
 > Extends Ti.XML.CharacterData
 > Platforms: both
@@ -435,6 +471,8 @@ Note that on iOS, only [Element](Titanium.XML.Element) nodes are mutable. This m
 ---
 
 ## Global
+> Full released contract: [Global](https://titaniumsdk.com/docs/sdk/13.4.1/Global)
+
 > The APIs that reside in the global scope, which may be called without a namespace prefix.
 > Extends Object
 > Platforms: both
@@ -444,24 +482,24 @@ Titanium provides a number of global built-in objects, detailed below.
 
 ### String Utilities
 
-Titanium includes several extra utility functions for formatting text, attached to the global [String](Global.String) object.
+Titanium includes several extra utility functions for formatting text, attached to the global [String](https://titaniumsdk.com/docs/sdk/13.4.1/Global.String) object.
 
 ### console
 
-Titanium provides [console](Global.Console) support familiar to many JavaScript developers for logging at the toplevel, in addition to the [Titanium](Titanium.API) logging facilities.
+Titanium provides [console](https://titaniumsdk.com/docs/sdk/13.4.1/Global.Console) support familiar to many JavaScript developers for logging at the toplevel, in addition to the [Titanium](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.API) logging facilities.
 
 ### Timers
 
 Titanium has built-in support for one-off and repeating timers:
 
-*(See full overview in titanium-docs)*
+Complete overview, setup, examples and version restrictions: [official Global API](https://titaniumsdk.com/docs/sdk/13.4.1/Global).
 
 ### Properties (unique: 4/16)
 | Property | Type | Default | Platform | Description |
 |----------|------|---------|----------|-------------|
 | console | Global.Console | — | both | Console logging facilities. |
 | global | Global | — | both | Reference to the global object itself. |
-| Buffer | buffer.Buffer | — | both | a global reference to the [Buffer](buffer.Buffer) class. |
+| Buffer | buffer.Buffer | — | both | a global reference to the [Buffer](https://titaniumsdk.com/docs/sdk/13.4.1/buffer.Buffer) class. |
 | process | process | — | both | Reference to the global `process` object. |
 
 ### Constants (12)
@@ -479,7 +517,7 @@ Titanium has built-in support for one-off and repeating timers:
 | clearTimeout(timerId) | void | both | Cancels a one-time timer. |
 | decodeURIComponent(encodedURI) | String | both | Replaces each escape sequence in the specified string, created using the `encod… |
 | encodeURIComponent(string) | String | both | Replaces each special character in the specified string with the equivalent URI… |
-| L(key, hint) | String | both | An alias for [Titanium.Locale.getString](Titanium.Locale.getString). |
+| L(key, hint) | String | both | An alias for [Titanium.Locale.getString](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.Locale). |
 | require(moduleId) | any | both | Loads either a native Titanium module or a CommonJS module. |
 | setInterval(function, delay) | Number | both | Executes a function repeatedly with a fixed time delay between each call to tha… |
 | setTimeout(function, delay) | Number | both | Executes code or a function after a delay. |
@@ -527,6 +565,8 @@ Titanium has built-in support for one-off and repeating timers:
 ---
 
 ## Global.Console
+> Full released contract: [Global.Console](https://titaniumsdk.com/docs/sdk/13.4.1/Global.Console)
+
 > Console logging facilities.
 > Extends Object
 > Platforms: both
@@ -560,6 +600,8 @@ Note that `console` does not currently implement the complete [Console](https://
 ---
 
 ## Global.Intl
+> Full released contract: [Global.Intl](https://titaniumsdk.com/docs/sdk/13.4.1/Global.Intl)
+
 > Namespace providing JavaScript's standard internationalization APIs.
 > Extends Object
 > Platforms: both
@@ -579,6 +621,8 @@ For more detail, see the MDN website about [Intl](https://developer.mozilla.org/
 ---
 
 ## Global.Intl.Collator
+> Full released contract: [Global.Intl.Collator](https://titaniumsdk.com/docs/sdk/13.4.1/Global.Intl.Collator)
+
 > Immutable object used to perform language sensitive string comparisons.
 > Extends Object
 > Platforms: both
@@ -619,6 +663,8 @@ For more detail, see the MDN website about [Intl.Collator](https://developer.moz
 ---
 
 ## Global.Intl.DateTimeFormat
+> Full released contract: [Global.Intl.DateTimeFormat](https://titaniumsdk.com/docs/sdk/13.4.1/Global.Intl.DateTimeFormat)
+
 > Immutable object used to generate localized date and time formatted strings.
 > Extends Object
 > Platforms: both
@@ -672,6 +718,8 @@ For more detail, see the MDN website about [Intl.DateTimeFormat](https://develop
 ---
 
 ## Global.Intl.NumberFormat
+> Full released contract: [Global.Intl.NumberFormat](https://titaniumsdk.com/docs/sdk/13.4.1/Global.Intl.NumberFormat)
+
 > Immutable object used to convert numbers to localized numeric strings.
 > Extends Object
 > Platforms: both
@@ -717,6 +765,8 @@ For more detail, see the MDN website about [Intl.NumberFormat](https://developer
 ---
 
 ## Global.String
+> Full released contract: [Global.String](https://titaniumsdk.com/docs/sdk/13.4.1/Global.String)
+
 > The JavaScript built-in String type.
 > Extends Object
 > Platforms: both

package/skills/ti-create-release/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: ti-create-release
+description: 'Use when preparing or publishing a GitHub release of a Titanium native module, building its platform ZIPs, checking release tags and assets, or configuring repository metadata for discovery in the Titanium module directory. Does not apply to App Store/Google Play releases or publishing Titanium SDK itself.'
+---
+
+# Release a Titanium native module
+
+Publish the requested platform packages from a verified source commit, following the repository's release conventions. Also check its discoverability at titaniumsdk.com/modules. This workflow applies to any maintainer's module, including single-platform modules and maintained forks.
+
+## Scope and authorization
+
+Inspect the user's request before acting. A release-readiness review is read-only; preparing notes/artifacts does not imply publishing. An explicit release request authorizes its scoped publication and accurate discovery metadata updates without another generic confirmation. Resolve concrete ambiguities before the affected mutation, while completing independent preparation.
+
+Do not publish app-store builds, Titanium SDK releases or a new TiTools version through this skill. Do not require an unrelated skill or a particular author's repository layout.
+
+## 1. Establish the source and release convention
+
+Read the repository instructions, README, platform manifests, build scripts/CI and recent releases. Identify the intended GitHub remote, default/release branch, requested platforms, version per platform and known build prerequisites.
+
+```sh
+SLUG=$(gh repo view --json nameWithOwner --jq .nameWithOwner)
+gh api "repos/$SLUG" --jq '{full_name,default_branch,private,archived,fork}'
+gh release list --repo "$SLUG" --limit 10
+git status --short
+git remote -v
+```
+
+Inspect a representative prior release's tag, title, notes and asset names. Reuse a consistent established convention: some modules release each platform separately; others attach several platform ZIPs to one release. Neither pattern is universal. First releases need a concrete proposed convention grounded in the module's versions and requested scope.
+
+Build from the intended merged default branch unless the user or repository specifies a release branch/commit. Fetch and inspect before switching or fast-forwarding. Preserve unrelated work; never reset, stash or commit it automatically. Use an isolated checkout/worktree when necessary to build the agreed commit without disturbing current work.
+
+Record the full commit SHA before building. A movable branch name is not sufficient provenance. If a later tracked source edit is needed, commit it within authorization, select the resulting SHA and rebuild before release.
+
+## 2. Check directory readiness
+
+Read [Module discovery](references/module-discovery.md) before changing metadata. It covers current official discovery rules, additive topics, English About descriptions, GitHub search verification and human Community review.
+
+A valid fork release may remain excluded from automatic discovery. Report that separately; directory exclusion alone does not block an otherwise valid authorized release. Do not detach forks, change visibility or fabricate native-platform folders to bypass filters.
+
+## 3. Build and inspect the requested packages
+
+Use the repository's documented build command and selected SDK/toolchain. Custom scripts may be required for Catalyst destinations, headers or package cleanup. Do not replace them with a guessed generic command. Standard module builds commonly run `ti build -p ios --build-only` or `ti build -p android --build-only` in the matching platform directory, but verify the installed builder and repository first.
+
+- Build only the requested/supported platforms. Single-platform releases and independently versioned Android/iOS packages are valid when intended.
+- Confirm fresh output from the recorded source SHA, rather than trusting an existing `dist/` ZIP. Serialize builds when they share generated inputs or output.
+- Inspect ZIP integrity, packaged manifest, module ID, platform, version, minimum SDK and required native payload. Match the manifest inside the ZIP to the intended release, not just the filename.
+- Apple packages conventionally use `iphone` in filenames even when the repository directory is `ios`. Preserve the actual builder output and platform scope, including Catalyst-only restrictions.
+- Record each exact artifact path and SHA-256. Avoid wildcard uploads that can include stale versions.
+
+If one requested build fails, fix it before publishing the affected release. Do not silently reduce scope, upload a stale platform package or claim that unbuilt platforms were released.
+
+## 4. Prepare notes and resolve tag state
+
+Follow the repository's established notes style. Describe the shipped platform changes, version/minimum-SDK changes and compatibility limits; link the relevant PR/commit when one exists. Do not require a PR for a direct committed release, mandate checkbox bullets or invent upstream dependency changes.
+
+Write the exact notes to a temporary UTF-8 file and use `--notes-file`. Keep release history out of skill resources.
+
+Distinguish an existing **Git tag** from an existing **GitHub release**. A release may legitimately be created for an existing tag, but first verify its remote peeled commit matches the built SHA. An existing release needs a separately authorized update; do not overwrite its assets or move tags as part of creating a new release. If immutable releases are enabled, published tags/assets cannot be replaced.
+
+Choose draft/prerelease/latest behavior from the user's intent, semantic version and repository convention. Do not mark a beta stable or replace a newer stable Latest unintentionally. Check `gh release create --help` for the installed CLI behavior.
+
+## 5. Publish the agreed release
+
+Before publication, have the exact source SHA, tag/title, notes file, platform artifact paths/hashes and release flags ready. Publish only within the existing authorization. For a new tag, target the full built commit SHA. For an already verified remote tag, use `--verify-tag`.
+
+Example shell invocation using prepared values and an explicit artifact list:
+
+```sh
+gh release create "$RELEASE_TAG" "${RELEASE_ASSETS[@]}" \
+  --repo "$SLUG" \
+  --target "$RELEASE_COMMIT" \
+  --title "$RELEASE_TITLE" \
+  --notes-file "$RELEASE_NOTES_FILE"
+```
+
+Set `RELEASE_ASSETS` to the exact requested ZIP paths. Add `--draft`, `--prerelease`, `--latest=false` or `--verify-tag` when the prepared plan requires them. Use one invocation per release grouping established above, rather than forcing one release per platform.
+
+If an API/upload fails, inspect the resulting release and assets before retrying: failure does not prove that no remote release was created. Do not create a second tag or replace an existing artifact to hide a partial upload. Report a genuine permission/build/publication blocker with the prepared details.
+
+## 6. Verify and report
+
+Read the resulting release back. Verify its public/draft status, exact tag commit, requested asset names/sizes and downloaded SHA-256 against the built packages. Authentication may hide a private release's availability to strangers; report visibility accurately.
+
+Follow [discovery verification](references/module-discovery.md#verify-discovery). Report these outcomes separately:
+
+- Release URL(s), platforms/versions, source SHA and verified assets.
+- Metadata changes, GitHub search eligibility and observed directory inclusion.
+- Any build, visibility, indexing or upstream refresh limitation that remains.
+
+A topic update or successful ZIP upload is not proof that the module is already listed or endorsed by TiDev. Do not trigger an upstream refresh or send a maintainer message without task authorization.
+
+## Sources
+
+- [GitHub CLI release creation](https://cli.github.com/manual/gh_release_create)
+- [GitHub CLI release inspection](https://cli.github.com/manual/gh_release_view)
+- [Titanium module discovery and curation](https://github.com/tidev/titaniumsdk.com/blob/main/docs/module-curation.md)
+
+Repository build/release instructions determine module-specific commands and artifacts; the linked discovery reference routes to the current generator and filters.

package/skills/ti-create-release/references/module-discovery.md

@@ -0,0 +1,69 @@
+# Automatic discovery in the Titanium module directory
+
+Use this during a native-module release or an explicit discovery-readiness task. The directory at [titaniumsdk.com/modules](https://titaniumsdk.com/modules) discovers repositories through GitHub search; it has no Showcase-style submission process.
+
+## Check current rules
+
+Consult the current official [curation policy](https://github.com/tidev/titaniumsdk.com/blob/main/docs/module-curation.md), [generator](https://github.com/tidev/titaniumsdk.com/blob/main/scripts/generate-community-modules.ts), [exclusion filter](https://github.com/tidev/titaniumsdk.com/blob/main/scripts/lib/community-filter.ts) and [refresh workflow](https://github.com/tidev/titaniumsdk.com/blob/main/.github/workflows/refresh-community-modules.yml). Recheck them when behavior changes; do not assume a past badge, author allowlist or schedule remains current.
+
+The current automatic filters are:
+
+- A public, non-archived repository that is not a fork.
+- At least one GitHub topic: `titanium`, `titanium-module` or `titanium-sdk`.
+- A language matching the generator's queries: Objective-C (`objc`), Swift, Java, Kotlin or JavaScript.
+- At least one recognized directory at the default branch root: `android`, `ios` or legacy `iphone`. The generator tests these paths through the GitHub contents API.
+- No match in the blocked or already-curated repository sets. An already-curated module uses its existing official listing rather than getting a duplicate community listing.
+
+Descriptions improve the generated listing but are not an automatic inclusion filter. Release ZIPs, manifest quality and license are human-review criteria, not extra filters in the current automatic scrape.
+
+Do not fabricate platform folders, add misleading language/topics, detach a fork or change visibility to make a repository pass. An Alloy widget without native platform directories does not meet this native-module discovery test. Report such cases for a maintainer decision instead of promising that topics fix them.
+
+## Inspect and complete metadata
+
+Resolve the intended repository from its remote before changing metadata:
+
+```sh
+SLUG=$(gh repo view --json nameWithOwner --jq .nameWithOwner)
+gh api "repos/$SLUG" --jq '{full_name,description,topics,private,archived,fork,language,default_branch}'
+gh api "repos/$SLUG/contents" --jq '.[] | select(.type == "dir") | .name'
+```
+
+For an authorized release/discovery task, add missing accurate topics. Adding all three Titanium topics makes the purpose explicit; any one is sufficient for discovery. `--add-topic` preserves existing topics:
+
+```sh
+gh repo edit "$SLUG"   --add-topic titanium   --add-topic titanium-module   --add-topic titanium-sdk
+```
+
+Add a few truthful feature/platform topics when useful. A Mac Catalyst-only module should say `mac-catalyst` and `macos`, rather than implying that it runs on iPhone merely because its package lives under `ios/`.
+
+Check GitHub's About description separately from the README. If empty or inaccurate, write a concise English sentence grounded in the README and released functionality: what the module does, its Titanium context and important platform limits. Preserve an existing accurate description. Apply the resulting sentence with `gh repo edit "$SLUG" --description "$DESCRIPTION"`, then read it back. Do not invent capabilities or fill an unknown description with generic marketing text.
+
+For example: “Native macOS open and save panels for Titanium SDK apps running on Mac Catalyst.” Use the actual module's capabilities, not this example for every release. A homepage is optional; set one only when an appropriate public documentation/product URL is known and the task calls for it.
+
+## Verify discovery
+
+1. Read repository metadata back and verify the resulting topics/description. Confirm the default-branch platform paths exist remotely; local unpushed folders do not qualify.
+2. Check GitHub search using the generator's topic and language filters. Scope by owner to keep the result readable, and verify the exact repository is returned:
+
+```sh
+REPO_OWNER=${SLUG%%/*}
+gh api --method GET search/repositories   -f "q=titanium in:topics language:objc language:swift language:java language:kotlin language:javascript user:$REPO_OWNER"   -f per_page=100   --jq '{incomplete_results, repositories: [.items[].full_name]}'
+```
+
+Repeat with `titanium-module` or `titanium-sdk` when those are the topics used. Paginate if needed; an incomplete/truncated search is not evidence that a missing repository is excluded. A newly added topic may take time to reach GitHub search. Record a pending search result without repeatedly rewriting correct metadata.
+
+3. Check current blocked/curated lists if the repository passes search but not the generator. A fork or archived repository remains excluded regardless of topic matches. Do not edit generated `registry/modules/community.json` by hand.
+4. Distinguish **metadata ready**, **found by GitHub search**, **eligible for the scrape**, and **observed in the live directory**. The refresh workflow currently runs daily; wait for its successful regeneration and deployment before claiming the final state. Do not trigger an upstream workflow, open an issue/PR or contact maintainers without task authorization.
+
+The generator labels any `ios/` or `iphone/` directory as iOS. For a Catalyst-only module, keep its actual runtime restriction prominent in the description and README; that badge alone does not establish iPhone compatibility.
+
+## Human review and release readiness
+
+Automatic discovery starts in **Unverified**, unless a maintainer's existing curation entry changes its tier. **Community** requires a person to review the repository against the current policy:
+
+- Public GitHub releases with packaged ZIP assets.
+- Parseable per-platform manifests containing `moduleid`, `version` and `minsdk`.
+- An OSI-approved license.
+- Evidence of maintenance within two years, or an explicit statement that the module is finished and works.
+
+Check these as release-quality information and report gaps. Do not change curation/author allowlists or claim TiDev endorsement. **Official** means TiDev maintains the module; publishing your own release does not grant that status.

package/skills/ti-expert/references/adaptive-layouts.md

@@ -560,4 +560,4 @@ aapt2 dump xmltree --file AndroidManifest.xml <apk> | grep -A2 "E: activity"
 | Spacing | `left`/`top` as offset from previous sibling in horizontal/vertical |
 | Batch updates | `view.applyProperties({...})` to reduce bridge overhead |
 
-For detailed layout APIs, see the `ti-ui` skill's [layouts-and-positioning.md](../../ti-ui/references/layouts-and-positioning.md) and [orientation.md](../../ti-ui/references/orientation.md).
+For detailed layout APIs, see the `ti-ui` skill's [layouts-and-positioning.md](../../ti-ui/references/layouts-and-positioning.md) and the released [Window orientation API](https://titaniumsdk.com/docs/sdk/13.4.1/Titanium.UI.Window).

package/skills/ti-guides/SKILL.md

@@ -1,86 +1,47 @@
 ---
 name: ti-guides
-description: 'Use when working on Titanium SDK fundamentals: project configuration (`tiapp.xml`, `timodule.xml`), CommonJS modules, Hyperloop native access, app distribution (App Store / Google Play, certificates, provisioning), Titanium CLI usage, memory management, bridge optimization, SQLite transactions, image memory, coding standards, the compatibility matrix (which JDK, Node.js, Xcode or Android SDK a given Titanium SDK needs), or what changed in a Titanium SDK release. Triggers include `tiapp.xml` in the project root, for either Alloy (`app/`) or Classic (`Resources/`) Titanium projects.'
+description: 'Use when working on current Titanium SDK fundamentals: environment setup, Classic or Alloy project creation and structure, tiapp.xml or timodule.xml configuration, native modules and npm dependencies, Hyperloop, app signing/distribution, Titanium CLI commands/configuration, local persistence, editor integration, released SDK compatibility and release notes. Applies when a project contains tiapp.xml, with Alloy app/ or Classic Resources/ sources. Use ti-api for individual API contracts, alloy-guides for MVC, and ti-howtos for native integrations.'
 ---
 
 # ti-guides
 
-## Overview
-
-Reference for Titanium SDK fundamentals: project configuration, distribution, native access via Hyperloop, CommonJS module patterns, memory and bridge optimization, and TiDev coding standards. Applies to both Alloy and Classic projects.
-
-## When to use
-
-Use this skill when:
-
-- The project contains `tiapp.xml` (definitive Titanium project indicator)
-- Configuring `tiapp.xml` or `timodule.xml`
-- Setting up app distribution (App Store / Google Play, certificates, provisioning, AAB / IPA)
-- Using Hyperloop to call native APIs (Objective-C / Swift / Java)
-- Optimizing memory: removing global listeners, caching native properties, image memory footprints
-- Working with the Titanium CLI (`ti build`, `ti sdk install`, `ti sdk select`)
-- Checking which JDK, Node.js, Xcode or Android SDK a Titanium SDK version requires
-- Finding out what changed in a Titanium SDK release and whether it affects existing code
-- Writing CommonJS modules (stateful caching, ES6+ patterns, antipatterns)
-- Authoring `AndroidManifest.xml` overrides
-- Following TiDev style and naming conventions
-
-Do NOT use for:
-
-- Alloy MVC concepts, controllers, models (use `alloy-guides`)
-- Alloy CLI usage and configuration files (use `alloy-howtos`)
-- Looking up specific Titanium API surfaces (use `ti-api`)
-- Native module dependency updates (use `ti-module-update`)
-
-## Quick reference
-
-| Topic | Reference |
-|---|---|
-| Project creation, structure, getting started (Alloy or Classic) | [hello-world.md](references/hello-world.md) |
-| JavaScript fundamentals, learning resources, ES6+ features | [javascript-primer.md](references/javascript-primer.md) |
-| Alloy vs Classic Titanium, framework selection | [application-frameworks.md](references/application-frameworks.md) |
-| Memory leaks, bridge efficiency, event naming, security, lazy loading | [coding-best-practices.md](references/coding-best-practices.md) |
-| Stateful modules, caching, ES6+ support, antipatterns | [commonjs-advanced.md](references/commonjs-advanced.md) |
-| SQLite transactions and image memory optimization | [advanced-data-and-images.md](references/advanced-data-and-images.md) |
-| Hyperloop: Objective-C / Swift / Java syntax, casting, debugging, XIB / Storyboards | [hyperloop-native-access.md](references/hyperloop-native-access.md) |
-| Naming standards and formatting rules | [style-and-conventions.md](references/style-and-conventions.md) |
-| ECMAScript, iOS, and Alloy reserved keywords to avoid | [reserved-words.md](references/reserved-words.md) |
-| Custom `AndroidManifest.xml`, permissions, manifest merge | [android-manifest.md](references/android-manifest.md) |
-| Google Play (APK / AAB), App Store (IPA), certificates, provisioning, deployment | [app-distribution.md](references/app-distribution.md) |
-| Complete `tiapp.xml` and `timodule.xml` reference | [tiapp-config.md](references/tiapp-config.md) |
-| Titanium CLI commands, options, tasks, configuration, build processes | [cli-reference.md](references/cli-reference.md) |
-| JDK, Node.js, Xcode and Android SDK versions each Titanium SDK supports | [compatibility-matrix.md](references/compatibility-matrix.md) |
-| What changed per 13.x release, and which changes affect your code | [sdk-release-notes.md](references/sdk-release-notes.md) |
-| Community support, modules, sample code, Slack, learning materials | [resources.md](references/resources.md) |
-
-## Core practices
-
-1. Validate that the project follows a modular pattern (CommonJS or Alloy).
-2. Ensure global listeners are removed and heavy objects are nulled during cleanup.
-3. Cache frequently accessed native properties to reduce bridge crossings.
-4. Use Hyperloop for specialized native functionality and handle casting and threading correctly.
-5. Use transactions for database work and manage image memory footprints.
-
-## Procedural rules
-
-- Always remove `Ti.App` and `Ti.Geolocation` listeners during controller cleanup.
-- Do not access `Ti.Platform` or `Ti.DisplayCaps` inside loops. Store values in local variables.
-- Concatenate Hyperloop selectors accurately (for example, `addAttribute:value:range:` → `addAttributeValueRange`).
-- Close result sets and database handles after every transaction block.
-
-## Response format
-
-When answering Titanium SDK questions:
-
-1. **Technical recommendation** — cite the specific TiDev best practice.
-2. **Optimized implementation** — provide modern ES6+ code.
-3. **Rationale** — briefly explain the performance or memory impact.
+Use current official guides maintained in [tidev/titaniumsdk.com](https://github.com/tidev/titaniumsdk.com). Discover routes through [llms.txt](https://titaniumsdk.com/llms.txt); append `.md` to guide routes. API routes can be pinned, for example `https://titaniumsdk.com/docs/sdk/13.4.1`. Read rendered compatibility Markdown because raw source uses generated includes.
+
+This skill covers the released SDK 13.4.1.GA baseline. Verify version-specific contracts against the selected SDK's declarations and implementation; do not treat SDK `main`, an unversioned API page, or SDK 14-only site guidance as released behavior. Current guides can contain errors. Explain a verified discrepancy instead of copying an invalid example.
+
+## Routes
+
+| Task | Reference |
+| --- | --- |
+| Toolchains, setup, Classic/Alloy creation, first run and hardware | [hello-world.md](references/hello-world.md) |
+| Source versus generated files, asset/native paths, framework choice | [application-frameworks.md](references/application-frameworks.md) |
+| Native module installation/declaration and npm runtime compatibility | [commonjs-advanced.md](references/commonjs-advanced.md) |
+| Properties, app files, SQLite cursors, async queries and seed migration | [advanced-data-and-images.md](references/advanced-data-and-images.md) |
+| Hyperloop setup, platform guards, native require paths and bridge costs | [hyperloop-native-access.md](references/hyperloop-native-access.md) |
+| Android manifest elements, merge behavior and release inspection | [android-manifest.md](references/android-manifest.md) |
+| Signing, AAB/archive/IPA workflows, review and code encryption | [app-distribution.md](references/app-distribution.md) |
+| Current tiapp.xml elements, ignored/removed settings and timodule.xml | [tiapp-config.md](references/tiapp-config.md) |
+| Current CLI commands, automation and machine configuration | [cli-reference.md](references/cli-reference.md) |
+| Released toolchain requirements and host/platform support | [compatibility-matrix.md](references/compatibility-matrix.md) |
+| Current registry release notes for SDK 13.4.1 | [sdk-release-notes.md](references/sdk-release-notes.md) |
+| VS Code, Pulsar and JetBrains integration | [resources.md](references/resources.md) |
+
+## Working rules
+
+- Confirm Classic versus Alloy source ownership before editing. Alloy generates `Resources/`; edit `app/` instead.
+- Pin SDK/module dependencies where reproducibility matters. Separate CLI requirements, SDK declarations and native-module compatibility.
+- A native module needs unpacking, declaration and a require. A JavaScript dependency must fit Titanium's actual runtime/API subset rather than assuming full Node.js or browser support.
+- Close SQLite cursors and database handles on success and failure. Await asynchronous work before closing resources.
+- Properties and encrypted JavaScript are not secure credential storage. Keep server secrets off the device.
+- Verify the final release manifest, privacy manifest placement, signing identity and actual exported artifact before submission.
+- For official guide examples use modern JavaScript, semicolons, braces and spaces. Preserve a regular function when callback behavior depends on its native `this` receiver.
 
 ## Related skills
 
-| Task | Use this skill |
-|---|---|
-| Alloy MVC concepts, controllers, models, data binding | `alloy-guides` |
-| Alloy CLI, `alloy.jmk`, `config.json`, debugging | `alloy-howtos` |
-| Titanium API lookup (Ti.UI, Ti.Network, modules) | `ti-api` |
+| Task | Skill |
+| --- | --- |
+| Alloy controllers, views, styles, models, collections and widgets | `alloy-guides` |
+| Alloy CLI, build configuration, debugging and localization | `alloy-howtos` |
+| Individual Titanium API properties, methods and event contracts | `ti-api` |
+| Media, notifications, maps, location and other native integrations | `ti-howtos` |
 | Native module dependency updates | `ti-module-update` |