[manuelmayer-dev]

Closes #934

Summary

Plugin widget types can set SupportsFlows on WidgetTypeDescriptor, and the host then runs a widget's stored flows on a press like it does for built-in widgets. Types that leave it unset behave as before.

Testing

Full build and all suites pass, including conformance and protocol, apart from two environment-only local failures that also fail on main. Verified with a scratch plugin on a running host: Web Client presses run an opted-in widget's flow and not a plain one's.

Plugin SDK / API compatibility

• No public, non-obsolete SDK or plugin protocol contract was removed or changed
• Contracts were only extended additively (new members with defaults, new optional fields, new message types)

Notes

Double Tap on hardware decks is not recognised for these widgets; that part of the request is documented as a limitation and left for a follow-up.

Checklist

• Tests were added or updated where needed
• The change was verified manually where appropriate
• Documentation was updated if the change affects documented behaviour
• I reviewed and understand every submitted change