fix(e2e): repair settings-scroll script (url assets + dev-surface gating)

[muzimu217]

Summary

The settings-scroll E2E has been unrunnable on main since 2026-09-28, due to two independent breakages stacked on top of each other (invisible to CI because E2E scripts are not in the gate set):

1. Build failure since ef9aae83a (live voice sessions): live-call-controller.ts imports ./pcm-worklet.js?url, which the script's bare-esbuild bundle cannot resolve — No matching export in "…/pcm-worklet.js?url" for import "default". This adds the same local-url-assets plugin that e2e-composer-paste.mjs, e2e-transcript-render.mjs and friends already use.

2. Assertion failure since 07bc80261 (expose Live Voice to regular users): the developmentOnly nav gating (settings-search.ts) hides the sync (Cloud sync) destination even with developer mode on, because the fixture defines import.meta.env.DEV: "false" (packaged semantics) — so includeDevelopmentOnly=false (SettingsPage.tsx:94) and the "Cloud sync must appear in settings search with developer mode" check can never pass. The fixture now runs with DEV semantics, matching how those surfaces are gated in a dev build; the developerOnly gate (absent without developer mode) is unchanged and still asserted.

Verification

• Before: build fails with the ?url error (exit 1).
• Plugin only: build passes, then the Cloud-sync assertion fails.
• Both fixes: SETTINGS_SCROLL {"ok":true, …} — light/dark themes, update preference, and pt-BR locale checks all pass, against a real host binary (PI_DESKTOP_HOST_BIN injected release build).

[vastsa]

Thanks for finding both breakages in the settings-scroll fixture and documenting the failure sequence. Your ?url asset handling and DEV-surface test setup are preserved in #1354. Running the complete fixture on the refreshed candidate exposed one more blocker: the i18n alias pointed at src/index.ts, so package subpaths resolved as invalid paths such as index.ts/locale-info. I updated the alias to the source directory; the isolated Electron E2E now passes all theme, update-preference, and pt-BR checks. #1354 includes your original commit, passed all CI gates, and is merged. Closing this PR as superseded.

[vastsa]

Superseded by merged PR #1354.

[muzimu217]

Thank you for the careful handoff — and apologies for the late acknowledgment on our side.

Two things worth recording from your note:

• Preserving the original commit in fix(e2e): make settings-scroll E2E runnable #1354 and landing it through your refreshed candidate is the better outcome; thank you for finishing it rather than bouncing the PR back.
• The missed blocker is on us: we verified the two breakages we had found but did not run the complete fixture on a refreshed candidate before opening the PR, so the i18n alias defect (src/index.ts resolving to invalid subpaths like index.ts/locale-info) never surfaced in our own runs. Lesson applied going forward: the full target script runs green on the rebased candidate before submission, not just the paths the PR set out to fix.