A signup's page gives no way to reach its organizer, and its only Contact link emails the site

Start with src/schemas/signups.ts, then trace the Settings tab action beside setRequireEmailAction and the public page in src/app/s/[slug]/signup-view.tsx. Check how toPublicSignup in src/app/s/[slug]/public-signup.ts and SparseSettingsSchema in src/mcp/tools/signups-write.ts expose settings. Done means organizers can set and clear the plain text line, viewers cannot, open and closed pages and the public API show it when set, and the privacy page, help article, and tests cover the change.

Needs your OK: this adds an optional contact line that organizers can show on their signup's page, and adds a line to the privacy page. Nothing about an organizer is shown unless they type it in. Swap pipeline:proposed for pipeline:ready to have it built.

What happens

Nothing on /s/[slug] names the organizer or says how to reach them, in any state. On a closed signup it matters most. SignupViewBody in src/app/s/[slug]/signup-view.tsx shows "This signup is no longer collecting responses." and every slot says Closed. Someone who wants to ask for a late spot, or say they can't come, has nowhere to go:

• The only "Contact" on the page is the site footer's (SiteFooter in src/components/site-footer.tsx). It's a mailto: to the site's operator (SUPPORT_MAILTO), who can't help with someone else's signup.
• Other participant pages already say "contact the organizer" and give no way to: the "took you off this slot" page (cancelled-message.ts) and the broken-link pages (gone-message.ts). The unsubscribe page (src/app/s/[slug]/unsubscribe/page.tsx) says "reply to the organizer", but participant emails come from the site's address and set no Reply-To, so a reply goes to the site.
• The account holds nothing safe to show. organizers.name is filled only by Google sign-in, and no screen lets an organizer change it. The personal workspace's name falls back to the organizer's sign-in email (src/auth/adapter.ts). organizerDisplayName is in SignupCreateInputSchema, but nothing stores it.

An organizer can type a phone number into the description today, but nothing suggests it, and the description isn't shown on the pages that say "contact the organizer".

To see it: on a fresh local instance, create a signup with one slot, publish it, then close it. Open its link signed out. The page has no organizer name and no way to reach them, and the footer's Contact opens an email to the site.

Fix, in outline

• A new optional setting, contactLine in SignupSettingsSchema (src/schemas/signups.ts). It's plain text, trimmed, up to 200 characters, and blank clears it. It's stored in signups.settings, so there's no migration.
• Set it on the Settings tab, in a new "Contact" section above the danger zone. Copy the "Sign-up form" section: a plain form, a server action next to setRequireEmailAction that calls updateSignup with sparse settings, Save, and SavedNotice. Help text: "Shown on your signup's page, so people can reach you. Leave it blank to show nothing."
• Show it on the public page under the description, in every state the page renders (open and closed), when it's set. Nothing shows when it's blank.
• Send it in the public API. Add it to the settings allow-list in toPublicSignup (src/app/s/[slug]/public-signup.ts), which is meant to match what the page shows.

Watch for

• Legal pages. In src/app/(legal)/privacy/page.tsx, under "What we collect from organizers", add a line: an optional contact line you add to a signup, shown to anyone with its link. Bump "Last updated". The terms' acceptable-use rules already cover what organizers publish. The cookies page doesn't change. #572, #573 and #574 also edit the privacy page, so whichever lands second merges.
• The AI connector. SparseSettingsSchema in src/mcp/tools/signups-write.ts takes every SignupSettingsSchema key not in UNREAD_SETTINGS, so update_signup will accept contactLine once it exists. Say in the tool's description that the line is shown publicly. Check that get_signup returns it.
• Plain text only. Render it as text, never as HTML or markdown, and don't turn it into links (see Choices).
• Don't use the workspace's or account's name as a stand-in. The workspace name can be the organizer's email.
• Viewers can't set it. The service already uses requireWorkspaceWrite for updates. Keep the Settings tab's refusal wording ("You don’t have edit access.").
• Help pages. Mention the setting in "Create and publish your first signup" (src/help/articles/), and run the help-pages skill's affected-articles script.
• CHANGELOG entry.

Choices this makes

• What to show: a free-text line the organizer writes, such as "Questions? Text Pat at 555-0100". Default: free text. The organizer chooses what to share (a phone number, an email, a group chat), and nothing is shown unless they add it.
  • Not the account's name or email. Neither was chosen for a public page, and the name often doesn't exist.
  • Not a relay form that emails the organizer without showing an address. It needs a rate limit, spam handling, a new email and a Reply-To decision (#202 weighs the same choice for messages the other way). It can follow on its own if a line isn't enough.
• Where it shows: the public page, open and closed. Default: there only. The "Your spot" page, the "took you off this slot" page and the unsubscribe page all tell people to contact the organizer, so showing the line there is a natural follow-up. It's left out to keep this to one PR.
• Where it's set: a "Contact" section on the Settings tab. Default: Settings tab. The other option is a box under the description on the Build tab, since the line is shown on the page like the description is. The Settings tab keeps the Build tab about slots.
• Links: plain text, with no automatic mailto: or tel: links. Default: plain text. An address or number can still be read and copied, and links built from organizer text would put clickable links on this site that it didn't write.
• The footer's Contact link: Default: unchanged. It reaches the site's operator, which is where the privacy page sends data requests. Renaming it "Contact this site" is a small follow-up if people keep writing to the operator about a signup.

Done when

• An organizer can add, change and clear the contact line on the Settings tab, and a viewer can't.
• When the line is set, an open signup's page and a closed signup's page both show it under the description, at 390px and 1280px wide. When it's blank, they show nothing.
• GET /api/public/signups/[slug] returns it in settings, and update_signup can set and clear it.
• The privacy page says what's stored and where it's shown, with a new date.
• Tests cover the schema (trim, length, blank), the sparse update and the page with and without the line.
• pnpm lint && pnpm typecheck && pnpm knip && pnpm test and pnpm test:db pass.

Found by the UX walkthrough (scenario O4) on 2026-10-24, and checked against the code on main at 4ed27a9.

Generated by Claude Code