## Problem/motivation Follow-up to: #3586202 _**Verify this is still an issue and the solution approach before proceeding**_ _**Assess if this should be pre-RC1 or post-1.0 and move for the latter**_ `AiContextSubcontextResolver::resolveConditionalChildren()` can make one synchronous provider `chat()` call per selected parent that has conditional children. This may dominate agent latency and provider usage compared with normal selection and rendering. Treat this as RC1 work if conditional subcontext is part of the RC1 product promise. If it is advanced functionality, it can be deferred or guarded more strictly. ## Solution Recommended options: - Keep conditional subcontext disabled unless explicitly configured. - Cap the number of conditional parent decisions per selection. - Batch decisions when possible. - Cache repeated decisions where the task, parent, and candidate children are identical enough to make caching valid. - Consider falling back to required-only children when latency budgets are tight. ## Tasks - Check against other issues to make sure it wasn't separately reported - Verify this is still an issue before proceeding - Verify the solution approach before proceeding - Update code - Review and test ## AI usage disclosures - [x] AI Assisted Issue - [ ] AI Assisted Code - [ ] AI Generated Code