## FAIL

### Release blockers

1. **Mobile mapping “Zur Reviewliste” leaves stale detail state in the URL**
   - `scripts/health/assets/health-assets/dashboard-v5.js:574-582` defines the URL as the durable mapping-selection state.
   - `scripts/health/assets/health-assets/dashboard-v5.js:624-627` pushes `mapping=<id>` when opening a detail, but the mobile back action only changes DOM visibility and focus; it does **not** remove `mapping` or create/replace history state.
   - Result: after returning to the list, the URL still represents the detail. Reload reopens the detail, so visible state, URL, reload, and history are incoherent.
   - The new test stops after checking list visibility and never verifies URL/reload after this action: `tests/browser/dashboard_v5_sprint6g_b1.spec.js:25-30`.

2. **The document mobile back action has the same stale-route defect**
   - Detail opening writes `document=<id>`: `scripts/health/assets/health-assets/dashboard-v5-record.js:337`.
   - “Zur Dokumentliste” only toggles local DOM state and focus: `scripts/health/assets/health-assets/dashboard-v5-record.js:339`.
   - Reload therefore restores the document detail rather than the list currently displayed to the user. This undermines the mobile master-detail navigation contract.

3. **Mapping master-detail still depends on legacy closed/detached `<details>` forms**
   - Every mapping editor is first constructed inside a legacy `<details>` element, with only the first opened: `scripts/health/assets/health-assets/dashboard-v5.js:650-653`, `663-779`.
   - The workspace then removes those cards from the DOM and extracts the selected form from the detached card: `scripts/health/assets/health-assets/dashboard-v5.js:802` and `627`.
   - This violates the explicit “no closed details dependency” requirement. The production detail is not independently rendered; failure to locate the backing card silently produces a detail without an editor.

4. **B1 browser coverage is not release-integrated**
   - `tests/browser/dashboard_v5_sprint6g_b1.spec.js` is currently **untracked**.
   - The focused `HEALTH_DASHBOARD_BROWSER_GROUP=b1` branch exists at `tests/browser/run_v5_isolated_matrix.sh:82-85`, but the default/full matrix at `tests/browser/run_v5_isolated_matrix.sh:92-105` never runs B1 and still reports only 13 groups.
   - Thus a normal release matrix can pass without exercising Sprint 6G-B1, and a clean commit could omit the untracked spec.

### Verified

- Focused synthetic B1 browser group: **7 passed**.
- Focused Python tests: **4 passed**.
- JavaScript syntax checks passed for both changed product scripts.
- `git diff --check` passed.
- Existing CSS provides visible `:focus-visible` outlines and general 44px control heights.
- The focused runtime passed its 390px overflow checks, contextual range visibility checks, global search opening, and primary navigation checks.

### Review integrity

- No product files were edited.
- One screenshot changed as a test side effect and was restored; final repository status matches the initial reviewed surface.