[Improve] Show richer static titles for shared app links

[roomote-roomote]

Opened on behalf of Bruno Bergher. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

Shared links into the product app now resolve to short static page titles and one-line descriptions instead of the generic global fallback:

• Task routes → Roomote Task
• Any settings page → Roomote Settings
• Task history (/tasks) → Roomote Task History
• Sign in → Roomote Log In
• Invite sign-up (/sign-in?invited=… and canVisitorSignUp()) → Roomote Sign up
• /setup → Roomote Setup
• /onboarding → Roomote Onboarding

Titles and descriptions are privacy-safe static strings (no task names or other dynamic data). Open Graph / Twitter images are intentionally omitted. Sign-up metadata now uses the same eligibility gate as the form, so a stale or fabricated invite query alone cannot flip the title to Roomote Sign up.

Why this change was made

Link previews for almost every web-app URL previously collapsed to Roomote / Cloud management for Roomote., which was too thin for sharing. We wanted slightly richer previews without leaking private work context through shared titles, and title mode should stay consistent with what the sign-in form is actually allowed to show.

Impact

When someone pastes a task, settings, history, auth, setup, or onboarding URL, crawlers and chat unfurl paths that read HTML metadata get a clearer static title and description. No OG images are generated, and no task- or user-specific content is exposed through metadata.

[roomote-roomote]

No new code issues found. See task

• apps/web/src/app/(unauthenticated)/sign-in/[[...sign-in]]/page.tsx:28 derives sign-up metadata from the invited query alone, but the form only enters sign-up mode when canVisitorSignUp() is also true. An expired or fabricated ?invited=1 URL therefore renders the sign-in form under a Roomote Sign up title; base the metadata decision on the same eligibility check as the form.

_{Reviewed 1a9a462}

[roomote-roomote]

Fixed in 1a9a462.

generateMetadata now bootstraps auth config, calls canVisitorSignUp(), and only emits Roomote Sign up when eligibility is true and invited is present — same gate as the form’s default mode. Otherwise it stays Roomote Log In.