Phase out reconciliation in views-reporting (closes views-reporting#72)

[Polichinel]

Epic: #31 · Depends on: #39 · Cross-repo (views-reporting) · closes views-reporting#72

Background

Only once views-postprocessing reconciliation is live in production (#39) is it safe to remove the views-reporting copy. This is the step that finally deletes torch from views-reporting (their register C-24).

Work

• Remove from views-reporting: views_reporting/reconciliation/, ForecastReconciler (in statistics.py), dataset_export.py, and the now-orphaned reconciliation-only metadata helpers.
• Drop the torch dependency there; update its docs/register; close views-reporting#72 with a pointer to the views-postprocessing home.

Acceptance criteria

• views-reporting has no reconciliation code and no torch dependency; its test suite passes.
• views-reporting#72 closed, pointing here.

Blocked by

• Wiring: expose reconciliation API + pipeline-core ensemble repoint #39 — must be live in production first.
• ⚠️ Do not start until Wiring: expose reconciliation API + pipeline-core ensemble repoint #39 is merged and running. Until then views-reporting is the parity oracle and must stay frozen (the whole epic relies on it being unchanged).

[Polichinel]

Update 2026-06-24 — removal scope confirmed.

Removing reconciliation from views-reporting = delete the reconciliation/ package and ForecastReconciler (in statistics/statistics.py); torch leaves cleanly (it is reconciliation-only in views-reporting — verified). Triggered once both point consumers (ensemble.py, dataframe_ensemble.py) are repointed (#39). The probabilistic-PFE work (B2) is additive and not a blocker for this removal.