[P4] Reserve Fallout.* package IDs on nuget.org

[ChrisonSimtian]

Why now

Squatters watch the github trends + Reserved Names list. If we don't reserve our package IDs early, someone else can claim them. Even if we publish to GitHub Packages today, we want to lock in nuget.org names for future use.

Action

For each upcoming Fallout package, do one of:

1. Publish a placeholder `0.0.0-reserved` package with empty content — claims the ID immediately.
2. Submit a Reserved Names request to NuGet via https://www.nuget.org/policies/Reserved-Names — gets the `Fallout.*` prefix locked to our account, but takes admin time.

Recommend option 1 for speed. List of IDs to reserve:

```
Fallout.Common
Fallout.Build
Fallout.Build.Shared
Fallout.Components
Fallout.GlobalTool
Fallout.MSBuildTasks
Fallout.ProjectModel
Fallout.SolutionModel
Fallout.SourceGenerators
Fallout.Tooling
Fallout.Tooling.Generator
Fallout.Utilities
Fallout.Utilities.IO.Compression
Fallout.Utilities.IO.Globbing
Fallout.Utilities.Net
Fallout.Utilities.Text.Json
Fallout.Utilities.Text.Yaml
```

Required

• NuGet.org account under organization or personal handle
• NuGet API key with package-create scope

Done when

• All 17 IDs registered (placeholder `0.0.0-reserved` or via Reserved Names policy)
• Owner verified — we control the IDs
• Document the chosen account in the strategy memory

[ChrisonSimtian]

Re-scope after the #35 bridge strategy

The original framing here ("squatters can claim our IDs if we delay") still stands, but the urgency has shifted now that #35 settled on GitHub Packages as the primary distribution feed during the rebrand window:

• Canonical `Fallout.` packages publish to our GH Packages feed, not nuget.org. See docs/rebrand-plan.md § Bridge strategy.
• nuget.org publication is a post-rebrand-window concern — likely lands somewhere around the shim sunset (R0 + 12-24mo per the timeline in the plan doc).
• The bridge `Nuke.` shim packages also publish to our GH feed only, so there's no immediate nuget.org collision exposure either.

What this means for this issue

The placeholder-publish step (option 1 in the body) is still worth doing, just not as a P4-blocker. It's defensive — squatter prevention — independent of when we actually start using the IDs. Doable in ~30 minutes any time we have an empty package CI lane.

Action proposal:

• Demote out of the rebrand milestone — this isn't on the critical path for the rename.
• Track as a standalone "defensive nuget.org reservation" task to do whenever convenient.
• Re-evaluate priority when planning the actual nuget.org migration phase.

Will leave open for the milestone owner to decide; happy to execute the placeholder publish if you give the green light on the nuget.org account/API key setup.

[ChrisonSimtian]

Update 2026-05-21: Reservation request submitted to support@nuget.org.

Prefix requested: Fallout (covers Fallout.*). Cited the 15 currently-published packages at v10.2.12 as evidence.

Holding this issue open until Microsoft responds (typical turnaround 1–7 business days). Will update with the outcome.

[ChrisonSimtian]

Approved by Microsoft — Fallout.* prefix is now reserved on nuget.org. Published packages get the verified-owner badge; nobody else can publish to the namespace.