Upgrade to Gradio 5 to resolve aiofiles conflict with crewai

gradio 4.44 caps aiofiles<24 but crewai 1.14 pins aiofiles~=24.1, which
blocked the HF Space from resolving requirements. Gradio 5 dropped the
cap, and all 47 frontend tests pass under gradio 5.50.

README.md

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

requirements.txt

@@ -2,10 +2,13 @@
 #
 # This file is consumed by the Space builder and installs into a CPU-only
 # environment (the GPU inference runs elsewhere on AMD Developer Cloud).
-# Pins here should stay tight to avoid drifting into incompatible combinations.
+# Pins here stay tight where they matter and relax where the resolver
+# needs room (notably gradio vs crewai on aiofiles).
 
-# Gradio frontend framework
-gradio==4.44.1
+# 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
 
 # Agent orchestration
 crewai==1.14.4
@@ -19,5 +22,5 @@ pandas-ta-remake==1.0.4
 # pandas-ta-remake 1.0.4 still imports pkg_resources; Setuptools >=81 removed it.
 setuptools<81
 
-# Tokenizers 0.20.x lacks DecodeStream on Py3.13; crewai needs >=0.21.
+# Tokenizers 0.20.x lacks DecodeStream on Python 3.13; crewai needs >=0.21.
 tokenizers>=0.21,<1