Skip to content

Upgrade: disposition and adopt block/buzz v0.5.1 without widening Hive #69

Description

@100yenadmin

Parent: #1
Depends on: #11
Release blockers that must land on the adopted candidate: #78, #43
Dashboard dependency for #78: https://github.com/electricsheephq/electric-sheep-website-dashboard-6158a244/issues/751

Pinned Hive upstream base: dd222a509b156ba52ed3219e895d7bf1cf322c92
Current Hive main before adoption: ce2850ca75a4d528baa4280953331b13188664a2
Candidate: block/buzz v0.5.1 at a13085e9ac9a7c8dbd9426a6b88fc75abf62220e
Comparison: 104 upstream commits from the pinned base; 37 commits from v0.5.0 (4a977c588a540be38bd8ddb268cd24437bac8165) to v0.5.1.

Outcome

Adopt native Buzz v0.5.1 before the David/customer candidate while keeping Hive a thin Electric adapter. Do not replace native collaboration, create managed brokers, duplicate the agent catalog, provision Hermes, or blindly rebase.

Required disposition work

  • Give all 104 upstream commits one candidate-scoped keep, backport, redesign, drop/omit, or prove-inapplicable disposition.
  • Preserve the exact 37-commit v0.5.0-to-v0.5.1 disposition table recorded in this issue before source replay.
  • Map conflicts across OAuth/identity, relay admission/policy, native collaboration, Agents/ACP runtimes, settings, updater/branding, packaging, and tests.
  • Treat v0.5.1 relay lock-inversion fix 22be8bb35177e27efc2dca2534df9a8dd871eae0 as customer-release backport-or-prove-present work.
  • Treat Hermes configured-MCP isolation 6300a6b1d03e32c473c7b6568df663c8927565cf as required backport-or-prove-present work for the supported Hive Hermes path.
  • Reconcile agent catalog sharing a35771fc441cdc3c6f517f419037206783b502d2 and shared-agent fidelity f7a3988ba13b590d9a55a7e8413fc3fb5ffbef18 with the thin Company VM adapter and Company VM agents: use native signed profile avatars #43. Reuse native projections; do not create a second catalog or identity.
  • Keep custom local harness creation only where the local runtime is truthfully supported; never expose it as Hive-side VM Hermes provisioning.
  • Keep Electric website ownership of invites/seats; do not re-enable native hosted-invite authority in managed Hive merely because v0.5.1 refines it.
  • Preserve Electric-only OAuth, entitlement, durable identity/session, host-derived tenant admission, branding/updater, Company VM catalog, and capability-gated responder seams only where upstream does not now provide the behavior.
  • Implement Release blocker: managed OAuth must restore the canonical Hive identity without pairing #78 and Company VM agents: use native signed profile avatars #43 against the frozen v0.5.1-based candidate so the release blockers are not built on the stale agent/auth surface.

Acceptance

  • Fresh integration branch from exact v0.5.1 with an exact commit-disposition artifact; no blind merge/rebase.
  • Native Buzz collaboration and supported settings remain unchanged except for explicit managed product dispositions.
  • Release blocker: managed OAuth must restore the canonical Hive identity without pairing #78 managed OAuth-only canonical identity recovery and Company VM agents: use native signed profile avatars #43 Company VM avatar presentation pass on the adopted candidate.
  • Focused desktop/relay/identity/agent/updater tests, canonical exact-head CI, one independent semantic review, and a terminal disposition for every finding.
  • One cumulative signed internal artifact and installed Andrew/Benjamin/ATRIS/shared-agent/channel/DM/huddle/OAuth/avatar/memory canary.
  • David/customer distribution begins only after that exact cumulative artifact is accepted internally.

Non-goals

Blind cherry-picking, OpenClaw changes, Hive-side Hermes provisioning, hosted communities, Compute, customer relay creation, signing/publication from source proof alone, or claiming v0.5.1 adoption because this issue/milestone changed.

Stop conditions

Stop on native collaboration replacement, managed channel/DM brokers, client-selected tenant/relay authority, duplicate identities, private-key exposure, fabricated local personas for VM identities, unsupported runtime claims, cross-tenant access, or an OOM recurrence.

Exact next action

Freeze a13085e9ac9a7c8dbd9426a6b88fc75abf62220e, produce/verify the complete 104-commit disposition artifact, then replay the thin Electric patch stack onto a fresh v0.5.1 integration branch. Run the narrowest conflict-focused checks before opening the draft adoption PR.

Proof boundary

Issue and disposition state prove planning only. Source/CI, merge, signed artifact, installed canary, internal acceptance, and David/customer rollout remain separate claims.

Metadata

Metadata

Assignees

No one assigned

    Labels

    canaryNamed internal or customer canary gatereleasePackaging, signing, notarization, or distribution

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions