4bc918af7a
The public search API accepts agent_ids / session_ids, and the chat reader applies them, but the coding path dropped both before calling the store. A caller that relies on agent or session boundaries could therefore recall facts and experiences written by another agent or session of the same user. Accept the id lists in the coding store, filter them with IN clauses and in the post-fetch checks, and forward them from _search_coding. Singular agent_id / session_id stay supported for existing callers. Add store-level and client-level regressions for the filtered scopes. Co-authored-by: qiye.sjh <shijiahao_0802@youzan.com> Co-authored-by: Claude Code <noreply@anthropic.com>