…12259)

The second `PinConfig` sample in the `BitmapDescriptor` docs (`bitmap.dart:1009`) doesn't compile, for two reasons:

1. **Unbalanced parens** — the block opens `PinConfig(`, `BitmapGlyph(` and `BitmapDescriptor.asset(` but only closes two of them. (The sibling `TextGlyph` sample directly above closes correctly.)
2. **Missing `await`** — `BitmapDescriptor.asset` is declared `static Future<AssetMapBitmap> asset(...)` (line 278), while `BitmapGlyph.bitmap` is `final BitmapDescriptor bitmap;` (line 1106), so a bare `BitmapDescriptor.asset(...)` can't be assigned to it.

The repo's own examples use the awaited form — e.g. `google_maps_flutter_web/example/latest/integration_test/advanced_markers_test.dart:422`:

```dart
bitmap: await BitmapDescriptor.asset(
```

The sample now mirrors that. Paren balance goes from 5 open / 4 close to 5 / 5.

Doc comment only; bumped to 2.16.1 with a CHANGELOG entry per the versioning policy — happy to switch to `## NEXT` if that's preferred for a docs-only change.

Adds the `triage-design` auto-labeler and changes `cupertino_ui`, `material_ui`, and related packages to be auto-labeled with `triage-design` instead of `triage-framework`. 

## Pre-Review Checklist

**Test and changelog exemption:** No changes to packages.

**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.

Export the Material tokens to `material_ui`. This PR simply exports the existing tokens from g3 to Github.

Work towards flutter/flutter#186906

## Pre-Review Checklist

**Test exemption:** All generated code.

**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.

Migrates the animations package to the material_ui package.

## Pre-Review Checklist

**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.

fixes flutter/flutter#191133
fixes flutter/flutter#191132
## Pre-Review Checklist

**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.

…12373)

`camera_android_camerax`'s Gradle module does not explicitly declare a dependency on `androidx.concurrent:concurrent-futures`. Verified via `androidx.camera:camera-core:1.6.1`'s own Gradle module metadata (`.module` file): `camera-core` declares `androidx.concurrent:concurrent-futures` only on its **runtime** variant (`releaseVariantReleaseRuntimePublication`), not its **api/compile** variant (`releaseVariantReleaseApiPublication`). So when a consumer compiles against `camera-core`, Gradle correctly does not put `concurrent-futures` on the compile classpath — that's not a resolution bug, it's what `camera-core`'s own metadata declares.

However, `camera-core`'s compiled `SurfaceRequest.class` carries a compile-time-retained jspecify `@NonNull` type annotation on a member typed `androidx.concurrent.futures.CallbackToFutureAdapter`. javac needs that class on the compile classpath to fully process the annotation metadata during compilation — even though no `camera_android_camerax` (or `camera-core`) source calls it directly. This is a mismatch in `camera-core`'s own packaging (a type needed at compile time for annotation processing, but declared runtime-only), which the Flutter team can't fix upstream since `camera-core` is owned by the AndroidX/Jetpack team. Declaring the dependency explicitly in `camera_android_camerax` works around it.

Confirmed 100% reproducible on a completely stock, uncustomized `flutter create` app on current stable (3.44.8, default AGP 9.0.1, compileSdk 37):

```
flutter create camera_repro
cd camera_repro
flutter pub add camera
flutter build apk --debug
```

fails every time with:

```
error: Cannot attach type annotations @org.jspecify.annotations.NonNull to
SurfaceRequest.mSurfaceRecreationCompleter: class file for
androidx.concurrent.futures.CallbackToFutureAdapter not found
```

Minimal repro repo (steps + README with root cause): https://github.com/dhc-tech/camera-android-camerax-build-repro

List which issues are fixed by this PR:

Fixes flutter/flutter#190505

## Pre-Review Checklist

Part of fixing flutter/flutter#183945.

Regenerating pigeon files will fix issue.

## Pre-Review Checklist

**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.

## Pre-Review Checklist

**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.

…12421)

the ink_splash is still using the flutter sdk's shader file, this pr fixes it

## Pre-Review Checklist

**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.