Count every commune's notices and put what needs you first (app review batch 5, Home and notices)

[EmotiveImpact]

Before: the bell counted only the open commune's notices, so a reminder or payment report from another commune showed nothing, even on Home. Home's Needs you listed every open expense you paid for alongside your unpaid shares, late jobs and pledges, sorted only by date, and This Hub built its list another way. Activity rows read "Inspection: Created" without saying whether it was a task, event, note or expense, and with no time of day. Screens showing someone who had left wrote "Former member" or "the bill payer", although the snapshot keeps their name. The sidebar carried the reminder allowance under your name, a blank name showed "MC" in its avatar, the saved splits filters sat apart without showing which was selected, and text over a bright commune photo dropped to between 1.6:1 and 2.7:1.

After: the bell adds up every commune's unread notices on every screen, and Notices lists the open commune first, then each other commune under its name. Needs you puts what only you can do first (payments someone says they sent, your unpaid shares, your late tasks and your pledges due) and keeps what others owe you in a quieter "Waiting on others" group, built by one rule on Home and This Hub. Activity rows name the record's type with a coloured chip, show the time and are grouped by day. Former members are named, with "(left)" where it matters. The reminder allowance shows where reminders are sent, a blank name shows "?", the saved splits filters match Funds' chips, and text over a white stand-in photo now measures at least 4.6:1 for small text.

This is the last of three pull requests for batch 5 of the app review fixes. It is built on #31 (getting around), so review that first; the diff here shows only this part.

What changed, by finding

Finding	Change
34	Migration 0039 adds each commune's unread count to the commune list the app already reads each minute, and my_unread_notices() returns the unread notices of every commune the caller belongs to, with the sender's name. The bell adds up every commune's count on every screen. Notices lists the open commune first, then each other commune with unread notices under its name, fetched only when Notices opens; a failed fetch offers Try again. Opening another commune's notice marks it read, refreshes that commune and switches to it before opening the record.
32	One rule, needsYou() in apps/web/src/live/model.ts, builds Needs you on Home and This Hub: payments someone says they have sent, which only the bill payer can confirm, then your unpaid shares (marked overdue when late), your tasks that are late or due today, then your pledges due, the earliest first within each. What others owe you, and payments you said you sent, sit in a quieter "Waiting on others" group. Home shows up to 6 actions and 4 waiting rows with "And N more", This Hub's count covers actions only, and Home lists pending payment reports for communes that aren't open (0039).
49	Each activity event carries its record type (expense, repayment, fund, pledge, contribution, recurring, template, task, event, note, member or announcement), worked out by 0039 from the record it is about, so older events get one too. Activity and All activity show a coloured chip and the type word (money in slate, plans in sage, shared things in cream) with the time, under Today, Yesterday or the date. Home's Recent activity shows the type with the day and time.
Former members (found while checking batch 3)	One helper, personName, names anyone the snapshot knows and adds "(left)" where it matters that they are no longer a member: Settle, the expense, pay and breakdown windows, Funds, Recurring, saved splits, Members, announcements, Notices, and note and task history. "Former member" remains only for someone the snapshot does not know.
55	A name with no letters shows "?" in its avatar instead of "MC". The reminder allowance leaves the sidebar, which now shows only the role; it stays in account settings, on an expense its payer can nudge from and in the reminder confirmation. Once a fifth or less is left, Settle, the expense window and an admin's fund window say how many are left, or when the next one comes back, wherever a Nudge or Chase is offered.
46	Saved splits' Active and Archived filters use the same chips as Funds, side by side, with the selected one marked.
58	The shade under each commune photo is now darkest where the text sits, measured up from the bottom, while the top of the photo is as light as before. The type labels and the Hub's buttons have their own small dark backdrop, and the status lines and a trip's Area and Stay are less faded. Over a white stand-in photo, small text now measures at least 4.6:1, large text 3.2:1 and the buttons 5.1:1. You chose to keep this darker shade on 9 October.

Not in this batch: Home's Recent activity is typed but not grouped by day, and the grey text on Hub panels (--hub-muted, about 4.2:1) stays as it is for now.

Releasing

Nothing hosted was touched. Migration 0039 is local only and follows 0038. Everything in it adds to what is there, so the previous client keeps working. Apply it and refresh the Data API schema cache before deploying this client, which calls my_unread_notices when another commune has unread notices.

Needs the owner

• The design reference page (apps/web/reference/design-language/index.html) now shows "Admin" alone in the account line, where it showed "Admin · 58 reminders left", to match the sidebar. Say if you would rather the reference stayed as it was.

How it was checked

On the final branch:

• 602 web tests in 56 files, including the new notices-across-communes (8), needs-you (4), activity-log (5), former-members (6), reminder-allowance (5) and cover-contrast (14). The contrast test fails against the old stylesheets.
• 27 database tests through run-local.sh, including the new notices_and_activity.sql; 2 more need a Neon branch.
• 21 local API suites on a disposable database and port, including the new notices-and-activity.mjs, and the reminder worker's unit tests and 4 database suites.
• Typechecks for the web app, local API and worker, a production build, and the secret scan.

In Chromium, on a disposable database with three communes: the bell read "Notifications, 4 unread" from Home, and Notices listed 14 Park Street first, then Studio East and Lisbon long weekend under their names. This Hub's Needs you put Jordan's reported payment first, then the shares owed, with Rent, Electricity and the sofa under Waiting on others. An older expense named "Lena Fischer (left)". Covers were compared over bright and dark photos before and after. No page errors.

How

needsYou() works only from the snapshot and the commune summaries, so Home and This Hub share it and its tests. 0039 changes the shared database functions in place with checked anchors, so it fails loudly instead of applying if one of them has changed underneath it. The contrast test reads the shade and colour values from the stylesheets and lays them over white, so a later style change that drops below the rule fails CI. docs/HANDOFF.md, docs/DESIGN-LANGUAGE.md, infra/neon/README.md and infra/local/README.md record the changes and migration 0039.

🤖 Generated with Claude Code

https://claude.ai/code/session_01A6P7aTcMBccooYYr4xYnVS

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
commune-web	Error		Oct 9, 2026 6:34pm UTC

[EmotiveImpact]

The Vercel preview for commune-web shows Error here, as it has on every branch since 6 October. It is the project or account issue explained on #24 (app review finding 45), not this diff: the Web app check, which builds the app, passes on this head (a3db9b2). It needs someone with the Vercel login to read a failed deployment's log.

---

Generated by Claude Code

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-12T02:02:27.529725Z	a3db9b2	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.