[Feature]: Rethink Overview dashboard — denser signal, clearer next actions

[rosspeili]

One-line summary

Explore what Overview should be beyond open/done/overdue bars — more useful at-a-glance, still calm.

Problem / motivation

Overview is a soft landing page. It may under-serve “what matters today” vs Fruits, and under-explain health vs Analytics, while partly duplicating header stats.

Proposed solution

Design exploration first (not random widgets). Possible directions — pick with rationale:

• Tighter link to Fruits top picks / overdue strip
• Mini activity sparkline (near analytics entry)
• Tracker health / empty states for new projects
• Trim redundant numbers vs header stats

Deliverable: proposal on the issue + 1–2 mock paths, then implement an agreed slice.

Implementer notes: Inventory current Overview components + docs/views/overview.md; reuse Analytics aggregations where possible; stay pastel/quiet — not a SaaS marketing dashboard. Out of scope: full Analytics rewrite; user-authored dashboard builder.

Alternatives considered

• Remove Overview and land on Fruits (radical — discuss).
• Keep as-is if exploration concludes that.

Primary surface

Views (Overview / Table / Kanban / Timeline / Neural / Fruits)

Constraints you accept

• Must stay local-first (no required cloud account)
• Should not break existing tracker *.md readability

Mock / sketch / reference (optional)

Attach before/after wireframes when the design conclusion is ready.