pod
Other formats agents might prefer:
markdownjsonllms.txt

Agent? You probably want markdown or json, or Pod over MCP.

Reported issues for panchangam

Pod holds 8 of 8 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to panchangam.

Most discussed

Add local Travel context, cardinal direction, and primary-traveller contract

Parent: #282 Epic: #248 Depends on: #249, #253 Related: #263

Outcome

Add the local, versioned event context required to apply Travel rules only to the journeys and traveller they actually govern.

Required context

  • Exactly one primary traveller profile.
  • Journey scope: short or long-distance.
  • Conveyance: road-or-rail, air, sea or other.
  • Purpose: business, pleasure, emergency or other.
  • Whether a business journey is to meet an influential person.
  • Departure direction: North, East

Read the thread · 2026-08-30 · open · 3 comments

Add a hardened DashaFlow profile-derivation contract

Parent epic: #224 Depends on: #225

User story

As the guest gateway, I need a narrow authenticated sidecar operation so I can derive reusable profile facts without exposing the raw DashaFlow API to browsers.

Scope

In socraticsurge/dashaflow-sidecar, add a versioned server-to-server endpoint that calls the existing DashaFlow 1.1.0 chart computation and projects only the approved contract.

Acceptance criteria

  • Strictly validates date, time, coordinate bounds, and IANA timezone

Read the thread · 2026-08-29 · closed · 1 comment

Create the safe contributor workflow for adding or changing a computation

Parent epic: https://github.com/socraticsurge/telugu-calendar-utilities/issues/164

Depends on #171, #165, #166, #167, #168 and #169.

User story

As a future contributor, I want one concrete path for adding or changing a computation so I know where it belongs, what evidence is required and which approval/release gates apply.

Scope

  • Create a copyable computation record/documentation template.
  • Provide decision guidance for engine core vs additive module vs personal layer vs adapter/pre

Read the thread · 2026-08-27 · closed · 1 comment

Add computation-documentation coverage and freshness gates

Parent epic: https://github.com/socraticsurge/telugu-calendar-utilities/issues/164

Depends on #165, #166 and #167.

User story

As a maintainer, I want the full verification command to detect undocumented or stale computations so documentation remains part of the release contract rather than a one-time snapshot.

Scope

  • Validate required fields and implementation/test links in the canonical computation inventory.
  • Detect runtime computations or public outputs added without a coverage d

Read the thread · 2026-08-27 · closed · 1 comment

Document derived, personal, calendar and browser computations end to end

Parent epic: https://github.com/socraticsurge/telugu-calendar-utilities/issues/164

Depends on #165.

User story

As a maintainer, practitioner or API consumer, I want the non-core computation layer documented end to end so I can understand every derived verdict, score, window and calendar result across Python, MCP and the website.

Scope

  • Cover timing/filter modules, named Muhurtas, Panchaka/Shuddhi, Homa elections, Tarabalam, Chandrabalam, Lagna/Hora, Gochara, Phalalu, Maudhya, Graha Y

Read the thread · 2026-08-27 · closed · 1 comment

Create a canonical, machine-readable computation inventory

Parent epic: https://github.com/socraticsurge/telugu-calendar-utilities/issues/164

User story

As a maintainer, I want one canonical inventory of production computations so I can prove that nothing ships without an owner, explanation, evidence state and verification path.

Scope

  • Define a stable computation identifier and a machine-readable record format.
  • Inventory engine calculations, derived timing modules, personal/scoring logic, graha calendars, generated-data builders and TypeScr

Read the thread · 2026-08-27 · closed · 1 comment

Integrate the Raman Borrowing election assessor

Parent event: #271 Parent epic: #248 Depends on: the Borrowing source, same-Rasi conjunction, role/purpose and both #289 research children; #292-#296, #254, #299

Outcome

Integrate only accepted Raman predicates and preserve honest fallbacks on unsupported surfaces.

Acceptance criteria

  • Preserve four universal Nakshatra exclusions and apply Janma-Nakshatra only to the explicit primary borrower.
  • Wire same-Rasi conjunction as reject after convention/effect acceptance.
  • App

Read the thread · 2026-08-30 · open · 0 comments

Restore MCP compatibility in fresh Python installations

Problem

The package declares mcp>=1.0. A fresh dependency resolution currently installs MCP 2.x, while the server imports mcp.server.fastmcp. The resulting package fails during import or startup across the supported Python 3.10-3.13 range.

Scope

  • Decide whether to constrain the supported MCP major version or adapt the server to MCP 2.x.
  • Add a clean-environment package import and CLI startup smoke test.
  • Regenerate the dependency lock after the compatibility decision.
  • Bump the PyPI

Read the thread · 2026-08-27 · closed · 0 comments

Most recent

The remaining reports are on the project's issue tracker.