Loading issues
A follow-up to PAR-402 (#72, #80).
Problem: the realtime EventHub is in memory per pod. That's fine at production's single replica, but with two or more API replicas a client would only see events committed on its own pod.
Do
issue.activity deliveries with NOTIFY, and have every pod LISTEN and fan out to its local streams.Last-Event-ID resume working: store a sequence in the database, or emit a reset event on gaps.EventHub and in docs/architecture.md.Implemented in https://github.com/ParadauxIO/taskl.ie/pull/112 as part of the ordered quality stack #107 → #108 → #109 → #110 → #111 → #112 → #113 → #114. Each layer targets its predecessor; #107 targets main. Local final-stack verification: 1,312 backend tests against disposable PostgreSQL 17/pgvector, 1,218 web unit tests, 486 Chromium stories, lint, TypeScript, production build/CSS gate and standalone HTTP smoke all pass. A focused listener cleanup regression also passes after the final lifecycle change. CI results are tracked on the PRs; no merges or deployments performed.
Implementing as one layer of the user-requested code-quality fix stack. Base is current main (rebuild has merged and its remote branch is gone). Plan: add focused behavioral regression coverage, implement this issue without weakening architecture rules, run affected checks and full applicable suites, then publish a stacked PR with validation and dependency links. Stack order: PAR-489 → PAR-492 → PAR-490 → PAR-494 → PAR-491 → PAR-454 → PAR-478 → PAR-493.