Should you build your own Connecteam?

Build me a narrow small-team workforce scheduler to replace only Connecteam's visible operations loop. Requirements:

- Use Node.js 22, Fastify, Nunjucks, htmx, and better-sqlite3. Run one
  process behind Caddy; do not add a SPA, ORM, or container platform.
- Give one admin a mobile-first two-week schedule editor for employees, roles,
  locations, open shifts, recurring shifts, and per-shift checklists.
- Employees sign in with expiring magic links sent through SMTP credentials in
  .env. No public signup; hash tokens and rate-limit every login endpoint.
- Each employee can set availability, request time off, claim an open shift,
  request a swap, see only their own schedule, and mark shift tasks complete.
- Add explicit clock-in/out buttons. Store server time and optional one-shot
  browser location only after consent; never track location in the background.
- Managers approve requests, publish changes, and see an append-only audit log.
  Export schedules, requests, and worked time as CSV; never calculate payroll.
- Store everything in SQLite, make nightly timestamped backups, and include a
  tested restore command. No telemetry or third-party tracking.
- Out of scope: native apps, push notifications, chat, GPS geofences, kiosk and
  NFC clocks, payroll integrations, training, HR documents, and legal compliance.
- Add focused tests for permissions, overlapping shifts, token expiry, and CSV
  export, plus one Playwright flow from invite through completed shift.
- Include a README for .env, HTTPS, backups, retention, and the employee-data
  risks. End by running tests and listing the exact commands and results.