Track latest flutterflow_cli; refresh build skill for SDK 0.0.41 (v0.1.7)

[johnbhiggins7]

Why

New plugin users can't create a workspace right now. The hook pins flutterflow_cli 0.0.38, but flutterflow ai init always downloads the latest FlutterFlow AI SDK, and SDK 0.0.41 (released 2026-09-23) requires CLI ≥ 0.0.41. Reproduced in a sandbox:

Downloading FlutterFlow AI SDK (prod, build 9e246f84)...
This FlutterFlow AI snapshot requires flutterflow_cli >= 0.0.41, but you are running 0.0.38.

With CLI 0.0.41 the same init gets past the SDK download (it stops only at the missing API key, as expected in the sandbox).

What changed

SessionStart hook: tracks the latest CLI instead of a pin

• A fresh install gets the latest flutterflow_cli.
• For an existing install, the hook reads the installed version from the pub-global lockfile. At most once every 6h it checks pub.dev (3s timeout, silent when offline) and runs dart pub global activate flutterflow_cli <latest> if a newer release exists.
• It never downgrades, skips path/git activations (dev checkouts), and only accepts a plain X.Y.Z from pub.dev.
• New tests fake pub.dev and dart, covering older, equal, and newer versions, path source, no lockfile, offline, and a malformed response. The existing tests now isolate PUB_CACHE so they never see the runner's real CLI.

Build skill (SKILL.md)

• Removed the flutterflow ai projects --json step from 0.1.6. No released CLI/SDK has that command (checked through 0.0.41 and beta 0.0.41+1), so the skill asks for the project URL instead.
• Added a "CLI is too old" recovery section.
• Added the 0.0.41 page-file edit workflow (init --page-dsl, orient → edit → run --dry-run → run, scaffold edit) and the new orient, review, assets, and scaffold commands.
• New gotchas:
  • the Supabase/Postgres list/detail validation gap from [SDK 0.0.39] Postgres/Supabase READ patterns fail validation (writes work) — Firestore equivalent works #1, with the workaround
  • MCP commit tools require userPrompts, which are stored server-side, so no secrets

README / CHANGELOG / version

• The README documents the upgrade behavior and what the CLI sends (installation ID with its opt-out, AI commit attribution, MCP prompts).
• Added a CHANGELOG entry and bumped the version to 0.1.7.

Tradeoff

New flutterflow_cli releases reach plugin users within about 6h with no review step, which the old pin was meant to prevent. Since it's FlutterFlow's own package, staying in sync with the SDK's minimum CLI seemed more important.

Testing

• session-start.test.sh and store-key-from-clipboard.test.sh pass
• claude plugin validate ./plugins/flutterflow --strict passes; shellcheck is clean
• The pub.dev lookup, run against the live API, returns 0.0.41 in about 0.2s

🤖 Generated with Claude Code