Update e2e report with workflow failure root cause

E2E_UX_REPORT_2026-03-14.md

@@ -63,6 +63,9 @@ Runtime notes from the run:
 
 - `sqlite-vec` fell back to table-backed storage repeatedly.
 - workflow-local reported `concurrency limit (1) reached`.
+- Live server logs repeatedly failed background filing workflows with:
+  - `SQLiteError: table filing_taxonomy_snapshot has no column named parser_engine`
+  - Inference: the local/e2e database schema is behind the code path used by filing taxonomy persistence.
 - The suite completed in about 1.2 minutes before failing.
 
 ## Manual Workflow Findings
@@ -72,6 +75,7 @@ Runtime notes from the run:
 - Overview page does not distinguish loading vs failure vs empty data.
   - Visiting `/analysis` rendered the full page shell but stayed on `Loading company overview`.
   - The user gets no timeout, error explanation, retry guidance, or indication that background filing tasks failed.
+  - The local server logs showed repeated filing workflow failures caused by a schema mismatch on `filing_taxonomy_snapshot.parser_engine`, which likely contributes directly to this broken state.
   - This is a broken primary workflow, not just a cosmetic state issue.
 
 - Auth confidence is too low.
@@ -87,6 +91,7 @@ Runtime notes from the run:
 - Notification spam degrades every workflow.
   - Coverage creation and navigation produced stacked `Filing sync` toasts.
   - Multiple toasts showed nearly identical states and remained visible across pages.
+  - Because failed background jobs keep retrying or re-reporting progress, the user sees noise instead of one durable status surface.
   - The notifications panel becomes ambient noise instead of actionable feedback.
 
 - Coverage actions can trigger expensive side effects without clear consent.