A "formated text, long, with summary" field can be filled via AI Automator, which in my case functions very nicely. (Thank you AI team). But we noticed, that the "summary" which comes with that field is left empty. I know that there are display options like "smart trim" or so, but having the AI to summarize a huge text field into one or two sentences is not possible. We will work around that by telling AI to create a summary within the main field and add `<d-summary>....</d-summary>` and extract it via post-processing or so. But a checkbox, with a sub-prompt for that extra-field would be nice. <details> <summary>Contextual information for getting started</summary> ## Context The **ai_automators** module lets you attach AI "automator" rules to entity fields so an LLM populates them on save. The **LLM: Text** automator (`LlmTextWithSummary.php`) targets `text_with_summary` fields (e.g. the standard Article **Body**) and currently generates only the main text — the optional **Summary** that ships with that field type is left empty. Your change adds a checkbox plus an optional sub-prompt to the automator's settings so it also generates and writes the field's summary, with the schema, subform, and processing wired in. ## Why does this matter Editors using `text_with_summary` fields get a fully written body but an empty summary, so they must hand-write it or fall back to display-only trimming — or the issue reporter's workaround of embedding a `<d-summary>…</d-summary>` block in the body and extracting it in post-processing. A first-class option removes that friction and makes the summary genuinely AI-authored. ## Acceptance After the change, the LLM: Text automator offers an opt-in checkbox and sub-prompt that, when enabled, make it generate and store the field's summary in addition to the main text; the summary lands in the field's `summary` value on save. With the option left off (and for existing configs that predate it), the automator behaves exactly as before — main text only, summary untouched — and config schema validation/export-import still passes. Worth flagging in the MR: confirm the default is off so upgrades don't silently start writing summaries, and decide how an empty/failed summary response is handled (leave blank vs. error). </details>