DanConwayDev c59c80a3a3 fix(purgatory): preserve membership across announcement promotion ...

Removing a pending announcement before its database save briefly exposed the previous membership graph. Concurrent reconciliation could then restore an obsolete state after the newly authorized state had aligned Git refs.

Keep the announcement through a successful save and remove only the exact saved candidate. Snapshot pending announcements around the database query and merge candidates using NIP-01 ordering, so promotion and concurrent replacement cannot resurrect an older graph. Admission policy and state ordering remain unchanged.

A deterministic promotion hook verifies visibility during saving, preservation of a concurrent replacement, and preference for newer database announcements. That regression, the existing invitation/state convergence integration, formatting and all-target Clippy pass. Full workspace confidence runs follow.

Assisted-by: Codex (GPT-6)

2026-09-21 08:54:39 +00:00

..

sync

test: remove scheduling margins from expiry assertions

2026-09-12 14:48:16 +00:00

helpers.rs

test: survive hostile git config and non-reaping PID 1 in CI

2026-08-15 07:11:52 +00:00

mod.rs

fix(purgatory): preserve membership across announcement promotion

2026-09-21 08:54:39 +00:00

persistence.rs

test: remove scheduling margins from expiry assertions

2026-09-12 14:48:16 +00:00

promotion_hooks.rs

fix(sync): preserve hooks after maintainer pre-save

2026-08-19 22:24:38 +00:00

types.rs

docs: sync implementation spec citations

2026-07-17 17:14:44 +01:00