update custom verifier code snippet to show redirect

[teallarson]

Our example verifier app uses nextjs, which has its own redirect function (which is what that uses)

I opted for generic redirects from the server here to keep the examples from getting bloated or specific to some particular framework. Open to other approaches!

Alas, I did not remember to copy the branch name from Linear, but this should resolve https://linear.app/arcadedev/issue/PLT-354/allow-customers-to-set-next-uri-in-dashboard (though in a different way)

---

Note

Refines the "Valid Response" examples in app/en/guides/user-facing-agents/secure-auth-production/page.mdx to emphasize server-driven redirects after the auth flow completes.

• JavaScript: use client.auth.waitForCompletion(result.auth_id) and return a 303 with Location header instead of a simple success string
• Python: add from starlette.responses import Response, use client.auth.wait_for_completion(result.auth_id), and return a 303 with Location header
• Removes prior placeholder success messages and clarifies redirect handling post-completion

^{Written by Cursor Bugbot for commit 4f7156f. This will update automatically on new commits. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
docs	Ready	Preview, Comment	Jan 7, 2026 4:39pm

[nbarbettini]

I opted for generic redirects from the server here to keep the examples from getting bloated or specific to some particular framework. Open to other approaches!

I think you're spot on - avoiding any one specific framework approach here is good since these are generic docs.

Added some small suggestions above!