3 commits

Author	SHA1	Message	Date
Light1YT	579ad54202	feat(export): compact Telegram summary export for §22 forecast (#959) ... render_report_telegram_summary (pure, no new deps, DRY-reuses report_pdf str helpers) + `tg` format on GET /{cad}/forecast/export → inline text/plain snippet (no attachment, copy-paste-ready). md/json unchanged; no-run 404, bad format 422. Graceful on thin/empty reports. Part of EPIC #959.	2026-06-06 18:55:47 +00:00
Light1YT	25f7052084	feat(export): Markdown + JSON download of §22 forecast report (#959) ... render_report_markdown (pure, no new runtime deps) reuses report_pdf's str helpers (DRY), + GET /{cad_num}/forecast/export?format=md|json. No forecast run → 404; graceful on thin/empty reports; GFM-safe table escaping. PDF/XLSX already existed; this adds the cheapest no-dep formats. Part of EPIC #959.	2026-06-06 18:39:51 +00:00
Light1YT	19584e0249	feat(parcels): wire §22 forecast into analyze endpoint (3b-ii, #995) ... Final forecast wiring — §22 reaches the API. - horizon query param on POST /{cad}/analyze ({6,12,18}, default 12; 422 before any DB/compute work otherwise). - best-effort fire-and-forget forecast_site_finder_report.delay(cad, horizon, created_by) after persist (lazy import, no api↔workers cycle); Celery/Redis down → forecast.status='unavailable', analyze still 200 (never blocks/500s). Adds additive result_payload['forecast'] = {status: pending|unavailable, horizon}. - new read-only GET /{cad}/forecast: latest schema_version='1.0' run → 200 {status:ready, run_id, created_at, report} else 202 {status:pending}; graceful on DB error (202, never 500). Mirrors fetch-status RBAC/style. Additive only — existing analyze response keys unchanged. code-review APPROVE (analyze uncrashable + additive; 422 pre-flight; GET reads '1.0' not 'analyze-1.0'). 96 api tests pass; ruff clean. Refs #995 #992 #961.	2026-06-05 09:22:57 +05:00