From ec4dab450b4735597a9a0504b071d17facdf3e0c Mon Sep 17 00:00:00 2001 From: Mikael Hugo Date: Sun, 3 May 2026 00:21:06 +0200 Subject: [PATCH] docs(sf): clarify memory-sleeper.ts is NOT part of the memory pipeline MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit memory-sleeper.ts had no file header and the "memory" prefix is misleading — it's a runtime tool-output watchdog (detects repeated bash failures, too-large tool results) that emits steers, completely unrelated to memory-store / memory-relations / memory-embeddings. A contributor reading directory listing top-down would reasonably assume this file participates in the same pipeline as the other memory-*.ts modules. Header now states the historical naming and points readers in the right direction. Co-Authored-By: Claude Opus 4.7 (1M context) --- src/resources/extensions/sf/memory-sleeper.ts | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/src/resources/extensions/sf/memory-sleeper.ts b/src/resources/extensions/sf/memory-sleeper.ts index 03829e659..7735d4496 100644 --- a/src/resources/extensions/sf/memory-sleeper.ts +++ b/src/resources/extensions/sf/memory-sleeper.ts @@ -1,3 +1,12 @@ +// SF Memory Sleeper — runtime tool-output watchdog +// +// Despite the "memory" prefix, this module is unrelated to the +// memory-store / memory-relations / memory-embeddings pipeline. It +// observes tool-result events at runtime and emits a steer (info / +// warning) when patterns like a repeated bash failure or a too-large +// tool result indicate the agent is stuck. Naming is historical — +// "sleeper" means a dormant watcher, not a stored memory. + import type { ToolResultEvent } from "@singularity-forge/pi-coding-agent"; export interface MemorySleeperSteer {