Paddy
b4c8c91795
Step 5 removes the legacy path, so it removes the fallback step 4 still leans on: the join that renders the author of every pre-cutover event, and the routes an old cached bundle talks to. Building it before step 4 has been deployed and watched turns a recoverable deploy into an unrecoverable one, so this records the shape rather than implementing it. Two decisions worth having in the runbook rather than in someone's memory. The legacy calendar user module gets deleted outright rather than unmounted - a survey confirmed nothing outside that directory imports it, and it is the API's last unauthenticated account-creation and mail-sending endpoint. The users and sessions tables get renamed aside rather than dropped: the display names are already snapshotted so nothing visible depends on those rows, but they still hold e-mail addresses and password hashes, and a rename makes them unreachable without destroying anything. Also notes the two consequences worth accepting deliberately: activation links already in inboxes become 404s, and createdById leaves the wire format. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>