Use the official Flutter SDK pinned in pubspec.yaml (3.47.5) on PATH.
BusyMark does not build or select a custom engine or GTK runtime.
flutter pub get --enforce-lockfile
flutter run -d linux
flutter run -d linux --profile
flutter run -d linux --release
flutter build linux --debug
flutter build linux --profile
flutter build linux --release
flutter analyze
flutter testIn Android Studio, open the repository root, configure the official Flutter SDK
pinned above, select the shared BusyMark (Linux) run configuration, and select
the Linux (desktop) device. The configuration runs lib/main.dart with
--device-id=linux. BusyMark has no Android application module; Android entries
in Flutter's transitive plugin dependencies do not add an Android target.
If Flutter imports produce many missing-type errors after using a temporary SDK,
run flutter pub get --enforce-lockfile with the configured SDK, then reload the
project so the IDE refreshes its package roots. Generated .dart_tool and IDE
package metadata can otherwise retain paths to an SDK that has been removed.
CI selects the same official version. Snapcraft downloads the checksum-pinned SDK and packages its unmodified release engine. Follow the README's clean Snapcraft procedure in a disposable supported environment; do not replace an installed application for acceptance. The local scaffold repack helper is not release or confinement validation. Strict-Snap checks use the normal systemd user-session bus for launcher cgroup tracking, not a private D-Bus session. Standalone smoke checks use disposable D-Bus sessions to retire desktop helpers.
Flutter Linux automatically runs bounded GTK/WebKit, compiled visualization/PDF,
dictionary installation/offline restart, Wayland and strict-Snap build/install
checks for PRs to main and release/v0.7.0, and pushes to main. It reuses
Linux native acceptance with run-stress: false. Run that workflow manually
with run-stress enabled for hundred-close, compiled document/media and
debug/profile campaigns. See compiled application checks.
A widget-suite pass does not validate the GTK embedder.
Yaru uses the unmodified dependencies in pubspec.lock through Flutter's
generated plugin build. No local plugin source preparation is required.
Compiled window, document and media checks exercise the actual application;
runtime shutdown failures still fail native release acceptance. A disappearing
window or forced cleanup is not successful natural shutdown.
Startup resolves the GTK accent or its portal fallback before building the UI,
using the existing readiness deadline. A valid GTK accent does not wait for the
portal. Saved preferences are read once before runApp() and handed to the
settings controller; failed reads use defaults without acknowledging them as a
persisted snapshot.