Per-user widgets, with an org-default underneath

When a user opens /dashboard/widgets, the resolver picks:

1. The user's most recently updated *private* dashboard (their personal config). 2. The org's is_org_default = true shared dashboard (the admin-curated default). 3. An empty state with "Configure your dashboard" — the user spins one up with one click.

The three states cover the spectrum: brand-new orgs see a default, established orgs see what each operator built for themselves, and the in-between case (org default exists, user hasn't customised) shows the org's choice unobtrusively.

Five widget kinds in v1:

• Change — a number with a delta-from-last-period badge. Default source is row count from contacts / deals / jobs / orders.
• Progress — numerator / denominator with a filled bar. Useful for "deals closed / quarterly target."
• Multi-metric — a card listing several metrics side by side; full chart rendering lands when the time-series engine grows up.
• Quick action — a button wired to an org-defined action key. The frontend dispatches; the server resolves what to do.
• Rich text — markdown note for context the team needs ("This week's priority is the inbound leads from the trade show").

Three follow-ons:

• Drag-to-arrange — today's editor uses up/down buttons; v2 brings a proper grid drag.
• Time-series renderer — the multi-metric card upgrades from inline values to actual sparklines / area charts once the metric engine ships time-bucketed reads.
• Filter rules + custom aggregations — today's resolver supports count against an allowlisted set of tables. V2 adds field-level filters, sum / avg / max, and joins against custom-field columns from the metadata engine.