Flutter app pipelines
The published Pipelines workflows for app/, kept here so their history lives
with the code they work on. Publish a change with
pipelines validate pipelines/<file>.md then
pipelines submit pipelines/<file>.md --name "<Name>".
| Pipeline | File | One run does |
|---|---|---|
| Flutter fix | flutter-fix.md |
One behaviour or bug: Ground → Red → Code → Review → Verify → Commit |
| Flutter design | flutter-design.md |
One visual defect on one screen: Capture → Compare → Code → Recapture → UIReview → Verify → Commit |
| Flutter preview | flutter-preview.md |
Publish main to the preview: Gate → Publish → Smoke |
Running one item:
- From the repository root,
git worktree add -b flutter/<slug> tmp/flutter-<slug> mainandflutter pub getin itsapp/. pipelines run "Flutter fix" --workspace tmp/flutter-<slug>/app --prompt "<one behaviour, with what you already know>". Flutter design takes the screen and its routes; Flutter preview runs in the main checkout'sapp/and takes a short name for the rollback directory.- A run ends with a local commit on its branch. The manager reads the diff,
merges the branch into main with
--no-ff, runssh tool/check_full.shon main, and publishes with Flutter preview.
Every stage runs on openai/gpt-6-luna (app/AGENTS.md). Stages share the repository's
own tools: tool/check_full.sh (analyze plus the full suite, passing only on
All tests passed!), tool/shoot_real_app.mjs (phone and desktop captures of the
real app against the loopback fixture) and tool/publish_preview.sh (build, then
swap build/web by rename with a rollback directory). No stage restarts a server,
uses the shared Pipelines server for captures, uses git stash, or adds AI
attribution to commits.