@alfe.ai/openclaw-chat 0.5.1 → 0.6.1

package/dist/index.d.cts

@@ -11,6 +11,10 @@ import { _ as AlfeResolvedAccount, g as AlfePluginConfig, h as AlfeChannelConfig
  * Each session file contains metadata and the full message history.
  * Sessions are written on every message to ensure durability.
  * Old sessions are cleaned up automatically (30-day TTL, 1000 max).
+ *
+ * NOTE: the storage path and SessionData shape are a read contract —
+ * packages/openclaw-memory-cloud/src/session-backfill.ts reads these files
+ * directly (the memory plugin can't depend on this package). Keep in sync.
  */
 interface ChatMessage {
   role: 'user' | 'assistant';
@@ -57,8 +61,24 @@ interface SessionData {
   createdAt: string;
   updatedAt: string;
   messages: ChatMessage[];
-  /** Absent on session files written before activity persistence shipped. */
+  /**
+   * Fallback activity records (see appendActivity). The PRIMARY history
+   * source is OpenClaw's own session transcript (transcript-activity.ts) —
+   * these records serve conversations whose transcript is missing
+   * (deleted / rotated / compacted). Absent on pre-persistence files.
+   */
   activity?: ChatActivityRecord[];
+  /**
+   * OpenClaw route(s) this conversation dispatched through, captured per
+   * turn — the exact transcript lookup keys for transcript-backed history.
+   * Multiple entries occur for group conversations (per-peer dm scope
+   * yields one OpenClaw session per sender). Absent on old files (the
+   * transcript index `:conv:` scan covers those retroactively).
+   */
+  routes?: {
+    sessionKey: string;
+    storePath: string;
+  }[];
 }
 interface SessionSummary {
   sessionId: string;

package/dist/index.d.ts

@@ -11,6 +11,10 @@ import { _ as AlfeResolvedAccount, g as AlfePluginConfig, h as AlfeChannelConfig
  * Each session file contains metadata and the full message history.
  * Sessions are written on every message to ensure durability.
  * Old sessions are cleaned up automatically (30-day TTL, 1000 max).
+ *
+ * NOTE: the storage path and SessionData shape are a read contract —
+ * packages/openclaw-memory-cloud/src/session-backfill.ts reads these files
+ * directly (the memory plugin can't depend on this package). Keep in sync.
  */
 interface ChatMessage {
   role: 'user' | 'assistant';
@@ -57,8 +61,24 @@ interface SessionData {
   createdAt: string;
   updatedAt: string;
   messages: ChatMessage[];
-  /** Absent on session files written before activity persistence shipped. */
+  /**
+   * Fallback activity records (see appendActivity). The PRIMARY history
+   * source is OpenClaw's own session transcript (transcript-activity.ts) —
+   * these records serve conversations whose transcript is missing
+   * (deleted / rotated / compacted). Absent on pre-persistence files.
+   */
   activity?: ChatActivityRecord[];
+  /**
+   * OpenClaw route(s) this conversation dispatched through, captured per
+   * turn — the exact transcript lookup keys for transcript-backed history.
+   * Multiple entries occur for group conversations (per-peer dm scope
+   * yields one OpenClaw session per sender). Absent on old files (the
+   * transcript index `:conv:` scan covers those retroactively).
+   */
+  routes?: {
+    sessionKey: string;
+    storePath: string;
+  }[];
 }
 interface SessionSummary {
   sessionId: string;