## Problem/motivation Follow-up to: #3586258+s Parent: #3586298+s **8. Configuration Policy Checks** **Priority:** Low to Medium **Why group these together:** These are not confirmed bugs. They should be handled as maintainer decisions or reproducibility checks before code changes. Includes: - Reproduce or dismiss simple config dependency concerns. - Confirm Scheduler dependency policy. ## Solution ### 8.1 Verify simple install config dependencies **Files:** - `config/install/ai_context.settings.yml` - `config/install/ai_context.agents.yml` - `config/install/ai_context.scope_settings.*.yml` - `config/install/taxonomy.vocabulary.ai_context_tags.yml` **Problem:** Some simple install config files do not declare top-level dependencies. No config import failure was reproduced during verification. **Recommended fix:** - Run a targeted install/export/import or config sync test. - If failures or warnings are reproduced, add the required dependencies. - If no issue is reproduced, document this as accepted or leave unchanged. ### 8.2 Confirm Scheduler is intentionally required **Files:** - `ai_context.info.yml` - Scheduler-related install config **Problem:** Scheduler and Scheduler Content Moderation Integration are hard dependencies. That is internally consistent with install config, but some reviews questioned whether Scheduler should be optional. **Recommended fix:** - Maintainers should confirm product intent. - If Scheduler is required, no action is needed beyond perhaps documenting why. - If Scheduler should be optional, this becomes a larger dependency/config refactor and should be handled separately. --- ## AI usage - [x] AI assisted issue