## Description The AI module already ships a `create-guardrail-plugin` agent skill that *authors* new guardrail plugin classes. There is, however, no equivalent skill for *operating* the guardrails that already exist — i.e. configuring them on a running site. Site builders and agents currently have to drive the admin UI by hand to wire up guardrails, guardrail sets, and the global guardrail list. This task adds a `setup-guardrails` skill (sibling of `create-guardrail-plugin`, under `ai/.agents/skills/`) that configures guardrails rather than creating them, driven through the [Tool module](https://www.drupal.org/project/tool)'s tools via `drush tool:run`. Note on architecture: the generic `tool_belt` entity tools are content-entity only (they require `ContentEntityInterface` and use field/cardinality APIs), so they cannot manage the guardrail **config** entities (`ai_guardrail`, `ai_guardrail_set`) or the `ai.settings:global_guardrails` simple-config value. Dedicated guardrail-management tool plugins are therefore needed so the skill can perform each action as a well-defined, access-checked tool invocation. Because the Tool module is **not** a dependency of the AI module, the skill must enable it with drush when it is not already enabled, and uninstall it again afterward if — and only if — the skill enabled it, leaving the site's module state unchanged. ## Tasks * [ ] Add the `setup-guardrails` skill under `ai/.agents/skills/setup-guardrails/`. * [ ] Provide the guardrail-management tool plugins the skill invokes via `drush tool:run`. * [ ] Set up, edit, and delete a guardrail (`ai_guardrail`) — deletion always requires explicit confirmation. * [ ] Set up, edit, and delete a guardrail set (`ai_guardrail_set`) — deletion always requires explicit confirmation. * [ ] Set up and edit the global guardrails (the sets applied to every AI request, stored in `ai.settings:global_guardrails`). * [ ] Enable the Tool module via drush when it is disabled, and uninstall it again only if the skill enabled it. ## Acceptance criteria * A guardrail, a guardrail set, and the global guardrail list can each be configured end to end without using the admin UI. * Deleting a guardrail or a guardrail set never proceeds without explicit user confirmation. * The site's enabled-module state is identical before and after a skill run (the Tool module is restored to its prior state). * The skill clearly distinguishes itself from `create-guardrail-plugin` (operate vs. author). ## Related issues Relates to the global guardrails work in #3584851.