Set up Cursor Cloud dev environment

[wang-bin]

Summary

Sets up the development environment for the fvp Flutter video-player plugin so future Cloud Agents can build, run, lint, and test it. Adds an AGENTS.md with durable, non-obvious setup/run notes.

fvp is a Flutter plugin (a video_player implementation + backend player API) backed by the native libmdk/mdk-sdk SDK via Dart FFI. There is no backend service — "running" the product means running the demo app in example/.

What was provisioned

• Flutter SDK (stable, 3.44.6) at /opt/flutter, symlinked onto PATH; Linux desktop enabled.
• Linux native build toolchain: cmake, clang, ninja-build, pkg-config, libgtk-3-dev, libpulse-dev, and libstdc++-14-dev (required — clang 18 selects the GCC 14 toolchain).
• Update script: flutter pub get for the plugin and example/.

Verification

• flutter analyze — passes (info-level lints only).
• flutter build linux --debug — builds the example (downloads/links mdk-sdk).
• flutter run -d linux — runs the demo app; remote (bee.mp4) and asset (Big Buck Bunny) videos render and play/pause works.

Notes

• example/test/player_test.dart has a pre-existing failure (stale expectation: MdkVideoPlayer vs MdkVideoPlayerPlatform), unrelated to environment setup. No app code was modified.

fvp_video_playback_demo.mp4

Remote video playing
Asset video playing

_{To show artifacts inline, enable in settings.}

  

[gemini-code-assist]

Code Review

This pull request introduces a new AGENTS.md file containing Cursor Cloud-specific instructions, environment details, build commands, and known gotchas for the fvp Flutter plugin. The review feedback suggests improving the clarity of the standard test and lint commands by explicitly stating the directory context for each command to prevent automated agents from running them in the wrong directory.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

To prevent automated agents from running commands in the wrong directory, it is highly recommended to make the directory context explicit for each command. Since the previous block leaves the shell in the example directory, running flutter analyze directly will fail or analyze the wrong scope if it expects to be run from the repo root.

Consider updating this section to:

Standard test/lint commands:

# Run from repo root
flutter analyze

# Run from example directory
cd example && flutter test