Initial scaffold: Turborepo monorepo + design wiki

Turborepo (pnpm workspaces) with all dependencies pinned to latest
mutually-compatible versions: turbo 2.9, TypeScript 6, Fastify 5,
React 19, Vite 8, better-sqlite3 12 + Drizzle ORM 0.45.

Layout:
- apps/server   Fastify backend (local JWT auth + role guard, /health)
- apps/web      React 19 + Vite 8 operator SPA
- packages/db   Drizzle schema on SQLite/WAL; append-only events + users
- packages/devices  reader/printer/relay adapter interfaces (intent-only relay)
- packages/shared   shared domain types

Architecture constraints from the design wiki are encoded in the scaffold:
append-only hash-chained + signed event log, device-agnostic adapters,
"a barrier is not a door" (relay expresses intent only), fully-local
offline-first auth.

wiki/ is an LLM-maintained Obsidian knowledge base (28 pages) ingested
from the architecture & design notes, with its own maintenance schema.

Verified: pnpm install, full turbo build (5/5), server boots and serves
/health, drizzle-kit generates the initial migration.

wiki/entities/payload-cms.md

@@ -0,0 +1,22 @@
+---
+type: entity
+tags: [parking, rejected, stack]
+sources: [parking-system-architecture]
+updated: 2026-06-14
+---
+
+# Payload CMS (rejected)
+
+A genuinely strong option that was **rejected** as the backend. (See
+[[parking-system-architecture]] §2.)
+
+- It has real strengths: free admin UI, built-in auth/RBAC, runs on Node so it *can* host
+  device drivers via init hooks.
+- **Primary reason rejected: the v3 license shift to BSL** (source-available, not open source).
+  For a long-lived business system, a vendor that can change licensing terms underneath you is
+  an unacceptable risk. This is the cautionary case behind the whole stack's
+  "vendor-agnostic, rug-pull-proof" preference (see [[technology-stack]]).
+- Secondary concerns: it's a CMS at heart (weaker on real-time/event-driven workloads), and
+  Next.js is heavier than needed here.
+
+Related rejected alternatives: [[refine]], [[logto-zitadel-oidc]].