festival-engine-v2.0.2Security- Credentials moved out of source and into environment configuration.
- Administrative PIN rotated.
- Test suite expanded to 152 tests; coverage re-measured honestly at 91%.
Changelog
What changed, and when
Rule corrections appear here alongside code changes, because a rule change can move a festival date without altering a single line of the API contract.
festival-engine-v2.0.0Engine- Festival determination moved to shastric kala-vyapini rules over real tithi intervals.
- Nine evaluators with an auto-registering registry; TieBreakEngine with kshaya and vriddhi handling.
- Rule versioning with a DRAFT to ARCHIVED lifecycle and shastric authority metadata.
- Observatory mode and per-festival confidence scores.
- Series resolution for the Diwali cluster, Navratri and Holi.
- Corrected Diwali, Janmashtami, Ganesh Chaturthi, Vijayadashami, Maha Shivaratri and Holi.
- Abhijit Muhurat is no longer suppressed by Rahu, Yamaganda or Gulika overlap.
Milestones
The longer arc
Verification frameworkExecution engine, comparison policies, adapter registry, external benchmark.
Security hardeningCredentials moved to environment, secrets rotated, 152 tests at 91% coverage.
Platform alignmentTier enforcement, webhook platform, plans and billing, analytics.
Festival Engine V2 — cutoverTier A/B/C validation, shadow mode, production cutover.
Festival Engine V2 — coreKalaCalculator, nine evaluators, TieBreakEngine, rule versioning, schema migration.
AstrologyBirth chart, Guna Milan compatibility, PDF reports, matchmaking engine.
Auth and usageJWT auth, API key management, plan-based rate limiting, usage tracking.
FoundationInitial API surface, panchang data import across 14 cities.