Files

Flutter app workflows

Use the registered Mobile pipeline for one app behaviour, bug or visual change. Its current flow prepares the worktree, implements the change, reviews the diff, reviews rendered UI when affected, and commits a candidate for the server's delivery checks and landing gate.

Inspect the live definition before a run; the server's registered version is authoritative:

pipelines list
pipelines show Mobile

Run one item in its own repository-root worktree (not inside app/), keeping other worktrees available for independent work:

git worktree add -b flutter/<slug> tmp/flutter-<slug> main
cd tmp/flutter-<slug>
(cd app && /Users/alan/development/flutter/bin/flutter pub get)
pipelines run Mobile "<one observable change and its acceptance criteria>"

Use Luna for pipeline stages unless the user requests another model. Verify the exact provider/model in pipelines show Mobile; do not copy model IDs from the old files here. Put task-specific requirements in the run prompt. Creating or publishing a workflow version requires an explicit pipeline-change request.

For evidence and recovery, use pipelines inspect <run-id> --json. A failed run keeps its branch and edits; inspect those before retrying or taking over. A successful model stage is not proof of landing: verify the delivery-check results and main's ancestry after the server's landing gate finishes. App change is the separate Caplens workflow; it is not the Flutter client workflow.

Verification and delivery

From app/, use tool/memwatch/full.sh test/<area> and tool/analyze.sh <changed paths> while editing. For integrated acceptance, sh tool/check_full.sh runs bounded analysis followed by the full suite through the memory watchdog. It fails on the actual command exit status and records wrapper summaries under build/check/. Never run a bare flutter test.

Rendered changes also need interaction and inspected captures with tool/capture/ (see its README); test-device requirements are in app/AGENTS.md. Code, checks, landing, publication and device installation are separate steps. Publish only when requested, preserve a rollback, and do not restart shared services over active work. tool/publish_preview.sh updates the checkout preview; the installed web root uses the installation's delivery path. APK publication uses tool/publish_apk.sh or the installation's --apk flow.

Historical definitions

flutter-fix.md, flutter-design.md and flutter-preview.md preserve earlier workflow definitions. They are not the current registered Mobile definition and must not be submitted just to start or repair an ordinary run. In particular, their names, model IDs, prompts and manual verification steps may be stale.