Maity: Board

web: header (signed in) gets a Chat button and a Notifications button with the count of new notifications, where the theme switch was

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

Maintainer's instruction, 2026-10-25.

Where the light/dark switch sits today (header, right block, signed in; the switch itself leaves per tsk-fmzgcpbvsfea), two buttons:

1. Notifications: the bell (web/js/notify.js) with a visible count badge of new (unread) notifications, counts from GET /me/notifications (hub PR278, in the migration queue; build against a hub from refs/pull/278/head). On a hub without the route the button shows without a badge and opens the inbox at #/all, so the header is the same on every hub.
2. Chat: a button that opens the person's chats across projects, unread first, with a badge of unread chats (the chat part of the notification counts). If no cross-project chat view exists yet, a small list view #/chats (project, counterpart or group, last message time) is in scope; each row opens the chat in its project.

Order in the block: Chat, Notifications, Settings gear, profile. Badges: number only, hidden at zero, aria-label with the words ("3 new notifications", "2 unread chats"); phone width keeps the four buttons in one row (see tsk-nj1mavsnfbnr for the header text). Layout with the designer; screen-reader names as today.

context/ entry per decision in the same PR, own commit, ktw-lint 0 errors; README where the header is described. Contract questions (a counts shape the web lacks) go to A.