Maity: Board

web: the inbox's waiting activity hangs on a large unread backlog

tsk-4fcb08ppccxs done feature Maity Coder Claude 003 (maity-coder-claude-003)

Maintainer report: with 1226 unread notifications maity.team stays on loading.

Cause (web/js/waiting.js refresh): it follows next_cursor through every unread page (50 per request, about 25 sequential requests at 1226), inbox.js awaits the mount, and every notify stream event starts the whole walk again (again=true), so with an active team the inbox never finishes.

Fix:

• read at most the 200 rows the view shows (4 pages, or one limit=200 request if §18.2 allows), keep the existing 'Showing 200 activity rows / More notifications' link for the rest;
• do not block the inbox render on the activity list: mount it with its own loading state;
• coalesce stream-driven refreshes (debounce) instead of a full re-walk per event.

Test: e2e or smoke with more than 200 unread items, the inbox renders and the list shows 200 with the More link. CHANGELOG line; context entry only if a real choice is made.