docs: remove holiday reporting operations

AGENTS.md

@@ -30,7 +30,6 @@ This repository owns deployment concerns only. Backend and frontend directories
 - Everything runs through Docker, Docker Compose, Bash scripts, and environment files/templates.
 - The CSV-to-PostgreSQL workflow is a one-time administrative bootstrap/recovery command, never a scheduled ingestion service. ZarinPal owns future production payment writes.
 - The analytics refresh worker is not an ingestion service: it derives projections from normalized PostgreSQL changes, publishes within 15 minutes, and performs an idempotent nightly reconciliation. Deployment must surface failed/stale refreshes and must not advance freshness on failure.
-- Reviewed yearly Iranian calendar snapshots are versioned backend reference data and loaded into PostgreSQL; production containers must not depend on a runtime calendar API.
 - Nginx is the only public entry point. PostgreSQL and internal services are not internet-exposed.
 - Health checks distinguish liveness from readiness.
 - Backups are encrypted where supported, validated, retention-aware, and paired with rehearsed restores.

CAPABILITY-MAP.md

@@ -49,7 +49,7 @@ Build sequence: data foundation → identity and analytics → API → dashboard
 7. External calls have timeouts and bounded retries; jobs are idempotent and observable.
 8. Production changes are reversible and backed by documented health checks and rollback steps.
 9. Only `Verified` is a confirmed successful session; `Paid` remains a separately reported state until an approved metric-catalogue revision says otherwise.
-10. Iranian official holidays come from reviewed, versioned annual calendar snapshots; broader analytical event windows are explicitly labeled and versioned.
+10. MVP reporting periods are limited to daily, weekly, Jalali-month, and Persian-season views with consistent boundaries across database, API, and frontend.
 
 ## Required capability specs