rcourtman b94d8473ce Count the days external agents read Pulse history ...

The agent event-record experiment is reviewed on 2027-01-27 against one
test: at least 15 install IDs on stable versions reading history on
three or more separate days in a 30-day window. No existing counter can
answer it: they count requests, fold these reads into general context,
and the activity history keeps only its newest 500 records, so a busy
agent pushes out the days it read on.

After a successful list_recent_changes or get_metric_history response,
an external-agent request now also records one content-free history_read
marker per UTC day. The marker skips Pulse's own pages, is deduplicated
in memory and on disk, and sits outside the 500-record cap. Telemetry
schema 21 reports the number of distinct marker days as
pulse_intelligence_external_agent_history_read_days_30d (0 to 30). The
per-request records are unchanged, so existing counters keep their
meaning.

2026-10-29 12:59:09 +00:00

..

integration

Count the days external agents read Pulse history

2026-10-29 12:59:09 +00:00

migration

Keep managed integration tests checkout-independent

2026-08-31 18:21:45 +01:00

qualification

Verify Patrol setup through a real local model and first run

2026-10-13 01:26:27 +01:00