docs(arch): end-to-end system + tech-stack diagrams

New ARCHITECTURE.md pulls the desktop app (TECHNICAL.md) and the
license server (LICENSE-SERVER.md) into a single picture — the two
were never reconciled into an end-to-end view before.

Contents:
  §1. System diagram (ASCII) showing operator laptop, license
      server stack (nginx → FastAPI → Postgres), Postmark, Gumroad,
      and the buyer's machine — with the three primary flows
      (sale, manual mint, offline activation) traced through it.
  §2. Tech stack diagram, layered: desktop / server / operator /
      external SaaS, with version pins.
  §3. Trust + isolation boundaries table — what crosses each one
      and what the threat model is.
  §4. "Where things are stored" — paths, tables, files.
  §5. Pointers to the deeper per-component docs.

ASCII over Mermaid since the repo's Gitea version is unknown and
plain text renders in every viewer / IDE / raw `cat`.

LICENSE-SERVER.md status flipped from "design proposal, not built"
to "deployed (PR 1 + PR 2 code merged)" — that was stale since
the PR 1 deploy yesterday.

TECHNICAL.md and ADMIN.md gain one-line pointers to ARCHITECTURE.md
so people land at the unified view when looking for "how does it
all fit together".

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

docs/LICENSE-SERVER.md

@@ -1,7 +1,9 @@
-# LICENSE-SERVER — Future online issuance & record-keeping
+# LICENSE-SERVER — online issuance & record-keeping
 
-**Status:** design proposal. Not built. The current system is
-fully offline (see `ADMIN.md`).
+**Status:** **deployed (PR 1 + PR 2 code merged)**. Live at
+`licenses.datatools.unalogix.com`. See `ADMIN.md §"Live deployment"`
+for day-2 operations, and `ARCHITECTURE.md` for the end-to-end
+diagram including the desktop and storefronts.
 
 This doc describes the smallest useful server we could build to
 replace the manual mint-and-paste workflow, without compromising the