Files
pipelines/app/WORK.md
T

2.7 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 0e0ef54 analyze + 1 scaffold test pass main not served
F1 Socket transport, endpoint rules, reconnect run 24 / flutter/f1-transport running pending —
F2 Adaptive shell and standard platform controls run 25 / flutter/f2-shell running pending pending
F3 Run models, live event fold, actions run 26 / flutter/f3-runs running pending —
F4 Chat models, history/live fold, request facade run 27 / flutter/f4-chat running pending —
F5 Isolated authenticated web preview tooling run 28 / flutter/f5-preview running 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. F5 provides a separate authenticated preview URL, without production changes. 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.

Each run pins Task v6 with a whole-run openai/gpt-6-luna override (all four stages), app-only write scope, its own worktree under tmp/flutter-fN, and an individual background pipelines wait. No workflow definitions were modified. The CLI reports a client/server build mismatch; admission succeeded and the server echoed the expected model/scope. No shared service was rebuilt/restarted.

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.