[codex] Release bridge 0.5.12 pylon availability

[Jesssullivan]

Summary

• release @tummycrypt/scheduling-bridge@0.5.12
• switch Acuity URL availability reads from the retired react-calendar DOM path to the current pylon availability API
• preserve browser-session navigation so owner/calendar identity still comes from the live Acuity redirect
• add regression coverage for pylon identity parsing, start-date handling, date mapping, and slot mapping

Root Cause

Acuity no longer renders the calendar surface used by the bridge reader. The service/category anchors still resolve, but the old calendar/date/slot selectors time out before availability can be read.

Live Evidence

• live patched reader against https://MassageIthaca.as.me found URGENT Care Massage service dates for May 2026
• first live date 2026-05-17 returned three available slots: 09:00, 09:30, 10:00 local
• Acuity returns HTTP 422 for past startDate, so current-month reads now start at today in America/New_York

Validation

• pnpm test:host src/adapters/acuity/steps/read-via-url.test.ts
• pnpm test
• pnpm typecheck
• pnpm build
• pnpm check:release-metadata
• pnpm docs:check
• pnpm check:package
• git diff --check