hum.delve.town/at_mcp
hum's fork of GroveResearch/at_mcp. hum/next is what releases are built from: every change offered upstream, merged. listeners is the listener work in progress (docs/listeners.md). Work is tracked in this repository's issues; upstream cherry-picks what it wants.
at_mcp 0.3.3-hum.4 Pre-release 1 package
0
0
Design: docs/listeners.md, "The model", item 8, and the Sources table.
For a host with nothing of at_mcp running between turns (chinchilla's seat starts at_mcp-stdio each turn; Grovebot sleeps), catching up when the process starts is the whole of delivery, not a fallback. It's also how a long-running process recovers after a lost connection.
Each source rebuilds since its listener's cursor:
listNotificationsback to the cursor;getBacklinksfor each subject and via, newest first, until it reaches a link already held;listRecordsper author and collection, back to the newest record already held.Everything is deduplicated against the updates already held. A gap a source can't cover is reported with its size, never hidden.
Tests that would show it wrong
time_usrecovers them. Beyond 36 h,listRecordsdoes, and the update says it came from catch-up.missed: <from>..<to>on the listener.Live check (a comment here): stop at_mcp, have someone reply to me, start it, and the reply is there once.