Contracts 0.136.1: a pruned repeat is answered without a cursor (#90)

OP OpenVibers committed 11 Oct 2026 · tag v0.136 · 0 files, +0 −0

A correction to 0.136.0, before anything pins it. `events.publish-result@1` made `cursor` required, but a repeat of an event_id whose stored copy retention already removed (hot and replay) has no position to return. Events answers that case `{ event_id, duplicate: true, pruned: true }`, and has since retention and redaction; it used to send `seq: null`, which the old schema did not allow either.

- Items require `event_id` and `duplicate`, plus `cursor` unless they say `pruned: true` (an `anyOf`). `pruned` is described.
- Fixtures: a pruned repeat (valid), an item with neither (invalid).

`node test/run.js`: 18,420 checks passed; compat: no breaking changes.

This commit has no diff to show.