Add full feature↔UI connectivity audit with gap analysis, CRUD matrix, and roadmap recommendations

[Copilot]

This PR delivers a full-codebase audit mapping features/functions to UI screens/components, then identifies missing, disconnected, and improper feature-to-UI linkages. It also compiles improvement recommendations, user stories, and CRUD operations into a single planning artifact under docs/plan/.

• Audit artifact

  • Added: docs/plan/full_feature_ui_functionality_connection_audit_2026-05-11.md
  • Consolidates feature map across routing, screens, controllers/providers, repositories, and shared widgets.

• Connection-gap findings

  • Documents concrete wiring issues (broken route usage, chat navigation contract mismatch, controller bypasses from UI, duplicate/parallel module paths, and unintegrated offline repositories).
  • Highlights high-risk architecture drift from duplicate classes/modules with overlapping ownership.

• Product + UX improvement recommendations (research-backed)

  • Captures actionable improvements aligned to external guidance (Material 3 navigation/search, Supabase Auth/RLS, Stripe PaymentIntents, WCAG, FCM).
  • Prioritizes remediation in P0/P1/P2 phases for faster execution.

• User stories + CRUD coverage

  • Adds feature-by-feature user story expansions.
  • Adds a CRUD capability matrix across major domains to expose implementation depth and gaps.

Example excerpt from the audit:

- Broken route usage: `context.go('/discovery')` while canonical route is `/discover`.
- Messaging CTA mismatch: profile screens pass `userId` to `/chat/:threadId` instead of creating/retrieving a thread ID first.

[supabase]

This pull request has been ignored for the connected project foubokcqaxyqgjhtgzsx because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.