feat: add post-signup survey feature

[gax97]

What's done

Add post-signup survey functionality including:

• Database migrations and schema updates for survey responses
• Backend models and API endpoints for survey data
• Frontend React component for survey form
• Authentication and configuration updates
• Tests for models and components

How it works:

recording_demo.mov

Resolves: #4052

[superplanehq-integration]

👋 Commands for maintainers:

• /sp start - Start an ephemeral machine (takes ~30s)
• /sp stop - Stop a running machine (auto-executed on pr close)

[cursor]

Cursor Bugbot has reviewed your changes and found 4 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit f484471. Configure here.}

[cursor]

Skip button missing loading prop

Medium Severity

The Skip LoadingButton passes loadingText="Skipping..." but never sets the loading prop. The Continue button correctly passes loading={loading === "continue"}, but the Skip button omits loading={loading === "skip"}. Because LoadingButton defaults loading to false, the spinner and "Skipping..." text never appear — the button just becomes disabled with the original label when the skip request is in flight.

 

^{Reviewed by Cursor Bugbot for commit f484471. Configure here.}

[cursor]

Prefer named exports

Low Severity

export default SignupSurvey adds a new default export for a page component under web_src/src. Named exports improve Vite compile behavior and IDE stability. See web_src/AGENTS.md (TypeScript).

 

^{Triggered by project rule: SuperPlane frontend — Bugbot rules}

^{Reviewed by Cursor Bugbot for commit f484471. Configure here.}

[cursor]

Prefer shadcn/ui primitives

Low Severity

A raw <input type="text"> is used for the "Other" source field, but @/components/ui/input provides a shadcn Input component. Use @/components/ui primitives instead of raw HTML when an equivalent exists.

 

^{Triggered by project rule: SuperPlane frontend — Bugbot rules}

^{Reviewed by Cursor Bugbot for commit f484471. Configure here.}

[cursor]

Byte-based string truncation corrupts multi-byte UTF-8

Medium Severity

len(trimmed) counts bytes and trimmed[:useCaseMaxLen] slices by bytes, not runes. For multi-byte UTF-8 input (e.g. CJK characters at 3 bytes each), the slice can cut a character in half, producing an invalid UTF-8 string. PostgreSQL in UTF-8 mode rejects invalid sequences, so this causes a 500 error for affected users. The frontend maxLength counts characters, so a user typing 500 CJK characters sends ~1500 bytes, triggering this truncation path.

Additional Locations (1)

• pkg/public/signup_survey.go#L112-L114

 

^{Reviewed by Cursor Bugbot for commit f484471. Configure here.}