Add AI-assisted QA test workflow: scenario cards, runner, hooks, API capture

A complete loop for defining, generating, running and gating tests:

- qa/: scenario-card template + examples (API/UI/binding), the Claude
  generation prompt, and a QA runbook tying it together
- e2e/CLAUDE.md: conventions that keep AI-generated tests consistent
- run-tests.ps1: one runner for every layer (backend/api/web/ui/binding),
  logs per run under .testlogs/, JUnit output, evidence report, and a
  re-seed guard against stale demo data
- .githooks/ + scripts/install-hooks.ps1: pre-commit secret scan and
  pre-push unit tests (shift-left before CI)
- evidence report now captures each API call's request, payload and
  response (Authorization redacted); JUnit reporter added for CI
- scripts/db.mjs: db:check freshness guard

Azure DevOps pipeline deferred; the runner already emits JUnit + the
evidence report for any CI to publish.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

qa/scenarios/SRCH-003-sort-by-fare.yml

@@ -0,0 +1,25 @@
+id: SRCH-003
+title: Flight results sort by lowest fare
+layer: ui
+area: Searching for flights
+risk: low
+owner: qa
+
+preconditions:
+  - signed in as agent@skyline.test / skyline
+  - more than one flight on JFK -> LHR
+
+steps:
+  given: the agent has searched JFK -> LHR
+  when: they choose "Lowest fare" from the sort control
+  then: the fares shown are in non-decreasing order down the page
+
+evidence:
+  - screenshot of the sorted results
+  - the ordered list of fares read off the page (recorded data)
+  - the GET /api/flights?sort=price request and response
+
+data:
+  origin: JFK
+  destination: LHR
+  sort: price