recall.ts: unescaped quotes/ellipsis in marker strings cause store miss and raw marker leak

Trap: buildRecallMarker() embeds raw query between double-quotes and raw id before … — looks safe because queries are usually plain text. But if query contains ", MARKER_REGEX (/📚 Searching (.+?) for "(.+?)"…/) truncates the captured group at the first inner quote; recallStoreKey() produces a mismatched key; store.get(key) returns undefined; the marker is left as raw text in the conversation visible to the upstream LLM. Same issue for id containing …. Fix: escape " → \" in buildRecallMarker() and unescape in parseRecallMarker(); for IDs, percent-encode or strip … before embedding.