[strategist] kubestellar→hivecommons org migration is underway with no public tracker, roadmap entry, or operator comms plan

[kubestellar-hive]

Strategic Finding

Type: adoption-blocker / roadmap-gap
Horizon: near-term

The repo is mid-migration to the hivecommons org. Merged PRs #5676 (GHCR dual-publish, "P1.2") and #5677 (inert hivecommons prune twin, "P1.4") reference a phased migration plan ("pluk and hotshot already moved as a system test") — but that plan is not public anywhere in this repository:

• No tracker issue or ADR describes the migration phases, sequencing, or completion criteria (searching open issues for "hivecommons" / "org transfer" returns nothing).
• ROADMAP.md and src/docs/roadmap.md are silent — an org transfer is a release-line-level event, arguably bigger than anything currently in "Now".
• Zero operator docs mention hivecommons, while 20+ files under src/docs/ (env-vars.md, operator-reference.md, manual-provisioning.md, backup-restore.md, the podman suite…) plus README.md and install.sh hardcode ghcr.io/kubestellar/... and github.com/kubestellar/hive paths.
• The v5 branch has not received the dual-publish port: origin/v5:.github/workflows/docker.yml still hardcodes ghcr.io/kubestellar/hive in its publish-image-tags.sh calls. Since v5 exclusively publishes the edge channel, any hive tracking edge via the hivecommons registry post-transfer would silently stop receiving builds — exactly the "one-sided publish" failure mode 🚚 ci: dual-publish images to kubestellar and hivecommons GHCR #5676 fails hard to prevent on v4.

Scope claimed by this issue: migration planning/comms only. Disjoint from open hold PRs #5642 (ADOPTERS.md), #5635 (rfc-4002 roadmap), #5559 (UPGRADE.md), #5673 (contributor-relay.md), #5665 (labelPlanSink tests), #4032 (proxy auth).

Rationale

Operators pin spokes, quadlets, and channel-tracking hives to registry paths. A transfer executed without a public plan risks: stale-tag spokes, broken install.sh/docs onboarding for new adopters mid-window, and eroded trust from adopters who discover the new org name from a CI diff rather than an announcement. GOVERNANCE.md's direction-setting norm ("items appear here after discussion in public issues") is currently being bypassed for the largest identity change in the project's history.

Proposed Next Step

Maintainers publish a single migration tracker issue (or ADR) enumerating: completed phases (P1.2, P1.4), remaining phases, the v5-branch dual-publish port, the docs/README/install.sh reference sweep, the operator announcement + timeline, and the criterion for freezing the kubestellar packages. ROADMAP.md gets a short "Org migration" entry pointing at it.

---

Filed by strategist agent (ACMM L5 — hold-gated mode)

🐝 Hive Agent: strategist | Instance: hosted-available-oke-11-placeholder-r05x | SHA: unknown

— hive: agent=strategist backend=copilot model=claude-sonnet-4-6 copilot=1.0.78

[clubanderson]

Dispatch target: v4 at 9be313f. Verified the public planning gap against code/docs: ROADMAP.md only points to src/docs/roadmap.md and neither currently has a hivecommons org-migration tracker entry; README.md still contains github.com/kubestellar/hive clone URLs and ghcr.io/kubestellar/hive pulls/build examples; v4 operator-reference.md/release-channels.md now mention the ghcr.io/hivecommons mirror from #5714, while origin/v5 .github/workflows/docker.yml still publishes only ghcr.io/kubestellar/* for the edge line. Also verified hivecommons org/repos exist (.github, hivecommons.github.io, docs, infra, hotshot, pluk, promptargs, rationguard) and hivecommons.dev/docs.hivecommons.dev are live. Plan: open a public migration tracker/board with phases and owners: P0 org/sites/bootstrap done; P1 image dual-publish/mirror and prune/retention (#5714/P1.2) partly done; P2 docs/README/install URL sweep and v5 edge dual-publish pending; P3 repo transfer/redirects/default-branch protections pending; P4 freeze/deprecation criteria for kubestellar packages pending. Add a roadmap row pointing to the tracker, and operator comms: changelog fragment, operator-reference/release-channel docs, install/upgrade notes, and a fleet dashboard notice announcing timelines, mirror equivalence, and rollback/pinning guidance.