Rotorsoft / act-root / 36575227428

100%

push

github

fix(act): carry __snapshot__ events through a store-sourced restore (#1682)

scan's pagination query omitted with_snaps, and every adapter filters
__snapshot__ out of a query that doesn't ask for it — so no snapshot ever
reached the walk from a real Store source, and none reached the sink.

For an ordinary stream that loses an optimization. For a stream pruned by
a windowed close it loses the data: the boundary snapshot is the stream's
only remaining event, so the stream vanished from the rebuilt store with
no events, no state, no error, and kept never counting it. Same for a
stream reseeded by close({restart:true}).

scan's own drop_snapshots branch was dead code against a Store, so the
documented compaction option was a no-op and dropped.snapshots was
structurally always 0. The max_id probe had the same omission and
under-reported progress whenever the newest event was a snapshot.

No existing test used a real Store as a restore SOURCE — restore.spec.ts
drives scan through a synthetic EventSource that ignores with_snaps, so
all seven drop_snapshots cases passed against dead code.

Closes #1671

Co-authored-by: rotorsoft <rotorsoft@outlook.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

4355 of 4355 branches covered (100.0%)

Branch coverage included in aggregate %.

9419 of 9419 relevant lines covered (100.0%)

1198.98 hits per line