Error Feedback Service + friendly error handling across all pages

- Error Feedback Service: POST /api/feedback saves to JSONL, GET with admin token
- ErrorFeedback component: warm amber tones, friendly messages, 'Report Issue' button
- Replaced ALL red-themed error displays across 15+ pages with ErrorFeedback
- Kind classification: network, auth, location, upgrade, default messages
- QA test suite v2: 8-layer testing (system, API, render, scenario, edge, mobile, perf, security)
- Browser-based visual QA with Playwright (Layer 9)

tests/qa-strategy.md

@@ -0,0 +1,27 @@
+# Falah Mobile — QA Test Strategy
+
+## Layers of Testing
+
+```
+Layer 1: SYSTEM   ── HTTP status, route existence, redirects
+Layer 2: API      ── Response shape, data types, error codes
+Layer 3: RENDER   ── Page content validates (no error messages in output)
+Layer 4: FLOW     ── Multi-step user journeys end-to-end
+Layer 5: EDGE     ── Permissions denied, no GPS, offline, first-time
+Layer 6: MOBILE   ── Viewport sizes, touch targets (≥44px), scroll
+Layer 7: REGRESSION ── Compare old behavior vs new
+```
+
+## Key Principle
+**A 200 status code does NOT mean the page works.** Every page must be tested for:
+- Absence of error messages in rendered HTML
+- Expected content elements present
+- API calls return correct data shapes
+- Visual states (loading → success → empty → error) all tested
+
+## Test Automation Priority
+1. API response shape validation (catch mismatch like PrayerApiResponse)
+2. Page content scanning for known error strings
+3. Authenticated flow tests
+4. Permission denied scenarios
+5. Accessibility baseline