tags. After the project summary prose, add a single subsection titled "

How can I help on this project?

" aimed at a developer. Suggest 2-3 concrete technical actions a contributor could take right now. Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, check the data for each issue: - If an issue shows a Related MR with state 'opened', do NOT suggest creating a patch or MR — one already exists. Suggest reviewing it instead. - If all Related MRs for an issue are merged, do NOT suggest reviewing them — they are already done. - If an issue is unassigned with no Related MRs, it is a good candidate to pick up. - Only suggest actions that are genuinely still needed given the current state in the data above. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Add detail logic to the playground pipelines and add the ability to show the debug data by clicking on the executed pipeline item](https://git.drupalcode.org/project/flowdrop/-/work_items/3589741) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: Shibin Das (D34dMan) | Labels: state::accepted, v1.x-dev Description: >>> [!note] Migrated issue Reported by: [gxleano](https://www.drupal.org/user/3591999) >>> Add detail logic to the playground pipelines and add the ability to show the debug data by clicking on the executed pipeline item ### [A state update is applied through the reducers after the node completes (SG-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592366) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `state_update` output applied through reducers post-completion; never exposure-stripped (= EXPO-12). - **Implementation:** `:1347-1351` - **Guaranteed by:** Rule `SG-3` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [What the runtime hands a node, and what the node must declare to see it (SG-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592365) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Three independent guarantees. **(1)** The runtime input array handed to `executeNode()` carries `__state__` (the full `GraphState::toArray()`), `__messages__` (message arrays) and `__data__`, plus `__iterator__` and `__current_item__` whenever the state has an iterator, plus `__interrupt_id__` when the job is a resume. A processor only *sees* one of these if it declares it as a parameter — an `__`-prefixed parameter is "internal" and always accepts its runtime input (= CFG-8/CFG-13). **(2)** Independently, the current `GraphState` is passed via `setGraphState()` to processors implementing `Sta… ### [How each state field is reduced (SG-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592364) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Reducers by field: messages=append, data/metadata=merge, rest=replace; absent field keeps value; state immutable. - **Implementation:** `GraphState.php:62-79` - **Guaranteed by:** 4 + 3 reducer suites Rule `SG-1` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-1` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [An engine that cannot consume a snapshot must throw (INT-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592363) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: An engine that cannot consume a given snapshot MUST **throw** `OrchestrationException` naming the snapshot, never silently discard-and-restart (restart re-fires side-effecting nodes). The two sync engines (`SynchronousOrchestrator`, `SynchronousPipelineOrchestrator`) have no snapshot-seeding mechanism, so ANY attached snapshot is refused before a pipeline or job exists; "no snapshot present" stays a plain fresh start (OPEN-10 part b; narrows an earlier "replay completed nodes on every engine" conclusion, which is unachievable: `toSnapshotData()` emits no completion set and both loop engines de… ### [A terminal snapshot is not resumable (INT-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592362) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: A terminal snapshot (COMPLETED/FAILED/CANCELLED) is **non-resumable** (OPEN-10 part a): the snapshot-consuming engines throw `OrchestrationException` naming the snapshot and its status before any pipeline is created. The same gate covers SG-12's *explicit* checkpoint-resume arm (a checkpoint capturing a terminal `GraphState` refuses to restore, naming the checkpoint). Thread continuity is deliberately NOT gated: restoring a thread's latest checkpoint (typically the previous turn's `workflow_end` state) seeds a NEW turn with accumulated conversation state — sessions depend on it — and is not a … ### [A checkpoint round-trip preserves which terminal status it was (INT-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592361) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: The checkpoint round-trip preserves the terminal-status distinction — **CANCELLED included**. The state carries its outcome as a `status` string (`completed`/`failed`/`cancelled`; NULL while the run is live) and the checkpoint payload persists it, because `isComplete` alone cannot tell cancellation from completion. A Cancel signal marks the state cancelled and writes the final `workflow_end` checkpoint, and the persisted status — never a re-derivation — becomes the WorkflowSnapshot status. **Dual read (mandatory, no data migration):** a payload written before the field carries no `status` key … ### [An async handover seeds the queued run from the snapshot (INT-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592360) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Async handover: queued run seeded from snapshot as pre-completed `injected` jobs. Each seeded job is COMPLETED carrying the snapshot's output plus the marker triple `injected` / `injected_from_snapshot` (source executionId) / `injected_at`, so the queue worker schedules only genuinely-remaining work and nothing mistakes a seeded row for work this run performed. A snapshot node with no matching job warns and is skipped; the count is reported as `results.injected_jobs` / `metadata.injected_node_count`. - **Implementation:** `AsynchronousOrchestrator.php:136-144`, `::initializeJobsFromSnapshot()… ### [Saving a snapshot is an upsert keyed by execution id (INT-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592359) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `EntitySnapshotStorage::save()` is an **upsert keyed by executionId**: an existing entity with the same `execution_id` is loaded and overwritten in place via `fromWorkflowSnapshot()`, so one execution never accumulates two snapshot rows; otherwise a new entity is created from the DTO. Every query in this service deliberately runs with `accessCheck(FALSE)` — snapshot access is **NOT** enforced here, it is enforced at the API layer (see `SnapshotAccessTest`), and cron cleanup runs with no user context. `cleanup($olderThan, $statuses)` deletes entities with `created < $olderThan` AND, when `$stat… ### [Snapshot validation returns a fixed set of codes (INT-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592358) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `validateSnapshot()` returns a `ValidationResult` whose codes are the contract: `ERROR_VERSION_MISMATCH` — only when the snapshot's `workflowVersion` is non-empty, an empty version **skips** the check and is not an error; `ERROR_UNKNOWN_NODE` per snapshot node absent from the definition; `ERROR_DEPENDENCY_NOT_MET` per completed node whose dependency has no state or is neither completed nor skipped; and — warnings only, which never make the result invalid — `WARNING_ORPHAN_NODE` per definition node missing from the snapshot and `WARNING_INJECTED_WITHOUT_DEPENDENCY` per *completed* injected node… ### [The workflow version hashes structural data only (INT-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592357) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `workflowVersion` = 16-hex sha256 over structural data only (labels/positions don't change it). - **Implementation:** `WorkflowStateManager.php:256-284` - **Guaranteed by:** Rule `INT-7` of `RT-INT` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: INT-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592098 ### [What a snapshot carries (INT-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592356) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `generateSnapshotFromPipeline()` builds a `WorkflowSnapshot` carrying `workflowId` (`"unknown"`, and an empty `workflowVersion`, when the pipeline has no workflow), the structural `workflowVersion`, the executionId, the caller-supplied status, one `NodeSnapshot` per job keyed by node id, `initialInput` = the pipeline input, and metadata `{orchestrator_type, pipeline_id}`. Per job, `createNodeSnapshotFromJob()` maps JobStatus→NodeSnapshot status one-to-one except `skipped` and `cancelled`, which BOTH become `skipped`, and any unrecognised status, which becomes `idle`; `output` is carried only f… ### [A pipeline signal is polled between jobs, never mid-job (INT-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592355) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `pollPipelineSignal()` runs between job iterations — the in-flight job always finishes first — and dispatches `PipelineSignalPollEvent`; a NULL signal continues the loop. **Cancel:** `markAsCancelled()` + `execution_time_us` stamped on the execution context, then BOTH `ExecutionCancelledEvent` and a `PipelineCompletedEvent` carrying `PipelineStatus::Cancelled` — cancellation is announced like any other terminal outcome, so session notices and sub-workflow sentinels fire (= ORC-15) — returning a response with status `cancelled` and metadata `orchestrator_type`/`signal_id`/`reason`; the flowdrop… ### [The four conditions for a node to own a resume (INT-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592354) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Resume ownership gate (all 4): bag has `__interrupt_id__`, processor Resumable, interrupt resolved, `job_id` matches; else fall through to `process()` (safe re-ask). - **Implementation:** `NodeRuntimeService.php:185-191,462-496` - **Guaranteed by:** 5 + 2 contract suites Rule `INT-4` of `RT-INT` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: INT-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592098 ### [Resolving an interrupt resets the job and resumes the pipeline (INT-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592353) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Resolution: find job by `job_id`, reset PENDING, resume only if pipeline PAUSED, via declared orchestrator; stateless run → no resume. The reset and the resume are **separate steps in that order** — the job goes back to PENDING unconditionally, and a non-PAUSED pipeline is then left strictly alone (never re-entered, so two executors cannot race). The stamped `job_id` is the primary lookup; the node-id pipeline scan is only the legacy fallback. - **Implementation:** `InterruptResolvedSubscriber.php:72-140` - **Guaranteed by:** 3 tests (`InterruptPauseAndResolutionContractTest`: job_id lookup +… ### [The interrupt entity is persisted by a subscriber (INT-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592352) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Interrupt entity persisted by subscriber; orchestrator reads from event/metadata, never the immutable exception. - **Implementation:** 2 sites - **Guaranteed by:** Rule `INT-2` of `RT-INT` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: INT-2` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592098 ### [An interrupted node pauses the pipeline and reports where it stopped (INT-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592351) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Node interrupt → job INTERRUPTED + `interrupt_id`, pipeline PAUSED, response carries `interrupt.*` + partials. The response shape is part of the rule: status `interrupted`, `metadata.interrupt.interrupt` = the persisted interrupt's API array (id/nodeId/status), `metadata.pipeline_id`, and `results` holding every node that completed before the interrupt. - **Implementation:** `AbstractOrchestratorBase.php:271-299`; pause + response `SynchronousPipelineOrchestrator.php:356-374`; payload `InterruptHandlingTrait::handleInterruptException()` - **Guaranteed by:** 1 test asserting all four together … ### [Tools are handed to a processor only when there are some (DATA-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592350) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `NodeRuntimeService` calls `setTools()` only when the projection is non-NULL **and** the processor instance is `ToolsAwareInterface` — a non-consumer with tools wired receives none at runtime (at compile time that wiring is already a validation error, `ToolConsumerValidator`; a `ToolPassthroughInterface` box is accepted there and forwards instead). Under StateGraph the projection is rebuilt **per job** from the workflow's stored graph data — re-enriched via `NodeMetadataResolver`, with the derived `DependencyGraph` memoised per workflow id — rather than read from a compiled pipeline, which is … ### [The model-facing tool schema omits parameters already filled (DATA-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592349) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Model-facing tool schema omits pinned-in-config and edge-fed params. - **Implementation:** `:126-135` - **Guaranteed by:** (3) Rule `DATA-11` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [Tool availability projects into tool bindings, not into data (DATA-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592348) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `tool_availability` projects into ToolBindings (flattened through ToolBox), not a data delivery; passthrough cycle → `ToolWiringException`. - **Implementation:** `ToolProjector.php:65-122` - **Guaranteed by:** (4 + flattener) Rule `DATA-10` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-10` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [The unified output port composes exposed outputs only (DATA-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592347) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Unified I/O `output` port composes exposed outputs only, excluding `_`-prefixed and `trigger`; an output key the node type does not configure defaults to exposed (kept). - **Implementation:** `NodeRuntimeService.php:823-851` - **Guaranteed by:** `NodeRuntimeServiceUnifiedOutputCompositionTest` (9 rows) + EXPO-14 ordering test Rule `DATA-9` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-9` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [The effective execution config is stamped on the pipeline (SG-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592376) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: The effective `ExecutionConfig` — including the resolved `threadId` and `checkpointerType` — is stamped on `$pipeline->getExecutionContext()['stategraph_config']` alongside `orchestrator_type`, and the re-stamp (plus its save) is skipped when both values are already exactly what would be written. A later resume or deferred launch rebuilds via `ExecutionConfig::fromArray()` on that key; only when the key is absent does it fall back to the workflow's `orchestrator_settings.stategraph` (plus a root `timeout`), then to defaults bounded by the caller's max-iterations. - **Implementation:** stamp `… ### [Which stored state a resume restores, in order (SG-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592375) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: State restore precedence: initialSnapshot → resumeFromCheckpoint (missing id warns+fresh; terminal checkpoint throws — INT-14's gate) → latest for threadId (deliberately ungated: thread continuity seeds a new turn, see INT-14; a terminal seed keeps everything accumulated but has its outcome — `isComplete`, `error`, `status` — cleared so the new turn reports its own result, see INT-13) → fresh. - **Implementation:** `orchestrate()` snapshot arm + `initializeState()` - **Guaranteed by:** 4 tests in `StateGraphResumeRefusalTest` (snapshot outranks an explicit checkpoint — proven by a TERMINAL ch… ### [A checkpoint per node, chained, plus one at the end (SG-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592374) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Checkpoint per node (chained `parentId`) + final `workflow_end`; memory checkpointer request-scoped; entity checkpointer persists; unknown type → `InvalidArgumentException`. - **Implementation:** `:813-821,947-954`; factory - **Guaranteed by:** 5 suites Rule `SG-11` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [The reserved trigger port means no branch for loopback naming (SG-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592373) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Reserved `trigger` source port = "no branch" for loopback naming. - **Implementation:** `:1684-1691` - **Guaranteed by:** Rule `SG-10` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-10` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [An edge condition never routes (SG-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592372) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `data.condition` never routes — not even on a loopback edge, the one place dispatch really decides; warning once per edge per resolution of its source's outgoing edges (= EDGE-8). - **Implementation:** `outgoingEdges()` - **Guaranteed by:** `StateGraphRemovedEdgeConditionTest::testConditionDoesNotGateLoopReentry`, `::testConditionedEdgeIsStoredWarnedAndFollowed` Rule `SG-9` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-9` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3… ### [How a repeated node's result is keyed (SG-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592371) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Two behaviours. **(a) Response keying** — the first execution of a node lands in `results` under the bare `nodeId`; each later execution lands under `"{nodeId}:{n}"` with `n` = that node's zero-based prior-execution count in this run (`node`, `node:1`, `node:2`…), and a `WorkflowStopException` payload uses the same key. The interrupt/partial-results path re-derives an equivalent scheme from storage rather than sharing the counter: completed jobs are walked in job-id order and keyed by the job's `loop_iteration` metadata when it carries one, else by the running per-node occurrence count. **(b) … ### [Loopback re-entry needs an active branch and remaining work (SG-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592370) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Loopback re-entry requires active branch AND (`iterator.hasMore` \| iteration count < max for branch-driven loops). - **Implementation:** `:846-869,1718-1808` - **Guaranteed by:** 3 suites Rule `SG-7` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [Routing decides per edge and dispatches per target (SG-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592369) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Routing decides per EDGE, dispatches per TARGET (multiple edges OR'd into one dispatch). - **Implementation:** `StateGraphOrchestrator.php:832-872` - **Guaranteed by:** Rule `SG-6` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [The loopback input doubles as the item result (SG-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592368) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `loop_back` input doubles as `item_result` when absent. - **Implementation:** `:113-122` - **Guaranteed by:** Rule `SG-5` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [How a ForEach loop initialises and finishes (SG-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592367) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: ForEach: init on empty `__iterator__` (needs items; non-array wrapped; re-indexed; empty completes immediately); defined output set incl. `collected_results` on completion. - **Implementation:** `ForEachNode.php:107-200+` - **Guaranteed by:** 8 cases Rule `SG-4` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [Which payloads the status vocabulary guards (PIPE-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592381) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Vocabulary guarding is scoped to `job_status_summary` / the job API's `status_summary`: `total` counts every job, but a bucket is incremented only when `JobStatus::tryFrom()` resolves the persisted value, so the buckets may sum to **less** than `total`, no out-of-enum key is ever added there, and no PHP warning is raised. The distinct unknown values are logged as exactly **one** warning per read. ⚠ `node_statuses[*].status_counts` is deliberately **NOT** guarded — it counts raw persisted values — so an out-of-enum status DOES appear as a key there, and as `node_statuses[*].status`. The two liv… ### [The job status summary has one shape, derived from the enum (PIPE-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592380) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `job_status_summary` has ONE shape, derived from the `JobStatus` enum (`emptySummary()`): the key `total` followed by one integer counter per case, `interrupted` included. All three build paths emit those exact keys in that order — the real jobs read, the missing-pipeline fallback and the failure catch (both fallbacks all-zero, via one `emptyJobsData()` builder). The job API's own `status_summary` shares the builder. - **Implementation:** `JobStatus::emptySummary()`; `PipelineApiController::getPipelineJobs`/`::emptyJobsData`; `JobApiController::getPipelineJobStatus` - **Guaranteed by:** Rul… ### [The live run status is read from persisted entities (PIPE-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592379) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: The live run-status contract is the pipeline API reading **persisted entity state** (= SG-15). Two routes, one envelope: `GET /api/flowdrop/pipeline/{pipeline_id}` and `.../status` both answer the standard `{success: TRUE, data: …}` shape (`ApiResponseTrait::successResponse`), publish the persisted lifecycle value as the raw `PipelineStatus` value string under `data.status`, and answer **404** (`{success: FALSE, error}`) for a missing pipeline and **403** for a denied one. The full route adds `node_statuses`, `jobs`, `job_status_summary`, `execution_data` (plus `id`/`name`/`description`/`creat… ### [The execution id the editor polls is the pipeline id (SG-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592378) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: StateGraph/sync-pipeline execution id = pipeline entity id (frontend polls pipeline API). Both engines **overwrite** the caller's `OrchestrationRequest::pipelineId` with the id of the pipeline they created — a synthetic id (the request's own `pipeline_{workflow}_{time}_{rand}`, a uuid, the thread id) would 404 every poll and freeze the canvas at idle. Pairs with PIPE-4: the same response id polls a payload whose `node_statuses` keys are the canvas node ids. - **Implementation:** `StateGraphOrchestrator.php:199-201`; `SynchronousPipelineOrchestrator.php:161` - **Guaranteed by:** 2 tests (`Stat… ### [Exceeding the iteration budget throws (SG-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592377) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `StateManager::applyUpdate()`/`incrementIteration()` throw `MaxIterationsException` once the *new* `iterationCount` **exceeds** `maxIterations` (strictly greater — the budget's own iteration is allowed); `StateGraphOrchestrator::orchestrate()` catches it and returns an `OrchestrationResponse` with status exactly `max_iterations_exceeded`, empty `results`, and metadata `max_iterations` / `current_iterations` / `node_id`. It is a terminal verdict, not ORC-10's resumable pause: no checkpoint-resume handle is offered and the status is never `paused`. NB the loop's own `$iteration >= maxIterations`… ### [node_statuses is keyed by the workflow node id (PIPE-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592382) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `node_statuses` is keyed by the **workflow node id** — the id the canvas holds, which is what the editor looks a badge up by. The key is `$job->getNodeId()` (job metadata `node_id`, stamped from the stored node's `id` at job generation), never the job entity id, the node-type id or an iteration-suffixed id: loop clones inherit the plain node id, so all of a node's iterations collapse onto one entry and the per-iteration picture rides inside it (`executions`, `status_counts`). `jobs[].node_id` carries the same ids, which is why the editor's per-job fallback resolves too. Only nodes that became … ### [A hidden output is stripped where it is produced (DATA-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592346) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Output stripping at the production point (= EXPO-11..14). - **Implementation:** — - **Guaranteed by:** — (cross-reference; GR-EXPO carries the tests) Rule `DATA-8` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [Inside a node, the parameter-resolution cascade decides (DATA-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592345) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: In-node precedence = CFG-4..6 chain. - **Implementation:** — - **Guaranteed by:** — (cross-reference; GR-CFG carries the tests) Rule `DATA-7` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [Launch data fills in under edge-delivered inputs (DATA-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592344) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `initialData[nodeId]` merges as fallback UNDER edge-delivered inputs (`array_merge`, so an edge-delivered NULL still wins); a non-array entry, or one keyed for another node, is ignored. - **Implementation:** `NodeRuntimeService.php:160-166` - **Guaranteed by:** `NodeRuntimeServiceInitialDataMergeTest` (5) Rule `DATA-6` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [Loopback and tool edges are dropped from data delivery (DATA-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592343) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Loopback edges (`*-input-loop_back`) and tool edges are dropped at **two** points. `buildDependencyGraph()` skips both, so they create no `dependent_jobs` reference and `validateDependencyGraph()` never raises "Circular dependency detected in workflow" for them; and `areJobDependenciesMet()` buckets loopback edges out of the checks and `continue`s past tool edges (`is_tool` flag OR an `-input-tool` target handle — `ReservedName::PORT_TOOL` — for jobs generated before the flag). Consequence: a node whose only incoming edges are loopback/tool has an empty `dependent_jobs` list and is promoted id… ### [Readiness promotes a job whose dependencies are met (DATA-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592342) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Readiness is evaluated in `getReadyJobs()`, which promotes a qualifying IDLE job to PENDING and **saves** it. Data-port readiness applies **only** to a job with zero incoming trigger edges (and only after the error-edge arm): with any trigger edge present, readiness is OR over triggers and data ports are ignored entirely, so a node can legitimately run with an unfilled data port. Otherwise: data edges are grouped by the extracted target port name (falling back to the raw target handle when it has no `-input-` marker), each group needs ≥1 completed **and branch-active** source (OR within a port… ### [A trigger edge carries no data (DATA-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592341) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Trigger edges carry no data. - **Implementation:** 2 sites - **Guaranteed by:** fixture Rule `DATA-3` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [One value per port, last executor wins (DATA-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592340) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Last-executor-wins, one value per port, never an array; ordering by `execution_order` desc, then a source *with* an order ahead of one without, then node-id strcmp; collision logs warning. ⚠ the strcmp fallback is reachable **only when neither source carries a positive order** — equal positive orders make the comparator return 0 and PHP's sort is stable, so that tie resolves to edge/parent declaration order, not alphabetically. ⚠ only the sort comparator is identical in the 3 input builders — the surrounding rules have drifted (sync lacks error-edge handling and adds a whole-output merge fallb… ### [Delivery is port to port, both names read from the handle (DATA-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592339) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Delivery is **port-to-port**: both port names come from splitting the handle on `-output-` / `-input-` (`{nodeId}-{direction}-{port}`), and if **either** handle lacks its marker the extracted name is NULL and the edge delivers nothing — silently, with no warning. Presence of the value is `array_key_exists($sourcePort, $sourceOutput)`, never `isset()`, so an explicitly emitted NULL IS delivered and reaches the resolver as Priority 1 (CFG-7) — **except on the StateGraph input builder, which gates with `isset()`, so a wire NULL is not delivered there** (documented divergence, see DATA-2). A sourc… ### [Direct sync skips a node whose trigger was never satisfied (BR-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592338) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Direct sync: a node with ≥1 incoming trigger edge and no satisfied trigger is **skipped, never executed**, and the skip is announced three ways carrying the *same* fixed reason `branch_not_active` — a `NodeSkippedEvent` (`reason:`), a real-time `ExecutionStatus::SKIPPED` update carrying `node_type_id` + `reason`, and `withNodeSkipped($nodeId, 'branch_not_active')` on the snapshot (landing as `metadata.skip_reason`). The node id also lands in the response's `metadata.skipped_node_ids` and is counted in `metadata.nodes_skipped`. ⚠ The reason is fixed even when the real cause is an unexecuted **n… ### [Staleness gates a branch decision, not delivery (BR-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592337) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Staleness gates only **branch decisions**, not delivery. For a trigger edge, an error edge, and a data edge leaving a **named port of a source that emitted `active_branches`**, a completed source job whose entity id is lower than that node's newest job id (any status) counts as not-completed, so the consumer stays not-ready and waits for its own iteration's job. An **unnamed** source port, or **any** source that emitted no `active_branches`, returns TRUE from `isEdgeBranchActive()` *before* the staleness check — so an ordinary data edge is still satisfied by the previous iteration's completed … ### [Branch gating applies to trigger and data ports alike (BR-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592336) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Branch gating applies regardless of target port kind (trigger or data). - **Implementation:** `JobGenerationService.php:1065+` - **Guaranteed by:** 2 stategraph suites Rule `BR-5` of `RT-BR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: BR-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592104 ### [A node's configured branches are the authority on branch ports (BR-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592335) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Branch-port authority = the node's configured `branches` `[{name,value}]`; entries without a non-empty **string** `name` are dropped by `normalize()` before anything else. Matching an outcome to a branch is type-aware, never a loose cast: a **boolean** outcome matches only a branch whose configured value *denotes* a boolean — a real bool, int `0`/`1`, or the strings `true`/`false`/`1`/`0` (case-insensitive) — a string-vs-string pair compares with `strcasecmp`, and anything else is identity (`===`). When **no** branch matches, `nameForValue()` returns the caller's **fallback literal** (`'true'`… ### [How active_branches is normalized (BR-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592334) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `active_branches` = list of strings; bare string is ONE name verbatim (no comma split); non-strings dropped; survivors trimmed + lower-cased. - **Implementation:** `:169-189` - **Guaranteed by:** `BranchActivationTest::testParse` + 2 `isActive` rows Rule `BR-3` of `RT-BR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: BR-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592104 ### [The three cases where a branch edge activates (BR-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592333) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Three deliberate TRUE cases, checked in this order and each returning before the membership test: an unnamed port (`$branchName === ''`); a source that emitted no (or an empty) `active_branches`; and a port that is a **value port**. Value-port authority is the source's configured `branches`, matched case-insensitively (`strcasecmp`); when the source declares **no** `branches` at all there is no authority and the fallback is the payload — a port whose name is a key in the source's output (`array_key_exists`, so a falsy or NULL value still counts) is taken for a value port. ⚠ That fallback is wr… ### [When a branch edge is gated at all (BR-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592332) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A branch edge is **gated at all** only when all three preconditions hold: the edge leaves a NAMED source port, the source emitted a non-empty `active_branches`, and that port is a branch port rather than a value port (BR-2/BR-4). Given those, the edge is followed iff `trim(strtolower($portName))` is in the parsed `active_branches` list — both sides trimmed and lower-cased — and otherwise not followed. In every other case the edge is followed, which is why the bare "iff" reading is false on its own: BR-2's three arms all return TRUE before membership is ever consulted. - **Implementation:** ga… ### [A cancelled run is announced like any other terminal outcome (ORC-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592331) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A CANCELLED run is announced like every other terminal outcome: every cancel path dispatches `PipelineCompletedEvent` carrying CANCELLED, exactly once per cancellation. The in-loop signal path (`AbstractOrchestratorBase::applyCancelSignal`, shared by all three loop engines) dispatches it after `ExecutionCancelledEvent` with the live execution id and stamped `execution_time_us`; the entity-level cancel paths (pipeline interaction form, trigger overlap Cancel/Terminate, session stop) announce via `PipelineCancellationAnnouncer` (execution id = pipeline id, duration from entity timestamps). `Pipe… ### [Claiming a job is atomic under concurrent workers (ORC-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592330) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Job claim/promotion is atomic under concurrent workers. Today: `getReadyJobs()` promote+`save()` is an unlocked, untransacted read-modify-write and `queuePipelineExecution()` enqueues with no dedup — two workers can execute the same job twice (side-effecting nodes fire twice). **Rule recorded, fix deliberately deferred** — FlowDrop currently documents a single-worker constraint rather than claiming safe concurrent execution. The cheap `:285` log-string-arg call hoist (state machine advanced to format a warning, redundant with `:259`) can land independently. - **Implementation:** `JobGeneratio… ### [Auto-resume is gated, not unconditional (INT-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592329) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Pause is NOT unconditionally held: auto-resume is gated on `PausedReason::budgetReasons()` (`time_budget`/`max_iterations` — async chunking *depends on* budget-pause→auto-resume→re-queue, maxIter 50 / maxTime 30.0); a **HITL/operator pause carries no reason and holds until explicit human resume** — absence-of-reason IS the HITL marker, do not add one. The async queue worker enforces both halves: it resumes and re-queues ONLY budget pauses; a reason-less pause is left paused. (REVERSES the decision-round T1-4 "pause holds identically on every engine" — that would stall every async run over 30s … ### [A terminal pipeline cannot be paused or resumed (INT-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592328) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A terminal pipeline (COMPLETED/FAILED/CANCELLED, `PipelineStatus::terminalStatuses()`) refuses re-entry: the sync-pipeline orchestrator throws `OrchestrationException` before touching it (async worker + the signal API already refuse), so cancel is durable — a rerun/requeue can never resurrect a dead run and re-fire side-effecting nodes. Re-running always means a NEW pipeline seeded with the source run's input and stamped `rerun_of` (`PipelineRerunService`), used by both operator rerun paths (rerun confirm form; interaction form's re-run buttons). - **Implementation:** refuse `SynchronousPipel… ### [A resume re-enters through the pipeline's declared orchestrator (ORC-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592327) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Interrupt resume re-enters through the pipeline's declared orchestrator, never the plain sync loop. - **Implementation:** `InterruptResolvedSubscriber.php:128-140` - **Guaranteed by:** parity test Rule `ORC-13` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-13` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592100 ### [An async launch returns queued immediately (ORC-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592326) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Async returns `"queued"` immediately; no in-request execution; optional snapshot seeding of pre-completed jobs. - **Implementation:** `AsynchronousOrchestrator.php:95-180` - **Guaranteed by:** `AsynchronousOrchestratorQueuedResponseTest` (queued response + no in-request node execution; the snapshot seeding leg is INT-10) Rule `ORC-12` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-12` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592100 ### [How a run's terminal status is decided (ORC-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592325) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Terminal status precedence: unhandled-failure→FAILED(+SKIPPED rest); interrupted→PAUSED(no reason); ready-remaining→PAUSED(+reason); else COMPLETED. CANCELLED never reaches this chain by design: a cancel signal exits through the signal path before it, announced there (ORC-15). The two ladders are not identical: only the stategraph ladder has an explicit `hasInterruptedJobs()` arm — on the sync-pipeline engine an interrupt leaves the ladder entirely through the `InterruptExceptionInterface` catch (which pauses the pipeline and returns INTERRUPTED), which is why that ladder has three arms and st… ### [An iteration and time budget breaks the loop (ORC-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592324) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Budget: maxIterations (default 100) + maxExecutionTime break the loop → PAUSED + `paused_reason` → pending system Pause signal → resumable with fresh budget; re-entry clears stale reason. - **Implementation:** 2 orchestrators + `ExecutionConfig` - **Guaranteed by:** `StateGraphBudgetPauseResumeTest` (3) Rule `ORC-10` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-10` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592100 ### [A pipeline engine is a ready-job loop (ORC-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592323) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Pipeline engines are ready-job loops. `getReadyJobs()` flips every IDLE job whose dependencies are met to PENDING **and persists it** (`markAsPending()` + `save()`), then returns **all** PENDING jobs — including ones already pending from an earlier pass — sorted **ascending by `getPriority()`** (lower number runs first). A job with unmet dependencies is left IDLE, untouched. The engines call it repeatedly and stop when it returns an empty array: that empty return **is** what "quiescent" means, and re-entering a node across passes is what makes loops possible. - **Implementation:** `JobGenerat… ### [Direct sync filters which trigger node starts the run (ORC-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592322) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Direct sync trigger filtering: `initialData['trigger_node_id']` selects one trigger; other trigger nodes dropped. Opt-in: without the key the compiled order is used verbatim (a manual/REST launch has no firing trigger to privilege), and non-trigger nodes are never filtered. - **Implementation:** `:242-271` - **Guaranteed by:** 2 tests (`SynchronousOrchestratorTest`) Rule `ORC-8` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent is… ### [Direct sync walks the execution order once (ORC-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592321) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Direct sync walks `ExecutionGraph::getExecutionOrder()` **once**, top to bottom, carrying results in an in-request context. It never re-queues or re-enters a node, so **each node executes exactly once per run and a loopback edge produces no second iteration** — a loop drawn on the canvas is inert on this engine. Loops require a pipeline engine (ORC-9). - **Implementation:** `SynchronousOrchestrator.php:254` (order), single `foreach` `:297-502` with no re-scheduling - **Guaranteed by:** `SynchronousOrchestratorTest::testLinearWorkflowExecutionOrder`, `::testLoopbackEdgeDoesNotProduceASecondIte… ### [Every strategy shares one contract and one hierarchy (ORC-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592320) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Common contract in a shared hierarchy: every strategy (direct sync included) extends the job-free `AbstractOrchestratorCore` (pipeline storage resolution, pipeline creation, interrupt handling, error-edge payload shape); the job strategies additionally share `AbstractOrchestratorBase` (NodeRuntimeService execution, retry, error routing, stop handling, signal polling, JobCompletedEvent, snapshots). - **Implementation:** both classes - **Guaranteed by:** `OrchestratorHierarchyContractTest` (structural: the shared members are asserted to be *inherited*, not merely callable) Rule `ORC-6` of `RT-… ### [Capability queries are answered from the plugin definition only (ORC-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592319) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Capability queries are definition-driven, and ONLY definition-driven: `OrchestratorHelper::hasCapability()` reads the `Orchestrator` attribute's `capabilities` list off the plugin definition — `isStateGraph()` = `stateful`, `isSynchronous()` = `synchronous_execution` && !`stateful` — and those verdicts gate real behavior (checkpoint storage selection `SessionExecutionService::715`, pipeline form branches). The former *method* API (`supportsWorkflow()`/`getCapabilities()`) was decorative — constant returns, zero production callers — and was deleted in 2.x; the attribute list is the single sourc… ### [StateGraph is the session default, not the global one (ORC-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592318) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: STATEGRAPH is the session/playground default, not global: `SessionExecutionService` passes it as the *caller* default to `getInstanceFromSettings()`, so it applies only when the session/workflow declared no engine, and the global chain (ORC-2) never resolves to it. - **Implementation:** `SessionExecutionService.php:686,715` - **Guaranteed by:** `SessionExecutionServiceOrchestratorDefaultTest` + `OrchestratorDefaultResolutionTest` Rule `ORC-4` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-4` token, and `scripts/spec-coverage… ### [An unknown orchestrator type falls back with a warning (ORC-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592317) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unknown type falls back with warning; missing fallback → `\RuntimeException`. - **Implementation:** `:73-100` - **Guaranteed by:** `OrchestratorDefaultResolutionTest` Rule `ORC-3` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592100 ### [How the default orchestrator is resolved (ORC-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592316) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Default resolution: presave→SYNC; else trigger settings; else flowdrop settings; else ASYNC. Each configured step must `validate()` before it is accepted, so an uninstalled engine cannot capture the default. Shipped: flowdrop=sync, trigger=async. - **Implementation:** `OrchestratorHelper.php:118-142` - **Guaranteed by:** `OrchestratorDefaultResolutionTest` Rule `ORC-2` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-2` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592… ### [The four orchestrator strategies and their ids (ORC-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592315) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Four strategies, each returning its namespaced plugin id verbatim from `getType()`. The `OrchestratorHelperInterface` constants are the single source of those strings: `SYNCHRONOUS = flowdrop_runtime:synchronous`, `SYNCHRONOUS_PIPELINE = flowdrop_runtime:synchronous_pipeline`, `ASYNCHRONOUS = flowdrop_runtime:asynchronous`, `STATEGRAPH = flowdrop_stategraph:stategraph`. - **Implementation:** `OrchestratorHelperInterface.php:37,45,53,62` - **Guaranteed by:** `SynchronousOrchestratorTest::testGetType`, `FlowDropRuntimeIntegrationTest::testOrchestratorType` (sync + sync_pipeline), `AsynchronousE… ### [Every orchestrator routes an error result identically (DECIDED) (ERR-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592314) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **All orchestrator strategies route error Outputs identically** (DECIDED ← OPEN-1): error edge present → the node's outputs are replaced by the shared `{error:{message,code,node_id,retryable}}` envelope and the run continues (ERR-7); no error edge → the run fails (ERR-8). Direct sync included. - **Implementation:** `SynchronousOrchestrator.php:404-411,850-902` - **Guaranteed by:** 2 tests (`SynchronousOrchestratorErrorRoutingTest`) Rule `ERR-13` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-13` token, and `scripts/spec-cove… ### [Remove the direct-sync record-and-continue divergence (ERR-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592313) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: *(collapsed into ERR-13)* The direct sync record-and-continue divergence is removed: the orchestrator inspects `Output::isError()` and applies ERR-13 like every other strategy. - **Implementation:** `SynchronousOrchestrator.php:404-411` - **Guaranteed by:** — (superseded by ERR-13) Rule `ERR-12` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-12` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [Retry is in-place, immediate and opt-in (ERR-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592312) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Retry: in-place, immediate, no backoff, opt-in (`max_retries` default 0), only `error_retryable`, counter persisted; idempotence is the author's contract. - **Implementation:** `AbstractOrchestratorBase.php:353-379` - **Guaranteed by:** 3 tests Rule `ERR-11` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [A routed-failed node satisfies only its error edges (ERR-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592311) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A routed-failed node satisfies only error edges (evaluated before trigger/data, OR semantics, staleness applies); success-path successors never ready. - **Implementation:** `JobGenerationService.php:676-689,812-847` - **Guaranteed by:** 5 tests (`JobGenerationServiceTest`: routed/unrouted, precedence over the trigger rule both ways, OR, staleness) Rule `ERR-10` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-10` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [A pipeline whose only failures were routed still completes (ERR-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592310) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A pipeline whose only FAILED jobs carry `error_routed` finishes with status `completed`. The verdict is computed from `hasUnhandledFailedJobs()` — TRUE iff some FAILED job's metadata lacks `error_routed === TRUE` — never from `hasFailedJobs()`; one unrouted failure alongside any number of routed ones still fails the run. A routed-failed job also dispatches `JobCompletedEvent` (the generic "job finished" channel), so per-node subscribers see it and discriminate on `getStatus()`. - **Implementation:** `:962-969`; routed dispatch `:938` - **Guaranteed by:** 2 tests (routed-only run completes; a … ### [An error result with no error edge fails the run (ERR-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592309) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: No error edge → `NodeProcessingException`, job FAILED without `error_routed`, run fails. - **Implementation:** `:249-251,317-330` - **Guaranteed by:** Rule `ERR-8` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [An error result with an error edge routes instead of failing the run (ERR-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592308) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Error-edge routing (pipeline engines): error Output + ≥1 error edge → job FAILED + `error_routed`, output becomes `{error:{message,code,node_id,retryable}}`, run continues. - **Implementation:** `AbstractOrchestratorBase.php:231-239,889-924` (payload shape shared via `AbstractOrchestratorCore::buildErrorEdgePayload`) - **Guaranteed by:** 2 suites Rule `ERR-7` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [An unserializable output fails the node (ERR-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592307) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: After unexposed outputs are filtered and the unified `output` port is composed, `assertSerializableOutput()` rejects any leaf that is not scalar/null/array/stdClass/`JsonSerializable` with `NonSerializableOutputException` naming the node id, the plugin id, the dotted path and the offending type. Because it is a `\RuntimeException` thrown inside the processor try block it becomes an error-status Output carrying that message with **no** `error_retryable` metadata (so it never retries and follows the normal error-edge-or-fail path). ⚠ Because the check runs *after* filtering, a non-serializable v… ### [A stop request bypasses the error catch and stops the run cleanly (ERR-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592306) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `WorkflowStopException` extends `\Exception`, so it bypasses the inner error-Output catch; `NodeRuntimeService` catches it in a clause placed *before* the generic `\Exception` clause and re-throws the SAME instance after broadcasting real-time `completed` for the node — were the ordering reversed the stop would be re-wrapped into a `RuntimeException` and fail the run. The orchestrator then marks the job COMPLETED (never FAILED), records `getResult()` under the node's result key, abandons downstream and unscheduled sibling jobs, and finishes the run with status `completed`. - **Implementation:… ### [An interrupt is re-thrown unchanged (ERR-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592305) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `InterruptExceptionInterface` re-thrown unchanged after event dispatch + `interrupted` status. - **Implementation:** `:276-311` - **Guaranteed by:** 2 tests (same instance re-thrown, event payload, no subscriber) Rule `ERR-4` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [Any other exception fails the node and is re-thrown wrapped (ERR-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592304) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Non-RuntimeException `\Exception` escapes, node FAILED, re-thrown wrapped — fails the run, does NOT take the error edge. - **Implementation:** `:326-344` - **Guaranteed by:** 2 tests (wrapped re-throw + cause; no Output exists, so nothing can route) Rule `ERR-3` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [A retryable exception stays recognisable after it is caught (ERR-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592303) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `RetryableExceptionInterface` survives type erasure as `error_retryable` metadata: when the caught `\RuntimeException` implements the marker the error Output carries `error_retryable` = TRUE; otherwise the key is **absent** (`getMetadata('error_retryable')` returns NULL, never FALSE). The absence is load-bearing — the retry gate is a strict `!== TRUE` check, so anything other than the literal TRUE marker is treated as non-retryable. - **Implementation:** marker `:236-238`; strict gate `AbstractOrchestratorBase.php:360-364` - **Guaranteed by:** 2 tests (marker present/absent, asserted on the O… ### [A RuntimeException from a processor becomes an error result (ERR-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592302) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `\RuntimeException` from a processor is caught → error-status Output; never propagates (the error-edge channel). The real-time broadcast for a converted failure is `completed`, not `failed` — the node finished; the error verdict rides the Output. - **Implementation:** `NodeRuntimeService.php:228-239` - **Guaranteed by:** `NodeRuntimeServiceErrorChannelTest` (3) Rule `ERR-1` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-1` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: … ### [A node mapping carries both the processor and the node-type id (CMP-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592301) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `NodeMapping` carries both `processorId` and `nodeTypeId`; runtime loads entities by nodeTypeId. - **Implementation:** `:734-765` - **Guaranteed by:** Rule `CMP-11` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [A tool consumer must declare that it accepts tools (CMP-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592300) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Tool consumer must implement `ToolsAwareInterface` or compile error. - **Implementation:** `:356-361` - **Guaranteed by:** Rule `CMP-10` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-10` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [Tool names must be unique per consumer at compile time (CMP-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592299) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Tool-name uniqueness per consumer over flattened leaf set at compile time; collision → `CompilationException`; passthroughs exempt/checked at consumer. - **Implementation:** `:290-362` - **Guaranteed by:** (3 + ToolBox suite) Rule `CMP-9` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-9` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [Execution order is a topological sort (CMP-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592298) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Order = Kahn toposort; ties broken by definition order (artifact, not id). - **Implementation:** `:663-697` - **Guaranteed by:** (independent roots + tied fan-out siblings; the test records this as an artifact authors may not lean on) Rule `CMP-8` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [A trigger dependency outranks a data dependency for ordering (CMP-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592297) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Trigger deps beat data deps for ordering (`executionDeps = triggerDeps ?: dataDeps`). - **Implementation:** `:410-430` - **Guaranteed by:** `topology-trigger-priority-over-data.yml` Rule `CMP-7` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [Which nodes are excluded from the execution graph (CMP-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592296) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Exclusion precedence: NonExecutable always out; tool-only out; rootless-in; loopback-only-in out; edge-free node IS executed. - **Implementation:** `:494-561` - **Guaranteed by:** (3 cases) Rule `CMP-6` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [Cycle detection ignores the edges that are meant to loop (CMP-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592295) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Cycle detection excludes `tool_availability`/`loopback`/`agent_result`; loopback+tool cycles legal; any other cycle → hard error. - **Implementation:** `:208-273` - **Guaranteed by:** (5 cases) Rule `CMP-5` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [Edge type is derived from handles, never declared (CMP-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592294) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Edge type derived from handles, never declared (= EDGE-3..6). - **Implementation:** `DependencyEdge.php:23-137` - **Guaranteed by:** Rule `CMP-4` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [Compile preconditions run first, in a fixed order (CMP-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592293) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Preconditions run first inside the compile try-block, in this order, the first failure throwing `CompilationException`: empty id → `Workflow must have an ID`; zero nodes → `Workflow must have at least one node`; then per node in definition order, missing id → `All nodes must have an ID`, missing type → `Node {id} must have a type`. Each reaches the caller prefixed by CMP-1's wrap. - **Implementation:** `:175-194` - **Guaranteed by:** (4 cases) Rule `CMP-3` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-3` token, and `scripts… ### [Re-enrichment on the run path is conditional (CMP-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592292) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Run-path re-enrichment from the live node types (= SCH-29) is **conditional, not a property of compilation**: it happens only on `compile()`'s **array** entry point and only when a `NodeMetadataResolver` was injected; handing `compile()` a pre-built `WorkflowDTO` skips it entirely. Every DTO-building caller therefore enriches first — `SynchronousOrchestrator:215-219` and `JobGenerationService:113-118` do, and `StateGraphOrchestrator:1674-1678` (which builds a DependencyGraph directly, never calling the compiler) does too. Without a resolver the (attacker-controllable) stored metadata cache is … ### [What compiling a workflow produces (CMP-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592291) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Compile = DependencyGraph (all edges) + ExecutionGraph (runnable nodes) + NodeMappings, produced in this stage order inside one try-block: structure preconditions (CMP-3) → dependency graph → cycle detection (CMP-5) → tool wiring (CMP-9/10) → execution graph (CMP-6/8) → node mappings (CMP-11). **Any `\Exception` from any stage — a `CompilationException` from an inner stage included — is logged at error and re-thrown as a NEW `CompilationException`** with message `'Workflow compilation failed: ' . $previous->getMessage()`, code `0`, and `getPrevious()` set to the original. So a caller always se… ### [One expression-error policy across every engine (DECIDED) (LANG-29)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592290) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **Uniform expression error policy** (DECIDED ← OPEN-8): an expression *error* — a path the engine cannot evaluate, an engine throwable — is wrapped in `\RuntimeException` → node fails → error-edge routing. IMPLEMENTED across all four expression-consuming processors: DataMapper (LANG-21), DataExtractor (LANG-22), DataShaper (LANG-25), PromptTemplate (LANG-26). **Scope is errors, not empty results:** an expression that evaluates cleanly and finds nothing is not a failure, so DataExtractor's `default` + `success: FALSE` soft-miss (LANG-24) is deliberately untouched by this policy — "expression er… ### [The six operators the if/else gateway declares (LANG-28)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592289) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: IfElse declares six operators (`equals`, `not_equals`, `contains`, `starts_with`, `ends_with`, `regex`) as a schema `enum` **only** — there is no IfElse-specific validator. The enum is enforced generically by `WorkflowValidator::validateConfigValue()` at save (`CONFIG_INVALID`) and by CFG-10 at resolution. There is **no** save-time check that `matchText` is a compilable regex: an uncompilable pattern surfaces at runtime as `InvalidNodeConfigurationException('Regex execution failed for pattern: …')`, and an operator reaching `process()` outside the enum throws `InvalidNodeConfigurationException… ### [The switch gateway matches a branch value instead of evaluating it (LANG-27)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592288) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: SwitchGateway does not evaluate `expression`: the first branch whose `value` is `===`-identical to it wins (no coercion, no engine) and its **name** is emitted as the single element of `__active_branches__`. No match falls back to `default_branch`. The guard is `empty($activeBranch)`, not a NULL check, so it ALSO throws `InvalidNodeConfigurationException("No active branch found for expression: ")` when a branch DID match but its name is falsy (`"0"`, `""`). The `input_value` output is always NULL — the matched value is never echoed. - **Implementation:** `SwitchGateway.php:55-85`; match loop … ### [A prompt template turns a Twig error into a node failure (LANG-26)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592287) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: PromptTemplate: any `Twig\Error\Error` from rendering (SyntaxError/RuntimeError/LoaderError) is caught and re-wrapped as `\RuntimeException` chaining the original → the node FAILS → error-edge routing (LANG-29 policy). - **Implementation:** `PromptTemplate.php:131-145` - **Guaranteed by:** `PromptTemplateTest` Rule `LANG-26` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-26` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [DataShaper resolves its five sentinels before consulting an engine (LANG-25)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592286) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: DataShaper resolves **five** sentinels before the engine is consulted: `_NOW_` → an ATOM-formatted timestamp, `_NULL_` → NULL, `_EMPTY_ARRAY_` → `[]`, `_EMPTY_OBJECT_` → `new \stdClass()`, and the `_LITERAL:` prefix → the remaining substring verbatim. Every sentinel increments `mappedFields`, **including `_NULL_`** — `resolveSpecialValue()` returns the wrapper `['value' => NULL]`, which is itself non-NULL, so the counter is bumped before the value is unwrapped; only a NULL from an expression that actually reached the engine goes uncounted. Any throwable from a source expression that does reach… ### [A NULL extraction is a soft miss, never an error (LANG-24)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592285) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: DataExtractor: a **NULL** extraction is a soft-miss, never an error — the configured `default` is substituted and `success` = FALSE means "no non-NULL match found"; the node succeeds. Extraction engines cannot distinguish a legit stored NULL from a no-match (LANG-8), so both take the default. Only NULL trips the soft-miss: FALSE/0/"" are delivered as success. This is live shipped behaviour, not a legacy remnant — the `default` config value and the `success` output port both survive LANG-29 unchanged, and the port's own description still reads "FALSE means the configured default was delivered" … ### [DataExtractor unwraps a first match only for JSONPath (LANG-23)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592284) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: DataExtractor first-match unwrapping keys off the ENGINE: only jsonpath running a `$`-query reduces an array result to its first match (`extract_all` FALSE); property_path (any non-jsonpath engine) delivers array results whole, even for `$`-prefixed paths, and the jsonpath property-path fallback route (non-`$`) never unwraps. The `is_jsonpath` output flag remains a `$`-prefix sniff report — a routing/reporting hint independent of the engine. - **Implementation:** `:105,136-153` - **Guaranteed by:** (3 cases) Rule `LANG-23` of `GR-LANG` in `docs/development/specification-registry.md`. Tests b… ### [DataExtractor re-wraps any evaluator throwable as a RuntimeException (LANG-22)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592283) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: DataExtractor: any evaluator throwable is re-wrapped as `\RuntimeException` naming the path and engine → the node FAILS → error-edge routing (same policy as DataMapper, per LANG-29). Scope is expression *errors* only (invalid path, engine error): the configured `default` never applies on an error, but it is untouched for the soft-miss case (LANG-24), which still substitutes it and still succeeds. What went away is the `{success: FALSE, error}` envelope an error used to produce (`error` was never a declared output port) — not default-on-no-match. - **Implementation:** `DataExtractor.php:118-13… ### [DataMapper re-wraps only a RuntimeException from an evaluator (LANG-21)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592282) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: DataMapper catches only `\RuntimeException` from `evaluate()` and re-wraps it as `\RuntimeException("Expression error in dynamic output '': …")`, aborting `process()` so no partial output map is returned. Unlike DataShaper/DataExtractor (which catch `\Throwable`), a non-`\RuntimeException` throwable — e.g. a `\TypeError` from an engine — escapes **unwrapped**, without the port name, and because both orchestrators catch only `\Exception` it is not converted into a node failure / error-edge route at all. - **Implementation:** `DataMapper.php:126-136` (`catch (\RuntimeException`) vs `DataShaper.… ### [What exists() answers for an empty path and for a scalar (LANG-20)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592281) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `exists('')` = TRUE; `exists()` on scalar+property-path = FALSE. - **Implementation:** `:149-164` - **Guaranteed by:** Rule `LANG-20` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-20` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [Extracting all matches on a property path wraps the single result (LANG-19)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592280) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `extractAll()` on property path wraps single result; NULL and no-match collapse to `[]`. - **Implementation:** `:127-131` - **Guaranteed by:** Rule `LANG-19` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-19` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [How a mapping value is marked as a literal instead of an expression (LANG-18)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592279) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `applyMappings()` literal escapes: `literal:x`, `"x"`, `'x'` bypass extraction (trigger mappings only). - **Implementation:** `:178-193,394-422` - **Guaranteed by:** Rule `LANG-18` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-18` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [Dot-to-bracket normalization is duplicated in three classes (LANG-17)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592278) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Dot→bracket normalization duplicated in THREE classes (JsonPathService, PropertyPathEvaluator, plus undocumented copy in GetWorkflowData) — currently in agreement, drift risk. - **Implementation:** 3 sites - **Guaranteed by:** (service side only) Rule `LANG-17` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-17` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [A string context is decoded as JSON when it is JSON (LANG-16)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592277) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: String context auto-json_decoded; non-JSON string passes through; `"null"` decodes to NULL. - **Implementation:** `:328-338` - **Guaranteed by:** 3 fixtures (`lang-jsonpath-*-context*.yml`) Rule `LANG-16` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-16` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [A single JSONPath match is unwrapped unless the path is multi-value (LANG-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592276) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Arity collapse: single match unwrapped unless path is "multi-value" (sniffed for `[*] [? .. [n:m]`); a filter matching one item stays an array. - **Implementation:** `:243-247,376-383` - **Guaranteed by:** Rule `LANG-15` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-15` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [A path is JSONPath when it starts with $ (LANG-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592275) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Path is JSONPath iff trimmed string starts `$`; else property path. - **Implementation:** `JsonPathService.php:198-200` - **Guaranteed by:** Rule `LANG-14` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-14` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [Twig validation is compile-only (LANG-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592274) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Twig `validate()` is compile-only; runtime-only failures validate TRUE. - **Implementation:** `TwigEvaluator.php:124-130` - **Guaranteed by:** `lang-twig-validate-compile-only.yml` Rule `LANG-13` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-13` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [JSONPath validation accepts anything that is not a $ path (LANG-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592273) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: jsonpath `validate()` returns TRUE unconditionally for non-`$` paths. - **Implementation:** `JsonPathEvaluator.php:97-102` - **Guaranteed by:** `lang-jsonpath-validate-non-dollar-unconditional.yml` Rule `LANG-12` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-12` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [Property-path validation delegates to the same parser (LANG-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592272) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: property_path `validate()` delegates to the same PropertyAccess parse `evaluate()` feeds (after dot→bracket normalization), so its accept-set is a superset of what `evaluate()` can resolve (e.g. `[user-name]` validates AND resolves); only paths PropertyAccess itself cannot parse (unclosed bracket, empty segment) validate FALSE. R11's LANG-11 gate is cleared. - **Implementation:** `:82-96` - **Guaranteed by:** `lang-property-path-validate-evaluate-agree.yml` Rule `LANG-11` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-11` … ### [Expression Language validation accepts unknown variable names (LANG-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592271) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: EL `validate()` pre-declares all identifiers → unknown variables validate OK, throw at runtime. - **Implementation:** `:94-100` - **Guaranteed by:** `lang-el-validate-predeclares-unknowns.yml` Rule `LANG-10` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-10` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [JSONPath never throws, and has three distinct outcomes (LANG-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592270) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: jsonpath never throws, and there are **three distinct outcomes**, not one: (1) a `$`-query that compiles but matches nothing returns the caller's `default` (NULL through the evaluator) with **no log entry**; (2) any `\Throwable` from compiling or running the query logs `warning: "JSONPath query failed for '': …"` and returns the default; (3) on the non-`$` property-path fallback route, `AccessException`/`UnexpectedTypeException` return the default **silently**, and only other throwables log `"Property path extraction failed …"`. Absence of a warning therefore does not mean the path was valid. … ### [A property path never throws; an unreadable path is NULL (LANG-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592269) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: property_path: never throws; unreadable path → NULL (indistinguishable from legit NULL). - **Implementation:** `PropertyPathEvaluator.php:59-74` - **Guaranteed by:** 3 fixtures (`lang-property-path-*.yml`, `lang-missing-key-divergence.yml`) Rule `LANG-8` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [Twig renders a missing variable as an empty string (LANG-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592268) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Twig: a missing variable renders silently as `''`; the result is always a string, HTML-escaped unless piped through `\|raw`. Twig is **not** failure-free: `SyntaxError` → `\RuntimeException('Twig syntax error: …')` and `RuntimeError` → `\RuntimeException('Twig runtime error: …')`, both chaining the original. No other throwable is caught (`LoaderError` and `\Error` propagate raw), so the failure surface is exactly those two arms. - **Implementation:** `TwigEvaluator.php:88-113` - **Guaranteed by:** 5 fixtures (`lang-twig-*.yml` incl. `lang-twig-syntax-error.yml`, `lang-missing-key-divergence.y… ### [Expression Language reports a syntax error, and a missing variable is one (LANG-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592267) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: EL: SyntaxError → "Expression syntax error: …" (a **missing variable IS a SyntaxError** to Symfony EL, so it takes this arm); any other throwable → "Expression evaluation error: …" — either way it **throws**. - **Implementation:** `ExpressionLanguageEvaluator.php:66-82` - **Guaranteed by:** 3 fixtures (`lang-el-*.yml`, `lang-missing-key-divergence.yml`) Rule `LANG-6` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592… ### [Expression validation has exactly one production call site (LANG-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592266) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Evaluator `validate()` has exactly ONE production call site — the save-time `WorkflowValidator` (R11); `getSyntaxHint()` still has zero. A second validate() caller or a vanished validator call goes red so the surface never drifts silently again. - **Implementation:** grep-verified - **Guaranteed by:** `ExpressionValidateCallSiteTest` (2 tests) Rule `LANG-5` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [A non-array context is wrapped for the template engines (LANG-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592265) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Non-array context wrapped as `['data' => ctx]` for EL/Twig. - **Implementation:** 2 sites - **Guaranteed by:** `lang-scalar-context-wrapping.yml` Rule `LANG-4` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [What an empty expression evaluates to, per engine (LANG-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592264) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Empty expression at the **evaluator** level: `expression_language`/`twig` → NULL; `property_path`/`jsonpath` → context unchanged (divergent polarity!), and all four `validate('')` TRUE. No author can observe that divergence through the shipped nodes: both consumers short-circuit before it — DataMapper maps an empty output expression to NULL whatever the engine (`DataMapper.php:121-124`), and DataExtractor returns `{data: , success: TRUE, is_jsonpath: FALSE, match_count: 0}` for an empty `path`, resolving the evaluator but never calling `evaluate()` (`DataExtractor.php:104-116`). The polarity i… ### [Getting an evaluator never lets a plugin-manager failure escape (LANG-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592263) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `ExpressionEvaluatorAwareTrait::getEvaluator()` wraps any plugin-manager failure as `\RuntimeException("Unknown expression engine '': …")` before any evaluator runs. On a real node this is a *second* line of defence: DataMapper/DataExtractor/DataShaper declare `engine` with `enum: getAvailableEngineIds()`, so an out-of-set value is refused earlier — at save by `WorkflowValidator` (`CONFIG_INVALID`) and at resolution by CFG-10 as `ParameterValidationException`. The `\RuntimeException` is what a caller bypassing the schema (direct trait use, tool invocation) sees. - **Implementation:** `Express… ### [Extraction engines query context; transformation engines see a variable map (LANG-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592262) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Extraction engines treat context as data-to-query; transformation engines as a variable map. - **Implementation:** `ExpressionEvaluatorInterface.php:34-37` - **Guaranteed by:** `lang-context-family-split.yml` Rule `LANG-1` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-1` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [Refuse a synchronous launch of an async-declared workflow (MAN-19)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592261) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `wait: TRUE` against an async-declared workflow refused before pipeline creation. - **Implementation:** `WorkflowLauncher.php:74-81` - **Guaranteed by:** Rule `MAN-19` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-19` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [The manifest is rebuilt only when the declared ports change (MAN-18)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592260) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Rebuild is *triggered* only when `input_ports` or `output_ports` differ from the original, or `$forced`; `isSyncing()` (config import) returns before any work, so an import never bumps a version — and a change inside a source plugin's fragment never triggers a rebuild, leaving the snapshot stale until something else does. An empty port list stores `NULL` for that side's schema. Version: any of major/minor/patch from `0.0.0` yields `1.0.0`; otherwise the named digit bumps and the lower ones reset. `none` writes the schemas and logs a `debug`, leaving `schema_version` untouched. A builder throw … ### [A declared output reads from its node's result (MAN-17)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592259) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Output side: `outputs[name] = results[node_id][port]`; presence is `array_key_exists`, so a NULL value counts as produced; produced-nothing → dropped with warning (composes with EXPO-13); malformed entries skipped silently. - **Implementation:** `WorkflowSchemaResolver.php:97-126` - **Guaranteed by:** 4 tests Rule `MAN-17` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-17` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [Launch inputs are checked against the manifest snapshot (MAN-16 (G4))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592258) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Values checked against snapshot fragments via the shared `SchemaFragmentChecker`, and only `type` and `enum` are **enforced**; ⚠ every other snapshot key (`minimum`,`maximum`,`minLength`,`maxLength`,`pattern`,`required`, nested `properties`/`items`) is **declared** in the published contract but never checked, as is a non-string/union `type`. No coercion; structured kinds (`object,array,list,map,json`) all collapse to `is_array`, and `enum` compares with strict `in_array` (so `1` ≠ `"1"`). Per-value violations aggregate into one `InvalidLaunchInputException` joined by `; `; a name with no fragm… ### [Input checking short-circuits at the first failing stage (MAN-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592257) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `WorkflowInputChecker::check()` short-circuits at the first failing stage (unknown keys → missing required → per-value) and returns one message; the launcher wraps it in `InvalidLaunchInputException`. Every message appends `Known inputs: …` (or `This workflow accepts no inputs.`). ⚠ **Product gap:** the missing-required stage reads `required` off the *manifest entry* (`NodePort::fromArray($port)->required`) — a key the authoring form never writes and the `flowdrop_workflow.port_exposure` config schema does not define, **so via the UI every declared input is optional at launch**. The snapshot f… ### [A malformed manifest entry is dropped with a warning, even in strict mode (MAN-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592256) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Malformed manifest entries dropped-with-warning even in strict mode (strict polices the *caller*, not the stored manifest). An empty `node_id`/`port` drops the same way. - **Implementation:** `:74-86` - **Guaranteed by:** 2 tests Rule `MAN-14` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-14` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [Strict mode refuses an undeclared input by name (MAN-13 (G3))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592255) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `strict: TRUE` (launcher) throws `\InvalidArgumentException` naming the offending key and the workflow; lenient (session) drops it and logs a `warning` carrying `not a declared input name` and `@name` — never silently. In **both** modes the value is never written into the returned `initialData` (the `continue` precedes every write). ⚠ Amended by API-2: the lenient session mode is slated for **deletion**; strict becomes the only externally reachable behavior. - **Implementation:** `:54-72` - **Guaranteed by:** 2 tests Rule `MAN-13 (G3)` of `GR-MAN` in `docs/development/specification-registry.… ### [Node-keyed pass-through is an internal contract (MAN-12 (G2))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592254) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Node-keyed pass-through is an internal contract (session/chat_input); the public launch boundary refuses it. ⚠ Amended by API-2: the session door today `array_merge`s **raw caller input** into this internal shape (`SessionExecutionService.php:639-642`) — the "internal" framing only holds once API-2 lands and the pass-through is unreachable from outside. - **Implementation:** `:45-52`; launcher `:219-224` - **Guaranteed by:** 3 tests (pin the launcher side; the session leak is API-2's ❌) Rule `MAN-12 (G2)` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a gr… ### [A named input resolves to its node and port (MAN-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592253) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Named input resolves to `initialData[node_id][port]`. - **Implementation:** `:33-36` - **Guaranteed by:** Rule `MAN-11` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [A declared manifest name wins over the node-keyed pass-through (MAN-10 (G1))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592252) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Declared manifest names win over node-id pass-through. - **Implementation:** `WorkflowSchemaResolver.php:41-44` - **Guaranteed by:** `::testDeclaredNameWinsOverNodeIdPassThrough` Rule `MAN-10 (G1)` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-10 (G1)` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [A workflow used as a node exposes its manifest, with a cycle guard (MAN-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592251) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Workflow-as-port composition: cycle guard keyed on workflow id → `{type:object, properties:{}}` + warning; sibling re-entry allowed. - **Implementation:** `:57-66,102-103` - **Guaranteed by:** 2 tests Rule `MAN-9` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-9` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [An unresolvable manifest entry is dropped from the snapshot (MAN-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592250) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: *Unresolvable* entries (node missing, plugin missing, port not declared by the plugin) skipped with log warning. ⚠ A *structurally malformed* entry (missing/empty `name`/`node_id`/`port`) is skipped **silently** — the shape guard logs nothing. - **Implementation:** `:73-96,276-330` - **Guaranteed by:** 4 tests (incl. the silent-skip divergence) Rule `MAN-8` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [Which default values survive into the manifest snapshot (MAN-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592249) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `default` survives when it is NULL, scalar, or a one-level array whose every element is scalar/NULL (an empty array included). An *object* default survives only when it has public vars, and is stored as `get_object_vars()` — i.e. coerced to an array; an empty object and any nested value are dropped, logging `Default value dropped from schema snapshot (unsupported shape).` while every other contract key of the fragment is retained. - **Implementation:** `:212-237` (`sanitiseDefault`), drop site `:139-147` - **Guaranteed by:** 4 tests Rule `MAN-7` of `GR-MAN` in `docs/development/specification… ### [Author metadata overlays the plugin annotations and wins (MAN-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592248) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Author metadata overlaid after stripping, wins over plugin annotations, input direction only; empties dropped. - **Implementation:** `:177-200` - **Guaranteed by:** 3 tests Rule `MAN-6` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [A manifest snapshot is built from the plugin fragment and stripped (MAN-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592247) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Snapshot built per entry from the plugin fragment, stripped by `pickContractKeys()` to exactly `type,enum,format,default,required,properties,items,minimum,maximum,minLength,maxLength,pattern` — every other key dropped **at every depth**, recursing into `properties[*]` and `items`. So plugin annotations (`title`,`description`,`examples`) and `x-*` extensions never reach the stored snapshot; annotations are re-attached at read time only (`?annotated=1`, MAN-6). - **Implementation:** `WorkflowSchemaBuilder.php:28-41` (CONTRACT_KEYS), `:116-152` - **Guaranteed by:** 2 tests (incl. `::testContract… ### [The validator guards manifest integrity (MAN-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592246) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: R4 guards manifest integrity (see GR-VAL R4.a–d). - **Implementation:** — - **Guaranteed by:** — (cross-reference; R4.a–d carry the tests) Rule `MAN-4` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [The authoring picker offers only ports that exist (MAN-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592245) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: The authoring picker is this module's own workflow form (`FlowDropWorkflowForm::getAvailableNodePorts()`) — there is no second picker anywhere else; the editor package has no workflow-exposure surface at all. It offers metadata-declared ports minus already-exposed pairs, minus `trigger`, and minus ports **not exposed on the node instance** — "hidden means hidden" in both directions, so the picker can no longer produce an entry R10 rejects at save. Exposure is resolved through R10's chain, not a metadata-only read: `PortExposure::instancePorts()` + `PortExposure::isExposed()` (instance `config.… ### [The shape of a manifest entry (MAN-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592244) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Entry shape `{name,node_id,port}` + optional `title,description,examples` (input side only). - **Implementation:** `WorkflowSchemaBuilder.php:177-200` - **Guaranteed by:** `::testAuthorMetadataOverlaid` Rule `MAN-2` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-2` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [A workflow's input ports are a declared manifest, never derived (MAN-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592243) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Workflow input ports are a **declared manifest** (`input_ports`), never derived from the exposure cascade; a plugin gaining a param cannot widen the launch surface. The builder never consults `PortExposure`: a declared entry is built even when the instance hides that port, and an exposed-but-undeclared param never reaches the snapshot. - **Implementation:** form `:143-168`; importer; `WorkflowSchemaBuilder.php:72-101` - **Guaranteed by:** `::testManifestIsIndependentOfExposureCascade` Rule `MAN-1` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable … ### [The dynamic-port form appears only when the node type opts in (DYN-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592242) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A metadata/form rule only: on node-type `configurable` opt-in (= SCH-5) the reserved param is routed to `configSchema` — never `inputSchema`, so it is never a wireable port — with default from the entity `default`, else the schema default, else `[]`; without opt-in it is dropped from both schemas. It says nothing about runtime, where the definitions are resolved as an ordinary schema property and then read back at `ParameterResolver.php:205`. Because the trait declares `default: []`, opting out resolves the definitions to `[]` and the `?? $workflowValues[…]` fallback there is unreachable — so … ### [Dynamic ports have no exposure semantics (DYN-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592241) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Dynamic ports have NO exposure semantics, and by construction rather than by exemption: the port name is absent from the plugin's `parameterSchema`/`outputSchema`, so every exposure gate misses it. `ParameterResolver` forwards the value from `runtimeInputs` after the main loop, with no exposure check; `filterUnexposedOutputs` iterates declared schema properties only, so a dynamic output's value is never stripped; R7 skips the edge because there is no metadata exposure default to enforce against. **Correction:** R10 does *not* skip it — a dynamic port named in a workflow-exposure entry is refus… ### [A static parameter name beats a dynamic one (DYN-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592240) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Static param names beat dynamic ones (collision → dynamic ignored). - **Implementation:** `ParameterResolver.php:173-175` - **Guaranteed by:** `ports-dynamic-passthrough.yml` Rule `DYN-5` of `GR-DYN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DYN-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592094 ### [An unconnected dynamic port resolves to NULL, with its key present (DYN-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592239) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unconnected dynamic ports yield NULL (key present). - **Implementation:** `:233-252` - **Guaranteed by:** `DynamicPortTraitTest` Rule `DYN-4` of `GR-DYN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DYN-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592094 ### [Reject an invalid or duplicate dynamic port name (DYN-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592238) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `validatePortNames()` throws on: name not `/^[a-zA-Z][a-zA-Z0-9_]*$/`; forbidden names; duplicates across the input∪output union. Empty/non-array defs skipped silently. Two caveats: the `__`-prefix guard is unreachable (a leading underscore already fails the pattern, so the caller gets the pattern message), and the pattern is not `D`-anchored, so a single trailing newline (`"port\n"`) is accepted. - **Implementation:** `:267-303` - **Guaranteed by:** `DynamicPortTraitTest` Rule `DYN-3` of `GR-DYN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-regist… ### [A dynamic port item needs a name, label and dataType (DYN-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592237) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Port item: `name,label,dataType` required; `dataType` enum closed (`string,number,boolean,array,json,mixed,file,image`), default `mixed`. The closure is **declarative only** — it constrains the port editor's choices; no PHP path validates per-item constraints, so an out-of-enum `dataType` is accepted at resolution and execution time. - **Implementation:** `:64-68,114-116` - **Guaranteed by:** `DynamicPortTraitTest` Rule `DYN-2` of `GR-DYN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DYN-2` token, and `scripts/spec-coverage.php --check` f… ### [A node type opts into dynamic ports by spreading their schema in (DYN-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592236) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Opt-in by spreading `buildDynamic{Inputs,Outputs}Schema()` into the param schema; declared as reserved array params, default `[]`. - **Implementation:** `DynamicPortTrait.php:78-190` - **Guaranteed by:** `DynamicPortTraitTest` Rule `DYN-1` of `GR-DYN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DYN-1` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592094 ### [Port order is cosmetic and the engine never reads it (EXPO-17)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592235) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `displayOrder`/`x-port-order` is cosmetic only — the engine never reads it (fdnpm's counterpart is `NodePort.displayOrder`; `x-port-order` appears nowhere in that repo's source). - **Implementation:** `NodePort.php:47-57` - **Guaranteed by:** `PortSchemaExtensionReachTest::testPortOrderIsConfinedToTheMetadataLayer` (grep-backed: only the DTO and the metadata resolver) + `NodePortTest` / `NodeMetadataResolverTransformPortsTest` for the mapping Rule `EXPO-17` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-17` token, and `scr… ### [The exposure checkbox seeds from the saved value (EXPO-16)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592234) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Each `exposed_by_default` checkbox seeds from the saved entity value; with none it mirrors `PortExposure::isExposedByDefault($schema)` **only while the port exists** (input: `connectable` ticked; output: `exposed` ticked) and reads unchecked otherwise. Both are `#states: enabled` on that sibling selector, and a disabled checkbox is not submitted — so a port that does not exist never shows a greyed-out tick and cannot be submitted as exposed. - **Implementation:** `NodeTypeFormSectionsTrait.php:235-247,485-496` - **Guaranteed by:** `NodeTypeFormExposureSeedingTest` (saved value wins; suggestio… ### [Which parameters a model may fill on a tool call (EXPO-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592233) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Tool-fillable set: param model-fillable iff `connectable && exposed` and no data edge feeds it. - **Implementation:** `ToolParameterScope.php:76-88` - **Guaranteed by:** `ToolParameterScopeTest` Rule `EXPO-15` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-15` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [Stripping runs before the unified output port is composed (EXPO-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592232) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Stripping runs before unified I/O output composition, serializability check, Output wrapping, job records, checkpoints, real-time, tool results. - **Implementation:** `:199-226` - **Guaranteed by:** `NodeRuntimeServiceOutputExposureOrderTest` (ordering-sensitive by construction: a hidden port never reappears inside the unified `output` — which filters on `exposed` only — and a json-hostile value on a hidden port does not fail the node) Rule `EXPO-14` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-14` token, and `scripts/sp… ### [An output the node type hides is stripped unconditionally (EXPO-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592231) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Entity `exposed: FALSE` → stripped unconditionally; else instance override → type default → TRUE. - **Implementation:** `:742-760` - **Guaranteed by:** 5 tests + fixture Rule `EXPO-13` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-13` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [Control outputs are never stripped (EXPO-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592230) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `CONTROL_OUTPUTS` (`active_branches`,`state_update`) never stripped. - **Implementation:** `:739-741` - **Guaranteed by:** `::testControlOutputsAreNeverStripped` Rule `EXPO-12` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-12` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [A hidden output's value is stripped where it is produced (EXPO-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592229) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Output stripping iterates the plugin's `getOutputSchema()['properties']` only, so undeclared keys (dynamic outputs, reserved control ports) pass through. ⚠ **Product gap — contradicts the exposure invariant:** two early-outs bypass the pass entirely, an empty `$result` and a plugin whose output schema declares **no** properties. In the second case nothing is stripped even when the node type marks the output `exposed: FALSE`, so a hidden output's value is delivered. - **Implementation:** `NodeRuntimeService.php:715-724`, loop `:730` - **Guaranteed by:** output-exposure suite (incl. `::testEmpt… ### [A hidden input port receives no runtime value (EXPO-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592228) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Runtime input gating: for a connectable-but-hidden port Priority 1 is *skipped*, not failed — the runtime/LLM value is ignored and resolution continues to the configured value when the param is `configurable` and present (`SOURCE_CONFIG`), else to the entity/schema default (`SOURCE_DEFAULT`). Never `SOURCE_RUNTIME`, and never NULL-by-omission: hiding a port changes precedence, it does not unset the parameter. Internal `__`-prefixed params sit outside the gate and always accept runtime input. - **Implementation:** `ParameterResolver.php:269` (gate `$isInternal \|\| ($connectable && $exposed)`)… ### [The one-time exposure freeze writes only the hidden entries (EXPO-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592227) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: One-time freezes: `update_10004` writes FALSE-only, idempotent, never overwrites an existing key, skips non-ports (non-connectable param / `exposed: FALSE` output); `update_10005` repairs the alpha10 sweep, unsetting only exact-FALSE, instance overrides survive. - **Implementation:** `flowdrop_node_type.install:167-315` - **Guaranteed by:** `ExposureFreezeUpdateTest` (10004) + `ExposureSweepRepairUpdateTest` (10005) Rule `EXPO-9` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-9` token, and `scripts/spec-coverage.php --chec… ### [A parameter added after install has no stored exposure until a re-save (EXPO-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592226) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **Known seam:** a plugin param added post-install with no re-save has no config key → runtime treats it as exposed regardless of the plugin's FALSE suggestion. - **Implementation:** doc `:56-61` - **Guaranteed by:** `ports-absent-flag-polarity.yml` Rule `EXPO-8` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [Materialize an exposure entry only when it diverges from the default (EXPO-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592225) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Materialization divergent-only, destructive-on-TRUE: config `exposed_by_default: FALSE` writes the x-flag; anything else unsets it. - **Implementation:** `NodeMetadataResolver.php:658-664,744-750` - **Guaranteed by:** derive-schemas suite Rule `EXPO-7` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [The plugin's exposure hint is read at authoring time only (EXPO-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592224) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `x-exposed-by-default` read only at authoring time (form seeding ×2, generator freeze, the two freeze update hooks) — never at execution. **Correction:** the flag is also read once on the API-generation path, at `NodeMetadataResolver::transformSchemaToPorts`, but the schema it reads there has already had the flag re-written from config (EXPO-7), so the plugin's own suggestion still never reaches generated metadata. - **Implementation:** 3 cited sites + `flowdrop_node_type.install`, `NodeMetadataResolver.php:816` - **Guaranteed by:** `PortSchemaExtensionReachTest` (grep-backed: the 6 productio… ### [A schema hides a port by default only when it says so exactly (EXPO-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592223) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `isExposedByDefault(schema)` FALSE only when `x-exposed-by-default` is exactly FALSE. - **Implementation:** `:95-97` - **Guaranteed by:** `PortExposureTest::testIsExposedByDefaultIsFalseOnlyForAnExactFalse` (identity, not truthiness: NULL/`0`/`''`/`'false'` all stay exposed) Rule `EXPO-5` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [An untouched node stores no ports key, so the default always applies (EXPO-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592222) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Untouched node stores no `ports` key → default always applies. - **Implementation:** `:38-41` - **Guaranteed by:** Rule `EXPO-4` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [How a port direction maps to its config key (EXPO-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592221) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Direction key mapping: OUTPUT→`outputs`, anything else→`inputs`; overrides direction-scoped. - **Implementation:** `:55` - **Guaranteed by:** Rule `EXPO-3` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [An instance override decides exposure before any default does (EXPO-2 (D3))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592220) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `isExposed`: scan direction-scoped `config.ports` for entry with `exposed` key → that value; else `exposedByDefault`. - **Implementation:** `:54-68` - **Guaranteed by:** 4 cases Rule `EXPO-2 (D3)` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-2 (D3)` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [PortExposure is the only PHP accessor for effective exposure (EXPO-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592219) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `PortExposure` is the single PHP accessor for effective exposure (mirrors the editor package's `isPortExposed` node-level check); 6 consumers: ParameterResolver, ToolParameterScope, R7, R10, NodeRuntimeService, and the workflow form's exposure picker (MAN-3). `instancePorts()` is the one place `data.config.ports` is located on a stored node, so the save boundary and the picker read the override from the same slot. - **Implementation:** `src/Utility/PortExposure.php:8-33` - **Guaranteed by:** `PortExposureTest` Rule `EXPO-1` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests … ### [A config default is written only for a configurable parameter (CFG-18)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592218) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `configDefaults[name]` written only when configurable and effective default non-NULL. - **Implementation:** `NodeMetadataResolver.php:680-683` - **Guaranteed by:** `NodeMetadataResolverDeriveSchemasTest` Rule `CFG-18` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-18` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [The unified input merge only fills connectable parameters (CFG-17)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592217) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unified I/O merge filters on `connectable` only; the main-loop re-gate drops hidden-port smuggled values (two guards, one outcome). - **Implementation:** `:387` vs `:269` - **Guaranteed by:** same fixture Rule `CFG-17` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-17` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [The reserved input port is decomposed before the schema loop (CFG-16)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592216) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: The reserved `input` port is decomposed **before** the schema loop. If its value is not an array nothing is decomposed: `warning: "Unified 'input' value is not an array, skipping decomposition"` is logged and the runtime inputs are returned unchanged — the raw `input` key survives, so a schema property literally named `input` still receives the scalar. Otherwise only keys that are `connectable`, internal (`__`) or a declared dynamic-port name are kept (the rest logged at debug: "Filtered non-connectable key"), and every individually wired port then overwrites the same key from the payload. - … ### [Every dynamic input is present in the resolved bag (CFG-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592215) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: After the schema loop, each `dynamicInputs[].name` present in the merged runtime inputs is copied into the bag **verbatim** — no exposure gate, no `required` check, no `validateValue()` call, so the entry's declared `type`/`dataType` is DECLARATIVE only (cf. DYN-2). A name that is already a key in the bag (any schema property, including one resolved to NULL) is skipped, so the statically resolved value wins; empty names are skipped. Definitions are read from the *resolved* `dynamicInputs` value, falling back to raw config. - **Implementation:** `:198-221`; verbatim forward at `:215`, collisio… ### [Every schema property is present in the bag, NULL when unresolved (CFG-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592214) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Every schema property is present in the bag, NULL when unresolved. - **Implementation:** `:183` - **Guaranteed by:** same fixture Rule `CFG-14` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-14` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [The resolved bag holds exactly the schema's keys plus dynamic ports (CFG-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592213) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Resolved bag = exactly the plugin schema's property keys (+ dynamic forwards); unknown config keys never reach the processor. - **Implementation:** `:113-221` - **Guaranteed by:** `ports-resolved-bag-shape.yml` Rule `CFG-13` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-13` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Format validation covers nine formats and ignores the rest (CFG-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592212) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `format` validation covers 9 formats; unknown formats pass. - **Implementation:** `:597-628` - **Guaranteed by:** `ports-validation-format-throws.yml` (config path — R6 does **not** check `format`; the resolver is the only guard) + same unit test (all 9 formats + unknown passes) Rule `CFG-12` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-12` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [The type check is a closed match with no coercion (CFG-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592211) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Type check closed-match; unknown type names pass; no coercion. - **Implementation:** `:658-670` - **Guaranteed by:** `ports-validation-no-coercion.yml` (wire path, same R6 caveat) + same unit test (full type matrix) Rule `CFG-11` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [A resolved value is validated against the plugin schema (CFG-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592210) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A non-NULL resolved value is validated against the plugin schema; any violation throws `ParameterValidationException` carrying the failing constraint name. NULL skips validation entirely. `type` and `enum` are checked first (either one failing returns immediately); the remaining constraints are then selected by the value's **PHP runtime type, not the declared `type`** — `minimum`/`maximum`/`exclusiveMinimum`/`exclusiveMaximum`/`multipleOf` run for any `is_numeric()` value (numeric strings included), `minLength`/`maxLength`/`pattern`/`format` for `is_string()`, `minItems`/`maxItems`/`uniqueItem… ### [A required parameter that resolves to NULL fails the node (CFG-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592209) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `required && resolved === NULL` → `MissingParameterException`, after cascade, before validation. - **Implementation:** `:170-176` - **Guaranteed by:** `ports-required-null-default-throws.yml` Rule `CFG-9` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-9` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Internal parameters accept a runtime value but never config (CFG-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592208) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Internal `__` params: always accept runtime, never config, else default; bypass all gates. - **Implementation:** `:261-283` - **Guaranteed by:** `ports-internal-param.yml` Rule `CFG-8` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Presence is key existence, so an explicit NULL wins over a lower priority (CFG-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592207) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Presence = `array_key_exists` at every priority: an explicit NULL at a higher priority **wins** — a wire-delivered NULL beats the author's config, a config NULL beats the schema default. Whether a wire NULL reaches the resolver at all is the *builder's* choice, and there are three builders that disagree: `AbstractOrchestratorBase::buildRuntimeInputData` (`:760`) and `SynchronousOrchestrator::resolveNodeInputs` (`:706`) collect wire values with `array_key_exists`, so a NULL output survives; the StateGraph builder still gates with `isset()` (`StateGraphOrchestrator.php:1621`), so on that path an… ### [Priority 3: fall back to the effective default (CFG-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592206) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Priority 3 DEFAULT: unconditional fallback. - **Implementation:** `:286-287` - **Guaranteed by:** `ports-precedence-full-chain.yml` Rule `CFG-6` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Priority 2: take a config value when the parameter is configurable (CFG-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592205) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Priority 2 CONFIG: iff `!internal AND configurable AND array_key_exists`. - **Implementation:** `:280-283` - **Guaranteed by:** `ports-connectable-not-configurable.yml` Rule `CFG-5` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Priority 1: take a runtime value when the port can receive one (CFG-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592204) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Priority 1 RUNTIME: iff `(internal OR (connectable AND exposed)) AND array_key_exists`. - **Implementation:** `:269-276` - **Guaranteed by:** fixtures + `ParameterResolverExposureTest` Rule `CFG-4` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [An effective default is the entity's, then the plugin's, then NULL (CFG-3 (D4))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592203) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Effective default = `E ?? P ?? NULL`; entity `null` indistinguishable from absent. - **Implementation:** `:142-144` - **Guaranteed by:** `ports-entity-default-overrides-schema.yml` Rule `CFG-3 (D4)` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-3 (D4)` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [The exposure default fails open (CFG-2 (D2))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592202) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `exposedByDefault` fails **open** (`?? TRUE`) — deliberate opposite polarity. - **Implementation:** `:138` - **Guaranteed by:** same fixture (pins the seam) Rule `CFG-2 (D2)` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-2 (D2)` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Gate flags fail closed (CFG-1 (D1))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592201) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Gate flags fail **closed** (`?? FALSE`). - **Implementation:** `ParameterResolver.php:128-130` - **Guaranteed by:** `ports-absent-flag-polarity.yml` Rule `CFG-1 (D1)` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-1 (D1)` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Config fields are ordered by their declared order (SCH-31)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592200) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `x-config-order` orders config fields ascending (absent or non-numeric = 0, ties keep declaration order) **inside the generated uiSchema only** — if no property carries a registered `x-group`, `generate()` returns NULL, there is no layout, and `x-config-order` has no effect on the flat form. The pre-2.x spelling `x-display-order` is still read when the new key is absent and logs a deprecation warning naming the property plus both key spellings, **once per property per `generate()` call** (so every form build re-warns); the new key wins when both are present and suppresses the warning. - **Imp… ### [The run path re-enriches from the live node type (SCH-29)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592199) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Run path re-enriches from the live node type then normalizes via `WorkflowDTO::fromArray` — stored metadata never authoritative at run. - **Implementation:** `WorkflowCompiler.php:92-104` - **Guaranteed by:** `WorkflowCompilerRunEnrichmentTest` Rule `SCH-29` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-29` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [The executor plugin id comes from the node type, never from the payload (SCH-28)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592198) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Executor plugin id resolves from the node-type entity, never trusted from stored node metadata. - **Implementation:** `NodeMetadataResolver.php:188-200` - **Guaranteed by:** `NodeMetadataResolverEnrichAnchorTest` + `WorkflowCompilerRunEnrichmentTest` Rule `SCH-28` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-28` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [The wire shape is lean: emit a key only when it diverges from the default (SCH-27)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592197) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Wire shape is lean-by-divergence: `defaultValue` emitted only non-NULL, `exposedByDefault` only FALSE, `displayOrder` only ≠0 — editor must read absence as exposed/0. - **Implementation:** `NodePort.php:172-197` - **Guaranteed by:** `NodePortTest` Rule `SCH-27` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-27` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [The editor catalog serves enabled node types, sorted (SCH-26)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592196) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Editor catalog serves enabled node types only, sorted category→name. - **Implementation:** `NodesController.php:99-130` - **Guaranteed by:** `NodesControllerCatalogTest` Rule `SCH-26` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-26` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Enrichment anchors on the node-type id alone (SCH-25)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592195) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Enrichment anchors on `node_type_id` (via `NodeAnchor::read()`) only: it sets `type` to the constant `universalNode`, replaces `data.metadata`, and normalizes `data` to an array before the write; `data.config`/`id`/`label`/`position` are untouched and re-running is a no-op. When the anchor is empty or the node type no longer builds, the node is returned unchanged — no `data.metadata` key is added. The `data` normalization is defensive only and unreachable in practice: the anchor lives *inside* `data`, so a node whose `data` is not an array returns at the empty-anchor guard before it. - **Impl… ### [Building node data logs and degrades instead of failing the editor (SCH-24)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592194) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `buildForNodeType()` catches `\Exception` only: it logs `Failed to build node data for @id: @error` on the `flowdrop` channel at **error** severity and returns NULL, so `enrichNode()` returns the stored node untouched (no `data.metadata` key written). A `\Throwable` that is not an `\Exception` (e.g. a `TypeError`/`Error` from a broken plugin) is **not** caught and fails the request. - **Implementation:** `:472-478`; unchanged-node path `:120-122` - **Guaranteed by:** (same suite) Rule `SCH-24` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `… ### [The UI schema is generated from the final config schema (SCH-23)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592193) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `uiSchema` is generated from the *final* configSchema (after reserved-prop injection) and is NULL **exactly when no property carries a registered `x-group`** — an unknown group falls back to the default bucket, so a schema tagged only with unknown groups is NULL too and the form stays on its flat path. The baseline ships every group collapsed; `enrichNode()` opens a group per instance when that group's fields are set in `data.config`. - **Implementation:** `:449`; `UiSchemaGenerator.php:106-128`; instance open-state `:134-141` - **Guaranteed by:** (same suite) + `UiSchemaGeneratorTest` Rule … ### [Only a config-edit provider gets a configEdit block (SCH-22)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592192) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `configEdit` populated only for `ConfigEditProviderInterface` implementors. - **Implementation:** `:417-420` - **Guaranteed by:** `NodeMetadataBuildTest` Rule `SCH-22` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-22` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Every node gets a reserved instance title and description (SCH-21)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592191) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved config props: `instanceTitle`/`instanceDescription` on every node; `maxRetries` + `ports` on executable nodes only; skipped if already declared. - **Implementation:** `:487-546` - **Guaranteed by:** `NodeMetadataResolverReservedConfigPropsTest` Rule `SCH-21` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-21` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [A node's visual type comes from the config entity only (SCH-20)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592190) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Visual type comes from the config entity only. When `getSupportedVisualTypes()` holds >1 entry a reserved `nodeType` string property (`enum` = the supported types, `default` = the entity's visual type, `x-group: general`) is written into configSchema, and its config *default* is stored under the same `nodeType` key. Unlike SCH-21's reserved props this write is **unconditional** — it overwrites a plugin-declared `nodeType` property. The `enum` is **declarative only**: nothing validates a stored `data.config.nodeType` against it at run (the entity accessor has no runtime caller besides this line… ### [Both key enumerations skip trigger and hidden parameters (SCH-19)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592189) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Both key enumerations skip `trigger` and hidden params (`format: hidden` / `hidden: TRUE`) — a hidden port does not exist on the instance, so it never appears in a unified port description. - **Implementation:** `:872-940` - **Guaranteed by:** `NodeMetadataResolverKeyEnumerationTest` Rule `SCH-19` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-19` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Prepend the unified output port when the node exposes one (SCH-18)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592188) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unified I/O `output` port prepended iff `isUnifiedOutputExposed()`, description enumerates exposed output keys only. - **Implementation:** `:361-376` - **Guaranteed by:** (same suite) Rule `SCH-18` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-18` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Prepend the unified input port when the node exposes one (SCH-17)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592187) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unified I/O `input` port prepended iff `isUnifiedInputExposed()`, dataType json, description enumerates connectable keys only. - **Implementation:** `:342-357` - **Guaranteed by:** `UnifiedIoPortInjectionTest` Rule `SCH-17` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-17` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [The exposure defaults of the reserved ports (SCH-16)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592186) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved-port exposure defaults table: input/output/tool/error=F, trigger in/out=T; node type overrides per key, storing divergent keys only. - **Implementation:** `FlowDropNodeType.php:235-242` - **Guaranteed by:** `FlowDropNodeTypeReservedPortExposureTest` Rule `SCH-16` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-16` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [An injected port declares its exposure default only when it diverges (SCH-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592185) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Injected reserved ports emit `x-exposed-by-default: FALSE` only when divergent from TRUE. - **Implementation:** 4 sites - **Guaranteed by:** (all 4 injection suites) Rule `SCH-15` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-15` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Inject the reserved error output on every executable node (SCH-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592184) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved `error` output injected except NonExecutable processors, `x-port-order: 120`, ships hidden. - **Implementation:** `:344-357` → `:819` - **Guaranteed by:** `ErrorPortInjectionTest` Rule `SCH-14` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-14` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Inject the reserved tool output only on a tool-exposed node (SCH-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592183) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved `tool` output injected iff `isToolExposed()`, `x-port-order: 110`. - **Implementation:** `:323-336` → `:819` - **Guaranteed by:** `ToolOutputInjectionTest` Rule `SCH-13` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-13` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Inject the reserved trigger output on every node but a terminal node (SCH-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592182) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved `trigger` output injected except Terminal processors, `x-port-order: 100`. - **Implementation:** `:305-318` → `:819` - **Guaranteed by:** `TriggerOutputInjectionTest` Rule `SCH-12` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-12` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Inject the reserved trigger input on every node but a start node (SCH-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592181) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved `trigger` input injected on every node except Start processors (unless already declared), carrying `x-port-order: 100`. - **Implementation:** `:276-289` → `:819` - **Guaranteed by:** `TriggerInputInjectionTest` Rule `SCH-11` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [The schema-to-dataType map is closed (SCH-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592180) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Schema→dataType map is closed: `string→string`, `number\|integer→number`, `boolean→boolean`, `array→array`, `object→json`, `tool→tool`, `mixed→mixed`, `trigger→trigger`; any other or absent type yields `string`. Every value the map can return must also be declared by `NodesController::getPortConfiguration()` — a coupling that is **test-enforced only, with no runtime assertion**; an undeclared type would leave the port compatible with nothing in the editor. - **Implementation:** `:868-882` - **Guaranteed by:** same suite + `NodesControllerPortConfigTest` Rule `SCH-10` of `GR-SCHEMA` in `docs/… ### [A union type normalizes to its first non-null member (SCH-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592179) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Union types normalize to first non-null member; all-null/empty → `string`. - **Implementation:** `:812-828` - **Guaranteed by:** (same suite) Rule `SCH-9` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-9` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [One mapping turns a schema into ports (SCH-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592178) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `transformSchemaToPorts()` is the only schema→NodePort mapping for schema-derived ports: `id` = the property key, `name` = `title` ?? key, `dataType` = the mapped normalized `type`, `required` = membership in the schema's `required` list, `defaultValue` = `default` ?? NULL, `exposedByDefault` = `PortExposure::isExposedByDefault()`, `displayOrder` = `(int) x-port-order` ?? 0. The two unified I/O ports (SCH-17/18) bypass it — they are constructed directly, always `dataType: json` and `displayOrder: 0`. - **Implementation:** `:795-824` vs the direct construction at `:371-379`/`:390-398` - **Guar… ### [An output reaches the editor only when the node type exposes it (SCH-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592177) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Output survives into metadata iff entity `outputs[name]['exposed'] ?? TRUE` (fail-open). - **Implementation:** `:726-753` - **Guaranteed by:** `ports-output-stripping.yml` Rule `SCH-7` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [A parameter is required on the input side only when it is not configurable (SCH-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592176) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `required` emitted into inputSchema.required iff `required && !configurable`; into configSchema.required iff `required && !connectable`. - **Implementation:** `:666-678` - **Guaranteed by:** `NodeMetadataResolverDeriveSchemasTest` Rule `SCH-6` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Reserved config-only parameters never become ports (SCH-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592175) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved config-only params (`dynamicInputs`,`dynamicOutputs`,`branches`) are never input ports; on per-node-type `configurable: TRUE` opt-in they enter configSchema and always get a `configDefaults` entry — entity `default`, else schema `default`, else `[]`. Never omitted and never NULL, unlike an ordinary configurable param, whose entry is omitted when its resolved default is NULL. - **Implementation:** `:635-645` vs the ordinary path at `:704-706` - **Guaranteed by:** (5 cases in suite) Rule `SCH-5` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a gr… ### [Hidden parameters are dropped from both derived schemas (SCH-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592174) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `format: hidden` / `hidden: TRUE` params are dropped from both derived schemas **and** from `configDefaults`, overriding entity `connectable`/`configurable`. The hidden check runs AFTER the reserved config-only branch (SCH-5), so a hidden `dynamicInputs`/`dynamicOutputs`/`branches` is still surfaced into configSchema when the node type opts in — the hidden marker does not suppress a reserved param. - **Implementation:** `:650-654`, reached only past the reserved branch at `:635-645` - **Guaranteed by:** `NodeMetadataResolverDeriveSchemasTest` Rule `SCH-4` of `GR-SCHEMA` in `docs/development/… ### [Deriving splits one parameter schema into an input schema and a config schema (SCH-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592173) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `deriveSchemas()` splits one param schema in two: param ∈ inputSchema iff `connectable`, ∈ configSchema iff `configurable`; both/one/neither legal. - **Implementation:** `NodeMetadataResolver.php:589-700` - **Guaranteed by:** (same suite) Rule `SCH-3` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Schema derivation reads its gate flags from the plugin schema (SCH-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592172) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `deriveSchemas()` reads the gate flags (`connectable`/`configurable`/`required`) from the node-type entity's parameter config only, each defaulting FALSE when the entity declares no entry — so a param the entity never declares appears in neither derived schema and in neither `required` list. Same-named keys in a plugin's `getParameterSchema()` are never read, but they are **not stripped** either: `cleanPropertySchema()` is a pass-through, so they survive verbatim into the served input/config schema and no consumer may read them. - **Implementation:** `NodeMetadataResolver.php:661-663`; `clean… ### [A node's input and output surface comes only from its two schema methods (SCH-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592171) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Input surface only via `getParameterSchema()`, output only via `getOutputSchema()`; the plugin attribute carries no port/visual data. - **Implementation:** `src/Attribute/FlowDropNodeProcessor.php:36-46` - **Guaranteed by:** — (structural) Rule `SCH-1` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-1` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Transport edges and job-metadata edges each own their own key names (EDGE-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592170) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Two edge domains, one key bag each. `EdgeKeys` names **only** the camelCase transport keys (`source`, `target`, `sourceHandle`, `targetHandle`) that `JsApi\Edge` reads and writes; the snake_case job-metadata record (`source_handle`, `target_handle`, `is_trigger`, `is_loopback`, `is_tool`, `branch_name`, `edge_id`) is owned solely by `ExecutionEdge`, which is the only reader and writer of those names. `EdgeKeys` must never carry a job-metadata constant: the four it used to carry (`IS_TRIGGER`, `IS_LOOPBACK`, `BRANCH_NAME`, `EDGE_ID`) had no reader at all and made the neighbouring `EdgeKeys::SOU… ### [Edge conditions are a removed feature that is tolerated but never read (EDGE-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592169) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `edge.data.condition` is a removed feature: schema-tolerated (declared `nullable`, so a stored workflow carrying it round-trips unchanged under strict config-schema validation), logged, always routes. The warning fires only for a non-empty *string* condition, and it is emitted where a source node's outgoing edges are resolved — so "once per edge" means once per dispatch pass, and a source that re-executes (a loop) warns again rather than once per launch. - **Implementation:** schema `flowdrop_workflow.schema.yml` `flowdrop_workflow.edge_data:condition`; `StateGraphOrchestrator::outgoingEdges(… ### [What makes a node tool-only (EDGE-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592168) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Tool-only node = ≥1 outgoing edge **and** every outgoing edge a tool edge; zero outgoing edges, or any non-tool outgoing edge, means not tool-only. A tool-only node is excluded from the compiled execution graph (`isExcluded($nodeId)` TRUE, reason `tool_only`) and generates no job — it runs inline only when a consumer invokes it as a tool. The classifier owns the rule and `JobGenerationService` reads it; the compiler applies the same rule over its own `DependencyEdge::isToolAvailability()` records and additionally requires a resolvable tool-consumer target. - **Implementation:** `EdgePortClass… ### [An edge is an error edge by its source handle (EDGE-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592167) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Error edge ⇔ an `ExecutionEdge` (the job-metadata record) whose source handle ends `-output-error`. `isErrorEdge()` accepts only that shape, so a transport `JsApi\Edge` is never classified here. Its presence is what makes a failing node return an `error` payload (`{message, code, node_id, retryable}`) and the job be marked FAILED + `error_routed`, with the run continuing down the error edge instead of throwing and failing. - **Implementation:** `src/Utility/EdgePortClassifier.php:85-87`; consumers `AbstractOrchestratorBase.php:741,879`, `StateGraphOrchestrator.php:1602`, `JobGenerationService… ### [An edge is a tool edge by declared type, else by its target handle (EDGE-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592166) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Tool edge ⇔ `data.edgeType === 'tool_availability'` (wins) else target handle ends `-input-tool`. Precedence runs both ways: a declared `tool_availability` makes a non-tool handle a tool edge, and any *other* non-empty string declaration makes a `-input-tool` handle NOT one. Only an absent, empty or non-string declaration falls through to the handle. - **Implementation:** classifier - **Guaranteed by:** `EdgePortClassifierTest::testExplicitEdgeTypePrecedence` Rule `EDGE-5` of `GR-EDGE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EDGE-5` … ### [An edge is a loopback edge when its target handle says so (EDGE-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592165) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Loopback edge ⇔ target handle ends `-input-loop_back` (value is `loop_back`, NOT `loopback`). - **Implementation:** `ReservedName.php:121-128` - **Guaranteed by:** `WorkflowCompilerSpecialEdgeTest::testLoopbackEdgeDetectedByHandle` Rule `EDGE-4` of `GR-EDGE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EDGE-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592088 ### [An edge is a trigger edge when its target handle says so (EDGE-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592164) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Trigger edge ⇔ target handle ends `-input-trigger`. - **Implementation:** `ReservedName::PORT_TRIGGER`; classifier - **Guaranteed by:** conformance `topology-*` Rule `EDGE-3` of `GR-EDGE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EDGE-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592088 ### [No wire key is structurally required; an absent one becomes a missing endpoint (EDGE-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592163) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: No wire key is structurally required — absent keys default to `''`/`[]` and become R8 "missing endpoint". - **Implementation:** `src/DTO/JsApi/Edge.php:66-75` - **Guaranteed by:** `EdgeTest::testDefaultsForMissingKeys`; `WorkflowValidatorTest::testEdge2KeylessEdgeIsReportedAsMissingEndpoints` Rule `EDGE-2` of `GR-EDGE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EDGE-2` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592088 ### [How a port handle encodes its node, direction and port name (EDGE-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592162) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Handle encoding `{nodeId}-{input\|output}-{portName}`; port name = everything after the FIRST `-input-`/`-output-`; kind classification is suffix-exact, never substring. - **Implementation:** `src/Utility/EdgePortClassifier.php` - **Guaranteed by:** `EdgePortClassifierTest::testExactSuffixMatching`, `::testPortNameExtraction`, `::testPortNameSplitsAtTheFirstDirectionMarker` Rule `EDGE-1` of `GR-EDGE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EDGE-1` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree.… ### [Refuse a duplicate edge between the same two ports (R13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592161) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Duplicate parallel edges rejected (`R13_EDGE_PARALLEL_DUPLICATE`); the error names the earlier edge's position. Detection keys on the two endpoint ids and the two **raw handle strings** verbatim (`source|sourceHandle|target|targetHandle`) with no port-name parsing or normalisation — so edges between the same nodes over *different* ports stay valid, and two edges over the same *logical* port spelled differently (one with `sourceHandle` omitted, one with the explicit `{node}-output-{port}` handle) are **both accepted**. Edges with an empty endpoint are excluded from the comparison entirely (DECI… ### [Refuse an edge from a node to itself (R12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592160) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: An edge whose non-empty `source` equals its `target` is rejected (`R12_EDGE_SELF`) at `edge.{index}` **regardless of handles** — wiring a node's own output into its own input is still refused — and regardless of whether the node exists (a self-edge on a deleted node also earns R8's two errors). An edge with an empty `source` is never reported as a self-edge even when the target is empty too: R5/R8 own that (DECIDED ← OPEN-7). - **Implementation:** E - **Guaranteed by:** `::testR12SelfEdgeIsRejected`, `::testR12SelfEdgeWithDistinctHandlesIsStillRejected` Rule `R12` of `GR-VAL` in `docs/develo… ### [Every configured expression must pass its engine's check at save (R11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592159) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Every configured expression must pass its engine's `validate()` at save (`R11_EXPRESSION_INVALID`); the error names the node, config key, engine and expression. Config carries no generic "this is an expression" marker, so the check is scoped to the known expression-bearing keys of the in-tree processors: `data_extractor.path`, `data_mapper` dynamic output `value`s, `data_shaper.mapping` sources (special values like `_LITERAL:`/`_NOW_` skipped, nested `_source`/`_each` walked), `prompt_template.template` (twig). All four engines are wired; twig/jsonpath verdicts are trivially permissive (LANG-1… ### [A workflow exposure must target a port exposed on the node instance (R10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592158) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Workflow-exposure entry must target a port exposed on the target node **instance** (`R10_EXPOSURE_HIDDEN_PORT`) — the exposure-map twin of R7, resolved through the same chain (instance `config.ports[].exposed` override → metadata `exposedByDefault` → exposed): hidden means hidden in both directions. The error names the workflow port, the node and the node port. Metadata-undeclared (dynamic) ports are out of scope, mirroring R7.d; disjoint from R7 by construction — R7 inspects edges, R10 inspects exposure entries, so one hidden port never earns one entry two reports. Doctor remedies: Expose the… ### [A node's node-type anchor must resolve to a node type that exists (R9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592157) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Node's `node_type_id` anchor must resolve to an existing node type (`R9_NODE_TYPE_UNKNOWN`); the error names the node and the type. Anchor-less nodes (Notes and other non-executables) are out of scope. Distinct from R1 by construction: entity missing → R9 (no plugin to check, R1 quiet); entity present but plugin missing → R1 — one defect, one report. BundleImporter generates a bundle's node types *before* validating (rolling them back when the import is refused) and a dry run discounts R9 errors for manifest-generatable types, so bundle import keeps working; config sync runs no validation, so … ### [Edge ids must be present and unique at save (DECIDED) (R3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592156) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Edge `id`s must be present (`R3_EDGE_MISSING_ID`) and unique (`R3_EDGE_DUPLICATE_ID`) at save; read-path minting stays legacy read tolerance only (DECIDED ← OPEN-5). - **Implementation:** E - **Guaranteed by:** `::testR3EdgeMissingIdIsRejected`, `::testR3DuplicateEdgeIdIsRejected` Rule `R3` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Node ids must be unique (DECIDED) (R2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592155) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Node `id`s must be unique (`R2_NODE_DUPLICATE_ID`) — the read path keys nodes by id, so a duplicate would silently collapse last-wins (DECIDED ← OPEN-4). - **Implementation:** E - **Guaranteed by:** `::testR2DuplicateNodeIdIsRejected` Rule `R2` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R2` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [The whole validator runs again at launch (VAL-LAUNCH)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592154) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: The full validator re-runs at launch (defense in depth): `WorkflowLauncher::validateDefinition()` re-runs every rule on the stored definition and, on any error, logs a warning and throws `WorkflowLaunchValidationException` carrying the `ValidationResult` — **before** any job generation, pipeline creation, deferred scheduling or queue item. The HTTP boundary maps it to 422 with per-error `code`/`message`/`locator` detail, mirroring the save path. - **Implementation:** inv - **Guaranteed by:** `CanvasHiddenInputPortTest` (3), `WorkflowLauncherTest::testInvalidDefinitionIsRejectedBeforeLaunch` (… ### [The validator instantiates plugins only for the exposure checks (VAL-PERF)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592153) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: The validator calls `FlowDropNodeProcessorPluginManager::createInstance()` only for the R4.d/R10 exposure checks, memoised per plugin id, so a workflow with no exposure entries makes zero *direct* constructions. **Not** a claim about total plugin construction: R6's config-schema lookup and R7/R10's `portExposureDefaults` both call `NodeMetadataResolver::buildForNodeTypeId()` (`NodeMetadataResolver.php:253`), which constructs the executor plugin itself — once per distinct node type per validation. R1 and W-T stay definition-only (`hasDefinition()`/`getDefinition()`). - **Implementation:** inv … ### [Warn about an edge leaving a terminal node (W-T)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592152) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Every edge whose **source** node's plugin class implements `TerminalNodeProcessorInterface` (read from the plugin definition's `class`, never instantiated) yields one non-blocking warning at `edge.{index}` naming the target and the terminal source — so a terminal node with N outgoing edges produces N warnings and `isValid()` stays TRUE. Only sources are inspected (an edgeless workflow looks nothing up) and the **target is not checked for existence**, so an edge from a terminal node to a deleted node produces this warning *and* R8's `R8_EDGE_TARGET_MISSING`; a dangling *source* is skipped (R8 o… ### [An exposure must name a port the plugin declares (R4.d)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592151) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Exposure `port` must be declared by plugin param schema (input) / output schema (output). The check still skips a node whose plugin is unresolvable (don't double-report R1/R9), but the old import-path hole is closed: R9 rejects a node anchored to an unknown type, and BundleImporter now generates a bundle's node types *before* validating, so the skip no longer swallows the normal import path — it remains only for anchor-less nodes and for types whose plugin R1 already reports. **Annotated 2026-07-30:** the skip covers only the port-declaration check and R10 (both need the plugin) — R4.a's name … ### [An exposure must name a node that exists (R4.c)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592150) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Exposure `node_id` must exist; failure skips the entry's other checks. - **Implementation:** E - **Guaranteed by:** `::testR4NodeMissing` Rule `R4.c` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R4.c` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Exposure names must be unique per side (R4.b)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592149) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Exposure names unique per side (input/output independent). - **Implementation:** E - **Guaranteed by:** `::testR4DuplicateName` Rule `R4.b` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R4.b` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [An exposure name must match the allowed format (R4.a)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592148) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Exposure `name` must match `/^[a-z0-9_-]+$/` — empty or absent included — rejected with `R4_NAME_FORMAT` at `schema.{side}.{index}`. Unlike R4.c this does **not** skip the entry's remaining checks: R4.b uniqueness, node existence and port declaration all still run, so two name-less entries yield two `R4_NAME_FORMAT` plus one `R4_NAME_DUPLICATE` on the empty name. - **Implementation:** E - **Guaranteed by:** `::testR4NameFormat`, `::testR4NameFormatDoesNotSkipTheEntry` Rule `R4.a` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R4… ### [Skip the edge-exposure check where another rule already owns the problem (R7.e/f)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592147) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unparseable handle, empty/unknown endpoint node, unresolvable node type → R7 skipped (R5/R8/R1 own those). **Annotated 2026-07-30:** the skip is **per endpoint, not per edge** — an edge with one unusable handle or one dangling node still has its other endpoint checked, so an R8 dangling-source error and an R7 hidden-target error can both be reported for the same edge (by construction, since the two passes are independent). The unresolvable-type arm also splits by cause: an unknown node type is reported by R9 (not R1), a resolvable type whose executor plugin is missing by R1, and an anchor-less… ### [A port the node type never declared is out of the edge-exposure check (R7.d)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592146) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Port absent from node-type metadata (dynamic/user-defined) is out of R7 scope. - **Implementation:** accept - **Guaranteed by:** `::testExposedAndUnknownPortEdgesAreValid` Rule `R7.d` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R7.d` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Effective exposure comes from the instance config, then the node-type default (R7.c)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592145) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Effective exposure = instance `config.ports[].exposed` override, else metadata `exposedByDefault`; exposing via config legalizes the edge. - **Implementation:** accept - **Guaranteed by:** `::testEdgeFromExposedErrorPortIsValid` Rule `R7.c` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R7.c` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse an edge out of a hidden output port (R7.b)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592144) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Edge from a declared-but-not-exposed **output** port rejected (`R7_EDGE_SOURCE_NOT_EXPOSED`) at `edge.{index}` (canonical: `error`, ships hidden). - **Implementation:** E - **Guaranteed by:** `::testEdgeFromNotExposedErrorPortIsRejected` Rule `R7.b` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R7.b` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse an edge into a hidden input port (R7.a)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592143) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Edge into a declared-but-not-exposed **input** port rejected (`R7_EDGE_TARGET_NOT_EXPOSED`) at `edge.{index}`. - **Implementation:** E - **Guaranteed by:** `::testEdgeIntoNotExposedInputPortIsRejected` Rule `R7.a` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R7.a` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [An edge missing both endpoints reports both errors (R8.c)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592142) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Both endpoints missing → two errors, same locator. - **Implementation:** E - **Guaranteed by:** `::testR8BothEndpointsMissingYieldTwoErrors` Rule `R8.c` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R8.c` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse an edge whose target node does not exist (R8.b)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592141) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Edge with an unresolvable **target** rejected (`R8_EDGE_TARGET_MISSING`); empty = missing. - **Implementation:** E - **Guaranteed by:** `::testR8DanglingTargetIsRejected` Rule `R8.b` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R8.b` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse an edge whose source node does not exist (R8.a)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592140) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Edge with an unresolvable **source** rejected (`R8_EDGE_SOURCE_MISSING`); empty = missing. - **Implementation:** E - **Guaranteed by:** `::testR8DanglingSourceIsRejected` Rule `R8.a` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R8.a` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Retire validateParams() from the processor contract (R6.k)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592139) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **RETIRED — `validateParams()` deleted from the processor contract (2.x).** The method was never invocable to any effect (the base returned success and no verdict gated anything), so it was removed from `FlowDropNodeProcessorInterface` along with every override and both runtime call sites (`NodeRuntimeService::validateNode`, `ScopedToolInvoker::validateArgs`). Save-time schema/expression validation (R6, R11) is the only config-verdict surface; invalid runtime values fail inside the node (GR-ERR). - **Implementation:** design - **Guaranteed by:** None — see the rule text. Rule `R6.k` of `GR-V… ### [Warn when a secret reference is written without its leading $ (R6.l)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592138) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A config **string** containing `{{ secrets.` without the leading `$` produces a non-blocking warning at `node.{id}.config.{key}` telling the author to write `${{ secrets.NAME }}`; array-valued config is walked recursively (so a reference nested in JSON-shaped config such as HTTP headers is covered), a correctly written `${{ secrets.X }}` produces none, and the save is never blocked. Implemented as a local regex, never a call into the runtime secret resolver — flowdrop_workflow sits below flowdrop_runtime in the module layering. - **Implementation:** W - **Guaranteed by:** `::testMalformedSecr… ### [An unresolvable node type skips only the schema-driven config checks (R6.j)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592137) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unresolvable node type skips the *schema-driven* checks of R6 — required keys, type/enum/bounds/pattern and the R6.c unknown-key warning are all skipped. **Annotated 2026-07-30:** not literally "all of R6" — the R6.a non-array guard runs *before* the schema lookup, so a scalar `data.config` is still rejected on a node whose type resolves to no metadata. - **Implementation:** accept - **Guaranteed by:** `::testR6UnresolvableNodeTypeSkipsSchemaChecks`, `::testR6NonArrayConfigIsRejectedWithoutResolvableType` Rule `R6.j` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to … ### [A NULL config value means unset and is never validated (R6.i)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592136) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Config value NULL = unset, never validated. - **Implementation:** accept - **Guaranteed by:** `::testR6ExplicitNullSatisfiesRequiredAndIsNotValidated` Rule `R6.i` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.i` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a string that does not match its pattern (R6.h)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592135) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `pattern` mismatch rejected; an *invalid schema pattern* does not block the author. - **Implementation:** E - **Guaranteed by:** `::testR6PatternMismatchIsRejected`, `::testR6InvalidSchemaPatternDoesNotBlockTheAuthor` Rule `R6.h` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.h` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a string outside its length bounds (R6.g)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592134) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `minLength`/`maxLength` (mb_strlen) violations rejected. - **Implementation:** E - **Guaranteed by:** `::testR6LengthBoundsUseCharacterCount` (4-char/8-byte fixture pins the character count) Rule `R6.g` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.g` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a number outside its minimum/maximum (R6.f)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592133) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `minimum`/`maximum` violations rejected (bounds are checked for `int`/`float` values only — a numeric *string* is never bounds-checked). - **Implementation:** E - **Guaranteed by:** `::testR6BelowMinimumIsRejected`, `::testR6AboveMaximumIsRejectedButInRangeAccepted` Rule `R6.f` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.f` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a config value outside its enum (R6.e)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592132) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Value outside `enum` (strict) rejected. - **Implementation:** E - **Guaranteed by:** `::testApiRejectsInvalidConfigValue` Rule `R6.e` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.e` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a config value of the wrong type (R6.d)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592131) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Wrong JSON-schema `type` rejected; unknown type names **pass**. **Shared shape of R6.d–R6.h:** all five raise the *same* code `R6_CONFIG_INVALID` at `node.{id}.config.{key}` and run in one fixed short-circuit order — type → enum → minimum → maximum → minLength → maxLength → pattern — with a `return` after the first violation, so one config key never yields more than one error (a value both outside its `enum` and over `maxLength` reports the enum failure only). They are distinguishable by message text, not by code. - **Implementation:** E - **Guaranteed by:** `::testR6WrongTypeIsRejected`, `::… ### [An unknown config key is a warning, not a refusal (R6.c)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592130) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unknown config key → **warning**, accepted ("ignored at runtime"). - **Implementation:** W - **Guaranteed by:** `WorkflowStructuralValidationTest::testValidatorWarnsButAcceptsUnknownConfigKey` Rule `R6.c` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.c` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Every required config key must be present (R6.b)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592129) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Every key on the **derived** `configSchema.required` list must be present (`array_key_exists` — explicit NULL satisfies); each missing key yields one `R6_CONFIG_REQUIRED` at `node.{id}.config.{key}`. The list is *not* the node type's `required` flags: a param the node type also marks `connectable` is deliberately omitted from `configSchema.required` (SCH-6), so a `required && configurable && connectable` param absent from `data.config` is **accepted at save even when no input edge supplies it** — the omission is decided from the node-type flags, never from the actual edge set. - **Implementat… ### [Refuse a node whose config is not an array (R6.a)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592128) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Non-array `data.config` rejected (`R6_CONFIG_INVALID`) at `node.{id}.config` — but **only on a node carrying a `node_type_id` anchor**: `checkConfig()` returns before the guard for an anchor-less node, so a Note-style node with a scalar `data.config` is accepted by all of R6. - **Implementation:** E - **Guaranteed by:** `WorkflowValidatorTest::testR6NonArrayConfigIsRejected`, `::testR6AnchorLessNodeSkipsTheNonArrayConfigGuard` Rule `R6.a` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.a` token, and `scripts/spec-coverage.php … ### [Report a missing plugin once, not once per port (R1.c)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592127) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A missing plugin is reported once, never re-reported per exposed port. - **Implementation:** — - **Guaranteed by:** `::testMissingPluginIsNotDoubleReported` Rule `R1.c` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R1.c` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [A node with no resolvable node type is skipped by the plugin check (R1.b)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592126) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Node with no `node_type_id` anchor / unresolvable node type is **skipped** by R1 (deferred) — R1's skip stands; a node anchored to an *unknown* type is rejected by R9, while a legitimately anchor-less node stays accepted. - **Implementation:** accept - **Guaranteed by:** `::testR1EmptyPluginIsSkipped` Rule `R1.b` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R1.b` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a node whose executor plugin does not exist (R1.a)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592125) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Node whose node-type-resolved executor plugin has no definition rejected (`R1_PLUGIN_MISSING`), no instantiation. - **Implementation:** E - **Guaranteed by:** `::testR1MissingPlugin`; kernel 422+not-persisted Rule `R1.a` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R1.a` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a node with no id, located by its position (R5.c)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592124) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Node with empty/absent `id` rejected, located by array position. - **Implementation:** E - **Guaranteed by:** `::testR5NodeMissingId` Rule `R5.c` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R5.c` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a workflow with more than 1000 edges (R5.b)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592123) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: >1000 edges rejected (`R5_TOO_MANY_EDGES`). - **Implementation:** E - **Guaranteed by:** `::testR5TooManyEdges` Rule `R5.b` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R5.b` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a workflow with more than 500 nodes (R5.a)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592122) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: >500 nodes rejected (`R5_TOO_MANY_NODES`). - **Implementation:** E - **Guaranteed by:** `WorkflowValidatorTest::testR5TooManyNodes` Rule `R5.a` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R5.a` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Retire the node config-validate endpoint (API-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592121) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **RETIRED — endpoint deleted (2.x).** The node config-validate endpoint (`POST /api/flowdrop/nodes/{plugin_id}/validate`) reported problems the save path accepts: it used the raw plugin schema, not the derived, edge-aware view (same spirit as R6), so it flagged `configurable && required` params an input edge would satisfy — and it could not become edge-aware without a contract change (it received only `config`, no edges). It had ZERO fdnpm consumers, so the ruled fix was deletion: route, `NodesController::validateConfiguration()` and its `validateValueType()` helper are gone. Save-time validat… ### [A session with no workflow is a 409, not a 500 (API-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592120) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: "Session has no workflow" is a dedicated typed exception (`MissingWorkflowException`) mapped to **409 Conflict** on both doors with the generic body `Session has no associated workflow` — a state problem on the session, same refusal family as the concurrent-turn 409; the internal message (naming the session id) goes to the logger, never the response. Controllers never catch `\RuntimeException` wide (masks real 500s) nor echo `$e->getMessage()` — the launch controller's typed pattern, everywhere. **409 is the agreed number, cross-checked with the editor package's maintainers and confirmed indep… ### [The session-turn door checks its inputs exactly like the launch door (API-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592119) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: The session-turn door validates `inputs` identically to the launch door (unknown keys rejected, required enforced, schema-checked, strict resolve); the lenient `else` that `array_merge`d raw caller input into node-keyed `initialData` is **deleted**, not flagged strict — amends MAN-12/MAN-13. Both doors now share `WorkflowInputChecker`, so the same body earns the same verdict; the turn door raises `InvalidTurnInputException` → 400. - **Implementation:** shared `flowdrop_workflow/src/Utility/WorkflowInputChecker.php`; `WorkflowLauncher::validateInputs()`; `SessionTurnService::executeTurn()`; st… ### [Every JSON door decodes through the shared, bounded decoder (API-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592118) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **Nine controllers accept a JSON body and all nine decode via `ApiResponseTrait::decodeJsonRequest()`**: `WorkflowsController`, `WorkflowLaunchApiController`, `SessionTurnApiController`, `PlaygroundApiController`, `ChatApiController`, `SnapshotApiController`, `TriggerConfigApiController`, `PipelineSignalController`, `InterruptApiController`. The gate is 8 MiB measured by `strlen()`, depth 64 (so 63 levels is the deepest accepted document), non-array decode refused — each as `BadRequestHttpException` → 400. A bare `json_decode($request->getContent())` at an HTTP door is a defect, and there are … ### [One payload key per node-type concept (STORE-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592117) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **One name per concept for a node's type.** A node-type *config-entity ID* is `node_type_id` everywhere it appears in a payload — job metadata, node metadata, the serialised node execution result, the node-status broadcast payload, and persisted session-message metadata. A node's *visual* type is `visual_type` in the per-node snapshot payload (and `nodeType` as a config key, per SCH-20). The bare `node_type` key is **not written anywhere**: it used to mean the entity id in run/status/message payloads but the visual type in the snapshot payload, so a reader could not tell which without knowing … ### [A finished turn leaves the session completed, not idle (STORE-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592116) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A finished turn releases the session as **`completed`**, not `idle`; `idle` means created-but-never-executed. **LEGACY READ:** session rows written before 2.x carry `idle` meaning "turn finished", so `WorkflowExecutionService::getSessionStatus()` maps BOTH `idle` and `completed` to `Completed`, and the sub-workflow sync wait accepts both. That mapping stays until the old rows are migrated or age out — no data migration ships with the writer change. - **Implementation:** writers `SessionExecutionService.php:299,321,354`, `DeferredMessageProcessor.php:193`, `SessionInterruptResolvedSubscriber.p… ### [Entity statuses are backed enums whose value is what crosses a boundary (STORE-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592115) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: The four entity status vocabularies (`JobStatus`, `PipelineStatus`, `SessionStatus`, `MessageStatus`) are **backed enums**; the backing value is the persisted field value and the string every JSON/event payload carries, so `->value` is what crosses any boundary. The set helpers stay value lists: `PipelineStatus::terminalStatuses()`, `MessageStatus::terminalStatuses()`, `JobStatus::activeStatuses()`, `allowedValues()` (and `PausedReason::budgetReasons()`, still a constant bag) return the strings, so they drop straight into entity-query conditions and `allowed_values`. - **Implementation:** `fl… ### [WorkflowDTO::fromArray() normalizes for the read path only (STORE-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592114) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `WorkflowDTO::fromArray()` is a **read/execute-path-only** normalizer with exactly four production call sites (`WorkflowCompiler:100`, `SynchronousOrchestrator:219`, `JobGenerationService:118`, `StateGraphOrchestrator:1678`). It prunes any edge whose source or target does not resolve into `droppedEdges` (keyed by edge id); mints `uniqid('edge_', TRUE)` ids for id-less edges; fills node config as `array_merge($metadata['config'], $data['config'])`, so **the stored `data.config` value wins on collision and defaults only fill absent keys**; and re-keys nodes and edges by id, so on **duplicate ids… ### [Bundle import runs its gates in a fixed order and rolls back on refusal (STORE-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592113) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **Import gates, in this fixed order:** envelope `format` → signature trust → capability manifest → node-type generation → validation → flow-id shape → id collision. Every refusal after generation **rolls the generated node types back**. `BundleImporter::import()` returns a `BundleImportResult` status and never an HTTP code; `WorkflowsController::importResponse()` is the sole mapper: `UNSUPPORTED_FORMAT` → 422 `Unsupported bundle format`; `UNTRUSTED_BLOCKED` → 403 `Bundle publisher is not trusted` (+`signature`, `hint`) unless confirmed+permitted; `MISSING_CAPABILITY` → 422 `Required processors… ### [A workflow's schema version must be semver (STORE-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592112) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `schema_version` must be semver (`\d+.\d+.\d+`), enforced by a `Regex` constraint that only bites under config *validation* (plain schema conformance accepts any string). As with every Symfony `Regex`, the empty string is exempt — the entity's `'0.0.0'` property default is what keeps an unset version semver. - **Implementation:** `flowdrop_workflow.schema.yml:68-73` - **Guaranteed by:** `WorkflowStorageApiTest::testSchemaVersionMustBeSemver` Rule `STORE-8` of `GR-STORE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: STORE-8` token, and `scr… ### [The stored config schema is strict about node metadata (STORE-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592111) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Config schema is strict: `data.metadata` may contain **only** `node_type_id`; `data.config` is `type: ignore` (unconstrained at storage — only R6 constrains it). - **Implementation:** `config/schema/flowdrop_workflow.schema.yml:272-311` - **Guaranteed by:** `FlowDropWorkflowKernelTest::testAnnotatedSnapshotPassesConfigSchema`; `ConfigSchemaConformanceTest` Rule `STORE-7` of `GR-STORE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: STORE-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue:… ### [Saving slims transient canvas state out of the stored workflow (STORE-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592110) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `preSave` slims in **two independent passes**, and only when `!isSyncing()`. Pass 1 drops transient canvas state (`selected`/`dragging`/`deletable`, plus `nodeId` at both the node and `data` level) from **every** node. Pass 2 drops the node-level `type` and reduces `data.metadata` to `{node_type_id}` — but only for a node with a resolvable anchor (`data.metadata.node_type_id`, or a legacy `metadata.id` which is renamed to it); an **unanchored node keeps its metadata and its `type` verbatim**, since nothing could re-enrich them on read. `measured`, `position`, `data.config`, `data.label` and `d… ### [A validation failure at the REST boundary is a 422 and never reaches save (STORE-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592109) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Validation failure at the REST boundary → 422 with exactly `{success:false, error:'Workflow validation failed', details:[{code,message,locator}]}`, and `$workflow->save()` is never reached. **Errors only:** `validateStructure()` returns NULL the moment `ValidationResult::isValid()` holds, so a warning neither blocks the save nor appears anywhere in the response — only the `errors` list is mapped, never `warnings`. `locator` is a rename of the validator's own `parameter` key. The same helper guards create and update, so both paths refuse identically and a refused update leaves the stored row un… ### [Absent collections default to empty on create; a partial update preserves them (STORE-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592108) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Absent `nodes`/`edges`/`metadata` default to `[]` on create; on update only touched when present (partial PUT preserves). `name` is the exception — it is required on update too, so there is no name-omitted PUT. Note the response envelope is not the stored value for `metadata`: `getClientMetadata()` folds `format`/`schemaVersion` back in on read (preSave strips them). - **Implementation:** `WorkflowsController.php:161-163,269-277` - **Guaranteed by:** `WorkflowStorageApiTest::testAbsentCollectionsDefaultToEmptyArraysOnCreate`, `::testPartialUpdatePreservesUntouchedCollections` Rule `STORE-4` … ### [A client-supplied id that already exists is a conflict, never an overwrite (STORE-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592107) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Client-supplied `id` that already exists → 409, never overwrite. - **Implementation:** `WorkflowsController.php:148-154` - **Guaranteed by:** `WorkflowStorageApiTest::testDuplicateClientIdConflictsWithoutOverwriting` Rule `STORE-3` of `GR-STORE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: STORE-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592095 ### [A workflow name is required and capped at 255 bytes (STORE-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592106) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `name` required, ≤255 chars (create + update) → 400. Two edges worth knowing: the presence test is `empty()`, so the literal name `'0'` is refused as missing; and the cap is `strlen()`, i.e. **bytes**, so a 200-character multibyte name is over it. - **Implementation:** `flowdrop_workflow/…/WorkflowsController.php:140-146,253-259` - **Guaranteed by:** `WorkflowStorageApiTest::testNameIsRequiredOnCreate`, `::testNameLengthIsCappedOnCreate`, `::testNameRulesApplyToUpdate` Rule `STORE-2` of `GR-STORE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-regist… ### [Branch gateways and which edges activate (RT-BR)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592104) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-BR — 7 rules How a gateway names its active branch, how a branch port is told from a value port, and when a completed source is too stale to satisfy a gate. All 7 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592332 — **BR-1** When a branch edge is gated at all - [ ] #3592333 — **BR-2** The three cases where a branch edge activ… ### [Delivering values between nodes (RT-DATA)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592103) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-DATA — 12 rules Port-to-port delivery: how a value travels along an edge, what happens when several sources feed one port, and when a node is ready to run. All 10 testable rules in this section are covered by a test. The remaining 2 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592339 —… ### [Compiling a workflow into an execution plan (RT-CMP)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592102) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-CMP — 11 rules Preconditions, dependency graph construction, cycle detection, execution ordering, and tool wiring. All 11 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592291 — **CMP-1** What compiling a workflow produces - [ ] #3592292 — **CMP-2** Re-enrichment on the run path is conditional - [ ] #3592293 — **CMP-3** Compile … ### [The pipeline status the editor polls (RT-PIPE)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592101) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-PIPE — 4 rules The polling payload the editor reads to draw node badges. Note the payload is mixed-case by contract — some keys are snake_case and some camelCase — and must not be normalised. All 4 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592379 — **PIPE-1** The live run status is read from persisted entities - [ ] #359238… ### [Choosing and running an orchestrator (RT-ORC)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592100) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-ORC — 17 rules Which execution strategy a run gets and why, the contract they share, and how a run's final status is decided. All 16 testable rules in this section are covered by a test. The remaining 1 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592315 — **ORC-1** The four orchestrat… ### [The StateGraph runner (RT-SG)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592099) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-SG — 15 rules State injection, checkpointing, loop iteration accounting, and how a restore chooses between a snapshot and a checkpoint. All 15 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592364 — **SG-1** How each state field is reduced - [ ] #3592365 — **SG-2** What the runtime hands a node, and what the node must declare to… ### [Interrupts, pausing and resuming (RT-INT)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592098) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-INT — 13 rules Human-in-the-loop and budget pauses: what a paused run records, who is allowed to resume it, and how a snapshot is validated and restored. All 13 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592351 — **INT-1** An interrupted node pauses the pipeline and reports where it stopped - [ ] #3592352 — **INT-2** The int… ### [How a failing node is handled (RT-ERR)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592097) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-ERR — 13 rules The error channel: which exception types become a routable error output, which escape and fail the run, how retryability survives, and when a failed node satisfies a downstream edge. All 12 testable rules in this section are covered by a test. The remaining 1 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the … ### [The JSON API doors (GR-API)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592096) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-API — 4 rules Behaviour shared by every endpoint that accepts a JSON body: the single decoder all of them use, its size and nesting bounds, and how a refusal is reported. All 3 testable rules in this section are covered by a test. The remaining 1 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - … ### [Storing and serving a workflow definition (GR-STORE)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592095) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-STORE — 13 rules The workflow entity and its REST surface: request body bounds, required fields, what a partial update preserves, what is stripped on save, and bundle import. All 13 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592105 — **STORE-1** Refuse an empty, oversized, malformed or too-deeply-nested request body - [ ] #3… ### [Author-defined dynamic ports (GR-DYN)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592094) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-DYN — 7 rules Ports an author adds at configuration time rather than the plugin declaring them: how they are opted into, how names are validated, and what they resolve to when nothing is connected. All 7 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592236 — **DYN-1** A node type opts into dynamic ports by spreading their schem… ### [A workflow's declared inputs and outputs (GR-MAN)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592093) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-MAN — 19 rules The launch manifest: a declared list, never derived from the exposure cascade. Covers the stored schema snapshot, how malformed entries are dropped, and what is checked when a run is launched. All 18 testable rules in this section are covered by a test. The remaining 1 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fai… ### [Resolving a node's parameters (GR-CFG)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592092) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-CFG — 18 rules The resolution cascade for every parameter: wire value, then stored config, then schema default — with presence tested by key existence, so an explicit NULL at a higher priority wins. All 18 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592201 — **CFG-1 (D1)** Gate flags fail closed - [ ] #3592202 — **CFG-2 (D2)*… ### [Turning a plugin schema into ports and forms (GR-SCHEMA)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592091) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-SCHEMA — 30 rules How a node type plus its plugin schema become the ports, config form and defaults the editor shows — including the reserved trigger, tool and error ports, and the unified input/output ports. All 29 testable rules in this section are covered by a test. The remaining 1 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fa… ### [The four expression engines (GR-LANG)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592090) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-LANG — 29 rules Expression Language, Twig, property paths and JSONPath. They deliberately disagree about a missing key (throw / blank / NULL / logged default), so each engine's behaviour is stated separately rather than smoothed over. Also the node-level policy: a genuine expression *failure* fails the node. All 29 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the … ### [Port exposure (GR-EXPO)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592089) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-EXPO — 17 rules Exposure resolves from configuration only — instance ports, then the node type's default, then visible. A hidden port does not exist on the instance: it cannot be wired, and a hidden output's value is stripped where it is produced. All 17 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592219 — **EXPO-1** PortExpo… ### [How edges connect ports (GR-EDGE)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592088) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-EDGE — 9 rules The wire format between two nodes: handle encoding, which keys are structurally required, and how tool and error edges are recognised. All 9 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592162 — **EDGE-1** How a port handle encodes its node, direction and port name - [ ] #3592163 — **EDGE-2** No wire key is stru… ### [What the workflow validator refuses (GR-VAL)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592087) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-VAL — 40 rules Every rule the validator enforces when a workflow is saved: node and edge structure, config against the plugin schema, port exposure, and expression parsing. `R*` ids are the author-facing error codes. All 39 testable rules in this section are covered by a test. The remaining 1 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --c… ### [Return 400 for a malformed API request body](https://git.drupalcode.org/project/flowdrop/-/work_items/3592086) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::bug, code, priority::normal, spec-registry Description: ## Problem Three JSON API endpoints disagreed with the other six about what an invalid request body means. Creating a playground session decoded its optional body by hand and tolerated anything — malformed JSON, a scalar instead of an object, or a payload of any size all silently became "no options", so the session was created as though nothing had been sent. Sending a playground or chat message did use the shared decoder, but wrapped it in a catch-all handler. The decoder reports a bad body by throwing, so every malformed message came back as a 500 "failed to process" — a server error for … ### [Write down and test every runtime and workflow-language rule](https://git.drupalcode.org/project/flowdrop/-/work_items/3592085) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## Problem Most of FlowDrop's behaviour existed only in the code. That made two things hard: knowing whether a surprising result was a bug or the design, and changing anything with confidence that nothing downstream depended on the old behaviour. ## What changed `docs/development/specification-registry.md` now enumerates every rule of the workflow language (definition grammar, schema discovery, config resolution, port exposure, expressions) and of the runtime (compilation, parameter resolution, branching, error handling, interrupts, state, status reporting). Each rule has a stable id, cite… ### [Remove unused API and developer surfaces from 2.x](https://git.drupalcode.org/project/flowdrop/-/work_items/3592084) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: ## Problem 2.x carried a number of endpoints, methods and configuration keys that nothing called and nothing read. Some were half-built features, some were superseded, and a few actively misled: an endpoint reporting metrics that were always zero, because it collected them per-request with no persistent backing. Dead surface is not free — it looks like API, so it constrains refactoring and misleads anyone reading the code for guidance. ## What changed Removed, each verified to have no callers first: - the status-polling endpoints (including the health and metrics routes) and their tracker… ### [Report pipeline and job status consistently to the editor](https://git.drupalcode.org/project/flowdrop/-/work_items/3592083) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::bug, code, priority::normal, spec-registry Description: ## Problem The editor polls the pipeline API to draw node status badges, and the payload it received was not dependable: - The job status summary came back in three different shapes depending on which code path built it, and some shapes were missing status keys entirely. - Two controllers incremented status counters without checking the status was one they knew, which raised PHP warnings in production when an unrecognised value appeared. - It was undocumented which node a status entry belonged to when a node runs more than once, so a loop's badges could not be drawn reliably. ## What change… ### [Make error routing, cancellation and resume behave the same in every runner](https://git.drupalcode.org/project/flowdrop/-/work_items/3592082) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::bug, code, priority::major, spec-registry Description: ## Problem FlowDrop has more than one execution strategy, and they had drifted apart on the parts users notice most: - The direct synchronous runner ignored error outputs completely — a node's `error` edge did nothing there, so the same workflow routed failures under one runner and failed outright under another. - Cancelling a run was not announced like other terminal outcomes, so a cancelled sub-workflow could leave its parent waiting, and a session might never notice the run had stopped. - Cancellation was not recorded in the checkpoint, so a cancelled run could be resumed back to life. - … ### [Catch broken workflows when they are saved, not when they run](https://git.drupalcode.org/project/flowdrop/-/work_items/3592081) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::feature, code, priority::normal, spec-registry Description: ## Problem Several ways of breaking a workflow were accepted at save time and only surfaced later — as a confusing runtime error, or as a node that silently never ran. The editor would happily store a definition the engine could not honour. ## What changed The workflow validator now refuses these at save, each with a specific message pointing at the offending node or edge: - a node whose type does not exist - duplicate node ids, and duplicate or missing edge ids - an edge from a node to itself - two identical edges between the same pair of ports - an expression that its engine cannot parse… ### [Expression errors fail the node and route to its error edge](https://git.drupalcode.org/project/flowdrop/-/work_items/3592080) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::bug, code, priority::major, spec-registry Description: ## Problem The four nodes that evaluate author-written expressions each handled a broken expression differently: - **Data Mapper** aborted the node. - **Data Extractor** turned the failure into a normal-looking result, so a typo in a path looked like "no match found". - **Data Shaper** and **Prompt Template** let the raw engine exception escape, so it bypassed error routing entirely and failed the whole run. An author had no way to handle a broken expression, and no consistent signal that one had happened. ## What changed All four now agree: an expression the engine cannot evaluate fails … ### [[meta] Make the 2.x runtime and workflow-language contracts explicit and tested](https://git.drupalcode.org/project/flowdrop/-/work_items/3592079) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::plan, code, documentation, priority::normal Description: ## Problem FlowDrop's behaviour was largely undocumented, and where it *was* described the description and the code had drifted apart. Two nodes doing the same thing could fail differently, the same workflow could behave one way under one runner and another way under a second, and there was no way to tell "not implemented yet" from "implemented wrong". That mattered most in two places: what happens when something goes wrong at runtime, and what the workflow definition itself actually promises (schema discovery, config resolution, port exposure, expressions). ## Approach Write the rules dow… ### [Refuse an empty, oversized, malformed or too-deeply-nested request body (STORE-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592105) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Request body: empty → 400; >8 MiB → 400; invalid JSON → 400; nesting at or past 64 levels → 400 (the bound is json_decode's `$depth` argument, so 63 levels is the deepest accepted document); non-object/array (any JSON scalar, incl. `null`) → 400. Every case raises `BadRequestHttpException`, which Symfony renders as the 400. - **Implementation:** `src/Controller/Api/ApiResponseTrait.php:165-185` - **Guaranteed by:** `DecodeJsonRequestTest` (11 cases, incl. both size/depth boundaries) Rule `STORE-1` of `GR-STORE` in `docs/development/specification-registry.md`. Tests bind to it with a greppabl… ### [AI Assistant is broken from 1.5.0](https://git.drupalcode.org/project/flowdrop/-/work_items/3592073) State: closed | Updated: 2026-07-30 | Author: David Galeano (gxleano) | Assigned: Shibin Das (D34dMan) | Labels: category::bug, priority::critical, state::fixed Description: When you try to use the AI Assistant inside the FlowDrop workflow, after applied the changes it got stuck. ### [Add "Show Pipelines" to the operations per workflow](https://git.drupalcode.org/project/flowdrop/-/work_items/3589740) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: Shibin Das (D34dMan) | Labels: category::feature, code, priority::normal, state::fixed Description: >>> [!note] Migrated issue Reported by: [gxleano](https://www.drupal.org/user/3591999) >>> Add Show Pipelines to the operations to list pipelines per workflow (right now the only way to check the pipelines is going into the pipeline list and filter by workflow) ### [Remove "Pending" tag when the workflow is executing and the component has been skipped](https://git.drupalcode.org/project/flowdrop/-/work_items/3589739) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: Shibin Das (D34dMan) | Labels: category::feature, code, priority::normal, state::fixed Description: >>> [!note] Migrated issue Reported by: [gxleano](https://www.drupal.org/user/3591999) >>> Add Skipped tag instead of Pending when the node processors has been skipped of been executed --- MERGE REQUESTS (24h) --- (none) --- COMMITS (24h) --- (none) ======================================================================== ## [2] summariseModule:agui:developer ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: AG-UI (machine name: agui) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a technical developer audience. Focus on: what was merged or shipped, specific bugs fixed, APIs changed, and what is blocking progress. Be specific — mention function names, module names, and MR references where relevant. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Ahmad Khalil (ahmad-khalil-imagex) [1], Bryan Sharpe (b_sharpe) [3]". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
AG-UI
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a developer. Suggest 2-3 concrete technical actions a contributor could take right now. Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, check the data for each issue: - If an issue shows a Related MR with state 'opened', do NOT suggest creating a patch or MR — one already exists. Suggest reviewing it instead. - If all Related MRs for an issue are merged, do NOT suggest reviewing them — they are already done. - If an issue is unassigned with no Related MRs, it is a good candidate to pick up. - Only suggest actions that are genuinely still needed given the current state in the data above. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Add config for max characters](https://git.drupalcode.org/project/agui/-/work_items/3585465) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: Bryan Sharpe (b_sharpe) | Labels: category::feature, code, priority::normal, state::accepted Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !40 [Add validator and extractor services/methods and new setting.](https://git.drupalcode.org/project/agui/-/merge_requests/40) | State: merged 2026-07-30 | Author: Bryan Sharpe (b_sharpe), 585 diff lines Description: >>> [!note] Migrated issue Reported by: [b_sharpe](https://www.drupal.org/user/2512258) >>> Problem/Motivation Token exhaustion exploitation is becoming a problem and although this generally can be configured at the assistant level, it makes sense to just deny right away via chat if a character limit is exceeded. We should: Add a character limit config Report back a message to the user if limit is exceeded Deny the chat from going to the remote ### [Better Error Handling in chat](https://git.drupalcode.org/project/agui/-/work_items/3590046) State: closed | Updated: 2026-07-30 | Author: Bryan Sharpe (b_sharpe) | Assigned: Bryan Sharpe (b_sharpe) | Labels: Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !39 [Add error util and handler.](https://git.drupalcode.org/project/agui/-/merge_requests/39) | State: merged 2026-07-30 | Author: Bryan Sharpe (b_sharpe), 86 diff lines Description: **Problem:** When the AG-UI chat endpoint (/agui/api/chat) returns a non-2xx HTTP response — for example a 403 from the new anonymous JWT/flood access check, or any other error before/instead of a normal SSE stream — the raw response body is surfaced verbatim inside the chat UI as if it were assistant content, instead of a short, user-friendly error message. This happens in two places on the frontend (components/chat/src/js/), both with the same anti-pattern: on a non-ok response they read the entire response body and bake it directly into a thrown Error's message, with no truncation,… ### [Allow Token support on Assistant Controller](https://git.drupalcode.org/project/agui/-/work_items/3589993) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: Bryan Sharpe (b_sharpe) | Labels: category::feature, code, priority::normal, state::accepted Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !38 [Resolve "Allow Token support on Assistant Controller"](https://git.drupalcode.org/project/agui/-/merge_requests/38) | State: merged 2026-07-30 | Author: Bryan Sharpe (b_sharpe), 673 diff lines Description: >>> [!note] Migrated issue Reported by: [b_sharpe](https://www.drupal.org/user/2512258) >>> Problem/Motivation Allowing anonymous users to utilize agents is very common, but without some sort of auth it can allow bots/scripts to try rack up your tokens via posts requests. Using the token won't prevent bots collecting the token and using it, but at least mitigates direct post request. ### [Enable Drupal GitLab CI pipeline and add Unit/Kernel/Functional test coverage](https://git.drupalcode.org/project/agui/-/work_items/3590044) State: closed | Updated: 2026-07-30 | Author: Ahmad Khalil (ahmad-khalil-imagex) | Assigned: Bryan Sharpe (b_sharpe) | Labels: state::rtbc Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !34 [Resolve "Enable Drupal GitLab CI pipeline and add Unit/Kernel/Functional test coverage"](https://git.drupalcode.org/project/agui/-/merge_requests/34) | State: merged 2026-07-30 | Author: Ahmad Khalil (ahmad-khalil-imagex), 1643 diff lines Description: ### Problem/Motivation The agui repository currently has no `.gitlab-ci.yml`, so no pipeline runs on merge requests — no coding-standards checks, no static analysis, and no automated tests. It also has no PHPUnit tests at all, for either the main module or the `agui_mercure` sub-module. Recent MRs (e.g. !33) have had to rely entirely on manual and ad-hoc verification. ### Proposed resolution **1. Enable the standard Drupal GitLab CI pipeline** by adding the stock `.gitlab-ci.yml`: ```yaml include: - project: project/gitlab_templates ref: default-ref file: - '/includes/inclu… --- MERGE REQUESTS (24h) --- (none) --- COMMITS (24h) --- - [cfa2abb7](https://git.drupalcode.org/project/agui/-/commit/cfa2abb716b2c9c133ed4a911f464d8805fbbca0) Add validator and extractor services/methods and new setting. — Bryan Sharpe (2026-07-30T10:39:33.000-07:00) - [e705cb5b](https://git.drupalcode.org/project/agui/-/commit/e705cb5b742e978bf18d15faa0c705ffb2b9ca0d) Add error util and handler. — Bryan Sharpe (2026-07-30T10:13:02.000-07:00) - [66dc00a3](https://git.drupalcode.org/project/agui/-/commit/66dc00a3173ff0f44161f47dea0a1f48cb8d042a) Resolve "Allow Token support on Assistant Controller" — Bryan Sharpe (2026-07-30T16:25:00.000+00:00) - [41319ce8](https://git.drupalcode.org/project/agui/-/commit/41319ce8e4c870ae3e7a0e0aa39238c6eb489ec5) Resolve "Enable Drupal GitLab CI pipeline and add Unit/Kernel/Functional test coverage" — Ahmad Khalil (2026-07-30T15:01:15.000+00:00) ======================================================================== ## [3] generateTldr:developer ======================================================================== You are an editor distilling a Drupal AI project newsletter into its most important highlights. You are writing for a technical developer audience. Be specific — name modules, merged features, and critical bugs. Read all the module summaries below. Separate the highlights into two categories: - SHIPPED: things that were merged, fixed, released, or completed during this period. - ONGOING: things that are actively in progress, under review, or blocked. Be specific — name the module, what happened, and why it matters. Do not use emoticons or mdashes. Do not include any text outside the two sections. When you mention a specific issue or merge request, add an inline citation using [N] where N is the reference number from the list below. You may cite multiple references per item, e.g. [1][3]. Place citations immediately after the relevant phrase, before any punctuation. Format as two HTML sections. Use exactly this structure (all
elements must be inside the
, never outside it):
Shipped

Title here — One sentence explanation [1].

Another title — One sentence explanation.

Ongoing

Title here — One sentence explanation [2].

Up to 5 items per section. Do not output any text, tags, or characters outside these two sections. Output only the HTML fragment, no surrounding tags. --- REFERENCE LIST --- [1] MDXEditor fails to parse Drupal tokens in AI Agents prompts (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586613 [2] MDXEditor throws error when prompt includes a colon (:) character (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586619 [3] Decide permission system for new AI Platform and AI Inference Providers (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586628 [4] Support Automator Chain trigger with Field Widget Actions (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586602 [5] What providers for TextClassification? (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586629 [6] The Toolbar Chatbot runs the fold out animation on page reload (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3568246 [7] Support interactive/rich content (e.g. links) in the AI tooltip component (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586630 [8] Streaming chat forces plain-text hostname filtering, corrupting URLs inside HTML attributes (e.g., href="") (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586624 [9] Adopt symfony/ai component v0.8 as platform provider (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586427 [10] AI Automator Token Replacement with removing unresolved Tokens (Checkbox?) (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586535 [11] Add a ChatMemoryInterface for storing ChatBot chat history (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586539 [12] [1.x] Add a setup-automators agent skill to configure automators on fields (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586563 [13] Add a configure-ai-settings agent skill for general AI settings (default models, providers, timeout, trusted domains) (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586562 [14] Add a setup-guardrails agent skill to configure guardrails, guardrail sets, and global guardrails (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586561 [15] Streamed chatbot agent response (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3578168 [16] Assistants backed by an agent never stream (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586627 [17] Refactor CommonMark instance creation (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586608 [18] Issue #3586602: Add a field widget action base class and text plugin to run... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1887 [19] Issue #3586602: Add a field widget action base class and text plugin to run... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1888 [20] Issue #3586602: Add a field widget action base class and text plugin to run... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1886 [21] Issue #3586602: Add a field widget action base class and text plugin to run... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1828 [22] feat: #3586585 Add YAML support to the MDX editor code blocks (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1823 [23] #3568246: fix late chatbot opening on page load (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1428 [24] feat: #3586427 Adopt symfony/ai v0.8's Platform concept (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1619 [25] Add CommonMarkConverterFactory service. (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1881 [26] Issue #3586535: AI Automators strip unresolved tokens from prompts (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1884 [27] Issue #3586589: Add ChatMemory plugin type (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1885 [28] fix: #3586589 Do not assume action definitions have a type when deriving action plugin functions (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1835 [29] bug: #3586624 Streaming chat forces plain-text hostname filtering, corrupting... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1883 [30] Resolve #3586627: Assistants backed by an agent never stream (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1882 [31] "1.x backport" (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1321 [32] Issue #3586620 Merge 1.3.x guardrails (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1880 [33] Create a skill for manual before/after testing of any issue, with optional glab upload (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586629 [34] Onboard Silver AI partner: Specbee (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586639 [35] Add Silver AI partner to d.o pages: Specbee (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586638 [36] Run AI partner audit report: Specbee (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586637 [37] Onboard Gold/Silver AI partner: TEMPLATE (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3579583 [38] Add Gold/Silver AI partner to d.o pages: TEMPLATE (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3579591 [39] Run AI partner audit report: TEMPLATE (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3579584 [40] Update AI partner badges to use Partner instead of Sponsor (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586636 [41] Add Gold AI partner to d.o pages: Pantheon+Omedia (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586631 [42] Onboard Gold AI partner: Pantheon+Omedia (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586630 [43] Partner contributor audit and cleanup August 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586634 [44] Update AI partner logo wall with latest logos July 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586635 [45] Update AI partner logo wall with latest logos March 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3580150 [46] Partner and contributor offboarding for July 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586633 [47] Partner and contributor offboarding for June 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586553 [48] Migrate the ECA agent to the Tools + ReAct architecture (create-only) (ai_integration_eca, Issue) — https://git.drupalcode.org/project/ai_integration_eca/-/work_items/3585017 [49] Resolve "Migrate the ECA agent to the Tools + ReAct architecture (create-only)" (ai_integration_eca, MR) — https://git.drupalcode.org/project/ai_integration_eca/-/merge_requests/14 [50] add support for batch embeddings (ai_provider_openai, MR) — https://git.drupalcode.org/project/ai_provider_openai/-/merge_requests/59 [51] Resolve #3612042 "Rate limits" (ai_provider_openai, MR) — https://git.drupalcode.org/project/ai_provider_openai/-/merge_requests/80 [52] Resolve #3613982 "Bug with gpt" (ai_provider_openai, MR) — https://git.drupalcode.org/project/ai_provider_openai/-/merge_requests/81 [53] Data loss: Deleting or clearing items in a Search API index deletes data from other indexes sharing the same Vector DB collection (ai_provider_amazeeio, Issue) — https://git.drupalcode.org/project/ai_provider_amazeeio/-/work_items/3586238 [54] feat: send X-Amazee-Client request tracking header (ai_provider_amazeeio, MR) — https://git.drupalcode.org/project/ai_provider_amazeeio/-/merge_requests/81 [55] [#3552969] feat: Refactor AzureProvider to use OpenAiBasedProviderClientBase (ai_provider_azure, MR) — https://git.drupalcode.org/project/ai_provider_azure/-/merge_requests/22 [56] Issue #3586862 by ignacio.perez.puertas: Re-apply Attributes columns after clear+reindex cycle (ai_vdb_provider_postgres, MR) — https://git.drupalcode.org/project/ai_vdb_provider_postgres/-/merge_requests/24 [57] Token Auth is not working (mcp, Issue) — https://git.drupalcode.org/project/mcp/-/work_items/3584901 [58] Resolve "Token Auth is not working" (mcp, MR) — https://git.drupalcode.org/project/mcp/-/merge_requests/52 [59] Add a way to set provider tags in the runner (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3557418 [60] Let an agent use a role when running a tool (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3518167 [61] Add limits on how often a tool can run (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3547995 [62] Give a parent agent possibility to forward request as is (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3550098 [63] Make it possible to pick providers per agent (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3535760 [64] Chatbot truncates 'search_string' context value while tool explorer does not (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3547304 [65] Chatbot repeats itself even after 'clear history' if 'return direct' (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3547225 [66] Create implementation of ShortTermMemory (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3546411 [67] Draft: Resolve "Give a parent agent possibility to forward request as is" (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/326 [68] Issue#3547304:chatbot-truncates-search-string-context-value-while-tool-explorer-does-not fixes (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/327 [69] Issue #3535760: Provider picker (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/315 [70] Issue#3547225-chatbot-repeats-itself-even-after-clear-history-if-return-direct fixes (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/325 [71] Issue#3541337-module-agent-fails fixes. (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/324 [72] Issue#3539557:error-message-when-using-the-ai-assistant-to-add-a-content-type fixes (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/323 [73] Configuration-sourced input values fatal: getConfigurationValue() semantics are inverted (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582959 [74] validateInputValue() only validates the first item of a multiple input (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582960 [75] ToolBase::access() throws on invalid/missing input instead of returning forbidden (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582961 [76] Correct API signatures before the RC1 freeze (batch) (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582962 [77] Prefix module-owned identifiers: alter hook, cache key, and 'text' data type ID (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582963 [78] Rework the tool execution contract: result naming, concrete typing, and decoupling from core ExecutableInterface (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582964 [79] Implement getCacheContexts() or drop CacheableDependencyInterface from ToolInterface (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582965 [80] Annotate the API surface (@api/@internal) and add tool.api.php (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582966 [81] Harden the 'administer tool' permission (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582967 [82] Tool Explorer execute form: masked exception on access denial, duplicate messages, no validation pass (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582968 [83] Tool Explorer RC cleanup: render arrays, dead cache tag, menu placement, first tests (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582969 [84] Drush hardening: --uid default, silently dropped inputs, exit codes (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582970 [85] Make violation messages translatable and stop surfacing raw exception text (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582971 [86] Emit richer JSON Schema: map remaining constraints and type formats (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582972 [87] Extend input coercion for unambiguous LLM value shapes (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582973 [88] Complete kernel coverage of the typed input/output traits and definition pipeline (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582974 [89] checkRequirements() is declared on the frozen interface but never called anywhere (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582975 [90] Filter workflow-only tools from one-shot CLI invokers (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582977 [91] Track Drupal core CLI alignment: metadata mapping, typed-outputs advocacy, future CLI invoker (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582976 [92] [META] Path to 1.0.0-rc1 (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582978 [93] Entity handle descriptions are HTML-escaped in LLM-facing schemas (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582958 [94] A tool whose input stage fails never executes, and external getResult() calls then throw BadMethodCallException, masking the error feedback (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582957 [95] Anthropic rejects tool schemas: nullable optional inputs render an object under "type" (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582956 [96] tool_ai_connector throws `BadMethodCallException` when the tool has not executed (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582948 [97] [AI Connector] - Context Data missing after execute (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3576586 [98] MapDefinitionNormalizer and ContextDefinitionNormalizer break REST serialization (same as #3568588) (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582939 [99] Issue #3582959 by michaellander: Configuration-sourced input values fatal:... (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/111 [100] Resolve "Entity handle descriptions are HTML-escaped in LLM-facing schemas" (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/110 [101] Resolve "A tool whose input stage fails never executes, and external getResult() calls then throw BadMethodCallException, masking the error feedback" (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/109 [102] Resolve "Anthropic rejects tool schemas: nullable optional inputs render an object under "type"" (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/108 [103] Resolve "tool_ai_connector throws `BadMethodCallException` when the tool has not executed" (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/107 [104] Issue #3576586 by b_sharpe: Set parent context data as well as input. (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/76 [105] Issue #3582939: Fix getSupportedTypes() in MapDefinitionNormalizer and... (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/95 [106] RTL support for Canvas visual editor (logical CSS properties, Radix DirectionProvider, autocomplete magnifier, and Undo/Redo timelines) (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591840 [107] Translatable props missing from TMGMT form when component instances cannot be auto-updated to active version (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591875 [108] Strengthen AutoSaveManager to generate stable hashes (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591785 [109] Dependency Dashboard (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591657 [110] CLI push includes unsupported label property for content templates (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591899 [111] Automatically create components when themes are installed (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591898 [112] Canvas CLI sync fails for media and link props in global regions (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591897 [113] Error message for empty value is displayed for select props even when they're not required (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591894 [114] Canvas AI: Add Tools dropdown to chat UI (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591856 [115] Automate MR review using PHPCS: disallow `\Drupal::service('something')`, require `\Drupal::service(Something::class)` whenever possible, with automatic fixing (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3581133 [116] Canvas AI: Improve the schema of the place_components tool (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591881 [117] Canvas AI: Add an Agents & Tools settings form to select the main agent and chat Tools (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591882 [118] Draft: fix: #3591840 RTL support for Canvas visual editor (logical CSS properties, Radix DirectionProvider, autocomplete magnifier, and Undo/Redo timelines) (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1453 [119] #3591875: "Translatable props missing from TMGMT form when component instances cannot be auto-updated to active version" (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1418 [120] chore(deps): update dependency cspell to v10 (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1273 [121] chore(deps): update dependency @eslint/compat to v2 (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1306 [122] chore(deps): update dependency @chromatic-com/storybook to v5 (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1305 [123] fix(deps): update npm minor and patch (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1238 [124] chore(deps): update mysql docker tag to v8.3 (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1272 [125] chore: version packages (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1452 [126] fix(CLI Tool): #3591899 CLI push includes unsupported label property for content templates (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1451 [127] feat: #3518272 support all entity types with configurable displays for content templates (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/791 [128] Generate components when extensions are installed, even if syncing config (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1450 [129] feat(CLI Tool): Return flexible codebase files to local environment on canvas pull (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1443 [130] Draft: #3591838 [PHASE 2] introduce color props (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1432 [131] feat(Headless): #3591861 Add a Canvas-owned routed content endpoint for headless apps (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1436 [132] #3591838 brand kit color implementation (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1385 [133] chore: version packages (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1449 [134] fix(CLI Tool): #3591897 Canvas CLI sync fails for media and link props in global regions (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1446 [135] fix(UI): #3591894 Error message for empty value is displayed for select props... (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1440 [136] Draft: #3591810 Add AiWizardDev, a dev chat wizard that posts to... (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1448 [137] Draft: Resolve "Canvas AI: Add Tools dropdown to chat UI" (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1447 [138] #3581133: Automate MR review using PHPCS: disallow `\Drupal::service('something')`, require `\Drupal::service(Something::class)` whenever possible, with automatic fixing (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1297 [139] Issue #3591882: Add an Agents & Tools settings form. (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1445 [140] Issue #3577155: Add support for file fields using custom stream wrappers (currently only `public` is supported) (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1204 [141] #3591881 Canvas AI: Improve the schema of the place_components tool (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1439 [142] feat: #3567225 Allow per-node override of Content Template via checkbox in node selector (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/948 [143] Avoid loading the full published catalog on the CCC overview page (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586355 [144] Avoid functional-test dual-container traps (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586325 [145] Rename entity bundle and target entity scope plugins for better DX (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586276 [146] Improve conditional subcontext disabled-state behavior and admin UX (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586292 [147] Allow scope plugins to declare an optional icon for UI display (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586262 [148] Complete scope plugin persistence API: manager orchestration, target entity encapsulation, and plugin-driven admin/selection (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586243 [149] Create Mad Libs style template for the CCC (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586340 [150] [Discuss] Adding priority to context item to affect ranking (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586364 [151] [Discuss] Review context selection ranking factors before 1.0 (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586365 [152] CCC beta3 blog post (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586332 [153] beta2 upgrade fails at updates 10006 and 10011 after bundleless entity conversion (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586343 [154] Update relevant CCC skipped tests (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586263 [155] QA team start testing CCC to get familiar with functionality and create QA plan (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586342 [156] Restore Drupal 10 compatibility and repair incomplete beta3 upgrades (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586338 [157] Clean up CCC inconsistencies and DX issues before rc1 (part 3) (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586271 [158] Add a dedicated editorial workflow for AI Context Items (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586345 [159] Issue #3586355: Avoid loading the full published catalog on the CCC overview page. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/232 [160] Issue #3586325: Fix functional-test dual-container traps in AiContextAdminSettingsTest. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/225 [161] Issue #3586276: Rename entity bundle and target entity scope plugins for better DX (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/195 [162] Issue #3586292: Exclude conditional subcontext items when AI decisions are disabled. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/226 [163] Issue #3586343: Fix beta2 upgrade failures in updates 10006, 10008, and 10011. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/229 [164] Issue #3586338: Restore Drupal 10 compatibility and repair beta3 upgrades. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/223 [165] Issue #3586345: Add a dedicated editorial workflow for AI Context Items (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/236 [166] Show AI status indicator next to the Generate button (ai_ckeditor, MR) — https://git.drupalcode.org/project/ai_ckeditor/-/merge_requests/6 [167] RagTool::execute() should expose structured per-result data and check entity access (ai_search, Issue) — https://git.drupalcode.org/project/ai_search/-/work_items/3584031 [168] Defer default search item access checking to the Search API datasource plugin (ai_search, Issue) — https://git.drupalcode.org/project/ai_search/-/work_items/3584042 [169] [PP-1] Provide an API for performing access check on non-content entities (ai_search, Issue) — https://git.drupalcode.org/project/ai_search/-/work_items/3579758 [170] Introduce a dedicated runtime access-checking API for AI Search / RAG filtering (ai_search, Issue) — https://git.drupalcode.org/project/ai_search/-/work_items/3584043 [171] bug: #3584035 Reset chunk-slicing progress when index is cleared or reset-tracker is run (ai_search, MR) — https://git.drupalcode.org/project/ai_search/-/merge_requests/71 [172] Support non content entity datasources (ai_search, MR) — https://git.drupalcode.org/project/ai_search/-/merge_requests/25 [173] Issue #3579758: Provide API for access checks on non-content entities (ai_search, MR) — https://git.drupalcode.org/project/ai_search/-/merge_requests/49 [174] [PP-1] Introduce a dedicated runtime access-checking API for AI Search / RAG filtering (ai_search, MR) — https://git.drupalcode.org/project/ai_search/-/merge_requests/75 [175] Add documentation (ai_translate, Issue) — https://git.drupalcode.org/project/ai_translate/-/work_items/3585534 [176] Fix Pipeline (ai_translate, Issue) — https://git.drupalcode.org/project/ai_translate/-/work_items/3585537 [177] Issue #3585537: Fix the Pipelines by adding composer.json (ai_translate, MR) — https://git.drupalcode.org/project/ai_translate/-/merge_requests/34 [178] Draft: Resolve "Add documentation" (ai_translate, MR) — https://git.drupalcode.org/project/ai_translate/-/merge_requests/32 [179] Add detail logic to the playground pipelines and add the ability to show the debug data by clicking on the executed pipeline item (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3589741 [180] A state update is applied through the reducers after the node completes (SG-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592366 [181] What the runtime hands a node, and what the node must declare to see it (SG-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592365 [182] How each state field is reduced (SG-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592364 [183] An engine that cannot consume a snapshot must throw (INT-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592363 [184] A terminal snapshot is not resumable (INT-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592362 [185] A checkpoint round-trip preserves which terminal status it was (INT-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592361 [186] An async handover seeds the queued run from the snapshot (INT-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592360 [187] Saving a snapshot is an upsert keyed by execution id (INT-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592359 [188] Snapshot validation returns a fixed set of codes (INT-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592358 [189] The workflow version hashes structural data only (INT-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592357 [190] What a snapshot carries (INT-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592356 [191] A pipeline signal is polled between jobs, never mid-job (INT-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592355 [192] The four conditions for a node to own a resume (INT-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592354 [193] Resolving an interrupt resets the job and resumes the pipeline (INT-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592353 [194] The interrupt entity is persisted by a subscriber (INT-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592352 [195] An interrupted node pauses the pipeline and reports where it stopped (INT-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592351 [196] Tools are handed to a processor only when there are some (DATA-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592350 [197] The model-facing tool schema omits parameters already filled (DATA-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592349 [198] Tool availability projects into tool bindings, not into data (DATA-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592348 [199] The unified output port composes exposed outputs only (DATA-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592347 [200] The effective execution config is stamped on the pipeline (SG-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592376 [201] Which stored state a resume restores, in order (SG-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592375 [202] A checkpoint per node, chained, plus one at the end (SG-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592374 [203] The reserved trigger port means no branch for loopback naming (SG-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592373 [204] An edge condition never routes (SG-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592372 [205] How a repeated node's result is keyed (SG-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592371 [206] Loopback re-entry needs an active branch and remaining work (SG-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592370 [207] Routing decides per edge and dispatches per target (SG-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592369 [208] The loopback input doubles as the item result (SG-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592368 [209] How a ForEach loop initialises and finishes (SG-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592367 [210] Which payloads the status vocabulary guards (PIPE-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592381 [211] The job status summary has one shape, derived from the enum (PIPE-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592380 [212] The live run status is read from persisted entities (PIPE-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592379 [213] The execution id the editor polls is the pipeline id (SG-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592378 [214] Exceeding the iteration budget throws (SG-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592377 [215] node_statuses is keyed by the workflow node id (PIPE-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592382 [216] A hidden output is stripped where it is produced (DATA-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592346 [217] Inside a node, the parameter-resolution cascade decides (DATA-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592345 [218] Launch data fills in under edge-delivered inputs (DATA-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592344 [219] Loopback and tool edges are dropped from data delivery (DATA-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592343 [220] Readiness promotes a job whose dependencies are met (DATA-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592342 [221] A trigger edge carries no data (DATA-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592341 [222] One value per port, last executor wins (DATA-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592340 [223] Delivery is port to port, both names read from the handle (DATA-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592339 [224] Direct sync skips a node whose trigger was never satisfied (BR-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592338 [225] Staleness gates a branch decision, not delivery (BR-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592337 [226] Branch gating applies to trigger and data ports alike (BR-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592336 [227] A node's configured branches are the authority on branch ports (BR-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592335 [228] How active_branches is normalized (BR-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592334 [229] The three cases where a branch edge activates (BR-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592333 [230] When a branch edge is gated at all (BR-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592332 [231] A cancelled run is announced like any other terminal outcome (ORC-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592331 [232] Claiming a job is atomic under concurrent workers (ORC-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592330 [233] Auto-resume is gated, not unconditional (INT-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592329 [234] A terminal pipeline cannot be paused or resumed (INT-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592328 [235] A resume re-enters through the pipeline's declared orchestrator (ORC-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592327 [236] An async launch returns queued immediately (ORC-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592326 [237] How a run's terminal status is decided (ORC-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592325 [238] An iteration and time budget breaks the loop (ORC-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592324 [239] A pipeline engine is a ready-job loop (ORC-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592323 [240] Direct sync filters which trigger node starts the run (ORC-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592322 [241] Direct sync walks the execution order once (ORC-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592321 [242] Every strategy shares one contract and one hierarchy (ORC-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592320 [243] Capability queries are answered from the plugin definition only (ORC-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592319 [244] StateGraph is the session default, not the global one (ORC-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592318 [245] An unknown orchestrator type falls back with a warning (ORC-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592317 [246] How the default orchestrator is resolved (ORC-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592316 [247] The four orchestrator strategies and their ids (ORC-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592315 [248] Every orchestrator routes an error result identically (DECIDED) (ERR-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592314 [249] Remove the direct-sync record-and-continue divergence (ERR-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592313 [250] Retry is in-place, immediate and opt-in (ERR-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592312 [251] A routed-failed node satisfies only its error edges (ERR-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592311 [252] A pipeline whose only failures were routed still completes (ERR-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592310 [253] An error result with no error edge fails the run (ERR-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592309 [254] An error result with an error edge routes instead of failing the run (ERR-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592308 [255] An unserializable output fails the node (ERR-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592307 [256] A stop request bypasses the error catch and stops the run cleanly (ERR-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592306 [257] An interrupt is re-thrown unchanged (ERR-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592305 [258] Any other exception fails the node and is re-thrown wrapped (ERR-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592304 [259] A retryable exception stays recognisable after it is caught (ERR-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592303 [260] A RuntimeException from a processor becomes an error result (ERR-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592302 [261] A node mapping carries both the processor and the node-type id (CMP-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592301 [262] A tool consumer must declare that it accepts tools (CMP-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592300 [263] Tool names must be unique per consumer at compile time (CMP-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592299 [264] Execution order is a topological sort (CMP-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592298 [265] A trigger dependency outranks a data dependency for ordering (CMP-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592297 [266] Which nodes are excluded from the execution graph (CMP-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592296 [267] Cycle detection ignores the edges that are meant to loop (CMP-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592295 [268] Edge type is derived from handles, never declared (CMP-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592294 [269] Compile preconditions run first, in a fixed order (CMP-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592293 [270] Re-enrichment on the run path is conditional (CMP-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592292 [271] What compiling a workflow produces (CMP-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592291 [272] One expression-error policy across every engine (DECIDED) (LANG-29) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592290 [273] The six operators the if/else gateway declares (LANG-28) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592289 [274] The switch gateway matches a branch value instead of evaluating it (LANG-27) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592288 [275] A prompt template turns a Twig error into a node failure (LANG-26) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592287 [276] DataShaper resolves its five sentinels before consulting an engine (LANG-25) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592286 [277] A NULL extraction is a soft miss, never an error (LANG-24) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592285 [278] DataExtractor unwraps a first match only for JSONPath (LANG-23) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592284 [279] DataExtractor re-wraps any evaluator throwable as a RuntimeException (LANG-22) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592283 [280] DataMapper re-wraps only a RuntimeException from an evaluator (LANG-21) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592282 [281] What exists() answers for an empty path and for a scalar (LANG-20) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592281 [282] Extracting all matches on a property path wraps the single result (LANG-19) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592280 [283] How a mapping value is marked as a literal instead of an expression (LANG-18) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592279 [284] Dot-to-bracket normalization is duplicated in three classes (LANG-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592278 [285] A string context is decoded as JSON when it is JSON (LANG-16) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592277 [286] A single JSONPath match is unwrapped unless the path is multi-value (LANG-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592276 [287] A path is JSONPath when it starts with $ (LANG-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592275 [288] Twig validation is compile-only (LANG-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592274 [289] JSONPath validation accepts anything that is not a $ path (LANG-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592273 [290] Property-path validation delegates to the same parser (LANG-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592272 [291] Expression Language validation accepts unknown variable names (LANG-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592271 [292] JSONPath never throws, and has three distinct outcomes (LANG-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592270 [293] A property path never throws; an unreadable path is NULL (LANG-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592269 [294] Twig renders a missing variable as an empty string (LANG-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592268 [295] Expression Language reports a syntax error, and a missing variable is one (LANG-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592267 [296] Expression validation has exactly one production call site (LANG-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592266 [297] A non-array context is wrapped for the template engines (LANG-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592265 [298] What an empty expression evaluates to, per engine (LANG-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592264 [299] Getting an evaluator never lets a plugin-manager failure escape (LANG-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592263 [300] Extraction engines query context; transformation engines see a variable map (LANG-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592262 [301] Refuse a synchronous launch of an async-declared workflow (MAN-19) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592261 [302] The manifest is rebuilt only when the declared ports change (MAN-18) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592260 [303] A declared output reads from its node's result (MAN-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592259 [304] Launch inputs are checked against the manifest snapshot (MAN-16 (G4)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592258 [305] Input checking short-circuits at the first failing stage (MAN-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592257 [306] A malformed manifest entry is dropped with a warning, even in strict mode (MAN-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592256 [307] Strict mode refuses an undeclared input by name (MAN-13 (G3)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592255 [308] Node-keyed pass-through is an internal contract (MAN-12 (G2)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592254 [309] A named input resolves to its node and port (MAN-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592253 [310] A declared manifest name wins over the node-keyed pass-through (MAN-10 (G1)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592252 [311] A workflow used as a node exposes its manifest, with a cycle guard (MAN-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592251 [312] An unresolvable manifest entry is dropped from the snapshot (MAN-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592250 [313] Which default values survive into the manifest snapshot (MAN-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592249 [314] Author metadata overlays the plugin annotations and wins (MAN-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592248 [315] A manifest snapshot is built from the plugin fragment and stripped (MAN-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592247 [316] The validator guards manifest integrity (MAN-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592246 [317] The authoring picker offers only ports that exist (MAN-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592245 [318] The shape of a manifest entry (MAN-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592244 [319] A workflow's input ports are a declared manifest, never derived (MAN-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592243 [320] The dynamic-port form appears only when the node type opts in (DYN-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592242 [321] Dynamic ports have no exposure semantics (DYN-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592241 [322] A static parameter name beats a dynamic one (DYN-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592240 [323] An unconnected dynamic port resolves to NULL, with its key present (DYN-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592239 [324] Reject an invalid or duplicate dynamic port name (DYN-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592238 [325] A dynamic port item needs a name, label and dataType (DYN-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592237 [326] A node type opts into dynamic ports by spreading their schema in (DYN-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592236 [327] Port order is cosmetic and the engine never reads it (EXPO-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592235 [328] The exposure checkbox seeds from the saved value (EXPO-16) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592234 [329] Which parameters a model may fill on a tool call (EXPO-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592233 [330] Stripping runs before the unified output port is composed (EXPO-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592232 [331] An output the node type hides is stripped unconditionally (EXPO-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592231 [332] Control outputs are never stripped (EXPO-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592230 [333] A hidden output's value is stripped where it is produced (EXPO-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592229 [334] A hidden input port receives no runtime value (EXPO-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592228 [335] The one-time exposure freeze writes only the hidden entries (EXPO-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592227 [336] A parameter added after install has no stored exposure until a re-save (EXPO-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592226 [337] Materialize an exposure entry only when it diverges from the default (EXPO-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592225 [338] The plugin's exposure hint is read at authoring time only (EXPO-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592224 [339] A schema hides a port by default only when it says so exactly (EXPO-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592223 [340] An untouched node stores no ports key, so the default always applies (EXPO-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592222 [341] How a port direction maps to its config key (EXPO-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592221 [342] An instance override decides exposure before any default does (EXPO-2 (D3)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592220 [343] PortExposure is the only PHP accessor for effective exposure (EXPO-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592219 [344] A config default is written only for a configurable parameter (CFG-18) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592218 [345] The unified input merge only fills connectable parameters (CFG-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592217 [346] The reserved input port is decomposed before the schema loop (CFG-16) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592216 [347] Every dynamic input is present in the resolved bag (CFG-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592215 [348] Every schema property is present in the bag, NULL when unresolved (CFG-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592214 [349] The resolved bag holds exactly the schema's keys plus dynamic ports (CFG-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592213 [350] Format validation covers nine formats and ignores the rest (CFG-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592212 [351] The type check is a closed match with no coercion (CFG-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592211 [352] A resolved value is validated against the plugin schema (CFG-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592210 [353] A required parameter that resolves to NULL fails the node (CFG-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592209 [354] Internal parameters accept a runtime value but never config (CFG-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592208 [355] Presence is key existence, so an explicit NULL wins over a lower priority (CFG-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592207 [356] Priority 3: fall back to the effective default (CFG-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592206 [357] Priority 2: take a config value when the parameter is configurable (CFG-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592205 [358] Priority 1: take a runtime value when the port can receive one (CFG-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592204 [359] An effective default is the entity's, then the plugin's, then NULL (CFG-3 (D4)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592203 [360] The exposure default fails open (CFG-2 (D2)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592202 [361] Gate flags fail closed (CFG-1 (D1)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592201 [362] Config fields are ordered by their declared order (SCH-31) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592200 [363] The run path re-enriches from the live node type (SCH-29) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592199 [364] The executor plugin id comes from the node type, never from the payload (SCH-28) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592198 [365] The wire shape is lean: emit a key only when it diverges from the default (SCH-27) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592197 [366] The editor catalog serves enabled node types, sorted (SCH-26) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592196 [367] Enrichment anchors on the node-type id alone (SCH-25) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592195 [368] Building node data logs and degrades instead of failing the editor (SCH-24) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592194 [369] The UI schema is generated from the final config schema (SCH-23) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592193 [370] Only a config-edit provider gets a configEdit block (SCH-22) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592192 [371] Every node gets a reserved instance title and description (SCH-21) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592191 [372] A node's visual type comes from the config entity only (SCH-20) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592190 [373] Both key enumerations skip trigger and hidden parameters (SCH-19) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592189 [374] Prepend the unified output port when the node exposes one (SCH-18) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592188 [375] Prepend the unified input port when the node exposes one (SCH-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592187 [376] The exposure defaults of the reserved ports (SCH-16) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592186 [377] An injected port declares its exposure default only when it diverges (SCH-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592185 [378] Inject the reserved error output on every executable node (SCH-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592184 [379] Inject the reserved tool output only on a tool-exposed node (SCH-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592183 [380] Inject the reserved trigger output on every node but a terminal node (SCH-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592182 [381] Inject the reserved trigger input on every node but a start node (SCH-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592181 [382] The schema-to-dataType map is closed (SCH-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592180 [383] A union type normalizes to its first non-null member (SCH-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592179 [384] One mapping turns a schema into ports (SCH-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592178 [385] An output reaches the editor only when the node type exposes it (SCH-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592177 [386] A parameter is required on the input side only when it is not configurable (SCH-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592176 [387] Reserved config-only parameters never become ports (SCH-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592175 [388] Hidden parameters are dropped from both derived schemas (SCH-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592174 [389] Deriving splits one parameter schema into an input schema and a config schema (SCH-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592173 [390] Schema derivation reads its gate flags from the plugin schema (SCH-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592172 [391] A node's input and output surface comes only from its two schema methods (SCH-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592171 [392] Transport edges and job-metadata edges each own their own key names (EDGE-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592170 [393] Edge conditions are a removed feature that is tolerated but never read (EDGE-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592169 [394] What makes a node tool-only (EDGE-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592168 [395] An edge is an error edge by its source handle (EDGE-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592167 [396] An edge is a tool edge by declared type, else by its target handle (EDGE-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592166 [397] An edge is a loopback edge when its target handle says so (EDGE-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592165 [398] An edge is a trigger edge when its target handle says so (EDGE-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592164 [399] No wire key is structurally required; an absent one becomes a missing endpoint (EDGE-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592163 [400] How a port handle encodes its node, direction and port name (EDGE-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592162 [401] Refuse a duplicate edge between the same two ports (R13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592161 [402] Refuse an edge from a node to itself (R12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592160 [403] Every configured expression must pass its engine's check at save (R11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592159 [404] A workflow exposure must target a port exposed on the node instance (R10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592158 [405] A node's node-type anchor must resolve to a node type that exists (R9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592157 [406] Edge ids must be present and unique at save (DECIDED) (R3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592156 [407] Node ids must be unique (DECIDED) (R2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592155 [408] The whole validator runs again at launch (VAL-LAUNCH) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592154 [409] The validator instantiates plugins only for the exposure checks (VAL-PERF) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592153 [410] Warn about an edge leaving a terminal node (W-T) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592152 [411] An exposure must name a port the plugin declares (R4.d) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592151 [412] An exposure must name a node that exists (R4.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592150 [413] Exposure names must be unique per side (R4.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592149 [414] An exposure name must match the allowed format (R4.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592148 [415] Skip the edge-exposure check where another rule already owns the problem (R7.e/f) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592147 [416] A port the node type never declared is out of the edge-exposure check (R7.d) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592146 [417] Effective exposure comes from the instance config, then the node-type default (R7.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592145 [418] Refuse an edge out of a hidden output port (R7.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592144 [419] Refuse an edge into a hidden input port (R7.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592143 [420] An edge missing both endpoints reports both errors (R8.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592142 [421] Refuse an edge whose target node does not exist (R8.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592141 [422] Refuse an edge whose source node does not exist (R8.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592140 [423] Retire validateParams() from the processor contract (R6.k) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592139 [424] Warn when a secret reference is written without its leading $ (R6.l) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592138 [425] An unresolvable node type skips only the schema-driven config checks (R6.j) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592137 [426] A NULL config value means unset and is never validated (R6.i) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592136 [427] Refuse a string that does not match its pattern (R6.h) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592135 [428] Refuse a string outside its length bounds (R6.g) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592134 [429] Refuse a number outside its minimum/maximum (R6.f) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592133 [430] Refuse a config value outside its enum (R6.e) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592132 [431] Refuse a config value of the wrong type (R6.d) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592131 [432] An unknown config key is a warning, not a refusal (R6.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592130 [433] Every required config key must be present (R6.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592129 [434] Refuse a node whose config is not an array (R6.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592128 [435] Report a missing plugin once, not once per port (R1.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592127 [436] A node with no resolvable node type is skipped by the plugin check (R1.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592126 [437] Refuse a node whose executor plugin does not exist (R1.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592125 [438] Refuse a node with no id, located by its position (R5.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592124 [439] Refuse a workflow with more than 1000 edges (R5.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592123 [440] Refuse a workflow with more than 500 nodes (R5.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592122 [441] Retire the node config-validate endpoint (API-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592121 [442] A session with no workflow is a 409, not a 500 (API-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592120 [443] The session-turn door checks its inputs exactly like the launch door (API-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592119 [444] Every JSON door decodes through the shared, bounded decoder (API-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592118 [445] One payload key per node-type concept (STORE-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592117 [446] A finished turn leaves the session completed, not idle (STORE-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592116 [447] Entity statuses are backed enums whose value is what crosses a boundary (STORE-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592115 [448] WorkflowDTO::fromArray() normalizes for the read path only (STORE-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592114 [449] Bundle import runs its gates in a fixed order and rolls back on refusal (STORE-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592113 [450] A workflow's schema version must be semver (STORE-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592112 [451] The stored config schema is strict about node metadata (STORE-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592111 [452] Saving slims transient canvas state out of the stored workflow (STORE-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592110 [453] A validation failure at the REST boundary is a 422 and never reaches save (STORE-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592109 [454] Absent collections default to empty on create; a partial update preserves them (STORE-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592108 [455] A client-supplied id that already exists is a conflict, never an overwrite (STORE-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592107 [456] A workflow name is required and capped at 255 bytes (STORE-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592106 [457] Branch gateways and which edges activate (RT-BR) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592104 [458] Delivering values between nodes (RT-DATA) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592103 [459] Compiling a workflow into an execution plan (RT-CMP) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592102 [460] The pipeline status the editor polls (RT-PIPE) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592101 [461] Choosing and running an orchestrator (RT-ORC) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592100 [462] The StateGraph runner (RT-SG) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592099 [463] Interrupts, pausing and resuming (RT-INT) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592098 [464] How a failing node is handled (RT-ERR) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592097 [465] The JSON API doors (GR-API) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592096 [466] Storing and serving a workflow definition (GR-STORE) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592095 [467] Author-defined dynamic ports (GR-DYN) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592094 [468] A workflow's declared inputs and outputs (GR-MAN) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592093 [469] Resolving a node's parameters (GR-CFG) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592092 [470] Turning a plugin schema into ports and forms (GR-SCHEMA) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592091 [471] The four expression engines (GR-LANG) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592090 [472] Port exposure (GR-EXPO) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592089 [473] How edges connect ports (GR-EDGE) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592088 [474] What the workflow validator refuses (GR-VAL) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592087 [475] Return 400 for a malformed API request body (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592086 [476] Write down and test every runtime and workflow-language rule (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592085 [477] Remove unused API and developer surfaces from 2.x (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592084 [478] Report pipeline and job status consistently to the editor (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592083 [479] Make error routing, cancellation and resume behave the same in every runner (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592082 [480] Catch broken workflows when they are saved, not when they run (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592081 [481] Expression errors fail the node and route to its error edge (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592080 [482] [meta] Make the 2.x runtime and workflow-language contracts explicit and tested (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592079 [483] Refuse an empty, oversized, malformed or too-deeply-nested request body (STORE-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592105 [484] AI Assistant is broken from 1.5.0 (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592073 [485] Add "Show Pipelines" to the operations per workflow (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3589740 [486] Remove "Pending" tag when the workflow is executing and the component has been skipped (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3589739 [487] Add config for max characters (agui, Issue) — https://git.drupalcode.org/project/agui/-/work_items/3585465 [488] Better Error Handling in chat (agui, Issue) — https://git.drupalcode.org/project/agui/-/work_items/3590046 [489] Allow Token support on Assistant Controller (agui, Issue) — https://git.drupalcode.org/project/agui/-/work_items/3589993 [490] Enable Drupal GitLab CI pipeline and add Unit/Kernel/Functional test coverage (agui, Issue) — https://git.drupalcode.org/project/agui/-/work_items/3590044 [491] Add validator and extractor services/methods and new setting. (agui, MR) — https://git.drupalcode.org/project/agui/-/merge_requests/40 [492] Add error util and handler. (agui, MR) — https://git.drupalcode.org/project/agui/-/merge_requests/39 [493] Resolve "Allow Token support on Assistant Controller" (agui, MR) — https://git.drupalcode.org/project/agui/-/merge_requests/38 [494] Resolve "Enable Drupal GitLab CI pipeline and add Unit/Kernel/Functional test coverage" (agui, MR) — https://git.drupalcode.org/project/agui/-/merge_requests/34 --- MODULE SUMMARIES ---
AI (Artificial Intelligence)

The past 24 hours saw progress on Field Widget Actions and guardrail serialization bugs. Support Automator Chain trigger with Field Widget Actions was merged, adding a base class and text plugin that allow Field Widget Actions to invoke Automator Chain workflows directly from entity edit forms without page reloads. This addresses multi-turn AI workflows that exceed single-prompt context limits.

Two guardrail-related fixes were merged into the 1.x branch: MR !1872 and MR !1880 resolve form serialization errors that prevented guardrail subforms from loading on Drupal 11.3 and 11.4.

Several issues remain under review. Streaming chat forces plain-text hostname filtering, corrupting URLs inside HTML attributes has an open MR (!1883) addressing how StreamChatMessageIteratorTrait::getHostnameFilterService() forces plain-text mode, causing HostnameFilter::filterUrlsInPlainText() to corrupt href attributes. Refactor CommonMark instance creation proposes a CommonMarkConverterFactory service to centralize configuration (MR !1881 open). Work continues on Adopt symfony/ai component v0.8 as platform provider (MR !1619), introducing @AiInferenceProvider plugins and associated config entities.

Open issues include MDXEditor fails to parse Drupal tokens in AI Agents prompts, where bracket syntax conflicts with markdown link parsing, and Add a ChatMemoryInterface for storing ChatBot chat history (two MRs open: !1885 and !1835).

How can I help on this project?

Review MR !1883 for the streaming hostname filter bug or MR !1881 for CommonMark refactoring. Pick up MDXEditor token parsing, which has no MR and needs a solution for bracket-syntax conflicts.

Contributors: Ahmad Khalil (ahmad-khalil-imagex) [1], Ann Mary Sruthy (annmarysruthy), Artem Dmitriiev (a.dmitriiev), Bruno Bruno (bbruno), Dezső Biczó (mxr576), Isaac Trogdon (dotist), Marcus Johansson (Marcus_Johansson), Prabhavathi Vanipenta (prabha1997), Rob Loach (robloach), Rodel Duterte (rduterte), Wolfgang Ziegler (fago)
---
Drupal AI Initiative

Activity during this period focused primarily on partnership management and onboarding workflows. Two template issues for partner onboarding were closed: Onboard Gold/Silver AI partner: TEMPLATE and Add Gold/Silver AI partner to d.o pages: TEMPLATE. These templates were used to complete onboarding for Pantheon+Omedia as a Gold partner, with both onboarding tasks and Drupal.org page updates marked closed.

Three new issues were opened for onboarding Specbee as a Silver partner: onboarding, Drupal.org page updates, and a follow-up audit report. A design request was filed to update partner badges from "Sponsor" to "Partner" terminology. Additional process issues were opened covering contributor offboarding, partner audits, and logo wall updates.

On the technical side, a new developer experience issue proposes creating a skill for consistent before/after testing of issues with optional GitLab upload to improve review consistency.

How can I help on this project?

Help design the before/after testing skill described in Create a skill for manual before/after testing of any issue to establish repeatable review workflows.

Pick up Update AI partner badges to use Partner instead of Sponsor, which needs badge SVG updates in the bluecheese theme.

---
AI Integration - ECA

Work continued on Migrate the ECA agent to the Tools + ReAct architecture (create-only) during this period. The migration aims to replace the legacy AiAgentBase architecture currently used in the agents submodule with the newer Tools + ReAct pattern. The existing implementation relies on hand-rolled control flow and three separate YAML sub-prompts (determineTask.yml, buildModel.yml, and answerQuestion.yml) called through runSubAgent(). The proposed refactor would modernize this approach to align with the current agent architecture standards. MR !14 remains open with over 4,400 lines of diff awaiting review. No commits were merged during the reporting period.

How can I help on this project?

Review MR !14 which refactors the ECA agent to use Tools + ReAct architecture. Test the migration against existing ECA workflows to ensure backward compatibility and validate the new control flow.
Contributors: Marcus Johansson (Marcus_Johansson) ---
OpenAI Provider

Three merge requests landed during the reporting period, addressing embeddings, rate limiting, and a GPT-related bug. The add support for batch embeddings MR was merged, adding 284 lines to enable batched embedding operations. A rate limits fix was also merged, contributing 129 lines to handle API rate limiting more effectively. Finally, a GPT bug fix was merged with 55 lines changed.

No issues saw comment activity or status changes in this window, and no blockers were identified in the available data.

How can I help on this project?

Review the OpenAI Provider issue queue for unassigned bugs or feature requests without related merge requests. Test the newly merged batch embeddings and rate limiting functionality against live OpenAI APIs to verify behavior. Document any edge cases or configuration gotchas discovered during testing.
Contributors: Marcus Johansson (Marcus_Johansson) [1], Paul Sheldrake (paulsheldrake) [1] ---
amazee.ai Private AI Provider

No merge activity occurred during the reporting period, though development continues. An open merge request proposes adding request tracking headers to all API calls to the amazee.ai service. The change introduces an X-Amazee-Client header to attribute traffic to the Drupal module and track version information across all outbound requests, including those made via AmazeeClient::makeRequest(), the OpenAI SDK PSR-18 wrapper, health checks, model configuration calls, and trial provisioning endpoints. Version detection uses extension.list.module with a fallback to "dev" for development checkouts.

A critical data loss issue has progressed to RTBC status. The bug affects deployments where multiple Search API indexes share the same Vector Database collection: deleting or clearing items from one index silently removes data from other indexes sharing that collection, due to overlapping entity identifiers. The issue remains assigned and awaiting final review before merge.

How can I help on this project?

Review the request tracking header MR to validate the version detection logic and header implementation.

Test the RTBC data loss fix in a multi-index Vector DB environment to confirm it resolves the issue.

Contributors: Dan Lemon (dan2k3k4)
---
Microsoft Azure AI

A significant refactoring effort is underway to modernize the Azure provider implementation. The merge request [#3552969] feat: Refactor AzureProvider to use OpenAiBasedProviderClientBase was opened during the reporting period, introducing 680 lines of changes to align the AzureProvider with the OpenAiBasedProviderClientBase architecture. This refactor aims to improve code reuse and maintainability by leveraging shared functionality from the base provider client. The merge request is currently awaiting review before it can be merged.

No commits were pushed directly to branches and no other issues saw activity in the past 24 hours. The refactoring work appears to be the primary focus for this module at present.

How can I help on this project?

Review the AzureProvider refactor merge request to help verify the OpenAiBasedProviderClientBase integration and test compatibility with existing Azure AI endpoints.

Test the refactored code against various Azure AI service configurations to identify edge cases or regressions before merge.

Contributors: Jukka Huhta (jhuhta)
---
Postgres VDB Provider

A new merge request was opened addressing Issue #3586862: Re-apply Attributes columns after clear+reindex cycle. The patch targets a problem where attributes columns are dropped during clear and reindex operations. The merge request modifies 40 lines across the codebase and awaits review on the 3586862-clearreindex-drops-columns branch.

No merge activity or commits were pushed during this period. The module remains ready for testing and feedback on the open merge request.

How can I help on this project?

Review the open merge request for re-applying attributes columns after clear+reindex and provide feedback on the approach and implementation.

Test the branch against a local Postgres VDB setup to verify attributes persistence through reindex cycles.

Contributors: Ignacio Pérez Puertas (djnash2002) ---
Model Context Protocol

The Model Context Protocol module saw continued work on authentication issues during this period. Activity focused on Token Auth is not working, which addresses two problems: a Form API states selector misconfiguration preventing the token authentication checkbox from functioning in the admin UI, and issues with token validation even when configured manually. The problem stems from an incorrect #states selector targeting :input[name="enable_token_auth"] instead of the correct :input[name="auth_settings[enable_token_auth]"] path. An open merge request (!52) with 239 lines of changes is awaiting review to resolve both authentication issues.

No merge requests were merged and no commits were pushed during this 24-hour window, though the issue remains actively assigned as part of the AI Initiative Sprint work.

How can I help on this project?

Review MR !52 to validate the Form API states selector fix and token authentication implementation. Test the changes in a local environment to confirm both the admin UI interaction and token validation work correctly across different configuration scenarios.
Contributors: Alin Ameiroaie (aalin) ---
AI Agents

Activity this period focused on feature work and bug fixes, though no merges were completed. The Add a way to set provider tags in the runner issue was closed, which introduced optional provider tagging for config agents to help filter LLM events during debugging and monitoring.

Several merge requests saw activity. A new draft MR opened to address Give a parent agent possibility to forward request as is, which aims to reduce information loss and costs when orchestration agents forward single instructions to subagents by allowing token-based passthrough. Work continued on provider picker functionality for the 1.4.0 release, enabling per-agent provider and temperature configuration rather than relying solely on default Chat with Tools providers or event-based workarounds.

Bug fix MRs remain open for chatbot issues including search_string truncation differences between the chatbot and tool explorer, and repeating responses after clearing history when using return direct mode. Additional work is in progress on role-based tool execution and tool run limits.

How can I help on this project?

Review the open MRs for chatbot search_string truncation and chatbot history clearing to help move bug fixes forward. Test the provider picker implementation for the upcoming 1.4.0 release to identify integration issues.
Contributors: Bharat Kelotra (bharatkelotra), Marcus Johansson (Marcus_Johansson) ---
Tool API

The Tool API module made significant progress toward 1.0.0-rc1 during this period, with multiple critical bug fixes merged and API freeze preparation underway. Five merge requests were integrated, resolving issues in REST serialization, result lifecycle handling, LLM schema generation, and context data propagation.

The MapDefinitionNormalizer and ContextDefinitionNormalizer break REST serialization issue was resolved, correcting getSupportedTypes() to restore compatibility with core's serialization system. The BadMethodCallException masking error feedback fix introduced hasResult() checks and test coverage to prevent exceptions when accessing unexecuted tool results. Schema generation for LLM consumers was improved by fixing HTML-escaped entity handle descriptions and addressing Anthropic schema validation failures caused by malformed nullable type declarations. Context data handling was corrected in the AI connector via fixes to parent context propagation.

Drupal 10.5 compatibility was restored with previous-major CI jobs now active, ensuring the module supports ^10.5 || ^11. A meta issue tracking the path to 1.0.0-rc1 identifies 16 remaining API freeze tasks covering signature corrections, identifier prefixing, cache implementation, translation, test coverage, and documentation.

How can I help on this project?

Review the open configuration-sourced input values fix (MR !111), which corrects inverted semantics in getConfigurationValue() and adds missing test coverage. Pick up translatable violation messages (no MR exists yet) to replace sprintf() calls with TranslatableMarkup. Help annotate the API surface with @api/@internal markers per the API documentation task.

Contributors: Abhisek Mazumdar (abhisekmazumdar) [1], Bryan Sharpe (b_sharpe) [1], Michael Lander (michaellander) [11]
---
Drupal Canvas

Three merge requests were completed during this period. The CLI push includes unsupported label property for content templates issue was resolved, ensuring the CLI tool omits the unsupported label property from POST requests while retaining it in local authored files. The Canvas CLI sync fails for media and link props in global regions fix was merged, addressing schema validation errors for media-image and link props by handling computed properties like inputs_resolved correctly during push operations. Additionally, the long-standing Automate MR review using PHPCS work was completed, introducing automated enforcement and fixing of service resolution patterns to require \Drupal::service(Something::class) over string-based service IDs wherever possible.

Active work continues on several fronts. The Canvas AI: Improve the schema of the place_components tool was merged, replacing the basic YAML string argument with a structured operations schema matching the edit_components tool. Open merge requests include enhancements to RTL support via logical CSS properties, TMGMT translation fixes for components on pinned versions, and AI tooling improvements including a Tools dropdown and an Agents & Tools settings form.

How can I help on this project?

Review the open MR !1418 addressing translatable props missing from TMGMT forms for older component versions. Test the MR !1440 fixing validation of non-required select props. Pick up the unassigned AutoSaveManager hash stability issue, which needs work on normalization and strict casting.

Contributors: **** (project_19391_bot_17a61b0edeafd5a3db3e8b2462b6c010), **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Adam G-H (phenaproxima), Ben Mullins (bnjmnm), Bálint Kléri (balintbrews) [1], Canvas version bot [2], David Bravo (davidbp), Harumi Jang (hooroomoo), Jeremy Chinquist (jjchinquist), Juan Correa (jucs7) [1], Kunal Sachdev (kunal.sachdev), mariosr, Rajab Natshah (RajabNatshah), Tekla Aivazashvili (aivazashvilit), Wim Leers (wimleers) [1], wotnak [1]
---
Context Control Center (CCC)

Work this period focused on upgrade path stability and Drupal 10 compatibility ahead of the 1.0 release candidate. An upgrade failure from beta2 was identified in updates 10006 and 10011, stemming from the bundleless entity conversion; the fix addresses NULL constraint violations and stale Content Moderation field definitions. Drupal 10 compatibility issues introduced in beta3 were traced to attribute-based hook discovery not available in Drupal 10; the solution includes explicit service registration for DiffHooks, DynamicEntityReferenceHooks, and SchedulerHooks, plus restoration of PHP 8.1 support.

Design work progressed on scope plugin improvements. Scope plugin persistence API refactoring aims to complete the manager orchestration layer and encapsulate target entity storage, removing special-case logic from AiContextItemForm and entity hooks. Renaming entity bundle and target entity scope plugins continues to improve developer experience around bundleless content entities. Performance optimization in AiContextOverviewController::overview() addresses unbounded published-ID queries; the proposal converts an early-break pattern to a LIMIT 1 scope-index query. Discussions opened on context item priority ranking and a broader review of selection factors before 1.0.

QA planning began for comprehensive manual and automated testing before stable release.

How can I help on this project?

Review MR !223 for Drupal 10 compatibility and hook service registration fixes.

Review MR !229 to validate the beta2 upgrade path repairs in updates 10006, 10008, and 10011.

Test the current beta manually on Drupal 10 and 11 installations to help identify additional upgrade or compatibility issues before RC1.

Contributors: Kristen Pol (kepol), Levente Besenyei (LeventeB), Pravesh Poonia (Pravesh_Poonia), Reinhold Schachner (reinimax), Tamas Balog (tbalog)
---
AI CKEditor

A new merge request was opened to Show AI status indicator next to the Generate button. The change mirrors the AI Writer status text into a compact indicator positioned next to the Generate button, addressing a usability issue where users previously had to scroll within the modal to see the status below the response editor. The 75-line diff aims to provide immediate feedback when a generation request is in progress.

How can I help on this project?

Review the open AI status indicator merge request, testing the UX improvement and providing feedback on the implementation approach.

Check the module's issue queue for unassigned bugs or feature requests that could benefit from a patch or new MR.

Contributors: Ricardo Castañeda (cadence96)
---
AI Search

Work this period centered on improving access control and data exposure in the AI Search module. Four issues saw active discussion and MR updates around how the module handles security, datasource flexibility, and result metadata.

Two new access-control proposals were opened as spinoffs from earlier work. Defer default search item access checking to the Search API datasource plugin proposes refactoring the hardcoded entity access checks in SearchApiAiSearchBackend to delegate to datasource plugins, enabling custom and non-content entity datasources to enforce their own access rules. A related issue, Introduce a dedicated runtime access-checking API for AI Search / RAG filtering, suggests a new layer for context-specific filtering beyond standard view access—such as excluding sensitive data from LLM requests or dynamically restricting results by chatbot persona.

A separate issue highlights that RagTool::execute() should expose structured per-result data and check entity access. Currently, RagTool::execute() flattens search results into a single string, discarding per-result metadata like entity IDs and scores, which blocks consumers from retrieving source citations or performing access checks on the underlying entities.

Contributors: David Bondor (superbondor), Dezső Biczó (mxr576)

How can I help on this project?

Review MR !74 for the datasource access delegation refactor, focusing on backward compatibility and edge cases.

Review MR !75 introducing the runtime access API; test coverage is explicitly needed.

Pick up RagTool::execute() structured data exposure, which has no MR yet and needs implementation.

---
AI translate

No merge requests were merged during the reporting period. Two open issues saw activity: work continued on Add documentation, which has a draft MR open to provide documentation for the module, and Fix Pipeline, where an open MR aims to resolve broken phpstan and phpunit pipelines on the 2.0.x branch by adding composer.json. Both issues remain in progress with no commits pushed in the last 24 hours.

How can I help on this project?

Review the open merge request for Fix Pipeline to help unblock CI/CD. Alternatively, review the draft documentation MR to provide feedback on completeness and clarity for module users.

Contributors: Marcus Johansson (Marcus_Johansson), Rob Loach (robloach)
---
FlowDrop

The FlowDrop project closed a major specification and testing milestone during this period, finalizing a comprehensive runtime and workflow-language contract for the 2.x branch. Over 70 specification-registry issues were closed, documenting behavior across validation, storage, orchestration, state management, error handling, interrupts, branching, data delivery, compilation, expression evaluation, port exposure, schema derivation, and edge semantics. Each rule now cites its implementation and binding test, enforced by scripts/spec-coverage.php --check.

Key contract clarifications include:

Error handling unified: All four expression-consuming processors (DataMapper, DataExtractor, DataShaper, PromptTemplate) now wrap engine errors as \RuntimeException, failing the node and enabling error-edge routing (LANG-29). Direct-sync error routing was brought into line with the pipeline engines (ERR-13), and cancellation is now announced via PipelineCompletedEvent across all runners (ORC-15).

Validation tightened at save: The workflow validator now refuses unresolvable node types (R9), edges into hidden ports (R7), workflow-exposure entries targeting hidden ports (R10), invalid expressions per engine (R11), and structural defects like self-edges (R12) and duplicate parallel edges (R13). Validation re-runs at launch (VAL-LAUNCH), and the session-turn door now applies the same strict input checking as the launch door (API-2).

Status reporting formalized: The pipeline API's node_statuses keys are guaranteed to be workflow node ids (PIPE-4), job status summaries have one shape derived from the JobStatus enum (PIPE-2), and vocabulary guarding is scoped to prevent unknown statuses from raising warnings (PIPE-3). Entity statuses are now backed enums (STORE-11), and a finished session turn leaves the session completed rather than idle (STORE-12).

Port exposure cascade: Effective exposure resolves from instance config.ports[].exposed override, then metadata exposedByDefault, then TRUE (EXPO-2). Hidden outputs are stripped at production (EXPO-11–14), and hidden inputs receive no runtime value (EXPO-10). The one-time exposure freeze (update_10004/10005) is documented (EXPO-9), and the seam where a post-install param has no config key is noted (EXPO-8).

Parameter resolution precedence: Runtime (Priority 1) when connectable && exposed, config (Priority 2) when configurable, default (Priority 3) unconditional (CFG-4–6). Presence is array_key_exists, so an explicit NULL wins (CFG-7).

Schema and metadata: The run path re-enriches from the live node type (SCH-29), executor plugin id resolves from the entity (SCH-28), and the wire shape is lean-by-divergence (SCH-27). Reserved config props and unified I/O ports are injected per documented rules (SCH-11–18, SCH-21).

Storage and API: All nine JSON-accepting controllers decode via ApiResponseTrait::decodeJsonRequest() with an 8 MiB, depth-64 gate (API-1, STORE-1). Validation failures at the REST boundary yield 422 with {success, error, details} (STORE-5), and a session with no workflow is a dedicated 409 (API-3).

Supporting changes: the node config-validate endpoint was retired (API-4), validateParams() deleted from the processor contract (R6.k), and dead API surfaces (status-polling endpoints, the metrics tracker, getSupportedInputTypes(), unused orchestrator methods) removed. WorkflowDTO::fromArray() is now read-path-only (STORE-10), bundle import runs its gates in a fixed order and rolls back on refusal (STORE-9), and preSave slims transient canvas state in two independent passes (STORE-6).

Three user-facing bugs were also closed: the AI Assistant no longer freezes after applying changes (fixed from 1.5.0), pipelines can now be viewed per workflow via a new operation link, and skipped nodes display a "Skipped" tag instead of remaining "Pending".

How can I help on this project?

Review the new specification registry in docs/development/specification-registry.md and flag any runtime behavior that contradicts a documented rule. Test edge cases around expression error handling (LANG-21–26) with processors that declare configurable && required parameters. Audit controller exception handling to ensure no endpoint still catches \RuntimeException wide or echoes getMessage() to the client.
---
AG-UI

Four significant features were merged over the past 24 hours, substantially improving security, error handling, and test coverage for the AG-UI module.

The Add config for max characters feature was merged, introducing new validator and extractor services to prevent token exhaustion exploitation. A configurable character limit now denies chat requests that exceed the threshold before they reach remote assistants.

Better Error Handling in chat was also shipped, addressing an issue where non-2xx HTTP responses (such as 403 errors from JWT/flood checks) were displayed verbatim in the chat UI. The new error utility and handler provide user-friendly error messages instead of raw response bodies.

Anonymous user security improved with the merge of Allow Token support on Assistant Controller, which adds token-based authentication to mitigate bot abuse via direct POST requests to agent endpoints.

Finally, Enable Drupal GitLab CI pipeline and add Unit/Kernel/Functional test coverage establishes automated testing infrastructure with a standard .gitlab-ci.yml configuration and comprehensive PHPUnit test coverage for both the main module and agui_mercure submodule.

How can I help on this project?

Review the open issues to identify bugs or feature requests without assigned merge requests. Test the newly merged character limit validator and error handling features in your own Drupal environment and report any edge cases. Contribute additional test coverage for untested code paths identified during CI runs.
Contributors: Ahmad Khalil (ahmad-khalil-imagex), Bryan Sharpe (b_sharpe) ======================================================================== ## [4] factcheck:tldr:developer ======================================================================== Layer-1 corrections: 0 Judge flags: 2 ======================================================================== ## [5] summariseModule:ai:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: AI (Artificial Intelligence) (machine name: ai) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Ahmad Khalil (ahmad-khalil-imagex) [1], Ann Mary Sruthy (annmarysruthy), Artem Dmitriiev (a.dmitriiev), Bruno Bruno (bbruno), Dezső Biczó (mxr576), Isaac Trogdon (dotist), Marcus Johansson (Marcus_Johansson), Prabhavathi Vanipenta (prabha1997), Rob Loach (robloach), Rodel Duterte (rduterte), Wolfgang Ziegler (fago)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
AI (Artificial Intelligence)
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [MDXEditor fails to parse Drupal tokens in AI Agents prompts](https://git.drupalcode.org/project/ai/-/work_items/3586613) State: opened | Updated: 2026-07-31 | Author: Marcus Johansson (Marcus_Johansson) | Assigned: Bruno Bruno (bbruno) | Labels: 2026Sprint15, aiAgent, category::bug, priority::major Description: When editing an AI Agent prompt in the MDXEditor-backed prompt field, entering a Drupal token can make the editor throw: > Parsing of the following markdown structure failed The likely cause is that a token such as `[node:title]` looks like the start of a markdown link reference (`[text](url)` / `[text][ref]`), so the MDX/markdown parser chokes on the bracketed text instead of treating it as literal content. ### Steps to reproduce (to be confirmed) 1. Go to an AI Agent that uses a prompt field rendered with MDXEditor (`data-mdxeditor`, see `src/Hook/FormElement.php` and `src/Form/AiPromptS… ### [MDXEditor throws error when prompt includes a colon (:) character](https://git.drupalcode.org/project/ai/-/work_items/3586619) State: closed | Updated: 2026-07-31 | Author: Michael Anello (ultimike) | Assigned: unassigned | Labels: category::bug, priority::normal, state::accepted, why::duplicate Description: I have this sentence as part of an AI prompt in MDXEditor: > If there is a field on the entity that that matches the field name provided to you, then use the Set field value tool to set the new field value. Be sure to pass it the entity using the format "node:NODE_ID" or "media:MEDIA_ID". For example, if the node to be updated has a node id of 7, then the entity value should be "node:7". While in Markdown mode, if the `:` is not escaped (`/:`), MDXEditor complains: > Parsing of the following markdown structure failed: {"type":"textDirective","name":"NODE_ID"}. > > You can fix the errors in… ### [Decide permission system for new AI Platform and AI Inference Providers](https://git.drupalcode.org/project/ai/-/work_items/3586628) State: opened | Updated: 2026-07-31 | Author: Dezső Biczó (mxr576) | Assigned: unassigned | Labels: category::plan, priority::normal, state::accepted Description: The new AI Platform Config and AI inference Providers Config entities still depends on the legacy "`administer ai providers`" permission. The scope of this issue is getting an agreement on whether we would like to change that or not. ### [Support Automator Chain trigger with Field Widget Actions](https://git.drupalcode.org/project/ai/-/work_items/3586602) State: closed | Updated: 2026-07-31 | Author: Zsolt Gere (gerezs) | Assigned: unassigned | Labels: 2026Sprint14, aiAutomators, category::feature, fieldWidgetActions Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1828 [Issue #3586602: Add a field widget action base class and text plugin to run...](https://git.drupalcode.org/project/ai/-/merge_requests/1828) | State: merged 2026-07-31 | Author: Ahmad Khalil (ahmad-khalil-imagex), 1287 diff lines Description: Feature suggest: In practice, we bumped into a situation where a workflow couldn't be done in a single Automator flow because of context window limit and in general it couldn't work as a single prompt and we didn't want to have multiple fields for a multiturn workflow so we figured to create the workflow of Automator Chain. We wanted to include this as an action on the edit page without page reload but FWA ddidn't allow to use Automator Chain. I asked a coding agent to prototype this and you can see this FWA form allows to select Aotmator Chain type option when adding a New Action, Next it al… ### [What providers for TextClassification?](https://git.drupalcode.org/project/ai/-/work_items/3586629) State: opened | Updated: 2026-07-31 | Author: Jonathan Hunt (jonathanhunt) | Assigned: unassigned | Labels: category::support, priority::normal, state::accepted Description: AI Settings `/admin/config/ai/settings` under 'Additional AI Capabilities' says for 'Text Classification' "Check the AI module homepage for available providers.", however I can find no information re text classification at https://www.drupal.org/project/ai or https://ultimike.github.io/ai-module-usage/ Also, https://project.pages.drupalcode.org/ai/1.4.x/developers/call_text_classification/ suggests using AI API Explorer > Text Classification Explorer under /admin/config/ai/explorers/ai-text-classification to test out different calls and see the code that you need for it, but no Text Classific… ### [The Toolbar Chatbot runs the fold out animation on page reload](https://git.drupalcode.org/project/ai/-/work_items/3568246) State: opened | Updated: 2026-07-31 | Author: drupalbot | Assigned: unassigned | Labels: 2026Sprint14, 2026Sprint15, AI Initiative Sprint, Needs UX review Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !1428 >>> [Tracker] Update Summary: [One-line status update for stakeholders] Short Description: [One-line issue summary for stakeholders] Check-in Date: MM/DD/YYYY Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation The chatbot was greatly improved with #3554510: Sync Design of Toolbar Chatbot with Canvas AI Chatbot, but one issue is that if you have a local storage to remember the position, when its open on page load it runs the open up… ### [Support interactive/rich content (e.g. links) in the AI tooltip component](https://git.drupalcode.org/project/ai/-/work_items/3586630) State: opened | Updated: 2026-07-31 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: UX, category::feature, priority::normal, state::accepted Description: ## Summary Follow-up to: ai_context#3586292+s The shared AI tooltip component renders its content as a non-interactive "hint" popover. Consuming modules cannot place reachable interactive content (such as links or buttons) inside a tooltip, because the popover is not focusable and its content is injected as innerHTML purely for display. ## Problem / motivation The tooltip is populated from a `data-ai-tooltip` attribute and injected via innerHTML, then shown on `mouseenter` / `focusin` as a transient hint: - `ai/assets/js/ai_global.js` sets `popover.innerHTML = popoverTrigger.dataset.aiTo… ### [Streaming chat forces plain-text hostname filtering, corrupting URLs inside HTML attributes (e.g., href="")](https://git.drupalcode.org/project/ai/-/work_items/3586624) State: opened | Updated: 2026-07-31 | Author: Ron Raney (rraney) | Assigned: unassigned | Labels: category::bug, priority::normal, state::needsReview Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1883 [bug: #3586624 Streaming chat forces plain-text hostname filtering, corrupting...](https://git.drupalcode.org/project/ai/-/merge_requests/1883) | State: opened | Author: Ann Mary Sruthy (annmarysruthy), 710 diff lines Description: **Problem/Motivation** `StreamChatMessageIteratorTrait::getHostnameFilterService()` forces `HostnameFilter::setPlainTextMode(TRUE)` whenever code isn't running inside a PHP Fiber (which is the normal case for typical request-based streaming consumers, e.g. AI CKEditor's Reformat/Modify tools). With plain-text mode forced on, `HostnameFilter::filterText()` skips the HTML-aware filtering branch and instead runs `filterUrlsInPlainText()` — a raw regex substring replace across the entire response text, with no awareness of HTML structure. When AI-processed content contains an `` tag pointing to … ### [Adopt symfony/ai component v0.8 as platform provider](https://git.drupalcode.org/project/ai/-/work_items/3586427) State: opened | Updated: 2026-07-30 | Author: Wolfgang Ziegler (fago) | Assigned: unassigned | Labels: Has Testing Steps, priority::normal, state::needsReview, v2.x-dev Description: [#3574187] introduced symfony/ai component in v0.6. Meanwhile 0.8 has been released, introducing its own provider abstraction: a symfony [ProviderInterface](https://github.com/symfony/ai/pull/1923). Based upon @mxr576's [plan](https://git.drupalcode.org/project/ai/-/work_items/3574187#note_809810), we want to adopt the new abstraction in this issue. Overview over the concepts, citing the Symfony PR: > **ProviderInterface** encapsulates what PlatformFactory::create() currently produces — a complete, self-contained connection to a single inference backend (model clients, result converters, c… ### [AI Automator Token Replacement with removing unresolved Tokens (Checkbox?)](https://git.drupalcode.org/project/ai/-/work_items/3586535) State: opened | Updated: 2026-07-30 | Author: ro-no-lo | Assigned: Rodel Duterte (rduterte) | Labels: 2026Sprint15, AI Initiative Sprint, Needs review, Quick Win Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1884 [Issue #3586535: AI Automators strip unresolved tokens from prompts](https://git.drupalcode.org/project/ai/-/merge_requests/1884) | State: opened | Author: Rodel Duterte (rduterte), 86 diff lines Description: When we use the Advanced mode with Tokens in the AI Automator settings, Tokens which are not resolved by the Token system stay in the AI Prompt. This is not much text for AI, but everything what can be avoided to send to AI, should be removed. As an example. I have an Entity where I defined a textarea called field_user_prompt which can optionally (!) be used to alter the prompt I setup in the field AI automation. So there is a Token like this: [node:field_user_prompt:value]. This stays when the user left the field empty. It's only replaced when something is filled in. I do think that unresol… ### [Add a ChatMemoryInterface for storing ChatBot chat history](https://git.drupalcode.org/project/ai/-/work_items/3586539) State: opened | Updated: 2026-07-30 | Author: Marcus Johansson (Marcus_Johansson) | Assigned: unassigned | Labels: aiChatbot, category::feature, priority::normal, state::needsReview Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1885 [Issue #3586589: Add ChatMemory plugin type](https://git.drupalcode.org/project/ai/-/merge_requests/1885) | State: opened | Author: Rob Loach (robloach), 1390 diff lines - MR !1835 [fix: #3586589 Do not assume action definitions have a type when deriving action plugin functions](https://git.drupalcode.org/project/ai/-/merge_requests/1835) | State: opened | Author: Ahmad Khalil (ahmad-khalil-imagex), 7787 diff lines Description: ## Problem/Motivation ChatBots need a way to store chat history. Today there is no standardized mechanism for a ChatBot to persist conversation history across requests. We want each ChatBot to be **in charge of its own memory handling**: - A ChatBot may opt in to a server-side memory backend by setting up a `ChatMemoryInterface` implementation. - A ChatBot may instead handle history entirely on the frontend (e.g. browser `localStorage`) and skip the interface altogether. The decision — whether to use a `ChatMemoryInterface` at all, and which implementation — belongs to the ChatBot. ## Pro… ### [[1.x] Add a setup-automators agent skill to configure automators on fields](https://git.drupalcode.org/project/ai/-/work_items/3586563) State: opened | Updated: 2026-07-30 | Author: Marcus Johansson (Marcus_Johansson) | Assigned: unassigned | Labels: AI Initiative Sprint, AI Innovation, aiAutomators, category::task Description: ## Description The AI Automators submodule lets site builders attach an **automator** to a field so its value is generated automatically when the entity is saved (for example, summarising body text into a summary field, or generating alt text for an image). Configuring an automator today means working through the field's admin UI. This task adds a `setup-automators` agent skill (under `modules/ai_automators/.agents/skills/`) that configures automators on fields, driven through the [Tool module](https://www.drupal.org/project/tool)'s tools via `drush tool:run`. It is the Automators counterpar… ### [Add a configure-ai-settings agent skill for general AI settings (default models, providers, timeout, trusted domains)](https://git.drupalcode.org/project/ai/-/work_items/3586562) State: opened | Updated: 2026-07-30 | Author: Marcus Johansson (Marcus_Johansson) | Assigned: unassigned | Labels: AI Initiative Sprint, AI Innovation, Has Testing Steps, aiCoreModule Description: ## Description Following the same pattern as the `setup-guardrails` skill (#3586561), the AI module would benefit from a companion skill that configures the module's **general settings** on a running site, driven through the [Tool module](https://www.drupal.org/project/tool)'s tools via `drush tool:run`. Today these settings can only be inspected and changed through the admin UI at `/admin/config/ai/settings`. This task adds a `configure-ai-settings` skill (sibling of `create-guardrail-plugin` and `setup-guardrails`, under `ai/.agents/skills/`) covering the core operational settings stored i… ### [Add a setup-guardrails agent skill to configure guardrails, guardrail sets, and global guardrails](https://git.drupalcode.org/project/ai/-/work_items/3586561) State: opened | Updated: 2026-07-30 | Author: Marcus Johansson (Marcus_Johansson) | Assigned: unassigned | Labels: AI Initiative Sprint, AI Innovation, Needs manual testing, aiCoreModule Description: ## 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](ht… ### [Streamed chatbot agent response](https://git.drupalcode.org/project/ai/-/work_items/3578168) State: opened | Updated: 2026-07-30 | Author: drupalbot | Assigned: unassigned | Labels: aiAssistantsApi, category::bug, priority::normal, state::needsWork Description: >>> [!note] Migrated issue Reported by: [d0t15t](https://www.drupal.org/user/132353) Related to !1304 >>> Problem/Motivation When using an AiAssistant that is backed by an AI agent (ai_agent field set), enabling streaming output has no effect. The full LLM response is always returned as a single chunk rather than being streamed token by token. The root cause is in AiAssistantApiRunner::process(): when an agent is detected, it delegates to AgentRunner::runAsAgent() but does not pass $this->streaming. As a result, the ChatInput passed to the agent never has setStreamedOutput(TRUE) called… ### [Assistants backed by an agent never stream](https://git.drupalcode.org/project/ai/-/work_items/3586627) State: closed | Updated: 2026-07-30 | Author: Isaac Trogdon (dotist) | Assigned: unassigned | Labels: state::closed, why::duplicate Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1882 [Resolve #3586627: Assistants backed by an agent never stream](https://git.drupalcode.org/project/ai/-/merge_requests/1882) | State: opened | Author: Isaac Trogdon (dotist), 51471 diff lines Description: Problem/Motivation An AI Assistant with an ai_agent attached can never stream. AgentRunner::runAsAgent() never tells the agent to stream, so the response always comes back as a ChatMessage. DeepChatApi then answers with application/json while the Deepchat block has already advertised connect.stream = true, so the frontend sits waiting for SSE frames that never arrive. The answer is still persisted, so it appears only after a page reload. Steps to reproduce 1. Create an AI Assistant and set an agent under AI Agent. 2. Place the AI Deepchat block, enable Stream. 3. Ask a questio… ### [Refactor CommonMark instance creation](https://git.drupalcode.org/project/ai/-/work_items/3586608) State: opened | Updated: 2026-07-30 | Author: Rob Loach (robloach) | Assigned: Ann Mary Sruthy (annmarysruthy) | Labels: aiCoreModule, category::feature, priority::minor, sprint-candidate Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1881 [Add CommonMarkConverterFactory service.](https://git.drupalcode.org/project/ai/-/merge_requests/1881) | State: opened | Author: Prabhavathi Vanipenta (prabha1997), 151 diff lines Description: ## Summary Following #3586595 , we moved league/commonmark to be a real dependency for the AI module. In this we create CommonMarkConverter objects, all with different options. ```php public function getCommonMarkConverter(): object { return new CommonMarkConverter(); } ``` ```php $converter = new CommonMarkConverter(['html_input' => 'escape']); ``` ```php $converter = new CommonMarkConverter([ 'html_input' => 'strip', 'allow_unsafe_links' => FALSE, ]); ``` It would be good to introduce some sort of service that would dependency inject the commonmarkconverte… --- MERGE REQUESTS (24h) --- ### [Issue #3586602: Add a field widget action base class and text plugin to run...](https://git.drupalcode.org/project/ai/-/merge_requests/1887) State: opened | Author: Artem Dmitriiev (a.dmitriiev) | Branch: cherry-pick-4189a111-2 | 1293 diff lines Description: ## Description ## Testing instructions 1. 2. ## Checklist - [ ] I have linked the related issue in the MR title or description - [ ] I have performed a self-review of my own code - [ ] I have added or updated tests, or explained in the description why this change is not covered by tests - [ ] I have updated documentation for any new or changed functionality - [ ] I have written testing instructions and verified them locally - [ ] I have noted any required post-merge steps (config imports, cache rebuilds, manual changes) - [ ] This MR contains no breaking API or hook changes, or the… ### [Issue #3586602: Add a field widget action base class and text plugin to run...](https://git.drupalcode.org/project/ai/-/merge_requests/1888) State: closed | Author: Artem Dmitriiev (a.dmitriiev) | Branch: cherry-pick-4189a111-3 | 1287 diff lines Description: ## Description ## Testing instructions 1. 2. ## Checklist - [ ] I have linked the related issue in the MR title or description - [ ] I have performed a self-review of my own code - [ ] I have added or updated tests, or explained in the description why this change is not covered by tests - [ ] I have updated documentation for any new or changed functionality - [ ] I have written testing instructions and verified them locally - [ ] I have noted any required post-merge steps (config imports, cache rebuilds, manual changes) - [ ] This MR contains no breaking API or hook changes, or the… ### [Issue #3586602: Add a field widget action base class and text plugin to run...](https://git.drupalcode.org/project/ai/-/merge_requests/1886) State: merged 2026-07-31 | Author: Artem Dmitriiev (a.dmitriiev) | Branch: cherry-pick-4189a111 | 1287 diff lines Description: ## Description ## Testing instructions 1. 2. ## Checklist - [ ] I have linked the related issue in the MR title or description - [ ] I have performed a self-review of my own code - [ ] I have added or updated tests, or explained in the description why this change is not covered by tests - [ ] I have updated documentation for any new or changed functionality - [ ] I have written testing instructions and verified them locally - [ ] I have noted any required post-merge steps (config imports, cache rebuilds, manual changes) - [ ] This MR contains no breaking API or hook changes, or the… ### [feat: #3586585 Add YAML support to the MDX editor code blocks](https://git.drupalcode.org/project/ai/-/merge_requests/1823) State: opened | Author: Ann Mary Sruthy (annmarysruthy) | Branch: 3586585-add-yaml-support-to-the-mdx-editor-code-blocks | 226 diff lines Description: ## Description - YAML is now available as a code block language in the rich text (MDX) editor. When inserting a code block and choosing a language from the dropdown, "YAML" now appears alongside the existing options (JavaScript, Python, CSS, JSON, etc.), with proper syntax highlighting. - Fixed a bug where code blocks in certain languages couldn't be typed into. Previously, choosing a language other than JavaScript or CSS for a code block (for example Python, or the newly added YAML) would silently stop accepting any keyboard input — the block looked fine but nothing you typed showed up. This… ### [#3568246: fix late chatbot opening on page load](https://git.drupalcode.org/project/ai/-/merge_requests/1428) State: opened | Author: Bruno Bruno (bbruno) | Branch: 3568246-chatbot-state | 198 diff lines Description: Persist chatbot open state in backend instead of localStorage to ensure it’s applied during initial render and prevent layout shift. localStorage + JS only runs after the page has loaded, so it will _always_ cause a shift. ### Testing Instructions 1. Create an Assistant at **/admin/config/ai/ai-assistant** 2. Place the `AI DeepChat Chatbot` block at **/admin/structure/block/list/gin** 3. Make sure the **Placement** field under **Styling settings** is set to `Toolbar` 4. Open the chatbot using the Chatbot opener button on the top left 5. Once opened, refresh the page -> check that the chatbo… ### [feat: #3586427 Adopt symfony/ai v0.8's Platform concept](https://git.drupalcode.org/project/ai/-/merge_requests/1619) State: opened | Author: Wolfgang Ziegler (fago) | Branch: 3586427-adopt-symfonyai-08 | 5767 diff lines Description: ## Dependencies ~~!! This MR builds upon the MR [#1613](https://git.drupalcode.org/project/ai/-/merge_requests/1613) - please review this one first!~~ ## Description This MR implements the Symfony AI integration architecture as documented in ADR 001 (AI Platform Integration Architecture), using the Plugin-in-Config pattern for both platform and inference provider configuration entities. ### New Plugin Types & Config Entities - **`@AiInferenceProvider`** plugin type + `ai_inference_provider` config entity - One Symfony inference backend with API key / base URL / model list - Ships `Gen… ### ["1.x backport"](https://git.drupalcode.org/project/ai/-/merge_requests/1321) State: closed | Author: Dezső Biczó (mxr576) | Branch: 3575992-1.x-backport | 137 diff lines Description: Closes #3575992 This PR also contains changes from https://www.drupal.org/project/ai_search/issues/3575999. ### [Issue #3586620 Merge 1.3.x guardrails](https://git.drupalcode.org/project/ai/-/merge_requests/1880) State: merged 2026-07-30 | Author: Marcus Johansson (Marcus_Johansson) | Branch: 1-3-merge-guardrails | 920 diff lines --- COMMITS (24h) --- - [4189a111](https://git.drupalcode.org/project/ai/-/commit/4189a1111e56f85aace1d5e645fd3e41072be03b) Issue #3586602: Add a field widget action base class and text plugin to run... — Ahmad Khalil (2026-07-31T07:46:35.000+00:00) ======================================================================== ## [6] summariseModule:ai_initiative:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Drupal AI Initiative (machine name: ai_initiative) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. Do not name any individual people in this section. No one was active enough this period to list. Format your response as an HTML fragment. Start with
Drupal AI Initiative
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Create a skill for manual before/after testing of any issue, with optional glab upload](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586629) State: opened | Updated: 2026-07-30 | Author: Marcus Johansson (Marcus_Johansson) | Assigned: Marcus Johansson (Marcus_Johansson) | Labels: 2026Sprint15, AI Initiative Sprint, DX (Developer Experience), ai::outside Description: ## Problem/Motivation Reviewing an issue manually is repetitive and easy to do inconsistently. To judge whether a merge request actually fixes what it claims, a reviewer has to set up the site, reproduce the original behaviour, apply the change, and then walk the exact same path again. In practice the "before" step is often skipped, so the review says "it works" without ever showing that it was broken to begin with. There is no shared, repeatable way to do this, and nothing that produces evidence a maintainer can look at without rebuilding the environment themselves. ## Proposed resolution … ### [Onboard Silver AI partner: Specbee](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586639) State: opened | Updated: 2026-07-30 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: category::task, management, priority, priority::normal Description: ## Problem/Motivation Need to onboard new Silver partner: Specbee ## Proposed resolution Go through onboarding form and do what I can and then hand off to dev, marketing, UX, and QA teams as needed. ## Target date or deadline July 2026 ## Remaining tasks - [x] Create partner onboarding tab from template - [x] Review onboarding form - [x] Send legal and invoicing contacts to DA - [ ] Add to mailing lists - [ ] Add to private Slack channels (partners/contributors) - [ ] Add to public Slack channels (marketing/UX/QA/ai-contrib) - [ ] Add to non-dev meeting invites (marketing/UX) - [ ] Add … ### [Add Silver AI partner to d.o pages: Specbee](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586638) State: opened | Updated: 2026-07-30 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: category::task, management, priority, priority::normal Description: ## Proposed resolution Follow-up to: #3586639+s Update `/ai/partners` and `/ai/become-a-partner`. **Logo:** https://drive.google.com/file/d/1O6UCiatujiRgLPpUWOde5POERWOYMF9g/view?usp=sharing Note that it's going to change soon **100 word text:** Specbee is a Drupal development agency headquartered in Atlanta. We have built only Drupal since 2015 and contribute regularly to the project. As a partner in the Drupal AI Initiative, we help advance AI capabilities in Drupal. Our clients include Michael J. Fox Foundation, Ericsson, and Georgia Tech. Our AI work runs on two tracks. We build A… ### [Run AI partner audit report: Specbee](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586637) State: opened | Updated: 2026-07-30 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: category::task, management, priority, priority::normal Description: ### Problem/Motivation Follow-up to: #3586639+s We want to make sure they were successfully onboarded to the right places. ### Proposed resolution Run the audit report for this partner after a week or two to look for gaps. ### Target date or deadline August 2026 ### Remaining tasks - [ ] Run report - [ ] Identify gaps - [ ] Email partner report ### [Onboard Gold/Silver AI partner: TEMPLATE](https://git.drupalcode.org/project/ai_initiative/-/work_items/3579583) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: unassigned | Labels: category::task, management, priority, priority::normal Description: ## Problem/Motivation **CREATING THIS AS A TEMPLATE THAT WILL BE COPIED FOR FUTURE ONBOARDING** Need to onboard new Gold/Silver partner: **PARTNER NAME** ## Proposed resolution Go through onboarding form and do what I can and then hand off to dev, marketing, UX, and QA teams as needed. ## Target date or deadline MONTH YEAR ## Remaining tasks - [ ] Create partner onboarding tab from template - [ ] Review onboarding form - [ ] Send legal and invoicing contacts to DA - [ ] Add to mailing lists - [ ] Add to private Slack channels (partners/contributors) - [ ] Add to public Slack channels (… ### [Add Gold/Silver AI partner to d.o pages: TEMPLATE](https://git.drupalcode.org/project/ai_initiative/-/work_items/3579591) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: unassigned | Labels: category::task, management, priority, priority::normal Description: ## Proposed resolution **CREATING THIS AS A TEMPLATE THAT WILL BE COPIED FOR FUTURE ONBOARDING** Follow-up to: #PARENT Update `/ai/partners` and `/ai/become-a-partner`. **Logo:** **100 word text:** ## Target date or deadline MONTH YEAR ## Tasks - [ ] Add logo/blurb to `/ai/partners` - [ ] Copy logo wall doc and add logo to logo wall doc - [ ] Save image with month and year, e.g. drupal-ai-partner-logo-wall-may-2026.png - [ ] Update `/ai/become-a-partner` with new logo wall image ### [Run AI partner audit report: TEMPLATE](https://git.drupalcode.org/project/ai_initiative/-/work_items/3579584) State: opened | Updated: 2026-07-30 | Author: drupalbot | Assigned: Kristen Pol (kepol) | Labels: category::task, management, priority, priority::normal Description: ### Problem/Motivation **CREATING THIS AS A TEMPLATE THAT WILL BE COPIED FOR FUTURE ONBOARDING** Follow-up to: #PARENT We want to make sure they were successfully onboarded to the right places. ### Proposed resolution Run the audit report for this partner after a week or two to look for gaps. ### Target date or deadline MONTH YEAR ### Remaining tasks - [ ] Run report - [ ] Identify gaps - [ ] Email partner report ### [Update AI partner badges to use Partner instead of Sponsor](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586636) State: opened | Updated: 2026-07-30 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: category::task, daRequest, design, priority::normal Description: ## Problem The AI initiative badges were created before we settled on the "Partner" naming (used to "Maker"). They show Sponsor now which doesn't capture the collaborative nature of the involvement with the initiative. ## Solution Update the badges to use "Partner" rather than "Sponsor": https://new.drupal.org/themes/contrib/bluecheese/images/badges/drupal_ai_founding_sponsor_badge.svg https://new.drupal.org/themes/contrib/bluecheese/images/badges/drupal_ai_gold_sponsor_badge.svg https://new.drupal.org/themes/contrib/bluecheese/images/badges/drupal_ai_silver_sponsor_badge.svg ### [Add Gold AI partner to d.o pages: Pantheon+Omedia](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586631) State: closed | Updated: 2026-07-30 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: category::task, management, priority, priority::normal Description: ## Proposed resolution Follow-up to: #3586630+s Update `/ai/partners` and `/ai/become-a-partner`. **Logo:** https://new.drupal.org/assets/2025-01/pantheon_3.png **100 word text:** Pantheon is the leading WebOps platform for Drupal, running more than 300,000 sites in the cloud and serving over 10 billion pageviews a month. Pantheon delivers the fastest, most secure platform for developing, testing, and hosting websites. Pantheon's collaboration tools enable web teams to iterate on their websites daily and launch new campaigns and features regularly. ## Target date or deadline July 202… ### [Onboard Gold AI partner: Pantheon+Omedia](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586630) State: closed | Updated: 2026-07-30 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: category::task, management, priority, priority::normal Description: ## Problem/Motivation Need to onboard new Gold partner: Pantheon+Omedia ## Proposed resolution Go through onboarding form and do what I can and then hand off to dev, marketing, UX, and QA teams as needed. ## Target date or deadline July 2026 ## Remaining tasks - [x] Create partner onboarding tab from template - [x] Add to mailing lists - [x] Add to private Slack channels (partners/contributors) - [x] Add to public Slack channels (marketing/UX/QA/ai-contrib) - [x] Add to dev meeting invites (planning/review/standups) - [n/a] Add to non-dev meeting invites (marketing/UX) - [x] Checked sup… ### [Partner contributor audit and cleanup August 2026](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586634) State: opened | Updated: 2026-07-30 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: category::task, management, priority::normal, state::accepted Description: ## Problem Some partners have contributors that no longer are helping but they don't notify the initiative managers to remove those contributors. ## Solution Periodically do an audit of partner contributors per partner and make a list of any contributors that should be offboarded in the regular process. This can happen every couple months or so. ## Tasks - Create list of contributors per partner - Check with each partner if any of those contributors should be removed - Add old contributors for next round of offboarding ### [Update AI partner logo wall with latest logos July 2026](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586635) State: opened | Updated: 2026-07-30 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: category::task, management, priority, priority::normal Description: ### Problem/Motivation Need to update the logo wall with latest partners: https://docs.google.com/drawings/d/1iBY0aPPf8JcoQNkBNkqDHQj0vkmUU7zQhu-nDJYT47M/edit ### Proposed resolution Cross-check the logo wall doc against the site, remove any old partners, and add any new partners. ### Target date or deadline July 2026 ### Remaining tasks - Add new partners to the doc - Remove old partners from the doc - Make image - Upload to `/ai/become-a-maker` ### AI usage (if applicable) - [ ] **AI Assisted Issue** This issue was generated with AI assistance, but was reviewed and refined by t… ### [Update AI partner logo wall with latest logos March 2026](https://git.drupalcode.org/project/ai_initiative/-/work_items/3580150) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: unassigned | Labels: category::task, management, priority, priority::normal Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Additional Collaborators: Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation Need to update the logo wall with latest partners: https://docs.google.com/drawings/d/1iBY0aPPf8JcoQNkBNkqDHQj0vkmUU7zQhu-nDJYT47M/edit Including: brainsum, itech4web, epam, integral vision, e-sepia, and any on the current site but not in the template Proposed resolution Cross-check … ### [Partner and contributor offboarding for July 2026](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586633) State: opened | Updated: 2026-07-30 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: category::task, management, priority::normal, state::accepted Description: ### Problem/Motivation There is some offboarding of contributors that needs to happen regularly. This issue is for July 2026. ### Proposed resolution Offboard contributors/partners as needed ### Target date or deadline July 2026 ### Remaining tasks - Determine who needs to be offboarded - Use the offboarding checklist - Go through all the steps - Create follow-up issues if necessary ### [Partner and contributor offboarding for June 2026](https://git.drupalcode.org/project/ai_initiative/-/work_items/3586553) State: opened | Updated: 2026-07-30 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: category::task, management, priority::normal Description: ### Problem/Motivation There is some offboarding of contributors that needs to happen regularly. This issue is for June 2026. ### Proposed resolution Offboard contributors/partners as needed ### Target date or deadline June 2026 ### Remaining tasks - Determine who needs to be offboarded - Use the offboarding checklist - Go through all the steps - Create follow-up issues if necessary --- MERGE REQUESTS (24h) --- (none) --- COMMITS (24h) --- (none) ======================================================================== ## [7] summariseModule:ai_integration_eca:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: AI Integration - ECA (machine name: ai_integration_eca) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Marcus Johansson (Marcus_Johansson)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
AI Integration - ECA
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Migrate the ECA agent to the Tools + ReAct architecture (create-only)](https://git.drupalcode.org/project/ai_integration_eca/-/work_items/3585017) State: opened | Updated: 2026-07-30 | Author: Marcus Johansson (Marcus_Johansson) | Assigned: unassigned | Labels: 2026sprint15, Road to 1.0.0, ai::inside, category::task Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !14 [Resolve "Migrate the ECA agent to the Tools + ReAct architecture (create-only)"](https://git.drupalcode.org/project/ai_integration_eca/-/merge_requests/14) | State: opened | Author: Marcus Johansson (Marcus_Johansson), 4481 diff lines Description: ### Problem/Motivation The ECA agent in the `agents` submodule (`Drupal\ai_integration_eca_agents\Plugin\AiAgent\Eca`) is still built on the **legacy `AiAgentBase` architecture**: a PHP plugin with the `#[AiAgent]` attribute that hand-rolls its own control flow and calls three YAML sub-prompts through `runSubAgent()`: - `prompts/eca/determineTask.yml` — triage step that classifies the request as `create` / `edit` / `info` / `fail`. - `prompts/eca/buildModel.yml` — builds the ECA model JSON (create or edit). - `prompts/eca/answerQuestion.yml` — answers questions about existing models / compon… --- MERGE REQUESTS (24h) --- (none) --- COMMITS (24h) --- (none) ======================================================================== ## [8] summariseModule:ai_provider_openai:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: OpenAI Provider (machine name: ai_provider_openai) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Marcus Johansson (Marcus_Johansson) [1], Paul Sheldrake (paulsheldrake) [1]". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
OpenAI Provider
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). (none) --- MERGE REQUESTS (24h) --- ### [add support for batch embeddings](https://git.drupalcode.org/project/ai_provider_openai/-/merge_requests/59) State: merged 2026-07-30 | Author: Paul Sheldrake (paulsheldrake) | Branch: 3568659-support-batched-embeddings | 284 diff lines Description: Closes #3568659 ### [Resolve #3612042 "Rate limits"](https://git.drupalcode.org/project/ai_provider_openai/-/merge_requests/80) State: merged 2026-07-30 | Author: Marcus Johansson (Marcus_Johansson) | Branch: 3612042-rate-limits | 129 diff lines Description: Closes #3612042 ### [Resolve #3613982 "Bug with gpt"](https://git.drupalcode.org/project/ai_provider_openai/-/merge_requests/81) State: merged 2026-07-30 | Author: Marcus Johansson (Marcus_Johansson) | Branch: 3613982-bug-with-gpt | 55 diff lines Description: Closes #3613982 --- COMMITS (24h) --- - [dd8a3c14](https://git.drupalcode.org/project/ai_provider_openai/-/commit/dd8a3c14067ea2ef4958c787da2fbc9ab950c016) add support for batch embeddings — Paul Sheldrake (2026-07-30T13:13:06.000+00:00) - [0a8f9670](https://git.drupalcode.org/project/ai_provider_openai/-/commit/0a8f9670dcc3e4c77a39f4181a933c699aea9b4e) Resolve #3612042 "Rate limits" — Marcus Johansson (2026-07-30T12:25:04.000+00:00) ======================================================================== ## [9] summariseModule:ai_provider_amazeeio:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: amazee.ai Private AI Provider (machine name: ai_provider_amazeeio) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Dan Lemon (dan2k3k4)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
amazee.ai Private AI Provider
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Data loss: Deleting or clearing items in a Search API index deletes data from other indexes sharing the same Vector DB collection](https://git.drupalcode.org/project/ai_provider_amazeeio/-/work_items/3586238) State: opened | Updated: 2026-07-30 | Author: Dezső Biczó (mxr576) | Assigned: Dan Lemon (dan2k3k4) | Labels: state::rtbc Description: ### Problem/Motivation When multiple Search API indexes share the same Vector Database (VDB) collection (table), index management operations (such as deleting items or clearing an index) cause silent and permanent data loss in other indexes sharing that collection: 1. **When individual items are deleted/re-indexed:** Deleting items with overlapping `drupal_entity_id`s (e.g., `node/1` exists in both Index A and Index B) from one index unintentionally deletes them from all other indexes in the vector database. 2. **When an index is cleared:** Running "Clear indexed data" on one index co… --- MERGE REQUESTS (24h) --- ### [feat: send X-Amazee-Client request tracking header](https://git.drupalcode.org/project/ai_provider_amazeeio/-/merge_requests/81) State: opened | Author: Dan Lemon (dan2k3k4) | Branch: client-request-tracking-header | 230 diff lines Description: Adds user-agent/version tracking for requests sent to amazee.ai. This helps attribute API traffic to the Drupal module and its specific version. Changes included: - Coverage: Adds tracking headers to all outbound calls, including `AmazeeClient::makeRequest()`, OpenAI SDK requests (via a PSR-18 wrapper), health/model config checks, and trial provisioning. - Version Handling: Pulls the module version via `extension.list.module`, falling back to `dev` for local/git checkouts. - Safety: Uses `getAllAvailableInfo()` instead of `getExtensionInfo()` to prevent unhandled exceptions on uninstalled m… --- COMMITS (24h) --- (none) ======================================================================== ## [10] summariseModule:ai_provider_azure:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Microsoft Azure AI (machine name: ai_provider_azure) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Jukka Huhta (jhuhta)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
Microsoft Azure AI
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). (none) --- MERGE REQUESTS (24h) --- ### [[#3552969] feat: Refactor AzureProvider to use OpenAiBasedProviderClientBase](https://git.drupalcode.org/project/ai_provider_azure/-/merge_requests/22) State: opened | Author: Jukka Huhta (jhuhta) | Branch: ai_provider_azure-3552969-1.2.x | 680 diff lines --- COMMITS (24h) --- (none) ======================================================================== ## [11] summariseModule:ai_vdb_provider_postgres:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Postgres VDB Provider (machine name: ai_vdb_provider_postgres) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Ignacio Pérez Puertas (djnash2002)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
Postgres VDB Provider
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). (none) --- MERGE REQUESTS (24h) --- ### [Issue #3586862 by ignacio.perez.puertas: Re-apply Attributes columns after clear+reindex cycle](https://git.drupalcode.org/project/ai_vdb_provider_postgres/-/merge_requests/24) State: opened | Author: Ignacio Pérez Puertas (djnash2002) | Branch: 3586862-clearreindex-drops-columns | 40 diff lines Description: Closes #3586862 --- COMMITS (24h) --- (none) ======================================================================== ## [12] summariseModule:mcp:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Model Context Protocol (machine name: mcp) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Alin Ameiroaie (aalin)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
Model Context Protocol
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Token Auth is not working](https://git.drupalcode.org/project/mcp/-/work_items/3584901) State: opened | Updated: 2026-07-30 | Author: drupalbot | Assigned: Giorgi Jibladze (jibla) | Labels: 2026Sprint14, 2026Sprint15, AI Initiative Sprint, ai::outside Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !52 [Resolve "Token Auth is not working"](https://git.drupalcode.org/project/mcp/-/merge_requests/52) | State: opened | Author: Alin Ameiroaie (aalin), 239 diff lines Description: >>> [!note] Migrated issue Reported by: [aalin](https://www.drupal.org/user/2941961) >>> Problem/Motivation There are actually 2 issues here: 1. Inside /admin/config/mcp , when you click on "Enable Token Auth" checkbox nothing happens. This is because #states selector on token_with_generation is not correctly set: 'visible' => [ ':input[name="enable_token_auth"]' => ['checked' => TRUE],], instead of 'visible' => [ ':input[name="auth_settings[enable_token_auth]"]' => ['checked' => TRUE],],2. Even when configured manually via config export/import, the … --- MERGE REQUESTS (24h) --- (none) --- COMMITS (24h) --- (none) ======================================================================== ## [13] summariseModule:ai_agents:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: AI Agents (machine name: ai_agents) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Bharat Kelotra (bharatkelotra), Marcus Johansson (Marcus_Johansson)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
AI Agents
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Add a way to set provider tags in the runner](https://git.drupalcode.org/project/ai_agents/-/work_items/3557418) State: closed | Updated: 2026-07-31 | Author: drupalbot | Assigned: unassigned | Labels: 2026Sprint15, AI Initiative Sprint, ai::inside, category::feature Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !226 >>> Problem/Motivation We need a way for any runner, meaning whomever starts an agent, to set extra tags to attach to the chat calls. When you are checking the llm events, you might want to look for something specific. So, when you start an agent, you should have the possibility to set what tags to add. This is only needed for config agents. It needs to propagate to subagents as well. Remaining tasks * Add a optional method called setProviderTags that can be set while running an … ### [Let an agent use a role when running a tool](https://git.drupalcode.org/project/ai_agents/-/work_items/3518167) State: opened | Updated: 2026-07-31 | Author: drupalbot | Assigned: unassigned | Labels: 2026Sprint14, 2026Sprint15, AI Initiative Sprint, ai::inside Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !87 >>> Problem/Motivation Currently the modus operandi is that the permissions checks that happens in tools, happens on the session that is running it. In AI Agents Explorer or the AI Assistants API, this means the user that triggers the query. There are however cases where agents should be completely autonomous or where they are triggered in queues/cron jobs, where there is no sessions attached. In those cases it should be possible for the person that sets up the agent to be able to… ### [Add limits on how often a tool can run](https://git.drupalcode.org/project/ai_agents/-/work_items/3547995) State: opened | Updated: 2026-07-31 | Author: drupalbot | Assigned: Joshua Fernandes (joshua1234511) | Labels: 2026Sprint14, 2026Sprint15, AI Initiative Sprint, ai::inside Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !224 >>> Problem/Motivation Right now we have to tell the system prompt how often it is allowed to use a specific tool. But there should also be a determenistic way, where if the tool gets stuck in a loop or searches to no awail in a RAG database for instance, we need to be able to programatically say how many times a tool can run. Proposed resolution Add a form value of how many times a tool can run. Add a form for setting the error message when this happens. If the tool has run tha… ### [Give a parent agent possibility to forward request as is](https://git.drupalcode.org/project/ai_agents/-/work_items/3550098) State: opened | Updated: 2026-07-30 | Author: drupalbot | Assigned: Marcus Johansson (Marcus_Johansson) | Labels: 2026Sprint15, AI Initiative Sprint, ai::inside, category::feature Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) >>> Problem/Motivation Many time a user is actually asking an orchestration agent just one instruction for one specific agent. Depending on how well the prompt is, there might be loss of information when this is forwarded to the subagent. If the parent knows that it should just forward the request as is, then it should be able to give this as a token instead. This helps both with consistency, but also costs and speed, since it will just output one token. Proposed resolution Create a token that th… ### [Make it possible to pick providers per agent](https://git.drupalcode.org/project/ai_agents/-/work_items/3535760) State: opened | Updated: 2026-07-30 | Author: drupalbot | Assigned: unassigned | Labels: 2026Sprint15, AI Initiative Sprint, ai::inside, category::feature Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !202 >>> Problem/Motivation Currently the agent is using the default Chat with Tools provider, which in most cases are good. But you might want to split this up, so you only for instance use a top of the line model for the overriding assistant, while each agent might be able to solve their results using some smaller models. Currently its solvable using events, but it should be part of the normal agent form. Since configurations, specifically temperature matters, we need a way to also … ### [Chatbot truncates 'search_string' context value while tool explorer does not](https://git.drupalcode.org/project/ai_agents/-/work_items/3547304) State: opened | Updated: 2026-07-30 | Author: drupalbot | Assigned: unassigned | Labels: category::bug, code, priority::normal, state::accepted Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !327 [Issue#3547304:chatbot-truncates-search-string-context-value-while-tool-explorer-does-not fixes](https://git.drupalcode.org/project/ai_agents/-/merge_requests/327) | State: opened | Author: Bharat Kelotra (bharatkelotra), 969 diff lines Description: >>> [!note] Migrated issue Reported by: [kevinquillen](https://www.drupal.org/user/317279) >>> Problem/Motivation I can't quite figure this one out, but the search_string pulled from context in the chatbot is truncated vs the tools explorer. The tools explorer passes the entire 'search string' for the RAG tool, but when used in the AI Chatbot its cut down to what looks like just the predicate or a couple of words. For example: Do you have content on severe snowstorms for sixth graders? is passed along as: severe snowstorms for sixth graders in the chatbot, but the tool explorer passes it a… ### [Chatbot repeats itself even after 'clear history' if 'return direct'](https://git.drupalcode.org/project/ai_agents/-/work_items/3547225) State: opened | Updated: 2026-07-30 | Author: drupalbot | Assigned: unassigned | Labels: category::bug, code, priority::normal, state::accepted Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !325 [Issue#3547225-chatbot-repeats-itself-even-after-clear-history-if-return-direct fixes](https://git.drupalcode.org/project/ai_agents/-/merge_requests/325) | State: opened | Author: Bharat Kelotra (bharatkelotra), 1669 diff lines Description: >>> [!note] Migrated issue Reported by: [kevinquillen](https://www.drupal.org/user/317279) >>> Problem/Motivation I am trying to create a simple chatbot that performs a search of the site and returns a list of formatted (with links) results. This is kind of difficult to do without using 'Return directly' from the search tool I made as the chatbot just repeats the same response over and over and over. If I disable return directly, I get unclear, unformatted results and odd conversation. If I use the tool explorer on the custom search tool, it provides a different answer with every prompt I… ### [Create implementation of ShortTermMemory](https://git.drupalcode.org/project/ai_agents/-/work_items/3546411) State: opened | Updated: 2026-07-30 | Author: drupalbot | Assigned: AKHIL BABU (AkhilBabu) | Labels: 2026Sprint15, AI Initiative Sprint, ai::inside, category::feature Description: >>> [!note] Migrated issue Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !183 >>> Problem/Motivation Short term memory is now available here: #3528730: Create ShortTermMemoryPlugin We should add an integration with it. Proposed resolution Add a parameter to the agent config to save the short term memory config. Add a subform integration for saving the configuration, while editing the AI Agent. Assume no ShortTermMemory by default. Trigger ShortTermMemory after the request event. --- MERGE REQUESTS (24h) --- ### [Draft: Resolve "Give a parent agent possibility to forward request as is"](https://git.drupalcode.org/project/ai_agents/-/merge_requests/326) State: opened | Author: Marcus Johansson (Marcus_Johansson) | Branch: 3550098-give-a-parent-agent-possibility-to-forward-request-as-is | 583 diff lines Description: Closes #3550098 ### [Issue #3535760: Provider picker](https://git.drupalcode.org/project/ai_agents/-/merge_requests/315) State: opened | Author: Marcus Johansson (Marcus_Johansson) | Branch: provider-model-picker | 796 diff lines Description: Provider picker but for 1.4.0, takes care of 1. Using the provider form element 2. Using the config schema element 3. Make sure to set back to default if a provider is uninstalled ### [Issue#3541337-module-agent-fails fixes.](https://git.drupalcode.org/project/ai_agents/-/merge_requests/324) State: opened | Author: Bharat Kelotra (bharatkelotra) | Branch: 3541337-module-agent-fails | 2277 diff lines Description: Closes #3541337 ### [Issue#3539557:error-message-when-using-the-ai-assistant-to-add-a-content-type fixes](https://git.drupalcode.org/project/ai_agents/-/merge_requests/323) State: opened | Author: Bharat Kelotra (bharatkelotra) | Branch: 3539557-error-message-when-using-the-ai-assistant-to-add-a-content-type | 1663 diff lines Description: Closes #3539557 --- COMMITS (24h) --- (none) ======================================================================== ## [14] summariseModule:tool:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Tool API (machine name: tool) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Abhisek Mazumdar (abhisekmazumdar) [1], Bryan Sharpe (b_sharpe) [1], Michael Lander (michaellander) [11]". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
Tool API
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Configuration-sourced input values fatal: getConfigurationValue() semantics are inverted](https://git.drupalcode.org/project/tool/-/work_items/3582959) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::bug, priority::normal, state::accepted Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !111 [Issue #3582959 by michaellander: Configuration-sourced input values fatal:...](https://git.drupalcode.org/project/tool/-/merge_requests/111) | State: opened | Author: Michael Lander (michaellander), 306 diff lines Description: ### Problem/Motivation The configuration source — one of the three input-value sources in the resolution chain (input > config > default) — has never worked, and has no test coverage. Three linked defects in `src/TypedInputsTrait.php`: 1. `getConfigurationValue()` (line ~440) inverts its `$return_typed_data` parameter: TRUE returns the plain value (`->getContextValue()`), FALSE returns the raw `Context` object — backwards from both the name and the docblock. 2. `getExecutableValue()` (line ~125) calls `$this->getConfigurationValue($name)->getValue()`. With the default `$return_typed_data = … ### [validateInputValue() only validates the first item of a multiple input](https://git.drupalcode.org/project/tool/-/work_items/3582960) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: Quick Win, category::bug, priority::normal, state::accepted Description: ### Problem/Motivation `src/TypedInputsTrait.php` (\~lines 337-341), inside `validateInputValue()`: ```php if ($definition->isMultiple() && is_array($value)) { foreach ($value as $item) { $item_definition = clone $definition; $item_definition->setMultiple(FALSE); return $this->validateInputValue($item_definition, $item); } } ``` The `return` inside the first loop iteration means items 2..n of a multiple input are never validated — invalid values in later positions pass validation and reach `doExecute()`. This is a validation bypass, which matters doubly now that the AI conne… ### [ToolBase::access() throws on invalid/missing input instead of returning forbidden](https://git.drupalcode.org/project/tool/-/work_items/3582961) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::bug, priority::normal, state::accepted Description: ### Problem/Motivation `ToolBase::access()` (src/Tool/ToolBase.php, \~line 201) calls `$this->getExecutableValues()`, which throws `\InvalidArgumentException` when validation fails. So checking access on a tool whose inputs are not yet valid produces an uncaught exception rather than an access result. `execute()` catches this exception; `access()` does not. Consequences: - Any consumer that checks access _before_ prompting for or validating values (the natural order) gets an exception where it expects an `AccessResult`. - Access checks should never throw on bad user input — a WSOD/stack tra… ### [Correct API signatures before the RC1 freeze (batch)](https://git.drupalcode.org/project/tool/-/work_items/3582962) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::bug, priority::normal, state::accepted Description: ### Problem/Motivation Five small signature/semantic mistakes that are one-to-five-line fixes today and BC breaks after RC1. Batched because none warrants its own issue. 1. **`getInputDefinition(): InputDefinitionInterface|InputException`** (src/TypedInputsInterface.php:55 and the trait): the exception is thrown, never returned. The union forces consumers to handle an impossible return. Fix: `: InputDefinitionInterface` + `@throws`. 2. **`ExecutableResult` nullable context values**: constructor and `success()`/`failure()` accept `?array $contextValues` but `getContextValues(): array` returns… ### [Prefix module-owned identifiers: alter hook, cache key, and 'text' data type ID](https://git.drupalcode.org/project/tool/-/work_items/3582963) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: Quick Win, category::bug, priority::normal, state::accepted Description: ### Problem/Motivation Three globally-namespaced identifiers are unprefixed. Identifier renames after RC1 break other modules, so this is a freeze item. 1. **Alter hook**: `TypedDataAdapterManager` (src/TypedData/Adapter/TypedDataAdapterManager.php:24) calls `$this->alterInfo('data_type_adapter_info')`, creating `hook_data_type_adapter_info_alter()`. Drupal convention requires module-prefixed alter hooks; a collision with another module implementing a generic "data type adapter" concept is plausible. 2. **Cache key**: same class, `setCacheBackend($cache_backend, 'data_type_adapter_plugins')`… ### [Rework the tool execution contract: result naming, concrete typing, and decoupling from core ExecutableInterface](https://git.drupalcode.org/project/tool/-/work_items/3582964) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::task, priority::normal, state::accepted Description: ### Problem/Motivation Three related contract problems that freeze at RC1: 1. **`ExecutableResultInterface` is misnamed.** It is implemented by the _tool plugin_ (`ToolInterface extends ExecutableResultInterface`) — it describes "a thing that carries an execution result" (`getResult()`, `getResultMessage()`, `getResultStatus()`, now `hasResult()`), not the result itself. Meanwhile `ExecutableResult` — the actual result — is a `final readonly` class implementing no interface. 2. **Concrete final classes are hard-typed into the frozen interface.** `getResult(): ExecutableResult` and (new since… ### [Implement getCacheContexts() or drop CacheableDependencyInterface from ToolInterface](https://git.drupalcode.org/project/tool/-/work_items/3582965) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::bug, priority::normal, state::accepted Description: ### Problem/Motivation `ToolInterface` extends `CacheableDependencyInterface`, but `ToolBase::getCacheContexts()` is a stub: ```php public function getCacheContexts() { // @todo Implement getCacheContexts() method. return []; } ``` Shipping a knowingly-unimplemented contract is worse than not implementing the interface — consumers caching tool results (render caching in explorers, AI response caching) will silently under-vary. Notably, a complete implementation already exists under the wrong name: `TypedInputsTrait::getCacheInputs()` (\~line 379) aggregates cache contexts from input de… ### [Annotate the API surface (@api/@internal) and add tool.api.php](https://git.drupalcode.org/project/tool/-/work_items/3582966) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::task, priority::normal, state::accepted Description: ### Problem/Motivation Zero files in `src/` carry `@api` or `@internal` markers, and no `tool.api.php` exists. At RC1 the entire surface freezes _implicitly_ — including subsystems that were never meant as public API. Annotation is the only lever for post-1.0 refactoring freedom, and project-application reviewers expect `tool.api.php` for the alter hooks. Surface that needs an explicit decision (grown since beta2): - **Stable API**: `ToolInterface`, `ToolBase`, `#[Tool]` attribute, `ExecutableResult`, `FormattedExecutableResult`, `InputDefinitionInterface` + definition classes, `ToolOperati… ### [Harden the 'administer tool' permission](https://git.drupalcode.org/project/tool/-/work_items/3582967) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::task, priority::normal, state::accepted Description: ### Problem/Motivation `tool.permissions.yml` is the bare minimum: ```yaml administer tool: title: 'Administer tool' ``` This permission gates the Tool Explorer routes including `/admin/config/tool/explorer/{plugin_id}/execute` — i.e. **execution of arbitrary Tool plugins** (entity CRUD and anything else tools can do). A permission with that power must declare `restrict access: TRUE` and warn in its description; its absence is a near-certain security-review flag for the stable-release/security-coverage application. ### Proposed resolution ```yaml administer tool: title: 'Administer to… ### [Tool Explorer execute form: masked exception on access denial, duplicate messages, no validation pass](https://git.drupalcode.org/project/tool/-/work_items/3582968) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::bug, priority::normal, state::accepted Description: ### Problem/Motivation Three defects in the execute flow (`modules/tool_explorer/src/Form/ToolExecuteForm.php` + `src/Form/ExecuteToolPluginForm.php`): 1. **Masked internal exception on access denial.** `ExecuteToolPluginForm::submitConfigurationForm()` checks access and messages the denial — then `ToolExecuteForm::submitForm()` calls `$tool->getResult()` on a tool that never executed, which throws `BadMethodCallException`; the generic catch shows the admin _"Error executing tool: The action result cannot be retrieved until the action ::execute() method has been called."_ alongside the real … ### [Tool Explorer RC cleanup: render arrays, dead cache tag, menu placement, first tests](https://git.drupalcode.org/project/tool/-/work_items/3582969) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::task, priority::normal, state::accepted Description: ### Problem/Motivation Housekeeping batch for the explorer before its URL and behavior freeze at RC1: 1. **Hand-built markup** in `ToolExplorerController` (\~lines 204-248): `'#markup' => '' . Yaml::encode(...) . ''` and literal `''` strings. `Xss::filterAdmin()` mangles any ` status_messages`-style elements. 2. **Dead cache tag**: `'#cache' => ['tags' => ['tool_list']]` (\~line 100) — nothing in the codebase ever invalidates `tool_list`. Drop it or wire real invalidation to plugin-definition cache clears. 3. **Menu/IA mismatch**: menu link parent is `system.admin_config_development` but the… ### [Drush hardening: --uid default, silently dropped inputs, exit codes](https://git.drupalcode.org/project/tool/-/work_items/3582970) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::bug, priority::normal, state::accepted Description: ### Problem/Motivation Three behaviors in `src/Drush/Commands/` that become contract at RC1: 1. **`tool:run --uid` defaults to `1`** (ToolRunCommand.php:58,67): every tool runs as the superuser by default, making `checkAccess()` effectively always-TRUE and training users to bypass the access layer. Account switching itself is implemented correctly — the default is the problem. 2. **Unparseable `--input` silently dropped** (`parseInputValues()`, \~lines 187-229): a value that is neither valid JSON nor `key=value` is ignored with no warning; scalar JSON (`--input=5`) also falls through silentl… ### [Make violation messages translatable and stop surfacing raw exception text](https://git.drupalcode.org/project/tool/-/work_items/3582971) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::bug, priority::normal, state::accepted Description: ### Problem/Motivation `src/TypedInputsTrait.php` builds user-surfaced text with `sprintf()`, bypassing translation: - \~line 205: `"The %s context is not a valid context."` - \~line 268: locked-input exception message - \~line 310: `'Input %s: %s'` violation prefix - \~line 349: `'The %s input must be an entity.'` - \~line 364: `'The %s input is invalid: %s'` These surface to end users via form errors, result messages, Drush output, and AI responses. Additionally, \~line 364 concatenates raw `$e->getMessage()` into the violation, and `ToolBase::execute()`'s catch-all does the same into fa… ### [Emit richer JSON Schema: map remaining constraints and type formats](https://git.drupalcode.org/project/tool/-/work_items/3582972) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::feature, priority::normal, state::accepted Description: ### Problem/Motivation The emitted input schemas omit several constraints and formats that tools already declare, so LLM/MCP consumers get weaker contracts than the typed-data layer enforces — costing correction round-trips. Constraint mapping is centralized in `ContextDefinitionNormalizer::getNormalizationSchema()` (currently: FixedValue, Choice, AllowedValues, PluginExists, Length, Range) and applies on both scalar paths (10.5 legacy normalizer / 11.1+ core normalizers — the selection bug was fixed in the beta3 cycle, and previous-major CI now tests both). Overlaps with #3582943 "Deliverab… ### [Extend input coercion for unambiguous LLM value shapes](https://git.drupalcode.org/project/tool/-/work_items/3582973) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::feature, priority::normal, state::accepted Description: ### Problem/Motivation `InputTypeCoercionSubscriber` (priority 50) currently handles list-wrapping, boolean strings, and numeric strings. Real LLM traffic produces more recoverable shapes; each currently costs a validation-failure round-trip (failure message + `input_schema` echo → model retry). Principle: **coerce only when unambiguous** — anything doubtful stays for validation, whose correction loop already works. Nested coverage is free via the recursive subscriber's child dispatch. ### Proposed resolution (priority order) | \# | Gap | Fix | |----|-----|-----| | B1 | JSON _string_ for ma… ### [Complete kernel coverage of the typed input/output traits and definition pipeline](https://git.drupalcode.org/project/tool/-/work_items/3582974) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::task, priority::normal, state::accepted Description: ### Problem/Motivation Every serious bug found this release cycle — the `getOutputValue()` throw on optional outputs (#3582954), the multi-value validation early-return, the configuration-source fatal, the coercion regressions — lived in `TypedInputsTrait`/`TypedOutputsTrait`, in paths with no test coverage. These traits are the API being frozen at RC1; untested frozen behavior is behavior we cannot safely refactor later. **Scope note:** the RC1 fix issues each carry their own tests — config-source precedence (config-value issue), multi-value item validation (validation issue), access-on-inv… ### [checkRequirements() is declared on the frozen interface but never called anywhere](https://git.drupalcode.org/project/tool/-/work_items/3582975) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::bug, priority::normal, state::accepted Description: ### Problem/Motivation `ToolInterface::checkRequirements(): void` (throws `RequirementsException`) is implemented as a no-op default in `ToolBase` and overridable by tools — but a code search shows **no call site anywhere**: not in `execute()`, not in the invokers (AI connector, MCP bridge, Drush), not in schema/derivative building. Design intent (recorded here so the implementation matches it): the method exists for tools with soft cross-module dependencies — a tool that should not be _usable_ while some other module is uninstalled, but should remain _discoverable_ so site builders can see … ### [Filter workflow-only tools from one-shot CLI invokers](https://git.drupalcode.org/project/tool/-/work_items/3582977) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: category::feature, priority::normal, state::accepted Description: ### Problem/Motivation Some tools only make sense inside a multi-call workflow where entity handles carry state between calls (AI conversations, MCP sessions). In a one-shot CLI process they are pointless or unusable: - A tool that mutates a passed entity without persisting it (field_set_value, entity_stub, entity_revision_add) produces in-memory state whose only consumer is a next call that never comes. - A tool whose only output is an entity (entity_load) produces a handle with nothing to pass it to. - Tools with entity _inputs_ but real side effects (entity_save, entity_delete) are useful… ### [Track Drupal core CLI alignment: metadata mapping, typed-outputs advocacy, future CLI invoker](https://git.drupalcode.org/project/tool/-/work_items/3582976) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: No Estimation Available, category::plan, priority::normal Description: ### Problem/Motivation External comparison feedback between Tools API and the emerging Drupal core CLI initiative confirms the module's metadata model is the shape core is being asked to adopt: 1. **Operation kind** (`ToolOperation`: explain/read/transform/trigger/ write) — straightforward for core CLI to model as an attribute. 2. **Destructive flag** — related but distinct from operation kind (a write is not necessarily destructive); equally easy to model. 3. **Typed outputs** — the most significant piece for AI use: structured, named, typed return values instead of a stdout string and exit… ### [[META] Path to 1.0.0-rc1](https://git.drupalcode.org/project/tool/-/work_items/3582978) State: opened | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: No Estimation Available, category::meta, priority::normal Description: ### 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:… ### [Entity handle descriptions are HTML-escaped in LLM-facing schemas](https://git.drupalcode.org/project/tool/-/work_items/3582958) State: closed | Updated: 2026-07-31 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !110 [Resolve "Entity handle descriptions are HTML-escaped in LLM-facing schemas"](https://git.drupalcode.org/project/tool/-/merge_requests/110) | State: merged 2026-07-31 | Author: Michael Lander (michaellander), 73 diff lines Description: **Problem/Motivation** `EntityHandleTransformer::transformInputDefinition()` and `::transformOutputDefinition()` assemble the handle description as a plain string, then wrap it in `new TranslatableMarkup('@description', ['@description' => $description])`. The `@` placeholder is run through `Html::escape()` when the markup is rendered, so any entity-typed input or output whose label/description contains an apostrophe, quote, ampersand, or angle bracket ships mangled text to the model on **every invoker path** (AI connector and MCP alike). Live example — tool_belt's send_email `token_data` inp… ### [A tool whose input stage fails never executes, and external getResult() calls then throw BadMethodCallException, masking the error feedback](https://git.drupalcode.org/project/tool/-/work_items/3582957) State: closed | Updated: 2026-07-30 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !109 [Resolve "A tool whose input stage fails never executes, and external getResult() calls then throw BadMethodCallException, masking the error feedback"](https://git.drupalcode.org/project/tool/-/merge_requests/109) | State: merged 2026-07-30 | Author: Michael Lander (michaellander), 271 diff lines Description: **Problem/Motivation** When an LLM sends an invalid input value (e.g. a text format that is not a valid choice on the site), the connector's input stage fails before the wrapped Tool plugin ever executes. The connector handles this gracefully — `errorMessage` is set and `getStructuredOutput()` returns a failure with the input schema so the LLM can self-correct. However, consumers that read the tool's result directly are not protected: ai_agents' image collection loop (`AiAgentEntityWrapper`) calls `getPluginInstance()->getResult()` without checking `hasResult()`. On an un-executed tool this … ### [Anthropic rejects tool schemas: nullable optional inputs render an object under "type"](https://git.drupalcode.org/project/tool/-/work_items/3582956) State: closed | Updated: 2026-07-30 | Author: Michael Lander (michaellander) | Assigned: unassigned | Labels: Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !108 [Resolve "Anthropic rejects tool schemas: nullable optional inputs render an object under "type""](https://git.drupalcode.org/project/tool/-/merge_requests/108) | State: merged 2026-07-30 | Author: Michael Lander (michaellander), 120 diff lines Description: **Problem/Motivation** Running any agent whose tools have optional inputs against an Anthropic model fails immediately with: > Error invoking model response: tools.N.custom.input_schema: JSON schema is > invalid. It must match JSON Schema draft 2020-12 Two shapes are produced, both for nullable/optional inputs, both invalid because `type` must be a string or array of strings: 1. `"type": {"anyOf": ["array", "null"]}` — the tool module's normalizer correctly emits `type: ["array", "null"]`, but the AI module's `ToolsPropertyInput::setType()` rewrites any numeric type array into an … ### [tool_ai_connector throws `BadMethodCallException` when the tool has not executed](https://git.drupalcode.org/project/tool/-/work_items/3582948) State: closed | Updated: 2026-07-30 | Author: Ajit Shinde (ajits) | Assigned: unassigned | Labels: category::bug, state::needsReview Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !107 [Resolve "tool_ai_connector throws `BadMethodCallException` when the tool has not executed"](https://git.drupalcode.org/project/tool/-/merge_requests/107) | State: merged 2026-07-30 | Author: Michael Lander (michaellander), 69 diff lines Description: `Drupal\tool_ai_connector\Plugin\AiFunctionCall\ToolPluginBase::getReadableOutput()` recomputes its output live from the underlying `tool` plugin instance every time it is called, via: ```php // tool_ai_connector/src/Plugin/AiFunctionCall/ToolPluginBase.php elseif ($this->getPluginInstance()?->getResult()?->isSuccess()) { ``` The underlying tool's result (`Drupal\tool\Tool\ToolBase::$result`) is a typed property with **no default value**, so it is *uninitialized* — not `null` — until `execute()` runs. `ToolBase::getResult()` **throws `\BadMethodCallException`** in that state rather than retu… ### [[AI Connector] - Context Data missing after execute](https://git.drupalcode.org/project/tool/-/work_items/3576586) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: unassigned | Labels: automation::error, category::bug, code, priority::normal Description: >>> [!note] Migrated issue Reported by: [b_sharpe](https://www.drupal.org/user/2512258) Related to !76 >>> Problem/Motivation When using a tool as a function call, no context values exist after execute. This can cause a ContextException when trying to get context values. It looks like the issue is a result of the base class signature changing, but the child is just settings values for input when we actually need both. ### [MapDefinitionNormalizer and ContextDefinitionNormalizer break REST serialization (same as #3568588)](https://git.drupalcode.org/project/tool/-/work_items/3582939) State: closed | Updated: 2026-07-30 | Author: Stephan Huber (stmh) | Assigned: unassigned | Labels: AI Initiative Sprint, AI Innovation, state::rtbc Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !95 [Issue #3582939: Fix getSupportedTypes() in MapDefinitionNormalizer and...](https://git.drupalcode.org/project/tool/-/merge_requests/95) | State: merged 2026-07-30 | Author: Abhisek Mazumdar (abhisekmazumdar), 189 diff lines Description: ### Steps to reproduce 1. Install Drupal 11.x with the REST module enabled and a content entity exposed via a `ResourceBase` plugin that calls `$serializer->normalize($entity, 'json')` (e.g. any custom REST resource that returns entities as normalized arrays). 2. Enable the Tool module (verified on 1.0.0-alpha9, 1.0.0-beta1, and 1.0.x-dev). 3. Request the REST endpoint and inspect the JSON response — or reproduce directly via `drush php:eval`: ```php $node = \Drupal::entityTypeManager()->getStorage('node')->load(1); print_r(\Drupal::service('serializer')->normalize($node, 'json')); … --- MERGE REQUESTS (24h) --- ### [Issue #3576586 by b_sharpe: Set parent context data as well as input.](https://git.drupalcode.org/project/tool/-/merge_requests/76) State: merged 2026-07-30 | Author: Bryan Sharpe (b_sharpe) | Branch: 3576586-ai-connector-- | 284 diff lines Description: Closes #3576586 --- COMMITS (24h) --- - [a255809b](https://git.drupalcode.org/project/tool/-/commit/a255809b51ff1bd040c0451f79f6617f7feed188) Resolve "Entity handle descriptions are HTML-escaped in LLM-facing schemas" — Michael Lander (2026-07-31T04:11:06.000+00:00) - [721afea5](https://git.drupalcode.org/project/tool/-/commit/721afea590593edbeadb1efb194ee9147b20c02a) Make LegacyTypedDataNormalizer selectable on pre-11.1 cores so scalar schemas keep their types. — Michael Lander (2026-07-30T16:46:03.000-06:00) - [213c6c9e](https://git.drupalcode.org/project/tool/-/commit/213c6c9ede4327f23c4edf3f25ba0901deaef6f7) Restore Drupal 10 compatibility: procedural hook bridge, annotation test metadata, advisory previous-major phpstan. — Michael Lander (2026-07-30T16:36:50.000-06:00) - [77233c15](https://git.drupalcode.org/project/tool/-/commit/77233c151bd732b2d51db3074af6da6c64c405b5) Run previous-major CI jobs on PHP 8.3 to satisfy the module's PHP requirement. — Michael Lander (2026-07-30T16:18:53.000-06:00) - [9f26cc00](https://git.drupalcode.org/project/tool/-/commit/9f26cc00670bbf9eeff6c4894075eba80c5ff339) Enable previous-major (Drupal 10.5) testing in CI. — Michael Lander (2026-07-30T16:10:14.000-06:00) - [d98db2e0](https://git.drupalcode.org/project/tool/-/commit/d98db2e0af8d31206ed98f951470b65f1b5dc90d) Align tool_explorer core requirement with the other modules. — Michael Lander (2026-07-30T16:08:13.000-06:00) - [2a565c76](https://git.drupalcode.org/project/tool/-/commit/2a565c7699423eac5c1ade8d11254623d02ac621) Raise minimum core requirement to Drupal 10.5 in the tool_test module. — Michael Lander (2026-07-30T16:07:35.000-06:00) - [5dad7026](https://git.drupalcode.org/project/tool/-/commit/5dad7026ae3a0d7cc2b47175f4d55262b7f487dd) Raise minimum core requirement to Drupal 10.5. — Michael Lander (2026-07-30T16:03:03.000-06:00) - [988dee65](https://git.drupalcode.org/project/tool/-/commit/988dee6551014b60186a6d26731e11190d2d79ea) Resolve "A tool whose input stage fails never executes, and external getResult() calls then throw BadMethodCallException, masking the error feedback" — Michael Lander (2026-07-30T21:44:35.000+00:00) - [02f61b2b](https://git.drupalcode.org/project/tool/-/commit/02f61b2bb8aa70e7030dff9748640a6efa9e066f) Resolve "Anthropic rejects tool schemas: nullable optional inputs render an object under "type"" — Michael Lander (2026-07-30T21:35:52.000+00:00) - [f62ac921](https://git.drupalcode.org/project/tool/-/commit/f62ac9213ed082921f391dde4cc4dd5d1b463c62) Resolve "tool_ai_connector throws `BadMethodCallException` when the tool has not executed" — Michael Lander (2026-07-30T20:24:21.000+00:00) - [eaa3596f](https://git.drupalcode.org/project/tool/-/commit/eaa3596fd3cb43cb9f543df5909612d74cc0bdda) Issue #3576586 by b_sharpe: Set parent context data as well as input. — Bryan Sharpe (2026-07-30T19:46:57.000+00:00) - [a663a313](https://git.drupalcode.org/project/tool/-/commit/a663a313fc5950b89e7a628fbd77b2c75a336d77) Issue #3582939: Fix getSupportedTypes() in MapDefinitionNormalizer and... — Abhisek Mazumdar (2026-07-30T18:10:02.000+00:00) ======================================================================== ## [15] summariseModule:canvas:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Drupal Canvas (machine name: canvas) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: **** (project_19391_bot_17a61b0edeafd5a3db3e8b2462b6c010), **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Adam G-H (phenaproxima), Ben Mullins (bnjmnm), Bálint Kléri (balintbrews) [1], Canvas version bot [2], David Bravo (davidbp), Harumi Jang (hooroomoo), Jeremy Chinquist (jjchinquist), Juan Correa (jucs7) [1], Kunal Sachdev (kunal.sachdev), Lionel Enkaoua (heyyo), mariosr, Rajab Natshah (RajabNatshah), Tekla Aivazashvili (aivazashvilit), Wim Leers (wimleers) [1], wotnak [1]". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
Drupal Canvas
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [RTL support for Canvas visual editor (logical CSS properties, Radix DirectionProvider, autocomplete magnifier, and Undo/Redo timelines)](https://git.drupalcode.org/project/canvas/-/work_items/3591840) State: opened | Updated: 2026-07-31 | Author: Lionel Enkaoua (heyyo) | Assigned: unassigned | Labels: Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1453 [Draft: fix: #3591840 RTL support for Canvas visual editor (logical CSS properties, Radix DirectionProvider, autocomplete magnifier, and Undo/Redo timelines)](https://git.drupalcode.org/project/canvas/-/merge_requests/1453) | State: opened | Author: Lionel Enkaoua (heyyo), 129 diff lines Description: When running Drupal Canvas in an RTL (Right-to-Left) language environment (such as Hebrew or Arabic), the visual editor shell UI components (sidebars, panels, toolbars, and icons) remain LTR-aligned and do not display in the correct RTL layout flow. We identified and tested the following fixes to achieve full visual editor RTL compatibility: ### 1. Physical Properties in Compiled CSS The compiled React application stylesheet (`ui/dist/assets/index.css`) uses physical margin/padding/border CSS rules instead of logical properties. * **The Fix:** Convert all occurrences of: * `margin-right:… ### [Translatable props missing from TMGMT form when component instances cannot be auto-updated to active version](https://git.drupalcode.org/project/canvas/-/work_items/3591875) State: opened | Updated: 2026-07-31 | Author: Kunal Sachdev (kunal.sachdev) | Assigned: unassigned | Labels: category::bug, priority::normal, state::needsWork, translation Description: **Overview** When using TMGMT to translate a content entity with a component_tree field, props for components on older pages may be entirely absent from the translation review form. This affects pages where component instances are pinned to a version that predates `string_shape` being retained in `derived_schema_metadata`, and where `canUpdate()` returns FALSE (because the active version changed prop storage formats). ### [Strengthen AutoSaveManager to generate stable hashes](https://git.drupalcode.org/project/canvas/-/work_items/3591785) State: opened | Updated: 2026-07-31 | Author: Feliksas Mazeikis (f.mazeikis) | Assigned: Feliksas Mazeikis (f.mazeikis) | Labels: 1.x-dev, auto-save, autoSave, backend Description: When AutoSaveManager normalizes entity, it is doing so without using strictly casted values. The set of normalized entity calues is used for `data_hash` hash computation. As the contents of the normalized entities are not strictly casted, the resulting hashes cannot be relied upon. The aim of this issue is to strengthen, simplify and standardise normalization and hashing processes happening in AutoSaveManager. ### [Dependency Dashboard](https://git.drupalcode.org/project/canvas/-/work_items/3591657) State: opened | Updated: 2026-07-31 | Author: **** (project_19391_bot_cb443e60680723bba08a5351bf595251) | Assigned: unassigned | Labels: projectManagement Description: This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more. ## Repository Problems Renovate tried to run on this repository, but found these problems. - ⚠️ WARN: Failed to set branch status - ⚠️ WARN: No github.com token has been configured. Skipping release notes retrieval - ⚠️ WARN: Rate limit exceeded for api.github.com, as no hostRules set for this host. Please set a GITHUB_COM_TOKEN - ⚠️ WARN: No tool releases found. ## Deprecations / Replacements > ⚠️ **Warning** > The foll… ### [CLI push includes unsupported label property for content templates](https://git.drupalcode.org/project/canvas/-/work_items/3591899) State: closed | Updated: 2026-07-30 | Author: Bálint Kléri (balintbrews) | Assigned: unassigned | Labels: cliTool Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1451 [fix(CLI Tool): #3591899 CLI push includes unsupported label property for content templates](https://git.drupalcode.org/project/canvas/-/merge_requests/1451) | State: merged 2026-07-30 | Author: Bálint Kléri (balintbrews), 91 diff lines Description: The CLI cannot create content templates because it includes `label` in the POST request, but the server schema does not accept this property. Keep `label` in the local authored file, but omit it from the create request. Add a test confirming that the request does not contain `label`. ### [Automatically create components when themes are installed](https://git.drupalcode.org/project/canvas/-/work_items/3591898) State: opened | Updated: 2026-07-30 | Author: Adam G-H (phenaproxima) | Assigned: unassigned | Labels: Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1450 [Generate components when extensions are installed, even if syncing config](https://git.drupalcode.org/project/canvas/-/merge_requests/1450) | State: opened | Author: Adam G-H (phenaproxima), 209 diff lines Description: With certain narrow exceptions, site templates -- and recipes more broadly -- should not be in the business of shipping `component` config entities. Component entities are ill-suited to be included in recipes because they are, fundamentally, **non-transferable**. They are the version history of a component as it has existed _in a particular site_. But a recipe is not a snapshot of a particular site; it is a generic package of configuration and setup steps. Up until now, Drupal CMS has worked around this by including the component entities in recipes' configuration. This has proven to be comp… ### [Canvas CLI sync fails for media and link props in global regions](https://git.drupalcode.org/project/canvas/-/work_items/3591897) State: closed | Updated: 2026-07-30 | Author: wotnak | Assigned: wotnak | Labels: cliTool Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1446 [fix(CLI Tool): #3591897 Canvas CLI sync fails for media and link props in global regions](https://git.drupalcode.org/project/canvas/-/merge_requests/1446) | State: merged 2026-07-30 | Author: wotnak, 515 diff lines Description: `canvas push` fails for global regions that contain media-image or link props. The push is rejected with schema validation errors such as: ``` elements..props.image.src: Invalid input: expected string, received undefined elements..props.link.url: expected string, received object ``` Region props like image `src` and link `url` are computed server-side and exposed only through the `inputs_resolved` property. The region path never carries them: 1. `PageRegion::normalizeForClientSide()` returns `getComponentTree()->getValue()`, which excludes the computed `inputs_resolved`. The CLI receives on… ### [Error message for empty value is displayed for select props even when they're not required](https://git.drupalcode.org/project/canvas/-/work_items/3591894) State: opened | Updated: 2026-07-30 | Author: mariosr | Assigned: unassigned | Labels: Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1440 [fix(UI): #3591894 Error message for empty value is displayed for select props...](https://git.drupalcode.org/project/canvas/-/merge_requests/1440) | State: opened | Author: mariosr, 13 diff lines Description: When a select prop value is set as - None - an error message is displayed even when the prop is not set as required. Steps to reproduce: 1. Insert a component with enum options that is not set as required 2. Select the option - None - Expected result: - No error is displayed Actual result: - Error message is displayed. E.g. data must be string Proposed solution: - On function shouldSkipPropValidation from componentFieldValidation.ts, the validation on line 146 is checking if the selected option is '' but it should also check if it's null or undefined. If so, and the prop is not required, t… ### [Canvas AI: Add Tools dropdown to chat UI](https://git.drupalcode.org/project/canvas/-/work_items/3591856) State: opened | Updated: 2026-07-30 | Author: AKHIL BABU (AkhilBabu) | Assigned: David Bravo (davidbp) | Labels: 1.x-dev, 2026Sprint15, AI Initiative Sprint, ai Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1447 [Draft: Resolve "Canvas AI: Add Tools dropdown to chat UI"](https://git.drupalcode.org/project/canvas/-/merge_requests/1447) | State: opened | Author: David Bravo (davidbp), 555 diff lines Description: ## Background — how Canvas AI works today The Canvas AI chat is an **orchestrator system**. Every message goes first to a single orchestrator agent. The orchestrator reads the message, infers the intent, and launches the matching sub-agent: - "Build me a landing page" → orchestrator → page-builder sub-agent - "Create a React component" → orchestrator → component sub-agent - "Write a title / meta description" → orchestrator → the relevant sub-agent The routing is implicit — the user never chooses which sub-agent runs; the orchestrator decides on every turn. Roadmap: https://git.drupalcode.o… ### [Automate MR review using PHPCS: disallow `\Drupal::service('something')`, require `\Drupal::service(Something::class)` whenever possible, with automatic fixing](https://git.drupalcode.org/project/canvas/-/work_items/3581133) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: Adam G-H (phenaproxima), Wim Leers (wimleers) | Labels: AI-accelerated, Chicago2026, DX (Developer Experience), Novice Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1297 [#3581133: Automate MR review using PHPCS: disallow `\Drupal::service('something')`, require `\Drupal::service(Something::class)` whenever possible, with automatic fixing](https://git.drupalcode.org/project/canvas/-/merge_requests/1297) | State: merged 2026-07-30 | Author: Wim Leers (wimleers), 6040 diff lines Description: >>> [!note] Migrated issue Reported by: [wim leers](https://www.drupal.org/user/99777) Related to !797 >>> Overview :pray: Let's use the `FQCN::class` wherever we can. Reduces magic, makes it easier to navigate & understand these tests. — yours truly at https://git.drupalcode.org/project/canvas/-/merge_requests/651#note_727491 Proposed resolution Automate this feedback. User interface changes None. ### [Canvas AI: Improve the schema of the place_components tool](https://git.drupalcode.org/project/canvas/-/work_items/3591881) State: closed | Updated: 2026-07-30 | Author: AKHIL BABU (AkhilBabu) | Assigned: unassigned | Labels: 1.x-dev, 2026Sprint15, AI Initiative Sprint, ai Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1439 [#3591881 Canvas AI: Improve the schema of the place_components tool](https://git.drupalcode.org/project/canvas/-/merge_requests/1439) | State: merged 2026-07-30 | Author: Juan Correa (jucs7), 1030 diff lines Description: ## Summary `place_components` (https://git.drupalcode.org/project/canvas/-/work_items/3591811) is merged, but its schema is as basic as it gets: one string argument, `component_structure_yaml`, holding an entire YAML document. Every part of the placement envelope — the `operations` root, the `target`, the `placement` enum, the `reference_uuid` — is taught to the model in prose and only discovered to be wrong after the call arrives. Replace it with the shape the sibling `edit_components` tool (https://git.drupalcode.org/project/canvas/-/work_items/3591812) already ships: an `operations` list … ### [Canvas AI: Add an Agents & Tools settings form to select the main agent and chat Tools](https://git.drupalcode.org/project/canvas/-/work_items/3591882) State: opened | Updated: 2026-07-30 | Author: AKHIL BABU (AkhilBabu) | Assigned: Tekla Aivazashvili (aivazashvilit) | Labels: 1.x-dev, 2026Sprint15, AI Initiative Sprint, ai Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !1445 [Issue #3591882: Add an Agents & Tools settings form.](https://git.drupalcode.org/project/canvas/-/merge_requests/1445) | State: opened | Author: Tekla Aivazashvili (aivazashvilit), 510 diff lines Description: ## Summary Add an **Agents & Tools** tab to the Canvas AI settings area where an admin picks the **main agent** (single select) and the **Tools** offered in the chat (checkboxes), and expose the selected Tools to the frontend as `drupalSettings.canvas.ai.tools`. The form, its route and its config all live in `canvas_dev_ai`. Nothing in `canvas_ai` changes. ## Why In the revamped flow, agent selection is config-driven and explicit — the user picks the agent for the turn from a dropdown instead of an orchestrator inferring it (roadmap item 2: https://git.drupalcode.org/project/canvas/-/work_… --- MERGE REQUESTS (24h) --- ### [#3591875: "Translatable props missing from TMGMT form when component instances cannot be auto-updated to active version"](https://git.drupalcode.org/project/canvas/-/merge_requests/1418) State: opened | Author: Kunal Sachdev (kunal.sachdev) | Branch: 3591875-translatable-props-missing-from-tmgmt-form-when-component-instances-cannot-be-auto-updated-to-active-version | 909 diff lines Description: AI-Generated: Yes (Used Github Copilot(Claude Sonnet 4.6) for the solution and test coverage). ### [chore(deps): update dependency cspell to v10](https://git.drupalcode.org/project/canvas/-/merge_requests/1273) State: opened | Author: **** (project_19391_bot_cb443e60680723bba08a5351bf595251) | Branch: renovate/major-cspell-monorepo | 13 diff lines Description: This MR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [cspell](https://cspell.org/) ([source](https://github.com/streetsidesoftware/cspell/tree/HEAD/packages/cspell)) | [`^9.2.0` → `^10.0.0`](https://renovatebot.com/diffs/npm/cspell/9.7.0/10.0.1) | ![age](https://developer.mend.io/api/mc/badges/age/npm/cspell/10.0.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/cspell/9.7.0/10.0.1?slim=true) | > :exclamation: **I… ### [chore(deps): update dependency @eslint/compat to v2](https://git.drupalcode.org/project/canvas/-/merge_requests/1306) State: opened | Author: **** (project_19391_bot_cb443e60680723bba08a5351bf595251) | Branch: renovate/eslint-compat-2.x | 13 diff lines Description: This MR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@eslint/compat](https://github.com/eslint/rewrite/tree/main/packages/compat#readme) ([source](https://github.com/eslint/rewrite/tree/HEAD/packages/compat)) | [`^1.3.1` → `^2.0.0`](https://renovatebot.com/diffs/npm/@eslint%2fcompat/1.4.1/2.1.0) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@eslint%2fcompat/2.1.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confide… ### [chore(deps): update dependency @chromatic-com/storybook to v5](https://git.drupalcode.org/project/canvas/-/merge_requests/1305) State: opened | Author: **** (project_19391_bot_cb443e60680723bba08a5351bf595251) | Branch: renovate/chromatic-com-storybook-5.x | 13 diff lines Description: This MR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@chromatic-com/storybook](https://github.com/chromaui/addon-visual-tests) | [`^3.2.2` → `^5.0.0`](https://renovatebot.com/diffs/npm/@chromatic-com%2fstorybook/3.2.7/5.2.1) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@chromatic-com%2fstorybook/5.2.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@chromatic-com%2fstorybook/3.2.7/5.2.1?slim=true) | >… ### [fix(deps): update npm minor and patch](https://git.drupalcode.org/project/canvas/-/merge_requests/1238) State: opened | Author: **** (project_19391_bot_cb443e60680723bba08a5351bf595251) | Branch: renovate/npm-minor-and-patch | 42 diff lines Description: This MR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [@axe-core/playwright](https://github.com/dequelabs/axe-core-npm) | [`4.11.1` → `4.12.1`](https://renovatebot.com/diffs/npm/@axe-core%2fplaywright/4.11.1/4.12.1) | ![age](https://developer.mend.io/api/mc/badges/age/npm/@axe-core%2fplaywright/4.12.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/npm/@axe-core%2fplaywright/4.11.1/4.12.1?slim=true) | | [@babel/parser](… ### [chore(deps): update mysql docker tag to v8.3](https://git.drupalcode.org/project/canvas/-/merge_requests/1272) State: opened | Author: **** (project_19391_bot_cb443e60680723bba08a5351bf595251) | Branch: renovate/mysql-8.x | 13 diff lines Description: This MR contains the following updates: | Package | Type | Update | Change | Pending | |---|---|---|---|---| | [mysql](https://hub.docker.com/_/mysql) ([source](https://github.com/docker-library/mysql)) | service-image | minor | `8.0` → `8.3` | `8.4` | > :exclamation: **Important** > > Release Notes retrieval for this MR were skipped because no github.com credentials were available. > If you are self-hosted, please see [this instruction](https://github.com/renovatebot/renovate/blob/master/docs/usage/examples/self-hosting.md#githubcom-token-for-release-notes). --- ### Configuration 📅 **S… ### [chore: version packages](https://git.drupalcode.org/project/canvas/-/merge_requests/1452) State: merged 2026-07-30 | Author: **** (project_19391_bot_17a61b0edeafd5a3db3e8b2462b6c010) | Branch: changeset-release/1.x | 53 diff lines Description: Automated merge request created from pending changesets. Merging it publishes the new package versions to npm. Do not commit to this branch manually; it is force-pushed on every push to 1.x. ### [feat: #3518272 support all entity types with configurable displays for content templates](https://git.drupalcode.org/project/canvas/-/merge_requests/791) State: opened | Author: Adam G-H (phenaproxima) | Branch: 3518272-field-ui-base-route | 1801 diff lines Description: Closes #3518272 ### [feat(CLI Tool): Return flexible codebase files to local environment on canvas pull](https://git.drupalcode.org/project/canvas/-/merge_requests/1443) State: opened | Author: Harumi Jang (hooroomoo) | Branch: 3591862-issue-branch | 1748 diff lines Description: AI Disclosure: Yes used Claude Extends the Canvas CLI pull to include * project's package.json - package.json is also now pushed and stored on the asset library and restored on pull, with a note in terminal to run npm install when it changes. (overwrites) * the local helper modules a component imports via the @/… alias (overwrites) * binary assets (images, video, SVG) via `@/.. `alias, `./`, or `../` (overwrites) ### Global asset library changes: `assets` extended with new fields: * path - the original relative disk path, so pull writes each file back to its true location (derived from th… ### [Draft: #3591838 [PHASE 2] introduce color props](https://git.drupalcode.org/project/canvas/-/merge_requests/1432) State: opened | Author: Ben Mullins (bnjmnm) | Branch: 3591838-phase-2-color-props | 10294 diff lines Description: \[Description of changes\] Pending... ## Testing instructions - [ ] First step for someone to test the changes in this MR Closes #3591838 ### [feat(Headless): #3591861 Add a Canvas-owned routed content endpoint for headless apps](https://git.drupalcode.org/project/canvas/-/merge_requests/1436) State: opened | Author: wotnak | Branch: 3591861-headless-new-canvas-content-api-endpoint | 2586 diff lines Description: #3591861 Adds Canvas-owned endpoint for retrieving routed content: `GET /canvas/api/v0/headless/content?requestUri={requestUri}` The endpoint routes the supplied request URI through Drupal and renders supported canonical content entities using Custom Elements. It returns one structured content root or `null`, an Unhead-compatible document-head object, and normalized route information. Headless SDK support for the new endpoint is added in a separate MR: !1437 ### Comparison with `/ce-api` | Behavior | Lupus `/ce-api/{path}` | Canvas `/canvas/api/v0/headless/content?requestUri={requestUri}… ### [#3591838 brand kit color implementation](https://git.drupalcode.org/project/canvas/-/merge_requests/1385) State: opened | Author: Ben Mullins (bnjmnm) | Branch: 3591838-brand-kit-color-support | 6790 diff lines Description: \[Description of changes\]TK AI Disclosure: Had Opencode + Kimi/Claude implement much of the work in several discrete stages. For the UI code, the prompts were detailed & granular enough that it can largely be viewed as my work aided by a robo-proofreader. Parts of the PHP side, however, could be accurately described as "Generated". I've looked though it but there's a bit of blind trust, and a Backend reviewer should keep that in mind. ## Testing instructions - [ ] enable 'canvas_dev_mode' module - [ ] Run DB updates to add Color entity type - [ ] (optional) enable 'canvas_test_code_compone… ### [chore: version packages](https://git.drupalcode.org/project/canvas/-/merge_requests/1449) State: merged 2026-07-30 | Author: **** (project_19391_bot_17a61b0edeafd5a3db3e8b2462b6c010) | Branch: changeset-release/1.x | 50 diff lines Description: Automated merge request created from pending changesets. Merging it publishes the new package versions to npm. Do not commit to this branch manually; it is force-pushed on every push to 1.x. ### [Draft: #3591810 Add AiWizardDev, a dev chat wizard that posts to...](https://git.drupalcode.org/project/canvas/-/merge_requests/1448) State: closed | Author: David Bravo (davidbp) | Branch: work/3591856-tools-dropdown | 1540 diff lines Description: [Description of changes] ## Testing instructions - [ ] First step for someone to test the changes in this MR ### [Issue #3577155: Add support for file fields using custom stream wrappers (currently only `public` is supported)](https://git.drupalcode.org/project/canvas/-/merge_requests/1204) State: opened | Author: Jeremy Chinquist (jjchinquist) | Branch: 3577155-add-support-for-file-fields-using-custom-stream-wrappers-currently-only-public-is-supported | 245 diff lines Description: Adds `private` to the allowed schemes on the `file_uri` field's `value` property in `FileUriItemOverride`. Canvas hardcodes `allowedSchemes => ['public']`, which rejects any file field configured to use the `private://` stream wrapper (e.g. private image/file fields). Because the override applies the constraint to the `file_uri` field type globally, this breaks `private://` file uploads site-wide, not only within Canvas. Both `public` and `private` are valid local, Drupal-managed file schemes (per the `uri_scheme` field storage setting of `\Drupal\file\Plugin\Field\FieldType\FileItem`), so b… ### [feat: #3567225 Allow per-node override of Content Template via checkbox in node selector](https://git.drupalcode.org/project/canvas/-/merge_requests/948) State: opened | Author: Rajab Natshah (RajabNatshah) | Branch: 3567225-allow-per-node-override | 286 diff lines Description: Closes #3567225 ## Summary Allows editing a Canvas layout on an individual node, overriding its Content Template. - A per-node Canvas editor (`/canvas/editor/node/{node}`) edits the node's own layout. - Field linking (dynamic prop sources) resolves against the node as the host entity. When editing a Content Template, the preview entity remains the host. - The Page Data panel is hidden in the per-node editor, and when `drupalSettings.canvas.hidePageDataPanel` is `TRUE`. - Prop-source suggestions are offered for node layouts, not only Content Templates. ## Changes - Back end: `ApiLayoutCont… --- COMMITS (24h) --- - [b88275d2](https://git.drupalcode.org/project/canvas/-/commit/b88275d25814b55458d627fe84786042e8ebeaa4) chore: version packages — Canvas version bot (2026-07-30T22:01:00.000+00:00) - [cbb1a535](https://git.drupalcode.org/project/canvas/-/commit/cbb1a535f35e9c7b9f2d0461b174e57a052701b5) fix(CLI Tool): #3591899 CLI push includes unsupported label property for content templates — Bálint Kléri (2026-07-30T21:59:45.000+00:00) - [2920c2e7](https://git.drupalcode.org/project/canvas/-/commit/2920c2e7e452c426f1e9364e908e97866ef65c68) chore: version packages — Canvas version bot (2026-07-30T15:13:14.000+00:00) - [d71fdd4b](https://git.drupalcode.org/project/canvas/-/commit/d71fdd4b51a54d08b6ba3d42618b081d1e8f1cf3) fix(CLI Tool): #3591897 Canvas CLI sync fails for media and link props in global regions — wotnak (2026-07-30T15:11:58.000+00:00) - [52f9fb59](https://git.drupalcode.org/project/canvas/-/commit/52f9fb594825a7835b52b86146d6837210a041d8) chore(Project management): #3581133 Automate MR review using PHPCS: disallow `\Drupal::service('something')`, require `\Drupal::service(Something::class)` whenever possible, with automatic fixing — Wim Leers (2026-07-30T12:59:02.000+00:00) - [0038ed51](https://git.drupalcode.org/project/canvas/-/commit/0038ed515ee9d4af65adf64c07bd621368dfcf55) task(AI): #3591881 Canvas AI: Improve the schema of the place_components tool — Juan Correa (2026-07-30T11:28:55.000+00:00) ======================================================================== ## [16] summariseModule:ai_context:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: Context Control Center (CCC) (machine name: ai_context) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Kristen Pol (kepol), Levente Besenyei (LeventeB), Pravesh Poonia (Pravesh_Poonia), Reinhold Schachner (reinimax), Tamas Balog (tbalog)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
Context Control Center (CCC)
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Avoid loading the full published catalog on the CCC overview page](https://git.drupalcode.org/project/ai_context/-/work_items/3586355) State: opened | Updated: 2026-07-31 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: 2026Sprint15, AI Initiative Sprint, ai::inside, blocker::stable Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !232 [Issue #3586355: Avoid loading the full published catalog on the CCC overview page.](https://git.drupalcode.org/project/ai_context/-/merge_requests/232) | State: opened | Author: Kristen Pol (kepol), 470 diff lines Description: ## Problem/motivation Parent: #3586309 `AiContextOverviewController::overview()` still: 1. Runs an unbounded published-ID query with `accessCheck(FALSE)`. 2. Calls `loadMultiple()` on every published context item just to set a boolean for whether any stored global item exists. The early `break` after finding one global item does not prevent the full entity load. There is already a `@todo` to replace this with a `LIMIT 1` scope-index query. Cache tags/contexts for the overview render array were added earlier; this issue is only about the expensive existence checks and aligning the query a… ### [Avoid functional-test dual-container traps](https://git.drupalcode.org/project/ai_context/-/work_items/3586325) State: opened | Updated: 2026-07-31 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: 2026Sprint15, AI Initiative Sprint, Quick Win, ai::inside Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !225 [Issue #3586325: Fix functional-test dual-container traps in AiContextAdminSettingsTest.](https://git.drupalcode.org/project/ai_context/-/merge_requests/225) | State: opened | Author: Pravesh Poonia (Pravesh_Poonia), 75 diff lines Description: ## Problem/motivation Follow-up to: #3586258+s Pull item 7.3 from: #3586299+s _**Verify the issue problem and solution before proceeding.**_ ### Avoid functional-test dual-container traps **File:** - `tests/src/Functional/AiContextAdminSettingsTest.php` **Problem:** At least one functional test submits a form directly through the test container's `form_builder`. Functional tests run separate test and web-server containers, so direct form builder submission can miss browser/runtime behavior. **Recommended fix:** - Use `$this->drupalGet()` and browser-level `$this->submitForm()` when… ### [Rename entity bundle and target entity scope plugins for better DX](https://git.drupalcode.org/project/ai_context/-/work_items/3586276) State: opened | Updated: 2026-07-31 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: 2026Sprint12, 2026Sprint13, 2026Sprint14, 2026Sprint15 Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !195 [Issue #3586276: Rename entity bundle and target entity scope plugins for better DX](https://git.drupalcode.org/project/ai_context/-/merge_requests/195) | State: opened | Author: Tamas Balog (tbalog), 5873 diff lines Description: ## Problem/solution Follow up to: #3586148+s The naming of the entity bundle and target entity scope plugins is confusing. ## Solution **AiContextScopeEntityBundle** Rename Entity Bundle => Entity Type at a code-level because there are bundleless content entities. Label: Entity Types Description: Apply this context to every entity of a chosen type, for example all Article nodes, every Document media item, or every Canvas page. Choose this when the context is true for the whole type, not a single item. **AiContextScopeTargetEntity** Rename Target Entity => Entity Item because target… ### [Improve conditional subcontext disabled-state behavior and admin UX](https://git.drupalcode.org/project/ai_context/-/work_items/3586292) State: opened | Updated: 2026-07-31 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: 2026Sprint13, 2026Sprint14, 2026Sprint15, AI Initiative Sprint Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !226 [Issue #3586292: Exclude conditional subcontext items when AI decisions are disabled.](https://git.drupalcode.org/project/ai_context/-/merge_requests/226) | State: opened | Author: Kristen Pol (kepol), 1737 diff lines Description: ## Description Follow-up to: #3586207+s ### Summary When **Enable conditional subcontext AI decisions** (`conditional_subcontext_enabled`) is off, conditional subcontext children should not participate in normal context selection. This issue implements that behavior and adds admin UX so editors understand why conditional items are inactive, can reach the setting to re-enable the feature, and get clear warnings when editing affected items. ### Problem / motivation Previously, disabling conditional subcontext AI caused **all conditional children to be included without an AI call**. That wa… ### [Allow scope plugins to declare an optional icon for UI display](https://git.drupalcode.org/project/ai_context/-/work_items/3586262) State: opened | Updated: 2026-07-31 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: 2026Sprint15, AI Initiative Sprint, ai::inside, priority::normal Description: ## Description Follow-up to: #3586220+s Blocked by: #3586243+s ### Summary Scope plugins are shown in several places across `ai_context` (and will likely appear in more over time). Today, when an icon is shown at all, it is hard-coded in the view layer — e.g. `AiContextItemViewBuilder::SCOPE_ICON_CLASSES` for the context item **Details** sidebar — with a generic funnel fallback for unknown plugins. This issue adds an **optional, plugin-level icon** on `AiContextScope` plugins so each scope can define a consistent visual identity wherever that plugin is rendered, without patching core ma… ### [Complete scope plugin persistence API: manager orchestration, target entity encapsulation, and plugin-driven admin/selection](https://git.drupalcode.org/project/ai_context/-/work_items/3586243) State: opened | Updated: 2026-07-31 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol) | Labels: 2026Sprint11, 2026Sprint16, ai::inside, category::task Description: ## Description Blocked by: #3586295+s ### Summary The scope plugin API was asymmetric: read and match were abstracted, but write, clear, index, cleanup, form integration, and save-time validation leaked storage details into callers. `AiContextItemForm`, entity presave, `hook_entity_delete()`, and `AiContextScopeIndexService` contained special cases — especially the `target_entities` DER field — that would repeat for every new scope. This issue completes the scope plugin value lifecycle contract before RC1. Callers delegate to `AiContextScopeManager` and scope plugins; custom storage (targ… ### [Create Mad Libs style template for the CCC](https://git.drupalcode.org/project/ai_context/-/work_items/3586340) State: opened | Updated: 2026-07-31 | Author: Emma Horrell (emma-horrell) | Assigned: unassigned | Labels: ai::context, category::feature, priority::major, state::postponed Description: To help new users understand how to use the Context Control Center, we proposed a Mad Libs style template that would enable users to follow steps to create context items to be used to shape their content in the way they wanted, and therefore get the hang of how the CCC works. Aidan had previously produced an AI readiness checklist which could be used as the basis for this template, to be included in the CCC and made available to users ### [[Discuss] Adding priority to context item to affect ranking](https://git.drupalcode.org/project/ai_context/-/work_items/3586364) State: opened | Updated: 2026-07-31 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol), Michael Anello (ultimike), Aidan Foster (aidanfoster), Emma Horrell (emma-horrell) | Labels: 2026Sprint16, category::plan, needs ux review, priority::major Description: ## Problem Some context will be more important than others. A simple way to factor this in would be to have a priority level for context items. ## Solution Discuss having a priority level, e.g. - Very high - High - Medium - Low Or - 1 (low) - 2 - 3 - 4 - 5 (high) Then the ranking could sort by priority level so that the highest priority items are more likely to make the cut when factoring in max items and max tokens. ### [[Discuss] Review context selection ranking factors before 1.0](https://git.drupalcode.org/project/ai_context/-/work_items/3586365) State: opened | Updated: 2026-07-31 | Author: Kristen Pol (kepol) | Assigned: Kristen Pol (kepol), Michael Anello (ultimike), Aidan Foster (aidanfoster), Emma Horrell (emma-horrell) | Labels: 2026Sprint15, AI Initiative Sprint, category::plan, needs ux review Description: ## Summary Before we ship 1.0, we should confirm that the current rules for choosing which context items reach an AI feature are the right set — and whether anything important is missing. This issue is a **discussion**. The goal is shared understanding of what the module does today, in plain language, so product/UX and engineering can decide together whether to add ranking factors before release. ## Background When someone uses an AI feature on the site, the module picks a small set of **context items** (brand voice, writing rules, section-specific guidance, etc.) and attaches them to the … ### [CCC beta3 blog post](https://git.drupalcode.org/project/ai_context/-/work_items/3586332) State: closed | Updated: 2026-07-31 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: 2026Sprint15, AI Initiative Sprint, ai::context, category::task Description: >>> [!note] Migrated issue Reported by: [kristen pol](https://www.drupal.org/user/8389) >>> [Tracker] Update Summary: [One-line status update for stakeholders] Check-in Date: MM/DD/YYYY Blocked by: [#XXXXXX] (New issues on new lines) Additional Collaborators: @username1, @username2 Metadata is used by the AI Tracker. Docs and additional fields here. [/Tracker] Problem/Motivation We need a blog post to announce CCC beta Proposed resolution Write it and run it by the marketing team Target date or deadline 20 July 2026 Remaining tasks Write blog post Review and tweak Ping marketing team for… ### [beta2 upgrade fails at updates 10006 and 10011 after bundleless entity conversion](https://git.drupalcode.org/project/ai_context/-/work_items/3586343) State: opened | Updated: 2026-07-31 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: 2026Sprint15, AI Initiative Sprint, ai::inside, blocker::beta Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !229 [Issue #3586343: Fix beta2 upgrade failures in updates 10006, 10008, and 10011.](https://git.drupalcode.org/project/ai_context/-/merge_requests/229) | State: opened | Author: Kristen Pol (kepol), 994 diff lines Description: ## Summary Upgrading from `1.0.0-beta2` to current `1.0.x` can fail during a single `drush updb` run in two places: 1. **`ai_context_update_10006()`** — entity saves while the database still has the bundled NOT NULL `type` column, but the code already defines a bundleless `ai_context_item`. Saves write `type` as NULL and hit an integrity constraint violation. 2. **`ai_context_update_10011()`** — after update `10008` removes the bundle, stale Content Moderation field definitions remain in memory in the same process. Later entity saves fail on `moderation_state` (or related p… ### [Update relevant CCC skipped tests](https://git.drupalcode.org/project/ai_context/-/work_items/3586263) State: closed | Updated: 2026-07-31 | Author: Kristen Pol (kepol) | Assigned: unassigned | Labels: 2026Sprint15, AI Initiative Sprint, ai::inside, category::task Description: ## Problem The `ai_context` test suite contains intentional skip paths that reduce CI coverage: - All five tests in `AiContextSchedulerRaceConditionTest` are skipped at the class level. - `testModulesInstalledHookIsSafeToCall` contains a second, redundant skip. - Up to 37 tests silently skip when Dynamic Entity Reference is unavailable, even though it is a declared `require-dev` dependency. ### Scheduler tests **File:** `tests/src/Functional/AiContextSchedulerRaceConditionTest.php` The class-level skip was added while the `scheduler_hide_publish_date` and `scheduler_hide_unpublish_date` h… ### [QA team start testing CCC to get familiar with functionality and create QA plan](https://git.drupalcode.org/project/ai_context/-/work_items/3586342) State: opened | Updated: 2026-07-31 | Author: Kristen Pol (kepol) | Assigned: Bruna Emerich (brunaemerich) | Labels: 2026Sprint15, AI Initiative Sprint, ai::inside, blocker::stable Description: ## Problem CCC is huge and there's a lot to test. Beta3 was released last week and there were bugs: - #3586338+s - #3586341+s These most likely would have be caught by the QA team. I tested here with AI on Drupal CMS / Drupal 11: #3586296+s but neglected to test with Drupal 10. Not sure why the settings pages didn't get hit though. I tested manually with Canvas AI though it would be amazing if that could be automated somehow. ## Solution QA team plays around with CCC to understand the functionality and starts a draft QA plan. Here's the QA plan from AI: https://git.drupalcode.org/-/… ### [Restore Drupal 10 compatibility and repair incomplete beta3 upgrades](https://git.drupalcode.org/project/ai_context/-/work_items/3586338) State: opened | Updated: 2026-07-30 | Author: Reinhold Schachner (reinimax) | Assigned: Daniel Rodriguez (danrod) | Labels: 2026Sprint14, 2026Sprint15, AI Initiative Sprint, ai::inside Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !223 [Issue #3586338: Restore Drupal 10 compatibility and repair beta3 upgrades.](https://git.drupalcode.org/project/ai_context/-/merge_requests/223) | State: opened | Author: Reinhold Schachner (reinimax), 1613 diff lines Description: # Updated issue info ## Summary The 1.0.0-beta3 release introduced Drupal 11-only hook discovery and API usage that breaks upgrades and runtime behavior on supported Drupal 10 sites. Failed upgrades can also leave context items with missing revision pointers. Enabling Drupal 10 CI further revealed that several attribute-based hooks were never invoked on Drupal 10, causing admin pages to error and Scheduler setup to be skipped. This issue covers: - Restoring Drupal 10 and PHP 8.1 compatibility. - Registering hook services explicitly for Drupal 10 (`DiffHooks`, `DynamicEntityReferenceHooks`,… ### [Clean up CCC inconsistencies and DX issues before rc1 (part 3)](https://git.drupalcode.org/project/ai_context/-/work_items/3586271) State: opened | Updated: 2026-07-30 | Author: Kristen Pol (kepol) | Assigned: Juan Correa (jucs7) | Labels: 2026Sprint13, 2026Sprint14, 2026Sprint15, AI Initiative Sprint Description: Follow-up to: #3586192 _**Verify the issue problem and solution before proceeding.**_ ## Title **AI Context: Consistency / DX cleanup (final, constructor promotion, snake_case locals, service interfaces)** --- ## Description Follow-up to #3586192 / naming & DX review. Addresses the remaining **consistency / DX** items that were explicitly out of scope for the naming MR. **No functional or API behavior changes** — style, clarity, and maintainability only. ### Background The naming/DX MR covered route/permission renames, dead code removal, `new self` in final classes, and snake_case fix… ### [Add a dedicated editorial workflow for AI Context Items](https://git.drupalcode.org/project/ai_context/-/work_items/3586345) State: opened | Updated: 2026-07-30 | Author: Kristen Pol (kepol) | Assigned: Levente Besenyei (LeventeB) | Labels: 2026Sprint15, AI Initiative Sprint, ai::inside, blocker::stable Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !236 [Issue #3586345: Add a dedicated editorial workflow for AI Context Items](https://git.drupalcode.org/project/ai_context/-/merge_requests/236) | State: opened | Author: Levente Besenyei (LeventeB), 821 diff lines Description: ## Problem Follow-up to #3586327+s AI Context Items currently reuse Drupal CMS’s shared `basic_editorial` workflow. This creates ambiguous Draft/Unpublished states and risks changing moderation behavior for unrelated content using that workflow. ## Solution Add an `ai_context_editorial` workflow owned by this module with: - **Draft** — editable work in progress. - **Published** — active context. - **Archived** — inactive and restore-only. - Transitions for publishing, archiving, and restoring to Draft or Published. - Migration of existing items and role permissions from `basic_editorial`… --- MERGE REQUESTS (24h) --- (none) --- COMMITS (24h) --- (none) ======================================================================== ## [17] summariseModule:ai_ckeditor:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: AI CKEditor (machine name: ai_ckeditor) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Ricardo Castañeda (cadence96)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
AI CKEditor
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). (none) --- MERGE REQUESTS (24h) --- ### [Show AI status indicator next to the Generate button](https://git.drupalcode.org/project/ai_ckeditor/-/merge_requests/6) State: opened | Author: Ricardo Castañeda (cadence96) | Branch: 3614074-show-ai-status | 75 diff lines Description: The AI Writer status was only shown below the response editor, requiring a scroll to see it inside the modal right after clicking Generate. Mirror the same status text into a compact indicator next to the button so users get immediate feedback that the request is in progress. Co-Authored-By: Claude Sonnet 5 Closes #3614074 --- COMMITS (24h) --- (none) ======================================================================== ## [18] summariseModule:ai_search:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: AI Search (machine name: ai_search) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Abhisek Mazumdar (abhisekmazumdar), David Bondor (superbondor), Dezső Biczó (mxr576)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
AI Search
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [RagTool::execute() should expose structured per-result data and check entity access](https://git.drupalcode.org/project/ai_search/-/work_items/3584031) State: opened | Updated: 2026-07-31 | Author: Abhisek Mazumdar (abhisekmazumdar) | Assigned: unassigned | Labels: 2026Sprint15, AI Initiative Sprint, ai::inside, state::needsReview Description: ## Problem/Motivation `RagTool::execute()` (`src/Plugin/AiFunctionCall/RagTool.php`) only ever hands the LLM a single flattened text string built from the search results. None of the per-result data survives the call: not which entity a chunk came from, not its score, not the raw chunk text. `getStructuredOutput()` returns `results` from `$this->results`, but `execute()` builds its output into a local `$end_results` array and never assigns anything to `$this->results`. It is always `[]`. This blocks consumers who want the *retrieved sources themselves*, not just the LLM's answer, from deleg… ### [Defer default search item access checking to the Search API datasource plugin](https://git.drupalcode.org/project/ai_search/-/work_items/3584042) State: opened | Updated: 2026-07-30 | Author: Dezső Biczó (mxr576) | Assigned: unassigned | Labels: needs backport to 1.x, state::needsReview Description: **Spinoff from:** #3579758 #### **Problem/Motivation** Prior to recent developments (#3575999), the AI Search backend (`SearchApiAiSearchBackend`) only supported access checks for content entities by hardcoding the entity load and access checks for items prefixed with `entity:` directly in `checkItemAccess()`. This bypasses the standard Search API architecture, preventing other datasource plugins (such as custom, federated, or non-content entity datasources) from managing and enforcing their own access control rules. #### **Proposed Resolution** Refactor `SearchApiAiSearchBackend::checkItem… ### [[PP-1] Provide an API for performing access check on non-content entities](https://git.drupalcode.org/project/ai_search/-/work_items/3579758) State: opened | Updated: 2026-07-30 | Author: drupalbot | Assigned: unassigned | Labels: category::feature, code, priority::normal, state::closed Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !49 [Issue #3579758: Provide API for access checks on non-content entities](https://git.drupalcode.org/project/ai_search/-/merge_requests/49) | State: opened | Author: David Bondor (superbondor), 1184 diff lines Description: >>> [!note] Migrated issue Reported by: [mxr576](https://www.drupal.org/user/315522) >>> Problem/Motivation SearchApiAiSearchBackend used to only have support for content entities (indexed via rupal\search_api\Plugin\search_api\datasource\ContentEntity but that was fixed in #3575999: Fix support of non-content entity SearchAPI datasources. Now SearchApiAiSearchBackend can index and work with other data sources however it does not provide an API for performing access checks on search results before they are returned. The scope of this issue is designing and introducing that new API that con… ### [Introduce a dedicated runtime access-checking API for AI Search / RAG filtering](https://git.drupalcode.org/project/ai_search/-/work_items/3584043) State: opened | Updated: 2026-07-30 | Author: Dezső Biczó (mxr576) | Assigned: unassigned | Labels: Needs tests Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !75 [[PP-1] Introduce a dedicated runtime access-checking API for AI Search / RAG filtering](https://git.drupalcode.org/project/ai_search/-/merge_requests/75) | State: opened | Author: Dezső Biczó (mxr576), 302 diff lines Description: **Spinoff from:** #3579758 #### **Problem/Motivation** While standard Search API datasource-level access checking (`getItemAccessResult()`) verifies whether a user is allowed to view a page on the website, AI Search / RAG applications introduce more complex, context-specific, and dynamic filtering requirements. For example, a business may need to: - Exclude highly sensitive personal or draft data from being sent to external LLMs, even if the logged-in user technically has website view access. - Restrict results dynamically based on chatbot persona/index contexts (e.g., a shared index where… --- MERGE REQUESTS (24h) --- ### [bug: #3584035 Reset chunk-slicing progress when index is cleared or reset-tracker is run](https://git.drupalcode.org/project/ai_search/-/merge_requests/71) State: opened | Author: Abhisek Mazumdar (abhisekmazumdar) | Branch: 3584035-issue-branch | 261 diff lines Description: Closes #3584035 ### [Support non content entity datasources](https://git.drupalcode.org/project/ai_search/-/merge_requests/25) State: opened | Author: Dezső Biczó (mxr576) | Branch: 3575999-support-non-content-datasources | 891 diff lines Description: Closes #3575999 TODO - [ ] The backport of #3487487 to 1.0.x (happened in #3584014) introduced a new `\Drupal\ai_search\Plugin\EmbeddingStrategy\EmbeddingBase::isTitleInContextual()` which not yet available in 2.0.x, when that becomes available it also has to be fine tuned with: ``` - if ($datasource) { + if ($datasource instanceof ContentEntity) { ``` - [ ] If https://git.drupalcode.org/project/ai_search/-/work_items/3584042 gets merged first than extend test coverage to verify access checking performed on items returns by the custom data source --- COMMITS (24h) --- (none) ======================================================================== ## [19] summariseModule:ai_translate:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: AI translate (machine name: ai_translate) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Marcus Johansson (Marcus_Johansson), Rob Loach (robloach)". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
AI translate
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Add documentation](https://git.drupalcode.org/project/ai_translate/-/work_items/3585534) State: opened | Updated: 2026-07-30 | Author: Marcus Johansson (Marcus_Johansson) | Assigned: unassigned | Labels: 2026Sprint15, AI Initiative Sprint, ai::inside, category::task Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !32 [Draft: Resolve "Add documentation"](https://git.drupalcode.org/project/ai_translate/-/merge_requests/32) | State: opened | Author: Marcus Johansson (Marcus_Johansson), 570 diff lines Description: Currently there is no documentation page for the module - lets have one. ### [Fix Pipeline](https://git.drupalcode.org/project/ai_translate/-/work_items/3585537) State: opened | Updated: 2026-07-30 | Author: Rob Loach (robloach) | Assigned: unassigned | Labels: category::task, priority::normal, state::accepted Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !34 [Issue #3585537: Fix the Pipelines by adding composer.json](https://git.drupalcode.org/project/ai_translate/-/merge_requests/34) | State: opened | Author: Rob Loach (robloach), 18 diff lines Description: phpstan and phpunit are broken on the 2.0.x branch. https://git.drupalcode.org/project/ai_translate/-/pipelines/842336 Fix them. --- MERGE REQUESTS (24h) --- (none) --- COMMITS (24h) --- (none) ======================================================================== ## [20] summariseModule:flowdrop:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: FlowDrop (machine name: flowdrop) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. Do not name any individual people in this section. No one was active enough this period to list. Format your response as an HTML fragment. Start with
FlowDrop
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Add detail logic to the playground pipelines and add the ability to show the debug data by clicking on the executed pipeline item](https://git.drupalcode.org/project/flowdrop/-/work_items/3589741) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: Shibin Das (D34dMan) | Labels: state::accepted, v1.x-dev Description: >>> [!note] Migrated issue Reported by: [gxleano](https://www.drupal.org/user/3591999) >>> Add detail logic to the playground pipelines and add the ability to show the debug data by clicking on the executed pipeline item ### [A state update is applied through the reducers after the node completes (SG-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592366) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `state_update` output applied through reducers post-completion; never exposure-stripped (= EXPO-12). - **Implementation:** `:1347-1351` - **Guaranteed by:** Rule `SG-3` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [What the runtime hands a node, and what the node must declare to see it (SG-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592365) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Three independent guarantees. **(1)** The runtime input array handed to `executeNode()` carries `__state__` (the full `GraphState::toArray()`), `__messages__` (message arrays) and `__data__`, plus `__iterator__` and `__current_item__` whenever the state has an iterator, plus `__interrupt_id__` when the job is a resume. A processor only *sees* one of these if it declares it as a parameter — an `__`-prefixed parameter is "internal" and always accepts its runtime input (= CFG-8/CFG-13). **(2)** Independently, the current `GraphState` is passed via `setGraphState()` to processors implementing `Sta… ### [How each state field is reduced (SG-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592364) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Reducers by field: messages=append, data/metadata=merge, rest=replace; absent field keeps value; state immutable. - **Implementation:** `GraphState.php:62-79` - **Guaranteed by:** 4 + 3 reducer suites Rule `SG-1` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-1` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [An engine that cannot consume a snapshot must throw (INT-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592363) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: An engine that cannot consume a given snapshot MUST **throw** `OrchestrationException` naming the snapshot, never silently discard-and-restart (restart re-fires side-effecting nodes). The two sync engines (`SynchronousOrchestrator`, `SynchronousPipelineOrchestrator`) have no snapshot-seeding mechanism, so ANY attached snapshot is refused before a pipeline or job exists; "no snapshot present" stays a plain fresh start (OPEN-10 part b; narrows an earlier "replay completed nodes on every engine" conclusion, which is unachievable: `toSnapshotData()` emits no completion set and both loop engines de… ### [A terminal snapshot is not resumable (INT-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592362) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: A terminal snapshot (COMPLETED/FAILED/CANCELLED) is **non-resumable** (OPEN-10 part a): the snapshot-consuming engines throw `OrchestrationException` naming the snapshot and its status before any pipeline is created. The same gate covers SG-12's *explicit* checkpoint-resume arm (a checkpoint capturing a terminal `GraphState` refuses to restore, naming the checkpoint). Thread continuity is deliberately NOT gated: restoring a thread's latest checkpoint (typically the previous turn's `workflow_end` state) seeds a NEW turn with accumulated conversation state — sessions depend on it — and is not a … ### [A checkpoint round-trip preserves which terminal status it was (INT-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592361) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: The checkpoint round-trip preserves the terminal-status distinction — **CANCELLED included**. The state carries its outcome as a `status` string (`completed`/`failed`/`cancelled`; NULL while the run is live) and the checkpoint payload persists it, because `isComplete` alone cannot tell cancellation from completion. A Cancel signal marks the state cancelled and writes the final `workflow_end` checkpoint, and the persisted status — never a re-derivation — becomes the WorkflowSnapshot status. **Dual read (mandatory, no data migration):** a payload written before the field carries no `status` key … ### [An async handover seeds the queued run from the snapshot (INT-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592360) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Async handover: queued run seeded from snapshot as pre-completed `injected` jobs. Each seeded job is COMPLETED carrying the snapshot's output plus the marker triple `injected` / `injected_from_snapshot` (source executionId) / `injected_at`, so the queue worker schedules only genuinely-remaining work and nothing mistakes a seeded row for work this run performed. A snapshot node with no matching job warns and is skipped; the count is reported as `results.injected_jobs` / `metadata.injected_node_count`. - **Implementation:** `AsynchronousOrchestrator.php:136-144`, `::initializeJobsFromSnapshot()… ### [Saving a snapshot is an upsert keyed by execution id (INT-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592359) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `EntitySnapshotStorage::save()` is an **upsert keyed by executionId**: an existing entity with the same `execution_id` is loaded and overwritten in place via `fromWorkflowSnapshot()`, so one execution never accumulates two snapshot rows; otherwise a new entity is created from the DTO. Every query in this service deliberately runs with `accessCheck(FALSE)` — snapshot access is **NOT** enforced here, it is enforced at the API layer (see `SnapshotAccessTest`), and cron cleanup runs with no user context. `cleanup($olderThan, $statuses)` deletes entities with `created < $olderThan` AND, when `$stat… ### [Snapshot validation returns a fixed set of codes (INT-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592358) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `validateSnapshot()` returns a `ValidationResult` whose codes are the contract: `ERROR_VERSION_MISMATCH` — only when the snapshot's `workflowVersion` is non-empty, an empty version **skips** the check and is not an error; `ERROR_UNKNOWN_NODE` per snapshot node absent from the definition; `ERROR_DEPENDENCY_NOT_MET` per completed node whose dependency has no state or is neither completed nor skipped; and — warnings only, which never make the result invalid — `WARNING_ORPHAN_NODE` per definition node missing from the snapshot and `WARNING_INJECTED_WITHOUT_DEPENDENCY` per *completed* injected node… ### [The workflow version hashes structural data only (INT-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592357) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `workflowVersion` = 16-hex sha256 over structural data only (labels/positions don't change it). - **Implementation:** `WorkflowStateManager.php:256-284` - **Guaranteed by:** Rule `INT-7` of `RT-INT` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: INT-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592098 ### [What a snapshot carries (INT-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592356) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `generateSnapshotFromPipeline()` builds a `WorkflowSnapshot` carrying `workflowId` (`"unknown"`, and an empty `workflowVersion`, when the pipeline has no workflow), the structural `workflowVersion`, the executionId, the caller-supplied status, one `NodeSnapshot` per job keyed by node id, `initialInput` = the pipeline input, and metadata `{orchestrator_type, pipeline_id}`. Per job, `createNodeSnapshotFromJob()` maps JobStatus→NodeSnapshot status one-to-one except `skipped` and `cancelled`, which BOTH become `skipped`, and any unrecognised status, which becomes `idle`; `output` is carried only f… ### [A pipeline signal is polled between jobs, never mid-job (INT-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592355) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `pollPipelineSignal()` runs between job iterations — the in-flight job always finishes first — and dispatches `PipelineSignalPollEvent`; a NULL signal continues the loop. **Cancel:** `markAsCancelled()` + `execution_time_us` stamped on the execution context, then BOTH `ExecutionCancelledEvent` and a `PipelineCompletedEvent` carrying `PipelineStatus::Cancelled` — cancellation is announced like any other terminal outcome, so session notices and sub-workflow sentinels fire (= ORC-15) — returning a response with status `cancelled` and metadata `orchestrator_type`/`signal_id`/`reason`; the flowdrop… ### [The four conditions for a node to own a resume (INT-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592354) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Resume ownership gate (all 4): bag has `__interrupt_id__`, processor Resumable, interrupt resolved, `job_id` matches; else fall through to `process()` (safe re-ask). - **Implementation:** `NodeRuntimeService.php:185-191,462-496` - **Guaranteed by:** 5 + 2 contract suites Rule `INT-4` of `RT-INT` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: INT-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592098 ### [Resolving an interrupt resets the job and resumes the pipeline (INT-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592353) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Resolution: find job by `job_id`, reset PENDING, resume only if pipeline PAUSED, via declared orchestrator; stateless run → no resume. The reset and the resume are **separate steps in that order** — the job goes back to PENDING unconditionally, and a non-PAUSED pipeline is then left strictly alone (never re-entered, so two executors cannot race). The stamped `job_id` is the primary lookup; the node-id pipeline scan is only the legacy fallback. - **Implementation:** `InterruptResolvedSubscriber.php:72-140` - **Guaranteed by:** 3 tests (`InterruptPauseAndResolutionContractTest`: job_id lookup +… ### [The interrupt entity is persisted by a subscriber (INT-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592352) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Interrupt entity persisted by subscriber; orchestrator reads from event/metadata, never the immutable exception. - **Implementation:** 2 sites - **Guaranteed by:** Rule `INT-2` of `RT-INT` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: INT-2` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592098 ### [An interrupted node pauses the pipeline and reports where it stopped (INT-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592351) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Node interrupt → job INTERRUPTED + `interrupt_id`, pipeline PAUSED, response carries `interrupt.*` + partials. The response shape is part of the rule: status `interrupted`, `metadata.interrupt.interrupt` = the persisted interrupt's API array (id/nodeId/status), `metadata.pipeline_id`, and `results` holding every node that completed before the interrupt. - **Implementation:** `AbstractOrchestratorBase.php:271-299`; pause + response `SynchronousPipelineOrchestrator.php:356-374`; payload `InterruptHandlingTrait::handleInterruptException()` - **Guaranteed by:** 1 test asserting all four together … ### [Tools are handed to a processor only when there are some (DATA-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592350) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `NodeRuntimeService` calls `setTools()` only when the projection is non-NULL **and** the processor instance is `ToolsAwareInterface` — a non-consumer with tools wired receives none at runtime (at compile time that wiring is already a validation error, `ToolConsumerValidator`; a `ToolPassthroughInterface` box is accepted there and forwards instead). Under StateGraph the projection is rebuilt **per job** from the workflow's stored graph data — re-enriched via `NodeMetadataResolver`, with the derived `DependencyGraph` memoised per workflow id — rather than read from a compiled pipeline, which is … ### [The model-facing tool schema omits parameters already filled (DATA-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592349) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Model-facing tool schema omits pinned-in-config and edge-fed params. - **Implementation:** `:126-135` - **Guaranteed by:** (3) Rule `DATA-11` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [Tool availability projects into tool bindings, not into data (DATA-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592348) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `tool_availability` projects into ToolBindings (flattened through ToolBox), not a data delivery; passthrough cycle → `ToolWiringException`. - **Implementation:** `ToolProjector.php:65-122` - **Guaranteed by:** (4 + flattener) Rule `DATA-10` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-10` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [The unified output port composes exposed outputs only (DATA-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592347) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Unified I/O `output` port composes exposed outputs only, excluding `_`-prefixed and `trigger`; an output key the node type does not configure defaults to exposed (kept). - **Implementation:** `NodeRuntimeService.php:823-851` - **Guaranteed by:** `NodeRuntimeServiceUnifiedOutputCompositionTest` (9 rows) + EXPO-14 ordering test Rule `DATA-9` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-9` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [The effective execution config is stamped on the pipeline (SG-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592376) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: The effective `ExecutionConfig` — including the resolved `threadId` and `checkpointerType` — is stamped on `$pipeline->getExecutionContext()['stategraph_config']` alongside `orchestrator_type`, and the re-stamp (plus its save) is skipped when both values are already exactly what would be written. A later resume or deferred launch rebuilds via `ExecutionConfig::fromArray()` on that key; only when the key is absent does it fall back to the workflow's `orchestrator_settings.stategraph` (plus a root `timeout`), then to defaults bounded by the caller's max-iterations. - **Implementation:** stamp `… ### [Which stored state a resume restores, in order (SG-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592375) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: State restore precedence: initialSnapshot → resumeFromCheckpoint (missing id warns+fresh; terminal checkpoint throws — INT-14's gate) → latest for threadId (deliberately ungated: thread continuity seeds a new turn, see INT-14; a terminal seed keeps everything accumulated but has its outcome — `isComplete`, `error`, `status` — cleared so the new turn reports its own result, see INT-13) → fresh. - **Implementation:** `orchestrate()` snapshot arm + `initializeState()` - **Guaranteed by:** 4 tests in `StateGraphResumeRefusalTest` (snapshot outranks an explicit checkpoint — proven by a TERMINAL ch… ### [A checkpoint per node, chained, plus one at the end (SG-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592374) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Checkpoint per node (chained `parentId`) + final `workflow_end`; memory checkpointer request-scoped; entity checkpointer persists; unknown type → `InvalidArgumentException`. - **Implementation:** `:813-821,947-954`; factory - **Guaranteed by:** 5 suites Rule `SG-11` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [The reserved trigger port means no branch for loopback naming (SG-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592373) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Reserved `trigger` source port = "no branch" for loopback naming. - **Implementation:** `:1684-1691` - **Guaranteed by:** Rule `SG-10` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-10` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [An edge condition never routes (SG-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592372) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `data.condition` never routes — not even on a loopback edge, the one place dispatch really decides; warning once per edge per resolution of its source's outgoing edges (= EDGE-8). - **Implementation:** `outgoingEdges()` - **Guaranteed by:** `StateGraphRemovedEdgeConditionTest::testConditionDoesNotGateLoopReentry`, `::testConditionedEdgeIsStoredWarnedAndFollowed` Rule `SG-9` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-9` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3… ### [How a repeated node's result is keyed (SG-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592371) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Two behaviours. **(a) Response keying** — the first execution of a node lands in `results` under the bare `nodeId`; each later execution lands under `"{nodeId}:{n}"` with `n` = that node's zero-based prior-execution count in this run (`node`, `node:1`, `node:2`…), and a `WorkflowStopException` payload uses the same key. The interrupt/partial-results path re-derives an equivalent scheme from storage rather than sharing the counter: completed jobs are walked in job-id order and keyed by the job's `loop_iteration` metadata when it carries one, else by the running per-node occurrence count. **(b) … ### [Loopback re-entry needs an active branch and remaining work (SG-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592370) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Loopback re-entry requires active branch AND (`iterator.hasMore` \| iteration count < max for branch-driven loops). - **Implementation:** `:846-869,1718-1808` - **Guaranteed by:** 3 suites Rule `SG-7` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [Routing decides per edge and dispatches per target (SG-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592369) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Routing decides per EDGE, dispatches per TARGET (multiple edges OR'd into one dispatch). - **Implementation:** `StateGraphOrchestrator.php:832-872` - **Guaranteed by:** Rule `SG-6` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [The loopback input doubles as the item result (SG-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592368) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `loop_back` input doubles as `item_result` when absent. - **Implementation:** `:113-122` - **Guaranteed by:** Rule `SG-5` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [How a ForEach loop initialises and finishes (SG-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592367) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: ForEach: init on empty `__iterator__` (needs items; non-array wrapped; re-indexed; empty completes immediately); defined output set incl. `collected_results` on completion. - **Implementation:** `ForEachNode.php:107-200+` - **Guaranteed by:** 8 cases Rule `SG-4` of `RT-SG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SG-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592099 ### [Which payloads the status vocabulary guards (PIPE-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592381) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: Vocabulary guarding is scoped to `job_status_summary` / the job API's `status_summary`: `total` counts every job, but a bucket is incremented only when `JobStatus::tryFrom()` resolves the persisted value, so the buckets may sum to **less** than `total`, no out-of-enum key is ever added there, and no PHP warning is raised. The distinct unknown values are logged as exactly **one** warning per read. ⚠ `node_statuses[*].status_counts` is deliberately **NOT** guarded — it counts raw persisted values — so an out-of-enum status DOES appear as a key there, and as `node_statuses[*].status`. The two liv… ### [The job status summary has one shape, derived from the enum (PIPE-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592380) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `job_status_summary` has ONE shape, derived from the `JobStatus` enum (`emptySummary()`): the key `total` followed by one integer counter per case, `interrupted` included. All three build paths emit those exact keys in that order — the real jobs read, the missing-pipeline fallback and the failure catch (both fallbacks all-zero, via one `emptyJobsData()` builder). The job API's own `status_summary` shares the builder. - **Implementation:** `JobStatus::emptySummary()`; `PipelineApiController::getPipelineJobs`/`::emptyJobsData`; `JobApiController::getPipelineJobStatus` - **Guaranteed by:** Rul… ### [The live run status is read from persisted entities (PIPE-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592379) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: The live run-status contract is the pipeline API reading **persisted entity state** (= SG-15). Two routes, one envelope: `GET /api/flowdrop/pipeline/{pipeline_id}` and `.../status` both answer the standard `{success: TRUE, data: …}` shape (`ApiResponseTrait::successResponse`), publish the persisted lifecycle value as the raw `PipelineStatus` value string under `data.status`, and answer **404** (`{success: FALSE, error}`) for a missing pipeline and **403** for a denied one. The full route adds `node_statuses`, `jobs`, `job_status_summary`, `execution_data` (plus `id`/`name`/`description`/`creat… ### [The execution id the editor polls is the pipeline id (SG-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592378) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: StateGraph/sync-pipeline execution id = pipeline entity id (frontend polls pipeline API). Both engines **overwrite** the caller's `OrchestrationRequest::pipelineId` with the id of the pipeline they created — a synthetic id (the request's own `pipeline_{workflow}_{time}_{rand}`, a uuid, the thread id) would 404 every poll and freeze the canvas at idle. Pairs with PIPE-4: the same response id polls a payload whose `node_statuses` keys are the canvas node ids. - **Implementation:** `StateGraphOrchestrator.php:199-201`; `SynchronousPipelineOrchestrator.php:161` - **Guaranteed by:** 2 tests (`Stat… ### [Exceeding the iteration budget throws (SG-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592377) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `StateManager::applyUpdate()`/`incrementIteration()` throw `MaxIterationsException` once the *new* `iterationCount` **exceeds** `maxIterations` (strictly greater — the budget's own iteration is allowed); `StateGraphOrchestrator::orchestrate()` catches it and returns an `OrchestrationResponse` with status exactly `max_iterations_exceeded`, empty `results`, and metadata `max_iterations` / `current_iterations` / `node_id`. It is a terminal verdict, not ORC-10's resumable pause: no checkpoint-resume handle is offered and the status is never `paused`. NB the loop's own `$iteration >= maxIterations`… ### [node_statuses is keyed by the workflow node id (PIPE-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592382) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: spec-registry, state::fixed Description: `node_statuses` is keyed by the **workflow node id** — the id the canvas holds, which is what the editor looks a badge up by. The key is `$job->getNodeId()` (job metadata `node_id`, stamped from the stored node's `id` at job generation), never the job entity id, the node-type id or an iteration-suffixed id: loop clones inherit the plain node id, so all of a node's iterations collapse onto one entry and the per-iteration picture rides inside it (`executions`, `status_counts`). `jobs[].node_id` carries the same ids, which is why the editor's per-job fallback resolves too. Only nodes that became … ### [A hidden output is stripped where it is produced (DATA-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592346) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Output stripping at the production point (= EXPO-11..14). - **Implementation:** — - **Guaranteed by:** — (cross-reference; GR-EXPO carries the tests) Rule `DATA-8` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [Inside a node, the parameter-resolution cascade decides (DATA-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592345) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: In-node precedence = CFG-4..6 chain. - **Implementation:** — - **Guaranteed by:** — (cross-reference; GR-CFG carries the tests) Rule `DATA-7` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [Launch data fills in under edge-delivered inputs (DATA-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592344) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `initialData[nodeId]` merges as fallback UNDER edge-delivered inputs (`array_merge`, so an edge-delivered NULL still wins); a non-array entry, or one keyed for another node, is ignored. - **Implementation:** `NodeRuntimeService.php:160-166` - **Guaranteed by:** `NodeRuntimeServiceInitialDataMergeTest` (5) Rule `DATA-6` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [Loopback and tool edges are dropped from data delivery (DATA-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592343) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Loopback edges (`*-input-loop_back`) and tool edges are dropped at **two** points. `buildDependencyGraph()` skips both, so they create no `dependent_jobs` reference and `validateDependencyGraph()` never raises "Circular dependency detected in workflow" for them; and `areJobDependenciesMet()` buckets loopback edges out of the checks and `continue`s past tool edges (`is_tool` flag OR an `-input-tool` target handle — `ReservedName::PORT_TOOL` — for jobs generated before the flag). Consequence: a node whose only incoming edges are loopback/tool has an empty `dependent_jobs` list and is promoted id… ### [Readiness promotes a job whose dependencies are met (DATA-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592342) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Readiness is evaluated in `getReadyJobs()`, which promotes a qualifying IDLE job to PENDING and **saves** it. Data-port readiness applies **only** to a job with zero incoming trigger edges (and only after the error-edge arm): with any trigger edge present, readiness is OR over triggers and data ports are ignored entirely, so a node can legitimately run with an unfilled data port. Otherwise: data edges are grouped by the extracted target port name (falling back to the raw target handle when it has no `-input-` marker), each group needs ≥1 completed **and branch-active** source (OR within a port… ### [A trigger edge carries no data (DATA-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592341) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Trigger edges carry no data. - **Implementation:** 2 sites - **Guaranteed by:** fixture Rule `DATA-3` of `RT-DATA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DATA-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592103 ### [One value per port, last executor wins (DATA-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592340) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Last-executor-wins, one value per port, never an array; ordering by `execution_order` desc, then a source *with* an order ahead of one without, then node-id strcmp; collision logs warning. ⚠ the strcmp fallback is reachable **only when neither source carries a positive order** — equal positive orders make the comparator return 0 and PHP's sort is stable, so that tie resolves to edge/parent declaration order, not alphabetically. ⚠ only the sort comparator is identical in the 3 input builders — the surrounding rules have drifted (sync lacks error-edge handling and adds a whole-output merge fallb… ### [Delivery is port to port, both names read from the handle (DATA-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592339) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Delivery is **port-to-port**: both port names come from splitting the handle on `-output-` / `-input-` (`{nodeId}-{direction}-{port}`), and if **either** handle lacks its marker the extracted name is NULL and the edge delivers nothing — silently, with no warning. Presence of the value is `array_key_exists($sourcePort, $sourceOutput)`, never `isset()`, so an explicitly emitted NULL IS delivered and reaches the resolver as Priority 1 (CFG-7) — **except on the StateGraph input builder, which gates with `isset()`, so a wire NULL is not delivered there** (documented divergence, see DATA-2). A sourc… ### [Direct sync skips a node whose trigger was never satisfied (BR-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592338) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Direct sync: a node with ≥1 incoming trigger edge and no satisfied trigger is **skipped, never executed**, and the skip is announced three ways carrying the *same* fixed reason `branch_not_active` — a `NodeSkippedEvent` (`reason:`), a real-time `ExecutionStatus::SKIPPED` update carrying `node_type_id` + `reason`, and `withNodeSkipped($nodeId, 'branch_not_active')` on the snapshot (landing as `metadata.skip_reason`). The node id also lands in the response's `metadata.skipped_node_ids` and is counted in `metadata.nodes_skipped`. ⚠ The reason is fixed even when the real cause is an unexecuted **n… ### [Staleness gates a branch decision, not delivery (BR-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592337) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Staleness gates only **branch decisions**, not delivery. For a trigger edge, an error edge, and a data edge leaving a **named port of a source that emitted `active_branches`**, a completed source job whose entity id is lower than that node's newest job id (any status) counts as not-completed, so the consumer stays not-ready and waits for its own iteration's job. An **unnamed** source port, or **any** source that emitted no `active_branches`, returns TRUE from `isEdgeBranchActive()` *before* the staleness check — so an ordinary data edge is still satisfied by the previous iteration's completed … ### [Branch gating applies to trigger and data ports alike (BR-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592336) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Branch gating applies regardless of target port kind (trigger or data). - **Implementation:** `JobGenerationService.php:1065+` - **Guaranteed by:** 2 stategraph suites Rule `BR-5` of `RT-BR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: BR-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592104 ### [A node's configured branches are the authority on branch ports (BR-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592335) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Branch-port authority = the node's configured `branches` `[{name,value}]`; entries without a non-empty **string** `name` are dropped by `normalize()` before anything else. Matching an outcome to a branch is type-aware, never a loose cast: a **boolean** outcome matches only a branch whose configured value *denotes* a boolean — a real bool, int `0`/`1`, or the strings `true`/`false`/`1`/`0` (case-insensitive) — a string-vs-string pair compares with `strcasecmp`, and anything else is identity (`===`). When **no** branch matches, `nameForValue()` returns the caller's **fallback literal** (`'true'`… ### [How active_branches is normalized (BR-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592334) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `active_branches` = list of strings; bare string is ONE name verbatim (no comma split); non-strings dropped; survivors trimmed + lower-cased. - **Implementation:** `:169-189` - **Guaranteed by:** `BranchActivationTest::testParse` + 2 `isActive` rows Rule `BR-3` of `RT-BR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: BR-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592104 ### [The three cases where a branch edge activates (BR-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592333) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Three deliberate TRUE cases, checked in this order and each returning before the membership test: an unnamed port (`$branchName === ''`); a source that emitted no (or an empty) `active_branches`; and a port that is a **value port**. Value-port authority is the source's configured `branches`, matched case-insensitively (`strcasecmp`); when the source declares **no** `branches` at all there is no authority and the fallback is the payload — a port whose name is a key in the source's output (`array_key_exists`, so a falsy or NULL value still counts) is taken for a value port. ⚠ That fallback is wr… ### [When a branch edge is gated at all (BR-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592332) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A branch edge is **gated at all** only when all three preconditions hold: the edge leaves a NAMED source port, the source emitted a non-empty `active_branches`, and that port is a branch port rather than a value port (BR-2/BR-4). Given those, the edge is followed iff `trim(strtolower($portName))` is in the parsed `active_branches` list — both sides trimmed and lower-cased — and otherwise not followed. In every other case the edge is followed, which is why the bare "iff" reading is false on its own: BR-2's three arms all return TRUE before membership is ever consulted. - **Implementation:** ga… ### [A cancelled run is announced like any other terminal outcome (ORC-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592331) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A CANCELLED run is announced like every other terminal outcome: every cancel path dispatches `PipelineCompletedEvent` carrying CANCELLED, exactly once per cancellation. The in-loop signal path (`AbstractOrchestratorBase::applyCancelSignal`, shared by all three loop engines) dispatches it after `ExecutionCancelledEvent` with the live execution id and stamped `execution_time_us`; the entity-level cancel paths (pipeline interaction form, trigger overlap Cancel/Terminate, session stop) announce via `PipelineCancellationAnnouncer` (execution id = pipeline id, duration from entity timestamps). `Pipe… ### [Claiming a job is atomic under concurrent workers (ORC-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592330) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Job claim/promotion is atomic under concurrent workers. Today: `getReadyJobs()` promote+`save()` is an unlocked, untransacted read-modify-write and `queuePipelineExecution()` enqueues with no dedup — two workers can execute the same job twice (side-effecting nodes fire twice). **Rule recorded, fix deliberately deferred** — FlowDrop currently documents a single-worker constraint rather than claiming safe concurrent execution. The cheap `:285` log-string-arg call hoist (state machine advanced to format a warning, redundant with `:259`) can land independently. - **Implementation:** `JobGeneratio… ### [Auto-resume is gated, not unconditional (INT-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592329) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Pause is NOT unconditionally held: auto-resume is gated on `PausedReason::budgetReasons()` (`time_budget`/`max_iterations` — async chunking *depends on* budget-pause→auto-resume→re-queue, maxIter 50 / maxTime 30.0); a **HITL/operator pause carries no reason and holds until explicit human resume** — absence-of-reason IS the HITL marker, do not add one. The async queue worker enforces both halves: it resumes and re-queues ONLY budget pauses; a reason-less pause is left paused. (REVERSES the decision-round T1-4 "pause holds identically on every engine" — that would stall every async run over 30s … ### [A terminal pipeline cannot be paused or resumed (INT-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592328) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A terminal pipeline (COMPLETED/FAILED/CANCELLED, `PipelineStatus::terminalStatuses()`) refuses re-entry: the sync-pipeline orchestrator throws `OrchestrationException` before touching it (async worker + the signal API already refuse), so cancel is durable — a rerun/requeue can never resurrect a dead run and re-fire side-effecting nodes. Re-running always means a NEW pipeline seeded with the source run's input and stamped `rerun_of` (`PipelineRerunService`), used by both operator rerun paths (rerun confirm form; interaction form's re-run buttons). - **Implementation:** refuse `SynchronousPipel… ### [A resume re-enters through the pipeline's declared orchestrator (ORC-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592327) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Interrupt resume re-enters through the pipeline's declared orchestrator, never the plain sync loop. - **Implementation:** `InterruptResolvedSubscriber.php:128-140` - **Guaranteed by:** parity test Rule `ORC-13` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-13` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592100 ### [An async launch returns queued immediately (ORC-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592326) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Async returns `"queued"` immediately; no in-request execution; optional snapshot seeding of pre-completed jobs. - **Implementation:** `AsynchronousOrchestrator.php:95-180` - **Guaranteed by:** `AsynchronousOrchestratorQueuedResponseTest` (queued response + no in-request node execution; the snapshot seeding leg is INT-10) Rule `ORC-12` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-12` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592100 ### [How a run's terminal status is decided (ORC-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592325) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Terminal status precedence: unhandled-failure→FAILED(+SKIPPED rest); interrupted→PAUSED(no reason); ready-remaining→PAUSED(+reason); else COMPLETED. CANCELLED never reaches this chain by design: a cancel signal exits through the signal path before it, announced there (ORC-15). The two ladders are not identical: only the stategraph ladder has an explicit `hasInterruptedJobs()` arm — on the sync-pipeline engine an interrupt leaves the ladder entirely through the `InterruptExceptionInterface` catch (which pauses the pipeline and returns INTERRUPTED), which is why that ladder has three arms and st… ### [An iteration and time budget breaks the loop (ORC-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592324) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Budget: maxIterations (default 100) + maxExecutionTime break the loop → PAUSED + `paused_reason` → pending system Pause signal → resumable with fresh budget; re-entry clears stale reason. - **Implementation:** 2 orchestrators + `ExecutionConfig` - **Guaranteed by:** `StateGraphBudgetPauseResumeTest` (3) Rule `ORC-10` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-10` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592100 ### [A pipeline engine is a ready-job loop (ORC-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592323) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Pipeline engines are ready-job loops. `getReadyJobs()` flips every IDLE job whose dependencies are met to PENDING **and persists it** (`markAsPending()` + `save()`), then returns **all** PENDING jobs — including ones already pending from an earlier pass — sorted **ascending by `getPriority()`** (lower number runs first). A job with unmet dependencies is left IDLE, untouched. The engines call it repeatedly and stop when it returns an empty array: that empty return **is** what "quiescent" means, and re-entering a node across passes is what makes loops possible. - **Implementation:** `JobGenerat… ### [Direct sync filters which trigger node starts the run (ORC-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592322) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Direct sync trigger filtering: `initialData['trigger_node_id']` selects one trigger; other trigger nodes dropped. Opt-in: without the key the compiled order is used verbatim (a manual/REST launch has no firing trigger to privilege), and non-trigger nodes are never filtered. - **Implementation:** `:242-271` - **Guaranteed by:** 2 tests (`SynchronousOrchestratorTest`) Rule `ORC-8` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent is… ### [Direct sync walks the execution order once (ORC-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592321) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Direct sync walks `ExecutionGraph::getExecutionOrder()` **once**, top to bottom, carrying results in an in-request context. It never re-queues or re-enters a node, so **each node executes exactly once per run and a loopback edge produces no second iteration** — a loop drawn on the canvas is inert on this engine. Loops require a pipeline engine (ORC-9). - **Implementation:** `SynchronousOrchestrator.php:254` (order), single `foreach` `:297-502` with no re-scheduling - **Guaranteed by:** `SynchronousOrchestratorTest::testLinearWorkflowExecutionOrder`, `::testLoopbackEdgeDoesNotProduceASecondIte… ### [Every strategy shares one contract and one hierarchy (ORC-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592320) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Common contract in a shared hierarchy: every strategy (direct sync included) extends the job-free `AbstractOrchestratorCore` (pipeline storage resolution, pipeline creation, interrupt handling, error-edge payload shape); the job strategies additionally share `AbstractOrchestratorBase` (NodeRuntimeService execution, retry, error routing, stop handling, signal polling, JobCompletedEvent, snapshots). - **Implementation:** both classes - **Guaranteed by:** `OrchestratorHierarchyContractTest` (structural: the shared members are asserted to be *inherited*, not merely callable) Rule `ORC-6` of `RT-… ### [Capability queries are answered from the plugin definition only (ORC-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592319) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Capability queries are definition-driven, and ONLY definition-driven: `OrchestratorHelper::hasCapability()` reads the `Orchestrator` attribute's `capabilities` list off the plugin definition — `isStateGraph()` = `stateful`, `isSynchronous()` = `synchronous_execution` && !`stateful` — and those verdicts gate real behavior (checkpoint storage selection `SessionExecutionService::715`, pipeline form branches). The former *method* API (`supportsWorkflow()`/`getCapabilities()`) was decorative — constant returns, zero production callers — and was deleted in 2.x; the attribute list is the single sourc… ### [StateGraph is the session default, not the global one (ORC-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592318) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: STATEGRAPH is the session/playground default, not global: `SessionExecutionService` passes it as the *caller* default to `getInstanceFromSettings()`, so it applies only when the session/workflow declared no engine, and the global chain (ORC-2) never resolves to it. - **Implementation:** `SessionExecutionService.php:686,715` - **Guaranteed by:** `SessionExecutionServiceOrchestratorDefaultTest` + `OrchestratorDefaultResolutionTest` Rule `ORC-4` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-4` token, and `scripts/spec-coverage… ### [An unknown orchestrator type falls back with a warning (ORC-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592317) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unknown type falls back with warning; missing fallback → `\RuntimeException`. - **Implementation:** `:73-100` - **Guaranteed by:** `OrchestratorDefaultResolutionTest` Rule `ORC-3` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592100 ### [How the default orchestrator is resolved (ORC-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592316) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Default resolution: presave→SYNC; else trigger settings; else flowdrop settings; else ASYNC. Each configured step must `validate()` before it is accepted, so an uninstalled engine cannot capture the default. Shipped: flowdrop=sync, trigger=async. - **Implementation:** `OrchestratorHelper.php:118-142` - **Guaranteed by:** `OrchestratorDefaultResolutionTest` Rule `ORC-2` of `RT-ORC` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ORC-2` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592… ### [The four orchestrator strategies and their ids (ORC-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592315) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Four strategies, each returning its namespaced plugin id verbatim from `getType()`. The `OrchestratorHelperInterface` constants are the single source of those strings: `SYNCHRONOUS = flowdrop_runtime:synchronous`, `SYNCHRONOUS_PIPELINE = flowdrop_runtime:synchronous_pipeline`, `ASYNCHRONOUS = flowdrop_runtime:asynchronous`, `STATEGRAPH = flowdrop_stategraph:stategraph`. - **Implementation:** `OrchestratorHelperInterface.php:37,45,53,62` - **Guaranteed by:** `SynchronousOrchestratorTest::testGetType`, `FlowDropRuntimeIntegrationTest::testOrchestratorType` (sync + sync_pipeline), `AsynchronousE… ### [Every orchestrator routes an error result identically (DECIDED) (ERR-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592314) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **All orchestrator strategies route error Outputs identically** (DECIDED ← OPEN-1): error edge present → the node's outputs are replaced by the shared `{error:{message,code,node_id,retryable}}` envelope and the run continues (ERR-7); no error edge → the run fails (ERR-8). Direct sync included. - **Implementation:** `SynchronousOrchestrator.php:404-411,850-902` - **Guaranteed by:** 2 tests (`SynchronousOrchestratorErrorRoutingTest`) Rule `ERR-13` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-13` token, and `scripts/spec-cove… ### [Remove the direct-sync record-and-continue divergence (ERR-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592313) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: *(collapsed into ERR-13)* The direct sync record-and-continue divergence is removed: the orchestrator inspects `Output::isError()` and applies ERR-13 like every other strategy. - **Implementation:** `SynchronousOrchestrator.php:404-411` - **Guaranteed by:** — (superseded by ERR-13) Rule `ERR-12` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-12` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [Retry is in-place, immediate and opt-in (ERR-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592312) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Retry: in-place, immediate, no backoff, opt-in (`max_retries` default 0), only `error_retryable`, counter persisted; idempotence is the author's contract. - **Implementation:** `AbstractOrchestratorBase.php:353-379` - **Guaranteed by:** 3 tests Rule `ERR-11` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [A routed-failed node satisfies only its error edges (ERR-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592311) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A routed-failed node satisfies only error edges (evaluated before trigger/data, OR semantics, staleness applies); success-path successors never ready. - **Implementation:** `JobGenerationService.php:676-689,812-847` - **Guaranteed by:** 5 tests (`JobGenerationServiceTest`: routed/unrouted, precedence over the trigger rule both ways, OR, staleness) Rule `ERR-10` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-10` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [A pipeline whose only failures were routed still completes (ERR-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592310) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A pipeline whose only FAILED jobs carry `error_routed` finishes with status `completed`. The verdict is computed from `hasUnhandledFailedJobs()` — TRUE iff some FAILED job's metadata lacks `error_routed === TRUE` — never from `hasFailedJobs()`; one unrouted failure alongside any number of routed ones still fails the run. A routed-failed job also dispatches `JobCompletedEvent` (the generic "job finished" channel), so per-node subscribers see it and discriminate on `getStatus()`. - **Implementation:** `:962-969`; routed dispatch `:938` - **Guaranteed by:** 2 tests (routed-only run completes; a … ### [An error result with no error edge fails the run (ERR-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592309) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: No error edge → `NodeProcessingException`, job FAILED without `error_routed`, run fails. - **Implementation:** `:249-251,317-330` - **Guaranteed by:** Rule `ERR-8` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [An error result with an error edge routes instead of failing the run (ERR-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592308) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Error-edge routing (pipeline engines): error Output + ≥1 error edge → job FAILED + `error_routed`, output becomes `{error:{message,code,node_id,retryable}}`, run continues. - **Implementation:** `AbstractOrchestratorBase.php:231-239,889-924` (payload shape shared via `AbstractOrchestratorCore::buildErrorEdgePayload`) - **Guaranteed by:** 2 suites Rule `ERR-7` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [An unserializable output fails the node (ERR-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592307) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: After unexposed outputs are filtered and the unified `output` port is composed, `assertSerializableOutput()` rejects any leaf that is not scalar/null/array/stdClass/`JsonSerializable` with `NonSerializableOutputException` naming the node id, the plugin id, the dotted path and the offending type. Because it is a `\RuntimeException` thrown inside the processor try block it becomes an error-status Output carrying that message with **no** `error_retryable` metadata (so it never retries and follows the normal error-edge-or-fail path). ⚠ Because the check runs *after* filtering, a non-serializable v… ### [A stop request bypasses the error catch and stops the run cleanly (ERR-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592306) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `WorkflowStopException` extends `\Exception`, so it bypasses the inner error-Output catch; `NodeRuntimeService` catches it in a clause placed *before* the generic `\Exception` clause and re-throws the SAME instance after broadcasting real-time `completed` for the node — were the ordering reversed the stop would be re-wrapped into a `RuntimeException` and fail the run. The orchestrator then marks the job COMPLETED (never FAILED), records `getResult()` under the node's result key, abandons downstream and unscheduled sibling jobs, and finishes the run with status `completed`. - **Implementation:… ### [An interrupt is re-thrown unchanged (ERR-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592305) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `InterruptExceptionInterface` re-thrown unchanged after event dispatch + `interrupted` status. - **Implementation:** `:276-311` - **Guaranteed by:** 2 tests (same instance re-thrown, event payload, no subscriber) Rule `ERR-4` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [Any other exception fails the node and is re-thrown wrapped (ERR-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592304) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Non-RuntimeException `\Exception` escapes, node FAILED, re-thrown wrapped — fails the run, does NOT take the error edge. - **Implementation:** `:326-344` - **Guaranteed by:** 2 tests (wrapped re-throw + cause; no Output exists, so nothing can route) Rule `ERR-3` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592097 ### [A retryable exception stays recognisable after it is caught (ERR-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592303) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `RetryableExceptionInterface` survives type erasure as `error_retryable` metadata: when the caught `\RuntimeException` implements the marker the error Output carries `error_retryable` = TRUE; otherwise the key is **absent** (`getMetadata('error_retryable')` returns NULL, never FALSE). The absence is load-bearing — the retry gate is a strict `!== TRUE` check, so anything other than the literal TRUE marker is treated as non-retryable. - **Implementation:** marker `:236-238`; strict gate `AbstractOrchestratorBase.php:360-364` - **Guaranteed by:** 2 tests (marker present/absent, asserted on the O… ### [A RuntimeException from a processor becomes an error result (ERR-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592302) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `\RuntimeException` from a processor is caught → error-status Output; never propagates (the error-edge channel). The real-time broadcast for a converted failure is `completed`, not `failed` — the node finished; the error verdict rides the Output. - **Implementation:** `NodeRuntimeService.php:228-239` - **Guaranteed by:** `NodeRuntimeServiceErrorChannelTest` (3) Rule `ERR-1` of `RT-ERR` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: ERR-1` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: … ### [A node mapping carries both the processor and the node-type id (CMP-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592301) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `NodeMapping` carries both `processorId` and `nodeTypeId`; runtime loads entities by nodeTypeId. - **Implementation:** `:734-765` - **Guaranteed by:** Rule `CMP-11` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [A tool consumer must declare that it accepts tools (CMP-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592300) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Tool consumer must implement `ToolsAwareInterface` or compile error. - **Implementation:** `:356-361` - **Guaranteed by:** Rule `CMP-10` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-10` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [Tool names must be unique per consumer at compile time (CMP-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592299) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Tool-name uniqueness per consumer over flattened leaf set at compile time; collision → `CompilationException`; passthroughs exempt/checked at consumer. - **Implementation:** `:290-362` - **Guaranteed by:** (3 + ToolBox suite) Rule `CMP-9` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-9` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [Execution order is a topological sort (CMP-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592298) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Order = Kahn toposort; ties broken by definition order (artifact, not id). - **Implementation:** `:663-697` - **Guaranteed by:** (independent roots + tied fan-out siblings; the test records this as an artifact authors may not lean on) Rule `CMP-8` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [A trigger dependency outranks a data dependency for ordering (CMP-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592297) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Trigger deps beat data deps for ordering (`executionDeps = triggerDeps ?: dataDeps`). - **Implementation:** `:410-430` - **Guaranteed by:** `topology-trigger-priority-over-data.yml` Rule `CMP-7` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [Which nodes are excluded from the execution graph (CMP-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592296) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Exclusion precedence: NonExecutable always out; tool-only out; rootless-in; loopback-only-in out; edge-free node IS executed. - **Implementation:** `:494-561` - **Guaranteed by:** (3 cases) Rule `CMP-6` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [Cycle detection ignores the edges that are meant to loop (CMP-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592295) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Cycle detection excludes `tool_availability`/`loopback`/`agent_result`; loopback+tool cycles legal; any other cycle → hard error. - **Implementation:** `:208-273` - **Guaranteed by:** (5 cases) Rule `CMP-5` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [Edge type is derived from handles, never declared (CMP-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592294) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Edge type derived from handles, never declared (= EDGE-3..6). - **Implementation:** `DependencyEdge.php:23-137` - **Guaranteed by:** Rule `CMP-4` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592102 ### [Compile preconditions run first, in a fixed order (CMP-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592293) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Preconditions run first inside the compile try-block, in this order, the first failure throwing `CompilationException`: empty id → `Workflow must have an ID`; zero nodes → `Workflow must have at least one node`; then per node in definition order, missing id → `All nodes must have an ID`, missing type → `Node {id} must have a type`. Each reaches the caller prefixed by CMP-1's wrap. - **Implementation:** `:175-194` - **Guaranteed by:** (4 cases) Rule `CMP-3` of `RT-CMP` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CMP-3` token, and `scripts… ### [Re-enrichment on the run path is conditional (CMP-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592292) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Run-path re-enrichment from the live node types (= SCH-29) is **conditional, not a property of compilation**: it happens only on `compile()`'s **array** entry point and only when a `NodeMetadataResolver` was injected; handing `compile()` a pre-built `WorkflowDTO` skips it entirely. Every DTO-building caller therefore enriches first — `SynchronousOrchestrator:215-219` and `JobGenerationService:113-118` do, and `StateGraphOrchestrator:1674-1678` (which builds a DependencyGraph directly, never calling the compiler) does too. Without a resolver the (attacker-controllable) stored metadata cache is … ### [What compiling a workflow produces (CMP-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592291) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Compile = DependencyGraph (all edges) + ExecutionGraph (runnable nodes) + NodeMappings, produced in this stage order inside one try-block: structure preconditions (CMP-3) → dependency graph → cycle detection (CMP-5) → tool wiring (CMP-9/10) → execution graph (CMP-6/8) → node mappings (CMP-11). **Any `\Exception` from any stage — a `CompilationException` from an inner stage included — is logged at error and re-thrown as a NEW `CompilationException`** with message `'Workflow compilation failed: ' . $previous->getMessage()`, code `0`, and `getPrevious()` set to the original. So a caller always se… ### [One expression-error policy across every engine (DECIDED) (LANG-29)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592290) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **Uniform expression error policy** (DECIDED ← OPEN-8): an expression *error* — a path the engine cannot evaluate, an engine throwable — is wrapped in `\RuntimeException` → node fails → error-edge routing. IMPLEMENTED across all four expression-consuming processors: DataMapper (LANG-21), DataExtractor (LANG-22), DataShaper (LANG-25), PromptTemplate (LANG-26). **Scope is errors, not empty results:** an expression that evaluates cleanly and finds nothing is not a failure, so DataExtractor's `default` + `success: FALSE` soft-miss (LANG-24) is deliberately untouched by this policy — "expression er… ### [The six operators the if/else gateway declares (LANG-28)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592289) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: IfElse declares six operators (`equals`, `not_equals`, `contains`, `starts_with`, `ends_with`, `regex`) as a schema `enum` **only** — there is no IfElse-specific validator. The enum is enforced generically by `WorkflowValidator::validateConfigValue()` at save (`CONFIG_INVALID`) and by CFG-10 at resolution. There is **no** save-time check that `matchText` is a compilable regex: an uncompilable pattern surfaces at runtime as `InvalidNodeConfigurationException('Regex execution failed for pattern: …')`, and an operator reaching `process()` outside the enum throws `InvalidNodeConfigurationException… ### [The switch gateway matches a branch value instead of evaluating it (LANG-27)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592288) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: SwitchGateway does not evaluate `expression`: the first branch whose `value` is `===`-identical to it wins (no coercion, no engine) and its **name** is emitted as the single element of `__active_branches__`. No match falls back to `default_branch`. The guard is `empty($activeBranch)`, not a NULL check, so it ALSO throws `InvalidNodeConfigurationException("No active branch found for expression: ")` when a branch DID match but its name is falsy (`"0"`, `""`). The `input_value` output is always NULL — the matched value is never echoed. - **Implementation:** `SwitchGateway.php:55-85`; match loop … ### [A prompt template turns a Twig error into a node failure (LANG-26)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592287) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: PromptTemplate: any `Twig\Error\Error` from rendering (SyntaxError/RuntimeError/LoaderError) is caught and re-wrapped as `\RuntimeException` chaining the original → the node FAILS → error-edge routing (LANG-29 policy). - **Implementation:** `PromptTemplate.php:131-145` - **Guaranteed by:** `PromptTemplateTest` Rule `LANG-26` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-26` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [DataShaper resolves its five sentinels before consulting an engine (LANG-25)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592286) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: DataShaper resolves **five** sentinels before the engine is consulted: `_NOW_` → an ATOM-formatted timestamp, `_NULL_` → NULL, `_EMPTY_ARRAY_` → `[]`, `_EMPTY_OBJECT_` → `new \stdClass()`, and the `_LITERAL:` prefix → the remaining substring verbatim. Every sentinel increments `mappedFields`, **including `_NULL_`** — `resolveSpecialValue()` returns the wrapper `['value' => NULL]`, which is itself non-NULL, so the counter is bumped before the value is unwrapped; only a NULL from an expression that actually reached the engine goes uncounted. Any throwable from a source expression that does reach… ### [A NULL extraction is a soft miss, never an error (LANG-24)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592285) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: DataExtractor: a **NULL** extraction is a soft-miss, never an error — the configured `default` is substituted and `success` = FALSE means "no non-NULL match found"; the node succeeds. Extraction engines cannot distinguish a legit stored NULL from a no-match (LANG-8), so both take the default. Only NULL trips the soft-miss: FALSE/0/"" are delivered as success. This is live shipped behaviour, not a legacy remnant — the `default` config value and the `success` output port both survive LANG-29 unchanged, and the port's own description still reads "FALSE means the configured default was delivered" … ### [DataExtractor unwraps a first match only for JSONPath (LANG-23)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592284) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: DataExtractor first-match unwrapping keys off the ENGINE: only jsonpath running a `$`-query reduces an array result to its first match (`extract_all` FALSE); property_path (any non-jsonpath engine) delivers array results whole, even for `$`-prefixed paths, and the jsonpath property-path fallback route (non-`$`) never unwraps. The `is_jsonpath` output flag remains a `$`-prefix sniff report — a routing/reporting hint independent of the engine. - **Implementation:** `:105,136-153` - **Guaranteed by:** (3 cases) Rule `LANG-23` of `GR-LANG` in `docs/development/specification-registry.md`. Tests b… ### [DataExtractor re-wraps any evaluator throwable as a RuntimeException (LANG-22)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592283) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: DataExtractor: any evaluator throwable is re-wrapped as `\RuntimeException` naming the path and engine → the node FAILS → error-edge routing (same policy as DataMapper, per LANG-29). Scope is expression *errors* only (invalid path, engine error): the configured `default` never applies on an error, but it is untouched for the soft-miss case (LANG-24), which still substitutes it and still succeeds. What went away is the `{success: FALSE, error}` envelope an error used to produce (`error` was never a declared output port) — not default-on-no-match. - **Implementation:** `DataExtractor.php:118-13… ### [DataMapper re-wraps only a RuntimeException from an evaluator (LANG-21)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592282) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: DataMapper catches only `\RuntimeException` from `evaluate()` and re-wraps it as `\RuntimeException("Expression error in dynamic output '': …")`, aborting `process()` so no partial output map is returned. Unlike DataShaper/DataExtractor (which catch `\Throwable`), a non-`\RuntimeException` throwable — e.g. a `\TypeError` from an engine — escapes **unwrapped**, without the port name, and because both orchestrators catch only `\Exception` it is not converted into a node failure / error-edge route at all. - **Implementation:** `DataMapper.php:126-136` (`catch (\RuntimeException`) vs `DataShaper.… ### [What exists() answers for an empty path and for a scalar (LANG-20)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592281) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `exists('')` = TRUE; `exists()` on scalar+property-path = FALSE. - **Implementation:** `:149-164` - **Guaranteed by:** Rule `LANG-20` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-20` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [Extracting all matches on a property path wraps the single result (LANG-19)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592280) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `extractAll()` on property path wraps single result; NULL and no-match collapse to `[]`. - **Implementation:** `:127-131` - **Guaranteed by:** Rule `LANG-19` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-19` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [How a mapping value is marked as a literal instead of an expression (LANG-18)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592279) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `applyMappings()` literal escapes: `literal:x`, `"x"`, `'x'` bypass extraction (trigger mappings only). - **Implementation:** `:178-193,394-422` - **Guaranteed by:** Rule `LANG-18` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-18` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [Dot-to-bracket normalization is duplicated in three classes (LANG-17)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592278) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Dot→bracket normalization duplicated in THREE classes (JsonPathService, PropertyPathEvaluator, plus undocumented copy in GetWorkflowData) — currently in agreement, drift risk. - **Implementation:** 3 sites - **Guaranteed by:** (service side only) Rule `LANG-17` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-17` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [A string context is decoded as JSON when it is JSON (LANG-16)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592277) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: String context auto-json_decoded; non-JSON string passes through; `"null"` decodes to NULL. - **Implementation:** `:328-338` - **Guaranteed by:** 3 fixtures (`lang-jsonpath-*-context*.yml`) Rule `LANG-16` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-16` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [A single JSONPath match is unwrapped unless the path is multi-value (LANG-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592276) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Arity collapse: single match unwrapped unless path is "multi-value" (sniffed for `[*] [? .. [n:m]`); a filter matching one item stays an array. - **Implementation:** `:243-247,376-383` - **Guaranteed by:** Rule `LANG-15` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-15` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [A path is JSONPath when it starts with $ (LANG-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592275) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Path is JSONPath iff trimmed string starts `$`; else property path. - **Implementation:** `JsonPathService.php:198-200` - **Guaranteed by:** Rule `LANG-14` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-14` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [Twig validation is compile-only (LANG-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592274) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Twig `validate()` is compile-only; runtime-only failures validate TRUE. - **Implementation:** `TwigEvaluator.php:124-130` - **Guaranteed by:** `lang-twig-validate-compile-only.yml` Rule `LANG-13` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-13` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [JSONPath validation accepts anything that is not a $ path (LANG-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592273) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: jsonpath `validate()` returns TRUE unconditionally for non-`$` paths. - **Implementation:** `JsonPathEvaluator.php:97-102` - **Guaranteed by:** `lang-jsonpath-validate-non-dollar-unconditional.yml` Rule `LANG-12` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-12` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [Property-path validation delegates to the same parser (LANG-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592272) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: property_path `validate()` delegates to the same PropertyAccess parse `evaluate()` feeds (after dot→bracket normalization), so its accept-set is a superset of what `evaluate()` can resolve (e.g. `[user-name]` validates AND resolves); only paths PropertyAccess itself cannot parse (unclosed bracket, empty segment) validate FALSE. R11's LANG-11 gate is cleared. - **Implementation:** `:82-96` - **Guaranteed by:** `lang-property-path-validate-evaluate-agree.yml` Rule `LANG-11` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-11` … ### [Expression Language validation accepts unknown variable names (LANG-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592271) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: EL `validate()` pre-declares all identifiers → unknown variables validate OK, throw at runtime. - **Implementation:** `:94-100` - **Guaranteed by:** `lang-el-validate-predeclares-unknowns.yml` Rule `LANG-10` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-10` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [JSONPath never throws, and has three distinct outcomes (LANG-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592270) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: jsonpath never throws, and there are **three distinct outcomes**, not one: (1) a `$`-query that compiles but matches nothing returns the caller's `default` (NULL through the evaluator) with **no log entry**; (2) any `\Throwable` from compiling or running the query logs `warning: "JSONPath query failed for '': …"` and returns the default; (3) on the non-`$` property-path fallback route, `AccessException`/`UnexpectedTypeException` return the default **silently**, and only other throwables log `"Property path extraction failed …"`. Absence of a warning therefore does not mean the path was valid. … ### [A property path never throws; an unreadable path is NULL (LANG-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592269) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: property_path: never throws; unreadable path → NULL (indistinguishable from legit NULL). - **Implementation:** `PropertyPathEvaluator.php:59-74` - **Guaranteed by:** 3 fixtures (`lang-property-path-*.yml`, `lang-missing-key-divergence.yml`) Rule `LANG-8` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [Twig renders a missing variable as an empty string (LANG-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592268) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Twig: a missing variable renders silently as `''`; the result is always a string, HTML-escaped unless piped through `\|raw`. Twig is **not** failure-free: `SyntaxError` → `\RuntimeException('Twig syntax error: …')` and `RuntimeError` → `\RuntimeException('Twig runtime error: …')`, both chaining the original. No other throwable is caught (`LoaderError` and `\Error` propagate raw), so the failure surface is exactly those two arms. - **Implementation:** `TwigEvaluator.php:88-113` - **Guaranteed by:** 5 fixtures (`lang-twig-*.yml` incl. `lang-twig-syntax-error.yml`, `lang-missing-key-divergence.y… ### [Expression Language reports a syntax error, and a missing variable is one (LANG-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592267) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: EL: SyntaxError → "Expression syntax error: …" (a **missing variable IS a SyntaxError** to Symfony EL, so it takes this arm); any other throwable → "Expression evaluation error: …" — either way it **throws**. - **Implementation:** `ExpressionLanguageEvaluator.php:66-82` - **Guaranteed by:** 3 fixtures (`lang-el-*.yml`, `lang-missing-key-divergence.yml`) Rule `LANG-6` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592… ### [Expression validation has exactly one production call site (LANG-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592266) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Evaluator `validate()` has exactly ONE production call site — the save-time `WorkflowValidator` (R11); `getSyntaxHint()` still has zero. A second validate() caller or a vanished validator call goes red so the surface never drifts silently again. - **Implementation:** grep-verified - **Guaranteed by:** `ExpressionValidateCallSiteTest` (2 tests) Rule `LANG-5` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [A non-array context is wrapped for the template engines (LANG-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592265) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Non-array context wrapped as `['data' => ctx]` for EL/Twig. - **Implementation:** 2 sites - **Guaranteed by:** `lang-scalar-context-wrapping.yml` Rule `LANG-4` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [What an empty expression evaluates to, per engine (LANG-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592264) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Empty expression at the **evaluator** level: `expression_language`/`twig` → NULL; `property_path`/`jsonpath` → context unchanged (divergent polarity!), and all four `validate('')` TRUE. No author can observe that divergence through the shipped nodes: both consumers short-circuit before it — DataMapper maps an empty output expression to NULL whatever the engine (`DataMapper.php:121-124`), and DataExtractor returns `{data: , success: TRUE, is_jsonpath: FALSE, match_count: 0}` for an empty `path`, resolving the evaluator but never calling `evaluate()` (`DataExtractor.php:104-116`). The polarity i… ### [Getting an evaluator never lets a plugin-manager failure escape (LANG-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592263) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `ExpressionEvaluatorAwareTrait::getEvaluator()` wraps any plugin-manager failure as `\RuntimeException("Unknown expression engine '': …")` before any evaluator runs. On a real node this is a *second* line of defence: DataMapper/DataExtractor/DataShaper declare `engine` with `enum: getAvailableEngineIds()`, so an out-of-set value is refused earlier — at save by `WorkflowValidator` (`CONFIG_INVALID`) and at resolution by CFG-10 as `ParameterValidationException`. The `\RuntimeException` is what a caller bypassing the schema (direct trait use, tool invocation) sees. - **Implementation:** `Express… ### [Extraction engines query context; transformation engines see a variable map (LANG-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592262) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Extraction engines treat context as data-to-query; transformation engines as a variable map. - **Implementation:** `ExpressionEvaluatorInterface.php:34-37` - **Guaranteed by:** `lang-context-family-split.yml` Rule `LANG-1` of `GR-LANG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: LANG-1` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592090 ### [Refuse a synchronous launch of an async-declared workflow (MAN-19)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592261) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `wait: TRUE` against an async-declared workflow refused before pipeline creation. - **Implementation:** `WorkflowLauncher.php:74-81` - **Guaranteed by:** Rule `MAN-19` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-19` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [The manifest is rebuilt only when the declared ports change (MAN-18)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592260) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Rebuild is *triggered* only when `input_ports` or `output_ports` differ from the original, or `$forced`; `isSyncing()` (config import) returns before any work, so an import never bumps a version — and a change inside a source plugin's fragment never triggers a rebuild, leaving the snapshot stale until something else does. An empty port list stores `NULL` for that side's schema. Version: any of major/minor/patch from `0.0.0` yields `1.0.0`; otherwise the named digit bumps and the lower ones reset. `none` writes the schemas and logs a `debug`, leaving `schema_version` untouched. A builder throw … ### [A declared output reads from its node's result (MAN-17)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592259) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Output side: `outputs[name] = results[node_id][port]`; presence is `array_key_exists`, so a NULL value counts as produced; produced-nothing → dropped with warning (composes with EXPO-13); malformed entries skipped silently. - **Implementation:** `WorkflowSchemaResolver.php:97-126` - **Guaranteed by:** 4 tests Rule `MAN-17` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-17` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [Launch inputs are checked against the manifest snapshot (MAN-16 (G4))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592258) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Values checked against snapshot fragments via the shared `SchemaFragmentChecker`, and only `type` and `enum` are **enforced**; ⚠ every other snapshot key (`minimum`,`maximum`,`minLength`,`maxLength`,`pattern`,`required`, nested `properties`/`items`) is **declared** in the published contract but never checked, as is a non-string/union `type`. No coercion; structured kinds (`object,array,list,map,json`) all collapse to `is_array`, and `enum` compares with strict `in_array` (so `1` ≠ `"1"`). Per-value violations aggregate into one `InvalidLaunchInputException` joined by `; `; a name with no fragm… ### [Input checking short-circuits at the first failing stage (MAN-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592257) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `WorkflowInputChecker::check()` short-circuits at the first failing stage (unknown keys → missing required → per-value) and returns one message; the launcher wraps it in `InvalidLaunchInputException`. Every message appends `Known inputs: …` (or `This workflow accepts no inputs.`). ⚠ **Product gap:** the missing-required stage reads `required` off the *manifest entry* (`NodePort::fromArray($port)->required`) — a key the authoring form never writes and the `flowdrop_workflow.port_exposure` config schema does not define, **so via the UI every declared input is optional at launch**. The snapshot f… ### [A malformed manifest entry is dropped with a warning, even in strict mode (MAN-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592256) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Malformed manifest entries dropped-with-warning even in strict mode (strict polices the *caller*, not the stored manifest). An empty `node_id`/`port` drops the same way. - **Implementation:** `:74-86` - **Guaranteed by:** 2 tests Rule `MAN-14` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-14` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [Strict mode refuses an undeclared input by name (MAN-13 (G3))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592255) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `strict: TRUE` (launcher) throws `\InvalidArgumentException` naming the offending key and the workflow; lenient (session) drops it and logs a `warning` carrying `not a declared input name` and `@name` — never silently. In **both** modes the value is never written into the returned `initialData` (the `continue` precedes every write). ⚠ Amended by API-2: the lenient session mode is slated for **deletion**; strict becomes the only externally reachable behavior. - **Implementation:** `:54-72` - **Guaranteed by:** 2 tests Rule `MAN-13 (G3)` of `GR-MAN` in `docs/development/specification-registry.… ### [Node-keyed pass-through is an internal contract (MAN-12 (G2))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592254) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Node-keyed pass-through is an internal contract (session/chat_input); the public launch boundary refuses it. ⚠ Amended by API-2: the session door today `array_merge`s **raw caller input** into this internal shape (`SessionExecutionService.php:639-642`) — the "internal" framing only holds once API-2 lands and the pass-through is unreachable from outside. - **Implementation:** `:45-52`; launcher `:219-224` - **Guaranteed by:** 3 tests (pin the launcher side; the session leak is API-2's ❌) Rule `MAN-12 (G2)` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a gr… ### [A named input resolves to its node and port (MAN-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592253) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Named input resolves to `initialData[node_id][port]`. - **Implementation:** `:33-36` - **Guaranteed by:** Rule `MAN-11` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [A declared manifest name wins over the node-keyed pass-through (MAN-10 (G1))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592252) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Declared manifest names win over node-id pass-through. - **Implementation:** `WorkflowSchemaResolver.php:41-44` - **Guaranteed by:** `::testDeclaredNameWinsOverNodeIdPassThrough` Rule `MAN-10 (G1)` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-10 (G1)` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [A workflow used as a node exposes its manifest, with a cycle guard (MAN-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592251) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Workflow-as-port composition: cycle guard keyed on workflow id → `{type:object, properties:{}}` + warning; sibling re-entry allowed. - **Implementation:** `:57-66,102-103` - **Guaranteed by:** 2 tests Rule `MAN-9` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-9` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [An unresolvable manifest entry is dropped from the snapshot (MAN-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592250) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: *Unresolvable* entries (node missing, plugin missing, port not declared by the plugin) skipped with log warning. ⚠ A *structurally malformed* entry (missing/empty `name`/`node_id`/`port`) is skipped **silently** — the shape guard logs nothing. - **Implementation:** `:73-96,276-330` - **Guaranteed by:** 4 tests (incl. the silent-skip divergence) Rule `MAN-8` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [Which default values survive into the manifest snapshot (MAN-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592249) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `default` survives when it is NULL, scalar, or a one-level array whose every element is scalar/NULL (an empty array included). An *object* default survives only when it has public vars, and is stored as `get_object_vars()` — i.e. coerced to an array; an empty object and any nested value are dropped, logging `Default value dropped from schema snapshot (unsupported shape).` while every other contract key of the fragment is retained. - **Implementation:** `:212-237` (`sanitiseDefault`), drop site `:139-147` - **Guaranteed by:** 4 tests Rule `MAN-7` of `GR-MAN` in `docs/development/specification… ### [Author metadata overlays the plugin annotations and wins (MAN-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592248) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Author metadata overlaid after stripping, wins over plugin annotations, input direction only; empties dropped. - **Implementation:** `:177-200` - **Guaranteed by:** 3 tests Rule `MAN-6` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [A manifest snapshot is built from the plugin fragment and stripped (MAN-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592247) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Snapshot built per entry from the plugin fragment, stripped by `pickContractKeys()` to exactly `type,enum,format,default,required,properties,items,minimum,maximum,minLength,maxLength,pattern` — every other key dropped **at every depth**, recursing into `properties[*]` and `items`. So plugin annotations (`title`,`description`,`examples`) and `x-*` extensions never reach the stored snapshot; annotations are re-attached at read time only (`?annotated=1`, MAN-6). - **Implementation:** `WorkflowSchemaBuilder.php:28-41` (CONTRACT_KEYS), `:116-152` - **Guaranteed by:** 2 tests (incl. `::testContract… ### [The validator guards manifest integrity (MAN-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592246) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: R4 guards manifest integrity (see GR-VAL R4.a–d). - **Implementation:** — - **Guaranteed by:** — (cross-reference; R4.a–d carry the tests) Rule `MAN-4` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [The authoring picker offers only ports that exist (MAN-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592245) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: The authoring picker is this module's own workflow form (`FlowDropWorkflowForm::getAvailableNodePorts()`) — there is no second picker anywhere else; the editor package has no workflow-exposure surface at all. It offers metadata-declared ports minus already-exposed pairs, minus `trigger`, and minus ports **not exposed on the node instance** — "hidden means hidden" in both directions, so the picker can no longer produce an entry R10 rejects at save. Exposure is resolved through R10's chain, not a metadata-only read: `PortExposure::instancePorts()` + `PortExposure::isExposed()` (instance `config.… ### [The shape of a manifest entry (MAN-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592244) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Entry shape `{name,node_id,port}` + optional `title,description,examples` (input side only). - **Implementation:** `WorkflowSchemaBuilder.php:177-200` - **Guaranteed by:** `::testAuthorMetadataOverlaid` Rule `MAN-2` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: MAN-2` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592093 ### [A workflow's input ports are a declared manifest, never derived (MAN-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592243) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Workflow input ports are a **declared manifest** (`input_ports`), never derived from the exposure cascade; a plugin gaining a param cannot widen the launch surface. The builder never consults `PortExposure`: a declared entry is built even when the instance hides that port, and an exposed-but-undeclared param never reaches the snapshot. - **Implementation:** form `:143-168`; importer; `WorkflowSchemaBuilder.php:72-101` - **Guaranteed by:** `::testManifestIsIndependentOfExposureCascade` Rule `MAN-1` of `GR-MAN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable … ### [The dynamic-port form appears only when the node type opts in (DYN-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592242) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A metadata/form rule only: on node-type `configurable` opt-in (= SCH-5) the reserved param is routed to `configSchema` — never `inputSchema`, so it is never a wireable port — with default from the entity `default`, else the schema default, else `[]`; without opt-in it is dropped from both schemas. It says nothing about runtime, where the definitions are resolved as an ordinary schema property and then read back at `ParameterResolver.php:205`. Because the trait declares `default: []`, opting out resolves the definitions to `[]` and the `?? $workflowValues[…]` fallback there is unreachable — so … ### [Dynamic ports have no exposure semantics (DYN-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592241) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Dynamic ports have NO exposure semantics, and by construction rather than by exemption: the port name is absent from the plugin's `parameterSchema`/`outputSchema`, so every exposure gate misses it. `ParameterResolver` forwards the value from `runtimeInputs` after the main loop, with no exposure check; `filterUnexposedOutputs` iterates declared schema properties only, so a dynamic output's value is never stripped; R7 skips the edge because there is no metadata exposure default to enforce against. **Correction:** R10 does *not* skip it — a dynamic port named in a workflow-exposure entry is refus… ### [A static parameter name beats a dynamic one (DYN-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592240) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Static param names beat dynamic ones (collision → dynamic ignored). - **Implementation:** `ParameterResolver.php:173-175` - **Guaranteed by:** `ports-dynamic-passthrough.yml` Rule `DYN-5` of `GR-DYN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DYN-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592094 ### [An unconnected dynamic port resolves to NULL, with its key present (DYN-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592239) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unconnected dynamic ports yield NULL (key present). - **Implementation:** `:233-252` - **Guaranteed by:** `DynamicPortTraitTest` Rule `DYN-4` of `GR-DYN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DYN-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592094 ### [Reject an invalid or duplicate dynamic port name (DYN-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592238) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `validatePortNames()` throws on: name not `/^[a-zA-Z][a-zA-Z0-9_]*$/`; forbidden names; duplicates across the input∪output union. Empty/non-array defs skipped silently. Two caveats: the `__`-prefix guard is unreachable (a leading underscore already fails the pattern, so the caller gets the pattern message), and the pattern is not `D`-anchored, so a single trailing newline (`"port\n"`) is accepted. - **Implementation:** `:267-303` - **Guaranteed by:** `DynamicPortTraitTest` Rule `DYN-3` of `GR-DYN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-regist… ### [A dynamic port item needs a name, label and dataType (DYN-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592237) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Port item: `name,label,dataType` required; `dataType` enum closed (`string,number,boolean,array,json,mixed,file,image`), default `mixed`. The closure is **declarative only** — it constrains the port editor's choices; no PHP path validates per-item constraints, so an out-of-enum `dataType` is accepted at resolution and execution time. - **Implementation:** `:64-68,114-116` - **Guaranteed by:** `DynamicPortTraitTest` Rule `DYN-2` of `GR-DYN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DYN-2` token, and `scripts/spec-coverage.php --check` f… ### [A node type opts into dynamic ports by spreading their schema in (DYN-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592236) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Opt-in by spreading `buildDynamic{Inputs,Outputs}Schema()` into the param schema; declared as reserved array params, default `[]`. - **Implementation:** `DynamicPortTrait.php:78-190` - **Guaranteed by:** `DynamicPortTraitTest` Rule `DYN-1` of `GR-DYN` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: DYN-1` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592094 ### [Port order is cosmetic and the engine never reads it (EXPO-17)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592235) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `displayOrder`/`x-port-order` is cosmetic only — the engine never reads it (fdnpm's counterpart is `NodePort.displayOrder`; `x-port-order` appears nowhere in that repo's source). - **Implementation:** `NodePort.php:47-57` - **Guaranteed by:** `PortSchemaExtensionReachTest::testPortOrderIsConfinedToTheMetadataLayer` (grep-backed: only the DTO and the metadata resolver) + `NodePortTest` / `NodeMetadataResolverTransformPortsTest` for the mapping Rule `EXPO-17` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-17` token, and `scr… ### [The exposure checkbox seeds from the saved value (EXPO-16)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592234) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Each `exposed_by_default` checkbox seeds from the saved entity value; with none it mirrors `PortExposure::isExposedByDefault($schema)` **only while the port exists** (input: `connectable` ticked; output: `exposed` ticked) and reads unchecked otherwise. Both are `#states: enabled` on that sibling selector, and a disabled checkbox is not submitted — so a port that does not exist never shows a greyed-out tick and cannot be submitted as exposed. - **Implementation:** `NodeTypeFormSectionsTrait.php:235-247,485-496` - **Guaranteed by:** `NodeTypeFormExposureSeedingTest` (saved value wins; suggestio… ### [Which parameters a model may fill on a tool call (EXPO-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592233) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Tool-fillable set: param model-fillable iff `connectable && exposed` and no data edge feeds it. - **Implementation:** `ToolParameterScope.php:76-88` - **Guaranteed by:** `ToolParameterScopeTest` Rule `EXPO-15` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-15` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [Stripping runs before the unified output port is composed (EXPO-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592232) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Stripping runs before unified I/O output composition, serializability check, Output wrapping, job records, checkpoints, real-time, tool results. - **Implementation:** `:199-226` - **Guaranteed by:** `NodeRuntimeServiceOutputExposureOrderTest` (ordering-sensitive by construction: a hidden port never reappears inside the unified `output` — which filters on `exposed` only — and a json-hostile value on a hidden port does not fail the node) Rule `EXPO-14` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-14` token, and `scripts/sp… ### [An output the node type hides is stripped unconditionally (EXPO-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592231) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Entity `exposed: FALSE` → stripped unconditionally; else instance override → type default → TRUE. - **Implementation:** `:742-760` - **Guaranteed by:** 5 tests + fixture Rule `EXPO-13` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-13` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [Control outputs are never stripped (EXPO-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592230) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `CONTROL_OUTPUTS` (`active_branches`,`state_update`) never stripped. - **Implementation:** `:739-741` - **Guaranteed by:** `::testControlOutputsAreNeverStripped` Rule `EXPO-12` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-12` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [A hidden output's value is stripped where it is produced (EXPO-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592229) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Output stripping iterates the plugin's `getOutputSchema()['properties']` only, so undeclared keys (dynamic outputs, reserved control ports) pass through. ⚠ **Product gap — contradicts the exposure invariant:** two early-outs bypass the pass entirely, an empty `$result` and a plugin whose output schema declares **no** properties. In the second case nothing is stripped even when the node type marks the output `exposed: FALSE`, so a hidden output's value is delivered. - **Implementation:** `NodeRuntimeService.php:715-724`, loop `:730` - **Guaranteed by:** output-exposure suite (incl. `::testEmpt… ### [A hidden input port receives no runtime value (EXPO-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592228) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Runtime input gating: for a connectable-but-hidden port Priority 1 is *skipped*, not failed — the runtime/LLM value is ignored and resolution continues to the configured value when the param is `configurable` and present (`SOURCE_CONFIG`), else to the entity/schema default (`SOURCE_DEFAULT`). Never `SOURCE_RUNTIME`, and never NULL-by-omission: hiding a port changes precedence, it does not unset the parameter. Internal `__`-prefixed params sit outside the gate and always accept runtime input. - **Implementation:** `ParameterResolver.php:269` (gate `$isInternal \|\| ($connectable && $exposed)`)… ### [The one-time exposure freeze writes only the hidden entries (EXPO-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592227) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: One-time freezes: `update_10004` writes FALSE-only, idempotent, never overwrites an existing key, skips non-ports (non-connectable param / `exposed: FALSE` output); `update_10005` repairs the alpha10 sweep, unsetting only exact-FALSE, instance overrides survive. - **Implementation:** `flowdrop_node_type.install:167-315` - **Guaranteed by:** `ExposureFreezeUpdateTest` (10004) + `ExposureSweepRepairUpdateTest` (10005) Rule `EXPO-9` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-9` token, and `scripts/spec-coverage.php --chec… ### [A parameter added after install has no stored exposure until a re-save (EXPO-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592226) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **Known seam:** a plugin param added post-install with no re-save has no config key → runtime treats it as exposed regardless of the plugin's FALSE suggestion. - **Implementation:** doc `:56-61` - **Guaranteed by:** `ports-absent-flag-polarity.yml` Rule `EXPO-8` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [Materialize an exposure entry only when it diverges from the default (EXPO-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592225) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Materialization divergent-only, destructive-on-TRUE: config `exposed_by_default: FALSE` writes the x-flag; anything else unsets it. - **Implementation:** `NodeMetadataResolver.php:658-664,744-750` - **Guaranteed by:** derive-schemas suite Rule `EXPO-7` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [The plugin's exposure hint is read at authoring time only (EXPO-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592224) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `x-exposed-by-default` read only at authoring time (form seeding ×2, generator freeze, the two freeze update hooks) — never at execution. **Correction:** the flag is also read once on the API-generation path, at `NodeMetadataResolver::transformSchemaToPorts`, but the schema it reads there has already had the flag re-written from config (EXPO-7), so the plugin's own suggestion still never reaches generated metadata. - **Implementation:** 3 cited sites + `flowdrop_node_type.install`, `NodeMetadataResolver.php:816` - **Guaranteed by:** `PortSchemaExtensionReachTest` (grep-backed: the 6 productio… ### [A schema hides a port by default only when it says so exactly (EXPO-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592223) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `isExposedByDefault(schema)` FALSE only when `x-exposed-by-default` is exactly FALSE. - **Implementation:** `:95-97` - **Guaranteed by:** `PortExposureTest::testIsExposedByDefaultIsFalseOnlyForAnExactFalse` (identity, not truthiness: NULL/`0`/`''`/`'false'` all stay exposed) Rule `EXPO-5` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [An untouched node stores no ports key, so the default always applies (EXPO-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592222) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Untouched node stores no `ports` key → default always applies. - **Implementation:** `:38-41` - **Guaranteed by:** Rule `EXPO-4` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [How a port direction maps to its config key (EXPO-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592221) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Direction key mapping: OUTPUT→`outputs`, anything else→`inputs`; overrides direction-scoped. - **Implementation:** `:55` - **Guaranteed by:** Rule `EXPO-3` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [An instance override decides exposure before any default does (EXPO-2 (D3))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592220) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `isExposed`: scan direction-scoped `config.ports` for entry with `exposed` key → that value; else `exposedByDefault`. - **Implementation:** `:54-68` - **Guaranteed by:** 4 cases Rule `EXPO-2 (D3)` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EXPO-2 (D3)` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592089 ### [PortExposure is the only PHP accessor for effective exposure (EXPO-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592219) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `PortExposure` is the single PHP accessor for effective exposure (mirrors the editor package's `isPortExposed` node-level check); 6 consumers: ParameterResolver, ToolParameterScope, R7, R10, NodeRuntimeService, and the workflow form's exposure picker (MAN-3). `instancePorts()` is the one place `data.config.ports` is located on a stored node, so the save boundary and the picker read the override from the same slot. - **Implementation:** `src/Utility/PortExposure.php:8-33` - **Guaranteed by:** `PortExposureTest` Rule `EXPO-1` of `GR-EXPO` in `docs/development/specification-registry.md`. Tests … ### [A config default is written only for a configurable parameter (CFG-18)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592218) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `configDefaults[name]` written only when configurable and effective default non-NULL. - **Implementation:** `NodeMetadataResolver.php:680-683` - **Guaranteed by:** `NodeMetadataResolverDeriveSchemasTest` Rule `CFG-18` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-18` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [The unified input merge only fills connectable parameters (CFG-17)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592217) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unified I/O merge filters on `connectable` only; the main-loop re-gate drops hidden-port smuggled values (two guards, one outcome). - **Implementation:** `:387` vs `:269` - **Guaranteed by:** same fixture Rule `CFG-17` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-17` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [The reserved input port is decomposed before the schema loop (CFG-16)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592216) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: The reserved `input` port is decomposed **before** the schema loop. If its value is not an array nothing is decomposed: `warning: "Unified 'input' value is not an array, skipping decomposition"` is logged and the runtime inputs are returned unchanged — the raw `input` key survives, so a schema property literally named `input` still receives the scalar. Otherwise only keys that are `connectable`, internal (`__`) or a declared dynamic-port name are kept (the rest logged at debug: "Filtered non-connectable key"), and every individually wired port then overwrites the same key from the payload. - … ### [Every dynamic input is present in the resolved bag (CFG-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592215) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: After the schema loop, each `dynamicInputs[].name` present in the merged runtime inputs is copied into the bag **verbatim** — no exposure gate, no `required` check, no `validateValue()` call, so the entry's declared `type`/`dataType` is DECLARATIVE only (cf. DYN-2). A name that is already a key in the bag (any schema property, including one resolved to NULL) is skipped, so the statically resolved value wins; empty names are skipped. Definitions are read from the *resolved* `dynamicInputs` value, falling back to raw config. - **Implementation:** `:198-221`; verbatim forward at `:215`, collisio… ### [Every schema property is present in the bag, NULL when unresolved (CFG-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592214) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Every schema property is present in the bag, NULL when unresolved. - **Implementation:** `:183` - **Guaranteed by:** same fixture Rule `CFG-14` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-14` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [The resolved bag holds exactly the schema's keys plus dynamic ports (CFG-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592213) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Resolved bag = exactly the plugin schema's property keys (+ dynamic forwards); unknown config keys never reach the processor. - **Implementation:** `:113-221` - **Guaranteed by:** `ports-resolved-bag-shape.yml` Rule `CFG-13` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-13` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Format validation covers nine formats and ignores the rest (CFG-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592212) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `format` validation covers 9 formats; unknown formats pass. - **Implementation:** `:597-628` - **Guaranteed by:** `ports-validation-format-throws.yml` (config path — R6 does **not** check `format`; the resolver is the only guard) + same unit test (all 9 formats + unknown passes) Rule `CFG-12` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-12` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [The type check is a closed match with no coercion (CFG-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592211) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Type check closed-match; unknown type names pass; no coercion. - **Implementation:** `:658-670` - **Guaranteed by:** `ports-validation-no-coercion.yml` (wire path, same R6 caveat) + same unit test (full type matrix) Rule `CFG-11` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [A resolved value is validated against the plugin schema (CFG-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592210) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A non-NULL resolved value is validated against the plugin schema; any violation throws `ParameterValidationException` carrying the failing constraint name. NULL skips validation entirely. `type` and `enum` are checked first (either one failing returns immediately); the remaining constraints are then selected by the value's **PHP runtime type, not the declared `type`** — `minimum`/`maximum`/`exclusiveMinimum`/`exclusiveMaximum`/`multipleOf` run for any `is_numeric()` value (numeric strings included), `minLength`/`maxLength`/`pattern`/`format` for `is_string()`, `minItems`/`maxItems`/`uniqueItem… ### [A required parameter that resolves to NULL fails the node (CFG-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592209) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `required && resolved === NULL` → `MissingParameterException`, after cascade, before validation. - **Implementation:** `:170-176` - **Guaranteed by:** `ports-required-null-default-throws.yml` Rule `CFG-9` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-9` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Internal parameters accept a runtime value but never config (CFG-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592208) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Internal `__` params: always accept runtime, never config, else default; bypass all gates. - **Implementation:** `:261-283` - **Guaranteed by:** `ports-internal-param.yml` Rule `CFG-8` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-8` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Presence is key existence, so an explicit NULL wins over a lower priority (CFG-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592207) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Presence = `array_key_exists` at every priority: an explicit NULL at a higher priority **wins** — a wire-delivered NULL beats the author's config, a config NULL beats the schema default. Whether a wire NULL reaches the resolver at all is the *builder's* choice, and there are three builders that disagree: `AbstractOrchestratorBase::buildRuntimeInputData` (`:760`) and `SynchronousOrchestrator::resolveNodeInputs` (`:706`) collect wire values with `array_key_exists`, so a NULL output survives; the StateGraph builder still gates with `isset()` (`StateGraphOrchestrator.php:1621`), so on that path an… ### [Priority 3: fall back to the effective default (CFG-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592206) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Priority 3 DEFAULT: unconditional fallback. - **Implementation:** `:286-287` - **Guaranteed by:** `ports-precedence-full-chain.yml` Rule `CFG-6` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Priority 2: take a config value when the parameter is configurable (CFG-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592205) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Priority 2 CONFIG: iff `!internal AND configurable AND array_key_exists`. - **Implementation:** `:280-283` - **Guaranteed by:** `ports-connectable-not-configurable.yml` Rule `CFG-5` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-5` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Priority 1: take a runtime value when the port can receive one (CFG-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592204) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Priority 1 RUNTIME: iff `(internal OR (connectable AND exposed)) AND array_key_exists`. - **Implementation:** `:269-276` - **Guaranteed by:** fixtures + `ParameterResolverExposureTest` Rule `CFG-4` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [An effective default is the entity's, then the plugin's, then NULL (CFG-3 (D4))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592203) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Effective default = `E ?? P ?? NULL`; entity `null` indistinguishable from absent. - **Implementation:** `:142-144` - **Guaranteed by:** `ports-entity-default-overrides-schema.yml` Rule `CFG-3 (D4)` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-3 (D4)` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [The exposure default fails open (CFG-2 (D2))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592202) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `exposedByDefault` fails **open** (`?? TRUE`) — deliberate opposite polarity. - **Implementation:** `:138` - **Guaranteed by:** same fixture (pins the seam) Rule `CFG-2 (D2)` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-2 (D2)` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Gate flags fail closed (CFG-1 (D1))](https://git.drupalcode.org/project/flowdrop/-/work_items/3592201) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Gate flags fail **closed** (`?? FALSE`). - **Implementation:** `ParameterResolver.php:128-130` - **Guaranteed by:** `ports-absent-flag-polarity.yml` Rule `CFG-1 (D1)` of `GR-CFG` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: CFG-1 (D1)` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592092 ### [Config fields are ordered by their declared order (SCH-31)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592200) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `x-config-order` orders config fields ascending (absent or non-numeric = 0, ties keep declaration order) **inside the generated uiSchema only** — if no property carries a registered `x-group`, `generate()` returns NULL, there is no layout, and `x-config-order` has no effect on the flat form. The pre-2.x spelling `x-display-order` is still read when the new key is absent and logs a deprecation warning naming the property plus both key spellings, **once per property per `generate()` call** (so every form build re-warns); the new key wins when both are present and suppresses the warning. - **Imp… ### [The run path re-enriches from the live node type (SCH-29)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592199) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Run path re-enriches from the live node type then normalizes via `WorkflowDTO::fromArray` — stored metadata never authoritative at run. - **Implementation:** `WorkflowCompiler.php:92-104` - **Guaranteed by:** `WorkflowCompilerRunEnrichmentTest` Rule `SCH-29` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-29` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [The executor plugin id comes from the node type, never from the payload (SCH-28)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592198) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Executor plugin id resolves from the node-type entity, never trusted from stored node metadata. - **Implementation:** `NodeMetadataResolver.php:188-200` - **Guaranteed by:** `NodeMetadataResolverEnrichAnchorTest` + `WorkflowCompilerRunEnrichmentTest` Rule `SCH-28` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-28` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [The wire shape is lean: emit a key only when it diverges from the default (SCH-27)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592197) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Wire shape is lean-by-divergence: `defaultValue` emitted only non-NULL, `exposedByDefault` only FALSE, `displayOrder` only ≠0 — editor must read absence as exposed/0. - **Implementation:** `NodePort.php:172-197` - **Guaranteed by:** `NodePortTest` Rule `SCH-27` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-27` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [The editor catalog serves enabled node types, sorted (SCH-26)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592196) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Editor catalog serves enabled node types only, sorted category→name. - **Implementation:** `NodesController.php:99-130` - **Guaranteed by:** `NodesControllerCatalogTest` Rule `SCH-26` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-26` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Enrichment anchors on the node-type id alone (SCH-25)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592195) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Enrichment anchors on `node_type_id` (via `NodeAnchor::read()`) only: it sets `type` to the constant `universalNode`, replaces `data.metadata`, and normalizes `data` to an array before the write; `data.config`/`id`/`label`/`position` are untouched and re-running is a no-op. When the anchor is empty or the node type no longer builds, the node is returned unchanged — no `data.metadata` key is added. The `data` normalization is defensive only and unreachable in practice: the anchor lives *inside* `data`, so a node whose `data` is not an array returns at the empty-anchor guard before it. - **Impl… ### [Building node data logs and degrades instead of failing the editor (SCH-24)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592194) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `buildForNodeType()` catches `\Exception` only: it logs `Failed to build node data for @id: @error` on the `flowdrop` channel at **error** severity and returns NULL, so `enrichNode()` returns the stored node untouched (no `data.metadata` key written). A `\Throwable` that is not an `\Exception` (e.g. a `TypeError`/`Error` from a broken plugin) is **not** caught and fails the request. - **Implementation:** `:472-478`; unchanged-node path `:120-122` - **Guaranteed by:** (same suite) Rule `SCH-24` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `… ### [The UI schema is generated from the final config schema (SCH-23)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592193) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `uiSchema` is generated from the *final* configSchema (after reserved-prop injection) and is NULL **exactly when no property carries a registered `x-group`** — an unknown group falls back to the default bucket, so a schema tagged only with unknown groups is NULL too and the form stays on its flat path. The baseline ships every group collapsed; `enrichNode()` opens a group per instance when that group's fields are set in `data.config`. - **Implementation:** `:449`; `UiSchemaGenerator.php:106-128`; instance open-state `:134-141` - **Guaranteed by:** (same suite) + `UiSchemaGeneratorTest` Rule … ### [Only a config-edit provider gets a configEdit block (SCH-22)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592192) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `configEdit` populated only for `ConfigEditProviderInterface` implementors. - **Implementation:** `:417-420` - **Guaranteed by:** `NodeMetadataBuildTest` Rule `SCH-22` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-22` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Every node gets a reserved instance title and description (SCH-21)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592191) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved config props: `instanceTitle`/`instanceDescription` on every node; `maxRetries` + `ports` on executable nodes only; skipped if already declared. - **Implementation:** `:487-546` - **Guaranteed by:** `NodeMetadataResolverReservedConfigPropsTest` Rule `SCH-21` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-21` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [A node's visual type comes from the config entity only (SCH-20)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592190) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Visual type comes from the config entity only. When `getSupportedVisualTypes()` holds >1 entry a reserved `nodeType` string property (`enum` = the supported types, `default` = the entity's visual type, `x-group: general`) is written into configSchema, and its config *default* is stored under the same `nodeType` key. Unlike SCH-21's reserved props this write is **unconditional** — it overwrites a plugin-declared `nodeType` property. The `enum` is **declarative only**: nothing validates a stored `data.config.nodeType` against it at run (the entity accessor has no runtime caller besides this line… ### [Both key enumerations skip trigger and hidden parameters (SCH-19)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592189) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Both key enumerations skip `trigger` and hidden params (`format: hidden` / `hidden: TRUE`) — a hidden port does not exist on the instance, so it never appears in a unified port description. - **Implementation:** `:872-940` - **Guaranteed by:** `NodeMetadataResolverKeyEnumerationTest` Rule `SCH-19` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-19` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Prepend the unified output port when the node exposes one (SCH-18)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592188) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unified I/O `output` port prepended iff `isUnifiedOutputExposed()`, description enumerates exposed output keys only. - **Implementation:** `:361-376` - **Guaranteed by:** (same suite) Rule `SCH-18` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-18` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Prepend the unified input port when the node exposes one (SCH-17)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592187) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unified I/O `input` port prepended iff `isUnifiedInputExposed()`, dataType json, description enumerates connectable keys only. - **Implementation:** `:342-357` - **Guaranteed by:** `UnifiedIoPortInjectionTest` Rule `SCH-17` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-17` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [The exposure defaults of the reserved ports (SCH-16)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592186) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved-port exposure defaults table: input/output/tool/error=F, trigger in/out=T; node type overrides per key, storing divergent keys only. - **Implementation:** `FlowDropNodeType.php:235-242` - **Guaranteed by:** `FlowDropNodeTypeReservedPortExposureTest` Rule `SCH-16` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-16` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [An injected port declares its exposure default only when it diverges (SCH-15)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592185) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Injected reserved ports emit `x-exposed-by-default: FALSE` only when divergent from TRUE. - **Implementation:** 4 sites - **Guaranteed by:** (all 4 injection suites) Rule `SCH-15` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-15` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Inject the reserved error output on every executable node (SCH-14)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592184) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved `error` output injected except NonExecutable processors, `x-port-order: 120`, ships hidden. - **Implementation:** `:344-357` → `:819` - **Guaranteed by:** `ErrorPortInjectionTest` Rule `SCH-14` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-14` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Inject the reserved tool output only on a tool-exposed node (SCH-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592183) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved `tool` output injected iff `isToolExposed()`, `x-port-order: 110`. - **Implementation:** `:323-336` → `:819` - **Guaranteed by:** `ToolOutputInjectionTest` Rule `SCH-13` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-13` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Inject the reserved trigger output on every node but a terminal node (SCH-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592182) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved `trigger` output injected except Terminal processors, `x-port-order: 100`. - **Implementation:** `:305-318` → `:819` - **Guaranteed by:** `TriggerOutputInjectionTest` Rule `SCH-12` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-12` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Inject the reserved trigger input on every node but a start node (SCH-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592181) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved `trigger` input injected on every node except Start processors (unless already declared), carrying `x-port-order: 100`. - **Implementation:** `:276-289` → `:819` - **Guaranteed by:** `TriggerInputInjectionTest` Rule `SCH-11` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-11` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [The schema-to-dataType map is closed (SCH-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592180) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Schema→dataType map is closed: `string→string`, `number\|integer→number`, `boolean→boolean`, `array→array`, `object→json`, `tool→tool`, `mixed→mixed`, `trigger→trigger`; any other or absent type yields `string`. Every value the map can return must also be declared by `NodesController::getPortConfiguration()` — a coupling that is **test-enforced only, with no runtime assertion**; an undeclared type would leave the port compatible with nothing in the editor. - **Implementation:** `:868-882` - **Guaranteed by:** same suite + `NodesControllerPortConfigTest` Rule `SCH-10` of `GR-SCHEMA` in `docs/… ### [A union type normalizes to its first non-null member (SCH-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592179) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Union types normalize to first non-null member; all-null/empty → `string`. - **Implementation:** `:812-828` - **Guaranteed by:** (same suite) Rule `SCH-9` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-9` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [One mapping turns a schema into ports (SCH-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592178) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `transformSchemaToPorts()` is the only schema→NodePort mapping for schema-derived ports: `id` = the property key, `name` = `title` ?? key, `dataType` = the mapped normalized `type`, `required` = membership in the schema's `required` list, `defaultValue` = `default` ?? NULL, `exposedByDefault` = `PortExposure::isExposedByDefault()`, `displayOrder` = `(int) x-port-order` ?? 0. The two unified I/O ports (SCH-17/18) bypass it — they are constructed directly, always `dataType: json` and `displayOrder: 0`. - **Implementation:** `:795-824` vs the direct construction at `:371-379`/`:390-398` - **Guar… ### [An output reaches the editor only when the node type exposes it (SCH-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592177) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Output survives into metadata iff entity `outputs[name]['exposed'] ?? TRUE` (fail-open). - **Implementation:** `:726-753` - **Guaranteed by:** `ports-output-stripping.yml` Rule `SCH-7` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [A parameter is required on the input side only when it is not configurable (SCH-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592176) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `required` emitted into inputSchema.required iff `required && !configurable`; into configSchema.required iff `required && !connectable`. - **Implementation:** `:666-678` - **Guaranteed by:** `NodeMetadataResolverDeriveSchemasTest` Rule `SCH-6` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-6` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Reserved config-only parameters never become ports (SCH-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592175) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Reserved config-only params (`dynamicInputs`,`dynamicOutputs`,`branches`) are never input ports; on per-node-type `configurable: TRUE` opt-in they enter configSchema and always get a `configDefaults` entry — entity `default`, else schema `default`, else `[]`. Never omitted and never NULL, unlike an ordinary configurable param, whose entry is omitted when its resolved default is NULL. - **Implementation:** `:635-645` vs the ordinary path at `:704-706` - **Guaranteed by:** (5 cases in suite) Rule `SCH-5` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a gr… ### [Hidden parameters are dropped from both derived schemas (SCH-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592174) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `format: hidden` / `hidden: TRUE` params are dropped from both derived schemas **and** from `configDefaults`, overriding entity `connectable`/`configurable`. The hidden check runs AFTER the reserved config-only branch (SCH-5), so a hidden `dynamicInputs`/`dynamicOutputs`/`branches` is still surfaced into configSchema when the node type opts in — the hidden marker does not suppress a reserved param. - **Implementation:** `:650-654`, reached only past the reserved branch at `:635-645` - **Guaranteed by:** `NodeMetadataResolverDeriveSchemasTest` Rule `SCH-4` of `GR-SCHEMA` in `docs/development/… ### [Deriving splits one parameter schema into an input schema and a config schema (SCH-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592173) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `deriveSchemas()` splits one param schema in two: param ∈ inputSchema iff `connectable`, ∈ configSchema iff `configurable`; both/one/neither legal. - **Implementation:** `NodeMetadataResolver.php:589-700` - **Guaranteed by:** (same suite) Rule `SCH-3` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Schema derivation reads its gate flags from the plugin schema (SCH-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592172) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `deriveSchemas()` reads the gate flags (`connectable`/`configurable`/`required`) from the node-type entity's parameter config only, each defaulting FALSE when the entity declares no entry — so a param the entity never declares appears in neither derived schema and in neither `required` list. Same-named keys in a plugin's `getParameterSchema()` are never read, but they are **not stripped** either: `cleanPropertySchema()` is a pass-through, so they survive verbatim into the served input/config schema and no consumer may read them. - **Implementation:** `NodeMetadataResolver.php:661-663`; `clean… ### [A node's input and output surface comes only from its two schema methods (SCH-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592171) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Input surface only via `getParameterSchema()`, output only via `getOutputSchema()`; the plugin attribute carries no port/visual data. - **Implementation:** `src/Attribute/FlowDropNodeProcessor.php:36-46` - **Guaranteed by:** — (structural) Rule `SCH-1` of `GR-SCHEMA` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: SCH-1` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592091 ### [Transport edges and job-metadata edges each own their own key names (EDGE-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592170) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Two edge domains, one key bag each. `EdgeKeys` names **only** the camelCase transport keys (`source`, `target`, `sourceHandle`, `targetHandle`) that `JsApi\Edge` reads and writes; the snake_case job-metadata record (`source_handle`, `target_handle`, `is_trigger`, `is_loopback`, `is_tool`, `branch_name`, `edge_id`) is owned solely by `ExecutionEdge`, which is the only reader and writer of those names. `EdgeKeys` must never carry a job-metadata constant: the four it used to carry (`IS_TRIGGER`, `IS_LOOPBACK`, `BRANCH_NAME`, `EDGE_ID`) had no reader at all and made the neighbouring `EdgeKeys::SOU… ### [Edge conditions are a removed feature that is tolerated but never read (EDGE-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592169) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `edge.data.condition` is a removed feature: schema-tolerated (declared `nullable`, so a stored workflow carrying it round-trips unchanged under strict config-schema validation), logged, always routes. The warning fires only for a non-empty *string* condition, and it is emitted where a source node's outgoing edges are resolved — so "once per edge" means once per dispatch pass, and a source that re-executes (a loop) warns again rather than once per launch. - **Implementation:** schema `flowdrop_workflow.schema.yml` `flowdrop_workflow.edge_data:condition`; `StateGraphOrchestrator::outgoingEdges(… ### [What makes a node tool-only (EDGE-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592168) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Tool-only node = ≥1 outgoing edge **and** every outgoing edge a tool edge; zero outgoing edges, or any non-tool outgoing edge, means not tool-only. A tool-only node is excluded from the compiled execution graph (`isExcluded($nodeId)` TRUE, reason `tool_only`) and generates no job — it runs inline only when a consumer invokes it as a tool. The classifier owns the rule and `JobGenerationService` reads it; the compiler applies the same rule over its own `DependencyEdge::isToolAvailability()` records and additionally requires a resolvable tool-consumer target. - **Implementation:** `EdgePortClass… ### [An edge is an error edge by its source handle (EDGE-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592167) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Error edge ⇔ an `ExecutionEdge` (the job-metadata record) whose source handle ends `-output-error`. `isErrorEdge()` accepts only that shape, so a transport `JsApi\Edge` is never classified here. Its presence is what makes a failing node return an `error` payload (`{message, code, node_id, retryable}`) and the job be marked FAILED + `error_routed`, with the run continuing down the error edge instead of throwing and failing. - **Implementation:** `src/Utility/EdgePortClassifier.php:85-87`; consumers `AbstractOrchestratorBase.php:741,879`, `StateGraphOrchestrator.php:1602`, `JobGenerationService… ### [An edge is a tool edge by declared type, else by its target handle (EDGE-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592166) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Tool edge ⇔ `data.edgeType === 'tool_availability'` (wins) else target handle ends `-input-tool`. Precedence runs both ways: a declared `tool_availability` makes a non-tool handle a tool edge, and any *other* non-empty string declaration makes a `-input-tool` handle NOT one. Only an absent, empty or non-string declaration falls through to the handle. - **Implementation:** classifier - **Guaranteed by:** `EdgePortClassifierTest::testExplicitEdgeTypePrecedence` Rule `EDGE-5` of `GR-EDGE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EDGE-5` … ### [An edge is a loopback edge when its target handle says so (EDGE-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592165) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Loopback edge ⇔ target handle ends `-input-loop_back` (value is `loop_back`, NOT `loopback`). - **Implementation:** `ReservedName.php:121-128` - **Guaranteed by:** `WorkflowCompilerSpecialEdgeTest::testLoopbackEdgeDetectedByHandle` Rule `EDGE-4` of `GR-EDGE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EDGE-4` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592088 ### [An edge is a trigger edge when its target handle says so (EDGE-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592164) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Trigger edge ⇔ target handle ends `-input-trigger`. - **Implementation:** `ReservedName::PORT_TRIGGER`; classifier - **Guaranteed by:** conformance `topology-*` Rule `EDGE-3` of `GR-EDGE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EDGE-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592088 ### [No wire key is structurally required; an absent one becomes a missing endpoint (EDGE-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592163) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: No wire key is structurally required — absent keys default to `''`/`[]` and become R8 "missing endpoint". - **Implementation:** `src/DTO/JsApi/Edge.php:66-75` - **Guaranteed by:** `EdgeTest::testDefaultsForMissingKeys`; `WorkflowValidatorTest::testEdge2KeylessEdgeIsReportedAsMissingEndpoints` Rule `EDGE-2` of `GR-EDGE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EDGE-2` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592088 ### [How a port handle encodes its node, direction and port name (EDGE-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592162) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Handle encoding `{nodeId}-{input\|output}-{portName}`; port name = everything after the FIRST `-input-`/`-output-`; kind classification is suffix-exact, never substring. - **Implementation:** `src/Utility/EdgePortClassifier.php` - **Guaranteed by:** `EdgePortClassifierTest::testExactSuffixMatching`, `::testPortNameExtraction`, `::testPortNameSplitsAtTheFirstDirectionMarker` Rule `EDGE-1` of `GR-EDGE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: EDGE-1` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree.… ### [Refuse a duplicate edge between the same two ports (R13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592161) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Duplicate parallel edges rejected (`R13_EDGE_PARALLEL_DUPLICATE`); the error names the earlier edge's position. Detection keys on the two endpoint ids and the two **raw handle strings** verbatim (`source|sourceHandle|target|targetHandle`) with no port-name parsing or normalisation — so edges between the same nodes over *different* ports stay valid, and two edges over the same *logical* port spelled differently (one with `sourceHandle` omitted, one with the explicit `{node}-output-{port}` handle) are **both accepted**. Edges with an empty endpoint are excluded from the comparison entirely (DECI… ### [Refuse an edge from a node to itself (R12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592160) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: An edge whose non-empty `source` equals its `target` is rejected (`R12_EDGE_SELF`) at `edge.{index}` **regardless of handles** — wiring a node's own output into its own input is still refused — and regardless of whether the node exists (a self-edge on a deleted node also earns R8's two errors). An edge with an empty `source` is never reported as a self-edge even when the target is empty too: R5/R8 own that (DECIDED ← OPEN-7). - **Implementation:** E - **Guaranteed by:** `::testR12SelfEdgeIsRejected`, `::testR12SelfEdgeWithDistinctHandlesIsStillRejected` Rule `R12` of `GR-VAL` in `docs/develo… ### [Every configured expression must pass its engine's check at save (R11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592159) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Every configured expression must pass its engine's `validate()` at save (`R11_EXPRESSION_INVALID`); the error names the node, config key, engine and expression. Config carries no generic "this is an expression" marker, so the check is scoped to the known expression-bearing keys of the in-tree processors: `data_extractor.path`, `data_mapper` dynamic output `value`s, `data_shaper.mapping` sources (special values like `_LITERAL:`/`_NOW_` skipped, nested `_source`/`_each` walked), `prompt_template.template` (twig). All four engines are wired; twig/jsonpath verdicts are trivially permissive (LANG-1… ### [A workflow exposure must target a port exposed on the node instance (R10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592158) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Workflow-exposure entry must target a port exposed on the target node **instance** (`R10_EXPOSURE_HIDDEN_PORT`) — the exposure-map twin of R7, resolved through the same chain (instance `config.ports[].exposed` override → metadata `exposedByDefault` → exposed): hidden means hidden in both directions. The error names the workflow port, the node and the node port. Metadata-undeclared (dynamic) ports are out of scope, mirroring R7.d; disjoint from R7 by construction — R7 inspects edges, R10 inspects exposure entries, so one hidden port never earns one entry two reports. Doctor remedies: Expose the… ### [A node's node-type anchor must resolve to a node type that exists (R9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592157) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Node's `node_type_id` anchor must resolve to an existing node type (`R9_NODE_TYPE_UNKNOWN`); the error names the node and the type. Anchor-less nodes (Notes and other non-executables) are out of scope. Distinct from R1 by construction: entity missing → R9 (no plugin to check, R1 quiet); entity present but plugin missing → R1 — one defect, one report. BundleImporter generates a bundle's node types *before* validating (rolling them back when the import is refused) and a dry run discounts R9 errors for manifest-generatable types, so bundle import keeps working; config sync runs no validation, so … ### [Edge ids must be present and unique at save (DECIDED) (R3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592156) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Edge `id`s must be present (`R3_EDGE_MISSING_ID`) and unique (`R3_EDGE_DUPLICATE_ID`) at save; read-path minting stays legacy read tolerance only (DECIDED ← OPEN-5). - **Implementation:** E - **Guaranteed by:** `::testR3EdgeMissingIdIsRejected`, `::testR3DuplicateEdgeIdIsRejected` Rule `R3` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Node ids must be unique (DECIDED) (R2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592155) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Node `id`s must be unique (`R2_NODE_DUPLICATE_ID`) — the read path keys nodes by id, so a duplicate would silently collapse last-wins (DECIDED ← OPEN-4). - **Implementation:** E - **Guaranteed by:** `::testR2DuplicateNodeIdIsRejected` Rule `R2` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R2` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [The whole validator runs again at launch (VAL-LAUNCH)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592154) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: The full validator re-runs at launch (defense in depth): `WorkflowLauncher::validateDefinition()` re-runs every rule on the stored definition and, on any error, logs a warning and throws `WorkflowLaunchValidationException` carrying the `ValidationResult` — **before** any job generation, pipeline creation, deferred scheduling or queue item. The HTTP boundary maps it to 422 with per-error `code`/`message`/`locator` detail, mirroring the save path. - **Implementation:** inv - **Guaranteed by:** `CanvasHiddenInputPortTest` (3), `WorkflowLauncherTest::testInvalidDefinitionIsRejectedBeforeLaunch` (… ### [The validator instantiates plugins only for the exposure checks (VAL-PERF)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592153) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: The validator calls `FlowDropNodeProcessorPluginManager::createInstance()` only for the R4.d/R10 exposure checks, memoised per plugin id, so a workflow with no exposure entries makes zero *direct* constructions. **Not** a claim about total plugin construction: R6's config-schema lookup and R7/R10's `portExposureDefaults` both call `NodeMetadataResolver::buildForNodeTypeId()` (`NodeMetadataResolver.php:253`), which constructs the executor plugin itself — once per distinct node type per validation. R1 and W-T stay definition-only (`hasDefinition()`/`getDefinition()`). - **Implementation:** inv … ### [Warn about an edge leaving a terminal node (W-T)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592152) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Every edge whose **source** node's plugin class implements `TerminalNodeProcessorInterface` (read from the plugin definition's `class`, never instantiated) yields one non-blocking warning at `edge.{index}` naming the target and the terminal source — so a terminal node with N outgoing edges produces N warnings and `isValid()` stays TRUE. Only sources are inspected (an edgeless workflow looks nothing up) and the **target is not checked for existence**, so an edge from a terminal node to a deleted node produces this warning *and* R8's `R8_EDGE_TARGET_MISSING`; a dangling *source* is skipped (R8 o… ### [An exposure must name a port the plugin declares (R4.d)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592151) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Exposure `port` must be declared by plugin param schema (input) / output schema (output). The check still skips a node whose plugin is unresolvable (don't double-report R1/R9), but the old import-path hole is closed: R9 rejects a node anchored to an unknown type, and BundleImporter now generates a bundle's node types *before* validating, so the skip no longer swallows the normal import path — it remains only for anchor-less nodes and for types whose plugin R1 already reports. **Annotated 2026-07-30:** the skip covers only the port-declaration check and R10 (both need the plugin) — R4.a's name … ### [An exposure must name a node that exists (R4.c)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592150) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Exposure `node_id` must exist; failure skips the entry's other checks. - **Implementation:** E - **Guaranteed by:** `::testR4NodeMissing` Rule `R4.c` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R4.c` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Exposure names must be unique per side (R4.b)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592149) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Exposure names unique per side (input/output independent). - **Implementation:** E - **Guaranteed by:** `::testR4DuplicateName` Rule `R4.b` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R4.b` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [An exposure name must match the allowed format (R4.a)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592148) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Exposure `name` must match `/^[a-z0-9_-]+$/` — empty or absent included — rejected with `R4_NAME_FORMAT` at `schema.{side}.{index}`. Unlike R4.c this does **not** skip the entry's remaining checks: R4.b uniqueness, node existence and port declaration all still run, so two name-less entries yield two `R4_NAME_FORMAT` plus one `R4_NAME_DUPLICATE` on the empty name. - **Implementation:** E - **Guaranteed by:** `::testR4NameFormat`, `::testR4NameFormatDoesNotSkipTheEntry` Rule `R4.a` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R4… ### [Skip the edge-exposure check where another rule already owns the problem (R7.e/f)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592147) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unparseable handle, empty/unknown endpoint node, unresolvable node type → R7 skipped (R5/R8/R1 own those). **Annotated 2026-07-30:** the skip is **per endpoint, not per edge** — an edge with one unusable handle or one dangling node still has its other endpoint checked, so an R8 dangling-source error and an R7 hidden-target error can both be reported for the same edge (by construction, since the two passes are independent). The unresolvable-type arm also splits by cause: an unknown node type is reported by R9 (not R1), a resolvable type whose executor plugin is missing by R1, and an anchor-less… ### [A port the node type never declared is out of the edge-exposure check (R7.d)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592146) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Port absent from node-type metadata (dynamic/user-defined) is out of R7 scope. - **Implementation:** accept - **Guaranteed by:** `::testExposedAndUnknownPortEdgesAreValid` Rule `R7.d` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R7.d` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Effective exposure comes from the instance config, then the node-type default (R7.c)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592145) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Effective exposure = instance `config.ports[].exposed` override, else metadata `exposedByDefault`; exposing via config legalizes the edge. - **Implementation:** accept - **Guaranteed by:** `::testEdgeFromExposedErrorPortIsValid` Rule `R7.c` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R7.c` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse an edge out of a hidden output port (R7.b)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592144) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Edge from a declared-but-not-exposed **output** port rejected (`R7_EDGE_SOURCE_NOT_EXPOSED`) at `edge.{index}` (canonical: `error`, ships hidden). - **Implementation:** E - **Guaranteed by:** `::testEdgeFromNotExposedErrorPortIsRejected` Rule `R7.b` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R7.b` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse an edge into a hidden input port (R7.a)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592143) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Edge into a declared-but-not-exposed **input** port rejected (`R7_EDGE_TARGET_NOT_EXPOSED`) at `edge.{index}`. - **Implementation:** E - **Guaranteed by:** `::testEdgeIntoNotExposedInputPortIsRejected` Rule `R7.a` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R7.a` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [An edge missing both endpoints reports both errors (R8.c)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592142) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Both endpoints missing → two errors, same locator. - **Implementation:** E - **Guaranteed by:** `::testR8BothEndpointsMissingYieldTwoErrors` Rule `R8.c` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R8.c` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse an edge whose target node does not exist (R8.b)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592141) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Edge with an unresolvable **target** rejected (`R8_EDGE_TARGET_MISSING`); empty = missing. - **Implementation:** E - **Guaranteed by:** `::testR8DanglingTargetIsRejected` Rule `R8.b` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R8.b` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse an edge whose source node does not exist (R8.a)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592140) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Edge with an unresolvable **source** rejected (`R8_EDGE_SOURCE_MISSING`); empty = missing. - **Implementation:** E - **Guaranteed by:** `::testR8DanglingSourceIsRejected` Rule `R8.a` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R8.a` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Retire validateParams() from the processor contract (R6.k)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592139) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **RETIRED — `validateParams()` deleted from the processor contract (2.x).** The method was never invocable to any effect (the base returned success and no verdict gated anything), so it was removed from `FlowDropNodeProcessorInterface` along with every override and both runtime call sites (`NodeRuntimeService::validateNode`, `ScopedToolInvoker::validateArgs`). Save-time schema/expression validation (R6, R11) is the only config-verdict surface; invalid runtime values fail inside the node (GR-ERR). - **Implementation:** design - **Guaranteed by:** None — see the rule text. Rule `R6.k` of `GR-V… ### [Warn when a secret reference is written without its leading $ (R6.l)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592138) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A config **string** containing `{{ secrets.` without the leading `$` produces a non-blocking warning at `node.{id}.config.{key}` telling the author to write `${{ secrets.NAME }}`; array-valued config is walked recursively (so a reference nested in JSON-shaped config such as HTTP headers is covered), a correctly written `${{ secrets.X }}` produces none, and the save is never blocked. Implemented as a local regex, never a call into the runtime secret resolver — flowdrop_workflow sits below flowdrop_runtime in the module layering. - **Implementation:** W - **Guaranteed by:** `::testMalformedSecr… ### [An unresolvable node type skips only the schema-driven config checks (R6.j)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592137) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unresolvable node type skips the *schema-driven* checks of R6 — required keys, type/enum/bounds/pattern and the R6.c unknown-key warning are all skipped. **Annotated 2026-07-30:** not literally "all of R6" — the R6.a non-array guard runs *before* the schema lookup, so a scalar `data.config` is still rejected on a node whose type resolves to no metadata. - **Implementation:** accept - **Guaranteed by:** `::testR6UnresolvableNodeTypeSkipsSchemaChecks`, `::testR6NonArrayConfigIsRejectedWithoutResolvableType` Rule `R6.j` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to … ### [A NULL config value means unset and is never validated (R6.i)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592136) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Config value NULL = unset, never validated. - **Implementation:** accept - **Guaranteed by:** `::testR6ExplicitNullSatisfiesRequiredAndIsNotValidated` Rule `R6.i` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.i` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a string that does not match its pattern (R6.h)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592135) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `pattern` mismatch rejected; an *invalid schema pattern* does not block the author. - **Implementation:** E - **Guaranteed by:** `::testR6PatternMismatchIsRejected`, `::testR6InvalidSchemaPatternDoesNotBlockTheAuthor` Rule `R6.h` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.h` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a string outside its length bounds (R6.g)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592134) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `minLength`/`maxLength` (mb_strlen) violations rejected. - **Implementation:** E - **Guaranteed by:** `::testR6LengthBoundsUseCharacterCount` (4-char/8-byte fixture pins the character count) Rule `R6.g` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.g` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a number outside its minimum/maximum (R6.f)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592133) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `minimum`/`maximum` violations rejected (bounds are checked for `int`/`float` values only — a numeric *string* is never bounds-checked). - **Implementation:** E - **Guaranteed by:** `::testR6BelowMinimumIsRejected`, `::testR6AboveMaximumIsRejectedButInRangeAccepted` Rule `R6.f` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.f` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a config value outside its enum (R6.e)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592132) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Value outside `enum` (strict) rejected. - **Implementation:** E - **Guaranteed by:** `::testApiRejectsInvalidConfigValue` Rule `R6.e` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.e` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a config value of the wrong type (R6.d)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592131) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Wrong JSON-schema `type` rejected; unknown type names **pass**. **Shared shape of R6.d–R6.h:** all five raise the *same* code `R6_CONFIG_INVALID` at `node.{id}.config.{key}` and run in one fixed short-circuit order — type → enum → minimum → maximum → minLength → maxLength → pattern — with a `return` after the first violation, so one config key never yields more than one error (a value both outside its `enum` and over `maxLength` reports the enum failure only). They are distinguishable by message text, not by code. - **Implementation:** E - **Guaranteed by:** `::testR6WrongTypeIsRejected`, `::… ### [An unknown config key is a warning, not a refusal (R6.c)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592130) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Unknown config key → **warning**, accepted ("ignored at runtime"). - **Implementation:** W - **Guaranteed by:** `WorkflowStructuralValidationTest::testValidatorWarnsButAcceptsUnknownConfigKey` Rule `R6.c` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.c` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Every required config key must be present (R6.b)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592129) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Every key on the **derived** `configSchema.required` list must be present (`array_key_exists` — explicit NULL satisfies); each missing key yields one `R6_CONFIG_REQUIRED` at `node.{id}.config.{key}`. The list is *not* the node type's `required` flags: a param the node type also marks `connectable` is deliberately omitted from `configSchema.required` (SCH-6), so a `required && configurable && connectable` param absent from `data.config` is **accepted at save even when no input edge supplies it** — the omission is decided from the node-type flags, never from the actual edge set. - **Implementat… ### [Refuse a node whose config is not an array (R6.a)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592128) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Non-array `data.config` rejected (`R6_CONFIG_INVALID`) at `node.{id}.config` — but **only on a node carrying a `node_type_id` anchor**: `checkConfig()` returns before the guard for an anchor-less node, so a Note-style node with a scalar `data.config` is accepted by all of R6. - **Implementation:** E - **Guaranteed by:** `WorkflowValidatorTest::testR6NonArrayConfigIsRejected`, `::testR6AnchorLessNodeSkipsTheNonArrayConfigGuard` Rule `R6.a` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R6.a` token, and `scripts/spec-coverage.php … ### [Report a missing plugin once, not once per port (R1.c)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592127) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A missing plugin is reported once, never re-reported per exposed port. - **Implementation:** — - **Guaranteed by:** `::testMissingPluginIsNotDoubleReported` Rule `R1.c` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R1.c` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [A node with no resolvable node type is skipped by the plugin check (R1.b)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592126) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Node with no `node_type_id` anchor / unresolvable node type is **skipped** by R1 (deferred) — R1's skip stands; a node anchored to an *unknown* type is rejected by R9, while a legitimately anchor-less node stays accepted. - **Implementation:** accept - **Guaranteed by:** `::testR1EmptyPluginIsSkipped` Rule `R1.b` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R1.b` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a node whose executor plugin does not exist (R1.a)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592125) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Node whose node-type-resolved executor plugin has no definition rejected (`R1_PLUGIN_MISSING`), no instantiation. - **Implementation:** E - **Guaranteed by:** `::testR1MissingPlugin`; kernel 422+not-persisted Rule `R1.a` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R1.a` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a node with no id, located by its position (R5.c)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592124) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Node with empty/absent `id` rejected, located by array position. - **Implementation:** E - **Guaranteed by:** `::testR5NodeMissingId` Rule `R5.c` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R5.c` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a workflow with more than 1000 edges (R5.b)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592123) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: >1000 edges rejected (`R5_TOO_MANY_EDGES`). - **Implementation:** E - **Guaranteed by:** `::testR5TooManyEdges` Rule `R5.b` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R5.b` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Refuse a workflow with more than 500 nodes (R5.a)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592122) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: >500 nodes rejected (`R5_TOO_MANY_NODES`). - **Implementation:** E - **Guaranteed by:** `WorkflowValidatorTest::testR5TooManyNodes` Rule `R5.a` of `GR-VAL` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: R5.a` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592087 ### [Retire the node config-validate endpoint (API-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592121) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **RETIRED — endpoint deleted (2.x).** The node config-validate endpoint (`POST /api/flowdrop/nodes/{plugin_id}/validate`) reported problems the save path accepts: it used the raw plugin schema, not the derived, edge-aware view (same spirit as R6), so it flagged `configurable && required` params an input edge would satisfy — and it could not become edge-aware without a contract change (it received only `config`, no edges). It had ZERO fdnpm consumers, so the ruled fix was deletion: route, `NodesController::validateConfiguration()` and its `validateValueType()` helper are gone. Save-time validat… ### [A session with no workflow is a 409, not a 500 (API-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592120) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: "Session has no workflow" is a dedicated typed exception (`MissingWorkflowException`) mapped to **409 Conflict** on both doors with the generic body `Session has no associated workflow` — a state problem on the session, same refusal family as the concurrent-turn 409; the internal message (naming the session id) goes to the logger, never the response. Controllers never catch `\RuntimeException` wide (masks real 500s) nor echo `$e->getMessage()` — the launch controller's typed pattern, everywhere. **409 is the agreed number, cross-checked with the editor package's maintainers and confirmed indep… ### [The session-turn door checks its inputs exactly like the launch door (API-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592119) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: The session-turn door validates `inputs` identically to the launch door (unknown keys rejected, required enforced, schema-checked, strict resolve); the lenient `else` that `array_merge`d raw caller input into node-keyed `initialData` is **deleted**, not flagged strict — amends MAN-12/MAN-13. Both doors now share `WorkflowInputChecker`, so the same body earns the same verdict; the turn door raises `InvalidTurnInputException` → 400. - **Implementation:** shared `flowdrop_workflow/src/Utility/WorkflowInputChecker.php`; `WorkflowLauncher::validateInputs()`; `SessionTurnService::executeTurn()`; st… ### [Every JSON door decodes through the shared, bounded decoder (API-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592118) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **Nine controllers accept a JSON body and all nine decode via `ApiResponseTrait::decodeJsonRequest()`**: `WorkflowsController`, `WorkflowLaunchApiController`, `SessionTurnApiController`, `PlaygroundApiController`, `ChatApiController`, `SnapshotApiController`, `TriggerConfigApiController`, `PipelineSignalController`, `InterruptApiController`. The gate is 8 MiB measured by `strlen()`, depth 64 (so 63 levels is the deepest accepted document), non-array decode refused — each as `BadRequestHttpException` → 400. A bare `json_decode($request->getContent())` at an HTTP door is a defect, and there are … ### [One payload key per node-type concept (STORE-13)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592117) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **One name per concept for a node's type.** A node-type *config-entity ID* is `node_type_id` everywhere it appears in a payload — job metadata, node metadata, the serialised node execution result, the node-status broadcast payload, and persisted session-message metadata. A node's *visual* type is `visual_type` in the per-node snapshot payload (and `nodeType` as a config key, per SCH-20). The bare `node_type` key is **not written anywhere**: it used to mean the entity id in run/status/message payloads but the visual type in the snapshot payload, so a reader could not tell which without knowing … ### [A finished turn leaves the session completed, not idle (STORE-12)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592116) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: A finished turn releases the session as **`completed`**, not `idle`; `idle` means created-but-never-executed. **LEGACY READ:** session rows written before 2.x carry `idle` meaning "turn finished", so `WorkflowExecutionService::getSessionStatus()` maps BOTH `idle` and `completed` to `Completed`, and the sub-workflow sync wait accepts both. That mapping stays until the old rows are migrated or age out — no data migration ships with the writer change. - **Implementation:** writers `SessionExecutionService.php:299,321,354`, `DeferredMessageProcessor.php:193`, `SessionInterruptResolvedSubscriber.p… ### [Entity statuses are backed enums whose value is what crosses a boundary (STORE-11)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592115) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: The four entity status vocabularies (`JobStatus`, `PipelineStatus`, `SessionStatus`, `MessageStatus`) are **backed enums**; the backing value is the persisted field value and the string every JSON/event payload carries, so `->value` is what crosses any boundary. The set helpers stay value lists: `PipelineStatus::terminalStatuses()`, `MessageStatus::terminalStatuses()`, `JobStatus::activeStatuses()`, `allowedValues()` (and `PausedReason::budgetReasons()`, still a constant bag) return the strings, so they drop straight into entity-query conditions and `allowed_values`. - **Implementation:** `fl… ### [WorkflowDTO::fromArray() normalizes for the read path only (STORE-10)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592114) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `WorkflowDTO::fromArray()` is a **read/execute-path-only** normalizer with exactly four production call sites (`WorkflowCompiler:100`, `SynchronousOrchestrator:219`, `JobGenerationService:118`, `StateGraphOrchestrator:1678`). It prunes any edge whose source or target does not resolve into `droppedEdges` (keyed by edge id); mints `uniqid('edge_', TRUE)` ids for id-less edges; fills node config as `array_merge($metadata['config'], $data['config'])`, so **the stored `data.config` value wins on collision and defaults only fill absent keys**; and re-keys nodes and edges by id, so on **duplicate ids… ### [Bundle import runs its gates in a fixed order and rolls back on refusal (STORE-9)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592113) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: **Import gates, in this fixed order:** envelope `format` → signature trust → capability manifest → node-type generation → validation → flow-id shape → id collision. Every refusal after generation **rolls the generated node types back**. `BundleImporter::import()` returns a `BundleImportResult` status and never an HTTP code; `WorkflowsController::importResponse()` is the sole mapper: `UNSUPPORTED_FORMAT` → 422 `Unsupported bundle format`; `UNTRUSTED_BLOCKED` → 403 `Bundle publisher is not trusted` (+`signature`, `hint`) unless confirmed+permitted; `MISSING_CAPABILITY` → 422 `Required processors… ### [A workflow's schema version must be semver (STORE-8)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592112) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `schema_version` must be semver (`\d+.\d+.\d+`), enforced by a `Regex` constraint that only bites under config *validation* (plain schema conformance accepts any string). As with every Symfony `Regex`, the empty string is exempt — the entity's `'0.0.0'` property default is what keeps an unset version semver. - **Implementation:** `flowdrop_workflow.schema.yml:68-73` - **Guaranteed by:** `WorkflowStorageApiTest::testSchemaVersionMustBeSemver` Rule `STORE-8` of `GR-STORE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: STORE-8` token, and `scr… ### [The stored config schema is strict about node metadata (STORE-7)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592111) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Config schema is strict: `data.metadata` may contain **only** `node_type_id`; `data.config` is `type: ignore` (unconstrained at storage — only R6 constrains it). - **Implementation:** `config/schema/flowdrop_workflow.schema.yml:272-311` - **Guaranteed by:** `FlowDropWorkflowKernelTest::testAnnotatedSnapshotPassesConfigSchema`; `ConfigSchemaConformanceTest` Rule `STORE-7` of `GR-STORE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: STORE-7` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue:… ### [Saving slims transient canvas state out of the stored workflow (STORE-6)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592110) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `preSave` slims in **two independent passes**, and only when `!isSyncing()`. Pass 1 drops transient canvas state (`selected`/`dragging`/`deletable`, plus `nodeId` at both the node and `data` level) from **every** node. Pass 2 drops the node-level `type` and reduces `data.metadata` to `{node_type_id}` — but only for a node with a resolvable anchor (`data.metadata.node_type_id`, or a legacy `metadata.id` which is renamed to it); an **unanchored node keeps its metadata and its `type` verbatim**, since nothing could re-enrich them on read. `measured`, `position`, `data.config`, `data.label` and `d… ### [A validation failure at the REST boundary is a 422 and never reaches save (STORE-5)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592109) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Validation failure at the REST boundary → 422 with exactly `{success:false, error:'Workflow validation failed', details:[{code,message,locator}]}`, and `$workflow->save()` is never reached. **Errors only:** `validateStructure()` returns NULL the moment `ValidationResult::isValid()` holds, so a warning neither blocks the save nor appears anywhere in the response — only the `errors` list is mapped, never `warnings`. `locator` is a rename of the validator's own `parameter` key. The same helper guards create and update, so both paths refuse identically and a refused update leaves the stored row un… ### [Absent collections default to empty on create; a partial update preserves them (STORE-4)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592108) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Absent `nodes`/`edges`/`metadata` default to `[]` on create; on update only touched when present (partial PUT preserves). `name` is the exception — it is required on update too, so there is no name-omitted PUT. Note the response envelope is not the stored value for `metadata`: `getClientMetadata()` folds `format`/`schemaVersion` back in on read (preSave strips them). - **Implementation:** `WorkflowsController.php:161-163,269-277` - **Guaranteed by:** `WorkflowStorageApiTest::testAbsentCollectionsDefaultToEmptyArraysOnCreate`, `::testPartialUpdatePreservesUntouchedCollections` Rule `STORE-4` … ### [A client-supplied id that already exists is a conflict, never an overwrite (STORE-3)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592107) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Client-supplied `id` that already exists → 409, never overwrite. - **Implementation:** `WorkflowsController.php:148-154` - **Guaranteed by:** `WorkflowStorageApiTest::testDuplicateClientIdConflictsWithoutOverwriting` Rule `STORE-3` of `GR-STORE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-registry: STORE-3` token, and `scripts/spec-coverage.php --check` fails if the rule and its test disagree. Parent issue: #3592095 ### [A workflow name is required and capped at 255 bytes (STORE-2)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592106) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: `name` required, ≤255 chars (create + update) → 400. Two edges worth knowing: the presence test is `empty()`, so the literal name `'0'` is refused as missing; and the cap is `strlen()`, i.e. **bytes**, so a 200-character multibyte name is over it. - **Implementation:** `flowdrop_workflow/…/WorkflowsController.php:140-146,253-259` - **Guaranteed by:** `WorkflowStorageApiTest::testNameIsRequiredOnCreate`, `::testNameLengthIsCappedOnCreate`, `::testNameRulesApplyToUpdate` Rule `STORE-2` of `GR-STORE` in `docs/development/specification-registry.md`. Tests bind to it with a greppable `spec-regist… ### [Branch gateways and which edges activate (RT-BR)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592104) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-BR — 7 rules How a gateway names its active branch, how a branch port is told from a value port, and when a completed source is too stale to satisfy a gate. All 7 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592332 — **BR-1** When a branch edge is gated at all - [ ] #3592333 — **BR-2** The three cases where a branch edge activ… ### [Delivering values between nodes (RT-DATA)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592103) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-DATA — 12 rules Port-to-port delivery: how a value travels along an edge, what happens when several sources feed one port, and when a node is ready to run. All 10 testable rules in this section are covered by a test. The remaining 2 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592339 —… ### [Compiling a workflow into an execution plan (RT-CMP)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592102) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-CMP — 11 rules Preconditions, dependency graph construction, cycle detection, execution ordering, and tool wiring. All 11 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592291 — **CMP-1** What compiling a workflow produces - [ ] #3592292 — **CMP-2** Re-enrichment on the run path is conditional - [ ] #3592293 — **CMP-3** Compile … ### [The pipeline status the editor polls (RT-PIPE)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592101) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-PIPE — 4 rules The polling payload the editor reads to draw node badges. Note the payload is mixed-case by contract — some keys are snake_case and some camelCase — and must not be normalised. All 4 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592379 — **PIPE-1** The live run status is read from persisted entities - [ ] #359238… ### [Choosing and running an orchestrator (RT-ORC)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592100) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-ORC — 17 rules Which execution strategy a run gets and why, the contract they share, and how a run's final status is decided. All 16 testable rules in this section are covered by a test. The remaining 1 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592315 — **ORC-1** The four orchestrat… ### [The StateGraph runner (RT-SG)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592099) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-SG — 15 rules State injection, checkpointing, loop iteration accounting, and how a restore chooses between a snapshot and a checkpoint. All 15 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592364 — **SG-1** How each state field is reduced - [ ] #3592365 — **SG-2** What the runtime hands a node, and what the node must declare to… ### [Interrupts, pausing and resuming (RT-INT)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592098) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-INT — 13 rules Human-in-the-loop and budget pauses: what a paused run records, who is allowed to resume it, and how a snapshot is validated and restored. All 13 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592351 — **INT-1** An interrupted node pauses the pipeline and reports where it stopped - [ ] #3592352 — **INT-2** The int… ### [How a failing node is handled (RT-ERR)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592097) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## RT-ERR — 13 rules The error channel: which exception types become a routable error output, which escape and fail the run, how retryability survives, and when a failed node satisfies a downstream edge. All 12 testable rules in this section are covered by a test. The remaining 1 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the … ### [The JSON API doors (GR-API)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592096) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-API — 4 rules Behaviour shared by every endpoint that accepts a JSON body: the single decoder all of them use, its size and nesting bounds, and how a refusal is reported. All 3 testable rules in this section are covered by a test. The remaining 1 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - … ### [Storing and serving a workflow definition (GR-STORE)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592095) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-STORE — 13 rules The workflow entity and its REST surface: request body bounds, required fields, what a partial update preserves, what is stripped on save, and bundle import. All 13 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592105 — **STORE-1** Refuse an empty, oversized, malformed or too-deeply-nested request body - [ ] #3… ### [Author-defined dynamic ports (GR-DYN)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592094) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-DYN — 7 rules Ports an author adds at configuration time rather than the plugin declaring them: how they are opted into, how names are validated, and what they resolve to when nothing is connected. All 7 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592236 — **DYN-1** A node type opts into dynamic ports by spreading their schem… ### [A workflow's declared inputs and outputs (GR-MAN)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592093) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-MAN — 19 rules The launch manifest: a declared list, never derived from the exposure cascade. Covers the stored schema snapshot, how malformed entries are dropped, and what is checked when a run is launched. All 18 testable rules in this section are covered by a test. The remaining 1 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fai… ### [Resolving a node's parameters (GR-CFG)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592092) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-CFG — 18 rules The resolution cascade for every parameter: wire value, then stored config, then schema default — with presence tested by key existence, so an explicit NULL at a higher priority wins. All 18 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592201 — **CFG-1 (D1)** Gate flags fail closed - [ ] #3592202 — **CFG-2 (D2)*… ### [Turning a plugin schema into ports and forms (GR-SCHEMA)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592091) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-SCHEMA — 30 rules How a node type plus its plugin schema become the ports, config form and defaults the editor shows — including the reserved trigger, tool and error ports, and the unified input/output ports. All 29 testable rules in this section are covered by a test. The remaining 1 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fa… ### [The four expression engines (GR-LANG)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592090) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-LANG — 29 rules Expression Language, Twig, property paths and JSONPath. They deliberately disagree about a missing key (throw / blank / NULL / logged default), so each engine's behaviour is stated separately rather than smoothed over. Also the node-level policy: a genuine expression *failure* fails the node. All 29 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the … ### [Port exposure (GR-EXPO)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592089) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-EXPO — 17 rules Exposure resolves from configuration only — instance ports, then the node type's default, then visible. A hidden port does not exist on the instance: it cannot be wired, and a hidden output's value is stripped where it is produced. All 17 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592219 — **EXPO-1** PortExpo… ### [How edges connect ports (GR-EDGE)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592088) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-EDGE — 9 rules The wire format between two nodes: handle encoding, which keys are structurally required, and how tool and error edges are recognised. All 9 testable rules in this section are covered by a test. Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --check` fails if the two disagree. ### Rules - [ ] #3592162 — **EDGE-1** How a port handle encodes its node, direction and port name - [ ] #3592163 — **EDGE-2** No wire key is stru… ### [What the workflow validator refuses (GR-VAL)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592087) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## GR-VAL — 40 rules Every rule the validator enforces when a workflow is saved: node and edge structure, config against the plugin schema, port exposure, and expression parsing. `R*` ids are the author-facing error codes. All 39 testable rules in this section are covered by a test. The remaining 1 row(s) assert nothing by design (structural statements or cross-references to another section). Each rule below cites its implementation and its binding test in `docs/development/specification-registry.md`; tests reference the rule with a `spec-registry: ` token, and `scripts/spec-coverage.php --c… ### [Return 400 for a malformed API request body](https://git.drupalcode.org/project/flowdrop/-/work_items/3592086) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::bug, code, priority::normal, spec-registry Description: ## Problem Three JSON API endpoints disagreed with the other six about what an invalid request body means. Creating a playground session decoded its optional body by hand and tolerated anything — malformed JSON, a scalar instead of an object, or a payload of any size all silently became "no options", so the session was created as though nothing had been sent. Sending a playground or chat message did use the shared decoder, but wrapped it in a catch-all handler. The decoder reports a bad body by throwing, so every malformed message came back as a 500 "failed to process" — a server error for … ### [Write down and test every runtime and workflow-language rule](https://git.drupalcode.org/project/flowdrop/-/work_items/3592085) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, documentation, priority::normal Description: ## Problem Most of FlowDrop's behaviour existed only in the code. That made two things hard: knowing whether a surprising result was a bug or the design, and changing anything with confidence that nothing downstream depended on the old behaviour. ## What changed `docs/development/specification-registry.md` now enumerates every rule of the workflow language (definition grammar, schema discovery, config resolution, port exposure, expressions) and of the runtime (compilation, parameter resolution, branching, error handling, interrupts, state, status reporting). Each rule has a stable id, cite… ### [Remove unused API and developer surfaces from 2.x](https://git.drupalcode.org/project/flowdrop/-/work_items/3592084) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: ## Problem 2.x carried a number of endpoints, methods and configuration keys that nothing called and nothing read. Some were half-built features, some were superseded, and a few actively misled: an endpoint reporting metrics that were always zero, because it collected them per-request with no persistent backing. Dead surface is not free — it looks like API, so it constrains refactoring and misleads anyone reading the code for guidance. ## What changed Removed, each verified to have no callers first: - the status-polling endpoints (including the health and metrics routes) and their tracker… ### [Report pipeline and job status consistently to the editor](https://git.drupalcode.org/project/flowdrop/-/work_items/3592083) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::bug, code, priority::normal, spec-registry Description: ## Problem The editor polls the pipeline API to draw node status badges, and the payload it received was not dependable: - The job status summary came back in three different shapes depending on which code path built it, and some shapes were missing status keys entirely. - Two controllers incremented status counters without checking the status was one they knew, which raised PHP warnings in production when an unrecognised value appeared. - It was undocumented which node a status entry belonged to when a node runs more than once, so a loop's badges could not be drawn reliably. ## What change… ### [Make error routing, cancellation and resume behave the same in every runner](https://git.drupalcode.org/project/flowdrop/-/work_items/3592082) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::bug, code, priority::major, spec-registry Description: ## Problem FlowDrop has more than one execution strategy, and they had drifted apart on the parts users notice most: - The direct synchronous runner ignored error outputs completely — a node's `error` edge did nothing there, so the same workflow routed failures under one runner and failed outright under another. - Cancelling a run was not announced like other terminal outcomes, so a cancelled sub-workflow could leave its parent waiting, and a session might never notice the run had stopped. - Cancellation was not recorded in the checkpoint, so a cancelled run could be resumed back to life. - … ### [Catch broken workflows when they are saved, not when they run](https://git.drupalcode.org/project/flowdrop/-/work_items/3592081) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::feature, code, priority::normal, spec-registry Description: ## Problem Several ways of breaking a workflow were accepted at save time and only surfaced later — as a confusing runtime error, or as a node that silently never ran. The editor would happily store a definition the engine could not honour. ## What changed The workflow validator now refuses these at save, each with a specific message pointing at the offending node or edge: - a node whose type does not exist - duplicate node ids, and duplicate or missing edge ids - an edge from a node to itself - two identical edges between the same pair of ports - an expression that its engine cannot parse… ### [Expression errors fail the node and route to its error edge](https://git.drupalcode.org/project/flowdrop/-/work_items/3592080) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::bug, code, priority::major, spec-registry Description: ## Problem The four nodes that evaluate author-written expressions each handled a broken expression differently: - **Data Mapper** aborted the node. - **Data Extractor** turned the failure into a normal-looking result, so a typo in a path looked like "no match found". - **Data Shaper** and **Prompt Template** let the raw engine exception escape, so it bypassed error routing entirely and failed the whole run. An author had no way to handle a broken expression, and no consistent signal that one had happened. ## What changed All four now agree: an expression the engine cannot evaluate fails … ### [[meta] Make the 2.x runtime and workflow-language contracts explicit and tested](https://git.drupalcode.org/project/flowdrop/-/work_items/3592079) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::plan, code, documentation, priority::normal Description: ## Problem FlowDrop's behaviour was largely undocumented, and where it *was* described the description and the code had drifted apart. Two nodes doing the same thing could fail differently, the same workflow could behave one way under one runner and another way under a second, and there was no way to tell "not implemented yet" from "implemented wrong". That mattered most in two places: what happens when something goes wrong at runtime, and what the workflow definition itself actually promises (schema discovery, config resolution, port exposure, expressions). ## Approach Write the rules dow… ### [Refuse an empty, oversized, malformed or too-deeply-nested request body (STORE-1)](https://git.drupalcode.org/project/flowdrop/-/work_items/3592105) State: closed | Updated: 2026-07-30 | Author: Shibin Das (D34dMan) | Assigned: unassigned | Labels: category::task, code, priority::normal, spec-registry Description: Request body: empty → 400; >8 MiB → 400; invalid JSON → 400; nesting at or past 64 levels → 400 (the bound is json_decode's `$depth` argument, so 63 levels is the deepest accepted document); non-object/array (any JSON scalar, incl. `null`) → 400. Every case raises `BadRequestHttpException`, which Symfony renders as the 400. - **Implementation:** `src/Controller/Api/ApiResponseTrait.php:165-185` - **Guaranteed by:** `DecodeJsonRequestTest` (11 cases, incl. both size/depth boundaries) Rule `STORE-1` of `GR-STORE` in `docs/development/specification-registry.md`. Tests bind to it with a greppabl… ### [AI Assistant is broken from 1.5.0](https://git.drupalcode.org/project/flowdrop/-/work_items/3592073) State: closed | Updated: 2026-07-30 | Author: David Galeano (gxleano) | Assigned: Shibin Das (D34dMan) | Labels: category::bug, priority::critical, state::fixed Description: When you try to use the AI Assistant inside the FlowDrop workflow, after applied the changes it got stuck. ### [Add "Show Pipelines" to the operations per workflow](https://git.drupalcode.org/project/flowdrop/-/work_items/3589740) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: Shibin Das (D34dMan) | Labels: category::feature, code, priority::normal, state::fixed Description: >>> [!note] Migrated issue Reported by: [gxleano](https://www.drupal.org/user/3591999) >>> Add Show Pipelines to the operations to list pipelines per workflow (right now the only way to check the pipelines is going into the pipeline list and filter by workflow) ### [Remove "Pending" tag when the workflow is executing and the component has been skipped](https://git.drupalcode.org/project/flowdrop/-/work_items/3589739) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: Shibin Das (D34dMan) | Labels: category::feature, code, priority::normal, state::fixed Description: >>> [!note] Migrated issue Reported by: [gxleano](https://www.drupal.org/user/3591999) >>> Add Skipped tag instead of Pending when the node processors has been skipped of been executed --- MERGE REQUESTS (24h) --- (none) --- COMMITS (24h) --- (none) ======================================================================== ## [21] summariseModule:agui:executive ======================================================================== You are a technical writer producing a newsletter section about recent Drupal module activity. Module: AG-UI (machine name: agui) Reporting period: last 24h (2026-07-30T08:14:12+00:00 to 2026-07-31T08:14:12+00:00) You are writing for a non-technical executive audience (CEO/leadership level). Focus on: business impact, strategic progress, risks, and what is being delivered. Avoid technical jargon. Do not mention branch names, function names, or API details. Explain what each piece of work means for users or the project's goals. Keep risk language proportionate to the stage of the software. For alpha or beta modules, unassigned bugs or open issues are normal and expected — do not describe them as 'reputational risks' or use alarmist framing. Reserve strong risk language for issues that are genuinely critical or blocking a stable release. Focus your report on activity that occurred within the reporting period (comments, MRs merged, commits pushed, status changes). Use the issue description to understand what each issue is about and provide context, but do not report on the description itself as news — it is background information only. Do not list every issue/MR individually — synthesise into prose. Keep it under 200 words. Do not use emoticons or mdashes. Do not wrap usernames or contributor names in tags — mention them as plain text. When mentioning a specific issue or MR, always hyperlink it using the URL provided in the data (e.g. Issue Title or the Markdown equivalent). Do not reference issues or MRs by number alone — always use their title as the link text. Do NOT attribute any action to a named individual. Do not say who merged, fixed, reviewed, authored, or opened anything. The "Author" and "Assigned" labels in the data are context only — never surface them as "X did Y". Describe the work itself in the passive voice (e.g. "the provider refactor was merged"), not the person who did it. The author of a merge request is often not the person who completed or merged the work, so naming them is misleading. End your section with a single line listing the people who were active this period, exactly in this form (plain text, no ): "Contributors: Ahmad Khalil (ahmad-khalil-imagex) [1], Bryan Sharpe (b_sharpe) [3]". Use only the names from that list, verbatim, keeping any trailing "[N]" commit count exactly as shown. Do not introduce any other names. Format your response as an HTML fragment. Start with
AG-UI
then use
,
,
/
, and as needed. Output only the HTML fragment with no surrounding , , or
tags. After the project summary prose, add a single subsection titled "
How can I help on this project?
" aimed at a non-technical executive. Suggest 2-3 concrete, high-level ways a leader could support or unblock progress (e.g. resourcing, stakeholder alignment, decision-making, funding, advocacy). Keep it under 60 words. Do not add any other 'How can I help' text anywhere else in the section. CRITICAL: Before writing each suggestion, verify it against the issue data. Do not suggest actions that are already in progress or covered by an existing MR — for example, do not suggest that work needs to be started if an issue already has a Related MR. --- ISSUES UPDATED IN LAST 24h --- Each issue includes its description (for context) and the most recent comments from the last 24h (or last 5 if fewer than 5 occurred in that window). ### [Add config for max characters](https://git.drupalcode.org/project/agui/-/work_items/3585465) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: Bryan Sharpe (b_sharpe) | Labels: category::feature, code, priority::normal, state::accepted Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !40 [Add validator and extractor services/methods and new setting.](https://git.drupalcode.org/project/agui/-/merge_requests/40) | State: merged 2026-07-30 | Author: Bryan Sharpe (b_sharpe), 585 diff lines Description: >>> [!note] Migrated issue Reported by: [b_sharpe](https://www.drupal.org/user/2512258) >>> Problem/Motivation Token exhaustion exploitation is becoming a problem and although this generally can be configured at the assistant level, it makes sense to just deny right away via chat if a character limit is exceeded. We should: Add a character limit config Report back a message to the user if limit is exceeded Deny the chat from going to the remote ### [Better Error Handling in chat](https://git.drupalcode.org/project/agui/-/work_items/3590046) State: closed | Updated: 2026-07-30 | Author: Bryan Sharpe (b_sharpe) | Assigned: Bryan Sharpe (b_sharpe) | Labels: Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !39 [Add error util and handler.](https://git.drupalcode.org/project/agui/-/merge_requests/39) | State: merged 2026-07-30 | Author: Bryan Sharpe (b_sharpe), 86 diff lines Description: **Problem:** When the AG-UI chat endpoint (/agui/api/chat) returns a non-2xx HTTP response — for example a 403 from the new anonymous JWT/flood access check, or any other error before/instead of a normal SSE stream — the raw response body is surfaced verbatim inside the chat UI as if it were assistant content, instead of a short, user-friendly error message. This happens in two places on the frontend (components/chat/src/js/), both with the same anti-pattern: on a non-ok response they read the entire response body and bake it directly into a thrown Error's message, with no truncation,… ### [Allow Token support on Assistant Controller](https://git.drupalcode.org/project/agui/-/work_items/3589993) State: closed | Updated: 2026-07-30 | Author: drupalbot | Assigned: Bryan Sharpe (b_sharpe) | Labels: category::feature, code, priority::normal, state::accepted Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !38 [Resolve "Allow Token support on Assistant Controller"](https://git.drupalcode.org/project/agui/-/merge_requests/38) | State: merged 2026-07-30 | Author: Bryan Sharpe (b_sharpe), 673 diff lines Description: >>> [!note] Migrated issue Reported by: [b_sharpe](https://www.drupal.org/user/2512258) >>> Problem/Motivation Allowing anonymous users to utilize agents is very common, but without some sort of auth it can allow bots/scripts to try rack up your tokens via posts requests. Using the token won't prevent bots collecting the token and using it, but at least mitigates direct post request. ### [Enable Drupal GitLab CI pipeline and add Unit/Kernel/Functional test coverage](https://git.drupalcode.org/project/agui/-/work_items/3590044) State: closed | Updated: 2026-07-30 | Author: Ahmad Khalil (ahmad-khalil-imagex) | Assigned: Bryan Sharpe (b_sharpe) | Labels: state::rtbc Related MRs (already exist for this issue — check state before suggesting new contributions): - MR !34 [Resolve "Enable Drupal GitLab CI pipeline and add Unit/Kernel/Functional test coverage"](https://git.drupalcode.org/project/agui/-/merge_requests/34) | State: merged 2026-07-30 | Author: Ahmad Khalil (ahmad-khalil-imagex), 1643 diff lines Description: ### Problem/Motivation The agui repository currently has no `.gitlab-ci.yml`, so no pipeline runs on merge requests — no coding-standards checks, no static analysis, and no automated tests. It also has no PHPUnit tests at all, for either the main module or the `agui_mercure` sub-module. Recent MRs (e.g. !33) have had to rely entirely on manual and ad-hoc verification. ### Proposed resolution **1. Enable the standard Drupal GitLab CI pipeline** by adding the stock `.gitlab-ci.yml`: ```yaml include: - project: project/gitlab_templates ref: default-ref file: - '/includes/inclu… --- MERGE REQUESTS (24h) --- (none) --- COMMITS (24h) --- - [cfa2abb7](https://git.drupalcode.org/project/agui/-/commit/cfa2abb716b2c9c133ed4a911f464d8805fbbca0) Add validator and extractor services/methods and new setting. — Bryan Sharpe (2026-07-30T10:39:33.000-07:00) - [e705cb5b](https://git.drupalcode.org/project/agui/-/commit/e705cb5b742e978bf18d15faa0c705ffb2b9ca0d) Add error util and handler. — Bryan Sharpe (2026-07-30T10:13:02.000-07:00) - [66dc00a3](https://git.drupalcode.org/project/agui/-/commit/66dc00a3173ff0f44161f47dea0a1f48cb8d042a) Resolve "Allow Token support on Assistant Controller" — Bryan Sharpe (2026-07-30T16:25:00.000+00:00) - [41319ce8](https://git.drupalcode.org/project/agui/-/commit/41319ce8e4c870ae3e7a0e0aa39238c6eb489ec5) Resolve "Enable Drupal GitLab CI pipeline and add Unit/Kernel/Functional test coverage" — Ahmad Khalil (2026-07-30T15:01:15.000+00:00) ======================================================================== ## [22] generateTldr:executive ======================================================================== You are an editor distilling a Drupal AI project newsletter into its most important highlights. You are writing for a non-technical executive audience. Focus on business impact, strategic progress, and delivery milestones. Avoid all technical jargon. Read all the module summaries below. Separate the highlights into two categories: - SHIPPED: things that were merged, fixed, released, or completed during this period. - ONGOING: things that are actively in progress, under review, or blocked. Be specific — name the module, what happened, and why it matters. Do not use emoticons or mdashes. Do not include any text outside the two sections. When you mention a specific issue or merge request, add an inline citation using [N] where N is the reference number from the list below. You may cite multiple references per item, e.g. [1][3]. Place citations immediately after the relevant phrase, before any punctuation. Format as two HTML sections. Use exactly this structure (all
elements must be inside the
, never outside it):
Shipped

Title here — One sentence explanation [1].

Another title — One sentence explanation.

Ongoing

Title here — One sentence explanation [2].

Up to 5 items per section. Do not output any text, tags, or characters outside these two sections. Output only the HTML fragment, no surrounding tags. --- REFERENCE LIST --- [1] MDXEditor fails to parse Drupal tokens in AI Agents prompts (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586613 [2] MDXEditor throws error when prompt includes a colon (:) character (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586619 [3] Decide permission system for new AI Platform and AI Inference Providers (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586628 [4] Support Automator Chain trigger with Field Widget Actions (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586602 [5] What providers for TextClassification? (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586629 [6] The Toolbar Chatbot runs the fold out animation on page reload (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3568246 [7] Support interactive/rich content (e.g. links) in the AI tooltip component (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586630 [8] Streaming chat forces plain-text hostname filtering, corrupting URLs inside HTML attributes (e.g., href="") (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586624 [9] Adopt symfony/ai component v0.8 as platform provider (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586427 [10] AI Automator Token Replacement with removing unresolved Tokens (Checkbox?) (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586535 [11] Add a ChatMemoryInterface for storing ChatBot chat history (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586539 [12] [1.x] Add a setup-automators agent skill to configure automators on fields (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586563 [13] Add a configure-ai-settings agent skill for general AI settings (default models, providers, timeout, trusted domains) (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586562 [14] Add a setup-guardrails agent skill to configure guardrails, guardrail sets, and global guardrails (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586561 [15] Streamed chatbot agent response (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3578168 [16] Assistants backed by an agent never stream (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586627 [17] Refactor CommonMark instance creation (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586608 [18] Issue #3586602: Add a field widget action base class and text plugin to run... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1887 [19] Issue #3586602: Add a field widget action base class and text plugin to run... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1888 [20] Issue #3586602: Add a field widget action base class and text plugin to run... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1886 [21] Issue #3586602: Add a field widget action base class and text plugin to run... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1828 [22] feat: #3586585 Add YAML support to the MDX editor code blocks (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1823 [23] #3568246: fix late chatbot opening on page load (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1428 [24] feat: #3586427 Adopt symfony/ai v0.8's Platform concept (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1619 [25] Add CommonMarkConverterFactory service. (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1881 [26] Issue #3586535: AI Automators strip unresolved tokens from prompts (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1884 [27] Issue #3586589: Add ChatMemory plugin type (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1885 [28] fix: #3586589 Do not assume action definitions have a type when deriving action plugin functions (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1835 [29] bug: #3586624 Streaming chat forces plain-text hostname filtering, corrupting... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1883 [30] Resolve #3586627: Assistants backed by an agent never stream (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1882 [31] "1.x backport" (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1321 [32] Issue #3586620 Merge 1.3.x guardrails (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1880 [33] Create a skill for manual before/after testing of any issue, with optional glab upload (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586629 [34] Onboard Silver AI partner: Specbee (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586639 [35] Add Silver AI partner to d.o pages: Specbee (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586638 [36] Run AI partner audit report: Specbee (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586637 [37] Onboard Gold/Silver AI partner: TEMPLATE (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3579583 [38] Add Gold/Silver AI partner to d.o pages: TEMPLATE (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3579591 [39] Run AI partner audit report: TEMPLATE (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3579584 [40] Update AI partner badges to use Partner instead of Sponsor (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586636 [41] Add Gold AI partner to d.o pages: Pantheon+Omedia (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586631 [42] Onboard Gold AI partner: Pantheon+Omedia (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586630 [43] Partner contributor audit and cleanup August 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586634 [44] Update AI partner logo wall with latest logos July 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586635 [45] Update AI partner logo wall with latest logos March 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3580150 [46] Partner and contributor offboarding for July 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586633 [47] Partner and contributor offboarding for June 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586553 [48] Migrate the ECA agent to the Tools + ReAct architecture (create-only) (ai_integration_eca, Issue) — https://git.drupalcode.org/project/ai_integration_eca/-/work_items/3585017 [49] Resolve "Migrate the ECA agent to the Tools + ReAct architecture (create-only)" (ai_integration_eca, MR) — https://git.drupalcode.org/project/ai_integration_eca/-/merge_requests/14 [50] add support for batch embeddings (ai_provider_openai, MR) — https://git.drupalcode.org/project/ai_provider_openai/-/merge_requests/59 [51] Resolve #3612042 "Rate limits" (ai_provider_openai, MR) — https://git.drupalcode.org/project/ai_provider_openai/-/merge_requests/80 [52] Resolve #3613982 "Bug with gpt" (ai_provider_openai, MR) — https://git.drupalcode.org/project/ai_provider_openai/-/merge_requests/81 [53] Data loss: Deleting or clearing items in a Search API index deletes data from other indexes sharing the same Vector DB collection (ai_provider_amazeeio, Issue) — https://git.drupalcode.org/project/ai_provider_amazeeio/-/work_items/3586238 [54] feat: send X-Amazee-Client request tracking header (ai_provider_amazeeio, MR) — https://git.drupalcode.org/project/ai_provider_amazeeio/-/merge_requests/81 [55] [#3552969] feat: Refactor AzureProvider to use OpenAiBasedProviderClientBase (ai_provider_azure, MR) — https://git.drupalcode.org/project/ai_provider_azure/-/merge_requests/22 [56] Issue #3586862 by ignacio.perez.puertas: Re-apply Attributes columns after clear+reindex cycle (ai_vdb_provider_postgres, MR) — https://git.drupalcode.org/project/ai_vdb_provider_postgres/-/merge_requests/24 [57] Token Auth is not working (mcp, Issue) — https://git.drupalcode.org/project/mcp/-/work_items/3584901 [58] Resolve "Token Auth is not working" (mcp, MR) — https://git.drupalcode.org/project/mcp/-/merge_requests/52 [59] Add a way to set provider tags in the runner (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3557418 [60] Let an agent use a role when running a tool (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3518167 [61] Add limits on how often a tool can run (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3547995 [62] Give a parent agent possibility to forward request as is (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3550098 [63] Make it possible to pick providers per agent (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3535760 [64] Chatbot truncates 'search_string' context value while tool explorer does not (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3547304 [65] Chatbot repeats itself even after 'clear history' if 'return direct' (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3547225 [66] Create implementation of ShortTermMemory (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3546411 [67] Draft: Resolve "Give a parent agent possibility to forward request as is" (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/326 [68] Issue#3547304:chatbot-truncates-search-string-context-value-while-tool-explorer-does-not fixes (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/327 [69] Issue #3535760: Provider picker (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/315 [70] Issue#3547225-chatbot-repeats-itself-even-after-clear-history-if-return-direct fixes (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/325 [71] Issue#3541337-module-agent-fails fixes. (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/324 [72] Issue#3539557:error-message-when-using-the-ai-assistant-to-add-a-content-type fixes (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/323 [73] Configuration-sourced input values fatal: getConfigurationValue() semantics are inverted (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582959 [74] validateInputValue() only validates the first item of a multiple input (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582960 [75] ToolBase::access() throws on invalid/missing input instead of returning forbidden (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582961 [76] Correct API signatures before the RC1 freeze (batch) (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582962 [77] Prefix module-owned identifiers: alter hook, cache key, and 'text' data type ID (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582963 [78] Rework the tool execution contract: result naming, concrete typing, and decoupling from core ExecutableInterface (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582964 [79] Implement getCacheContexts() or drop CacheableDependencyInterface from ToolInterface (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582965 [80] Annotate the API surface (@api/@internal) and add tool.api.php (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582966 [81] Harden the 'administer tool' permission (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582967 [82] Tool Explorer execute form: masked exception on access denial, duplicate messages, no validation pass (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582968 [83] Tool Explorer RC cleanup: render arrays, dead cache tag, menu placement, first tests (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582969 [84] Drush hardening: --uid default, silently dropped inputs, exit codes (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582970 [85] Make violation messages translatable and stop surfacing raw exception text (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582971 [86] Emit richer JSON Schema: map remaining constraints and type formats (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582972 [87] Extend input coercion for unambiguous LLM value shapes (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582973 [88] Complete kernel coverage of the typed input/output traits and definition pipeline (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582974 [89] checkRequirements() is declared on the frozen interface but never called anywhere (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582975 [90] Filter workflow-only tools from one-shot CLI invokers (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582977 [91] Track Drupal core CLI alignment: metadata mapping, typed-outputs advocacy, future CLI invoker (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582976 [92] [META] Path to 1.0.0-rc1 (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582978 [93] Entity handle descriptions are HTML-escaped in LLM-facing schemas (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582958 [94] A tool whose input stage fails never executes, and external getResult() calls then throw BadMethodCallException, masking the error feedback (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582957 [95] Anthropic rejects tool schemas: nullable optional inputs render an object under "type" (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582956 [96] tool_ai_connector throws `BadMethodCallException` when the tool has not executed (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582948 [97] [AI Connector] - Context Data missing after execute (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3576586 [98] MapDefinitionNormalizer and ContextDefinitionNormalizer break REST serialization (same as #3568588) (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582939 [99] Issue #3582959 by michaellander: Configuration-sourced input values fatal:... (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/111 [100] Resolve "Entity handle descriptions are HTML-escaped in LLM-facing schemas" (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/110 [101] Resolve "A tool whose input stage fails never executes, and external getResult() calls then throw BadMethodCallException, masking the error feedback" (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/109 [102] Resolve "Anthropic rejects tool schemas: nullable optional inputs render an object under "type"" (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/108 [103] Resolve "tool_ai_connector throws `BadMethodCallException` when the tool has not executed" (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/107 [104] Issue #3576586 by b_sharpe: Set parent context data as well as input. (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/76 [105] Issue #3582939: Fix getSupportedTypes() in MapDefinitionNormalizer and... (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/95 [106] RTL support for Canvas visual editor (logical CSS properties, Radix DirectionProvider, autocomplete magnifier, and Undo/Redo timelines) (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591840 [107] Translatable props missing from TMGMT form when component instances cannot be auto-updated to active version (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591875 [108] Strengthen AutoSaveManager to generate stable hashes (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591785 [109] Dependency Dashboard (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591657 [110] CLI push includes unsupported label property for content templates (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591899 [111] Automatically create components when themes are installed (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591898 [112] Canvas CLI sync fails for media and link props in global regions (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591897 [113] Error message for empty value is displayed for select props even when they're not required (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591894 [114] Canvas AI: Add Tools dropdown to chat UI (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591856 [115] Automate MR review using PHPCS: disallow `\Drupal::service('something')`, require `\Drupal::service(Something::class)` whenever possible, with automatic fixing (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3581133 [116] Canvas AI: Improve the schema of the place_components tool (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591881 [117] Canvas AI: Add an Agents & Tools settings form to select the main agent and chat Tools (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591882 [118] Draft: fix: #3591840 RTL support for Canvas visual editor (logical CSS properties, Radix DirectionProvider, autocomplete magnifier, and Undo/Redo timelines) (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1453 [119] #3591875: "Translatable props missing from TMGMT form when component instances cannot be auto-updated to active version" (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1418 [120] chore(deps): update dependency cspell to v10 (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1273 [121] chore(deps): update dependency @eslint/compat to v2 (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1306 [122] chore(deps): update dependency @chromatic-com/storybook to v5 (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1305 [123] fix(deps): update npm minor and patch (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1238 [124] chore(deps): update mysql docker tag to v8.3 (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1272 [125] chore: version packages (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1452 [126] fix(CLI Tool): #3591899 CLI push includes unsupported label property for content templates (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1451 [127] feat: #3518272 support all entity types with configurable displays for content templates (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/791 [128] Generate components when extensions are installed, even if syncing config (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1450 [129] feat(CLI Tool): Return flexible codebase files to local environment on canvas pull (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1443 [130] Draft: #3591838 [PHASE 2] introduce color props (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1432 [131] feat(Headless): #3591861 Add a Canvas-owned routed content endpoint for headless apps (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1436 [132] #3591838 brand kit color implementation (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1385 [133] chore: version packages (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1449 [134] fix(CLI Tool): #3591897 Canvas CLI sync fails for media and link props in global regions (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1446 [135] fix(UI): #3591894 Error message for empty value is displayed for select props... (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1440 [136] Draft: #3591810 Add AiWizardDev, a dev chat wizard that posts to... (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1448 [137] Draft: Resolve "Canvas AI: Add Tools dropdown to chat UI" (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1447 [138] #3581133: Automate MR review using PHPCS: disallow `\Drupal::service('something')`, require `\Drupal::service(Something::class)` whenever possible, with automatic fixing (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1297 [139] Issue #3591882: Add an Agents & Tools settings form. (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1445 [140] Issue #3577155: Add support for file fields using custom stream wrappers (currently only `public` is supported) (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1204 [141] #3591881 Canvas AI: Improve the schema of the place_components tool (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1439 [142] feat: #3567225 Allow per-node override of Content Template via checkbox in node selector (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/948 [143] Avoid loading the full published catalog on the CCC overview page (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586355 [144] Avoid functional-test dual-container traps (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586325 [145] Rename entity bundle and target entity scope plugins for better DX (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586276 [146] Improve conditional subcontext disabled-state behavior and admin UX (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586292 [147] Allow scope plugins to declare an optional icon for UI display (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586262 [148] Complete scope plugin persistence API: manager orchestration, target entity encapsulation, and plugin-driven admin/selection (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586243 [149] Create Mad Libs style template for the CCC (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586340 [150] [Discuss] Adding priority to context item to affect ranking (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586364 [151] [Discuss] Review context selection ranking factors before 1.0 (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586365 [152] CCC beta3 blog post (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586332 [153] beta2 upgrade fails at updates 10006 and 10011 after bundleless entity conversion (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586343 [154] Update relevant CCC skipped tests (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586263 [155] QA team start testing CCC to get familiar with functionality and create QA plan (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586342 [156] Restore Drupal 10 compatibility and repair incomplete beta3 upgrades (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586338 [157] Clean up CCC inconsistencies and DX issues before rc1 (part 3) (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586271 [158] Add a dedicated editorial workflow for AI Context Items (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586345 [159] Issue #3586355: Avoid loading the full published catalog on the CCC overview page. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/232 [160] Issue #3586325: Fix functional-test dual-container traps in AiContextAdminSettingsTest. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/225 [161] Issue #3586276: Rename entity bundle and target entity scope plugins for better DX (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/195 [162] Issue #3586292: Exclude conditional subcontext items when AI decisions are disabled. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/226 [163] Issue #3586343: Fix beta2 upgrade failures in updates 10006, 10008, and 10011. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/229 [164] Issue #3586338: Restore Drupal 10 compatibility and repair beta3 upgrades. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/223 [165] Issue #3586345: Add a dedicated editorial workflow for AI Context Items (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/236 [166] Show AI status indicator next to the Generate button (ai_ckeditor, MR) — https://git.drupalcode.org/project/ai_ckeditor/-/merge_requests/6 [167] RagTool::execute() should expose structured per-result data and check entity access (ai_search, Issue) — https://git.drupalcode.org/project/ai_search/-/work_items/3584031 [168] Defer default search item access checking to the Search API datasource plugin (ai_search, Issue) — https://git.drupalcode.org/project/ai_search/-/work_items/3584042 [169] [PP-1] Provide an API for performing access check on non-content entities (ai_search, Issue) — https://git.drupalcode.org/project/ai_search/-/work_items/3579758 [170] Introduce a dedicated runtime access-checking API for AI Search / RAG filtering (ai_search, Issue) — https://git.drupalcode.org/project/ai_search/-/work_items/3584043 [171] bug: #3584035 Reset chunk-slicing progress when index is cleared or reset-tracker is run (ai_search, MR) — https://git.drupalcode.org/project/ai_search/-/merge_requests/71 [172] Support non content entity datasources (ai_search, MR) — https://git.drupalcode.org/project/ai_search/-/merge_requests/25 [173] Issue #3579758: Provide API for access checks on non-content entities (ai_search, MR) — https://git.drupalcode.org/project/ai_search/-/merge_requests/49 [174] [PP-1] Introduce a dedicated runtime access-checking API for AI Search / RAG filtering (ai_search, MR) — https://git.drupalcode.org/project/ai_search/-/merge_requests/75 [175] Add documentation (ai_translate, Issue) — https://git.drupalcode.org/project/ai_translate/-/work_items/3585534 [176] Fix Pipeline (ai_translate, Issue) — https://git.drupalcode.org/project/ai_translate/-/work_items/3585537 [177] Issue #3585537: Fix the Pipelines by adding composer.json (ai_translate, MR) — https://git.drupalcode.org/project/ai_translate/-/merge_requests/34 [178] Draft: Resolve "Add documentation" (ai_translate, MR) — https://git.drupalcode.org/project/ai_translate/-/merge_requests/32 [179] Add detail logic to the playground pipelines and add the ability to show the debug data by clicking on the executed pipeline item (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3589741 [180] A state update is applied through the reducers after the node completes (SG-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592366 [181] What the runtime hands a node, and what the node must declare to see it (SG-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592365 [182] How each state field is reduced (SG-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592364 [183] An engine that cannot consume a snapshot must throw (INT-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592363 [184] A terminal snapshot is not resumable (INT-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592362 [185] A checkpoint round-trip preserves which terminal status it was (INT-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592361 [186] An async handover seeds the queued run from the snapshot (INT-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592360 [187] Saving a snapshot is an upsert keyed by execution id (INT-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592359 [188] Snapshot validation returns a fixed set of codes (INT-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592358 [189] The workflow version hashes structural data only (INT-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592357 [190] What a snapshot carries (INT-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592356 [191] A pipeline signal is polled between jobs, never mid-job (INT-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592355 [192] The four conditions for a node to own a resume (INT-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592354 [193] Resolving an interrupt resets the job and resumes the pipeline (INT-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592353 [194] The interrupt entity is persisted by a subscriber (INT-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592352 [195] An interrupted node pauses the pipeline and reports where it stopped (INT-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592351 [196] Tools are handed to a processor only when there are some (DATA-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592350 [197] The model-facing tool schema omits parameters already filled (DATA-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592349 [198] Tool availability projects into tool bindings, not into data (DATA-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592348 [199] The unified output port composes exposed outputs only (DATA-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592347 [200] The effective execution config is stamped on the pipeline (SG-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592376 [201] Which stored state a resume restores, in order (SG-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592375 [202] A checkpoint per node, chained, plus one at the end (SG-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592374 [203] The reserved trigger port means no branch for loopback naming (SG-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592373 [204] An edge condition never routes (SG-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592372 [205] How a repeated node's result is keyed (SG-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592371 [206] Loopback re-entry needs an active branch and remaining work (SG-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592370 [207] Routing decides per edge and dispatches per target (SG-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592369 [208] The loopback input doubles as the item result (SG-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592368 [209] How a ForEach loop initialises and finishes (SG-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592367 [210] Which payloads the status vocabulary guards (PIPE-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592381 [211] The job status summary has one shape, derived from the enum (PIPE-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592380 [212] The live run status is read from persisted entities (PIPE-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592379 [213] The execution id the editor polls is the pipeline id (SG-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592378 [214] Exceeding the iteration budget throws (SG-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592377 [215] node_statuses is keyed by the workflow node id (PIPE-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592382 [216] A hidden output is stripped where it is produced (DATA-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592346 [217] Inside a node, the parameter-resolution cascade decides (DATA-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592345 [218] Launch data fills in under edge-delivered inputs (DATA-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592344 [219] Loopback and tool edges are dropped from data delivery (DATA-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592343 [220] Readiness promotes a job whose dependencies are met (DATA-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592342 [221] A trigger edge carries no data (DATA-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592341 [222] One value per port, last executor wins (DATA-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592340 [223] Delivery is port to port, both names read from the handle (DATA-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592339 [224] Direct sync skips a node whose trigger was never satisfied (BR-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592338 [225] Staleness gates a branch decision, not delivery (BR-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592337 [226] Branch gating applies to trigger and data ports alike (BR-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592336 [227] A node's configured branches are the authority on branch ports (BR-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592335 [228] How active_branches is normalized (BR-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592334 [229] The three cases where a branch edge activates (BR-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592333 [230] When a branch edge is gated at all (BR-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592332 [231] A cancelled run is announced like any other terminal outcome (ORC-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592331 [232] Claiming a job is atomic under concurrent workers (ORC-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592330 [233] Auto-resume is gated, not unconditional (INT-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592329 [234] A terminal pipeline cannot be paused or resumed (INT-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592328 [235] A resume re-enters through the pipeline's declared orchestrator (ORC-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592327 [236] An async launch returns queued immediately (ORC-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592326 [237] How a run's terminal status is decided (ORC-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592325 [238] An iteration and time budget breaks the loop (ORC-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592324 [239] A pipeline engine is a ready-job loop (ORC-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592323 [240] Direct sync filters which trigger node starts the run (ORC-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592322 [241] Direct sync walks the execution order once (ORC-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592321 [242] Every strategy shares one contract and one hierarchy (ORC-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592320 [243] Capability queries are answered from the plugin definition only (ORC-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592319 [244] StateGraph is the session default, not the global one (ORC-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592318 [245] An unknown orchestrator type falls back with a warning (ORC-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592317 [246] How the default orchestrator is resolved (ORC-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592316 [247] The four orchestrator strategies and their ids (ORC-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592315 [248] Every orchestrator routes an error result identically (DECIDED) (ERR-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592314 [249] Remove the direct-sync record-and-continue divergence (ERR-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592313 [250] Retry is in-place, immediate and opt-in (ERR-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592312 [251] A routed-failed node satisfies only its error edges (ERR-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592311 [252] A pipeline whose only failures were routed still completes (ERR-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592310 [253] An error result with no error edge fails the run (ERR-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592309 [254] An error result with an error edge routes instead of failing the run (ERR-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592308 [255] An unserializable output fails the node (ERR-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592307 [256] A stop request bypasses the error catch and stops the run cleanly (ERR-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592306 [257] An interrupt is re-thrown unchanged (ERR-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592305 [258] Any other exception fails the node and is re-thrown wrapped (ERR-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592304 [259] A retryable exception stays recognisable after it is caught (ERR-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592303 [260] A RuntimeException from a processor becomes an error result (ERR-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592302 [261] A node mapping carries both the processor and the node-type id (CMP-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592301 [262] A tool consumer must declare that it accepts tools (CMP-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592300 [263] Tool names must be unique per consumer at compile time (CMP-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592299 [264] Execution order is a topological sort (CMP-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592298 [265] A trigger dependency outranks a data dependency for ordering (CMP-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592297 [266] Which nodes are excluded from the execution graph (CMP-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592296 [267] Cycle detection ignores the edges that are meant to loop (CMP-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592295 [268] Edge type is derived from handles, never declared (CMP-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592294 [269] Compile preconditions run first, in a fixed order (CMP-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592293 [270] Re-enrichment on the run path is conditional (CMP-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592292 [271] What compiling a workflow produces (CMP-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592291 [272] One expression-error policy across every engine (DECIDED) (LANG-29) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592290 [273] The six operators the if/else gateway declares (LANG-28) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592289 [274] The switch gateway matches a branch value instead of evaluating it (LANG-27) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592288 [275] A prompt template turns a Twig error into a node failure (LANG-26) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592287 [276] DataShaper resolves its five sentinels before consulting an engine (LANG-25) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592286 [277] A NULL extraction is a soft miss, never an error (LANG-24) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592285 [278] DataExtractor unwraps a first match only for JSONPath (LANG-23) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592284 [279] DataExtractor re-wraps any evaluator throwable as a RuntimeException (LANG-22) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592283 [280] DataMapper re-wraps only a RuntimeException from an evaluator (LANG-21) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592282 [281] What exists() answers for an empty path and for a scalar (LANG-20) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592281 [282] Extracting all matches on a property path wraps the single result (LANG-19) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592280 [283] How a mapping value is marked as a literal instead of an expression (LANG-18) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592279 [284] Dot-to-bracket normalization is duplicated in three classes (LANG-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592278 [285] A string context is decoded as JSON when it is JSON (LANG-16) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592277 [286] A single JSONPath match is unwrapped unless the path is multi-value (LANG-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592276 [287] A path is JSONPath when it starts with $ (LANG-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592275 [288] Twig validation is compile-only (LANG-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592274 [289] JSONPath validation accepts anything that is not a $ path (LANG-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592273 [290] Property-path validation delegates to the same parser (LANG-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592272 [291] Expression Language validation accepts unknown variable names (LANG-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592271 [292] JSONPath never throws, and has three distinct outcomes (LANG-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592270 [293] A property path never throws; an unreadable path is NULL (LANG-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592269 [294] Twig renders a missing variable as an empty string (LANG-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592268 [295] Expression Language reports a syntax error, and a missing variable is one (LANG-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592267 [296] Expression validation has exactly one production call site (LANG-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592266 [297] A non-array context is wrapped for the template engines (LANG-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592265 [298] What an empty expression evaluates to, per engine (LANG-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592264 [299] Getting an evaluator never lets a plugin-manager failure escape (LANG-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592263 [300] Extraction engines query context; transformation engines see a variable map (LANG-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592262 [301] Refuse a synchronous launch of an async-declared workflow (MAN-19) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592261 [302] The manifest is rebuilt only when the declared ports change (MAN-18) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592260 [303] A declared output reads from its node's result (MAN-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592259 [304] Launch inputs are checked against the manifest snapshot (MAN-16 (G4)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592258 [305] Input checking short-circuits at the first failing stage (MAN-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592257 [306] A malformed manifest entry is dropped with a warning, even in strict mode (MAN-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592256 [307] Strict mode refuses an undeclared input by name (MAN-13 (G3)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592255 [308] Node-keyed pass-through is an internal contract (MAN-12 (G2)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592254 [309] A named input resolves to its node and port (MAN-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592253 [310] A declared manifest name wins over the node-keyed pass-through (MAN-10 (G1)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592252 [311] A workflow used as a node exposes its manifest, with a cycle guard (MAN-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592251 [312] An unresolvable manifest entry is dropped from the snapshot (MAN-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592250 [313] Which default values survive into the manifest snapshot (MAN-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592249 [314] Author metadata overlays the plugin annotations and wins (MAN-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592248 [315] A manifest snapshot is built from the plugin fragment and stripped (MAN-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592247 [316] The validator guards manifest integrity (MAN-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592246 [317] The authoring picker offers only ports that exist (MAN-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592245 [318] The shape of a manifest entry (MAN-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592244 [319] A workflow's input ports are a declared manifest, never derived (MAN-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592243 [320] The dynamic-port form appears only when the node type opts in (DYN-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592242 [321] Dynamic ports have no exposure semantics (DYN-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592241 [322] A static parameter name beats a dynamic one (DYN-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592240 [323] An unconnected dynamic port resolves to NULL, with its key present (DYN-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592239 [324] Reject an invalid or duplicate dynamic port name (DYN-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592238 [325] A dynamic port item needs a name, label and dataType (DYN-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592237 [326] A node type opts into dynamic ports by spreading their schema in (DYN-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592236 [327] Port order is cosmetic and the engine never reads it (EXPO-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592235 [328] The exposure checkbox seeds from the saved value (EXPO-16) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592234 [329] Which parameters a model may fill on a tool call (EXPO-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592233 [330] Stripping runs before the unified output port is composed (EXPO-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592232 [331] An output the node type hides is stripped unconditionally (EXPO-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592231 [332] Control outputs are never stripped (EXPO-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592230 [333] A hidden output's value is stripped where it is produced (EXPO-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592229 [334] A hidden input port receives no runtime value (EXPO-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592228 [335] The one-time exposure freeze writes only the hidden entries (EXPO-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592227 [336] A parameter added after install has no stored exposure until a re-save (EXPO-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592226 [337] Materialize an exposure entry only when it diverges from the default (EXPO-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592225 [338] The plugin's exposure hint is read at authoring time only (EXPO-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592224 [339] A schema hides a port by default only when it says so exactly (EXPO-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592223 [340] An untouched node stores no ports key, so the default always applies (EXPO-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592222 [341] How a port direction maps to its config key (EXPO-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592221 [342] An instance override decides exposure before any default does (EXPO-2 (D3)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592220 [343] PortExposure is the only PHP accessor for effective exposure (EXPO-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592219 [344] A config default is written only for a configurable parameter (CFG-18) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592218 [345] The unified input merge only fills connectable parameters (CFG-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592217 [346] The reserved input port is decomposed before the schema loop (CFG-16) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592216 [347] Every dynamic input is present in the resolved bag (CFG-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592215 [348] Every schema property is present in the bag, NULL when unresolved (CFG-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592214 [349] The resolved bag holds exactly the schema's keys plus dynamic ports (CFG-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592213 [350] Format validation covers nine formats and ignores the rest (CFG-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592212 [351] The type check is a closed match with no coercion (CFG-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592211 [352] A resolved value is validated against the plugin schema (CFG-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592210 [353] A required parameter that resolves to NULL fails the node (CFG-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592209 [354] Internal parameters accept a runtime value but never config (CFG-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592208 [355] Presence is key existence, so an explicit NULL wins over a lower priority (CFG-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592207 [356] Priority 3: fall back to the effective default (CFG-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592206 [357] Priority 2: take a config value when the parameter is configurable (CFG-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592205 [358] Priority 1: take a runtime value when the port can receive one (CFG-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592204 [359] An effective default is the entity's, then the plugin's, then NULL (CFG-3 (D4)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592203 [360] The exposure default fails open (CFG-2 (D2)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592202 [361] Gate flags fail closed (CFG-1 (D1)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592201 [362] Config fields are ordered by their declared order (SCH-31) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592200 [363] The run path re-enriches from the live node type (SCH-29) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592199 [364] The executor plugin id comes from the node type, never from the payload (SCH-28) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592198 [365] The wire shape is lean: emit a key only when it diverges from the default (SCH-27) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592197 [366] The editor catalog serves enabled node types, sorted (SCH-26) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592196 [367] Enrichment anchors on the node-type id alone (SCH-25) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592195 [368] Building node data logs and degrades instead of failing the editor (SCH-24) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592194 [369] The UI schema is generated from the final config schema (SCH-23) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592193 [370] Only a config-edit provider gets a configEdit block (SCH-22) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592192 [371] Every node gets a reserved instance title and description (SCH-21) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592191 [372] A node's visual type comes from the config entity only (SCH-20) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592190 [373] Both key enumerations skip trigger and hidden parameters (SCH-19) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592189 [374] Prepend the unified output port when the node exposes one (SCH-18) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592188 [375] Prepend the unified input port when the node exposes one (SCH-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592187 [376] The exposure defaults of the reserved ports (SCH-16) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592186 [377] An injected port declares its exposure default only when it diverges (SCH-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592185 [378] Inject the reserved error output on every executable node (SCH-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592184 [379] Inject the reserved tool output only on a tool-exposed node (SCH-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592183 [380] Inject the reserved trigger output on every node but a terminal node (SCH-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592182 [381] Inject the reserved trigger input on every node but a start node (SCH-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592181 [382] The schema-to-dataType map is closed (SCH-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592180 [383] A union type normalizes to its first non-null member (SCH-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592179 [384] One mapping turns a schema into ports (SCH-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592178 [385] An output reaches the editor only when the node type exposes it (SCH-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592177 [386] A parameter is required on the input side only when it is not configurable (SCH-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592176 [387] Reserved config-only parameters never become ports (SCH-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592175 [388] Hidden parameters are dropped from both derived schemas (SCH-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592174 [389] Deriving splits one parameter schema into an input schema and a config schema (SCH-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592173 [390] Schema derivation reads its gate flags from the plugin schema (SCH-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592172 [391] A node's input and output surface comes only from its two schema methods (SCH-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592171 [392] Transport edges and job-metadata edges each own their own key names (EDGE-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592170 [393] Edge conditions are a removed feature that is tolerated but never read (EDGE-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592169 [394] What makes a node tool-only (EDGE-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592168 [395] An edge is an error edge by its source handle (EDGE-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592167 [396] An edge is a tool edge by declared type, else by its target handle (EDGE-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592166 [397] An edge is a loopback edge when its target handle says so (EDGE-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592165 [398] An edge is a trigger edge when its target handle says so (EDGE-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592164 [399] No wire key is structurally required; an absent one becomes a missing endpoint (EDGE-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592163 [400] How a port handle encodes its node, direction and port name (EDGE-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592162 [401] Refuse a duplicate edge between the same two ports (R13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592161 [402] Refuse an edge from a node to itself (R12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592160 [403] Every configured expression must pass its engine's check at save (R11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592159 [404] A workflow exposure must target a port exposed on the node instance (R10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592158 [405] A node's node-type anchor must resolve to a node type that exists (R9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592157 [406] Edge ids must be present and unique at save (DECIDED) (R3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592156 [407] Node ids must be unique (DECIDED) (R2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592155 [408] The whole validator runs again at launch (VAL-LAUNCH) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592154 [409] The validator instantiates plugins only for the exposure checks (VAL-PERF) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592153 [410] Warn about an edge leaving a terminal node (W-T) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592152 [411] An exposure must name a port the plugin declares (R4.d) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592151 [412] An exposure must name a node that exists (R4.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592150 [413] Exposure names must be unique per side (R4.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592149 [414] An exposure name must match the allowed format (R4.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592148 [415] Skip the edge-exposure check where another rule already owns the problem (R7.e/f) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592147 [416] A port the node type never declared is out of the edge-exposure check (R7.d) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592146 [417] Effective exposure comes from the instance config, then the node-type default (R7.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592145 [418] Refuse an edge out of a hidden output port (R7.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592144 [419] Refuse an edge into a hidden input port (R7.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592143 [420] An edge missing both endpoints reports both errors (R8.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592142 [421] Refuse an edge whose target node does not exist (R8.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592141 [422] Refuse an edge whose source node does not exist (R8.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592140 [423] Retire validateParams() from the processor contract (R6.k) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592139 [424] Warn when a secret reference is written without its leading $ (R6.l) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592138 [425] An unresolvable node type skips only the schema-driven config checks (R6.j) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592137 [426] A NULL config value means unset and is never validated (R6.i) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592136 [427] Refuse a string that does not match its pattern (R6.h) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592135 [428] Refuse a string outside its length bounds (R6.g) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592134 [429] Refuse a number outside its minimum/maximum (R6.f) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592133 [430] Refuse a config value outside its enum (R6.e) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592132 [431] Refuse a config value of the wrong type (R6.d) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592131 [432] An unknown config key is a warning, not a refusal (R6.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592130 [433] Every required config key must be present (R6.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592129 [434] Refuse a node whose config is not an array (R6.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592128 [435] Report a missing plugin once, not once per port (R1.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592127 [436] A node with no resolvable node type is skipped by the plugin check (R1.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592126 [437] Refuse a node whose executor plugin does not exist (R1.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592125 [438] Refuse a node with no id, located by its position (R5.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592124 [439] Refuse a workflow with more than 1000 edges (R5.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592123 [440] Refuse a workflow with more than 500 nodes (R5.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592122 [441] Retire the node config-validate endpoint (API-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592121 [442] A session with no workflow is a 409, not a 500 (API-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592120 [443] The session-turn door checks its inputs exactly like the launch door (API-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592119 [444] Every JSON door decodes through the shared, bounded decoder (API-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592118 [445] One payload key per node-type concept (STORE-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592117 [446] A finished turn leaves the session completed, not idle (STORE-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592116 [447] Entity statuses are backed enums whose value is what crosses a boundary (STORE-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592115 [448] WorkflowDTO::fromArray() normalizes for the read path only (STORE-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592114 [449] Bundle import runs its gates in a fixed order and rolls back on refusal (STORE-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592113 [450] A workflow's schema version must be semver (STORE-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592112 [451] The stored config schema is strict about node metadata (STORE-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592111 [452] Saving slims transient canvas state out of the stored workflow (STORE-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592110 [453] A validation failure at the REST boundary is a 422 and never reaches save (STORE-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592109 [454] Absent collections default to empty on create; a partial update preserves them (STORE-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592108 [455] A client-supplied id that already exists is a conflict, never an overwrite (STORE-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592107 [456] A workflow name is required and capped at 255 bytes (STORE-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592106 [457] Branch gateways and which edges activate (RT-BR) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592104 [458] Delivering values between nodes (RT-DATA) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592103 [459] Compiling a workflow into an execution plan (RT-CMP) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592102 [460] The pipeline status the editor polls (RT-PIPE) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592101 [461] Choosing and running an orchestrator (RT-ORC) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592100 [462] The StateGraph runner (RT-SG) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592099 [463] Interrupts, pausing and resuming (RT-INT) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592098 [464] How a failing node is handled (RT-ERR) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592097 [465] The JSON API doors (GR-API) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592096 [466] Storing and serving a workflow definition (GR-STORE) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592095 [467] Author-defined dynamic ports (GR-DYN) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592094 [468] A workflow's declared inputs and outputs (GR-MAN) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592093 [469] Resolving a node's parameters (GR-CFG) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592092 [470] Turning a plugin schema into ports and forms (GR-SCHEMA) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592091 [471] The four expression engines (GR-LANG) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592090 [472] Port exposure (GR-EXPO) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592089 [473] How edges connect ports (GR-EDGE) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592088 [474] What the workflow validator refuses (GR-VAL) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592087 [475] Return 400 for a malformed API request body (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592086 [476] Write down and test every runtime and workflow-language rule (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592085 [477] Remove unused API and developer surfaces from 2.x (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592084 [478] Report pipeline and job status consistently to the editor (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592083 [479] Make error routing, cancellation and resume behave the same in every runner (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592082 [480] Catch broken workflows when they are saved, not when they run (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592081 [481] Expression errors fail the node and route to its error edge (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592080 [482] [meta] Make the 2.x runtime and workflow-language contracts explicit and tested (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592079 [483] Refuse an empty, oversized, malformed or too-deeply-nested request body (STORE-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592105 [484] AI Assistant is broken from 1.5.0 (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592073 [485] Add "Show Pipelines" to the operations per workflow (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3589740 [486] Remove "Pending" tag when the workflow is executing and the component has been skipped (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3589739 [487] Add config for max characters (agui, Issue) — https://git.drupalcode.org/project/agui/-/work_items/3585465 [488] Better Error Handling in chat (agui, Issue) — https://git.drupalcode.org/project/agui/-/work_items/3590046 [489] Allow Token support on Assistant Controller (agui, Issue) — https://git.drupalcode.org/project/agui/-/work_items/3589993 [490] Enable Drupal GitLab CI pipeline and add Unit/Kernel/Functional test coverage (agui, Issue) — https://git.drupalcode.org/project/agui/-/work_items/3590044 [491] Add validator and extractor services/methods and new setting. (agui, MR) — https://git.drupalcode.org/project/agui/-/merge_requests/40 [492] Add error util and handler. (agui, MR) — https://git.drupalcode.org/project/agui/-/merge_requests/39 [493] Resolve "Allow Token support on Assistant Controller" (agui, MR) — https://git.drupalcode.org/project/agui/-/merge_requests/38 [494] Resolve "Enable Drupal GitLab CI pipeline and add Unit/Kernel/Functional test coverage" (agui, MR) — https://git.drupalcode.org/project/agui/-/merge_requests/34 --- MODULE SUMMARIES ---
AI (Artificial Intelligence)

The AI module saw focused progress on field-level automation and streaming chat capabilities over the past 24 hours. Work was completed to enable AI-powered workflows directly within content editing interfaces, allowing editors to trigger automated text generation without leaving the page. This capability connects Field Widget Actions with the module's multi-step Automator Chain feature, supporting more complex editorial workflows that previously required multiple separate fields or manual steps.

Two separate merges integrated this Field Widget Action support into different release branches, ensuring the feature will be available across supported versions. The work addresses practical limits on how much context AI models can process in a single request, enabling multi-turn workflows that break complex tasks into manageable steps.

Several bugs affecting the editor experience were identified and are under review. Issues were reported with the markdown-based prompt editor failing to parse Drupal tokens and colons—both common in real-world prompts. A fix is in progress for a streaming chat bug that corrupts URLs when AI-generated content includes links. Another bug preventing assistants backed by agents from streaming responses was identified and closed as a duplicate of an existing issue.

Planning and architectural work continued on permissions for the platform configuration system, chat memory persistence, and adoption of the latest Symfony AI component. Three new agent skills were proposed to enable command-line configuration of automators, guardrails, and general AI settings—part of a broader effort to make the module more scriptable and agent-friendly.

How can I help on this project?

Prioritize user experience review of the markdown editor issues affecting prompt authoring, as these directly impact day-to-day usability for content teams configuring AI workflows.

Clarify strategic direction on permissions and multi-tenancy for the new platform configuration, helping the team finalize architecture decisions that will shape governance and delegation capabilities.

Contributors: Ahmad Khalil (ahmad-khalil-imagex) [1], Ann Mary Sruthy (annmarysruthy), Artem Dmitriiev (a.dmitriiev), Bruno Bruno (bbruno), Dezső Biczó (mxr576), Isaac Trogdon (dotist), Marcus Johansson (Marcus_Johansson), Prabhavathi Vanipenta (prabha1997), Rob Loach (robloach), Rodel Duterte (rduterte), Wolfgang Ziegler (fago)
---
Drupal AI Initiative

Activity this period centered on partnership expansion and process improvements. Two new partners are being onboarded: Pantheon (Gold tier) and Specbee (Silver tier). The Pantheon onboarding was completed, including integration into communication channels and team workflows. Work on Specbee's onboarding continued, with follow-up tasks to add them to the partner directory and run an audit to confirm successful integration.

To support future growth, templates for partner onboarding and audit processes were closed as complete, standardizing how new organizations join the initiative. A request was opened to update partner badges to use "Partner" instead of "Sponsor" language, better reflecting the collaborative nature of these relationships. Work also began on refreshing the partner logo wall and conducting periodic audits of contributor access to ensure alignment with active participation.

A new capability was proposed to create repeatable manual testing processes for issue review, aiming to improve consistency and provide documented evidence of before-and-after behavior without requiring reviewers to rebuild environments.

How can I help on this project?

Approve the partner badge redesign request to ensure brand consistency as the partnership program scales.

Allocate resources to formalize the testing documentation approach if early feedback indicates it reduces review friction.

---
AI Integration - ECA

This module enables natural-language interaction with Drupal's Event-Condition-Action (ECA) automation system, allowing users to create and manage automation workflows through conversational AI rather than manual configuration.

Work has begun on modernising the module's underlying architecture. A migration to the Tools + ReAct architecture was opened this period. This effort will replace the current custom control flow with a more maintainable, standardised approach that leverages the broader AI Integration framework. The change is expected to improve reliability and make future enhancements easier to deliver. The work is part of the roadmap toward a stable 1.0.0 release.

No merge activity or commits occurred during this period. Development continues in the open merge request.

How can I help on this project?

Review and approve the architectural direction for the Tools + ReAct migration to accelerate progress toward 1.0.0.

Allocate testing resources to validate the new architecture once the merge request is ready for review.

Contributors: Marcus Johansson (Marcus_Johansson)
---
OpenAI Provider

The OpenAI Provider module made steady progress over the past 24 hours, with three updates merged that improve performance and reliability for users integrating OpenAI services into their Drupal sites.

Support for batch embeddings was added, enabling more efficient processing of multiple text inputs at once. This reduces the number of API calls needed and improves system performance when generating embeddings at scale.

A fix for rate limits was merged, helping the module handle OpenAI's usage restrictions more gracefully. This should reduce service interruptions and provide more predictable behavior during high-volume operations.

A bug affecting GPT functionality was also resolved, restoring expected behavior for users working with GPT-based features.

Together, these updates strengthen the module's stability and efficiency for organizations deploying AI-powered content and automation workflows.

How can I help on this project?

Ensure the team has adequate OpenAI API credits and budget for testing across different usage patterns and rate limit scenarios.

Connect the development team with end users to gather feedback on performance improvements and identify remaining pain points.

Contributors: Marcus Johansson (Marcus_Johansson) [1], Paul Sheldrake (paulsheldrake) [1] ---
amazee.ai Private AI Provider

The module made progress on instrumentation and is addressing a critical data integrity issue. A new merge request was opened to add tracking headers to API requests, enabling better visibility into which module versions are generating traffic to the amazee.ai service. This will support troubleshooting and usage analytics.

A significant data loss issue was identified and is now awaiting final review: Deleting or clearing items in a Search API index deletes data from other indexes sharing the same Vector DB collection. The issue occurs when multiple search indexes share the same underlying database collection. Clearing or updating one index can inadvertently delete records from others, resulting in silent and permanent data loss. This affects any deployment using shared vector database collections and has been assigned for resolution.

How can I help on this project?

Prioritize review and approval of the data loss fix to prevent further incidents in production environments.

Ensure adequate testing resources are available to validate the fix across different deployment configurations before release.

Contributors: Dan Lemon (dan2k3k4)
---
Microsoft Azure AI

A significant refactor of the Azure provider infrastructure was opened during this period. The [#3552969] feat: Refactor AzureProvider to use OpenAiBasedProviderClientBase merge request represents work to restructure how the module connects to Azure's AI services. This change is designed to improve code reusability and maintainability by building on a shared foundation with other OpenAI-compatible providers. For users, this means more consistent behavior across different AI service integrations and easier future enhancements. The refactor is substantial, touching 680 lines of code, and signals progress toward a more mature and scalable architecture.

No issues were updated during this period, and the refactor remains open for review. This is normal development activity for a module in active evolution.

How can I help on this project?

Ensure the team has dedicated time allocated for code review of the open refactor, as architectural changes require careful evaluation before integration.

Consider whether user acceptance testing resources are available once the refactor merges to validate that Azure AI integrations continue working as expected.

Contributors: Jukka Huhta (jhuhta)
---
Postgres VDB Provider

A new merge request was opened to address an issue where certain data columns are lost after clearing and reindexing operations. This work aims to preserve important data structure throughout the reindex process, ensuring that information is not inadvertently dropped when the system refreshes its indices. If merged, this fix will improve data consistency and reduce the risk of information loss during routine maintenance operations.

No issues were updated and no code was committed to the main repository during this period. The module is continuing its development with focused attention on data integrity concerns.

How can I help on this project?

Arrange code review resources to evaluate the pending merge request, which addresses a data integrity concern.

Clarify release timeline expectations and prioritization for this module within the broader AI initiative.

Contributors: Ignacio Pérez Puertas (djnash2002) ---
Model Context Protocol

The Model Context Protocol module saw continued work during this period on authentication functionality. A Token Auth is not working issue remains open, with an associated merge request under review. The issue addresses problems preventing administrators from enabling token-based authentication through the configuration interface, which currently requires manual configuration workarounds. Resolving this will allow site administrators to enable secure authentication options through the standard interface, improving both usability and security setup for the module.

No merge requests were merged or commits pushed during this 24-hour window, indicating planning and review activities are underway rather than active code integration.

How can I help on this project?

Allocate review capacity to evaluate the open authentication merge request, enabling faster integration of completed work.

Clarify the module's target release timeline (alpha, beta, or stable) to help the team prioritize stabilization versus new features.

Contributors: Alin Ameiroaie (aalin)
---
AI Agents

Development activity this period centered on refining agent configuration and addressing operational issues. Work was completed to allow users to set custom provider tags when running agents, making it easier to track and filter specific interactions in the event log. This capability was marked complete and closed.

Several configuration enhancements are in progress. Work continues on allowing individual agents to use specific language model providers rather than a shared default, giving administrators more control over cost and performance tradeoffs. A related feature to let parent agents forward requests directly to subagents without reprocessing is under development, aimed at improving response consistency and reducing latency.

Multiple bug fixes are being addressed through open merge requests, including issues where the chatbot interface handles search queries differently than the tool explorer, and where conversation history persists unexpectedly after clearing. Work is also underway on implementing limits to prevent tools from running too frequently, and on integrating short-term memory capabilities into agents.

The module continues in active development with normal issue activity for a pre-stable release. No critical blockers were identified this period.

How can I help on this project?

Review open merge requests to help validate whether bug fixes resolve the reported issues, particularly around chatbot behavior consistency.

Provide guidance on prioritization between new configuration features and stability improvements as the module approaches a production-ready release.

Contributors: Bharat Kelotra (bharatkelotra), Marcus Johansson (Marcus_Johansson)
---
Tool API

The Tool API project made significant progress toward its first release candidate, with five key integration issues resolved and compatibility with Drupal 10.5 through 11 now tested in continuous integration. The focus this period was on ensuring the module's data schemas work reliably across different AI platforms and fixing issues where execution failures were not clearly reported to users or AI models.

The project resolved problems that prevented tools from working with Anthropic AI models and fixed issues where entity descriptions containing common punctuation appeared garbled to AI systems. A fix was merged for the REST serialization conflict that broke other modules' JSON output when Tool API was enabled. Additional work corrected how the AI connector handles tools that fail before execution, ensuring callers receive meaningful error messages instead of technical exceptions.

The project opened a comprehensive tracking issue outlining the path to release candidate 1, identifying 18 items that must be addressed before the programming interface can be frozen. These include fixing broken configuration-sourced inputs, correcting validation logic that skips items in multi-value fields, and resolving access-check failures. Several issues are tagged as quick wins requiring only a few lines of code but representing breaking changes if deferred beyond the release candidate freeze.

Strategic planning work began tracking alignment with Drupal core's emerging CLI initiative, positioning the module's metadata model as a candidate for adoption in core and identifying opportunities for advocacy as core considers structured outputs for command-line tools.

How can I help on this project?

Prioritise resourcing for the 18 pre-RC1 items to meet the interface freeze deadline. Facilitate a decision on the API surface annotation strategy to clarify which components are stable versus internal. Consider sponsoring documentation work for the stable release security review.

Contributors: Abhisek Mazumdar (abhisekmazumdar) [1], Bryan Sharpe (b_sharpe) [1], Michael Lander (michaellander) [11]
---
Drupal Canvas

The past 24 hours saw three fixes merged to production and continued advancement across AI tooling, translation workflows, and developer experience.

Two command-line interface issues were resolved. A fix for content template push errors was merged, enabling the CLI to correctly create templates without triggering server-side validation failures. A fix for global region synchronization resolved failures when pushing media images and links, ensuring these props are now handled correctly during sync operations.

A major developer experience improvement was also merged: an automated code quality check that enforces safer, more maintainable service references across the codebase. This change reduces ambiguity and makes code easier to navigate.

Active development continues on AI chat capabilities, including a tools dropdown for the chat interface and an admin settings form to configure available agents and tools. The placement tool schema was improved to give AI agents clearer, more structured instructions when positioning components.

Work is also progressing on translation support for older component versions, right-to-left language layout, autosave reliability, and broader entity type support for content templates.

How can I help on this project?

Prioritize backend review capacity for the translation fix and RTL support work to ensure multilingual readiness.

Clarify product direction on AI agent selection: confirm whether the admin-controlled tools approach aligns with rollout plans.

Contributors: **** (project_19391_bot_17a61b0edeafd5a3db3e8b2462b6c010), **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Adam G-H (phenaproxima), Ben Mullins (bnjmnm), Bálint Kléri (balintbrews) [1], Canvas version bot [2], David Bravo (davidbp), Harumi Jang (hooroomoo), Jeremy Chinquist (jjchinquist), Juan Correa (jucs7) [1], Kunal Sachdev (kunal.sachdev), Lionel Enkaoua (heyyo), mariosr, Rajab Natshah (RajabNatshah), Tekla Aivazashvili (aivazashvilit), Wim Leers (wimleers) [1], wotnak [1]
---
Context Control Center (CCC)

Development this period focused on preparing the module for its first release candidate and stable version. Work advanced on several stability and compatibility issues that are critical for production readiness.

A dedicated editorial workflow for context items is being created to replace reliance on shared workflows, giving the module clearer publishing states and preventing unintended side effects on other content. Progress continued on fixing upgrade problems for sites moving from beta2 to current versions, particularly around entity bundle changes. A separate effort is addressing Drupal 10 compatibility issues and incomplete beta3 upgrades to ensure the module works reliably across supported platform versions.

Performance improvements are underway to avoid loading the entire published catalog when displaying the overview page. The scope plugin architecture is being completed to provide a consistent persistence and selection interface, which will make future extensions easier to build. A rename of scope plugins is in progress to improve clarity for editors choosing which entities receive context.

Planning discussions opened on context ranking factors and priority levels, exploring how the module should decide which guidance reaches AI features when limits apply. A quality assurance plan is being developed to systematically test functionality before the stable release.

How can I help on this project?

Ensure the quality assurance team has sufficient time allocated to complete systematic testing and develop the QA plan before stable release.

Confirm product direction on the context ranking and priority discussions to unblock design decisions needed before version 1.0.

Contributors: Kristen Pol (kepol), Levente Besenyei (LeventeB), Pravesh Poonia (Pravesh_Poonia), Reinhold Schachner (reinimax), Tamas Balog (tbalog)
---
AI CKEditor

A new merge request was opened to improve user feedback during content generation. Currently, when users click the Generate button inside the editor, they must scroll down to see whether their request is being processed. The proposed change will display a status indicator directly next to the Generate button, giving users immediate visual confirmation that their request is in progress without requiring them to navigate within the modal window.

This enhancement addresses a usability gap in the AI Writer feature and should reduce confusion for users waiting for generated content to appear. The change is relatively small in scope and awaits review before being integrated into the module.

How can I help on this project?

Ensure the team has capacity to review and merge the pending user experience improvement.

If broader user testing or feedback on the AI Writer workflow is planned, allocate time or resources to conduct it.

Contributors: Ricardo Castañeda (cadence96) ---
AI Search

The AI Search module saw focused development activity around improving how search results are checked for access and how structured data is returned to applications using the module's RAG (retrieval-augmented generation) capabilities.

A key gap was identified and addressed: the RAG tool was previously only returning a single text string to language models, discarding important metadata like which content each result came from, relevance scores, and individual text chunks. Work on RagTool::execute() should expose structured per-result data and check entity access aims to preserve this information so applications can show users which sources were consulted, not just the AI-generated answer.

Parallel efforts are improving access control. The module historically only supported permission checks for standard content, blocking use with other data types. New work is underway to defer access checking to Search API datasource plugins and to introduce a dedicated runtime access-checking API that lets organizations enforce stricter filters—for example, preventing sensitive data from being sent to external AI services even when a user technically has permission to view it on the website.

How can I help on this project?

Prioritize testing and review resources for the open access-control work, which affects data security and compliance.

Clarify business requirements for sensitive-data filtering to guide the new runtime access API design.

Contributors: Abhisek Mazumdar (abhisekmazumdar), David Bondor (superbondor), Dezső Biczó (mxr576)
---
AI translate

The AI translate module saw foundational work over the past 24 hours focused on project infrastructure and knowledge sharing. Two key issues were advanced to ensure the module can be effectively maintained and adopted.

A documentation initiative is underway to create user-facing guidance for the module, which currently has none. A draft merge request has been opened with substantial content to address this gap. Clear documentation will be essential for teams evaluating or implementing automated translation capabilities.

Separately, work began on Fix Pipeline to restore automated quality checks that are currently non-functional. A proposed solution has been submitted for review. Restoring these checks will help maintain code quality as development continues.

Both issues remain open with draft or pending solutions. No code was merged during this period, but the preparatory work positions the project to improve both developer experience and end-user accessibility.

How can I help on this project?

Allocate reviewer time to assess and merge the pending documentation and pipeline fixes, enabling faster iteration.

Clarify the target release timeline and stability goals to help prioritize outstanding work appropriately.

Contributors: Marcus Johansson (Marcus_Johansson), Rob Loach (robloach)
---
FlowDrop

FlowDrop has completed a major consolidation of its runtime and workflow-language contracts, closing 316 specification-related issues over the reporting period. This work establishes a formal, tested foundation for how workflows are validated, executed, and reported across all execution strategies.

Strategic Progress

The project has delivered a comprehensive specification registry covering ten domains: workflow storage and API boundaries, schema and port discovery, parameter resolution, exposure semantics, edge classification, expression engines, validation rules, orchestrator behaviour, error handling, data delivery, branching, compilation, interrupts, state management, and status reporting. Each of 247 runtime rules now cites its implementation and binding test, with automated coverage enforcement preventing drift. This positions FlowDrop to onboard contributors and evolve the platform with confidence that changes will not silently break downstream behaviour.

Key user-facing improvements include unified error routing (all four runners now handle error edges identically), consistent status reporting to the editor (node badges now reflect the correct execution state even for loops), and comprehensive save-time validation (broken workflows are refused when authored, not discovered at runtime). Expression errors now fail the node and route to its error edge across all four processors, providing authors a predictable recovery path.

Deliverables

The specification registry documents 247 rules across runtime execution, workflow grammar, and API contracts. All testable rules are covered by binding tests, with 11 structural or cross-reference entries completing the set. A companion issue cleaned legacy surfaces (unused endpoints, deprecated methods, and misleading metrics) from the 2.x branch. Validation now refuses 13 structural defects at save time, including missing plugins, hidden-port wiring, duplicate edges, self-edges, malformed expressions, and oversized payloads. Error handling, cancellation, and resume behaviour now behave identically across all runners, and status payloads have been standardised for editor consumption.

Risks

No blocking issues for a stable release were introduced during this period. The work closed long-standing inconsistencies and undocumented behaviour, reducing the surface area for runtime surprises. Future changes to validated behaviour will be visible in the specification registry, making impact assessment straightforward.

How can I help on this project?

Advocate the specification registry approach to other Drupal projects managing complex runtime behaviour, positioning FlowDrop's documentation model as a reference.

Coordinate a stable 2.x release now that the runtime contracts are explicit and tested, unlocking production adoption.

---
AG-UI

The AG-UI module saw significant progress in security, quality assurance, and user experience over the past 24 hours, with four key pieces of work delivered.

A new character limit configuration was merged to help prevent token exhaustion attacks. Site administrators can now set maximum message lengths; users who exceed the limit will receive a clear message and their requests will be blocked before reaching the AI service. This adds a layer of cost control and abuse prevention.

Error handling in the chat interface was improved so that when something goes wrong, users now see friendly, concise error messages instead of raw technical output cluttering the conversation.

The module now supports token-based authentication for anonymous users, allowing public-facing AI assistants to be deployed while reducing the risk of abuse from automated scripts.

Finally, automated testing and continuous integration were enabled, establishing a quality gate for all future changes. The pipeline now runs coding standards checks, static analysis, and automated tests on every contribution.

How can I help on this project?

Prioritise a decision on release timeline and readiness criteria for a stable 1.0 version to guide remaining feature and documentation work.

Consider allocating design or UX resources to review the chat interface and error messaging for accessibility and usability.

Contributors: Ahmad Khalil (ahmad-khalil-imagex) [1], Bryan Sharpe (b_sharpe) [3]
======================================================================== ## [23] factcheck:tldr:executive ======================================================================== Layer-1 corrections: 0 Judge flags: 5 ======================================================================== ## [24] generate2026Capabilities ======================================================================== You are an editor writing a strategic section for a non-technical executive audience. The Drupal AI initiative has 8 planned capabilities for 2026. Your task is to read the module activity summaries below and explain how today's progress moves each capability forward — or note where there was no relevant progress today. Be concise and direct. Focus on what matters to a business leader: is progress happening, what is the next milestone, and are there any risks? When you describe progress on a capability, add inline citations using [N] where N is the reference number from the list below. You may cite multiple references per item, e.g. [1][3]. Place citations at the end of the relevant sentence, before the closing punctuation. Output an HTML fragment using exactly this structure:
2026 Capabilities Progress

Capability name — One or two sentences on how today's activity relates to this goal, or "No direct progress today" if nothing relevant occurred.

Use only the 8 capabilities listed below, in the same order. Do not add, remove, or rename them. Do not output any text outside the
and
tags. --- 2026 CAPABILITIES --- 1. Page generation — Describe what you need and get a usable page, built from your actual design system components 2. Context management — A central place to define brand voice, style guides, audience profiles, and governance rules that AI can use 3. Background agents — AI that works without being prompted, responding to triggers and schedules while respecting editorial workflows 4. Design system integration — AI that builds with your components and can propose new ones when needed 5. Content creation and discovery — Smarter search, AI-powered optimization, and content drafting assistance 6. Advanced governance — Batch approvals, branch-based versioning, and comprehensive audit trails for AI changes 7. Intelligent website improvements — AI that learns from performance data, proposes concrete changes, and gets smarter over time through editorial review 8. Multi-channel campaigns — Create content for websites, social, email, and automation platforms from a single campaign goal --- REFERENCE LIST --- [1] MDXEditor fails to parse Drupal tokens in AI Agents prompts (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586613 [2] MDXEditor throws error when prompt includes a colon (:) character (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586619 [3] Decide permission system for new AI Platform and AI Inference Providers (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586628 [4] Support Automator Chain trigger with Field Widget Actions (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586602 [5] What providers for TextClassification? (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586629 [6] The Toolbar Chatbot runs the fold out animation on page reload (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3568246 [7] Support interactive/rich content (e.g. links) in the AI tooltip component (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586630 [8] Streaming chat forces plain-text hostname filtering, corrupting URLs inside HTML attributes (e.g., href="") (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586624 [9] Adopt symfony/ai component v0.8 as platform provider (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586427 [10] AI Automator Token Replacement with removing unresolved Tokens (Checkbox?) (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586535 [11] Add a ChatMemoryInterface for storing ChatBot chat history (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586539 [12] [1.x] Add a setup-automators agent skill to configure automators on fields (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586563 [13] Add a configure-ai-settings agent skill for general AI settings (default models, providers, timeout, trusted domains) (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586562 [14] Add a setup-guardrails agent skill to configure guardrails, guardrail sets, and global guardrails (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586561 [15] Streamed chatbot agent response (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3578168 [16] Assistants backed by an agent never stream (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586627 [17] Refactor CommonMark instance creation (ai, Issue) — https://git.drupalcode.org/project/ai/-/work_items/3586608 [18] Issue #3586602: Add a field widget action base class and text plugin to run... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1887 [19] Issue #3586602: Add a field widget action base class and text plugin to run... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1888 [20] Issue #3586602: Add a field widget action base class and text plugin to run... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1886 [21] Issue #3586602: Add a field widget action base class and text plugin to run... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1828 [22] feat: #3586585 Add YAML support to the MDX editor code blocks (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1823 [23] #3568246: fix late chatbot opening on page load (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1428 [24] feat: #3586427 Adopt symfony/ai v0.8's Platform concept (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1619 [25] Add CommonMarkConverterFactory service. (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1881 [26] Issue #3586535: AI Automators strip unresolved tokens from prompts (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1884 [27] Issue #3586589: Add ChatMemory plugin type (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1885 [28] fix: #3586589 Do not assume action definitions have a type when deriving action plugin functions (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1835 [29] bug: #3586624 Streaming chat forces plain-text hostname filtering, corrupting... (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1883 [30] Resolve #3586627: Assistants backed by an agent never stream (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1882 [31] "1.x backport" (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1321 [32] Issue #3586620 Merge 1.3.x guardrails (ai, MR) — https://git.drupalcode.org/project/ai/-/merge_requests/1880 [33] Create a skill for manual before/after testing of any issue, with optional glab upload (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586629 [34] Onboard Silver AI partner: Specbee (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586639 [35] Add Silver AI partner to d.o pages: Specbee (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586638 [36] Run AI partner audit report: Specbee (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586637 [37] Onboard Gold/Silver AI partner: TEMPLATE (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3579583 [38] Add Gold/Silver AI partner to d.o pages: TEMPLATE (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3579591 [39] Run AI partner audit report: TEMPLATE (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3579584 [40] Update AI partner badges to use Partner instead of Sponsor (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586636 [41] Add Gold AI partner to d.o pages: Pantheon+Omedia (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586631 [42] Onboard Gold AI partner: Pantheon+Omedia (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586630 [43] Partner contributor audit and cleanup August 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586634 [44] Update AI partner logo wall with latest logos July 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586635 [45] Update AI partner logo wall with latest logos March 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3580150 [46] Partner and contributor offboarding for July 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586633 [47] Partner and contributor offboarding for June 2026 (ai_initiative, Issue) — https://git.drupalcode.org/project/ai_initiative/-/work_items/3586553 [48] Migrate the ECA agent to the Tools + ReAct architecture (create-only) (ai_integration_eca, Issue) — https://git.drupalcode.org/project/ai_integration_eca/-/work_items/3585017 [49] Resolve "Migrate the ECA agent to the Tools + ReAct architecture (create-only)" (ai_integration_eca, MR) — https://git.drupalcode.org/project/ai_integration_eca/-/merge_requests/14 [50] add support for batch embeddings (ai_provider_openai, MR) — https://git.drupalcode.org/project/ai_provider_openai/-/merge_requests/59 [51] Resolve #3612042 "Rate limits" (ai_provider_openai, MR) — https://git.drupalcode.org/project/ai_provider_openai/-/merge_requests/80 [52] Resolve #3613982 "Bug with gpt" (ai_provider_openai, MR) — https://git.drupalcode.org/project/ai_provider_openai/-/merge_requests/81 [53] Data loss: Deleting or clearing items in a Search API index deletes data from other indexes sharing the same Vector DB collection (ai_provider_amazeeio, Issue) — https://git.drupalcode.org/project/ai_provider_amazeeio/-/work_items/3586238 [54] feat: send X-Amazee-Client request tracking header (ai_provider_amazeeio, MR) — https://git.drupalcode.org/project/ai_provider_amazeeio/-/merge_requests/81 [55] [#3552969] feat: Refactor AzureProvider to use OpenAiBasedProviderClientBase (ai_provider_azure, MR) — https://git.drupalcode.org/project/ai_provider_azure/-/merge_requests/22 [56] Issue #3586862 by ignacio.perez.puertas: Re-apply Attributes columns after clear+reindex cycle (ai_vdb_provider_postgres, MR) — https://git.drupalcode.org/project/ai_vdb_provider_postgres/-/merge_requests/24 [57] Token Auth is not working (mcp, Issue) — https://git.drupalcode.org/project/mcp/-/work_items/3584901 [58] Resolve "Token Auth is not working" (mcp, MR) — https://git.drupalcode.org/project/mcp/-/merge_requests/52 [59] Add a way to set provider tags in the runner (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3557418 [60] Let an agent use a role when running a tool (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3518167 [61] Add limits on how often a tool can run (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3547995 [62] Give a parent agent possibility to forward request as is (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3550098 [63] Make it possible to pick providers per agent (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3535760 [64] Chatbot truncates 'search_string' context value while tool explorer does not (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3547304 [65] Chatbot repeats itself even after 'clear history' if 'return direct' (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3547225 [66] Create implementation of ShortTermMemory (ai_agents, Issue) — https://git.drupalcode.org/project/ai_agents/-/work_items/3546411 [67] Draft: Resolve "Give a parent agent possibility to forward request as is" (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/326 [68] Issue#3547304:chatbot-truncates-search-string-context-value-while-tool-explorer-does-not fixes (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/327 [69] Issue #3535760: Provider picker (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/315 [70] Issue#3547225-chatbot-repeats-itself-even-after-clear-history-if-return-direct fixes (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/325 [71] Issue#3541337-module-agent-fails fixes. (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/324 [72] Issue#3539557:error-message-when-using-the-ai-assistant-to-add-a-content-type fixes (ai_agents, MR) — https://git.drupalcode.org/project/ai_agents/-/merge_requests/323 [73] Configuration-sourced input values fatal: getConfigurationValue() semantics are inverted (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582959 [74] validateInputValue() only validates the first item of a multiple input (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582960 [75] ToolBase::access() throws on invalid/missing input instead of returning forbidden (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582961 [76] Correct API signatures before the RC1 freeze (batch) (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582962 [77] Prefix module-owned identifiers: alter hook, cache key, and 'text' data type ID (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582963 [78] Rework the tool execution contract: result naming, concrete typing, and decoupling from core ExecutableInterface (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582964 [79] Implement getCacheContexts() or drop CacheableDependencyInterface from ToolInterface (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582965 [80] Annotate the API surface (@api/@internal) and add tool.api.php (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582966 [81] Harden the 'administer tool' permission (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582967 [82] Tool Explorer execute form: masked exception on access denial, duplicate messages, no validation pass (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582968 [83] Tool Explorer RC cleanup: render arrays, dead cache tag, menu placement, first tests (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582969 [84] Drush hardening: --uid default, silently dropped inputs, exit codes (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582970 [85] Make violation messages translatable and stop surfacing raw exception text (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582971 [86] Emit richer JSON Schema: map remaining constraints and type formats (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582972 [87] Extend input coercion for unambiguous LLM value shapes (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582973 [88] Complete kernel coverage of the typed input/output traits and definition pipeline (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582974 [89] checkRequirements() is declared on the frozen interface but never called anywhere (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582975 [90] Filter workflow-only tools from one-shot CLI invokers (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582977 [91] Track Drupal core CLI alignment: metadata mapping, typed-outputs advocacy, future CLI invoker (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582976 [92] [META] Path to 1.0.0-rc1 (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582978 [93] Entity handle descriptions are HTML-escaped in LLM-facing schemas (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582958 [94] A tool whose input stage fails never executes, and external getResult() calls then throw BadMethodCallException, masking the error feedback (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582957 [95] Anthropic rejects tool schemas: nullable optional inputs render an object under "type" (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582956 [96] tool_ai_connector throws `BadMethodCallException` when the tool has not executed (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582948 [97] [AI Connector] - Context Data missing after execute (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3576586 [98] MapDefinitionNormalizer and ContextDefinitionNormalizer break REST serialization (same as #3568588) (tool, Issue) — https://git.drupalcode.org/project/tool/-/work_items/3582939 [99] Issue #3582959 by michaellander: Configuration-sourced input values fatal:... (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/111 [100] Resolve "Entity handle descriptions are HTML-escaped in LLM-facing schemas" (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/110 [101] Resolve "A tool whose input stage fails never executes, and external getResult() calls then throw BadMethodCallException, masking the error feedback" (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/109 [102] Resolve "Anthropic rejects tool schemas: nullable optional inputs render an object under "type"" (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/108 [103] Resolve "tool_ai_connector throws `BadMethodCallException` when the tool has not executed" (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/107 [104] Issue #3576586 by b_sharpe: Set parent context data as well as input. (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/76 [105] Issue #3582939: Fix getSupportedTypes() in MapDefinitionNormalizer and... (tool, MR) — https://git.drupalcode.org/project/tool/-/merge_requests/95 [106] RTL support for Canvas visual editor (logical CSS properties, Radix DirectionProvider, autocomplete magnifier, and Undo/Redo timelines) (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591840 [107] Translatable props missing from TMGMT form when component instances cannot be auto-updated to active version (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591875 [108] Strengthen AutoSaveManager to generate stable hashes (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591785 [109] Dependency Dashboard (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591657 [110] CLI push includes unsupported label property for content templates (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591899 [111] Automatically create components when themes are installed (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591898 [112] Canvas CLI sync fails for media and link props in global regions (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591897 [113] Error message for empty value is displayed for select props even when they're not required (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591894 [114] Canvas AI: Add Tools dropdown to chat UI (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591856 [115] Automate MR review using PHPCS: disallow `\Drupal::service('something')`, require `\Drupal::service(Something::class)` whenever possible, with automatic fixing (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3581133 [116] Canvas AI: Improve the schema of the place_components tool (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591881 [117] Canvas AI: Add an Agents & Tools settings form to select the main agent and chat Tools (canvas, Issue) — https://git.drupalcode.org/project/canvas/-/work_items/3591882 [118] Draft: fix: #3591840 RTL support for Canvas visual editor (logical CSS properties, Radix DirectionProvider, autocomplete magnifier, and Undo/Redo timelines) (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1453 [119] #3591875: "Translatable props missing from TMGMT form when component instances cannot be auto-updated to active version" (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1418 [120] chore(deps): update dependency cspell to v10 (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1273 [121] chore(deps): update dependency @eslint/compat to v2 (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1306 [122] chore(deps): update dependency @chromatic-com/storybook to v5 (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1305 [123] fix(deps): update npm minor and patch (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1238 [124] chore(deps): update mysql docker tag to v8.3 (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1272 [125] chore: version packages (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1452 [126] fix(CLI Tool): #3591899 CLI push includes unsupported label property for content templates (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1451 [127] feat: #3518272 support all entity types with configurable displays for content templates (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/791 [128] Generate components when extensions are installed, even if syncing config (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1450 [129] feat(CLI Tool): Return flexible codebase files to local environment on canvas pull (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1443 [130] Draft: #3591838 [PHASE 2] introduce color props (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1432 [131] feat(Headless): #3591861 Add a Canvas-owned routed content endpoint for headless apps (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1436 [132] #3591838 brand kit color implementation (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1385 [133] chore: version packages (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1449 [134] fix(CLI Tool): #3591897 Canvas CLI sync fails for media and link props in global regions (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1446 [135] fix(UI): #3591894 Error message for empty value is displayed for select props... (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1440 [136] Draft: #3591810 Add AiWizardDev, a dev chat wizard that posts to... (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1448 [137] Draft: Resolve "Canvas AI: Add Tools dropdown to chat UI" (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1447 [138] #3581133: Automate MR review using PHPCS: disallow `\Drupal::service('something')`, require `\Drupal::service(Something::class)` whenever possible, with automatic fixing (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1297 [139] Issue #3591882: Add an Agents & Tools settings form. (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1445 [140] Issue #3577155: Add support for file fields using custom stream wrappers (currently only `public` is supported) (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1204 [141] #3591881 Canvas AI: Improve the schema of the place_components tool (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/1439 [142] feat: #3567225 Allow per-node override of Content Template via checkbox in node selector (canvas, MR) — https://git.drupalcode.org/project/canvas/-/merge_requests/948 [143] Avoid loading the full published catalog on the CCC overview page (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586355 [144] Avoid functional-test dual-container traps (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586325 [145] Rename entity bundle and target entity scope plugins for better DX (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586276 [146] Improve conditional subcontext disabled-state behavior and admin UX (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586292 [147] Allow scope plugins to declare an optional icon for UI display (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586262 [148] Complete scope plugin persistence API: manager orchestration, target entity encapsulation, and plugin-driven admin/selection (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586243 [149] Create Mad Libs style template for the CCC (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586340 [150] [Discuss] Adding priority to context item to affect ranking (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586364 [151] [Discuss] Review context selection ranking factors before 1.0 (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586365 [152] CCC beta3 blog post (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586332 [153] beta2 upgrade fails at updates 10006 and 10011 after bundleless entity conversion (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586343 [154] Update relevant CCC skipped tests (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586263 [155] QA team start testing CCC to get familiar with functionality and create QA plan (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586342 [156] Restore Drupal 10 compatibility and repair incomplete beta3 upgrades (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586338 [157] Clean up CCC inconsistencies and DX issues before rc1 (part 3) (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586271 [158] Add a dedicated editorial workflow for AI Context Items (ai_context, Issue) — https://git.drupalcode.org/project/ai_context/-/work_items/3586345 [159] Issue #3586355: Avoid loading the full published catalog on the CCC overview page. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/232 [160] Issue #3586325: Fix functional-test dual-container traps in AiContextAdminSettingsTest. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/225 [161] Issue #3586276: Rename entity bundle and target entity scope plugins for better DX (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/195 [162] Issue #3586292: Exclude conditional subcontext items when AI decisions are disabled. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/226 [163] Issue #3586343: Fix beta2 upgrade failures in updates 10006, 10008, and 10011. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/229 [164] Issue #3586338: Restore Drupal 10 compatibility and repair beta3 upgrades. (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/223 [165] Issue #3586345: Add a dedicated editorial workflow for AI Context Items (ai_context, MR) — https://git.drupalcode.org/project/ai_context/-/merge_requests/236 [166] Show AI status indicator next to the Generate button (ai_ckeditor, MR) — https://git.drupalcode.org/project/ai_ckeditor/-/merge_requests/6 [167] RagTool::execute() should expose structured per-result data and check entity access (ai_search, Issue) — https://git.drupalcode.org/project/ai_search/-/work_items/3584031 [168] Defer default search item access checking to the Search API datasource plugin (ai_search, Issue) — https://git.drupalcode.org/project/ai_search/-/work_items/3584042 [169] [PP-1] Provide an API for performing access check on non-content entities (ai_search, Issue) — https://git.drupalcode.org/project/ai_search/-/work_items/3579758 [170] Introduce a dedicated runtime access-checking API for AI Search / RAG filtering (ai_search, Issue) — https://git.drupalcode.org/project/ai_search/-/work_items/3584043 [171] bug: #3584035 Reset chunk-slicing progress when index is cleared or reset-tracker is run (ai_search, MR) — https://git.drupalcode.org/project/ai_search/-/merge_requests/71 [172] Support non content entity datasources (ai_search, MR) — https://git.drupalcode.org/project/ai_search/-/merge_requests/25 [173] Issue #3579758: Provide API for access checks on non-content entities (ai_search, MR) — https://git.drupalcode.org/project/ai_search/-/merge_requests/49 [174] [PP-1] Introduce a dedicated runtime access-checking API for AI Search / RAG filtering (ai_search, MR) — https://git.drupalcode.org/project/ai_search/-/merge_requests/75 [175] Add documentation (ai_translate, Issue) — https://git.drupalcode.org/project/ai_translate/-/work_items/3585534 [176] Fix Pipeline (ai_translate, Issue) — https://git.drupalcode.org/project/ai_translate/-/work_items/3585537 [177] Issue #3585537: Fix the Pipelines by adding composer.json (ai_translate, MR) — https://git.drupalcode.org/project/ai_translate/-/merge_requests/34 [178] Draft: Resolve "Add documentation" (ai_translate, MR) — https://git.drupalcode.org/project/ai_translate/-/merge_requests/32 [179] Add detail logic to the playground pipelines and add the ability to show the debug data by clicking on the executed pipeline item (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3589741 [180] A state update is applied through the reducers after the node completes (SG-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592366 [181] What the runtime hands a node, and what the node must declare to see it (SG-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592365 [182] How each state field is reduced (SG-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592364 [183] An engine that cannot consume a snapshot must throw (INT-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592363 [184] A terminal snapshot is not resumable (INT-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592362 [185] A checkpoint round-trip preserves which terminal status it was (INT-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592361 [186] An async handover seeds the queued run from the snapshot (INT-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592360 [187] Saving a snapshot is an upsert keyed by execution id (INT-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592359 [188] Snapshot validation returns a fixed set of codes (INT-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592358 [189] The workflow version hashes structural data only (INT-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592357 [190] What a snapshot carries (INT-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592356 [191] A pipeline signal is polled between jobs, never mid-job (INT-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592355 [192] The four conditions for a node to own a resume (INT-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592354 [193] Resolving an interrupt resets the job and resumes the pipeline (INT-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592353 [194] The interrupt entity is persisted by a subscriber (INT-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592352 [195] An interrupted node pauses the pipeline and reports where it stopped (INT-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592351 [196] Tools are handed to a processor only when there are some (DATA-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592350 [197] The model-facing tool schema omits parameters already filled (DATA-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592349 [198] Tool availability projects into tool bindings, not into data (DATA-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592348 [199] The unified output port composes exposed outputs only (DATA-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592347 [200] The effective execution config is stamped on the pipeline (SG-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592376 [201] Which stored state a resume restores, in order (SG-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592375 [202] A checkpoint per node, chained, plus one at the end (SG-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592374 [203] The reserved trigger port means no branch for loopback naming (SG-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592373 [204] An edge condition never routes (SG-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592372 [205] How a repeated node's result is keyed (SG-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592371 [206] Loopback re-entry needs an active branch and remaining work (SG-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592370 [207] Routing decides per edge and dispatches per target (SG-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592369 [208] The loopback input doubles as the item result (SG-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592368 [209] How a ForEach loop initialises and finishes (SG-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592367 [210] Which payloads the status vocabulary guards (PIPE-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592381 [211] The job status summary has one shape, derived from the enum (PIPE-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592380 [212] The live run status is read from persisted entities (PIPE-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592379 [213] The execution id the editor polls is the pipeline id (SG-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592378 [214] Exceeding the iteration budget throws (SG-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592377 [215] node_statuses is keyed by the workflow node id (PIPE-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592382 [216] A hidden output is stripped where it is produced (DATA-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592346 [217] Inside a node, the parameter-resolution cascade decides (DATA-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592345 [218] Launch data fills in under edge-delivered inputs (DATA-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592344 [219] Loopback and tool edges are dropped from data delivery (DATA-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592343 [220] Readiness promotes a job whose dependencies are met (DATA-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592342 [221] A trigger edge carries no data (DATA-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592341 [222] One value per port, last executor wins (DATA-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592340 [223] Delivery is port to port, both names read from the handle (DATA-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592339 [224] Direct sync skips a node whose trigger was never satisfied (BR-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592338 [225] Staleness gates a branch decision, not delivery (BR-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592337 [226] Branch gating applies to trigger and data ports alike (BR-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592336 [227] A node's configured branches are the authority on branch ports (BR-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592335 [228] How active_branches is normalized (BR-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592334 [229] The three cases where a branch edge activates (BR-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592333 [230] When a branch edge is gated at all (BR-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592332 [231] A cancelled run is announced like any other terminal outcome (ORC-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592331 [232] Claiming a job is atomic under concurrent workers (ORC-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592330 [233] Auto-resume is gated, not unconditional (INT-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592329 [234] A terminal pipeline cannot be paused or resumed (INT-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592328 [235] A resume re-enters through the pipeline's declared orchestrator (ORC-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592327 [236] An async launch returns queued immediately (ORC-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592326 [237] How a run's terminal status is decided (ORC-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592325 [238] An iteration and time budget breaks the loop (ORC-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592324 [239] A pipeline engine is a ready-job loop (ORC-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592323 [240] Direct sync filters which trigger node starts the run (ORC-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592322 [241] Direct sync walks the execution order once (ORC-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592321 [242] Every strategy shares one contract and one hierarchy (ORC-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592320 [243] Capability queries are answered from the plugin definition only (ORC-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592319 [244] StateGraph is the session default, not the global one (ORC-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592318 [245] An unknown orchestrator type falls back with a warning (ORC-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592317 [246] How the default orchestrator is resolved (ORC-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592316 [247] The four orchestrator strategies and their ids (ORC-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592315 [248] Every orchestrator routes an error result identically (DECIDED) (ERR-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592314 [249] Remove the direct-sync record-and-continue divergence (ERR-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592313 [250] Retry is in-place, immediate and opt-in (ERR-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592312 [251] A routed-failed node satisfies only its error edges (ERR-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592311 [252] A pipeline whose only failures were routed still completes (ERR-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592310 [253] An error result with no error edge fails the run (ERR-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592309 [254] An error result with an error edge routes instead of failing the run (ERR-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592308 [255] An unserializable output fails the node (ERR-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592307 [256] A stop request bypasses the error catch and stops the run cleanly (ERR-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592306 [257] An interrupt is re-thrown unchanged (ERR-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592305 [258] Any other exception fails the node and is re-thrown wrapped (ERR-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592304 [259] A retryable exception stays recognisable after it is caught (ERR-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592303 [260] A RuntimeException from a processor becomes an error result (ERR-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592302 [261] A node mapping carries both the processor and the node-type id (CMP-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592301 [262] A tool consumer must declare that it accepts tools (CMP-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592300 [263] Tool names must be unique per consumer at compile time (CMP-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592299 [264] Execution order is a topological sort (CMP-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592298 [265] A trigger dependency outranks a data dependency for ordering (CMP-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592297 [266] Which nodes are excluded from the execution graph (CMP-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592296 [267] Cycle detection ignores the edges that are meant to loop (CMP-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592295 [268] Edge type is derived from handles, never declared (CMP-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592294 [269] Compile preconditions run first, in a fixed order (CMP-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592293 [270] Re-enrichment on the run path is conditional (CMP-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592292 [271] What compiling a workflow produces (CMP-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592291 [272] One expression-error policy across every engine (DECIDED) (LANG-29) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592290 [273] The six operators the if/else gateway declares (LANG-28) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592289 [274] The switch gateway matches a branch value instead of evaluating it (LANG-27) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592288 [275] A prompt template turns a Twig error into a node failure (LANG-26) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592287 [276] DataShaper resolves its five sentinels before consulting an engine (LANG-25) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592286 [277] A NULL extraction is a soft miss, never an error (LANG-24) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592285 [278] DataExtractor unwraps a first match only for JSONPath (LANG-23) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592284 [279] DataExtractor re-wraps any evaluator throwable as a RuntimeException (LANG-22) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592283 [280] DataMapper re-wraps only a RuntimeException from an evaluator (LANG-21) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592282 [281] What exists() answers for an empty path and for a scalar (LANG-20) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592281 [282] Extracting all matches on a property path wraps the single result (LANG-19) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592280 [283] How a mapping value is marked as a literal instead of an expression (LANG-18) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592279 [284] Dot-to-bracket normalization is duplicated in three classes (LANG-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592278 [285] A string context is decoded as JSON when it is JSON (LANG-16) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592277 [286] A single JSONPath match is unwrapped unless the path is multi-value (LANG-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592276 [287] A path is JSONPath when it starts with $ (LANG-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592275 [288] Twig validation is compile-only (LANG-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592274 [289] JSONPath validation accepts anything that is not a $ path (LANG-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592273 [290] Property-path validation delegates to the same parser (LANG-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592272 [291] Expression Language validation accepts unknown variable names (LANG-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592271 [292] JSONPath never throws, and has three distinct outcomes (LANG-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592270 [293] A property path never throws; an unreadable path is NULL (LANG-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592269 [294] Twig renders a missing variable as an empty string (LANG-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592268 [295] Expression Language reports a syntax error, and a missing variable is one (LANG-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592267 [296] Expression validation has exactly one production call site (LANG-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592266 [297] A non-array context is wrapped for the template engines (LANG-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592265 [298] What an empty expression evaluates to, per engine (LANG-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592264 [299] Getting an evaluator never lets a plugin-manager failure escape (LANG-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592263 [300] Extraction engines query context; transformation engines see a variable map (LANG-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592262 [301] Refuse a synchronous launch of an async-declared workflow (MAN-19) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592261 [302] The manifest is rebuilt only when the declared ports change (MAN-18) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592260 [303] A declared output reads from its node's result (MAN-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592259 [304] Launch inputs are checked against the manifest snapshot (MAN-16 (G4)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592258 [305] Input checking short-circuits at the first failing stage (MAN-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592257 [306] A malformed manifest entry is dropped with a warning, even in strict mode (MAN-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592256 [307] Strict mode refuses an undeclared input by name (MAN-13 (G3)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592255 [308] Node-keyed pass-through is an internal contract (MAN-12 (G2)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592254 [309] A named input resolves to its node and port (MAN-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592253 [310] A declared manifest name wins over the node-keyed pass-through (MAN-10 (G1)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592252 [311] A workflow used as a node exposes its manifest, with a cycle guard (MAN-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592251 [312] An unresolvable manifest entry is dropped from the snapshot (MAN-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592250 [313] Which default values survive into the manifest snapshot (MAN-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592249 [314] Author metadata overlays the plugin annotations and wins (MAN-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592248 [315] A manifest snapshot is built from the plugin fragment and stripped (MAN-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592247 [316] The validator guards manifest integrity (MAN-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592246 [317] The authoring picker offers only ports that exist (MAN-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592245 [318] The shape of a manifest entry (MAN-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592244 [319] A workflow's input ports are a declared manifest, never derived (MAN-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592243 [320] The dynamic-port form appears only when the node type opts in (DYN-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592242 [321] Dynamic ports have no exposure semantics (DYN-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592241 [322] A static parameter name beats a dynamic one (DYN-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592240 [323] An unconnected dynamic port resolves to NULL, with its key present (DYN-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592239 [324] Reject an invalid or duplicate dynamic port name (DYN-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592238 [325] A dynamic port item needs a name, label and dataType (DYN-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592237 [326] A node type opts into dynamic ports by spreading their schema in (DYN-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592236 [327] Port order is cosmetic and the engine never reads it (EXPO-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592235 [328] The exposure checkbox seeds from the saved value (EXPO-16) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592234 [329] Which parameters a model may fill on a tool call (EXPO-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592233 [330] Stripping runs before the unified output port is composed (EXPO-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592232 [331] An output the node type hides is stripped unconditionally (EXPO-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592231 [332] Control outputs are never stripped (EXPO-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592230 [333] A hidden output's value is stripped where it is produced (EXPO-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592229 [334] A hidden input port receives no runtime value (EXPO-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592228 [335] The one-time exposure freeze writes only the hidden entries (EXPO-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592227 [336] A parameter added after install has no stored exposure until a re-save (EXPO-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592226 [337] Materialize an exposure entry only when it diverges from the default (EXPO-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592225 [338] The plugin's exposure hint is read at authoring time only (EXPO-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592224 [339] A schema hides a port by default only when it says so exactly (EXPO-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592223 [340] An untouched node stores no ports key, so the default always applies (EXPO-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592222 [341] How a port direction maps to its config key (EXPO-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592221 [342] An instance override decides exposure before any default does (EXPO-2 (D3)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592220 [343] PortExposure is the only PHP accessor for effective exposure (EXPO-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592219 [344] A config default is written only for a configurable parameter (CFG-18) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592218 [345] The unified input merge only fills connectable parameters (CFG-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592217 [346] The reserved input port is decomposed before the schema loop (CFG-16) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592216 [347] Every dynamic input is present in the resolved bag (CFG-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592215 [348] Every schema property is present in the bag, NULL when unresolved (CFG-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592214 [349] The resolved bag holds exactly the schema's keys plus dynamic ports (CFG-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592213 [350] Format validation covers nine formats and ignores the rest (CFG-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592212 [351] The type check is a closed match with no coercion (CFG-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592211 [352] A resolved value is validated against the plugin schema (CFG-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592210 [353] A required parameter that resolves to NULL fails the node (CFG-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592209 [354] Internal parameters accept a runtime value but never config (CFG-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592208 [355] Presence is key existence, so an explicit NULL wins over a lower priority (CFG-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592207 [356] Priority 3: fall back to the effective default (CFG-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592206 [357] Priority 2: take a config value when the parameter is configurable (CFG-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592205 [358] Priority 1: take a runtime value when the port can receive one (CFG-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592204 [359] An effective default is the entity's, then the plugin's, then NULL (CFG-3 (D4)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592203 [360] The exposure default fails open (CFG-2 (D2)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592202 [361] Gate flags fail closed (CFG-1 (D1)) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592201 [362] Config fields are ordered by their declared order (SCH-31) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592200 [363] The run path re-enriches from the live node type (SCH-29) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592199 [364] The executor plugin id comes from the node type, never from the payload (SCH-28) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592198 [365] The wire shape is lean: emit a key only when it diverges from the default (SCH-27) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592197 [366] The editor catalog serves enabled node types, sorted (SCH-26) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592196 [367] Enrichment anchors on the node-type id alone (SCH-25) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592195 [368] Building node data logs and degrades instead of failing the editor (SCH-24) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592194 [369] The UI schema is generated from the final config schema (SCH-23) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592193 [370] Only a config-edit provider gets a configEdit block (SCH-22) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592192 [371] Every node gets a reserved instance title and description (SCH-21) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592191 [372] A node's visual type comes from the config entity only (SCH-20) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592190 [373] Both key enumerations skip trigger and hidden parameters (SCH-19) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592189 [374] Prepend the unified output port when the node exposes one (SCH-18) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592188 [375] Prepend the unified input port when the node exposes one (SCH-17) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592187 [376] The exposure defaults of the reserved ports (SCH-16) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592186 [377] An injected port declares its exposure default only when it diverges (SCH-15) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592185 [378] Inject the reserved error output on every executable node (SCH-14) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592184 [379] Inject the reserved tool output only on a tool-exposed node (SCH-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592183 [380] Inject the reserved trigger output on every node but a terminal node (SCH-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592182 [381] Inject the reserved trigger input on every node but a start node (SCH-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592181 [382] The schema-to-dataType map is closed (SCH-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592180 [383] A union type normalizes to its first non-null member (SCH-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592179 [384] One mapping turns a schema into ports (SCH-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592178 [385] An output reaches the editor only when the node type exposes it (SCH-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592177 [386] A parameter is required on the input side only when it is not configurable (SCH-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592176 [387] Reserved config-only parameters never become ports (SCH-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592175 [388] Hidden parameters are dropped from both derived schemas (SCH-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592174 [389] Deriving splits one parameter schema into an input schema and a config schema (SCH-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592173 [390] Schema derivation reads its gate flags from the plugin schema (SCH-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592172 [391] A node's input and output surface comes only from its two schema methods (SCH-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592171 [392] Transport edges and job-metadata edges each own their own key names (EDGE-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592170 [393] Edge conditions are a removed feature that is tolerated but never read (EDGE-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592169 [394] What makes a node tool-only (EDGE-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592168 [395] An edge is an error edge by its source handle (EDGE-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592167 [396] An edge is a tool edge by declared type, else by its target handle (EDGE-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592166 [397] An edge is a loopback edge when its target handle says so (EDGE-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592165 [398] An edge is a trigger edge when its target handle says so (EDGE-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592164 [399] No wire key is structurally required; an absent one becomes a missing endpoint (EDGE-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592163 [400] How a port handle encodes its node, direction and port name (EDGE-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592162 [401] Refuse a duplicate edge between the same two ports (R13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592161 [402] Refuse an edge from a node to itself (R12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592160 [403] Every configured expression must pass its engine's check at save (R11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592159 [404] A workflow exposure must target a port exposed on the node instance (R10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592158 [405] A node's node-type anchor must resolve to a node type that exists (R9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592157 [406] Edge ids must be present and unique at save (DECIDED) (R3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592156 [407] Node ids must be unique (DECIDED) (R2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592155 [408] The whole validator runs again at launch (VAL-LAUNCH) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592154 [409] The validator instantiates plugins only for the exposure checks (VAL-PERF) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592153 [410] Warn about an edge leaving a terminal node (W-T) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592152 [411] An exposure must name a port the plugin declares (R4.d) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592151 [412] An exposure must name a node that exists (R4.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592150 [413] Exposure names must be unique per side (R4.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592149 [414] An exposure name must match the allowed format (R4.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592148 [415] Skip the edge-exposure check where another rule already owns the problem (R7.e/f) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592147 [416] A port the node type never declared is out of the edge-exposure check (R7.d) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592146 [417] Effective exposure comes from the instance config, then the node-type default (R7.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592145 [418] Refuse an edge out of a hidden output port (R7.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592144 [419] Refuse an edge into a hidden input port (R7.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592143 [420] An edge missing both endpoints reports both errors (R8.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592142 [421] Refuse an edge whose target node does not exist (R8.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592141 [422] Refuse an edge whose source node does not exist (R8.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592140 [423] Retire validateParams() from the processor contract (R6.k) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592139 [424] Warn when a secret reference is written without its leading $ (R6.l) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592138 [425] An unresolvable node type skips only the schema-driven config checks (R6.j) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592137 [426] A NULL config value means unset and is never validated (R6.i) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592136 [427] Refuse a string that does not match its pattern (R6.h) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592135 [428] Refuse a string outside its length bounds (R6.g) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592134 [429] Refuse a number outside its minimum/maximum (R6.f) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592133 [430] Refuse a config value outside its enum (R6.e) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592132 [431] Refuse a config value of the wrong type (R6.d) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592131 [432] An unknown config key is a warning, not a refusal (R6.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592130 [433] Every required config key must be present (R6.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592129 [434] Refuse a node whose config is not an array (R6.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592128 [435] Report a missing plugin once, not once per port (R1.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592127 [436] A node with no resolvable node type is skipped by the plugin check (R1.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592126 [437] Refuse a node whose executor plugin does not exist (R1.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592125 [438] Refuse a node with no id, located by its position (R5.c) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592124 [439] Refuse a workflow with more than 1000 edges (R5.b) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592123 [440] Refuse a workflow with more than 500 nodes (R5.a) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592122 [441] Retire the node config-validate endpoint (API-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592121 [442] A session with no workflow is a 409, not a 500 (API-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592120 [443] The session-turn door checks its inputs exactly like the launch door (API-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592119 [444] Every JSON door decodes through the shared, bounded decoder (API-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592118 [445] One payload key per node-type concept (STORE-13) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592117 [446] A finished turn leaves the session completed, not idle (STORE-12) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592116 [447] Entity statuses are backed enums whose value is what crosses a boundary (STORE-11) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592115 [448] WorkflowDTO::fromArray() normalizes for the read path only (STORE-10) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592114 [449] Bundle import runs its gates in a fixed order and rolls back on refusal (STORE-9) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592113 [450] A workflow's schema version must be semver (STORE-8) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592112 [451] The stored config schema is strict about node metadata (STORE-7) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592111 [452] Saving slims transient canvas state out of the stored workflow (STORE-6) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592110 [453] A validation failure at the REST boundary is a 422 and never reaches save (STORE-5) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592109 [454] Absent collections default to empty on create; a partial update preserves them (STORE-4) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592108 [455] A client-supplied id that already exists is a conflict, never an overwrite (STORE-3) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592107 [456] A workflow name is required and capped at 255 bytes (STORE-2) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592106 [457] Branch gateways and which edges activate (RT-BR) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592104 [458] Delivering values between nodes (RT-DATA) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592103 [459] Compiling a workflow into an execution plan (RT-CMP) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592102 [460] The pipeline status the editor polls (RT-PIPE) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592101 [461] Choosing and running an orchestrator (RT-ORC) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592100 [462] The StateGraph runner (RT-SG) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592099 [463] Interrupts, pausing and resuming (RT-INT) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592098 [464] How a failing node is handled (RT-ERR) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592097 [465] The JSON API doors (GR-API) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592096 [466] Storing and serving a workflow definition (GR-STORE) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592095 [467] Author-defined dynamic ports (GR-DYN) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592094 [468] A workflow's declared inputs and outputs (GR-MAN) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592093 [469] Resolving a node's parameters (GR-CFG) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592092 [470] Turning a plugin schema into ports and forms (GR-SCHEMA) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592091 [471] The four expression engines (GR-LANG) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592090 [472] Port exposure (GR-EXPO) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592089 [473] How edges connect ports (GR-EDGE) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592088 [474] What the workflow validator refuses (GR-VAL) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592087 [475] Return 400 for a malformed API request body (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592086 [476] Write down and test every runtime and workflow-language rule (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592085 [477] Remove unused API and developer surfaces from 2.x (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592084 [478] Report pipeline and job status consistently to the editor (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592083 [479] Make error routing, cancellation and resume behave the same in every runner (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592082 [480] Catch broken workflows when they are saved, not when they run (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592081 [481] Expression errors fail the node and route to its error edge (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592080 [482] [meta] Make the 2.x runtime and workflow-language contracts explicit and tested (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592079 [483] Refuse an empty, oversized, malformed or too-deeply-nested request body (STORE-1) (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592105 [484] AI Assistant is broken from 1.5.0 (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3592073 [485] Add "Show Pipelines" to the operations per workflow (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3589740 [486] Remove "Pending" tag when the workflow is executing and the component has been skipped (flowdrop, Issue) — https://git.drupalcode.org/project/flowdrop/-/work_items/3589739 [487] Add config for max characters (agui, Issue) — https://git.drupalcode.org/project/agui/-/work_items/3585465 [488] Better Error Handling in chat (agui, Issue) — https://git.drupalcode.org/project/agui/-/work_items/3590046 [489] Allow Token support on Assistant Controller (agui, Issue) — https://git.drupalcode.org/project/agui/-/work_items/3589993 [490] Enable Drupal GitLab CI pipeline and add Unit/Kernel/Functional test coverage (agui, Issue) — https://git.drupalcode.org/project/agui/-/work_items/3590044 [491] Add validator and extractor services/methods and new setting. (agui, MR) — https://git.drupalcode.org/project/agui/-/merge_requests/40 [492] Add error util and handler. (agui, MR) — https://git.drupalcode.org/project/agui/-/merge_requests/39 [493] Resolve "Allow Token support on Assistant Controller" (agui, MR) — https://git.drupalcode.org/project/agui/-/merge_requests/38 [494] Resolve "Enable Drupal GitLab CI pipeline and add Unit/Kernel/Functional test coverage" (agui, MR) — https://git.drupalcode.org/project/agui/-/merge_requests/34 --- TODAY'S MODULE SUMMARIES ---
AI (Artificial Intelligence)

The AI module saw focused progress on field-level automation and streaming chat capabilities over the past 24 hours. Work was completed to enable AI-powered workflows directly within content editing interfaces, allowing editors to trigger automated text generation without leaving the page. This capability connects Field Widget Actions with the module's multi-step Automator Chain feature, supporting more complex editorial workflows that previously required multiple separate fields or manual steps.

Two separate merges integrated this Field Widget Action support into different release branches, ensuring the feature will be available across supported versions. The work addresses practical limits on how much context AI models can process in a single request, enabling multi-turn workflows that break complex tasks into manageable steps.

Several bugs affecting the editor experience were identified and are under review. Issues were reported with the markdown-based prompt editor failing to parse Drupal tokens and colons—both common in real-world prompts. A fix is in progress for a streaming chat bug that corrupts URLs when AI-generated content includes links. Another bug preventing assistants backed by agents from streaming responses was identified and closed as a duplicate of an existing issue.

Planning and architectural work continued on permissions for the platform configuration system, chat memory persistence, and adoption of the latest Symfony AI component. Three new agent skills were proposed to enable command-line configuration of automators, guardrails, and general AI settings—part of a broader effort to make the module more scriptable and agent-friendly.

How can I help on this project?

Prioritize user experience review of the markdown editor issues affecting prompt authoring, as these directly impact day-to-day usability for content teams configuring AI workflows.

Clarify strategic direction on permissions and multi-tenancy for the new platform configuration, helping the team finalize architecture decisions that will shape governance and delegation capabilities.

Contributors: Ahmad Khalil (ahmad-khalil-imagex) [1], Ann Mary Sruthy (annmarysruthy), Artem Dmitriiev (a.dmitriiev), Bruno Bruno (bbruno), Dezső Biczó (mxr576), Isaac Trogdon (dotist), Marcus Johansson (Marcus_Johansson), Prabhavathi Vanipenta (prabha1997), Rob Loach (robloach), Rodel Duterte (rduterte), Wolfgang Ziegler (fago)
---
Drupal AI Initiative

Activity this period centered on partnership expansion and process improvements. Two new partners are being onboarded: Pantheon (Gold tier) and Specbee (Silver tier). The Pantheon onboarding was completed, including integration into communication channels and team workflows. Work on Specbee's onboarding continued, with follow-up tasks to add them to the partner directory and run an audit to confirm successful integration.

To support future growth, templates for partner onboarding and audit processes were closed as complete, standardizing how new organizations join the initiative. A request was opened to update partner badges to use "Partner" instead of "Sponsor" language, better reflecting the collaborative nature of these relationships. Work also began on refreshing the partner logo wall and conducting periodic audits of contributor access to ensure alignment with active participation.

A new capability was proposed to create repeatable manual testing processes for issue review, aiming to improve consistency and provide documented evidence of before-and-after behavior without requiring reviewers to rebuild environments.

How can I help on this project?

Approve the partner badge redesign request to ensure brand consistency as the partnership program scales.

Allocate resources to formalize the testing documentation approach if early feedback indicates it reduces review friction.

---
AI Integration - ECA

This module enables natural-language interaction with Drupal's Event-Condition-Action (ECA) automation system, allowing users to create and manage automation workflows through conversational AI rather than manual configuration.

Work has begun on modernising the module's underlying architecture. A migration to the Tools + ReAct architecture was opened this period. This effort will replace the current custom control flow with a more maintainable, standardised approach that leverages the broader AI Integration framework. The change is expected to improve reliability and make future enhancements easier to deliver. The work is part of the roadmap toward a stable 1.0.0 release.

No merge activity or commits occurred during this period. Development continues in the open merge request.

How can I help on this project?

Review and approve the architectural direction for the Tools + ReAct migration to accelerate progress toward 1.0.0.

Allocate testing resources to validate the new architecture once the merge request is ready for review.

Contributors: Marcus Johansson (Marcus_Johansson)
---
OpenAI Provider

The OpenAI Provider module made steady progress over the past 24 hours, with three updates merged that improve performance and reliability for users integrating OpenAI services into their Drupal sites.

Support for batch embeddings was added, enabling more efficient processing of multiple text inputs at once. This reduces the number of API calls needed and improves system performance when generating embeddings at scale.

A fix for rate limits was merged, helping the module handle OpenAI's usage restrictions more gracefully. This should reduce service interruptions and provide more predictable behavior during high-volume operations.

A bug affecting GPT functionality was also resolved, restoring expected behavior for users working with GPT-based features.

Together, these updates strengthen the module's stability and efficiency for organizations deploying AI-powered content and automation workflows.

How can I help on this project?

Ensure the team has adequate OpenAI API credits and budget for testing across different usage patterns and rate limit scenarios.

Connect the development team with end users to gather feedback on performance improvements and identify remaining pain points.

Contributors: Marcus Johansson (Marcus_Johansson) [1], Paul Sheldrake (paulsheldrake) [1] ---
amazee.ai Private AI Provider

The module made progress on instrumentation and is addressing a critical data integrity issue. A new merge request was opened to add tracking headers to API requests, enabling better visibility into which module versions are generating traffic to the amazee.ai service. This will support troubleshooting and usage analytics.

A significant data loss issue was identified and is now awaiting final review: Deleting or clearing items in a Search API index deletes data from other indexes sharing the same Vector DB collection. The issue occurs when multiple search indexes share the same underlying database collection. Clearing or updating one index can inadvertently delete records from others, resulting in silent and permanent data loss. This affects any deployment using shared vector database collections and has been assigned for resolution.

How can I help on this project?

Prioritize review and approval of the data loss fix to prevent further incidents in production environments.

Ensure adequate testing resources are available to validate the fix across different deployment configurations before release.

Contributors: Dan Lemon (dan2k3k4)
---
Microsoft Azure AI

A significant refactor of the Azure provider infrastructure was opened during this period. The [#3552969] feat: Refactor AzureProvider to use OpenAiBasedProviderClientBase merge request represents work to restructure how the module connects to Azure's AI services. This change is designed to improve code reusability and maintainability by building on a shared foundation with other OpenAI-compatible providers. For users, this means more consistent behavior across different AI service integrations and easier future enhancements. The refactor is substantial, touching 680 lines of code, and signals progress toward a more mature and scalable architecture.

No issues were updated during this period, and the refactor remains open for review. This is normal development activity for a module in active evolution.

How can I help on this project?

Ensure the team has dedicated time allocated for code review of the open refactor, as architectural changes require careful evaluation before integration.

Consider whether user acceptance testing resources are available once the refactor merges to validate that Azure AI integrations continue working as expected.

Contributors: Jukka Huhta (jhuhta)
---
Postgres VDB Provider

A new merge request was opened to address an issue where certain data columns are lost after clearing and reindexing operations. This work aims to preserve important data structure throughout the reindex process, ensuring that information is not inadvertently dropped when the system refreshes its indices. If merged, this fix will improve data consistency and reduce the risk of information loss during routine maintenance operations.

No issues were updated and no code was committed to the main repository during this period. The module is continuing its development with focused attention on data integrity concerns.

How can I help on this project?

Arrange code review resources to evaluate the pending merge request, which addresses a data integrity concern.

Clarify release timeline expectations and prioritization for this module within the broader AI initiative.

Contributors: Ignacio Pérez Puertas (djnash2002) ---
Model Context Protocol

The Model Context Protocol module saw continued work during this period on authentication functionality. A Token Auth is not working issue remains open, with an associated merge request under review. The issue addresses problems preventing administrators from enabling token-based authentication through the configuration interface, which currently requires manual configuration workarounds. Resolving this will allow site administrators to enable secure authentication options through the standard interface, improving both usability and security setup for the module.

No merge requests were merged or commits pushed during this 24-hour window, indicating planning and review activities are underway rather than active code integration.

How can I help on this project?

Allocate review capacity to evaluate the open authentication merge request, enabling faster integration of completed work.

Clarify the module's target release timeline (alpha, beta, or stable) to help the team prioritize stabilization versus new features.

Contributors: Alin Ameiroaie (aalin)
---
AI Agents

Development activity this period centered on refining agent configuration and addressing operational issues. Work was completed to allow users to set custom provider tags when running agents, making it easier to track and filter specific interactions in the event log. This capability was marked complete and closed.

Several configuration enhancements are in progress. Work continues on allowing individual agents to use specific language model providers rather than a shared default, giving administrators more control over cost and performance tradeoffs. A related feature to let parent agents forward requests directly to subagents without reprocessing is under development, aimed at improving response consistency and reducing latency.

Multiple bug fixes are being addressed through open merge requests, including issues where the chatbot interface handles search queries differently than the tool explorer, and where conversation history persists unexpectedly after clearing. Work is also underway on implementing limits to prevent tools from running too frequently, and on integrating short-term memory capabilities into agents.

The module continues in active development with normal issue activity for a pre-stable release. No critical blockers were identified this period.

How can I help on this project?

Review open merge requests to help validate whether bug fixes resolve the reported issues, particularly around chatbot behavior consistency.

Provide guidance on prioritization between new configuration features and stability improvements as the module approaches a production-ready release.

Contributors: Bharat Kelotra (bharatkelotra), Marcus Johansson (Marcus_Johansson)
---
Tool API

The Tool API project made significant progress toward its first release candidate, with five key integration issues resolved and compatibility with Drupal 10.5 through 11 now tested in continuous integration. The focus this period was on ensuring the module's data schemas work reliably across different AI platforms and fixing issues where execution failures were not clearly reported to users or AI models.

The project resolved problems that prevented tools from working with Anthropic AI models and fixed issues where entity descriptions containing common punctuation appeared garbled to AI systems. A fix was merged for the REST serialization conflict that broke other modules' JSON output when Tool API was enabled. Additional work corrected how the AI connector handles tools that fail before execution, ensuring callers receive meaningful error messages instead of technical exceptions.

The project opened a comprehensive tracking issue outlining the path to release candidate 1, identifying 18 items that must be addressed before the programming interface can be frozen. These include fixing broken configuration-sourced inputs, correcting validation logic that skips items in multi-value fields, and resolving access-check failures. Several issues are tagged as quick wins requiring only a few lines of code but representing breaking changes if deferred beyond the release candidate freeze.

Strategic planning work began tracking alignment with Drupal core's emerging CLI initiative, positioning the module's metadata model as a candidate for adoption in core and identifying opportunities for advocacy as core considers structured outputs for command-line tools.

How can I help on this project?

Prioritise resourcing for the 18 pre-RC1 items to meet the interface freeze deadline. Facilitate a decision on the API surface annotation strategy to clarify which components are stable versus internal. Consider sponsoring documentation work for the stable release security review.

Contributors: Abhisek Mazumdar (abhisekmazumdar) [1], Bryan Sharpe (b_sharpe) [1], Michael Lander (michaellander) [11]
---
Drupal Canvas

The past 24 hours saw three fixes merged to production and continued advancement across AI tooling, translation workflows, and developer experience.

Two command-line interface issues were resolved. A fix for content template push errors was merged, enabling the CLI to correctly create templates without triggering server-side validation failures. A fix for global region synchronization resolved failures when pushing media images and links, ensuring these props are now handled correctly during sync operations.

A major developer experience improvement was also merged: an automated code quality check that enforces safer, more maintainable service references across the codebase. This change reduces ambiguity and makes code easier to navigate.

Active development continues on AI chat capabilities, including a tools dropdown for the chat interface and an admin settings form to configure available agents and tools. The placement tool schema was improved to give AI agents clearer, more structured instructions when positioning components.

Work is also progressing on translation support for older component versions, right-to-left language layout, autosave reliability, and broader entity type support for content templates.

How can I help on this project?

Prioritize backend review capacity for the translation fix and RTL support work to ensure multilingual readiness.

Clarify product direction on AI agent selection: confirm whether the admin-controlled tools approach aligns with rollout plans.

Contributors: **** (project_19391_bot_17a61b0edeafd5a3db3e8b2462b6c010), **** (project_19391_bot_cb443e60680723bba08a5351bf595251), Adam G-H (phenaproxima), Ben Mullins (bnjmnm), Bálint Kléri (balintbrews) [1], Canvas version bot [2], David Bravo (davidbp), Harumi Jang (hooroomoo), Jeremy Chinquist (jjchinquist), Juan Correa (jucs7) [1], Kunal Sachdev (kunal.sachdev), Lionel Enkaoua (heyyo), mariosr, Rajab Natshah (RajabNatshah), Tekla Aivazashvili (aivazashvilit), Wim Leers (wimleers) [1], wotnak [1]
---
Context Control Center (CCC)

Development this period focused on preparing the module for its first release candidate and stable version. Work advanced on several stability and compatibility issues that are critical for production readiness.

A dedicated editorial workflow for context items is being created to replace reliance on shared workflows, giving the module clearer publishing states and preventing unintended side effects on other content. Progress continued on fixing upgrade problems for sites moving from beta2 to current versions, particularly around entity bundle changes. A separate effort is addressing Drupal 10 compatibility issues and incomplete beta3 upgrades to ensure the module works reliably across supported platform versions.

Performance improvements are underway to avoid loading the entire published catalog when displaying the overview page. The scope plugin architecture is being completed to provide a consistent persistence and selection interface, which will make future extensions easier to build. A rename of scope plugins is in progress to improve clarity for editors choosing which entities receive context.

Planning discussions opened on context ranking factors and priority levels, exploring how the module should decide which guidance reaches AI features when limits apply. A quality assurance plan is being developed to systematically test functionality before the stable release.

How can I help on this project?

Ensure the quality assurance team has sufficient time allocated to complete systematic testing and develop the QA plan before stable release.

Confirm product direction on the context ranking and priority discussions to unblock design decisions needed before version 1.0.

Contributors: Kristen Pol (kepol), Levente Besenyei (LeventeB), Pravesh Poonia (Pravesh_Poonia), Reinhold Schachner (reinimax), Tamas Balog (tbalog)
---
AI CKEditor

A new merge request was opened to improve user feedback during content generation. Currently, when users click the Generate button inside the editor, they must scroll down to see whether their request is being processed. The proposed change will display a status indicator directly next to the Generate button, giving users immediate visual confirmation that their request is in progress without requiring them to navigate within the modal window.

This enhancement addresses a usability gap in the AI Writer feature and should reduce confusion for users waiting for generated content to appear. The change is relatively small in scope and awaits review before being integrated into the module.

How can I help on this project?

Ensure the team has capacity to review and merge the pending user experience improvement.

If broader user testing or feedback on the AI Writer workflow is planned, allocate time or resources to conduct it.

Contributors: Ricardo Castañeda (cadence96) ---
AI Search

The AI Search module saw focused development activity around improving how search results are checked for access and how structured data is returned to applications using the module's RAG (retrieval-augmented generation) capabilities.

A key gap was identified and addressed: the RAG tool was previously only returning a single text string to language models, discarding important metadata like which content each result came from, relevance scores, and individual text chunks. Work on RagTool::execute() should expose structured per-result data and check entity access aims to preserve this information so applications can show users which sources were consulted, not just the AI-generated answer.

Parallel efforts are improving access control. The module historically only supported permission checks for standard content, blocking use with other data types. New work is underway to defer access checking to Search API datasource plugins and to introduce a dedicated runtime access-checking API that lets organizations enforce stricter filters—for example, preventing sensitive data from being sent to external AI services even when a user technically has permission to view it on the website.

How can I help on this project?

Prioritize testing and review resources for the open access-control work, which affects data security and compliance.

Clarify business requirements for sensitive-data filtering to guide the new runtime access API design.

Contributors: Abhisek Mazumdar (abhisekmazumdar), David Bondor (superbondor), Dezső Biczó (mxr576)
---
AI translate

The AI translate module saw foundational work over the past 24 hours focused on project infrastructure and knowledge sharing. Two key issues were advanced to ensure the module can be effectively maintained and adopted.

A documentation initiative is underway to create user-facing guidance for the module, which currently has none. A draft merge request has been opened with substantial content to address this gap. Clear documentation will be essential for teams evaluating or implementing automated translation capabilities.

Separately, work began on Fix Pipeline to restore automated quality checks that are currently non-functional. A proposed solution has been submitted for review. Restoring these checks will help maintain code quality as development continues.

Both issues remain open with draft or pending solutions. No code was merged during this period, but the preparatory work positions the project to improve both developer experience and end-user accessibility.

How can I help on this project?

Allocate reviewer time to assess and merge the pending documentation and pipeline fixes, enabling faster iteration.

Clarify the target release timeline and stability goals to help prioritize outstanding work appropriately.

Contributors: Marcus Johansson (Marcus_Johansson), Rob Loach (robloach)
---
FlowDrop

FlowDrop has completed a major consolidation of its runtime and workflow-language contracts, closing 316 specification-related issues over the reporting period. This work establishes a formal, tested foundation for how workflows are validated, executed, and reported across all execution strategies.

Strategic Progress

The project has delivered a comprehensive specification registry covering ten domains: workflow storage and API boundaries, schema and port discovery, parameter resolution, exposure semantics, edge classification, expression engines, validation rules, orchestrator behaviour, error handling, data delivery, branching, compilation, interrupts, state management, and status reporting. Each of 247 runtime rules now cites its implementation and binding test, with automated coverage enforcement preventing drift. This positions FlowDrop to onboard contributors and evolve the platform with confidence that changes will not silently break downstream behaviour.

Key user-facing improvements include unified error routing (all four runners now handle error edges identically), consistent status reporting to the editor (node badges now reflect the correct execution state even for loops), and comprehensive save-time validation (broken workflows are refused when authored, not discovered at runtime). Expression errors now fail the node and route to its error edge across all four processors, providing authors a predictable recovery path.

Deliverables

The specification registry documents 247 rules across runtime execution, workflow grammar, and API contracts. All testable rules are covered by binding tests, with 11 structural or cross-reference entries completing the set. A companion issue cleaned legacy surfaces (unused endpoints, deprecated methods, and misleading metrics) from the 2.x branch. Validation now refuses 13 structural defects at save time, including missing plugins, hidden-port wiring, duplicate edges, self-edges, malformed expressions, and oversized payloads. Error handling, cancellation, and resume behaviour now behave identically across all runners, and status payloads have been standardised for editor consumption.

Risks

No blocking issues for a stable release were introduced during this period. The work closed long-standing inconsistencies and undocumented behaviour, reducing the surface area for runtime surprises. Future changes to validated behaviour will be visible in the specification registry, making impact assessment straightforward.

How can I help on this project?

Advocate the specification registry approach to other Drupal projects managing complex runtime behaviour, positioning FlowDrop's documentation model as a reference.

Coordinate a stable 2.x release now that the runtime contracts are explicit and tested, unlocking production adoption.

---
AG-UI

The AG-UI module saw significant progress in security, quality assurance, and user experience over the past 24 hours, with four key pieces of work delivered.

A new character limit configuration was merged to help prevent token exhaustion attacks. Site administrators can now set maximum message lengths; users who exceed the limit will receive a clear message and their requests will be blocked before reaching the AI service. This adds a layer of cost control and abuse prevention.

Error handling in the chat interface was improved so that when something goes wrong, users now see friendly, concise error messages instead of raw technical output cluttering the conversation.

The module now supports token-based authentication for anonymous users, allowing public-facing AI assistants to be deployed while reducing the risk of abuse from automated scripts.

Finally, automated testing and continuous integration were enabled, establishing a quality gate for all future changes. The pipeline now runs coding standards checks, static analysis, and automated tests on every contribution.

How can I help on this project?

Prioritise a decision on release timeline and readiness criteria for a stable 1.0 version to guide remaining feature and documentation work.

Consider allocating design or UX resources to review the chat interface and error messaging for accessibility and usability.

Contributors: Ahmad Khalil (ahmad-khalil-imagex) [1], Bryan Sharpe (b_sharpe) [3]
======================================================================== ## [25] factcheck:capabilities:executive ======================================================================== Layer-1 corrections: 0 Judge flags: 3