Loading issues
Code-quality audit finding 5. Ordinary UI PRs run lint/types/unit/stories but skip next build and its CSS manifest gate until a deploy is selected. Acceptance: every affected PR runs production build and starts the built app for bounded smoke checks; public/session/refusal routes and stylesheet script/link behavior are asserted without production credentials; cleanup/timeouts are reliable; deployment still stays opt-in. Reconcile stale root README architecture and branch instructions with the shipped rebuild. Rules 3, 34, 35.
Implemented in https://github.com/ParadauxIO/taskl.ie/pull/114 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.