Memory recall no longer feeds a session its own transcript notes back to itself.
What's wrong with this entry?
Candidate memory files belonging to the running session are now filtered out, so a session cannot recall its own transcript notes back into itself.
- A predicate passed into memory recall rejects any candidate under
logs/whose basename is<id>.mdor starts with<id>-, where<id>is the first 8 characters of the current session identifier. - Built defensively: returns undefined if the session id cannot be read, in which case no filtering is applied.
if (!r.startsWith("logs/")) return !1;
Strings lifted out of the shipped bundle, so the claim above can be checked against them.