PRACTICAL ROUTE Save and reload an account’s display name, then use a second test account to check that another person cannot change it. Your role: Use two controlled sessions and verify whose stored value actually changed. 1. Use the supplied project and ask your coding assistant to carry out the implementation. You do not need to write HTML, JavaScript or SQL yourself. 2. Follow the current lesson steps, configure only your own permitted accounts and check the result in the actual page/provider. 3. Keep expected results and observed results separate. Record the exact blocked step if you cannot run a live check. The detailed setup below is available to you and your assistant. Code explanations and extra implementation exercises are optional; important access/privacy checks are still part of the practical lesson. --- REQUIRED SETUP (CODE READING IS OPTIONAL) --- Use a separate Supabase practice project. Configure its Email authentication and a permitted test recipient/custom SMTP. In the Magic Link email template, include {{ .Token }} so the message contains an OTP code rather than only a link. Put only the project URL and PUBLISHABLE key in public/config.js. Never use a secret/service-role key there. Serve public/ over localhost HTTP or your own HTTPS host; module imports do not work reliably from file://. Test only inboxes you control. Sender/account limits may require provider configuration. Run schema.sql once in a separate practice project. The browser uses only a publishable key. Sign in before saving; the database policies bind rows to the verified auth.uid(), not a trusted browser field. Changing a display name does not change the account’s verified email.