[sztomek]

Description

Sends the episode chat analytics from EventHorizonSchemas#139 that Android was still missing. This PR is based on #6142.

episode_chat_message_sent.message_index

• The position of the user's question in the conversation, starting at 1.
• It continues from the saved conversation when the chat is reopened, and starts again at 1 after Clear Chat. (Clear Chat is removed in a follow-up PR, so in the end it only continues.)
• A retried question keeps its number.
• If a question fails and the user asks a new one instead of retrying, the failed one isn't counted. It's also no longer sent to the server as part of the conversation history (it was never saved, so it disappeared from the chat anyway).

episode_chat_quote_play_tapped / episode_chat_quote_stop_tapped

• These now send quote_source = inline_timestamp, the only way to play a quote since [Episode Chat] Restyle the conversation #6124.
• The stop event goes away in the follow-up that makes a quote tap keep playing. Automattic/EventHorizonSchemas#140 removes it from the schema.

episode_chat_response_received (new on Android)

• duration_ms measures how long the user waits for an answer: from sending the question until the answer is saved. A token refresh or the database writes can add to it.
• ChatViewModel gets the clock injected as a TimeSource, so tests can control the time.

episode_chat_response_rated (new on Android)

• Sent each time a 👍/👎 from [Episode Chat] Rate answers with thumbs up or down #6142 sets a rating, with rating and message_index (the number of the question the answer replies to). Clearing a rating isn't tracked, since the schema says it "fires on each tap that sets a rating".

Fixes POC-952 https://linear.app/a8c/issue/POC-952

Testing Instructions

Use a debug build with "Episode Chat" on in Beta features, and watch adb logcat | grep "Analytics:".

1. Open Ask about this episode and ask two questions. ✅ episode_chat_message_sent shows message_index=1, then 2. Each one is followed by episode_chat_response_received with a duration_ms.
2. Close the chat, reopen it, and ask again. ✅ message_index=3.
3. ⋯ › Clear Chat, then ask again. ✅ message_index=1.
4. Turn on airplane mode and ask a question. ✅ episode_chat_message_failed, and no response_received. Turn airplane mode off and tap Retry. ✅ It keeps the same message_index.
5. Tap a quote's timestamp, then tap it again. ✅ The play and stop events both have quote_source=inline_timestamp.
6. Tap 👎 under the second answer. ✅ episode_chat_response_rated with rating=negative and message_index=2. Tap 👎 again to clear it. ✅ Nothing is tracked.

Screenshots or Screencast

No UI changes.

Checklist

• If this is a user-facing change, I have added an entry in CHANGELOG.md
• Ensure the linter passes (./gradlew spotlessApply to automatically apply formatting/linting)
• I have considered whether it makes sense to add tests for my changes
• All strings that need to be localized are in modules/services/localization/src/main/res/values/strings.xml
• Any jetpack compose components I added or changed are covered by compose previews
• I have updated (or requested that someone edit) the Event Horizon schema to reflect any new or changed analytics.

I have tested any UI changes...

• with different themes
• with a landscape orientation
• with the device set to have a large display and font size
• for accessibility with TalkBack

[claude]

Claude finished @sztomek's task in 54s —— View job

---

No blocking issues. message_index comes out right for retry, Clear Chat, reopen, and a new question after a failure, since the UI's canSend blocks a second send while one is in flight. TimeSource is already provided by UtilsModule, which the chat module depends on, so Hilt can inject it.

Non-blocking

• modules/features/chat/src/main/kotlin/au/com/shiftyjelly/pocketcasts/chat/ChatViewModel.kt:468: if a save fails partway, the failed question can already be in the DB and still shown in the chat. The next question then leaves it out of message_index and the history. Doing the inserts in ChatManagerImpl.sendMessage in one transaction fixes this. [Episode Chat] Send the missing chat analytics properties #6141 (comment)

[claude]

Claude finished @sztomek's task in 34s —— View job

---

The new push rebases the same five commits onto the updated feat/episode-chat-answer-rating, and the ViewModel changes look the same as in the last review. Nothing new to flag. The earlier non-blocking finding is still open: ChatManagerImpl.sendMessage still saves the question, reply and quote as separate writes, not in one transaction.

Non-blocking

• modules/features/chat/src/main/kotlin/au/com/shiftyjelly/pocketcasts/chat/ChatViewModel.kt:476: still open. See [Episode Chat] Send the missing chat analytics properties #6141 (comment)

[claude]

Claude finished @sztomek's task in 31s —— View job

---

The new commit (c3a6d4b) fixes the earlier non-blocking finding. ChatManagerImpl.sendMessage now saves the question, reply and quote with one insertMessages call, which Room runs as a single transaction. A failed question really is never saved now. The createdAt + index offsets keep the three rows in order. Nothing new to flag, and nothing still open.

[claude]

Claude finished @sztomek's task in 35s —— View job

---

This push rebases the same six commits onto the updated feat/episode-chat-answer-rating. The single-transaction insertMessages change in ChatManagerImpl is the same as in the last review, so there's nothing new to flag and nothing still open.

[wpmobilebot]

Version 8.23 has now entered code-freeze, so the milestone of this PR has been updated to 8.24.

[claude]

Claude finished @sztomek's task in 16s —— View job

---

This push rebases the same six commits onto the updated feat/episode-chat-answer-rating without changing the PR diff, so there's nothing new to flag and nothing still open.

[claude]

Claude finished @sztomek's task in 15s —— View job

---

This push rebases the same six commits onto the updated feat/episode-chat-answer-rating without changing the PR diff, so there's nothing new to flag and nothing still open.

[claude]

Claude finished @sztomek's task in 12s —— View job

---

This push rebases the same six commits onto the updated feat/episode-chat-answer-rating without changing the PR diff, so there's nothing new to flag and nothing still open.

[claude]

Claude finished @sztomek's task in 16s —— View job

---

This push rebases the same six commits onto the updated feat/episode-chat-answer-rating without changing the PR diff, so there's nothing new to flag and nothing still open.