# Shared brief — UI polish pass (2026-09-04) The operator asked for a design/bug-fix pass over the web dashboard v2 (Tailwind redesign, merged to `main` at `e719e03`+). The work is split into three tasks (`01-toc.md`, `02-rating.md`, `03-shell.md`) that run in parallel in separate git worktrees. Read `docs/plans/briefs/web-dashboard-v2/00-shared.md` for the design language (quiet morning paper: warm paper, near-black ink, one red accent, hairline rules, real typographic hierarchy; reader pages serif, dashboard sans) and the Tailwind v4 conventions. This brief overrides it where they disagree. ## Ground rules - Work only in the worktree named in your brief. **Never touch the main checkout** at `/home/thallada/workspace/the-daily-epub`. Do not `git commit` (the sandbox cannot write `.git/worktrees`); leave the work in the tree and the orchestrator commits. If you can commit, one commit on the worktree branch is fine. - Styling lives in **`src/web/tailwind.css`** (Tailwind v4, `@apply` in `@layer components`, semantic colour tokens `paper/paper-2/ink/ink-2/muted/rule/ rule-strong/accent/loved/good/down/warn`) and in Tailwind utility classes in the askama templates under `src/web/templates/`. **Rebuild the committed CSS** after every change with `npm run css` (writes `src/web/static/app.css`; the binary embeds it with `include_str!`, so rebuild Rust after the CSS). `npm run css:check` must print no diff at the end. - CSP is `default-src 'self'; style-src 'self'; script-src 'self'`: **no inline `