Dart 3.9 / Flutter 3.35 [first LLM release] (#2714)

I got carried away with Gemini and basically rewrote CI and the release
process for the new LLM reality. This work was largely completed by
Gemini.

- Bump all SDK versions to the current beta (3.9.0-0)
- Run `flutter channel beta`
- Wrote `ci_script.dart` to replace the bash scripts
- Converted repository to pub workspace #2499 
- Added llm.md and release.md
- Added redirect for deprecated Samples Index

## Pre-launch Checklist

- [x] I read the [Flutter Style Guide] _recently_, and have followed its
advice.
- [x] I signed the [CLA].
- [x] I read the [Contributors Guide].
- [x] I have added sample code updates to the [changelog].
- [x] I updated/added relevant documentation (doc comments with `///`).

Author: ericwindmill

.gemini/settings.json

@@ -0,0 +1,11 @@
+{
+  "mcpServers": {
+    "dart": {
+      "command": "dart",
+      "args": [
+        "mcp-server"
+      ]
+    }
+  },
+  "contextFileName": "/.prompts/llm.md"
+}

.github/workflows/beta.yml

@@ -15,10 +15,10 @@ defaults:
     shell: bash
 
 jobs:
-  # Run the stable test script on the beta channel. Since this branch will soon
-  # be merged into main as our stable-targeting code, this is the key thing we
-  # need to test.
-  stable-tests-on-beta:
+  # Test all samples on the beta channel. Since the beta channel will soon be
+  # promoted to stable, this branch is only concerned with the beta.
+  Beta-CI:
+    name: Test flutter beta channel
     runs-on: ${{ matrix.os }}
     if: github.repository == 'flutter/samples'
     strategy:
@@ -34,7 +34,7 @@ jobs:
       - uses: subosito/flutter-action@e938fdf56512cc96ef2f93601a5a40bde3801046
         with:
           channel: beta
-      - run: ./tool/flutter_ci_script_stable.sh
+      - run: flutter pub get && dart tool/ci_script.dart
 
   # Verify the Android add-to-app samples build and pass tests with the beta
   # channel.
@@ -54,16 +54,16 @@ jobs:
 
   # Verify the iOS add-to-app samples build and pass tests with the beta
   # channel.
-  ios-build:
-    runs-on: macos-latest
-    if: github.repository == 'flutter/samples'
-    steps:
-      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
-      - uses: actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00
-        with:
-          distribution: 'zulu'
-          java-version: '17'
-      - uses: subosito/flutter-action@e938fdf56512cc96ef2f93601a5a40bde3801046
-        with:
-          channel: beta
-      - run: ./tool/ios_ci_script.sh
+  # ios-build:
+  #   runs-on: macos-latest
+  #   if: github.repository == 'flutter/samples'
+  #   steps:
+  #     - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
+  #     - uses: actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00
+  #       with:
+  #         distribution: 'zulu'
+  #         java-version: '17'
+  #     - uses: subosito/flutter-action@e938fdf56512cc96ef2f93601a5a40bde3801046
+  #       with:
+  #         channel: beta
+  #     - run: ./tool/ios_ci_script.sh

.github/workflows/main.yml

@@ -24,7 +24,7 @@ jobs:
     strategy:
       fail-fast: false
       matrix:
-        flutter_version: [stable, beta, master]
+        flutter_version: [stable, beta]
         os: [ubuntu-latest, macos-latest, windows-latest]
     steps:
       - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
@@ -35,7 +35,7 @@ jobs:
       - uses: subosito/flutter-action@e938fdf56512cc96ef2f93601a5a40bde3801046
         with:
           channel: ${{ matrix.flutter_version }}
-      - run: ./tool/flutter_ci_script_${{ matrix.flutter_version }}.sh
+      - run: flutter pub get && dart tool/ci_script.dart
 
   # android-build:
   #   runs-on: ubuntu-latest
@@ -51,16 +51,16 @@ jobs:
   #         channel: stable
   #     - run: ./tool/android_ci_script.sh
 
-  ios-build:
-    runs-on: macos-latest
-    if: github.repository == 'flutter/samples'
-    steps:
-      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
-      - uses: actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00
-        with:
-          distribution: 'zulu'
-          java-version: '17'
-      - uses: subosito/flutter-action@e938fdf56512cc96ef2f93601a5a40bde3801046
-        with:
-          channel: stable
-      - run: ./tool/ios_ci_script.sh
+  # ios-build:
+  #   runs-on: macos-latest
+  #   if: github.repository == 'flutter/samples'
+  #   steps:
+  #     - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
+  #     - uses: actions/setup-java@c5195efecf7bdfc987ee8bae7a71cb8b11521c00
+  #       with:
+  #         distribution: 'zulu'
+  #         java-version: '17'
+  #     - uses: subosito/flutter-action@e938fdf56512cc96ef2f93601a5a40bde3801046
+  #       with:
+  #         channel: stable
+  #     - run: ./tool/ios_ci_script.sh

.gitignore

@@ -27,6 +27,7 @@
 .pub-cache/
 .pub/
 /build/
+**/build/
 
 # Android related
 **/gradle-wrapper.jar
@@ -81,3 +82,6 @@ yarn.lock
 !**/ios/**/default.pbxuser
 !**/ios/**/default.perspectivev3
 !/packages/flutter_tools/test/data/dart_dependencies_test/**/.packages
+
+.claude/
+logs/

.prompts/code_freshness.md

@@ -0,0 +1,63 @@
+# Code Health and Style Guide Analysis
+
+This document provides instructions for an AI assistant to analyze this repository against the Dart and Flutter style guide (`.prompts/llm.md`) and log opportunities for improvement.
+
+## Workflow
+
+The AI assistant must follow these steps exactly:
+
+### 1. Setup
+
+1.  **Create Log Directory**: If it does not already exist, create a directory named `logs` in the repository root.
+2.  **Create Log File**: Create a new file inside the `logs` directory named `YYYY-MM-DD_HH-MM-SS-freshness-scores.md`, where `YYYY-MM-DD_HH-MM-SS` is the current timestamp.
+
+### 2. Project Identification
+
+1.  **Find Projects**: Identify all sample projects by searching for `pubspec.yaml` files within the repository. Each directory containing a `pubspec.yaml` should be considered a separate project.
+2.  **Create a Queue**: Compile a list of the absolute paths to these project directories to process them one by one.
+
+### 3. Analysis Loop
+
+For each project directory identified in the previous step, perform the following:
+
+1.  **Check for Dart Files**:
+    *   Verify that the project directory contains at least one `.dart` file.
+    *   If not, add an entry to the log file stating that the project was skipped for this reason and proceed to the next project.
+
+2.  **Analyze Git History**:
+    *   Run `git log` to find the most recent commit to a `.dart` file within that project's directory made by a human (i.e., not a bot).
+    *   **Command**:
+        ```bash
+        git log -1 --author='^(?!.*bot).*$' --pretty="format:%ad" --date=short -- ./**/*.dart
+        ```
+        *(Note: This command should be run from within the project's directory).*
+    *   **Handle No Commits**: If the command returns no output, note "No human commits found" for the log. If there are no commits at all, note that as well.
+
+3.  **Read and Assess Code**:
+    *   Read all `.dart` files within the project directory (recursively).
+    *   Compare the code against the rules and patterns defined in `.prompts/llm.md`.
+    *   The assessment must focus on:
+        *   Code organization and structure.
+        *   Adherence to naming conventions.
+        *   Proper use of Flutter and Dart patterns (e.g., `const` constructors, collection literals).
+        *   State management best practices.
+        *   Clarity, readability, and documentation.
+
+4.  **Log Findings**:
+    *   Append a new entry to the log file using the following Markdown template. Ensure all fields are filled out.
+
+    ```markdown
+    ---
+    **Sample**: `path/to/sample`
+    **Last Human Commit**: `YYYY-MM-DD` or "No human commits found"
+    **Assessment Date**: `YYYY-MM-DD`
+
+    **Summary of Style Guide Adherence**:
+    A brief, one-paragraph summary of how well the project adheres to the style guide. Mention its strengths and weaknesses in general terms.
+
+    **Opportunities for Improvement**:
+    - A concrete, actionable bullet point describing a specific area for improvement.
+    - Another actionable bullet point.
+    - A third bullet point, if applicable. Focus on providing clear, specific, and helpful recommendations.
+    ---
+    ```