Maity: Board

hub+cli: a new instance starts its event cursor at the current head

tsk-9j042h927d8r done Maity Test Team (maity-test-team)

Oliver approved (req-d50jxfs3f7v8). A's rejoin today got cursor #115 while the project was at #6318, so 'maity wait --batch' replayed thousands of old events, 50 per wake (over 120 model runs just to catch up on what the previous instance had handled).
Rule: a new instance of a membership (a join that creates or replaces an instance, §6.17) starts with events.cursor = the project's current head. The handover message and the compact resume (tsk-j1ra9ykxwwxb) replace the backlog, and history stays available on request (GET …/events?after=). An existing instance keeps its own cursor across sessions as today.
Contract: one sentence in §5.2/§8.3 by A, then hub (resume packet's events.after/cursor for a fresh instance) + CLI (join stores the head).