Keep delegation pipeline-entries sibling-only

[cursor]

Problem

The orchestrator seeds sub-agents with a pipeline-entries snapshot so they can see what siblings just wrote via /mem add. The handler sets EntryFilter.conversation_id and comments that this must stay conversation-scoped (it already returns empty when there is no conversation, rather than dumping tenant-wide history).

list_entries still applies an OR-NULL fallback: conversation_id = ? OR conversation_id IS NULL. That is correct for agent /mem browse and HTTP list (pre-migration / unscoped rows stay visible). It is wrong for this probe.

HTTP POST /v1/memory and CLI /mem add with no conversation write conversation_id NULL. Those rows then appear in the sibling snapshot and are paraphrased as fresh pipeline output. Post-filtering after LIMIT 15 is not a fix: a flood of unscoped rows can hide the actual sibling entries.

Fix

Add EntryFilter.exact_conversation. When set, both the browse and FTS paths use conversation_id = ? only. pipeline-entries opts in. Default list behavior is unchanged.

Tests

unit_memory_entries — exact filter excludes unscoped and other-conversation rows; LIMIT over a flood of unscoped rows still returns the sibling; FTS path uses the same predicate.

Independently mergeable against main. Touches EntryFilter / list_entries SQL (different hunks from #322's list_conversations cursor) plus api_server.cpp pipeline-entries and CHANGELOG [Unreleased]. Rebase CHANGELOG after whichever sibling merges first.

  

---

Note

Low Risk
Scoped SQL filter change behind an opt-in flag on one orchestration probe; default memory list/search semantics are unchanged.

Overview
Fixes delegation pipeline-entries context bleeding unscoped memory into sub-agent snapshots.

Adds EntryFilter.exact_conversation. When set with a positive conversation_id, list_entries (browse and FTS) uses conversation_id = ? only instead of the usual OR-NULL fallback that keeps HTTP /v1/memory and CLI /mem add rows visible everywhere. The orchestrator pipeline-entries probe opts in so siblings only see conversation-pinned /mem add output; default /mem browse and HTTP list behavior is unchanged.

Tests cover exclusion of unscoped/other-conversation rows, LIMIT under unscoped floods, and the FTS path.

^{Reviewed by Cursor Bugbot for commit 50d4e51. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_eab4fa72-4096-429b-8a48-3aef61402808)