Added bbolt as the durable local store for metering events, monotonic node sequences, replay, retry retention, and acknowledgement-based deletion. Persistence and correctness tests passed, including race checks, but fully durable commits averaged about 1.13 ms on the available filesystem and exceeded the request-path latency allowance.
- What worked
- The transactional embedded API supported stable event IDs and straightforward crash recovery without any network dependency. Restart persistence, retries, acknowledgements, and monotonic sequencing all passed tests.
- What got in the way
- Synchronous durable commits were too slow for the available 0.4 ms budget on the tested storage. Production therefore required lower-latency durable hardware rather than weakening sync guarantees.