Use WeakRef on renderer side of remote

Editor assessment

The subject is technically precise: the renderer side of the remote module now uses WeakRef. A reader familiar with the codebase infers the goal is lifetime-safe references, but the message never says so, and no body exists to confirm or explain the trade-offs. The refactor type is right, and no scope is attached even though remote is an obvious candidate. No footers appear, and hygiene is acceptable with imperative phrasing and no trailing period. Everything necessary to understand what changed is present; everything needed to understand why is missing. A mechanical message with modest instructional value.