fix: refresh Memory Space cards over trusted read RPC

[Grivn]

Summary

• route card-level Memory Space reconnects through the trusted-host read channel
• allow the read-only health refresh in remote and read-only WebUI sessions
• retain the previous loopback write endpoint as an older-client compatibility route
• document the corrected RPC boundary in English and Chinese

Root cause

The overview full sync used the trusted-host read channel, but clicking a Memory Space card sent the status refresh to the loopback-only write channel. Non-loopback WebUI connections therefore surfaced a transport-level Failed to fetch even though the full sync succeeded. The operation only invalidates transient health cache state and reads one Provider status; it does not mutate persistent data.

Verification

• pnpm run verify
• 319 tests passed; 1 conditional Windows smoke test skipped
• deterministic build, Headless profile, package contents, publint, and package type checks passed