Lohnt sich dein eigenes Nolt?

Build a personal replacement for Nolt in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and Resend; do not offer alternative stacks.
The core loop is: collect structured feedback on a public board with voting and comments, merge duplicates, connect evidence to themes, and publish a transparent roadmap with statuses.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Create public and private feedback intake with consent text and optional contact details.
Support posts, votes, comments, tags, statuses, owners, and duplicate merging.
Add a research note type with evidence links, quotes, themes, and confidence.
Build search and filters across feedback, customers, segments, themes, and status.
Provide email notifications, moderation, export, deletion, and an audit log.
Publish a read-only roadmap or findings page using only explicitly public items.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
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 accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out a paid research-participant marketplace.
Deliberately leave out unlimited video storage and automated transcription.
Deliberately leave out enterprise repositories, SSO, and governance.
Finish by running the tests and listing the exact commands used.