Should you build your own Reeder?

Build a personal replacement for Reeder in an empty repository.
Use Next.js 15, TypeScript, SQLite, Drizzle ORM, Readability.js, and a local background worker; do not offer alternative stacks.
The core loop is: subscribe to permitted feeds, save articles to read later, extract readable text, search and tag the archive locally, sync through a chosen account, and export in open formats.
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 manual URL save, RSS or Atom subscriptions, OPML import, and a simple bookmarklet.
Fetch politely with a clear user agent, rate limits, conditional requests, and robots-aware behavior.
Extract title, author, date, canonical URL, readable HTML, and selected images.
Provide inbox, unread, archive, favorites, tags, highlights, notes, and full-text search.
Keep the original URL prominent and never attempt to bypass authentication or paywalls.
Export OPML, bookmarks HTML, Markdown, and a complete JSON backup.
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 paywall circumvention.
Deliberately leave out licensed publisher content and recommendation networks.
Deliberately leave out native mobile clients and seamless commercial sync.
Finish by running the tests and listing the exact commands used.