## Problem/Motivation project/modeler_api#3588517 added four third-party settings that let a model express the recipe metadata it previously could not: `summary`, `recipes`, `config_actions` and `export_config`. It landed on `modeler_api` `1.1.x` (`84502f7`), and `ExportRecipe` now reads them, so a re-export is idempotent and a UI edit is a legitimate way to produce a recipe release. The Workflow Modeler does not carry them yet, so today they can only be set through configuration, a recipe, or the API — not in the modeler, which is where every other piece of model metadata is edited. `WorkflowModeler::export()` assembles `$metadata` from the owner: ```php $metadata = [ 'label' => $owner->getLabel($model), 'documentation' => $owner->getDocumentation($model), 'executable' => $owner->getStatus($model), 'tags' => $owner->getTags($model), 'changelog' => $owner->getChangelog($model), // … ]; ``` and the getters read it back: ```php public function getChangelog(): string { return $this->metadata['changelog'] ?? ''; } ``` The four new values are absent from both halves, and from `MetadataModal`. ## The hazard, which is the reason to be careful here `modeler_api`'s new modeler getters deliberately return **`NULL`, not an empty value**. `Api::prepareModelFromData()` skips the setter when a getter returns `NULL`, so a modeler that predates #3588517 cannot wipe these settings on save. `NULL` means "this modeler does not carry this value"; `''` or `[]` means "the user cleared it". That distinction has to survive into the React layer. `MetadataModal` currently normalizes with `|| ''`: ```ts documentation: metadata?.documentation || '', changelog: metadata?.changelog || '', ``` Applied to the new keys, that turns *absent* into *empty*, and the modal would then post `summary: ''` on every save — which `modeler_api` reads as a deliberate clear. **Opening the metadata dialog and pressing save would silently erase a summary a recipe had just installed.** The same applies to `recipes`, `config_actions` and `export_config`. So the modal must omit a key it never received rather than defaulting it, and the PHP getters must return `NULL` for an absent key rather than `''`/`[]`. ## Proposed resolution 1. **`WorkflowModeler::export()`** — add the four values to `$metadata` from the owner's new getters. 2. **`WorkflowModeler` getters** — implement `getSummary()`, `getRecipes()`, `getConfigActions()` and `getExportConfig()` reading `$this->metadata[...] ?? NULL`. Note the `?? NULL`, in contrast to the existing getters' `?? ''`. 3. **`ui/src/types/settings.ts`** and **`ui/src/types/pluginApi.ts`** — add the four optional fields to the metadata shapes (there are two declarations of `changelog?: string` in `settings.ts`; check whether both need it). 4. **`ui/src/components/MetadataModal.tsx`** — add the fields: `summary` a single-line input; `recipes` and `export_config` lists, one entry per line; `config_actions` a YAML textarea with the JSON/YAML constraint treatment the module already uses for structured fields. **Do not normalize absent to empty** for these four. 5. **`composer.json`** — the metadata round trip only works against a `modeler_api` release that contains #3588517, so the constraint needs raising once that release is tagged. 6. Test coverage for the absent-versus-empty distinction in both layers — a save that never touched these fields must leave them untouched. ## Remaining tasks - [ ] Carry the four values through `WorkflowModeler::export()` and its getters, with `NULL` for absent - [ ] Extend the TypeScript metadata types - [ ] Add the fields to `MetadataModal` without collapsing absent into empty - [ ] Raise the `modeler_api` constraint once a release carries #3588517 - [ ] Tests: opening and saving the metadata dialog does not clear values the modeler did not receive ## Related - `modeler_api` #3588517 — added the settings and the `NULL` semantics - `modeler_api` #3588509 / #3588516 — the preservation approach this replaces - `drupal/documentation/eca#111` — the ECA Guide issue that motivated the chain