## Problem Parent: #3586427+s Depends on Step 1: #3586385+s / !267 (done) Step 4 of the Inside AI Rotterdam CCC recipe PoC. Steps 2 and 3 cover other agent-based consumers (Answers and translate). This issue wires the university context items into **Canvas AI agents**, once the Canvas AI recipe is available. The Canvas AI recipe is still coming. Exact agents, settings, and recipe actions will be updated after that recipe can be applied locally. ## Proposed resolution When the Canvas AI recipe is available, update the university demo recipe (currently `recipes/ai_context_demo_university/` in `ai_context`) so that: 1. CCC agent/consumer settings subscribe the demo's Canvas AI agents to the university context items. 2. Any extra CCC admin defaults needed for Canvas AI are set via config **actions**, not by importing a full settings file. 3. The recipe still does **not** install `canvas_ai`, `canvas_dev_ai`, or the Canvas AI recipe. Those come from the coming recipe / the starter template. Until #3586346+s lands, configure the current agent-based consumer subscriptions. When the generic consumer config shape is available, switch the recipe to that action if needed. If Canvas AI is **not** in the demo, document that decision here and close this issue without recipe changes. ## Recipe placement Keep working in the `ai_context` recipe for now so this can be tested against 1.0.x-dev. The whole recipe is expected to move to a GitLab demo repo later (tracked on the meta). Do not apply this recipe automatically on `ai_context` install. ## Acceptance criteria - [ ] Canvas AI recipe is available enough to apply locally (even if still in progress). - [ ] Canvas AI recipe applied locally (not as a dependency of this CCC recipe). - [ ] Canvas AI agents that need CCC configuration are identified. - [ ] Demo-scope decision recorded: Canvas AI is in / out of the Rotterdam demo. - [ ] If in scope: CCC agent/consumer settings route university context into those Canvas AI agents. - [ ] If in scope: agents debugger shows context injection for the Canvas AI agents. - [ ] If in scope: recipe updated with only this demo's Canvas AI subscriptions / settings. - [ ] If in scope: re-applying the recipe does not duplicate context items or wipe unrelated CCC config. - [ ] If in scope: kernel/test coverage updated for the new settings (or omission explained). - [ ] If in scope: README updated for the new apply result and any new prerequisites. - [ ] If out of scope: issue updated with the decision and no recipe change. ## Out of scope - #3586385+s — Step 1: install CCC and university context items (done / in !267). - #3586424+s — Step 2: Answers agent/consumer configuration. - #3586425+s — Step 3: translate agent/consumer configuration. - #3586426+s — Step 5: CKEditor / non-agent consumer configuration. - Installing Canvas AI, content types, or the university corpus from this recipe. - Writing the Canvas AI recipe itself (that recipe is coming separately). - Implementing the generic consumer configuration API (that is #3586346+s). - Starter template reference, Drupal Forge install, pinned versions, and demo page draft: #3586427+s and ai_initiative#3586678+s. - Final Aidan copy for the context items. ## Work 1. Wait for the Canvas AI recipe (or test against its MR / local checkout). 2. Apply that recipe locally on the university demo site. 3. Identify which Canvas AI agents need CCC configuration (page builder / component agents). 4. Update CCC agent/consumer settings for those agents. 5. Test those agents with agents debugger and confirm context is injected. 6. Confirm Canvas AI is part of the Rotterdam demo. 7. If it is, update the university CCC recipe with those agent/consumer settings. ## Demo scenario (verification) Only if Canvas AI is in the demo: 1. Apply the updated university demo recipe (and the separate Canvas AI / corpus recipes as needed). 2. Confirm the three university items from Step 1 are still present. 3. Use a Canvas AI agent on a demo page (for example the page builder chat or component agent). 4. Confirm the agent uses the university guidelines (visible in agents debugger). 5. Change one guideline and run the same Canvas AI task again. 6. Confirm the result changes. The primary on-stage Answers scenario stays on #3586424+s / #3586427+s / ai_initiative#3586657+s. ## Technical notes This step is agent-based, like Steps 2 and 3. Agents debugger is the expected injection check. Prefer configuration **actions** on the existing recipe. Importing a complete `ai_context.settings` file can overwrite unrelated existing configuration. The consumer action should add/update **only this demo's** Canvas AI subscriptions. ```yaml # Direction of travel — exact keys TBD after the Canvas AI recipe # exists and local testing names the agents. config: actions: ai_context.settings: simpleConfigUpdate: # Optional demo admin defaults (e.g. token limit). # Agent / consumer subscriptions for Canvas AI. # Use #3586346+s shape when available. ``` Do not add `canvas_ai` or the Canvas AI recipe to this recipe's `install:` or `recipes:` list just to satisfy subscriptions. The starter template (or a later integration pass) controls apply order. If subscriptions require Canvas AI to be present first, document that prerequisite in the recipe README. Do not make this CCC recipe own that module. ## Dependencies - #3586385+s / !267 — Step 1 recipe with the three university items. - #3586339+s — higher-education context content source and licensing. - #3586346+s — generic consumer configuration (recipe subscription shape). Nice to have if an MR exists; not a hard blocker for agent-based config. - Canvas AI recipe (coming) available on the test site (applied by another recipe / manually). ## Related - Parent meta: #3586427+s - Sibling steps: #3586385+s, #3586424+s, #3586425+s, #3586426+s - Demo scenario: ai_initiative#3586657+s - [ai_recipe_context](https://www.drupal.org/project/ai_recipe_context) — empty generic recipe; unlikely to be used here. ## AI disclosure - [x] AI assisted issue