memory: strip inbound metadata envelopes from user messages in session corpus

[zqchris]

Summary

Session corpus ingestion was feeding raw Telegram/Discord/Slack inbound envelopes into the dreaming corpus unchanged. Each user message in the transcript carries a ~338-char `Conversation info` + `Sender` JSON prefix built by `buildInboundUserContextPrefix`, which exceeds the `SESSION_INGESTION_MAX_SNIPPET_CHARS` (280) cap used downstream in `dreaming-phases.ts`. Result: the user's actual words never made it into the corpus, and REM topic extraction latched onto envelope words like `assistant` / `untrusted metadata` as the top "topics".

Root cause is ordering in `buildSessionEntry` → `extractSessionText`: `normalizeSessionText` collapses newlines to spaces per text block, and once newlines are gone, `stripInboundMetadata` can no longer locate sentinel lines or fenced-json blocks. So stripping must happen before normalization, and only for `user` role (assistant messages may legitimately discuss envelope formats).

Changes

• `src/memory-host-sdk/host/session-files.ts`: add `role` parameter to `extractSessionText`; strip inbound metadata on user-role text blocks before `normalizeSessionText` runs.
• `src/memory-host-sdk/host/session-files.test.ts`: new test using a real multi-line Telegram envelope asserts the corpus entry contains only the actual user text; separate test confirms assistant messages containing sentinel-like text are preserved untouched.

Test plan

• `pnpm test src/memory-host-sdk/host/session-files.test.ts` — 8/8 passing (6 existing + 2 new)
• `pnpm check` — clean (lint, format, type, import cycles, madge, webhook/auth guards)
• Manual verification on next dreaming cycle: REM topics should reflect real user words instead of envelope noise

[greptile-apps]

Greptile Summary

This PR fixes a corpus-ingestion bug where raw inbound metadata envelopes (prepended by buildInboundUserContextPrefix for Telegram/Discord/Slack messages) were being fed into the dreaming corpus unchanged, causing SESSION_INGESTION_MAX_SNIPPET_CHARS truncation to cut the actual user text entirely. The fix — stripping the envelope before normalizeSessionText collapses newlines — is correct and well-targeted, and the new tests directly cover the root-cause ordering constraint.

Confidence Score: 5/5

• Safe to merge; the fix is correct and well-tested with no production-affecting issues.
• All remaining findings are P2. The only notable gap is that the parallel packages/memory-host-sdk/src/host/session-files.ts copy was not updated, but it is not exported or used in any production code path so it poses no current risk.
• packages/memory-host-sdk/src/host/session-files.ts — parallel standalone copy not updated with this fix.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: src/memory-host-sdk/host/session-files.ts
Line: 188

Comment:
**Parallel copy in `packages/` not updated**

`packages/memory-host-sdk/src/host/session-files.ts` is a separate standalone implementation (not a re-export facade like the rest of the package) and was not patched. It still calls `extractSessionText(message.content)` without passing `message.role` and has no `stripInboundMetadata` import. While that copy is currently unexported and not on any production code path, if it is ever promoted or wired up the corpus-truncation bug will silently return.

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "memory: strip inbound metadata envelopes..." | Re-trigger Greptile}

[greptile-apps]

Parallel copy in packages/ not updated

packages/memory-host-sdk/src/host/session-files.ts is a separate standalone implementation (not a re-export facade like the rest of the package) and was not patched. It still calls extractSessionText(message.content) without passing message.role and has no stripInboundMetadata import. While that copy is currently unexported and not on any production code path, if it is ever promoted or wired up the corpus-truncation bug will silently return.

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/memory-host-sdk/host/session-files.ts
Line: 188

Comment:
**Parallel copy in `packages/` not updated**

`packages/memory-host-sdk/src/host/session-files.ts` is a separate standalone implementation (not a re-export facade like the rest of the package) and was not patched. It still calls `extractSessionText(message.content)` without passing `message.role` and has no `stripInboundMetadata` import. While that copy is currently unexported and not on any production code path, if it is ever promoted or wired up the corpus-truncation bug will silently return.

How can I resolve this? If you propose a fix, please make it concise.

[zqchris]

Addressed Greptile's P2: applied the same strip to the parallel packages/memory-host-sdk/src/host/session-files.ts copy in ab90812. That file isn't currently exported or on any production code path, but keeping the two copies consistent prevents a silent regression if it ever gets wired up later.

[jalehman]

Merged via squash.

• Prepared head SHA: 98562b2a84450b039d78034fcb10122edafc235f
• Merge commit: 82e349a48ad9b672c18d0eec5057d51c8ceafbd8

Thanks @zqchris!