v0.5.0

Upgrading to 0.5.0

• If a client or key used the holidays tool, it is gone: tools/list no longer offers it and
  a call is refused as an unknown tool. For "is this date a working day" questions, use
  datetime business_days / add / diff with region and subdiv - the public-holiday
  calendar behind those is unchanged. There is no replacement for festival lookups; a date the
  server cannot source is a date it should not answer.
• Keys scoped to holidays keep working for every other tool they name; edit the scope on the
  dashboard when convenient.
• Reminder from 0.4.2: /external/mcp is retired; every tool is on /mcp.

Removed

• The holidays tool. It answered "which festival is when" from tables it could not vouch
  for. A dry run across 2026 for twenty Indian states and twenty-four countries, and a
  three-source comparison (the West Bengal gazette, an astronomical tithi computation, and the
  upstream tables) showed the upstream Durga Puja days off by one for 2026 and half the
  Bengali festivals absent altogether - and a date with no source behind it is exactly what
  this server exists to replace. Rather than ship it as a source of confident wrong answers,
  it is retired: holidays is no longer published, /docs/tools/holidays is gone, the
  catalogue is 17 tools, and datetime's festival anchors ({"festival": ...} as a date) are
  refused with the reason. A key whose stored scope names holidays keeps loading and simply
  no longer lists it. What stays: datetime's add, diff and business_days still
  honour region / subdiv, because counting working days needs only the public-holiday
  tables, which are the part of the upstream dataset that is what it says it is. (#80, #86, #91)