[Web/PWA] Run original release parity and visual QA pass

[AlphaMao1]

Parent

#11

What to build

Before the final MVP acceptance pass, compare the Web/PWA rebuild against the existing Tauri release at the product-capability level. The goal is not to copy desktop implementation details, but to prevent the rebuild from shipping as a thin demo that misses core DeepReader workflows.

Acceptance criteria

• A parity checklist compares Web/PWA against the current release for library, reader controls, annotation/notepad, AI chat, memory, settings, skills, statistics, export, and deletion.
• Every intentional omission is tied to the PRD out-of-scope list or a follow-up issue.
• Visual QA verifies the approved design system on desktop library, desktop reader, settings, notepad/digest, AI chat, and Android/narrow reader.
• The UI contains Chinese user-facing copy and no development/internal issue text.
• The QA pass checks that demo-only books, fake progress, mock-only sync, and fake indexing are not counted as completed functionality.
• Findings are recorded in the issue or a linked QA artifact with screenshots and reproduction notes.

Blocked by

• [Web/PWA] Add Markdown export and deletion semantics #20
• [Web/PWA][UI] Apply selected visual system to app shell and core screens #23
• [Web/PWA] Complete library management beyond EPUB upload #24
• [Web/PWA] Complete reader controls for TOC, search, reading settings, and session state #25
• [Web/PWA] Add annotations notepad and reading digest review surfaces #26
• [Web/PWA] Add settings surfaces for sync, model providers, embeddings, fonts, and local keys #27
• [Web/PWA] Add skills library and slash command entry points for the reader assistant #28
• [Web/PWA] Add reading statistics and history #29