Follow up to: #3582494 _**NOTE: Before working on this issue, verify it's still relevant and makes sense.**_ **Description** We need to decide whether AI Context should continue treating context item content as one text body or introduce a clearer content format model for different things, e.g. Markdown, JSON, structured context, templates, imported content, AI-assisted authoring. This issue is for discussion and design only. The main decision is whether to reserve or introduce a `content_format` field or another storage/API model before the content entity schema becomes harder to change. Questions to resolve: - Should context items have an explicit `content_format`? - Which formats should be supported initially, e.g. Markdown, JSON, other - Is `content_format` a hidden schema reservation or exposed UI? - How should rendering behave for different formats? - How does this affect templates, document ingestion, and AI authoring tools? - What follow-up issues should be created? Potential follow-ups: - Add `content_format` base field - Add JSON/structured context output support - Add starter templates - Add document/URL ingestion wizard - Add AI assistant for authoring context [x] AI Assisted Issue