Uploaded complete moirai_forecast_app contents

README.md

@@ -5,6 +5,7 @@ colorFrom: blue
 colorTo: indigo
 sdk: gradio
 sdk_version: "4.44.0"
+python_version: "3.11"
 app_file: app.py
 pinned: false
 license: cc-by-nc-4.0
@@ -99,6 +100,28 @@ needed `io.StringIO` on the sandbox's pandas 3.0.2) — left in this
 history deliberately, since "we ran it and fixed what broke" is the
 whole point of section 6 (real execution validation vs. static checks).
 
+## Real deployment history (from an actual HF Spaces build)
+
+Two real build failures happened after this was first deployed, both
+worth recording because the diagnosis process matters as much as the fix:
+
+1. **First failure**: `scipy` failed `metadata-generation-failed` while
+   building from source. I initially (and wrongly) assumed my own
+   `numpy<2.0` pin was the cause and removed it — that didn't fix it.
+2. **Real cause, found from the actual build log**: `uni2ts`'s own
+   `pyproject.toml` pins `scipy~=1.11.3` — a 2023-era release with no
+   prebuilt wheel for Python 3.13 (which is what the Space was actually
+   running, per `/usr/local/lib/python3.13/site-packages` in the log).
+   pip fell back to compiling `scipy-1.11.4.tar.gz` from source, and that
+   specific old release's build system doesn't work with the Space's
+   modern Cython/meson toolchain (`ERROR: Compiler cython cannot compile
+   programs`) — not a missing system package, a real incompatibility.
+3. **Fix**: pin `python_version: "3.11"` in this README's frontmatter
+   (a documented HF Spaces config key) so scipy 1.11.x resolves to a
+   prebuilt wheel instead of a source build. No requirements.txt change
+   was actually needed — my earlier "fix" there was chasing the wrong
+   variable, corrected here for the record rather than quietly erased.
+
 ## Architecture
 
 ```