docs(ai-transport): remove AI Transport section from message counting

Remove the AI Transport operations section and its frontmatter
references from the platform message counting page; it will be
re-added in a later PR alongside the AI Transport pricing page.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: umair-ably

src/pages/docs/platform/pricing/message-counting.mdx

@@ -1,7 +1,7 @@
 ---
 title: "Message counting"
-meta_description: "Understand which operations across all Ably products count as messages, including Pub/Sub, Chat, LiveObjects, Spaces, AI Transport, and LiveSync."
-meta_keywords: "message counting, pricing, Pub/Sub messages, Chat messages, LiveObjects messages, Spaces messages, AI Transport messages, LiveSync messages"
+meta_description: "Understand which operations across all Ably products count as messages, including Pub/Sub, Chat, LiveObjects, Spaces, and LiveSync."
+meta_keywords: "message counting, pricing, Pub/Sub messages, Chat messages, LiveObjects messages, Spaces messages, LiveSync messages"
 intro: "Messages are the primary unit of consumption that Ably charges for. Understanding which operations count as messages helps you estimate and manage costs."
 ---
 
@@ -154,19 +154,6 @@ Live cursors use a [separate channel](/docs/spaces/cursors#foundations) from oth
 
 For Spaces-specific cost optimization strategies, see [Spaces pricing](/docs/spaces/pricing).
 
-## AI Transport operations <a id="ai-transport-operations"/>
-
-[AI Transport](/docs/ai-transport) uses standard Pub/Sub messaging. Each token or message published to Ably counts as an inbound message, and each delivery to a subscriber counts as an outbound message.
-
-| Operation | Messages counted |
-| --- | --- |
-| Token append | 1 inbound message per token appended |
-| Token append with [rollup](/docs/ai-transport/features/token-streaming#rollup) | Multiple appends conflated into fewer inbound messages |
-| Token delivery | 1 outbound message per subscriber |
-| [Persistence](/docs/storage-history/storage) storage | 1 additional message per stored message |
-
-AI Transport streams a response by [appending](/docs/ai-transport/features/token-streaming) each token to a single message. By default, [append rollup](/docs/ai-transport/features/token-streaming#rollup) conflates the appends received within a rollup window into fewer published inbound messages, reducing cost. Tune this with the `appendRollupWindow` transport parameter.
-
 ## LiveSync operations <a id="livesync-operations"/>
 
 [LiveSync](/docs/livesync) publishes database changes as Pub/Sub messages. Each update follows the standard inbound/outbound counting pattern.