flowdrop 1.5.0

[1.5.0] - 2026-05-27

Added

• Pipeline lineage — parent_pipeline_id / root_pipeline_id (flowdrop_pipeline): FlowDropPipeline now records its parentage. parent_pipeline_id is NULL for a top-level run and points at the spawning pipeline for a nested (shared-session sub-workflow) run; root_pipeline_id is the top of the chain and is always populated — a root pipeline self-roots to its own id in postSave() (a single-column write on insert, so no save-recursion and no COALESCE at read time), and a nested run inherits its parent's root. Installed and backfilled (root = id for existing rows, in a batched sandbox update) by flowdrop_pipeline_update_10003.
• rootPipelineId / parentPipelineId on playground messages (flowdrop_session, flowdrop_playground): Every message returned by the playground message endpoints now carries the root and parent pipeline ids of the run that produced it, so messages from a single conversational turn — including those emitted by nested sub-workflows — can be correlated to their top-level run. Resolved via the new flowdrop_pipeline-owned PipelineLineageResolver (numeric-filtered, existence-checked and session-scoped, so a generic/external execution_id cannot false-match), batched to one query per session in SessionService::formatMessagesForApi(). Matches the existing @flowdrop/flowdrop PlaygroundMessage contract. Additive — executionId is unchanged.

Fixes

• #3592069: Fix regression in playground mode where Status of the pipeline is not being reported at all