handleStorageConnectionsDelete performed a hard DeleteOne with only a tenant
check, so a connection still referenced by a workflow node's connectionId could
be deleted — leaving a dangling reference that breaks workflow save/run
validation ("connectionId must reference an existing storage connection") with
no recovery path (the record is hard-deleted and unaudited). Add a reference
guard: before deleting, scan the connection's organization for workflows whose
nodes reference it; if any, return 409 Conflict listing the referencing
workflow/node ids so the caller can remove the reference first. Reuses the
existing ListAllWorkflowsByOrganization store method (no schema/interface change,
no runtime-path impact).
Co-Authored-By: Claude <noreply@anthropic.com>
Include the accumulated workflow scheduling, run history, subtree rerun, operator UI, deployment, data asset, object storage, database browser, and documentation changes currently in the worktree.