docs: move the LOTUS_TODO / LOTUS_TESTING backlogs into Gitea issues; keep a reference-only LOTUS_REFERENCE.md

LOTUS_TODO.md → LOTUS_REFERENCE.md (design laws, decided deferrals,
server-blocked features, operational reference only). Every open task was
filed: cinny #195–#210, cinny-desktop #15–#18, matrix #8–#10.

LOTUS_TESTING.md keeps the automated-coverage map, the Playwright notes and
the deploy tip; every manual checklist is now a `qa` issue under the
'Manual QA backlog' (cinny #170–#194, #198) and 'Desktop QA backlog'
(cinny-desktop #11–#14, #18) milestones.

Repointed the README, LOTUS_FEATURES, CI and source comments that
referenced LOTUS_TODO.md.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PPmy3tPq869XDW4njjVaKA

src/app/utils/cryptoDiagLog.ts

@@ -5,7 +5,7 @@ import pkg from '../../../package.json';
 //
 // Installs pass-through wrappers around `console.warn` / `console.error` that
 // ring-buffer any log line matching the KE-1..KE-4 bug-cluster signatures
-// (E2EE KE-1..4 capture; see LOTUS_TODO.md). It NEVER swallows a log call — the
+// (E2EE KE-1..4 capture; see cinny #201). It NEVER swallows a log call — the
 // original console method is always invoked — and it performs NO network I/O.
 // The report metadata is limited to SDK version / device id / user id / sync
 // state; the captured log lines themselves are intentional evidence and may