## Description Follow-up to: #3586418+s Installing `ai_context` through a recipe or a config sync does not create the module's own config entities unless that recipe or sync explicitly supplies them. This is correct, intended Drupal behavior: `ConfigInstaller` runs in "syncing" mode for both paths, so `ai_context_install()` skips its workflow setup and `config/install/` is not applied on its own. A recipe is expected to be explicit about the config it wants, the same way core recipes name the config entities they need. The problem is that ai_context never says so anywhere, and the result is invisible. A recipe like: ```yaml name: 'Install AI Context' type: 'Site' install: - ai_context ``` produces a site where `ai_context_item` is not a moderated entity type: no `ai_context_editorial` workflow, no `moderation_state` field, no error, no log entry. The tags vocabulary, the usage view, and the default form and view displays are missing for the same reason. A site builder only finds out when the moderation UI isn't there. This was reported as a bug in #3586418 and closed as works-as-designed. The gap that remains is documentation plus visibility, not behavior. The test fixtures, install-path test coverage, and status-report warning drafted in !266 can be carried over to this issue. ## Tasks Two notes for whoever implements the warning. Procedural `hook_requirements()` is deprecated as of Drupal 11.3 and removed in 13.0, but adding `#[LegacyRequirementsHook]` to silence that deprecation *stops the function from running* on 11.3+ — it only makes sense paired with an OOP `hook_runtime_requirements()` implementation. `canvas.install` has the attribute without the counterpart, so don't copy that pattern. Separately, the int `REQUIREMENT_WARNING` severity is deprecated in favor of the `RequirementSeverity` enum, which doesn't exist on Drupal 10; while the module keeps `^10.5` support, the int constant is the pragmatic choice. * [ ] Document the recipe requirement in the module's docs: a recipe that installs `ai_context` must also import its config, either fully (`config: import: { ai_context: '*' }`) or by naming the specific config entities it needs, starting with `workflows.workflow.ai_context_editorial`. * [ ] Document the same requirement for config sync: a sync source that adds `ai_context` to `core.extension` must also carry the module's config, which a normal full export from a working site already does. * [ ] List which config entities a recipe or sync needs to supply, and what each one is responsible for (editorial workflow, tags vocabulary, usage view, default form and view displays). * [ ] Add a copy-pasteable example recipe to the docs that installs `ai_context` correctly. * [ ] Add a runtime `hook_requirements()` warning when `ai_context_item` is not attached to a moderation workflow, pointing at the docs and at Configuration › Workflow › Workflows. Salvage from !266. * [ ] Word that warning so a site that intentionally does not moderate context items understands it can be ignored, and confirm the module degrades cleanly in that state (see `AiContextItem::unpublish()`). * [ ] Add kernel coverage for the four install paths: full config sync, bare config sync, recipe without `config: import:`, and recipe with `config: import:`. Salvage `AiContextInstallationPathsTest` and the two recipe fixtures from !266. * [ ] Assert the warning through the hook system (for example `system.manager`'s `listRequirements()`) rather than by calling `ai_context_requirements()` directly, so the test also covers the hook being registered and invoked. ## Acceptance criteria * A site builder writing a recipe that installs `ai_context` can find, in the module's docs, what config the recipe must import and a working example. * A site where `ai_context_item` is not attached to a moderation workflow shows a warning on the status report explaining the consequence and how to fix it. * That warning does not appear during `drush updatedb` or `drush config:import`, and does not appear on a correctly configured site. * All four install paths are covered by automated tests, and the two that legitimately leave the item unmoderated assert both the absence of the workflow and the presence of the warning. * No config is created automatically after a config import or recipe apply; the module does not self-heal. ## Testing instructions *(added by implementor before review)* 1. ## Related issues #3586418+s ## AI disclosure - [x] AI assisted issue