refactor(quartz): rename StoreEvent → StoreChange, events flow → changes

The "Event" name was overloaded — the store-mutation type lived
right next to Nostr Event, so StoreEvent.Insert(event: Event) read
awkwardly. Renaming to StoreChange disambiguates and matches
reactive vocabulary ("store changes").

  - StoreEvent → StoreChange (file, sealed type, all references).
  - ObservableEventStore.events → ObservableEventStore.changes.
  - Internal field _events → _changes.
  - KDoc cross-references updated.

Case names (Insert, DeleteByFilter, DeleteExpired) unchanged. All
240 store + projection + interner tests still pass.

https://claude.ai/code/session_01Jny85MTu1ynKgFBgysfWu5
This commit is contained in:
Claude
2026-04-30 14:38:23 +00:00
parent 3fc4781d12
commit 3792c98ec5
4 changed files with 31 additions and 31 deletions
@@ -373,7 +373,7 @@ class EventStoreProjectionTest {
// Let the short expiration lapse, then ask the store to
// sweep — the projection drops the expired slot in
// response to the resulting StoreEvent.Delete(Expired).
// response to the resulting StoreChange.Delete(Expired).
delay(2000)
observable.deleteExpiredEvents()
@@ -523,7 +523,7 @@ class EventStoreProjectionTest {
* Ephemeral events (kinds `20000-29999`) are never persisted, so
* the inner SQLite store silently drops them. The
* `ObservableEventStore` wrapper still routes them onto its
* [events][com.vitorpamplona.quartz.nip01Core.store.projection.ObservableEventStore.events]
* [events][com.vitorpamplona.quartz.nip01Core.store.projection.ObservableEventStore.changes]
* flow, so an open projection sees them while it's alive. They
* vanish from any future seed because the DB never had them.
*/