fix: update message structure in TwitterInteractionClient to include tweet content

[sin-bufan]

Relates to:

N/A

Risks

Low - This change only affects how tweet data is passed to action handlers internally, with no external API changes.

Background

What does this PR do?

This PR enhances the tweet interaction handling process by including the complete tweet data in message.content when calling processActions. This allows action handlers to access comprehensive information about the tweet being processed.

Key changes:

• Modified the handleTweet method in TwitterInteractionClient to pass the entire tweet object in the message content
• Updated message structure to include tweet data alongside existing content

What kind of change is this?

Improvements (misc. changes to existing features)

Why are we doing this? Any context or related work?

Previously, when processing tweet interactions, action handlers only had access to the tweet's text content through message.content. This limited their ability to make informed decisions or perform complex operations that might require additional tweet metadata (like author information, timestamps, media attachments, etc.).

By including the complete tweet object in the message content, we enable action handlers to:

1. Access rich tweet metadata for more contextual decision making
2. Handle tweet-specific features more effectively
3. Implement more sophisticated interaction logic based on tweet properties
4. Reduce the need for additional API calls to fetch tweet information

This enhancement provides a more robust foundation for implementing advanced tweet interaction features and improves the overall flexibility of the action handling system.

Documentation changes needed?

My changes do not require a change to the project documentation.

Testing

Where should a reviewer start?

1. Review the changes in packages/client-twitter/src/interactions.ts
2. Focus on the handleTweet method where tweet data is now included in the message content

Detailed testing steps

1. Run the Twitter interaction client with test tweets
2. Verify that action handlers receive the complete tweet object through message.content.tweet
3. Test various action handlers to ensure they can properly access and utilize the additional tweet metadata
4. Verify that existing functionality continues to work as expected

Screenshots

N/A

Deploy Notes

No special deployment steps required. Standard deployment process applies.

Database changes

None

Deployment instructions

Standard deployment process

[odilitime]

Hello,

We are changing our plugin development strategy to be more scalable. We have moved the plugins out into their own repos and we're looking for people to either maintain those or own them on their own Github.

Please make your code changes to this repo: https://github.com/elizaos-plugins/client-twitter

If you'd like to be a maintainer, file an issue in the plugin repo and join our Discord https://discord.gg/elizaos to coordinate.

If you'd like to control the plugin on your own Github, please add an issue to the plugin repo pointing to your repo, and add a modification to the registry. Submit a PR to edit the registry here: https://github.com/elizaos-plugins/registry

Closing this PR for now. Let us know if you have any questions