### Problem/Motivation 1.0.0-beta3 resolved the operational blockers (support matrix `^10.5 || ^11` with previous-major CI, connector result lifecycle, REST serialization conflicts, the post-#3582933 bug cluster). What remains before RC1 is the API freeze — RC means no further interface changes — plus the security posture items drupal.org review will check, and documentation. ### Remaining tasks **API freeze (must land before the RC1 tag):** - [ ] [#3582959](https://www.drupal.org/project/tool/issues/3582959): Configuration-sourced input values are broken end-to-end - [ ] [#3582960](https://www.drupal.org/project/tool/issues/3582960): Multiple-value input validation only validates the first item - [ ] [#3582961](https://www.drupal.org/project/tool/issues/3582961): `ToolBase::access()` throws on invalid input instead of returning forbidden - [ ] [#3582962](https://www.drupal.org/project/tool/issues/3582962): Signature corrections batch: return-type union, nullable result values, broken `create()`, `prepareExecutableValue()` visibility, `Transform` idempotency - [ ] [#3582963](https://www.drupal.org/project/tool/issues/3582963): Prefix module-owned identifiers: alter hook, cache key, `text` data type ID - [ ] [#3582964](https://www.drupal.org/project/tool/issues/3582964): Tool execution contract rework: result naming, concrete typing, and decoupling from core `ExecutableInterface`'s scheduled `execute($object)` signature change - [ ] [#3582975](https://www.drupal.org/project/tool/issues/3582975): `checkRequirements()` is frozen API that nothing calls — wire it: enforce at execute, exclude from machine surfaces, show as unavailable-with-reason in human surfaces - [ ] [#3582965](https://www.drupal.org/project/tool/issues/3582965): Cacheability: implement `getCacheContexts()` or drop `CacheableDependencyInterface` - [ ] [#3582966](https://www.drupal.org/project/tool/issues/3582966): `@api`/`@internal` sweep + `tool.api.php` — includes the new `src/Handle/` namespace and normalizer services - [ ] Decide #3582944 (pre/post-execute events): implement, or close as fulfilled by the transform events — record either way **Security posture:** - [ ] **TBD — per-invoker tool exposure control.** Deliberately not filed yet: the original framing (per-tool opt-in for AI exposure) may be half of the real feature — the inverse case (tools that should _only_ be exposed to AI, or only to a specific invoker class) looks equally plausible. The scope question is whether this becomes a general per-invoker visibility model rather than an AI-specific opt-in; [#3582977](https://www.drupal.org/project/tool/issues/3582977)'s capability-declaration escalation path is the same design space. To be scoped into an issue once the model is clearer; `lifecycle: experimental` on tool_ai_connector rides with whatever shape this takes. - [ ] [#3582967](https://www.drupal.org/project/tool/issues/3582967): Harden `administer tool` permission - [ ] [#3582968](https://www.drupal.org/project/tool/issues/3582968): Tool Explorer execute form error handling - [ ] [#3582970](https://www.drupal.org/project/tool/issues/3582970): Drush hardening: `--uid` default, silent input drops, exit codes **Improvement track (explicitly NOT freeze-bound — RC window or 1.0.x):** - [ ] [#3582972](https://www.drupal.org/project/tool/issues/3582972): Schema constraint/format gaps in the normalizers (overlaps #3582943 Deliverable A) - [ ] [#3582973](https://www.drupal.org/project/tool/issues/3582973): Input coercion gaps for unambiguous LLM value shapes - [ ] [#3582976](https://www.drupal.org/project/tool/issues/3582976): Drupal core CLI alignment: metadata mapping, typed-outputs advocacy, future CLI invoker - [ ] [#3582977](https://www.drupal.org/project/tool/issues/3582977): Filter workflow-only tools from one-shot CLI invokers - [ ] [#3582943](https://www.drupal.org/project/tool/issues/3582943): Introspectable tool declarations over CLI + enriched input schema — the umbrella proposal this track hangs off: Deliverable A overlaps [#3582972](https://www.drupal.org/project/tool/issues/3582972); Deliverable B (introspectable operation kind, destructive flag, typed outputs, access, static requirements) is the metadata surface that [#3582976](https://www.drupal.org/project/tool/issues/3582976), [#3582977](https://www.drupal.org/project/tool/issues/3582977), and the advertisement half of [#3582975](https://www.drupal.org/project/tool/issues/3582975) all consume - [ ] [#3562612](https://www.drupal.org/project/tool/issues/3562612): Optional logo/image per tool (and possibly per group), settable by derivers — design then implement. Freeze note: keep it additive metadata (optional attribute/definition property), which is safe to land post-1.0 - [ ] [#3572774](https://www.drupal.org/project/tool/issues/3572774): File input handling — research/design phase, still being scoped. One freeze-relevant check to do early: confirm the design needs only _additions_ to the input-definition family (new definition classes/data types are non-breaking post-1.0); if it would change the base input contracts, that must be known before #3582964 freezes them. Design note: file entities are content entities, so the entity handle store already carries them — the reference-to-file conversion step may partially exist via the handle pattern. **Rides along to rc1:** - [ ] [#3582974](https://www.drupal.org/project/tool/issues/3582974): Trait/definition-pipeline test coverage residue — pins the frozen contract - [ ] [#3582969](https://www.drupal.org/project/tool/issues/3582969): Tool Explorer cleanup + first functional test - [ ] [#3582971](https://www.drupal.org/project/tool/issues/3582971): Translatable messages / stop surfacing raw exception text - [ ] Docs: land [#3582955](https://www.drupal.org/project/tool/issues/3582955) (README + plugin guide) and [#3552983](https://www.drupal.org/project/tool/issues/3552983) (Quick Start Guide — not a blocker, but the adoption-side counterpart to the API docs; MR !21 exists as a starting point); add `hook_help()` - [ ] composer.json: add `drush/drush` to require-dev; `suggest` drupal/ai - [ ] Queue hygiene: migrate tool_belt-scoped issues (\~12), close #3543445 (already done in code), retire #3558327 into this meta **In flight (MR green, pending merge):** - [#3582958](https://www.drupal.org/project/tool/issues/3582958): Entity handle descriptions are HTML-escaped in LLM-facing schemas ### API changes Frozen at RC1: everything in `src/`, including `src/Handle/`, `src/Event/`, the normalizer services, and the expanded `ToolInterface`. ### AI usage (if applicable) - [x] **AI Assisted Issue:** This issue was generated with AI assistance, but was reviewed and refined by the creator. - [ ] **AI Assisted Code:** This code was mainly generated by a human, with AI autocompleting or parts AI generated, but under full human supervision. - [ ] **AI Generated Code:** This code was mainly generated by an AI with human guidance, and reviewed, tested, and refined by a human. - [ ] **Vibe Coded:** This code was generated by an AI and has only been functionally tested.