Give a rate-limit flush its own run, linked to the run that held the value

A flush ran its cascade under no id, so its executions and failures belonged
to no run. It now records a run with source "flush", and the holding run's id
travels on the queue item into a new `flow_run.parent` column, also on the
`/observability/runs` rows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WgBfkm4rCmtd1T4vHWjEPx
This commit is contained in:
2026-10-15 09:37:30 +02:00
co-authored by Claude Opus 5.5
parent c7e38a8a44
commit 13567f8990
10 changed files with 157 additions and 26 deletions
@@ -85,6 +85,8 @@ class RunRow(BaseModel):
id: str
flow: str
source: str
#: The run this one continues: for a flush, the run whose value it released.
parent: str = ""
status: str
started_at: datetime
finished_at: datetime | None = None