Send a request
Use this form for implementation feedback, institutional setup, or rollout coordination.
Direct route
What to include in a good request
Better input reduces iteration time once this moves into the real application.
Page and workflow context
Specify whether the issue belongs to landing, auth, homepage dashboard, generator, cases, community, history, analytics, insights, settings, or internal debug. That keeps the migration path clean.
Expected vs actual behavior
State exactly what the page should do and what it does instead. For example: login should route to homepage, analytics should use the common shell, or support pages should match the landing page header.
Implementation priority
Say whether the request is design-only, prototype navigation, content completion, or something that must be preserved when we move to Supabase and Vercel in the Next application.