fix(acp): wake agents for mentions added by edits

[loganj]

🤖

Summary

• Fixes edited messages failing to wake an agent when the edit adds that agent as a new mention.
• Adds stream-message edits (kind:40003) to the ACP harness's default actionable-mention subscriptions for startup, dynamically discovered channels, and setup/not-ready mode.
• Keeps the existing p-tag requirement and preserves explicit --kinds and config-rule overrides, so ordinary edits and unchanged mentions do not re-wake agents.
• Documents the updated defaults.

Related issue

None found. Source report: Buzz task thread

Testing

• cargo fmt --all -- --check
• cargo test -p buzz-acp — 670 unit tests and 9 integration tests passed
• cargo check -p buzz-acp
• git diff --check
• Pre-push: branch-skew, Rust tests, Desktop checks/tests, and Desktop Tauri clippy/tests passed

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ac89510841

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Resolve edit mentions to the original message before prompting

When a kind 40003 event wakes the harness, its bare e tag identifies the edited message, but parse_thread_tags only recognizes marker-based NIP-10 tags. The edit is therefore treated as a top-level message, and the prompt tells the agent to reply with --reply-to <edit-event-id>; the CLI then roots that reply at the auxiliary edit rather than the visible original message. Such replies do not appear in the original thread, and the setup listener has the same problem when publishing its nudge. Resolve the edit target and use the original message/thread as the context and reply anchor before forwarding these events.

Useful? React with 👍 / 👎.