All issues

DM global-cap ordering key is client-supplied, so future-dated messages evict honest ones rather than merely filling the cap

#687

· sanity opened

on Sep 9, 2026

No pre-merge check that the crates.io versions a branch claims are still unpublished (bit #673 twice)

#685

· sanity opened

on Sep 6, 2026

riverctl: two remaining list-vs-stream JSON asymmetries (`reactors` on message events, `reply_to.author_id`)

#684

· sanity opened

on Sep 6, 2026

riverctl: `member deputies` / `member deputized-by` JSON has no `verifying_key`, though a deputy holds ban authority

#683

· sanity opened

on Sep 6, 2026

riverctl: reaction data identifies reactors only by 40-bit short id, and a live bot bans on it

#682

· sanity opened

on Sep 6, 2026

ed25519 verify costs 2373 us because opt-level='z' size-optimises curve25519-dalek — 61x available for +2% WASM

#681

· sanity opened

on Sep 6, 2026

No CI job rebuilds the WASM, so a committed artifact that is not the build of its own source passes every gate

#678

· sanity opened

on Sep 6, 2026

check-pointer-freshness: the vanish and monotonicity clauses never execute in --ci (absolute TOML_PATH fed to git show)

#677

· sanity opened

on Sep 6, 2026

A no-op merge cannot normalise state: bare-None short-circuit skips post_apply_cleanup, leaving live peers with an unpopulated actions_state

#676

· sanity opened

on Sep 6, 2026

DM retention horizon goes stale mid-merge: three steps shrink the receiver's held set after it is published

#674

· sanity opened

on Sep 6, 2026

Delegate migration has no test that can fail: a future stdlib bump would strand user data silently, again

#630

· sanity opened

on Aug 22, 2026

Delegate-cached room snapshot can be near-empty, not merely stale, and the 5-minute debounce does not explain it

#622

· sanity opened

on Aug 13, 2026