Bump gradio to 6.x to fully resolve aiofiles conflict

gradio 5.x still caps aiofiles<24 in its metadata; only gradio 6
dropped the aiofiles dependency entirely. crewai 1.14 stays at the
declared aiofiles~=24.1 pin. The app and frontend tests pass under
gradio 6.14 with no code changes required.

README.md

@@ -4,7 +4,7 @@ emoji: 🤖
 colorFrom: green
 colorTo: blue
 sdk: gradio
-sdk_version: 5.1.0
+sdk_version: 6.14.0
 app_file: app.py
 pinned: false
 license: mit

requirements.txt

@@ -5,10 +5,11 @@
 # Pins here stay tight where they matter and relax where the resolver
 # needs room (notably gradio vs crewai on aiofiles).
 
-# Gradio frontend framework. Pinned to 5.x because 4.44 caps aiofiles<24
-# and crewai 1.14 pins aiofiles~=24.1 — the two are resolver-incompatible
-# in a single environment.
-gradio>=5.0,<6
+# Gradio frontend framework. Pinned to 6.x because gradio 4.44 / 5.x cap
+# aiofiles<24 while crewai 1.14 pins aiofiles~=24.1 — they are
+# resolver-incompatible. Gradio 6 dropped the aiofiles dependency
+# entirely so both packages can coexist.
+gradio>=6.0,<7
 
 # Agent orchestration
 crewai==1.14.4