docs: add video recording guide + rework visual-testing

[goosewobbler]

Summary

Originally this PR added a single new doc — docs/video-recording.md — recommending wdio-video-reporter as the companion to docs/visual-testing.md (PR #266): video is the debugging artefact, visual is the regression signal.

Scope expanded mid-review to trim and reframe both ecosystem-integration guides so they scale as new framework services land from the roadmap, without needing per-doc maintenance.

Changes

Original: new video-recording guide

• Quick-start config; pnpm onlyBuiltDependencies snippet for @ffmpeg-installer/*.
• Honest framing: screenshot-stitching at command granularity, 3–10 fps slideshow — not a real video pipeline.
• Tauri provider matrix (embedded everywhere; official Linux + Windows — note that unlike the visual cell, the Linux + official combo here works because the reporter has no before() script; crabnebula macOS only, excluded from hosted macOS CI for the TCC reason).
• Cross-links in packages/electron-service/README.md and packages/tauri-service/README.md.

Expanded scope: trim + reframe both guides (commits 3dfc336, b6cfb24)

• Trim: replaced parallel Electron + Tauri config blocks with a single service-agnostic snippet showing only the new entry the user adds (reporter or visual service), with ...subdirs parameterised. Cut install/wire-in/spec boilerplate that paraphrased upstream. ~30% line reduction in each doc.
• Reframe: dropped the "Both @wdio/electron-service and @wdio/tauri-service compose with X" opener in favour of "WDIO's service architecture lets services compose freely — no special integration needed." Framework names are now illustrative examples (mock-API snippets, Tauri provider notes) rather than canonical enumerations. When new framework services land, the docs already cover them — only framework-specific sections need additions.

What stays foregrounded

The valuable, can't-find-anywhere-else content:

• Tauri provider × OS matrix in both docs.
• CrabNebula × macOS-CI Screen Recording known issue.
• official × Linux × executeAsync hang (visual only — explicitly noted as not hit by video).
• Windows ~0.5% subpixel noise + MAX_MISMATCH_PCT = 1 rationale (visual).
• pnpm onlyBuiltDependencies for @ffmpeg-installer/* (video).
• Mock-API handoff for native UI surfaces, framed as framework-service-agnostic with Electron/Tauri as examples (visual).

Test plan

• Render-check both docs on GitHub — table layout, code blocks, link targets.
• Click every cross-link: upstream tool docs, GitHub repos, example repo, sibling doc back-link, mock-API references in packages/*/docs/.
• Confirm Video Recording pointer shows under per-package README sections (Operations on electron, Guides on tauri).
• Skim both docs end-to-end: a reader arriving cold should be able to wire up the feature without bouncing to upstream for everything.

Companion

• Validated by goosewobbler/wdio-desktop-mobile-example#124 — all 16 video cells passed (electron × 3 OSes × 3 packages, tauri-embedded × 3 OSes, tauri-official × Linux + Windows, tauri-crabnebula × Linux + Windows). Surprising-positive: tauri-official on Linux works for video even though it's broken for visual.
• Companion to existing docs/visual-testing.md (PR docs: add visual regression testing guide #266).

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR adds a new docs/video-recording.md guide for wdio-video-reporter integration and reworks docs/visual-testing.md to be framework-agnostic, replacing per-framework config blocks with a single service-agnostic snippet. Cross-links are added to all three package READMEs.

• New video-recording guide covers install quirks (pnpm onlyBuiltDependencies), output-path conventions with Tauri's extra <provider> segment, screenshot-stitching limitations, and the full Tauri provider × OS × CI matrix.
• Visual-testing rework consolidates three framework-specific config blocks into one, merges the Dioxus-only Linux Xvfb section into a shared Tauri + Dioxus section (and correctly switches from 24-bit to 16-bit colour depth), and adds a back-link to the new video guide.
• README cross-links in electron-service, tauri-service, and dioxus-service add a Video Recording pointer alongside the existing Visual Testing entry.

Confidence Score: 5/5

Documentation-only change with no executable code paths; safe to merge.

All five changed files are Markdown documentation. The new video guide is accurate and the visual-testing rework preserves all previously validated technical details while reducing duplication. No production code is touched.

No files require special attention.

Important Files Changed

Filename	Overview
docs/video-recording.md	New guide for wdio-video-reporter integration; accurate provider matrix, Tauri output-path variants, pnpm onlyBuiltDependencies snippet, and known CI issues are all well-documented.
docs/visual-testing.md	Reworked to a framework-agnostic single config snippet; Linux Xvfb section now correctly recommends 16-bit depth (fixing the old 24-bit Dioxus recommendation); cross-links to video guide added.
packages/electron-service/README.md	One-line addition: Video Recording link inserted in the Operations section alongside existing Visual Testing entry.
packages/tauri-service/README.md	One-line addition: Video Recording link inserted in the Guides section alongside existing Visual Testing entry.
packages/dioxus-service/README.md	One-line addition: Video Recording link appended to the Guides section.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[WDIO Test Run] --> B{Framework Service}
    B --> C[electron-service]
    B --> D[tauri-service]
    B --> E[dioxus-service]
    C --> F[Visual Testing]
    D --> F
    E --> F
    C --> G[Video Recording]
    D --> G
    E --> G
    D --> L{Tauri Provider}
    L --> M[embedded]
    L --> N[official]
    L --> O[crabnebula]
    F --> P[Output: __visual__ / platform / arch / provider]
    G --> Q[Output: __video__ / platform / arch / provider]

Loading

_{Reviews (7): Last reviewed commit: "docs: refine review fixes — autoXvfb cre..." | Re-trigger Greptile}

[github-actions]

Release Preview — no release

No bump label detected.
Reason: No release labels found (need bump:* or release:stable)
Note: Add bump:patch, bump:minor, or bump:major to trigger a release.

---

Updated automatically by ReleaseKit