/** * Durable findings store — survives agent context compaction AND restarts. * * The MCP itself is stateless from the agent's perspective: tools are * idempotent, payloads are self-describing. But long monitoring workflows * still lose user-stated nuance ("ignore stETH dips under 2%", "alert me * only above $10k positions"). Those facts have nowhere to live unless we * give them a home outside conversation memory. * * Storage: JSONL, append-only, at $GRAPH_AAVE_MCP_STATE_DIR/findings.jsonl * (default ~/.graph-aave-mcp). One file per server install — scope by * namespace if you need multi-tenant separation. * * Capped at MAX_FINDINGS lines via tail-on-read; older entries stay on * disk for audit but aren't returned by get_session_state. */ export interface Finding { id: string; namespace: string; text: string; tags: string[]; createdAt: string; } export declare function noteFinding(text: string, options?: { namespace?: string; tags?: string[]; }): Promise; export declare function listFindings(options?: { namespace?: string; tag?: string; limit?: number; }): Promise; export declare function deleteFinding(id: string): Promise; export declare function getSessionState(namespace?: string): Promise<{ namespace: string; storagePath: string; totalFindings: number; findings: Finding[]; hint: string; }>; //# sourceMappingURL=sessionState.d.ts.map