Lohnt sich dein eigenes RADAAR?

Build a personal replacement for RADAAR in an empty repository.
Use Next.js 15, TypeScript, PostgreSQL, Drizzle ORM, and exactly one official social-platform API; do not offer alternative stacks.
The core loop is: create, schedule, preview, publish, and track posts for one social network with a searchable content calendar.
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.
Support drafts, scheduled posts, queues, campaigns, tags, reusable snippets, and a weekly calendar.
Connect exactly one social platform using its documented OAuth flow.
Validate character, media, aspect-ratio, and file-size limits before scheduling.
Publish through idempotent background jobs with retries and clear failure states.
Store platform post identifiers and refresh publication status through the official API.
Maintain a reusable media library with local storage.
Support CSV export and token reconnect.
Include clear empty, loading, success, and recoverable error states.
Add robust validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for scheduling logic and one end-to-end publishing flow.
Create a README covering setup, architecture, permissions, data storage, and backup.
Do not add billing, telemetry, hosted infrastructure, enterprise collaboration, social inbox, listening, analytics dashboards, white-labeling, or unofficial scraping.
Finish by running the tests and listing the exact commands used.