dsh-context 0.52.1 → 0.53.0

package/lib/index.d.ts

@@ -32,6 +32,15 @@ export declare const Config: z.ZodPreprocess<z.ZodObject<{
   maxFileOps: z.ZodDefault<z.ZodNumber>;
 }, z.core.$strict>>;
 //#endregion
+//#region src/host/activity.d.ts
+/** The persisted fold state (the registry's `stateSchema` contract). */
+interface ActivityState {
+  days: Record<string, {
+    tokens: number;
+    requests: number;
+  }>;
+}
+//#endregion
 //#region src/host/headers.d.ts
 /**
  * One stored tool: the v1 row shape carried the producer description and the
@@ -143,6 +152,14 @@ interface TimelineState {
    * the first human input folds.
    */
   humanInputs?: number;
+  /**
+   * The user's newest own message as a bounded one-line preview (the surface
+   * node's first-text line). Last-wins — a newer human input replaces it, a
+   * text-less one (images only) keeps the previous line. Additive-optional
+   * like the 0.47 fields: cached rows folded before the field existed read
+   * without it and the card just hides its preview line.
+   */
+  lastUser?: string;
   archiveFloor?: number;
   /**
    * The detail collections' revision marker (see ContextTimelineDetail):
@@ -263,10 +280,21 @@ declare module '@deepseek-ai/dsh-session-projection/types' {
      * content of a picked step (key absence = older host: tokens only).
      */
     contextHeaders: ContextHeaders;
+    /**
+     * The per-day activity ledger (billed tokens + completed requests keyed
+     * by local day) behind the Context Dashboard's heatmap — the timeline's
+     * "current snapshot" cannot draw a per-day chart, so the overview reads
+     * this off every session-list row's projection column. Tiny (one small
+     * record per day, retention-capped), so riding every list row costs
+     * nothing next to the timeline head. Key absence = older host: the
+     * heatmap degrades to its empty note.
+     */
+    contextActivity: ContextActivity;
   }
   interface SessionProjectionStateMap {
     contextTimeline: TimelineState;
     contextHeaders: HeadersState;
+    contextActivity: ActivityState;
   }
 }
 /**
@@ -314,6 +342,26 @@ interface TimelineLast {
   total: number;
   prompt?: number;
 }
+/** One day's ledger entry in the `contextActivity` projection. */
+interface ActivityDay {
+  /**
+   * Billed tokens folded from provider-reported usage that day (prompt-side
+   * input + cache read/write + output). Requests without a usage settlement
+   * count only toward `requests` — a fabricated 0 never understates the day.
+   */
+  tokens: number;
+  /** Completed model calls (assistant settlements) that day. */
+  requests: number;
+}
+/**
+ * The per-session daily activity ledger (`contextActivity` wire value):
+ * day key (`YYYY-MM-DD`, host-local — see shared/days.ts) → that day's
+ * billed volume, retention-capped by the fold. The Context Dashboard merges
+ * every listed session's ledger into its activity heatmap.
+ */
+interface ContextActivity {
+  days: Record<string, ActivityDay>;
+}
 interface Snapshot {
   ok: boolean;
   /**
@@ -362,6 +410,13 @@ interface Snapshot {
    * from older hosts; clients treat absence as zero.
    */
   humanInputs?: number;
+  /**
+   * The user's newest own message as a one-line bounded preview (first text
+   * block, whitespace collapsed, ~80 chars): the session cards' footer line.
+   * Additive-optional — absent from rows folded before the field existed
+   * (older hosts, idle sessions' cached rows); clients hide the line then.
+   */
+  lastUser?: string;
   /**
    * Split-generation head fields — present exactly when the host serves the
    * SLIM head (the heavy collections moved to the on-demand detail channel,
@@ -446,6 +501,17 @@ interface Snapshot {
  */
 interface ContextTimelineDetail {
   rev: number;
+  /**
+   * The slim wire head at the SAME fold cut as the collections: the
+   * composition scalars (`current`), the window/model envelope, and the
+   * precomputed counts. Sessions listed cold (never attached since the
+   * requesting unit last changed) carry no `contextTimeline` projection row
+   * for the browser's list reads, so the Agent network card fetches this
+   * head per node to render their composition rings. The host always serves
+   * it; optional so a payload missing it still serves the collections (the
+   * detail cards) and only the ring composition degrades.
+   */
+  head?: ContextTimeline;
   requests: RequestRecord[];
   events: ContextEventRecord[];
   nodes: SurfaceNode[];
@@ -736,4 +802,4 @@ export declare const name = "dsh-context";
 export declare const inject: string[];
 export declare function apply(ctx: Context, config: Config): void;
 //#endregion
-export type { Category, ContextEventRecord, ContextHeaders, ContextTimeline, ContextTimelineDetail, HeaderRecord, HeaderTool, HeadersState, RequestRecord, Snapshot, SurfaceNode, TimelineCounts, TimelineLast, TimelineState };
+export type { ActivityDay, ActivityState, Category, ContextActivity, ContextEventRecord, ContextHeaders, ContextTimeline, ContextTimelineDetail, HeaderRecord, HeaderTool, HeadersState, RequestRecord, Snapshot, SurfaceNode, TimelineCounts, TimelineLast, TimelineState };