Add mobile app, map-core, nearby sync, and activity recording specs

mobile-app: Unified React Native + Expo app combining Planner and
Journal. OAuth2 PKCE auth, MapLibre maps, versioned REST API with
Zod schemas, configurable server URL, offline SQLite, Web Push relay
notifications. TanStack Query + Zustand state management. Jest +
Maestro testing. 76 tasks across 5 phases.

map-core-package: Extract renderer-agnostic map definitions (tiles,
color palettes, POI categories, z-index) into @trails-cool/map-core.
Pure refactor preparing for MapLibre on mobile. 27 tasks.

mobile-activity-recording: GPS recording, live stats, HealthKit/Health
Connect export. Separated from mobile-app for independent scheduling.

mobile-nearby-sync: BLE route sync between nearby devices for offline
group riding. QR waypoint sharing as simpler v1. TXQR noted as future.

journal-rest-api spec: Full API contract — endpoints, auth, pagination,
errors, discovery, versioning, BRouter proxy.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

openspec/changes/mobile-app/specs/mobile-testing/spec.md

@@ -0,0 +1,26 @@
+## ADDED Requirements
+
+### Requirement: Unit and component testing with Jest
+The mobile app SHALL use Jest + jest-expo + React Native Testing Library for unit and component tests.
+
+#### Scenario: Unit tests run
+- **WHEN** `pnpm test` is run in the mobile workspace
+- **THEN** Jest executes all `*.test.ts(x)` files with jest-expo preset
+
+#### Scenario: Component rendering tests
+- **WHEN** a component test renders a screen with React Native Testing Library
+- **THEN** the test can query by accessibility label, text, and testID without a device
+
+### Requirement: E2E testing with Maestro
+The mobile app SHALL use Maestro for end-to-end flow testing on real/emulated devices.
+
+#### Scenario: Maestro flow execution
+- **WHEN** a Maestro YAML flow is run against a development build
+- **THEN** the flow interacts with the app via the accessibility layer (tap, scroll, assert text)
+
+#### Scenario: E2E in CI
+- **WHEN** a PR is opened
+- **THEN** Maestro E2E flows run against an EAS preview build
+
+### Requirement: No Vitest for mobile
+Vitest SHALL NOT be used for the mobile app. React Native Testing Library has incomplete Vitest support — Jest with jest-expo is the stable, Expo-recommended choice.