Add a launch and invite kit to community deployment success

[Caneryy]

Planning

• Plan ID: N7
• Depends on: Canonicalize all community navigation under /communities #247 (H1), Retire the duplicate community creation wizard #249 (H3), Standardize on-chain identifiers, copy actions, and explorer links #253 (H7)
• PRD alignment: FR-6; UJ-1

Problem

After deployment, creators need a clear way to share the Community and guide the first Members instead of copying contract IDs manually.

Scope

Extend the registry-verified success state with the canonical Community URL, copy/share actions, explorer links, and a checklist: verify metadata, invite Members, mint membership, delegate, create the first Proposal.

Acceptance criteria

• Share content uses the canonical registered Community URL.
• Native Web Share is used when available with clipboard fallback.
• Explorer links use the active network.
• Refreshing a recoverable deployment retains the success handoff after registry verification.

Verification

npm run lint && npm run typecheck && npm test

[bobo-24]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. I’ll prioritize this immediately and ensure a reliable solution is delivered as soon as possible. Thank you!

[bobo-24]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. I’ll prioritize this immediately and ensure a reliable solution is delivered as soon as possible. Thank you!

[s6pa1rta3n-lab]

/try

[mimi-esc]

Hi, I would love to work on this issue