Migrate zos-product repos off GitHub rename redirects (tracking)

[ashraffouda]

Tracking issue for migrating the zos-product repos off GitHub's rename redirects (which are not permanent). Renamed repos work today only because GitHub redirects old URLs + Go module paths were left unchanged; this issue tracks removing that dependency.

Rename map (old → new)

zosbase→zos_base · zoslight→zos_light · zos-config→zos_config · 0-initramfs→zos_initramfs · zinit→zos_zinit · rfs→zos_rfs · tfgrid-sdk-go→zos_sdk_go · tfgrid-sdk-rust→zos_sdk_rust · tfgrid-sdk-ts→zos_sdk_ts · tfgrid-sdk-dart→zos_sdk_dart · tfchain→ledger_chain · quantum-storage→qss_quantum_storage

P0 — fragile non-Go fetch URLs (release downloads, raw URLs, pubspec/Dockerfile deps). PRs open:

• zos — Update download/config URLs after repo renames #2692 (rfs, zos-config, doc links + setup-go CI fix)
• zos_light — Update download URLs after repo renames (rfs->zos_rfs, zinit->zos_zinit) zos_light#84 (rfs, zinit + setup-go CI fix)
• zos_v4 — Update rfs/zos-config URLs after repo renames zos_v4#30 (rfs, zos-config + setup-go CI fix)
• zos_initramfs — Fix package download URLs after repo renames (zinit->zos_zinit, rfs->zos_rfs) zos_initramfs#99 (dev-v3), difference between part of an IPv6 addr and ifacename #100 (dev-v4), add documentation how to configure exit node and create private networks #101 (dev-v3light) — zinit, rfs
• zos_base — Fix runtime config URL after zos-config repo rename (zos-config->zos_config) zos_base#117 (zos-config runtime URL)
• zos_images — Update zinit/tfgrid-sdk-go download URLs after repo renames zos_images#370 (zinit ×40, tfgrid-sdk-go tfrobot)
• qss_quantum_storage — Update zinit download URL after repo rename (zinit->zos_zinit) qss_quantum_storage#51 (zinit)
• zos_sdk_ts — Update zinit download URL after repo rename (zinit->zos_zinit) zos_sdk_ts#4506 (zinit Dockerfile)
• grid_connect — Update pubspec git deps after repo rename (tfgrid-sdk-dart->zos_sdk_dart) grid_connect#1239 (tfgrid-sdk-dart ×4 pubspec)
• tfgridv4-sdk-dart — Update pubspec git dep after repo rename (tfgrid-sdk-dart->zos_sdk_dart) tfgridv4-sdk-dart#16 (tfgrid-sdk-dart pubspec)
• zos_zinit — Repoint self-references from old repo name (zinit->zos_zinit) zinit#77 (self-referenced old name)

All URL edits verified to return 200 before push. No functional changes.

Remaining work

P1 — Go module-path migration (bottom-up, breaking; only needed so FUTURE releases / GOPROXY=direct don't rely on redirects)

Base libs first (rename module + fix internal imports + tag), then consumers update require+imports:

• zos_sdk_go (was tfgrid-sdk-go, 11 submodules — biggest fan-out; de-conflict rmb-sdk-go vs zos_sdk_go_v4)
• ledger_chain (was tfchain) — …/tfchain/clients/tfchain-client-go
• zos_base (was zosbase) — …/zosbase→…/zos_base, ~642 internal imports
• zos_light — currently declares …/zos4 on main by mistake (zos4 = zos_v4, forked from zoslight); give it its own path, NOT zos4
• Consumers: zos, zos_light, zos_v4, grid_agent, griddriver, grid_terraform, grid_pulumi, qss_quantum_storage/quantumd, grid_kyc_verifier

P2 — cosmetic docs/badges (bulk find/replace)

• grid_wiki (~630, incl. wiki/products/v3/*.toml repo=), zos_sdk_ts (~600 generated HTML/badges), grid_manual (~194), zos_base docs (~20), zos_rfs (5)

Follow-ups / notes

• zos_images master branch — replicate release pipeline: invalid version number for development flist #370 if that branch is actively built
• Verify ghcr.io/threefoldtech/tfchain image refs (grid_deployment, zos_sdk_dart CI) — container-registry names don't follow repo renames

Pre-existing issues found (NOT caused by the rename; separate fixes)

• mycelium checksum mismatch (v0.6.1 asset re-uploaded) → fix in fix(mycelium): update stale md5 checksum for v0.6.1 asset zos_v4#31
• virtwhat build: upstream git.annexia.org returns HTTP 503 → needs a reliable mirror
• zos_v4 wordpress / qss zdb-hook.sh: stale paths, already broken before rename
• Kernel workflow (zos_initramfs) chronically red since 2026-05: EOL ubuntu:18.04 container + deprecated node actions can't run Node 24 — needs workflow modernization

Golden rule

Never recreate/reuse an old repo name — that's the only thing that actually kills a redirect. Keep old names reserved as the safety net through the whole migration.