feat: Add version detection warnings for hot reload

commands/create-app.toml

@@ -86,6 +86,7 @@ The implementation plan should specify after each phase that you should:
 - [ ] Use `git diff` to verify the changes that have been made, and create a suitable commit message for any changes, following any guidelines you have about commit messages. Be sure to properly escape dollar signs and backticks, and present the change message to the user for approval.
 - [ ] Wait for approval. Don't commit the changes or move on to the next phase of implementation until the user approves the commit.
 - [ ] After commiting the change, if the app is running, use the hot_reload tool to reload it.
+  - Hot reload only works reliably on Flutter at versions at or above 3.37.0. If hot_reload fails, and they are using a version below that, inform the user and suggest either switching to the Flutter main channel or manually reloading the app.
 
 In the last phase of the plan, include steps to:
 

commands/debug-app.toml

@@ -34,6 +34,7 @@ Next, collect additional information required for debugging. Ask the user one qu
 Before diving into the code, let's verify the project's dependencies and environment.
 
 - [ ] Run `flutter doctor` to get the Flutter and Dart SDK versions and check for any issues reported.
+  - Hot reload only works reliably on Flutter at versions at or above 3.37.0. If hot_reload fails, and they are using a version below that, inform the user and suggest either switching to the Flutter main channel or manually reloading the app.
 - [ ] Use the `pub` tool with the `outdated` command to look for outdated packages or dependency conflicts in `pubspec.yaml` and `pubspec.lock`.
   - Run the command `pub` tool with `upgrade` to upgrade to latest versions.
   - If that isn't sufficient, sometimes upgrading the package version to a new major version can help. The `pub` tool can't do this, so run the command `dart pub upgrade --major-versions` to do this.
@@ -62,7 +63,9 @@ The debugging strategy should be chosen to yield the best results and may involv
 
 - **Logging and Tracing:**
   - Add strategic logging statements to the code to trace execution flow. Prefer `debugPrint()` over `print()` for cleaner, non-interfering output.
-  - Use `hot_reload` to apply logging changes quickly while preserving the app's state. If the state needs to be reset, explain that a Hot Restart is needed, and you will need to stop and restart the app.
+  - Use `hot_reload` to apply logging changes quickly while preserving the app's state.
+    - Hot reload only works reliably on Flutter at versions at or above 3.37.0. If hot_reload fails, and they are using a version below that, inform the user and suggest either switching to the Flutter main channel or manually reloading the app.
+  - If the state needs to be reset, explain that a Hot Restart is needed, and you will need to stop and restart the app.
 
 - **Flutter DevTools & UI Inspection:**
   - **For UI and layout bugs:** Use the `get_widget_tree` tool to inspect the widget hierarchy and properties.

commands/modify.toml

@@ -73,6 +73,7 @@ The implementation plan should specify after each phase that you should:
 - [ ] Use `git diff` to verify the changes that have been made, and create a suitable commit message for any changes, following any guidelines you have about commit messages. Be sure to properly escape dollar signs and backticks, and present the change message to the user for approval.
 - [ ] Wait for approval. Don't commit the changes or move on to the next phase of implementation until the user approves the commit.
 - [ ] After commiting the change, if an app is running, use the hot_reload tool to reload it.
+  - Hot reload only works reliably on Flutter at versions at or above 3.37.0. If hot_reload fails, and they are using a version below that, inform the user and suggest either switching to the Flutter main channel or manually reloading the app.
 
 In the last phase of the plan, include steps to:
 

flutter.md

@@ -816,6 +816,13 @@ education levels, and learning styles.
 
   PLEASE. DON'T FORGET TO USE THE DART TOOLS. I BEG YOU.
 
+- **Running Apps**: If the user asks to "run the app" or "start the app" and the
+  `launch_app` tool is not available or fails, provide clear guidance:
+
+  > "To run your app, open a new terminal, cd into your project directory, and
+  > type `flutter run`. Or, open your IDE and use its Run features via the
+  > Flutter extension or plugin."
+
 - **PREREQUISITES**:
   - Before calling tools which operate on the project, you must use the
     `create_project` tool to create a project if it doesn't already exist.