This file captures tasks which derive from roadmap tasks (unfinished, deferred), bugs encountered during usage and feature requests/improvements which are not fitting directly in the roadmap.
Always sort by priority and put tasks blocked by other tasks/features at the dedicated section.
When working on a task, check for other, similar tasks that could be resolved on the way.
Use following pattern to classify tasks: TYPE/SCOPE
Where TYPE could be BUG, FEAT, PERF, CHORE and SCOPE could be UX, UI, FLOW, NODE, API, INFRA, DOCS appended by MOBILE if only for mobile use case.
Don't write temporary reasons for deferring a task in the task description (only strategical reasons should be noted).
Deferring because out of scope is fine, but don't mention deferring than.

## Open

- BUG/UI: `SidePanel`'s mobile branch does not set `data-testid` on the `SheetContent`, so
  `[data-testid=node-panel]` does not exist on a phone. Mobile specs cannot address the panel.
- FEAT/UI: no way to point a node parameter at a stored secret. The store and the
  `{"$secret": "name"}` reference both work, but the params form only produces literals, so a
  webhook secret typed there lands in `flow.json`.
- FEAT/UI: flow-level edits (title, inputs) go through `FlowPanel.onChange` and stay outside
  the undo stack.
- CHORE/UI: `make test-backend` cannot reach Postgres while the integrated stack is up —
  `compose.local.yml` does `db: ports: !reset []`. Run it against the container's address, or
  move the suite inside the compose network.
- BUG/FLOW: deleting a flow leaves its state in Redis — the value, timestamp, version and
  history keys under `pipeline:{flow}.*` all survive. Clear the namespace on delete.
- CHORE/UI: the Playwright specs run against the development stack and leave their users and
  flows behind, which is why the flowbar filled with `test_flow_*`. Give them their own data
  or clean up after themselves, as `pytest` now does.
- CHORE/UI: the standalone Vite origin (`make dev-frontend` on :5173) is still not in
  `BACKEND_CORS_ORIGINS`. `scripts/setup.sh` regenerates the list on every `make init` and
  `compose.local.yml` re-declares it as a container variable that wins, so the origin has to
  be added in both places to work.
- CHORE/INFRA: `test-backend.yml` runs pytest on the runner host, so it keeps the fixed
  container name and port 5432 that `compose.ci.yml` resets everywhere else. Two concurrent
  runs of that one job collide.
- PERF/UI: (deferred for now) the Monaco chunk is 2.6 MB. It only loads when a node panel opens, but the
  editor could be trimmed further or swapped for CodeMirror if that becomes a problem.
- CHORE/FLOW: `app/flow/nodes.py` is excluded from strict mypy (`[[tool.mypy.overrides]]` in
  `pyproject.toml`). The node classes still carry prototype typing, `croniter` ships no stubs
  and `influxdb_client` does not re-export its names. Shrink it as each integration is revisited.
- PERF/FLOW: every save rebuilds the whole pipeline. Fine at the current flow count; rebuild
  only the touched flow when it starts to show.
- FEAT/UI: reintroduce `--chart-*` tokens as one designed sequential scale when the first
  chart lands. The node sparkline draws one series in `--primary` and needs none.
- PERF/UI: the app's entry chunk is 680 kB (210 kB gzipped) and exceeds the warning
  threshold. React Flow and Monaco are already lazy; a manualChunks split measured no better,
  so this needs route-level work on the shell rather than chunking config.

## Blocked

- FEAT/UI: a "Bug" icon on the node error bubble opening the console at the full error. The
  bubble now shows one line and the traceback only reaches the server log; there is no
  console in the roadmap yet for it to open.
- FEAT/INFRA: MQTT broker and InfluxDB compose services for local development. The node types
  exist; a local broker would make them testable without external hardware.
- CHORE/INFRA: `bun install` inside the frontend Docker build intermittently fails with
  "Fail extracting tarball" for several packages at once, and succeeds on a plain rebuild.
  It looks like concurrent extraction under memory pressure. Pin down or retry in the
  Dockerfile if it starts costing CI time.