Follow up to: #3582494 _**NOTE: Before working on this issue, verify it's still relevant and makes sense.**_ **Description** We need to decide how AI Context should attach context to existing Drupal objects such as Canvas/SDC components, entity fields, and Webform definitions. This issue is for discussion and design only. It should compare `third_party_settings`, bridge entities, source plugins, and scope plugins as integration patterns. Questions to resolve: - When should context be attached directly to another config/content entity? - When should it be represented as a source plugin? - Is `third_party_settings` appropriate for Canvas/SDC component context? - Should references use UUIDs for config portability? - How should export/import work? - How should cacheability and access be handled? - What follow-up issues should be created? Potential follow-ups: - Add SDC/Canvas component context integration - Add entity field context source - Add Webform context integration - Add config schema for third-party settings if that approach is chosen [x] AI Assisted Issue