✍️ Day Summary
I implemented multi-year date pinning for the timeline, including verifying era and samvatsara formulas across multiple calendar boundaries. I also built out the per-day CalendarContext assembler by integrating Shaka/Vikram eras and corrected the amanta offset calculation based on observed panchang data. Finally, I added logic to determine ayana and ritu periods alongside refining how amanta, purnimanta, and adhika months are calculated.
📊 Daily Overview
Total Activity: 14 commits + 4 merges across 1 repositories
🚀 GitHub Activity
1. astroacharya 🔒 — 14 commits + 4 merges
chore(propagation): declare muhurta type-mirror + public calendar downstreams · eeb11e2
Enrich app/api/muhurta.py block with VK types.ts/muhurta-utils.ts/MuhurtaWindows.tsx; add app/api/calendar.py + calendar_combined.py → VK festivals.service.ts/types.ts/client.ts for the festivals-calendar + lunar work.
fix(db): resolve MONGODB_DB when the URI has no default database · 321aeff
get_default_database() RAISES (not returns None) on an Atlas SRV URI with no DB path; fall back to MONGODB_DB, mirroring scripts/seed_mongo.py. Without this the app crashes on boot against the Atlas URI.
feat(seeds): bilingual descriptions for grahas + rashis; vara storyHi · cd3c18d
Canon-grounded EN+HI description/descriptionHi added (graha 9, rashi 12) and storyHi for the 7 varas, all hi_verified:false for Tushar review. Re-seeded to Atlas.
docs(plans): festival drik-exact + core/timeline shared layer specs + impl plan · 6ce4d5c
Two sequenced specs (shared timeline layer first, festivals on top) + the
implementation plan for the shared layer. Captures: RC1 chandra-masa
(amanta/purnimanta, adhika-aware), RC2 vyapini catalog, RC3 sankranti; the
cost-tiered contracts (global AstronomicalTimeline vs per-location SunriseGrid),
adversarial defenses, and drikpanchang pin-test approach. Festival parity target:
drik-exact.
feat(timeline): scaffold module + data contracts (Task 1) · 33ed988
feat(timeline): tithi-boundary + sankranti instant finders (Tasks 2-3) · 9fe9b62
Tier A, location-free. find_tithi_boundaries scans at 6h (handles 0/1/2
boundaries per day) + bisects to 1e-6 day. find_sankrantis lands the true
ingress instant (Makar Sankranti Jan 14/15 IST, vs the festival engine’s
next-sunrise Jan 16 — validates the RC3 fix). Uses get_sun_moon_lons (2 swe
calls) in the hot loop.
feat(timeline): AstronomicalTimeline global assembly (Task 4) · 6e38c30
feat(timeline): SunriseGrid + panchanga_day_of day-attribution (Task 5) · f9feb54
feat(timeline): LunarMonthTable — amanta/purnimanta + adhika (Tasks 6-7) · 444a6c9
amanta name = LUNAR_NAMES[(interior_sankranti_rashi+1)%12] (pinned: Tula→Kartik,
Mesha→Vaishakha, Makara→Magha); purnimanta = amanta+1 (Krishna-paksha shift);
adhika = month with no sankranti (2026 May16–Jun14 detected). Coincident
sankranti/amavasya resolved at instant level. Exact adhika name pinned in Task 12.
feat(timeline): ayana + ritu (Task 8) · 526802f
fix(timeline): amanta offset 0, pinned to drikpanchang (corrects Tasks 6-7) · 7888468
Armchair guess was amanta = LUNAR_NAMES[(rashi+1)%12]; the drik day-panchang
header (2026-06-26 = Jyeshtha amanta; Diwali = Kartik purnimanta) shows amanta =
LUNAR_NAMES[rashi] (offset 0), and the +1 is the purnimanta Krishna-paksha shift.
Diwali is Ashvin-amavasya (amanta) / Kartik-amavasya (purnimanta). 2026 adhika
correctly names ‘Adhika Jyeshtha’. Tests re-pinned to drik values. This is the
‘pin to drik, not first principles’ rule catching the guess, as the spec intended.
feat(timeline): era + samvatsara + CalendarContext assembler (Tasks 9, 11) · 1d4b6dd
Shaka/Vikram era (rollover at Chaitra new year), Vikram-reckoned samvatsara
(pinned: VS 2083 = Siddharthi), and the per-day CalendarContext assembler.
Verified against drik’s 2026-06-26 header: Shaka 1948, Vikram 2083 Siddharthi,
Jyeshtha (amanta+purnimanta, Shukla), Uttarayana, Grishma.
…and 2 more commits in this repo.
Merges:
- Merge pull request #36 from Rupali59/fix/sunrise-local-midnight-search
- Merge pull request #37 from Rupali59/fix/muhurta-rahukaal-gulika-yamaganda
- Merge pull request #39 from Rupali59/feat/muhurta-summary-and-input-hardening
- Merge remote-tracking branch ‘origin/main’ into feat/muhurta-summary-and-input-hardening
📈 Development Analytics
Daily Summary
| Metric | Today |
|---|---|
| Commits | 14 |
| Merges | 4 |
| Skill runs | 0 |
| Decisions | 0 |
| Eurekas | 0 |
| CEO plans | 0 |
| Notes touched | 0 |
Decisions logged today
None today.
Eurekas
None today.
Strategic plans authored
None today.
Notes touched
None today.
Running totals (as of this date)
Active days last 90: 69 / 90 (substantive)
Days with any signal last 90: 72 / 90
Skill runs (since 2026-03-25): 75
Commits this year (authored): 1453
Decisions logged this year: 15
Eurekas this year: 5
CEO plans authored this year: 13
Projects touched this year: 57
Top projects last 90: VipinKaushik (27d), astroacharya (21d), portfolio (19d), vipin-kaushik-content (17d), Mothership (13d)
💭 My Notes
[Your own thoughts, observations, or context for this day — this section is never overwritten by automation]