migration: rename GitHub organization handle to bytefolk

[PeterGuy326]

Outcome

Rename the GitHub organization handle from fullstack-ai-infra to bytefolk, making https://github.com/bytefolk the canonical ByteFolk home without breaking runtime downloads, CI, published images, or active documentation.

Frozen decisions

• Target handle: bytefolk (accepted by the GitHub Rename UI on 2026-09-01).
• Scope: GitHub organization URLs, repository coordinates, API paths, raw-content URLs, repository metadata, GHCR namespace, and local remotes.
• Compatibility scope retained for this migration: npm packages remain under @fullstack-ai-infra/*.
• Stable identifiers remain unchanged unless migrated separately: desktop app IDs, MCP IDs, schema identities, cache directories, npm tarball names, and legal copyright text.
• Do not create an empty organization at the old handle; GitHub does not support it as an alias and it can invalidate repository redirects.

Baseline

• Owner executing migration: PeterGuy326 (active, role admin).
• Organization: 11 repositories (7 public, 4 private), all on main, none archived, no GitHub Pages sites.
• Actions: 18 workflow files; no uses: fullstack-ai-infra/... references.
• Integrations: 0 repository webhooks and 0 GitHub App installations; organization hooks and self-hosted runners require post-change UI verification because current token cannot enumerate them.
• Local tracked references: 8 repositories, 190 files, 643 matching lines.
• Published container: ghcr.io/fullstack-ai-infra/digital-employee has 11 public tags; 0.6.0 resolves to sha256:37cad26dd91273a2b546332d1c14398b783b31fae442cffe8e67f36622d5667a.

Migration sequence

• Prepare isolated per-repository PRs for GitHub URL/API/repository-coordinate changes.
• Update runtime-critical references: org-workbench checkout source, mem release download source, digital-employee governance default repository, raw-content URLs, and package metadata.
• Keep npm scope and stable application/registry identifiers unchanged.
• Freeze a short cutover window and record pre-change readbacks.
• Rename the organization in GitHub Settings from fullstack-ai-infra to bytefolk.
• Update local remotes and merge the prepared PRs against the renamed repositories.
• Verify github.com/bytefolk, all 11 repositories, API ownership, clone/fetch/push redirects, and required CI.
• Verify GHCR migration and publish/pull using ghcr.io/bytefolk/digital-employee; document the old pull-path behavior.
• Verify organization hooks, runners, Packages settings, profile/avatar, and repository homepage metadata.
• Record final commit SHAs, CI run URLs, new organization URL, and follow-up debt.

Acceptance criteria

• https://github.com/bytefolk is the live organization profile and API login is bytefolk.
• All 11 repositories are present under the new organization handle.
• Runtime-critical references contain no old GitHub owner coordinate.
• Required checks pass on every migration PR; no branch protection or review policy is bypassed.
• ghcr.io/bytefolk/digital-employee:0.6.0 is pullable and digest behavior is recorded.
• npm @fullstack-ai-infra/* consumers continue to work unchanged.
• Post-change verification and rollback limitations are recorded in this issue.

GitHub behavior relied on

GitHub creates web/Git redirects for existing repositories, but not for the old organization profile. Actions/reusable-workflow references and package consumer paths must be updated explicitly. The old handle becomes available for others and is not a reliable rollback mechanism.

Official reference: https://docs.github.com/en/organizations/managing-organization-settings/renaming-an-organization

[PeterGuy326]

Prepared migration PRs

The cutover set is ready. All repository changes remain unmerged so the new URLs and GHCR path do not become canonical before the organization rename.

Public repositories:

• .github: docs: prepare ByteFolk organization handle migration #21 — Governance green
• org-workbench: chore: prepare ByteFolk owner-coordinate migration org-workbench#103 — Node 24 Linux/macOS green
• digital-employee: migration: prepare digital-employee for ByteFolk handle digital-employee#243 — full CI green
• mem: chore(migration): prepare ByteFolk GitHub coordinates mem#142 — CI, acceptance, and metadata gates green
• digital-employee-quickstart: chore(migration): prepare ByteFolk GitHub coordinates digital-employee-quickstart#17 — both verification suites green
• doc: chore(migration): prepare ByteFolk GitHub coordinates doc#33 — test and container build green
• design-system: chore(migration): prepare ByteFolk GitHub coordinates design-system#16 — full check green

The private platform migration PR is also open and its Node 20/22/24, coverage/audit, and PostgreSQL checks are green. Private repository details are intentionally omitted from this public issue.

Independent technical review caught commit identity metadata on three branches before merge. Those commits were rewritten with the verified GitHub noreply identity using force-with-lease; tree and diff hashes were unchanged, and the replacement CI runs are green.

Current gate: all required CI is green; independent repository reviews are still pending. Do not rename or merge the new canonical URLs until at least one independent approval is recorded for each protected migration PR.

Cutover order after approvals:

1. Read back all PR head SHAs and checks.
2. Rename the organization to bytefolk in Settings.
3. Verify organization/repository/API redirects and GHCR namespace.
4. Merge the prepared PRs without bypassing protection.
5. Update local remotes and the quickstart repository homepage.
6. Run post-change verification and record evidence here.

[PeterGuy326]

Preflight correction — cutover remains HOLD

Independent diff review found that digital-employee PR #243 mechanically changed seven JSON Schema $id values and their downstream identity references. Those values are frozen compatibility identifiers under this issue and must not follow the GitHub organization handle.

PR #243 is therefore HOLD even though its CI is green. A targeted correction is in progress to restore the schema identities, keep real GitHub/GHCR owner coordinates migrated, and replace the broad zero-residual check with an exact allowlist. The PR evidence will also be corrected and exact-head CI rerun.

The other seven migration PRs passed independent preflight. No organization rename or migration PR merge will occur until #243 passes re-review and the independent repository approval gate is satisfied.

[PeterGuy326]

Preflight restored

digital-employee PR #243 has been corrected and independently re-reviewed at exact head 92de4f23be534dddc336859be41a14a7e97f00b2.

• All 9 JSON Schema $id values match main exactly.
• The 16 retained old-owner lines are confined to the 15 frozen schema-identity files; allowlist extras are zero.
• Outside that allowlist, old GitHub/API/GHCR/bare owner coordinates are zero.
• npm scope, domain, legal, and tarball identities remain unchanged.
• [Unreleased] now records the ByteFolk GitHub/GHCR migration and preserved compatibility identities.
• Exact-head CI run https://github.com/fullstack-ai-infra/digital-employee/actions/runs/33469610174 completed successfully with all 12 jobs green.

Independent technical preflight is now PASS for all eight migration PRs. The remaining cutover gate is human repository review/approval; no rename or merge has been performed.