Improve error messages for common setup issues

[charliewwdev]

New users sometimes hit confusing errors during setup. We should improve error messages for:

• Missing SDK integration (app not patched)
• Port already in use
• Wrong Flutter version
• Missing platform tools (Xcode, Android SDK)

What's needed: Better error messages with suggested fixes in lib/src/cli/server.dart

[tabibeyal]

While improving the error message for the SDK integration failure, I noticed that the current logic in runSetup catches only one failure case: the regex not finding void main() { in lib/main.dart.

Are there additional cases that could cause injection to fail? If so, I'd like to make sure the error message covers them as well.

[charliewwdev]

PR #19 is addressing this issue and is currently under review. Two bugs have been flagged (duplicate _checkForUpdates() call and a false-positive in the flutter doctor check). The issue will be closed once the PR is fixed and merged.

[charliewwdev]

Significantly improved in v0.9.31 🎉

New error detection in diagnose_project() and connection error messages:

Error	Detection	Actionable Steps
SDK not integrated	FlutterSkillBinding missing / method -32601	Step-by-step setup instructions
Port already in use	Address already in use / bind failed	lsof command to kill, alt ports
Wrong Flutter version	requires Flutter / SDK version mismatch	Upgrade instructions + version matrix
No devices	No connected device / flutter doctor	Simulator/AVD setup steps

Example error message when SDK is not integrated:

❌ flutter_skill SDK not integrated in the app

1. Add dependency:
   flutter pub add flutter_skill

2. Add to lib/main.dart BEFORE runApp():
   import 'package:flutter_skill/flutter_skill.dart';
   void main() {
     FlutterSkillBinding.ensureInitialized();
     runApp(MyApp());
   }

3. Hot restart (not hot reload):
   hot_restart()

Auto-fix: run  diagnose_project()  to patch automatically.

Please update to flutter_skill: ^0.9.31.