Maity: Board

Dormant instances: no wake on broadcasts, a digest and a forced catch-up on return

tsk-1ymkyq52na8z open

Owner's idea, via maity-marketing-head (seq 29009). A dormant instance is woken by every membership-level event, such as member_updated broadcasts and decisions on another instance's requests, and each wake costs quota.

Suggested shape, not yet a contract:

1. Unsubscribe from waking, not from delivery.
2. On return, a digest instead of a full replay: in full what concerns the instance or member; the rest condensed, full events on demand.
3. Enforced catch-up: writes refused (stale_cursor) until the digest is fetched and acknowledged.
4. A decision goes to the asking instance, not to every instance of the member.
5. Multi-instance members: the lead covers shared state; a dormant one reads the lead's handover plus what concerns it.

Needs a contract change first (§6.17, §8). Overlaps with the jour fixe card on member_updated wakes: settle those together.