# v96 RC19 QA

## Automated checks
- `node -c assets/js/app.js`: OK
- `node -c assets/js/shell.js`: OK
- `node qa_check.js`: OK
- Core asset scan: OK after filtering dynamic template-string URLs; no missing direct local assets in HTML/CSS/core JS.

## Browser screenshot status
Actual Chromium/Playwright screenshots could not be produced in this sandbox. Attempts were made with:
- system Chromium CLI
- Playwright with `/usr/bin/chromium`
- local HTTP URL
- file URL
- data URL

The browser returned `net::ERR_BLOCKED_BY_ADMINISTRATOR` for HTTP, file and data URLs, and the CLI renderer also hung previously. Because of that, the package includes static fallback/target images for mobile, iPad and desktop in `docs/`, but these are not true live DOM screenshots.

## Included visual references
- `QA_v96_RC19_mobile_static_target.png` — approved visual target for the mobile progress module.
- `QA_v96_RC19_ipad_static_target.png` — approved visual target for iPad full dashboard direction.
- `QA_v96_RC19_desktop_static_target.png` — same visual target used as desktop reference until live DOM screenshot can be produced outside the sandbox.
- `QA_v96_RC19_*_static_fallback.png` — deterministic fallback render attempts, included only for traceability.

## Internal visual assessment
RC19 specifically addresses the real app issues reported from iPhone screenshots:
- Hero chip icons should no longer render as large empty dark ovals.
- `Starta pass` should stay on one line.
- Mobile `Framgångsmätare` should no longer collapse into a tall single-column stack.
- `4 av 12 pass` should retain readable spacing and fit next to the main ring.
- KPI values should remain compact in a two-column grid.
- iPad/desktop small metrics should stay unboxed and to the side of phase progress.

## Release confidence
Code-level confidence: high.
Visual confidence: not claimed as 100% because live DOM screenshot rendering was blocked in the sandbox. This RC should be checked on nextnarvik.no / a real browser immediately after upload.
