Fix agent reply targeting: use mention post ID instead of root post ID

[Copilot]

The agent was replying to the conversation root instead of the specific post where it was mentioned, breaking reply threading.

Root Cause

GrokService.analyzeAndDecide() received the thread context but not the mention post ID. It defaulted to using thread.root_post.id as the reply target, causing all replies to target the conversation root regardless of where the mention occurred.

Changes

• Added mentionPostId parameter to analyzeAndDecide() and simulateAnalysis()
• Pass mention post ID from call sites in agent.ts and examples.ts
• Use mentionPostId as target_post_id instead of thread.root_post.id

Example Flow

// Before: always replied to root
const analysis = await grokService.analyzeAndDecide(mention.post.text, thread);
// analysis.action.target_post_id = thread.root_post.id ❌

// After: replies to the mention
const analysis = await grokService.analyzeAndDecide(mention.post.text, thread, mention.post.id);
// analysis.action.target_post_id = mention.post.id ✅

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[Copilot]

Pull request overview

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

[Copilot]

Unexpected any. Specify a different type.