Sam Valladares 01d2e006dc fix(dashboard): split empty-database from API-failure on the graph page ... Before this, any exception from `api.graph()` — network down, dashboard disabled server-side, 500, 404 — surfaced as "No memories yet. Start using Vestige to populate your graph." Indistinguishable from a clean first-run install. Users couldn't tell whether Vestige was empty or actually broken. The fix checks both the error message shape (looks for 404 / not found / empty / "no memor" patterns) AND the last known graph node count. Only when both say "empty" do we keep the onboarding message; anything else surfaces the real error under "Failed to load graph: ..." so debugging doesn't require guessing.		2026-04-19 16:45:08 -05:00
..
dashboard	fix(dashboard): split empty-database from API-failure on the graph page	2026-04-19 16:45:08 -05:00