Can I vibecode UserVoice?

Build a comprehensive, production-ready clone of UserVoice, a product management and customer feedback platform. The app must be developed using Next.js (App Router), TypeScript, Tailwind CSS, PostgreSQL, and Drizzle ORM. Do not offer alternative tech stacks.

### Data Models & State
1. **Users/Customers**: Track name, email, company, role, MRR (Monthly Recurring Revenue), and account type for segmentation. Store all user data locally by default.
2. **Feedback/Feature Requests**: Store title, description, category, tags, submitter, upvotes, downvotes, and current status (e.g., Under Review, Planned, In Progress, Completed).
3. **Comments**: Threaded discussions attached to feature requests.
4. **Themes/Insights**: Group related feedback together for prioritization and research view.
5. **Research Notes**: Add a research note type with evidence links, quotes, themes, and confidence.

### Core Logic & Features
- **Feedback Portal & Intake Widget**: Create a public and private feedback intake portal where users can submit feature requests, browse existing ideas, upvote/downvote, and comment. Include optional contact details and consent text.
- **Admin Dashboard**: A separate interface for product teams to review, categorize, search, filter, and prioritize raw feedback based on customers, segments, themes, and status.
- **Prioritization & Scoring Engine**: Implement an objective scoring system based on MRR, upvote volume, and custom effort vs. impact scores.
- **Smart Merging & Theme Detection**: Provide a UI to manually merge duplicate feature requests and connect evidence to overarching themes.
- **Status Updates & Communication**: When a request's status changes, simulate email notifications (using Resend) to all users who upvoted or commented. Provide moderation, export, deletion, and an audit log.
- **Public Roadmap**: Publish a read-only Kanban-style roadmap or findings page using only explicitly public items.

### UI, UX & Aesthetics
- **Design System**: Use a modern, sleek, and professional aesthetic suitable for SaaS products. Employ a curated color palette with subtle gradients, sharp typography, and ample whitespace.
- **Micro-interactions**: Include smooth hover effects on cards, soft transitions when upvoting or changing statuses, and dynamic notifications.
- **State Management**: Implement clear empty states, loading skeletons, success states, and graceful handling of unavailable APIs. Add input validation and safe filenames.

### Technical Requirements
- Make the first run work locally with one documented command.
- Put secrets in `.env`, ship `.env.example`, and never commit credentials.
- Write focused tests for the core transformation and one end-to-end happy path.
- Create a README with setup, architecture, permissions, data location, and backup steps.
- Do not add real accounts, billing, telemetry, analytics, or a hosted control plane.
- Deliberately leave out a paid research-participant marketplace, unlimited video storage, automated transcription, enterprise repositories, SSO, and governance.
- Finish by running the tests and listing the exact commands used.