screens: visible UI gaps from post-cutover-blog audit (Join/Leave, Soft-delete banner, Blog tag chips, etc.)

[themightychris]

Umbrella for v1-completeness UI gaps

A 2026-05-30 spec-drift audit found seven screen-level gaps where the spec declares a feature but the SPA doesn't render it. None are cutover regressions; all are "spec says X, screen does less than X."

Screen	Missing	Spec
ProjectDetail	"Join Project" / "Leave project" buttons (API endpoints exist; no UI)	`specs/screens/project-detail.md` Actions table
ProjectDetail	Soft-delete banner for staff viewing a soft-deleted project	`specs/screens/project-detail.md` Header / Footer
ProjectDetail	"More ▼" dropdown wrapping secondary actions (currently flat buttons)	`specs/screens/project-detail.md` Header
BlogDetail	Tag chips in footer linking to `/blog?tag=` (response doesn't carry tags yet)	`specs/screens/blog-detail.md` Footer
BlogIndex	First-paragraph excerpt of `bodyHtml` as fallback when `summary` is null	`specs/screens/blog-index.md` Display Rules
HelpWantedIndex	"Post a role" project-picker entry point (modal exists, button doesn't)	`specs/screens/help-wanted-index.md` Header
PeopleIndex	Sort dropdown (createdAt / fullName)	`specs/screens/people-index.md` Header
PersonDetail	"Manage account" link to `/account` for self	`specs/screens/person-detail.md` Sidebar

How to split

Each is independently shippable. Suggest one PR per screen or two pairs of related screens (BlogIndex + BlogDetail; ProjectDetail buttons + soft-delete banner) to keep review surface small.

Why now

Aiming for v1-spec-completeness before cutover so the SPA matches what `specs/screens/*` declared. Not regressions — laddr didn't have most of these — but spec drift adds up.

Identified during the 2026-05-30 post-cutover-blog spec-drift audit.