Add ZeroGPU compatibility marker

README.md

@@ -42,3 +42,9 @@ English, Ghanaian English, and Twi.
 - `KHAYA_API_KEY` when using hosted Khaya translation.
 
 Outputs are evaluation signals, not clinical deployment certification.
+
+## Runtime Note
+
+This demo uses cloud/API calls and CPU-side orchestration by default. It includes
+a small ZeroGPU compatibility marker for Spaces that are forced onto ZeroGPU,
+but CPU hardware is the intended runtime when available.

gmass_app.py

@@ -21,6 +21,11 @@ import pandas as pd
 import plotly.graph_objects as go
 from dotenv import load_dotenv
 
+try:
+    import spaces
+except Exception:  # pragma: no cover - spaces exists only on Hugging Face runtimes
+    spaces = None
+
 APP_DIR = Path(__file__).resolve().parent
 ROOT = APP_DIR if (APP_DIR / "configs").exists() else APP_DIR.parent
 if str(ROOT) not in sys.path:
@@ -72,6 +77,16 @@ REQUIRED_ENV_BY_MODEL = {
 DEFAULT_RESULTS_PATH = ROOT / "data" / "eval_outputs" / "combined" / "all_models_scored.jsonl"
 
 
+if spaces is not None:
+    @spaces.GPU
+    def zerogpu_compatibility_probe():
+        """Satisfy ZeroGPU startup checks; G-MASS itself uses API/CPU calls."""
+        return "ready"
+else:
+    def zerogpu_compatibility_probe():
+        return "ready"
+
+
 def _error(message: str) -> str:
     return (
         "<div class='gmass-error'>"

requirements.txt

@@ -16,3 +16,4 @@ rich==13.7.1
 jinja2==3.1.4
 gradio==5.23.1
 plotly==5.22.0
+spaces==0.51.1