Validate integration patterns across multiple Abilities

[jeffpaul]

Description

Confirm that the plugin’s connection layer, feature encapsulation, and SDK usage all work cleanly across more than one AI Ability (for example, text.generate, vision.describe, or classify). This issue ensures the architecture is robust enough to support different Ability types and multiple providers.

Goals

• Define an Ability matrix showing which plugin features use which Abilities and which providers support them.
• Validate that at least two Abilities function correctly within the plugin (for instance, text.generate for Title Rewriting and vision.describe for Alt Text Generation).
• Confirm that the connection layer and feature modules handle differing input/output formats gracefully.
• Implement runtime checks so features confirm required Abilities before exposing UI elements.
• Document how new features should declare and verify Ability requirements.

Acceptance Criteria

• Ability matrix added to /docs/abilities.md.
• Features log consistent capability checks through the shared connection manager.
• At least two Abilities verified end-to-end across two providers.
• UI properly hides or disables controls when a required Ability is unavailable.

[jeffpaul]

@dkotter perhaps the one remaining item here to handle for is:

• Document how new features should declare and verify Ability requirements.

Anything else you'd like done before we can consider this closed out?

[dkotter]

Nothing else I'm seeing here that needs done that isn't already done