01a0abd6 - Put the closed Moderators group on /moderate

[TaprootFreakAI]

EN:
Moves the closed Moderators group off /messages onto /moderate.
Confirmed moderators open it from the hub as /moderate/group; the page chrome is its only back control and the composer is text only.
The inbox never lists that thread and does not open it through ?c=.
Release the api first: the app needs GET /conversations/moderator-group.

DE:
Verschiebt die geschlossene Moderatoren-Gruppe von /messages nach /moderate.
Bestätigte Moderatorinnen und Moderatoren öffnen sie vom Hub unter /moderate/group; das einzige Zurück ist die Seitenleiste, der Composer ist reiner Text.
Die Inbox listet den Thread nicht und öffnet ihn auch nicht per ?c=.
Zuerst die API ausrollen: die App braucht GET /conversations/moderator-group.

Details

• Hub: founders still see Hidden notes and Open proposals only. Confirmed moderators (role === 'moderator') get a further tool linking to /moderate/group. Founders and everyone else see moderate.groupForbidden there and nothing is fetched.
• Staff room: ModeratorGroupScreen fetches GET /conversations/moderator-group then the thread and reuses InboxScreen as one open thread (showFilter false, showAmount false, heading always moderate.groupLabel). Back to /moderate is ProfileChromeLeft in the page chrome; the card has no back control, matching the one-back inbox.
• Inbox: moderator_group rows are never listed. ?c= opens only after the list loaded. A listed moderator_group id never opens. For a confirmed moderator an unlisted ?c= first resolves the staff-room id once (neutral loading, not the list); a match never opens and fetchConversation is not called. Other roles and a failed lookup fall through to the api, which rejects accounts that may not read the thread.
• After the rebase onto inbox unread: a thread can no longer load before the list, so the list-is-null badge fallback and the stale-list read guard were removed with their tests; the badge is refreshed once per opened thread from the loaded list.
• Api: same-origin proxy GET /conversations/moderator-group; conversationResponseSchema parses { conversation } including unread.
• Baselines: 20 /moderate/group Linux baselines from CI. The 4 welcome overlay-external-link baselines are the images develop itself renders (develop is red on that test); they are byte-identical to the develop unblocker af507305 - Unblocks develop: refresh the external-link overlay baselines #273.
• Rollout: the endpoint exists on the api develop branch only. Api release first, app release right after; in between moderators merely do not see the group in the inbox list.

[TaprootFreakAI]

EN:
Ready after 6 review passes.
Moves the closed Moderators group from the inbox to /moderate/group, with the page chrome as its only back control.

DE:
Bereit nach 6 Review-Durchläufen.
Verschiebt die geschlossene Moderatoren-Gruppe aus dem Posteingang nach /moderate/group, mit der Seitenleiste als einzigem Zurück.

Details

Head 878fa4f5, rebased onto develop a71d717c (after #255 inbox unread, #237, #259, #264, #266 one-back inbox). Three passes ran on the earlier stand, three on the rebased one.

Rebase reconciliation

• The inbox card has no back control any more (01a0b0b0 - Show one back control on inbox threads #266). /moderate/group therefore gets its only back control in the page chrome (ProfileChromeLeft → /moderate); InboxScreen.backLabel and the group screen's in-card back are gone.
• ?c= still opens only after the inbox list loaded, so the list-is-null badge fallback and the stale-list read guard from 01a0adcb - Show inbox unread in the menu and home-screen badge #255 can no longer run; they were removed together with their three tests.
• Conversations carry unread (01a0adcb - Show inbox unread in the menu and home-screen badge #255): moderator-group fixtures and the wrapper schema test follow.

Fixed during review

• Pass 4: the staff room showed an Amount field that could not be typed into → InboxScreen.showAmount, off for the staff room. Forbidden copy said "founders and moderators" although founders are not admitted → moderate.groupForbidden in all four locales. Loaded heading now always comes from moderate.groupLabel. On /messages the moderator lookup runs once per opened id and shows neutral loading instead of the list. conversationOneSchema → conversationResponseSchema. Handbook: every caller of fetchModeratorGroup, the exact ?c= guard, the /moderate/group actions and calls.
• Pass 5: the /moderate/group forbidden variant needle still matched the hub's copy, so the e2e gate did not check this screen → fixed. TSDoc of InboxLoader, InboxScreen, ModeratorGroupScreen; /moderate/group recipe in docs/ui.md; neutral-loading test seeded with a Direct row so its list assertion can fail.
• Pass 6: 0 findings on both dimensions.

Decided, not changed

• When the staff-room lookup fails for a moderator opening an unlisted ?c=, the inbox falls through and opens the thread. Deliberate and tested; not an ACL matter because the api admits moderators to that thread; documented in the InboxLoader handbook entry.
• A session-bound inbox list was added in pass 5 and removed again: the session only changes through passkey login (neither component is mounted there) and hydration, which refuses to swap one token for another, so a token-to-token change on a mounted tree is not reachable.

Baselines

• 20 /moderate/group Linux baselines refreshed from the CI artifacts.
• 4 welcome overlay-external-link baselines: develop itself is red on that test since 01a0ae8f - Make note URLs clickable with an external-link warning #264 met 01a0abc5 - Move private messages to the profile; Gift only on replies #237; the images are byte-identical to the separate develop unblocker af507305 - Unblocks develop: refresh the external-link overlay baselines #273, so this branch is green on its own.

Verification at the head

• CI: all six jobs green (checks, E2E behavior, four Visual projects).
• Full local chain at the exact commit: typecheck, lint, handbook/e2e/screenshot checks, 2726 tests with 100% coverage, build.

Rollout note

• The app calls GET /conversations/moderator-group, which exists on the api develop branch only. Release the api first and the app right after it; until the app is live, moderators merely do not see the group in the inbox list.