Lohnt sich dein eigenes Linear?

Build me a personal issue tracker to replace Linear. Requirements:

- A local web app: Node + Express + better-sqlite3, server-rendered, dark, bound
  to localhost. One SQLite file I back up.
- Issues have an auto ID with a team prefix (ENG-142), a Markdown body, a status
  (backlog, todo, in progress, in review, done, canceled), a priority (urgent to
  none), labels, and a point estimate.
- Keyboard-first: c creates, s status, p priority, l labels, / searches titles,
  bodies, and comments with SQLite FTS5, cmd+k opens a command palette for all
  of it.
- Three views: My Issues, a board with drag between columns, and the current
  cycle, a two-week window with a remaining-estimate burndown. On its last
  day, unfinished issues roll forward, done ones archive.
- node scripts/sync-github.js (octokit, token and repo list in .env) pulls open
  GitHub issues in, keyed on issue number so re-runs update instead of duplicate.
- Pressing b copies a branch name (me/eng-142-short-title) to the clipboard.
- Comments and a per-issue activity log. No accounts, no telemetry, nothing
  leaves the machine except the GitHub calls.
- Out of scope: multiplayer, mobile apps, and writing back to GitHub. Skip auth
  and deploy config, this runs on my machine.
- README: how to run it, where the SQLite file lives, and the GitHub token scope.