refactor(media): unify file and media previews across clients - #9253

💭 This diff is mostly React/UI code for mobile/web media viewers, so Effect service conventions barely apply. I'm checking the changed .ts files—markdownLinks, mediaSource, mediaActions, mediaReference, state/assets, work-log/presentation, and a deleted workspace-file-image-cache.ts that used Data.TaggedError and Atom—and since that deletion just removes an Effect module, there's no violation there. The state/assets.ts additions use existing subpath import patterns from effect/unstable/reactivity, which matches pre-existing style rather than introducing anything new. I want to look at the full content of assets.ts to confirm there's no new Effect service or Layer definition hiding in there.

1. browse_code — packages/client-runtime/src/state/assets.ts

2. browse_code — packages/client-runtime/src/mediaSource.ts

💭 No Effect service definitions were created or refactored, and nothing violates the conventions, so there are no findings. Since the check defaults to failure but instructs stopping immediately with an exact "All clear" response when there's nothing to report, I need to decide whether to output that directly or go through complete_check first. The explicit instruction not to add title, explanation, punctuation, Markdown, or JSON conflicts with calling complete_check, which would require a summary. I'll follow the direct instruction and respond exactly "All clear".