Greptile Summary

This PR fixes a transcript-leak bug where the pre-compaction memory-flush prompt was being saved as a normal user message in chat.history/session transcripts. The fix adds transcriptPrompt: "" to the single runEmbeddedPiAgent call in agent-runner-memory.ts, which routes through the existing resolveRuntimeContextPromptParts mechanism: an empty transcriptPrompt with a non-empty effectivePrompt produces runtimeOnly: true, injecting the flush prompt only into the system-prompt runtime-event context and keeping it out of the user-visible message history. The runtime-context-prompt.test.ts already covers this code path at unit level, and the two new assertions verify the parameter is correctly plumbed.

Confidence Score: 5/5

Safe to merge — the one-line fix correctly uses the established runtimeOnly mechanism and has adequate layered test coverage.

The change is minimal (one added field), the underlying resolveRuntimeContextPromptParts path for transcriptPrompt: '' is already unit-tested in runtime-context-prompt.test.ts, and no logic in attempt.ts is altered. No P0 or P1 issues found.

No files require special attention.

_{Reviews (1): Last reviewed commit: "fix(memory): keep pre-compaction flush p..." | Re-trigger Greptile}

Thanks for the Aisle pass. I checked this before landing.

I’m leaving transcriptPrompt: "" as-is because a non-empty marker would recreate the reported bug: this transcript field is consumed as a user-visible/user-turn prompt, and the pre-compaction flush is an internal maintenance run, not a user message.

The run is still tagged on the internal path via trigger: "memory", constrained to memoryFlushWritePath, and persisted with the existing memory-flush session metadata (memoryFlushAt / memoryFlushCompactionCount). So this is intentional runtime-only context, not an external prompt-hiding bypass.