Release asset URL encoding leaves capture-export srcset test red on main

[chubes4]

Reproduction\nAt current main 17b90cc3 (DLA 0.6.10), npx vitest run src/lib/capture-export.test.ts -t "keeps a runtime-selected desktop rendition whose uncaptured sibling embeds the bare original as a prefix" fails without any candidate changes. The test expects literal /IMG_2019.JPG/:/rs=w:1160,h:720.jpg and rs=w:390,h:242.jpg; main now correctly exports browser URLs with %3A, %3D and %2C in those path components after asset-path encoding (#429). CI for unrelated draft PR #438 fails at this inherited test (1 failure, 1375 other tests passed).\n\n## Acceptance\nUpdate the test to assert the actual browser-resolvable encoded portable URLs (including both mobile and desktop renditions and their bytes) rather than the pre-encoding raw path spelling. Prove it fails on current main and passes with the expectation change; leave runtime behavior untouched. Verify the repo test job and avoid weakening the image-selection checks.\n\n## AI assistance\nOpenAI gpt-6-sol via OpenCode inspected failed CI and reproduced the exact failing assertion on an untouched main worktree before drafting this tracker.

[chubes4]

Resolved upstream by merged PR #440 (0dc29385), which updated the browser-encoded srcset fixture while preserving its asset-byte assertions. My Homeboy candidate produced the same scoped test-only correction, so I am retaining that local work as duplicate evidence and will not open a redundant PR. I reproduced the original failure on untouched main before #440 and will rebase/recheck desktop parity PR #438 on the repaired base. AI assistance: OpenAI gpt-6-sol via OpenCode compared the merged fix against the independently verified candidate and prepared this note.