Add /progress dashboard + homepage Resume Reading widget

[nomadicmehul]

Summary

Adds a top-level /progress dashboard and a "Resume Reading" widget on the homepage, both powered by the same localStorage data that Captain's Bridge writes when users mark sections complete.

Stacked on top of PR #41 (feature/captains-bridge-reader). Targets that branch as its base, so this PR's diff reads as the pure Progress feature — no Bridge noise. When #41 merges to main, retarget this PR's base to main (GitHub offers one click) and no rebase is needed.

What this ships

/progress page

• Hero — four stat cards: sections read, pages touched, pages complete, last active (relative + absolute timestamp).
• By Category — expandable groups for every learning path, tool, and cloud provider detected in the doc tree. Each group shows a dual progress bar (touched vs complete). Click to reveal every doc with status dot ○ / ◐ / ●, title, and N/M counter.
• Empty state — clean CTA block when no progress exists, with links to DevOps path + Docker start.
• Manage — four control cards:
  • ⬇ Export — downloads cloudcaptain-progress-YYYY-MM-DD.json
  • ⬆ Import — merge or replace from a previously exported file
  • 🪄 Seed demo data — fills 8 sample entries spread over the last 10 days for demos / screenshots; reversible via "Remove demo data"
  • ↻ Reset — requires user to type DELETE to confirm
• Live updates via cc-bridge-read-change (same-tab) and storage (cross-tab) events.
• Footer link and new navbar link 📖 Progress for discoverability.

Homepage Resume Reading widget

• ⚓ CAPTAIN'S LOG — Resume where you left off card, slotted between the hero and stats sections.
• Top 3 in-progress docs (readCount > 0 && !isComplete), sorted by most-recently-updated.
• Each row: title, N / M progress, relative time (2h ago), animated bar, doc path, Continue →.
• Renders nothing when there's no partial progress, so first-time visitors see an unchanged hero+stats flow.
• Wrapped in BrowserOnly — SSR is unaffected.

Architecture

localStorage  (written by Bridge's useReadProgress)
  cloudcaptain.bridge.read./docs/tools/docker/fundamentals = {
    readSections: ["what-is-docker", "containers-vs-vms"],
    totalSections: 8,
    lastUpdated: 1713028347000
  }
        │
        ▼
  getAllReadEntries()           ←  readProgress.ts (duplicates Bridge contract)
        │
        ▼
  useAllDocsData()              ←  Docusaurus plugin-content-docs client API
  (full doc tree + titles)
        │
        ▼
  classifyDoc(pathname)         ←  groupDocs.ts (regex → category + icon)
        │
        ▼
  ┌────────────────────┬────────────────────────┐
  │  /progress         │  homepage widget       │
  │  ProgressHero      │  ResumeReadingWidget   │
  │  ProgressByTool    │                        │
  │  ProgressControls  │                        │
  └────────────────────┴────────────────────────┘

Files added

website/src/pages/progress.tsx                                 (top-level page, SSR-safe)
website/src/components/Progress/
  ProgressHero.tsx              (four stat cards)
  ProgressByTool.tsx            (expandable category groups + dual progress bars)
  ProgressControls.tsx          (export / import / seed / reset, typed DELETE)
  ResumeReadingWidget.tsx       (homepage "Captain's Log" card)
  readProgress.ts               (localStorage reader / writer / export / import)
  groupDocs.ts                  (pathname → category matcher, ordered)
  seedDemo.ts                   (8 synthetic entries, reversible)
  styles.module.css             (dashboard styles)
  resumeWidget.module.css       (homepage widget styles)

website/src/pages/index.tsx     (wires BrowserOnly<ResumeReadingWidget />)
website/docusaurus.config.ts    (navbar + footer links)

Design notes

• Client-only. No backend. No new npm dependencies. Everything runs in the browser.
• Privacy first. Progress stays in localStorage; the page surfaces this in a footer note and on the Reset card. Export provides user-owned backup; there's no telemetry.
• SSR safe. Every component that touches localStorage is gated by BrowserOnly or checks typeof localStorage. A minimal SSR skeleton renders on first paint and the real dashboard hydrates client-side.
• Schema contract with Bridge. readProgress.ts duplicates the 20-line localStorage helper that lives inside the Bridge feature (useReadProgress.getAllReadEntries). This duplication is intentional — it keeps the two features decoupled at the source code level but honours the same cloudcaptain.bridge.read.{pathname} key schema at the data level. Refactor into a shared module is easy once both PRs merge.
• Category grouping is centralized. groupDocs.ts holds the regex-to-category mapping with display icons and sort order — one file to update when a new tool section is added.
• Demo seed is reversible. Seeded keys are tracked in cloudcaptain.bridge.demo-seed; unseedDemoProgress() removes only those keys. Real user progress is never clobbered (seeder refuses to overwrite entries with non-zero readCount).

Test plan

• npm run build in website/ passes — no new warnings from this branch
• Navigate to /progress
  • Empty state renders with CTA block when localStorage is clean
  • Click 🪄 Seed demo data — hero stats + groups populate instantly, 8 entries across Docker/K8s/Terraform/Linux/Git/DevOps
  • Expand any group — every doc appears with correct status dot
  • Click any doc link — navigates
• Complete a real section via Bridge's m key on a tool page → dashboard live-updates without refresh
• Open site in second tab, complete a section there → first tab's dashboard updates via storage event
• ⬇ Export — downloads valid JSON (version:1, entries map)
• ⬆ Import → Merge — adds entries without clobbering
• ⬆ Import → Replace all — wipes then imports
• ↻ Reset — requires typed DELETE confirmation; clears localStorage
• 🪄 Seed demo data → Remove demo data — clean round-trip
• Homepage — with progress seeded, "Captain's Log" card appears between hero and stats
  • Shows top 3 in-progress docs
  • Progress bars match stored readCount / totalSections
  • "View all progress →" → /progress
  • Each row navigates to the doc
• Homepage — with progress cleared, widget does NOT render (clean hero+stats flow)
• Navbar 📖 Progress link visible and routes correctly
• Footer 📖 Your Progress link routes correctly
• Mobile viewport (< 600px) — all three views (dashboard, widget, controls) remain usable

Not in this PR

• Calendar heatmap visualization (Phase 2).
• Cross-device sync (requires user accounts — explicitly out of scope).
• Learning-path grouping from careerPaths.json (different semantic model; defer).