fix: self-host compose ownership, key import, owner onboarding

[Chessing234]

Summary

• Compose: chown buzz-git-data to uid 1000 so the non-root relay can write pack-cache (Fresh deploy/compose stack: relay crash-loops on /data/git/.pack-cache (root-owned named volume vs non-root uid 1000) #2814).
• buzz-admin generate-key: print nsec/npub for desktop paste (buzz-admin generate-key emits a hex secret that desktop onboarding rejects (expects nsec1) #2815 admin half).
• Owner onboarding: offer self-hosted relay URL path alongside Builderlab (Self-host onboarding dead-ends: 'I already have a community' → 'I own the community' only offers Builderlab, never a relay URL #2816).

Hex secret import for desktop lives in #4504 (dropped from this tip on rebase to avoid duplicating it).

Test plan

• Fresh compose volume: relay starts without pack-cache permission loop
• buzz-admin generate-key prints nsec1… / npub1…
• Owner onboarding can enter a self-hosted relay URL

[BillChirico]

Can we have this merged to fix this issue?

[Chessing234]

@tlongwell-block @wesbillman @wpfleger96 mind taking a look when you get a chance?

[Chessing234]

hex import is split out as a focused pr: https://github.com/block/buzz/pull/new — wait, will link the number. this selfhost bundle stays conflicting; happy to rebase the compose bits separately if useful.

[Chessing234]

hex import is split out as #4504 so it can land without the conflicting compose bundle.

[Chessing234]

also closed #4244 in favor of #4348; hex import lives in #4504.

[Chessing234]

self-host compose ownership + key import path. @MajorTal you've been in the desktop/git weeds lately if this is useful overlap.

[Chessing234]

rebased onto main and split hex import into #4504 — still waiting on maintainer review before it can merge.

[ryanmitchellneely]

Review (issue author of #2816)

Thanks @Chessing234 — this unblocks the exact dead-end I hit.

#2816 owner onboarding — LGTM

WelcomeSetup.tsx does the right product split:

• I own the community no longer jumps straight to Builderlab
• New owner page offers:
  • Connect a self-hosted relay → existing member/relay URL flow
  • Sign in with Builderlab → hosted path
• memberBackPage keeps Back correct from both entry points (member and self-host owner)

That matches the expected behavior in #2816 and the provider-neutral framing others confirmed on current main (role ≠ hosting).

Related fixes in this PR — also good

• buzz-admin generate-key: prints hex and npub/nsec so desktop paste works (#2815 half). Clear operator copy.
• compose git-data-init: chown buzz-git-data to uid 1000 before relay start — correct fix for fresh named volumes + non-root USER buzz pack-cache loop (#2814).

Non-blocking notes

• Hex secret import for desktop is correctly deferred to #4504 per PR body — fine; just keep that linked so self-hosters don’t think this PR alone finishes key import.
• No Playwright/onboarding regression in the diff; morthenjensen-wq offered a focused test on #2816 — nice follow-up but not a merge blocker for this UX fix.
• Self-host Mac still needs the known CORS footgun (BUZZ_CORS_ORIGINS=tauri://localhost) until that’s documented/defaulted elsewhere — out of scope here.

Verdict

Please merge. This is the first-five-minutes path for the OSS/self-host audience the repo targets. Happy to re-verify on a desktop build once it lands.

— Ryan (reporter of #2816)

[Glucksberg]

Confirmed — I just hit this exact onboarding path while setting up Buzz on a second machine with the same identity.

My existing community was already working on Windows, including another member who had successfully joined it. When setting up the Mac with the same nsec, I chose:

"I already have a community" → "I own the community"

That sent me directly into the Builderlab sign-in flow, even though I wasn't trying to create or manage a hosted community.

The workaround was basically to "go through the gap in the fence":

1. Go back
2. Choose "Join a community" instead — even though I'm actually the owner
3. Use the same invite link from my existing community
4. Buzz connects normally to the existing community with the same identity

So #2824 matches the actual user experience very well. The important UX distinction really is ownership vs. hosting: owning a community shouldn't imply that it is Builderlab-hosted.

The proposed split between Connect a self-hosted relay and Sign in with Builderlab would have made the correct path immediately obvious.