feat(mobile): connect orders and reservations flow to backend

[masch]

Pull Request Template

Linked Issue

Closes #211

Summary

• Connects the mobile client to the new backend endpoints (/v1/orders and /v1/reservations) with type-safe operations.
• Implements a 2-step booking flow with automated rollback (cancels reservation if order creation fails) in REST mode.
• Refactors REST services (RestOrderService and RestProductService) to use the new apiClient helper injecting the auth token.
• Cleans up and archives the SDD planning artifacts for both connect-mobile-orders-api and orders-endpoints-booking-flow sessions.

Changes

File	Change
apps/mobile/src/services/api-client.ts	Created API client with token injection & base URL prefix
apps/mobile/src/services/order.service.ts	Refactored RestOrderService to use client & support Zod DTOs
apps/mobile/src/services/product.service.ts	Refactored RestProductService & threw errors in REST placeOrder
apps/mobile/src/app/tourist/booking.tsx	Implemented 2-step booking flow + reservation rollback
openspec/changes/archive/	Archived both SDD changes and added archive-report.md

Test Summary

✅ PASS: 532 total tests, make check successful

Contributor Checklist

• Linked an approved issue
• Added exactly one type:* label
• Ran make check and tests pass
• Conventional commit format
• No Co-Authored-By trailers

[github-actions]

React Doctor

Score: 87 / 100

react-doctor v0.2.4

✔ Select projects to scan › impenetrable-mobile
Scanning changes: issue-211/connect-mobile-orders-api → main

Scanning /home/runner/work/impenetrable-connect/impenetrable-connect/apps/mobile...



  ⚠ react-doctor/no-giant-component                ×3
      Component "ProjectFormScreen" is 365 lines — consider breaking it into smaller focused components
      → Extract logical sections into focused components: `<UserHeader />`, `<UserActions />`, etc.
      src/app/admin/project/[id].tsx:55
      src/app/tourist/booking.tsx:41
      src/app/tourist/index.tsx:29

  ⚠ react-doctor/prefer-useReducer                 ×2
      Component "BookingScreen" has 7 useState calls — consider useReducer for related state
      → Group related state: `const [state, dispatch] = useReducer(reducer, { field1, field2, ... })`
      src/app/tourist/booking.tsx:41
      src/app/tourist/index.tsx:29

  ⚠ react-doctor/jsx-no-jsx-as-prop
      JSX prop receives JSX created on every render — extract it or memoize to avoid re-renders.
      → Hoist the inner JSX outside the render or memoize via `useMemo`.
      src/app/tourist/booking.tsx:342

  ⚠ react-doctor/rn-no-scrollview-mapped-list
      <ScrollView> rendering items.map(...) — use FlashList, LegendList, or FlatList so only visible rows mount
      → Use FlashList, LegendList, or FlatList — `<ScrollView>{items.map(...)}</ScrollView>` mounts every row in memory
      src/app/tourist/booking.tsx:453

  ⚠ react-doctor/rendering-hydration-mismatch-time
      new Date() reachable from JSX renders differently on server vs client — wrap in useEffect+useState (client-only) or add suppressHydrationWarning to the parent if intentional
      → Wrap dynamic time/random values in useEffect+useState (client-only) or add suppressHydrationWarning to the parent if intentional
      src/app/tourist/index.tsx:422

  ⚠ react-doctor/no-generic-handler-names
      Non-descriptive handler name "handleChange" — name should describe what it does, not when it runs
      → Rename to describe the action: e.g. `handleSubmit` → `saveUserProfile`, `handleClick` → `toggleSidebar`
      src/components/DatePicker.tsx:283

  ┌─────┐  96 / 100 Great
  │ ◠ ◠ │  ████████████████████████████████████████████████░░
  │  ▽  │  React Doctor (www.react.doctor)
  └─────┘

  9 issues across 4/23 files  in 1.4s
  Full diagnostics written to /tmp/react-doctor-ba92251e-63e9-4330-a10c-655ff5cac3f6

[masch]

🥦

[masch]

🥦

[masch]

🥦