Files
pipelines/app/WORK.md
T

2.0 KiB

Flutter delivery queue

Behavioral parity with the existing web app, native controls, web-only testing. All work under app/. Existing applications remain running and unchanged.

First wave (independent worktrees, Task v6, Luna for every stage)

Item Scope Source Verification Landing Preview
F0 Scaffold and gateway contract ready pending pending not served
F1 Socket transport, endpoint rules, reconnect queued pending pending —
F2 Adaptive shell and standard platform controls queued pending pending pending
F3 Run models, live event fold, actions queued pending pending —
F4 Chat models, history/live fold, request facade queued pending pending —

Next ready work

  • P1 pipelines list/detail/source/version; P2 graph and stage/visit selection.
  • R1 runs list/detail/timeline; R2 decisions/run/retry/cancel/title and attention.
  • C1 chat list/group/search/star/rename/close/create; C2 transcript/markdown/reasoning/tools; C3 composer/attachments/queue/stop; C4 forms/permissions/models/metrics/shells.
  • A1 artifact gallery/preview/share/download; D1 diff viewer.
  • S1 schedules and provenance; T1 templates/create/validate/submit.
  • X1 search; N1 settings/persistence/notifications; I1 routes/deep links and integration.

F1 + F2 unlock live preview and feature screens. F3/F4 unlock runs/chat UI. Parallel tasks own separate feature subdirectories and tests. Manager owns main, shell registration, pubspec, this queue and integration. Small shared-file edits are resolved at landing, not used to serialize independent features.

Completion loop

Use pipelines wait for every started run. Inspect failure evidence before fixing, resuming or retrying; preserve partial work. On success inspect actual diff and checks, integrate, verify ancestry, then launch the next ready item. Do not rerun completed work just because session export or landing failed. Keep source, tests, landing and preview states separate. No production cutover in this phase.