[leemour]

Core slice of the linked-chats plan (item 4.3 of the evidence follow-ups; owner answers NEED-1575 A, NEED-1576 A).

What changes

gatherProjectEvidence

• Request: linkedChats?: { provider: string; account: string; chat: string }[] (at most 16). These are the host's confirmed member-of links. Core checks only their shape and refuses one chat given twice.
• Each chat is matched to the selected source of its own account (mail for provider: "email", otherwise message). If its account is not in sources, the chat is never read and there is no fallback to another account.
• Each chat in scope gets its own lane: { id, kinds: ["linked-chat"], query: null, people: [], chat: "chat:<provider>/<account>/<chat>" }. Its ids come after the word lanes. It has one unit per 90-day chunk, and those units come after all word units, so in each round a word lane labels a shared hit first.
• Items: context: "linked-chat", the first 300 characters as the excerpt, and no around. When several lanes find a reference it keeps the strongest context: project > linked-chat > person-only.
• Result: linkedChats: [{ provider, account, chat, ref, source: number | null, lane: string | null, state: "in-scope" | "out-of-scope" | "unavailable" }].
• Checkpoint stays version: 1. A run without linked chats keeps its old fingerprint and checkpoint. A run with linked chats stores the optional linkedChats hash. If the links changed, the run is refused with "the project's linked chats changed; start again without --cursor".

Context reader: an optional chat takes the place of query. It reads one chat or mail thread, newest first, and also reads a chat hidden from search. It reports coverage.matching: "chat" and index: "ready" (no word index is used), and available: false when the chat is not stored. It is refused together with query and on document or meeting sources. The cursor scope includes chat only when one is given, so old cursors stay valid.

knowledge.relate: a chat reference may be the from of member-of to a project:, and confirmRelation works on that link. The account comes from the reference itself. A scope key for another account is refused, and a chat cannot be related to anything else.

Also

• contextRecords.read now resolves messages in chats hidden from search, so evidence from a linked hidden chat can be staged.
• Fix: a resumed gathering read nothing when every open unit already had at least one page.

Checks

pnpm typecheck, pnpm lint, pnpm docs:check, the full pnpm test (5850 passed, 14 skipped) and bun run scripts/smoke.ts, all sandboxed.

🤖 Generated with Claude Code

[leemour]

Resume fix verified on the new large-document benchmark (cli-testing#185): memo projects evidence LNW --max-pages 2 continued with --cursor, same Memo main (8183d1e), synthetic store.

Core	Invocations	References	Outcome
0.371.0	4	4 of 9	stalls (0 bytes, same checkpoint)
main 48c2ea4 (0.374.0, without this PR)	4	4 of 9	stalls
this PR c951474	7	9 of 9, 0 duplicates	completes; bytes equal to one run

So the stall is fixed by this PR alone.

🤖 Generated with Claude Code