Complete admin page API integration and fix broken cart hook

[Copilot]

11 admin pages were stub components (return <div>AdminX</div>), useCart.ts was a broken placeholder causing build failures, and the router was missing the /admin/users/:id route.

Admin pages — stubs replaced with real API integration

Page	Endpoints wired
AdminOrders	GET /admin/orders, PATCH /admin/orders/:id (status update)
AdminInquiries	GET /admin/inquiries, PATCH /admin/inquiries/:id (mark read)
AdminBlog	GET /admin/blog, DELETE /admin/blog/:id
AdminBlogEditor	POST /admin/blog, PUT /admin/blog/:id (create + edit form)
AdminProducts	Full CRUD via modal — /admin/products, /admin/products/:id
AdminGallery	GET/POST /admin/gallery, DELETE /admin/gallery/:id
AdminResources	GET/POST /admin/resources, DELETE /admin/resources/:id
AdminFarmers	Full CRUD via modal — /admin/farmers, /admin/farmers/:id
AdminPrices	GET/POST /admin/prices, PUT /admin/prices/:id
AdminAiConfig	GET/PUT /admin/ai-config via existing AiConfig component
AdminAnalytics	GET /admin/analytics → bar + line charts (30-day signups & orders)

All pages include loading / error / empty states. All responses parsed consistently as res.data?.data ?? res.data.

useCart.ts — Zustand cart store implemented

Was a broken re-export of useAuth causing 3 TypeScript errors. Replaced with a proper persisted Zustand store:

const useCartStore = create<CartStore>()(
  persist(
    (set) => ({
      items: [],
      addItem: (product) => set((state) => { /* merge or append */ }),
      removeItem: (productId) => set(...),
      updateQuantity: (productId, quantity) => set(...),
      clearCart: () => set({ items: [], count: 0, total: 0 }),
    }),
    { name: 'willbry-cart' }
  )
)

Other fixes

• Added missing /admin/users/:id route to the router
• Removed unused Settings imports from AdminDashboard and AdminUsers
• Added INTEGRATION_REPORT.md at repo root documenting endpoints, auth flow, limitations, and local setup

Original prompt

You MUST continue existing PR work; do not restart from main and do not overwrite prior work.

Repository: Alouzious/willbry
Branch to work on: copilot/connect-frontend-to-backend
Target: Continue PR #3 titled "[WIP] Connect frontend to backend for API integration".

Context:

• PR already has partial integration work (+1,264 / -674).
• Public pages partly connected: ProductsPage, BlogPage, BlogPostPage, GalleryPage, FarmerDirectoryPage.
• Portal pages partly connected: PortalDashboard, PortalOrders, PortalOrderDetail, PortalResources, PortalFarmProfile, PortalMarketPrices, PortalBookings, PortalSettings.
• Some admin work started: AdminDashboard, AdminUsers, AdminUserDetail. Many other admin pages still stubs.
• Backend updates started: auth register now creates refresh_token; blog endpoints now return author_name using BlogPostWithAuthor model.

Tasks (must all be completed):

A) Analyze current branch vs main

1. Identify completed integrations.
2. Identify partially implemented pages.
3. Identify remaining admin stubs.
4. Identify frontend API calls that do not match backend routes.
5. Identify backend routes still missing that frontend needs.

B) Finish integration end-to-end

1. COMPLETE REMAINING ADMIN PAGES by replacing stubs with real API integration:

• AdminDashboard, AdminUsers, AdminUserDetail (verify correctness)
• AdminOrders
• AdminInquiries
• AdminBlog
• AdminBlogEditor
• AdminProducts
• AdminGallery
• AdminResources
• AdminFarmers
• AdminPrices
• AdminAiConfig
• AdminAnalytics

2. VERIFY FRONTEND API CALLS match backend routes:

• willbry-frontend/src/lib/api.ts
• willbry-frontend/src/context/AuthContext.tsx
• willbry-frontend/src/hooks/*
• willbry-frontend/src/pages/public/*
• willbry-frontend/src/pages/portal/*
• willbry-frontend/src/pages/admin/*
  Ensure consistent parsing: const data = res.data?.data ?? res.data.

3. VERIFY BACKEND ROUTES exist and match.
   Inspect:

• willbry-backend/src/main.rs
• willbry-backend/src/handlers/*
• willbry-backend/src/models/*
• willbry-backend/migrations/*
  If frontend needs an endpoint that backend does not have, add it properly with handler + model + route + migrations if needed.

4. Remove dummy data wherever backend support exists.

5. Fix data shape mismatches with aligned TS types and safe optional handling.

6. Auth flow:

• login/register must work
• access_token + refresh_token stored
• user stored
• Bearer token auto-attached
• /portal requires login
• /admin requires user.role === "admin"
• backend admin endpoints enforce admin role

7. Loading + error + empty states for every connected page.

C) Final verification (REQUIRED)

• Run cd willbry-frontend && npm run build and fix all errors.
• Run cd willbry-backend && cargo check and fix all errors.
  Do NOT claim completion until both pass.

D) Update INTEGRATION_REPORT.md at repo root
Include:

• completed integrations and pages connected
• endpoints matched and backend endpoints added/fixed
• remaining limitations
• how to run frontend/backend locally
• how to create or test admin access
• frontend build result
• backend cargo check result

Strict rules:

• Do NOT redesign UI.
• Do NOT remove pages.
• Do NOT restart from main.
• Do NOT replace previous work.
• Do NOT leave TODOs.
• Finish the implementation, not just planning.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: @copilot continue from Pull Request #3 on branch copilot/connect-frontend-to-backend.

PR title: [WIP] Connect frontend to backend for API integration.

IMPORTANT:
This PR already has partial integration work:

• +1,264 additions and -674 deletions
• frontend public pages were partly connected
• portal pages were partly connected
• admin pages were inspected but many are still stubs
• previous agent stopped because of weekly rate limit

Do NOT restart.
Do NOT recreate the project.
Do NOT overwrite the work already done.
Continue exactly from the current PR branch:
copilot/connect-frontend-to-backend

First analyze the current branch and compare with main:

• identify completed integrations
• identify partially implemented pages
• identify remaining admin stubs
• identify frontend API calls that do not match backend routes
• identify backend routes still missing

Then finish the integration.

Mission:
Fully connect frontend and backend across public, portal, and admin flows.

Focus:

1. COMPLETE REMAINING ADMIN PAGES

• Replace stub admin pages with real API integration.
• Connect AdminDashboard, AdminUsers, AdminUserDetail, AdminOrders, AdminInquiries, AdminBlog, AdminBlogEditor, AdminProducts, AdminGallery, AdminResources, AdminFarmers, AdminPrices, AdminAiConfig, AdminAnalytics.

2. VERIFY FRONTEND API CALLS
   Check:

• src/lib/api.ts
• src/context/AuthContext.tsx
• src/hooks/*
• src/pages/public/*
• src/pages/portal/*
• src/pages/admin/*
  Make sure every API call matches a real backend route.

3. VERIFY BACKEND ROUTES
   Check:

• willbry-backend/src/main.rs
• willbry-backen...

This pull request was created from Copilot chat.