feat: ToU readiness — onboarding, footer, and bug fixes

[jim-counter]

Summary

Completes the remaining items on the ToU Readiness milestone:

• Onboarding (Apply new Terms of Use to onboarding and add footer link #627): Updated to dynamically fetch the current active ToU version URL from the backend and link to it. Falls back to the static EXTERNAL_ROUTES.termsOfUse URL. ToU acceptance is recorded after account creation via POST /tou/accept. Changed label from "terms and conditions" to "Terms of Use" for consistency. Confirmed ToU URL: https://autonomys.xyz/auto-drive-terms-of-use.
• Landing footer (Apply new Terms of Use to onboarding and add footer link #627): Added Terms of Use and Privacy Policy links to the footer's Links column.
• Re-consent interstitial fallback URL (Apply new Terms of Use to onboarding and add footer link #627): Updated the hardcoded fallback in TouAcceptanceInterstitial to the confirmed URL.
• Missing dependency (Missing setTouStatus in useEffect dependency array #636): Added setTouStatus to the useEffect dependency array in SessionEnsurer.
• Date formatting (toLocaleDateString locale-dependent on server environment #635): Replaced toLocaleDateString('en-US', ...) with Intl.DateTimeFormat for banner date formatting. Note: the original issue flagged this for Alpine-based Docker images where OS locale data may be missing. Our Dockerfiles use node:20.18.3-bookworm-slim (Debian), which ships with full ICU data, so toLocaleDateString would have worked in practice. The Intl.DateTimeFormat change is still an improvement — it's the modern API, constructs the formatter once, and explicitly sets timeZone: 'UTC' for deterministic output.
• Timestamp types (🔴 High — tou_versions table uses timestamp without time zone #639): Migration to convert all TIMESTAMP columns in tou_versions and user_tou_acceptance to TIMESTAMP WITH TIME ZONE, consistent with banners and purchased_credits tables.
• Idempotent accept (🔴 High — acceptCurrentVersion is not idempotent (unhandled UNIQUE violation) #640): createAcceptance now returns the existing record on duplicate calls instead of null. The ON CONFLICT DO NOTHING already prevented 500 errors, but the response is now consistent.
• Non-material enforcement (🟢 Low — ToU enforcement doesn't block non-material versions #645): Confirmed as intentional per Terms of Use versioning, acceptance tracking, and re-consent flow #625 — non-material changes don't require re-acceptance; continued use constitutes acceptance per the ToU.

Closes #627
Closes #636
Closes #635
Closes #639
Closes #640
Closes #645

Test plan

• Verify onboarding page links to the active ToU version's contentUrl (or falls back to static URL if no active version)
• Verify new user onboarding records ToU acceptance via POST /tou/accept
• Verify existing users who haven't accepted a material ToU change see the acceptance interstitial
• Verify landing page footer displays Terms of Use and Privacy Policy links
• Verify POST /tou/accept called twice returns 204 both times (no 500)
• Verify banner date formatting produces "April 1, 2026" style output
• Run database migration and confirm timestamp columns are TIMESTAMP WITH TIME ZONE

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for auto-drive-storage ready!

Name	Link
🔨 Latest commit	7933005
🔍 Latest deploy log	https://app.netlify.com/projects/auto-drive-storage/deploys/69cd44c106e9230008a3e5db
😎 Deploy Preview	https://deploy-preview-648--auto-drive-storage.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[jim-counter]

bugbot run

[jim-counter]

bugbot run

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR