Workflow Builder edit request:
- Plan: {{ .PlanID }}
- Base draft revision: {{ .BaseDraftRevision }}
- Context target: {{ .TargetLabel }}
{{ if .Diagnostics }}- Diagnostics:
{{ range .Diagnostics }}  - {{ .Severity }}{{ if .Code }} · {{ .Code }}{{ end }}{{ if .Path }} · {{ .Path }}{{ end }}{{ if .Location }} · {{ .Location }}{{ end }}{{ if .Message }}: {{ .Message }}{{ end }}
{{ end }}{{ else }}- Diagnostics: none.
{{ end }}{{ if .AdditionalDiagnostics }}  - … {{ .AdditionalDiagnostics }} additional diagnostics omitted
{{ end }}

The target is context, not a write boundary. Inspect and edit the current Draft through loop exec workflow plan using these existing actions:
- workflow plan show
- workflow plan validate
- workflow plan update

Perform at most one changed update, and it must use expectedRevision={{ .BaseDraftRevision }}. If that update conflicts or fails, do not reload, rebase, or attempt another changed update for this request. Do not publish, submit, archive, create a Binding, or start a Run for this request. If you omit layout, the server preserves the saved layout. A failing workflow command prints a structured error envelope as JSON on stderr; act on its "code", "stage", "path", and "diagnostics", retry the exact same call only when the envelope declares "retryable: true", and reuse the exact same "idempotencyKey" for that retry. Do not send an acknowledgement or progress message: the first reply ends this edit request. Reply to this exact Workflow target with message_send only after the edit succeeds, or once if you need to explain a failure.

Write your reply for a non-technical user. Describe what you changed in plain terms the user asked for ("I'll send a reminder to the engineering channel when the request is approved") and confirm the workflow is now set up to do that. Do not include node ids, revision numbers, compiler diagnostics, plan terminology, or YAML/code snippets unless the user explicitly asked. The goal is that the user feels the workflow is configured to do what they wanted, not that they have to read code to verify it.