[Muawiya-contact]

Why

After the old hosted services were deleted, the production Supabase API still returned HTTP 404 for /confirmed, /reset-password, and /privacy. The app and review site also had links or guidance tied to the retired host. This PR restores those public pages and finishes the repository cleanup in the same cutover change.

Changes

• Serve confirmation, password reset, and learner privacy pages from the Supabase api Edge function. A direct confirmation-page visit now shows a neutral message; success appears only after an Auth token arrives. The recovery form uses the public Auth key, clears the URL token fragment, and keeps service credentials server-side.
• Keep the mobile API path when opening the privacy page and direct the review site's privacy policy to the Supabase page.
• Accept the exact /functions/v1/api URL in the review-site build, require it to match the Supabase Auth project, and emit valid origin-based CSP headers.
• Remove the retired deployment manifest and active host references from runtime comments, workflows, release instructions, setup guides, and the privacy page. Update current operations for protected Supabase Edge deployments and Cron workers.
• Mark old runbooks as historical. Applied SQL migrations, generated schema contracts, and factual work-log records retain their accurate history. The Supabase Auth email HTML templates already contained no retired host URL, so they were left intact.

Verification

• Supabase TypeScript check and all 95 Edge handler tests passed, including direct, verified, and recovery confirmation-page cases.
• Mobile TypeScript check and all 103 Node tests passed.
• Review site: 22 unit tests, TypeScript check, and production build passed with public fixture values.
• git diff --check passed. A source search found no retired host reference in active runtime code, email templates, workflows, or current setup guides.
• A local mocked browser recovery flow was checked before these cleanup commits. It does not prove live email delivery.

Release steps

There is no database migration. After review and an explicitly approved merge, deploy the tested Edge API revision through the protected production workflow, configure the exact Supabase Auth redirect URLs, and test fresh confirmation and recovery links with an owner-controlled inbox. Publish the compatible mobile OTA for the privacy link and redeploy the Netlify review site for its link/config changes. The separate narrow production hotfix remains in PR #460. Neither PR is merged or deployed by this update.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	⚠️ Failed 2026-10-25T08:08:25.873318Z We couldn’t complete this review. Comment @codex review to try again.	dbc9748	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

[Muawiya-contact]

ok