fix(messaging): dismiss stale message overlay before send_message

[devag7]

Fixes #433. Calls _dismiss_message_ui at the beginning of send_message to prevent stale overlays from causing composer_unavailable.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a proactive cleanup step to send_message to dismiss any lingering LinkedIn messaging overlay before navigating, along with a regression test to enforce the call order.

Changes:

• Call _dismiss_message_ui() at the start of LinkedInExtractor.send_message() to prevent UI overlays from intercepting interactions.
• Add an async test ensuring dismissal happens before the first navigation in send_message.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
tests/test_scraping.py	Adds a regression test verifying _dismiss_message_ui() is invoked before navigation in send_message.
linkedin_mcp_server/scraping/extractor.py	Ensures send_message dismisses any stale messaging overlay before navigating to the recipient profile.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[greptile-apps]

Greptile Summary

This PR updates send_message to clear stale LinkedIn messaging UI before composing a new message. It changes:

• Adds a best-effort _dismiss_message_ui() call after the recipient profile page loads.
• Keeps the existing compose navigation and confirmation flow intact.
• Adds coverage for the expected navigation and dismissal call order.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

_{Reviews (3): Last reviewed commit: "test(messaging): use synchronous mock si..." | Re-trigger Greptile}