[Bug] Mobile: in-thread replies to an agent do not trigger the agent

[potseeslc]

Summary

On the Buzz mobile app, replying to an agent from inside an existing channel thread does not trigger the addressed agent. The same agent responds when contacted from a new top-level channel message, so the failure appears specific to the mobile in-thread reply path.

Steps to reproduce

1. Open a channel in the Buzz mobile app that contains a managed agent.
2. Start with a message or existing thread involving that agent.
3. Reply to the agent from inside the thread, including the agent mention if the composer requires it.
4. Wait for the agent to receive/handle the event.

Expected behavior

The in-thread reply is delivered to the managed-agent harness and triggers the agent, just like a top-level @mention. The agent's response should remain attached to the same thread.

Actual behavior

The mobile in-thread reply does not trigger the agent. Sending a new top-level @mention to the same agent works, so users have to abandon the thread and restart the conversation at channel level.

Impact

• Thread continuity is broken for human-agent conversations on mobile.
• Users may assume the agent is working or offline when the reply was never dispatched to it.
• The workaround creates duplicate top-level conversations and loses context.

Notes

This may be related to #2415, which covers nested mobile thread replies not appearing because the read query is root-scoped. This report focuses on agent invocation/delivery: the reply does not wake or trigger the addressed agent, while a top-level mention does.

It would be useful to compare the Nostr tags produced by mobile for top-level mentions versus in-thread replies, especially the agent p tag and the e tags carrying root and reply markers, and then verify how buzz-acp filters those events.