Super-Calendar Legacy Compatibility

Documentation:
https://super-calendar.io/legacy/

Machine contract:
https://super-calendar.io/api/legacy

Transport:
HTTP compatibility: http://legacy.super-calendar.io/
HTTPS mirror: https://legacy.super-calendar.io/
HTTPS upstream: https://super-calendar.io/

Current compatibility routes:
http://legacy.super-calendar.io/health.txt
http://legacy.super-calendar.io/calendar/
http://legacy.super-calendar.io/weather-summary
http://legacy.super-calendar.io/exchange-summary
http://legacy.super-calendar.io/moon-summary
http://legacy.super-calendar.io/seasons-summary
http://legacy.super-calendar.io/religion-summary
http://legacy.super-calendar.io/events-summary
http://legacy.super-calendar.io/custom-summary
http://legacy.super-calendar.io/holidays-summary
http://legacy.super-calendar.io/crypto-summary
http://legacy.super-calendar.io/earnings-summary
http://legacy.super-calendar.io/sports-summary

Scope:
GET and HEAD only.
Public low-level text and the fixed local legacy calendar only.
No login, cookies, credentials, private data, or arbitrary proxying.
The proxy upgrades its fixed allowlisted requests to the HTTPS API upstream.
Summary routes mirror the public I/O catalog; endpoint implementations are not duplicated.
The calendar is served locally and never proxies the modern calendar page.

Charset:
?charset=0  UTF-8 / Unicode (default)
?charset=1  US-ASCII
?charset=2  ISO-8859-1 / Latin-1

Calendar presentation query:
?locale=pt-BR&mode=compact&view=month-grid&surface=web&theme=paper

Legacy is a narrow compatibility surface. New integrations should prefer OpenAPI or I/O.