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 support context from sources beyond manually authored context items, including documents, URLs, Google Drive, analytics, entity fields, Webforms, and federated sites. This issue is for discussion and design only. It should define whether AI Context needs a source plugin API, what the initial interface should look like, and what responsibilities belong in the base framework versus individual integrations. Questions to resolve: - Should we introduce a context source plugin type? - Should the interface be marked experimental at first? - What methods and data structures should source plugins expose? - How should sync modes work: manual, scheduled, event-driven, or live? - How should cacheability, stale data, errors, and retries be represented? - How do source items participate in scope selection? - What follow-up issues should be created? Potential follow-ups: - Add context source plugin manager/interface - Add remote/dynamic context framework - Add context ingestion wizard - Add Google Drive source - Add Google Analytics source - Add knowledge base / many-URLs source - Add entity field source - Add Webform source - Add hot/warm/cold context caching [x] AI Assisted Issue