June 2026 performance summary for nammayatri/nammayatri. Focused on increasing resilience in leg-route resolution and preserving user experience when data is incomplete. Implemented robust fallback for missing route/station data in getLegRouteInfo and introduced FRFS-backed fallbacks to keep UI data populated even when OTP lookups fail. These changes are tied to commit 0d2e18e84268344a0ac2b6e6f53e6e9d3c8dd183. Key outcomes include: - Prevented overall failure in leg route rendering by returning best-effort LegRouteInfo via new LegRouteInfoFallback and mkFallbackFromFrfsBooking/mkFallbackFromFrfsSearch, sourcing metadata from FRFS requests when OTP data is unavailable. - Downstream data flow now passes the fallback through; missing identifiers default to UNKNOWN to avoid nulls and improve debuggability. - Added targeted error logging for missing fields: FromStationCode, ToStationCode, RouteCode, and OTP lookup failures to improve observability. - Comprehensive test considerations established to verify: (a) correct rendering with complete data, (b) fallback usage when OTP data is missing, (c) fallback behavior for search flows, and (d) error log emission for missing data fields. Business value: reduces trip planning failures, preserves user experience during partial data outages, lowers support burden, and increases data quality signals for monitoring and analytics.

May 2026: Reverted currency-based rounding across the Finance Kernel to restore unrounded monetary values across core finance flows, driving improved accuracy, consistency, and auditability in financial reporting. The change reverts the rounding wrapper introduced upstream, ensuring all relevant services store and propagate monetary values as computed, unrounded amounts. This aligns with established accounting expectations and reduces rounding drift in balances, invoices, settlements, and tax calculations across the system.