feat: add event cleanup mechanism for memory store

[bianbiandashen]

Summary

Add automatic event cleanup for the in-memory store to prevent unbounded memory growth.

Problem

The in-memory store's events array grows indefinitely:

const events: AFSEvent[] = [];  // Never cleaned up

In long-running processes, this leads to:

• Gradual memory increase
• Eventually OOM crashes
• Performance degradation as the array grows

Solution

Implement a dual-strategy cleanup mechanism:

1. Count-based Cleanup

• Configurable maximum event count
• Triggers immediate cleanup when at 120% capacity
• Oldest events are removed first (FIFO)

2. Time-based Cleanup

• Configurable TTL for events
• Periodic background cleanup removes expired events
• Default: 1 hour retention

Configuration (Environment Variables)

Variable	Default	Description
AGENTATION_MAX_EVENTS	10000	Maximum events to retain
AGENTATION_EVENT_TTL_MS	3600000	Event TTL (1 hour)
AGENTATION_CLEANUP_INTERVAL_MS	300000	Cleanup frequency (5 min)

Implementation Details

• cleanupEvents(): Removes expired and over-limit events
• addEvent(): Wrapper that triggers cleanup when needed
• Cleanup timer properly stopped on close()
• Logging when events are cleaned up for observability

Changes

• mcp/src/server/store.ts: Add cleanup logic to memory store

Test plan

• Verified normal event creation still works
• Verified events are cleaned up when over limit
• Verified cleanup timer stops on close()
• Verified configuration via environment variables

[vercel]

@bianbiandashen is attempting to deploy a commit to the Benji Taylor's Projects Team on Vercel.

A member of the Team first needs to authorize it.