PRACTICAL ROUTE Reproduce a supplied broken visitor action, ask an assistant for a focused repair and verify the same action after the change. Your role: Perform the visitor task, record the visible failure and repeat the same action after repair. 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) --- Create a JavaScript project in your own Sentry account. In its SDK Setup/Loader Script settings copy your public loader URL from js.sentry-cdn.com into public/config.js. Keep tracing and Session Replay OFF for this lab. The loader URL/DSN is public ingestion configuration, not an account management token; never ship an auth token. Serve public/ over HTTP. Click Enable practice monitoring, wait for its loaded status, then click Find contact section. The deliberately missing target creates a controlled report. In Sentry find the matching practice-R1 issue and source frame. Replace public/app.js with worked-solution/app.js and change RELEASE to practice-R2. Repeat the user action and inspect the outcome. Alerts require an explicit rule/recipient in your own project; a captured issue is not proof an alert arrived. Only run on synthetic practice paths without personal data.