Initial commit: astrape-oracle split out of the combined Astrape tree

The forecasting runtime gibil pilots: weather ingest (Open-Meteo
forecasts and the Ecowitt station), the oracle and weather stores, the
snapshot daemon, the forecast evaluator, and the TCN training
scheduler.

classes/datasets.py holds the shapes the stores return for display.
They sit beside the stores deliberately: a store's return type belongs
to the store, and keeping them with the renderers would mean this repo
importing the dashboard, which is backwards.

Extracted from a single repository where the forecasting engine, the
database plumbing, the hardware client, the ingest daemons and the web
UI all imported each other freely. Verified that every module imports
with gibil resolved from its own installed checkout.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

astrape_oracle/classes/datasets.py

@@ -0,0 +1,28 @@
+"""Shapes the stores return for display.
+
+These live beside the stores rather than beside the renderers on purpose. A
+store's return type belongs to the store: putting them in the dashboard would
+mean astrape-oracle importing astrape-dashboard, which is backwards -- the
+dashboard reads from the oracle, never the other way round.
+"""
+
+from __future__ import annotations
+
+from dataclasses import dataclass
+
+from gibil.classes.models import (
+    WeatherForecastPoint,
+    WeatherResolvedTruth,
+    WeatherStationObservation,
+)
+
+
+@dataclass(frozen=True)
+class WeatherDisplayDataset:
+    forecast_points: list[WeatherForecastPoint]
+    resolved_truth: list[WeatherResolvedTruth]
+
+
+@dataclass(frozen=True)
+class WeatherStationDisplayDataset:
+    observations: list[WeatherStationObservation]