**Attendees:** Aidan, Marcus, Emma, Bruno, Vidit, Darren ### AI Review overview build * Real implementation demoed, not a mockup; example review runs in about 20 seconds, targeting completion this weekend * Built with HTMX per row, now in Drupal core; the response returns row markup and replaces the row, so no React or hand-written fetch * Open gaps: top counter needs a little JS, thresholds still hard-coded at 50/80 thresholds, latest-result visual bug, missing play button ### Canvas generation and timeout * Akhil prototyping row-by-row generation, with a component-by-component variant, to check if output quality improves * Row-by-row also eases the timeout in the 1.x branch; AI 2.x Symfony Messenger stays the root-cause fix, possibly ready for Rotterdam ### Restricting tools UI — [#3552047](https://www.drupal.org/node/3552047) * Moves to Tool API as versioned, restricted tools; Marcus to rewrite with Michael Lander and close this issue ### Improve add/edit Agent UI — [#3552140](https://www.drupal.org/node/3552140) * Deprioritized; agent UI already improved and FlowDrop covers the need; tag to be removed ## Decisions * Keep focus on AI Review and CCC; defer the CCC to AI Review bridge until AI Review works on its own ## Questions - Re AI Review * Authoring the evaluation criteria themselves — the rules/prompts/examples a criterion uses so its scoring and feedback are actually good and consistent. (This ties to the June 1 "examples become a context-item bundle" decision and the "next big problem" framing.) ## Next Steps * **Aidan:** Spec the pill-shaped list-view widget; draft a functional and UI requirements issue for the Phase 2 feedback UI * **Marcus:** Rewrite #3552047 into a Tool API issue and remove the stalled-ticket tags * **Akhil:** Finish the row-by-row generation prototype and report on quality * **Bruno:** Finish the overview panel; * **Eric:** continue the CCC single-entity view > Related issue: [Issue #3584831](https://www.drupal.org/node/3584831)