Move the SatisfactorySaveNet repo under the erp-for-factory-games org

[ChrisonSimtian]

Updated 2026-08-09 per ADR-0029.

Both repos we depend on live under the personal account ChrisonSimtian, but they're project infrastructure. The erp-for-factory-games org currently holds exactly one repo. Moving them makes ownership match reality — bus-factor, issue triage, and package publishing all stop being tied to one personal account.

Fork	Upstream	Licence	Role	Divergence
SatisfactorySaveNet	R3dByt3/SatisfactorySaveNet	MIT	Runtime — PackageReference in Satisfactory.Infrastructure	21 ahead, 0 behind — we're the maintained line
CUE4Parse	FabianFG/CUE4Parse	Apache-2.0	Build-time only — tools/SatisfactoryPakExtractor	0 ahead, 0 behind — pristine mirror

Scope

• Transfer SatisfactorySaveNet → erp-for-factory-games/Satisfactory (rename per ADR-0029 §1).
• Transfer CUE4Parse mirror → erp-for-factory-games.
• Update .gitmodules for whatever submodules still exist at that point (Consume upstream CUE4Parse from nuget.org and drop the vendor submodule #310 and Rebrand SatisfactorySaveNet fork as ErpForFactoryGames.Satisfactory.Saves on nuget.org #312 each remove one — if both land first, this is a no-op).
• Repoint the CUE4Parse publish workflow at the org's GitHub Packages feed (https://nuget.pkg.github.com/erp-for-factory-games/index.json).
• Update CLAUDE.md, .claude/README.md, and nuget.config comments naming ChrisonSimtian.
• Verify the CI GITHUB_TOKEN / packages: read grant still resolves cross-repo within the org (still needed for the extractor tools, not for the solution).

Gotchas

• GitHub redirects old repo URLs after transfer, so submodules and clones keep working. GitHub Packages feed URLs do not redirect — already-published versions stay on the old feed. Plan a republish or version bump.
• A fork transferred between owners keeps its fork relationship, so upstream PRs still work.

Sequencing

Land #312 first (nuget.org publish). That's what removes the nuget.config credentials/mapping complexity, so this transfer only has to be done once and against a much smaller surface.

Out of scope

• Publishing to nuget.org (Rebrand SatisfactorySaveNet fork as ErpForFactoryGames.Satisfactory.Saves on nuget.org #312) or GitHub Packages (Consume upstream CUE4Parse from nuget.org and drop the vendor submodule #310).
• Any code change inside either repo.

[ChrisonSimtian]

Scope reduced by #314: CUE4Parse no longer needs an org mirror at all — we consume upstream's rolling builds from nuget.org directly, and the submodule is gone. This issue now covers only the SatisfactorySaveNet → erp-for-factory-games/Satisfactory transfer.

[ChrisonSimtian]

Done — but as a hard fork, not a transfer

Chris called it: we are not feeding changes back upstream, so a GitHub transfer (which preserves the fork relationship) was the wrong mechanism. Created fresh at erp-for-factory-games/Satisfactory with the full history pushed in — 71 commits, 3 tags, is_fork: false.

ChrisonSimtian/SatisfactorySaveNet is left untouched rather than transferred, so nothing that currently consumes it breaks.

Attribution kept intact

MIT obliges us to preserve the notice, and upstream never filled theirs in — it still reads Copyright (c) [year] [fullname]. The new LICENSE keeps the grant verbatim and attributes the original to R3dByt3 and contributors, so the lineage isn't lost by accident. The README states the fork relationship plainly and warns that the upstream SatisfactorySaveNet package on nuget.org is a different project.

One trap worth recording

The inherited ci.yml publishes to GitHub Packages on every push to main, targeting nuget.pkg.github.com/${{ github.repository_owner }}. Pushing history to the org would have immediately published SatisfactorySaveNet packages under erp-for-factory-games — to precisely the feed ADR-0029 retires, under the old package identity.

Actions were disabled on the repo before the first push, the publish job was then gated behind if: false && … with a comment explaining what must happen first, and Actions re-enabled so build/test still runs. Re-enable publishing only as part of #315 → #312; dropping the false && alone would republish under the old name to the wrong feed.

Remaining

nuget.config in this repo still points at github-chrisonsimtian, and Satisfactory.Infrastructure still references SatisfactorySaveNet 4.1.6 from it. That switch is #312's job and needs #315 first — nothing is broken meanwhile.