fix: drive bottom nav from module registry so all modules appear on mobile

The bottom nav was hardcoded; the sidebar already read from the module
registry. Converted BottomNav to a server component that calls
getRegistry() using the same pattern as Sidebar, so any module with a
nav field automatically populates both nav surfaces.

Bumps version to 0.4.2.

drizzle/meta/_journal.json

@@ -113,6 +113,13 @@
       "when": 1748736000000,
       "tag": "0015_garden_schema",
       "breakpoints": true
+    },
+    {
+      "idx": 16,
+      "version": "7",
+      "when": 1748822400000,
+      "tag": "0016_garden_improvements",
+      "breakpoints": true
     }
   ]
 }

package.json

@@ -1,6 +1,6 @@
 {
   "name": "famapp",
-  "version": "0.4.0",
+  "version": "0.4.2",
   "private": true,
   "type": "module",
   "packageManager": "pnpm@10.33.3",

src/components/bottom-nav.tsx

@@ -1,19 +1,19 @@
-"use client";
+import { getRegistry } from "@/modules/_core/registry";
-
 import { NavLink } from "@/components/nav-link";
 
-const ITEMS: Array<{ href: string; label: string; icon: string }> = [
+export async function BottomNav() {
+  const { modules } = getRegistry();
+  const moduleNav = modules.flatMap((m) => (m.nav ? [m.nav] : []));
+
+  const items = [
     { href: "/", label: "Dashboard", icon: "home" },
-  { href: "/calendar", label: "Calendar", icon: "calendar" },
+    ...moduleNav.map((n) => ({ href: n.href, label: n.label, icon: n.icon ?? "circle" })),
-  { href: "/lists", label: "Lists", icon: "list" },
-  { href: "/notes", label: "Notes", icon: "note" },
     { href: "/settings", label: "Settings", icon: "settings" },
   ];
 
-export function BottomNav() {
   return (
     <nav className="bottom-nav" aria-label="Primary navigation">
-      {ITEMS.map((it) => (
+      {items.map((it) => (
         <NavLink key={it.href} href={it.href} icon={it.icon} label={it.label} variant="bottom" />
       ))}
     </nav>