feat(integrations): introduce optional SocialProviderCapabilities con…

[benceabel69]

What kind of change does this PR introduce?

Feature (non-breaking architectural enhancement)

Why was this change needed?

As the number of supported social providers grows, feature support (e.g. threads, polling, analytics, media limits, comments) is currently inferred implicitly through optional methods and scattered flags across provider implementations.

This can lead to:

• Implicit assumptions about provider capabilities
• Reduced clarity when introducing new providers
• Harder feature introspection in the future (e.g. dynamic UI behavior or validation)

To address this, this PR introduces a structured and backward-compatible SocialProviderCapabilities interface and extends the existing SocialProvider contract with an optional capabilities property.

This allows providers to explicitly declare supported features without introducing breaking changes or modifying existing behavior.

This change:

• Does NOT alter any existing method signatures
• Does NOT make new fields required
• Maintains full backward compatibility
• Keeps the change isolated to the integrations layer

The capability property has been implemented for:

• X
• LinkedIn
• Instagram

Other providers continue to function unchanged.

Other information:

This change was designed to be minimal and surgical, focusing only on extending the integration abstraction layer without refactoring unrelated code.

The goal is to provide a scalable foundation for future feature introspection (e.g. dynamic UI rendering, validation rules, or provider-specific feature toggling) while maintaining compatibility with all existing providers.

No configuration, infrastructure, or dependency changes were introduced.

Checklist:

• I have read the CONTRIBUTING guide.
• I checked that there were not similar issues or PRs already open for this.
• This PR fixes just ONE issue (do not include multiple issues or types of change in the same PR)

[vercel]

@benceabel69 is attempting to deploy a commit to the Listinai Team on Vercel.

A member of the Team first needs to authorize it.

[github-actions]

This PR is stale because it has been open for 90 days with no activity.

[github-actions]

This PR was closed because it has been inactive for 7 days since being marked as stale.