chore(globaltool)!: rename Fallout.GlobalTool → Fallout.Cli

AssemblyInfo.cs

@@ -10,8 +10,8 @@
 [assembly: InternalsVisibleTo("Fallout.Build.Tests")]
 [assembly: InternalsVisibleTo("Fallout.Common")]
 [assembly: InternalsVisibleTo("Fallout.Common.Tests")]
-[assembly: InternalsVisibleTo("Fallout.GlobalTool")]
-[assembly: InternalsVisibleTo("Fallout.GlobalTool.Tests")]
+[assembly: InternalsVisibleTo("Fallout.Cli")]
+[assembly: InternalsVisibleTo("Fallout.Cli.Tests")]
 [assembly: InternalsVisibleTo("Fallout.ProjectModel.Tests")]
 [assembly: InternalsVisibleTo("Fallout.SourceGenerators")]
 [assembly: InternalsVisibleTo("Fallout.SolutionModel")]

CLAUDE.md

@@ -40,7 +40,7 @@ Production project groupings under `src/`:
 | Core framework | `Fallout.Common`, `Fallout.Build`, `Fallout.Build.Shared`, `Fallout.Components`, `Fallout.Tooling` |
 | Code generation | `Fallout.SourceGenerators`, `Fallout.Tooling.Generator` |
 | Models | `Fallout.ProjectModel`, `Fallout.SolutionModel` |
-| Tooling | `Fallout.GlobalTool`, `Fallout.MSBuildTasks` |
+| Tooling | `Fallout.Cli`, `Fallout.MSBuildTasks` |
 | Migration | `Fallout.Migrate` (CLI for NUKE → Fallout repo migration) |
 | Utilities | `Fallout.Utilities`, `Fallout.Utilities.IO.Compression`, `Fallout.Utilities.IO.Globbing`, `Fallout.Utilities.Net`, `Fallout.Utilities.Text.Json`, `Fallout.Utilities.Text.Yaml` |
 | Vendored | `Fallout.VisualStudio.SolutionPersistence` (fork of upstream `Microsoft.VisualStudio.SolutionPersistence`, sources in `vendor/`) |

CONTRIBUTING.md

@@ -44,7 +44,7 @@ Fallout welcomes contributions. As a community, we want to help each other, prov
 - Branch from `main`. Name your branch `feature/<slug>`, `bugfix/<slug>`, or `chore/<slug>`.
 - Make sure your employer allows the contribution.
 - Read [CLAUDE.md](CLAUDE.md) for the codebase conventions — package versions go in `Directory.Packages.props`, license headers are mechanical, tests live next to code.
-- The bootstrappers are now thin: `./build.ps1` / `./build.sh` provision .NET if needed, then run `dotnet tool restore` + `dotnet fallout "$@"`. The `Fallout.GlobalTool` version is pinned in `.config/dotnet-tools.json`.
+- The bootstrappers are now thin: `./build.ps1` / `./build.sh` provision .NET if needed, then run `dotnet tool restore` + `dotnet fallout "$@"`. The `Fallout.Cli` version is pinned in `.config/dotnet-tools.json`.
 - Run `./build.ps1 Test` (or `./build.sh Test`, or directly `dotnet fallout Test` once your tools are restored) locally first.
 
 ### When writing the PR

Directory.Packages.props

@@ -43,7 +43,7 @@
     <PackageVersion Include="xunit" Version="2.9.3" />
     <PackageVersion Include="xunit.runner.visualstudio" Version="3.1.5" />
   </ItemGroup>
-  <!-- Roslyn (Fallout.SourceGenerator + Fallout.GlobalTool + Fallout.Migrate.Analyzers) -->
+  <!-- Roslyn (Fallout.SourceGenerator + Fallout.Cli + Fallout.Migrate.Analyzers) -->
   <ItemGroup>
     <PackageVersion Include="Microsoft.CodeAnalysis.Analyzers" Version="3.11.0" />
     <PackageVersion Include="Microsoft.CodeAnalysis.CSharp" Version="4.12.0" />

build/Build.cs

@@ -83,7 +83,7 @@ private static int ParseMajor(string informationalVersion)
             .ClearProperties());
 
     IEnumerable<(Fallout.Common.ProjectModel.Project Project, string Framework)> ICompile.PublishConfigurations =>
-        from project in new[] { Solution.Fallout_GlobalTool, Solution.Fallout_MSBuildTasks }
+        from project in new[] { Solution.Fallout_Cli, Solution.Fallout_MSBuildTasks }
         from framework in project.GetTargetFrameworks()
         select (project, framework);
 
@@ -256,8 +256,8 @@ IEnumerable<AbsolutePath> NuGetPackageFiles
         .DependsOn<IPack>()
         .Executes(() =>
         {
-            SuppressErrors(() => DotNet($"tool uninstall -g {Solution.Fallout_GlobalTool.Name}"), logWarning: false);
-            DotNet($"tool install -g {Solution.Fallout_GlobalTool.Name} --add-source {OutputDirectory} --version {DefaultDeploymentVersion}");
+            SuppressErrors(() => DotNet($"tool uninstall -g {Solution.Fallout_Cli.Name}"), logWarning: false);
+            DotNet($"tool install -g {Solution.Fallout_Cli.Name} --add-source {OutputDirectory} --version {DefaultDeploymentVersion}");
         });
 
     T From<T>()

docs/01-getting-started/01-installation.md

@@ -6,11 +6,11 @@ Before you can set up a build project, you need to install Fallout's dedicated [
 
 ```powershell
 # terminal-command
-dotnet tool install Fallout.GlobalTool --global
+dotnet tool install Fallout.Cli --global
 ```
 
 :::tip
-For repos that already have a `.config/dotnet-tools.json` manifest with `Fallout.GlobalTool` pinned (this is what `fallout :setup` creates), you can skip the global install and run `dotnet tool restore` instead — the local manifest version then takes precedence.
+For repos that already have a `.config/dotnet-tools.json` manifest with `Fallout.Cli` pinned (this is what `fallout :setup` creates), you can skip the global install and run `dotnet tool restore` instead — the local manifest version then takes precedence.
 :::
 
 From now on, you can use the global tool to:

docs/01-getting-started/02-setup.md

@@ -34,7 +34,7 @@ The setup will create a number of files in your repository and – if you've cho
 ```bash
 <root-directory>
 ├── .config
-│   └── dotnet-tools.json           # Local tool manifest pinning Fallout.GlobalTool
+│   └── dotnet-tools.json           # Local tool manifest pinning Fallout.Cli
 │
 ├── .fallout                        # Root directory marker
 │   ├── build.schema.json           # Build schema file
@@ -51,7 +51,7 @@ The setup will create a number of files in your repository and – if you've cho
 ```
 
 :::note
-The two thin bootstrappers (`build.ps1` and `build.sh`) provision the .NET SDK locally when it's not on `PATH`, then run `dotnet tool restore` and `dotnet fallout "$@"`. They're optional once you have a global `dotnet` install and have run `dotnet tool restore` at least once — but they're the safest way to run the build in CI and on a freshly-cloned machine. The `.config/dotnet-tools.json` manifest pins the exact `Fallout.GlobalTool` version your build expects.
+The two thin bootstrappers (`build.ps1` and `build.sh`) provision the .NET SDK locally when it's not on `PATH`, then run `dotnet tool restore` and `dotnet fallout "$@"`. They're optional once you have a global `dotnet` install and have run `dotnet tool restore` at least once — but they're the safest way to run the build in CI and on a freshly-cloned machine. The `.config/dotnet-tools.json` manifest pins the exact `Fallout.Cli` version your build expects.
 :::
 
 ## Project Structure
@@ -64,7 +64,7 @@ While you can enjoy writing most build-relevant logic inside your build console
 ```powershell
 <root-directory>
 ├── .config
-│   └── dotnet-tools.json    # Local tool manifest (Fallout.GlobalTool pin)
+│   └── dotnet-tools.json    # Local tool manifest (Fallout.Cli pin)
 │
 ├── .fallout
 │   ├── parameters.json      # Parameters files

docs/01-getting-started/03-execution.md

@@ -34,7 +34,7 @@ fallout [arguments]
 </Tabs>
 
 :::info
-The bootstrappers are thin: they provision the .NET SDK if it isn't already installed, run `dotnet tool restore` (to pin the `Fallout.GlobalTool` version from `.config/dotnet-tools.json`), then forward to `dotnet fallout`. Once `dotnet` is on your `PATH` and tools are restored, `fallout [arguments]` and `./build.sh [arguments]` do the same thing.
+The bootstrappers are thin: they provision the .NET SDK if it isn't already installed, run `dotnet tool restore` (to pin the `Fallout.Cli` version from `.config/dotnet-tools.json`), then forward to `dotnet fallout`. Once `dotnet` is on your `PATH` and tools are restored, `fallout [arguments]` and `./build.sh [arguments]` do the same thing.
 :::
 
 :::info

docs/03-common/07-solution-project-model.md

@@ -33,7 +33,7 @@ With an instance of the `Solution` type you can **read and write the solution**
 
 ```csharp
 // Gather projects
-var globalToolProject = Solution.GetProject("Fallout.GlobalTool");
+var globalToolProject = Solution.GetProject("Fallout.Cli");
 var testProjects = Solution.GetAllProjects("*.Tests");
 
 // Gather all solution items

docs/05-cicd/github-actions.md

@@ -98,7 +98,7 @@ jobs:
 ```
 
 :::info
-The generated workflow uses `actions/setup-dotnet` to install the .NET SDK on the runner, then `dotnet tool restore` to install the `Fallout.GlobalTool` version pinned in `.config/dotnet-tools.json`, then `dotnet fallout <targets>` to run your build. Your repository needs a `.config/dotnet-tools.json` manifest with `Fallout.GlobalTool` pinned — `fallout :setup` creates one automatically.
+The generated workflow uses `actions/setup-dotnet` to install the .NET SDK on the runner, then `dotnet tool restore` to install the `Fallout.Cli` version pinned in `.config/dotnet-tools.json`, then `dotnet fallout <targets>` to run your build. Your repository needs a `.config/dotnet-tools.json` manifest with `Fallout.Cli` pinned — `fallout :setup` creates one automatically.
 :::
 
 </details>

docs/adr/0002-cross-provider-auth-and-secret-conventions.md

@@ -14,7 +14,7 @@ Fallout already has mature primitives that are scattered and worth surfacing:
 - **`[Parameter]`** (`src/Fallout.Build/ParameterAttribute.cs:34`) — declarative field injection from CLI args + env vars.
 - **`[Secret]`** (`src/Fallout.Build/ParameterAttribute.cs:76`) — marker attribute; semantically "do not log this value." Currently a passive marker — actual log-scrubbing behaviour needs explicit framework-side support (see Open Questions).
 - **`CredentialStore`** (`src/Fallout.Build/Utilities/CredentialStore.cs`) — macOS Keychain wrapper. Linux/Windows fall back to prompt-only.
-- **Encrypted parameters file** — `parameters.json` (+ named profiles `parameters.<profile>.json`), AES-encrypted with a password held in the Keychain or prompted for. Managed interactively via `dotnet fallout :secrets` (`src/Fallout.GlobalTool/Program.Secrets.cs`).
+- **Encrypted parameters file** — `parameters.json` (+ named profiles `parameters.<profile>.json`), AES-encrypted with a password held in the Keychain or prompted for. Managed interactively via `dotnet fallout :secrets` (`src/Fallout.Cli/Program.Secrets.cs`).
 - **`ImportSecrets`** on `[GitHubActions]` (`src/Fallout.Common/CI/GitHubActions/GitHubActionsAttribute.cs:65`) — declares which `[Parameter, Secret]` fields the workflow should inject from GitHub's secret store, mapped via `SplitCamelHumpsWithKnownWords().JoinUnderscore().ToUpperInvariant()` (line 217).
 - **Provider-sourced injection** — `AzureKeyVaultSecretAttribute`, `AppVeyorSecretAttribute` already exist. They're a third category: **runtime-resolved value providers** that look up the secret from an external store on startup, no env-var hop required.
 
@@ -148,7 +148,7 @@ Skip the existing infrastructure; layer on a standard .NET configuration provide
 - [ADR-0001](0001-cd-primitives-attributes-vs-tasks.md) — the two CD patterns this layers on
 - `src/Fallout.Build/ParameterAttribute.cs:34,76` — `ParameterAttribute` and `SecretAttribute` definitions
 - `src/Fallout.Build/Utilities/CredentialStore.cs` — macOS Keychain wrapper
-- `src/Fallout.GlobalTool/Program.Secrets.cs` — encrypted parameters file CLI
+- `src/Fallout.Cli/Program.Secrets.cs` — encrypted parameters file CLI
 - `src/Fallout.Common/CI/GitHubActions/GitHubActionsAttribute.cs:217` — canonical name derivation (`SplitCamelHumpsWithKnownWords().JoinUnderscore().ToUpperInvariant()`)
 - `src/Fallout.Common/Tools/AzureKeyVault/AzureKeyVaultSecretAttribute.cs` — runtime value-provider precedent (step 3 of the resolution chain)
 - RFC [#113](https://github.com/ChrisonSimtian/Fallout/issues/113) — deployment agent (needs the resolution chain to authenticate to coordinators)

docs/architecture.md

@@ -61,7 +61,7 @@ Images, icons, logos, and other non-code binary content live under `.assets/`. T
 | Core framework | `Fallout.Common`, `Fallout.Build`, `Fallout.Build.Shared`, `Fallout.Components`, `Fallout.Tooling` | The API consumers reference and the host runtime that executes targets. |
 | Code generation | `Fallout.SourceGenerators`, `Fallout.Tooling.Generator` | Roslyn source generators that produce per-target code at compile time, plus the `.cs`-from-`.json` tool-wrapper generator. |
 | Models | `Fallout.ProjectModel`, `Fallout.SolutionModel` | Strongly-typed wrappers over `.csproj` / `.sln` / `.slnx`. |
-| Tooling | `Fallout.GlobalTool`, `Fallout.MSBuildTasks` | The `dotnet fallout` global tool and the MSBuild tasks layer it builds on. |
+| Tooling | `Fallout.Cli`, `Fallout.MSBuildTasks` | The `dotnet fallout` global tool and the MSBuild tasks layer it builds on. |
 | Utilities | `Fallout.Utilities` + sub-packages (`IO.Compression`, `IO.Globbing`, `Net`, `Text.Json`, `Text.Yaml`) | Standalone helpers reusable outside the build context. |
 
 Every project under `src/` has a sibling under `tests/` (e.g. `src/Fallout.Common/` → `tests/Fallout.Common.Tests/`).

docs/dependencies.md

@@ -14,7 +14,7 @@ Central package versions are pinned in `Directory.Packages.props`; this page lin
 |---|---|---|
 | `Microsoft.Build` (+ `.Framework`, `.Tasks.Core`, `.Utilities.Core`) | MSBuild engine — read/evaluate `.csproj`/`.props` files | `Fallout.ProjectModel`, `Fallout.MSBuildTasks` |
 | `Microsoft.Build.Locator` | Locate an installed MSBuild at runtime | `Fallout.ProjectModel` |
-| `Microsoft.CodeAnalysis.*` (CSharp, Workspaces, MSBuild, Analyzers) | Roslyn — C# parsing/compilation/analysis | `Fallout.SourceGenerators`, `Fallout.GlobalTool` (Cake rewriter) |
+| `Microsoft.CodeAnalysis.*` (CSharp, Workspaces, MSBuild, Analyzers) | Roslyn — C# parsing/compilation/analysis | `Fallout.SourceGenerators`, `Fallout.Cli` (Cake rewriter) |
 | `Microsoft.Extensions.DependencyModel` | Parse `.deps.json` runtime metadata | `Fallout.Build` |
 | `Microsoft.SourceLink.GitHub` | Source-link symbols into published nupkgs so debuggers can step into Fallout | All packable libs |
 | `Nerdbank.GitVersioning` | Build-time semver derived from git history | All packable libs |
@@ -46,7 +46,7 @@ Central package versions are pinned in `Directory.Packages.props`; this page lin
 |---|---|---|
 | `NJsonSchema` + `.NewtonsoftJson` | Generate `build.schema.json` so IDEs can auto-complete `--params` | Drags `Newtonsoft.Json` transitively |
 | `Newtonsoft.Json` | Legacy JSON — direct usage in older codepaths | Long-term consolidation to `System.Text.Json` tracked in [#83](https://github.com/ChrisonSimtian/Fallout/issues/83) |
-| `Scriban` | Templating engine | Used by `Fallout.GlobalTool` Cake rewriter only. **Open CVE NU1903 tracked in [#84](https://github.com/ChrisonSimtian/Fallout/issues/84).** |
+| `Scriban` | Templating engine | Used by `Fallout.Cli` Cake rewriter only. **Open CVE NU1903 tracked in [#84](https://github.com/ChrisonSimtian/Fallout/issues/84).** |
 
 ## Text, IO, archives
 

docs/introduction.md

@@ -18,7 +18,7 @@ description: Fallout is a C#-first build automation framework for .NET — the h
 
 ```powershell
 # terminal-command
-dotnet tool install Fallout.GlobalTool --global
+dotnet tool install Fallout.Cli --global
 ```
 
 **2. Go to a repository of your choice and set up a build:**
@@ -45,7 +45,7 @@ Get a feeling how your Cake scripts would look like in Fallout.
 
 ```powershell
 # terminal-command
-dotnet tool install Fallout.GlobalTool --global
+dotnet tool install Fallout.Cli --global
 ```
 
 **2. Go to a repository built with Cake.**

docs/rebrand-plan.md

@@ -45,7 +45,7 @@ This is locked by the bridge-package design — `[TypeForwardedTo]` requires the
 | `Nuke.Common.Utilities` (+ `.Collections`, `.Net`) | `Fallout.Common.Utilities` | |
 | `Nuke.Common.ValueInjection` | `Fallout.Common.ValueInjection` | |
 | `Nuke.Components` | `Fallout.Components` | |
-| `Nuke.GlobalTool` (+ `.Rewriting.Cake`) | `Fallout.GlobalTool` | |
+| `Nuke.GlobalTool` (+ `.Rewriting.Cake`) | `Fallout.Cli` | Renamed from `Fallout.GlobalTool` post-rebrand for install ergonomics (`dotnet tool install Fallout.Cli`). Command name stays `fallout`. |
 | `Nuke.MSBuildTasks` | `Fallout.MSBuildTasks` | |
 | `Nuke.SourceGenerators` | `Fallout.SourceGenerators` | |
 | `Nuke.Utilities.Text.Json` | `Fallout.Utilities.Text.Json` | |

fallout.slnx

@@ -14,7 +14,7 @@
   <Project Path="src\Fallout.Build\Fallout.Build.csproj" />
   <Project Path="src\Fallout.Common\Fallout.Common.csproj" />
   <Project Path="src\Fallout.Components\Fallout.Components.csproj" />
-  <Project Path="src\Fallout.GlobalTool\Fallout.GlobalTool.csproj" />
+  <Project Path="src\Fallout.Cli\Fallout.Cli.csproj" />
   <Project Path="src\Fallout.Migrate\Fallout.Migrate.csproj" />
   <Project Path="src\Fallout.Migrate.Analyzers\Fallout.Migrate.Analyzers.csproj" />
   <Project Path="src\Shims\Nuke.Build\Nuke.Build.csproj" />
@@ -35,7 +35,7 @@
   <Project Path="src\Fallout.Utilities\Fallout.Utilities.csproj" />
   <Project Path="tests\Fallout.Build.Tests\Fallout.Build.Tests.csproj" />
   <Project Path="tests\Fallout.Common.Tests\Fallout.Common.Tests.csproj" />
-  <Project Path="tests\Fallout.GlobalTool.Tests\Fallout.GlobalTool.Tests.csproj" />
+  <Project Path="tests\Fallout.Cli.Tests\Fallout.Cli.Tests.csproj" />
   <Project Path="tests\Fallout.Migrate.Tests\Fallout.Migrate.Tests.csproj" />
   <Project Path="tests\Fallout.Migrate.Analyzers.Tests\Fallout.Migrate.Analyzers.Tests.csproj" />
   <Project Path="tests\Nuke.Common.Shim.Tests\Nuke.Common.Shim.Tests.csproj" />

src/Fallout.Build/Execution/Extensions/UpdateNotificationAttribute.cs

@@ -40,9 +40,9 @@ private static void Notify()
             {
                 "--- UPDATE RECOMMENDED FROM 5.1.0 ---",
                 "1. Update your global tool",
-                "   dotnet tool update Fallout.GlobalTool -g",
+                "   dotnet tool update Fallout.Cli -g",
                 "2. Update your build",
-                "   nuke :update",
+                "   fallout :update",
                 "3. Confirm on update for configuration file and build scripts",
                 "   (Others are be optional)",
                 string.Empty

src/Fallout.Build/Telemetry/Telemetry.cs

@@ -32,7 +32,7 @@
     private const string VersionPropertyName = "FalloutTelemetryVersion";
     private const string LegacyVersionPropertyName = "NukeTelemetryVersion";
 
     private static readonly int? s_confirmedVersion;
 
     static Telemetry()
     {
@@ -52,7 +52,7 @@
         AbsolutePath GetCookieFile(string name, int version)
             => Constants.GlobalFalloutDirectory / "telemetry-awareness" / $"v{version}" / name;
 
-        // Check for calls from Fallout.GlobalTool and custom global tools
+        // Check for calls from Fallout.Cli and custom global tools
         if (SuppressErrors(() => FalloutBuild.BuildProjectFile, logWarning: false) == null)
         {
             var cookieName = Assembly.GetEntryAssembly().NotNull().GetName().Name;
@@ -84,7 +84,7 @@
 
         for (var version = CurrentVersion; version > 0; version--)
         {
-            var cookieFile = GetCookieFile("Fallout.GlobalTool", version);
+            var cookieFile = GetCookieFile("Fallout.Cli", version);
             if (cookieFile.FileExists())
                 return version;
         }

src/Fallout.Build/Utilities/SchemaUtility.cs

@@ -100,7 +100,7 @@ private static JsonObject BuildSchema(IFalloutBuild build)
             userSchema["properties"] = userProperties;
 
         // BuildProjectFile is read by the Fallout global tool's in-tool runner from .fallout/parameters.json
-        // (see Fallout.GlobalTool.BuildProjectResolver). It's not a [Parameter] on the build itself, but we
+        // (see Fallout.Cli.BuildProjectResolver). It's not a [Parameter] on the build itself, but we
         // surface it in the schema so editors offer IntelliSense when consumers configure a non-conventional
         // build project path.
         baseProperties["BuildProjectFile"] = new JsonObject

src/Fallout.GlobalTool/BuildProjectResolver.cs → src/Fallout.Cli/BuildProjectResolver.cs

@@ -9,7 +9,7 @@
 using Fallout.Common.Utilities;
 using static Fallout.Common.Constants;
 
-namespace Fallout.GlobalTool;
+namespace Fallout.Cli;
 
 /// <summary>
 /// Resolves the build project file (.csproj) for a Fallout-managed repository.

src/Fallout.GlobalTool/Program.AddPackage.cs → src/Fallout.Cli/Program.AddPackage.cs

@@ -12,7 +12,7 @@
 using Fallout.Common.Tooling;
 using Fallout.Common.Tools.DotNet;
 
-namespace Fallout.GlobalTool;
+namespace Fallout.Cli;
 
 partial class Program
 {

src/Fallout.GlobalTool/Program.Cake.cs → src/Fallout.Cli/Program.Cake.cs

@@ -14,11 +14,11 @@
 using Fallout.Common.ProjectModel;
 using Fallout.Common.Tooling;
 using Fallout.Common.Utilities;
-using Fallout.GlobalTool.Rewriting.Cake;
+using Fallout.Cli.Rewriting.Cake;
 using static Fallout.Common.Constants;
 using static Fallout.Common.EnvironmentInfo;
 
-namespace Fallout.GlobalTool;
+namespace Fallout.Cli;
 
 partial class Program
 {

src/Fallout.GlobalTool/Program.Complete.cs → src/Fallout.Cli/Program.Complete.cs

@@ -12,7 +12,7 @@
 using Fallout.Utilities.Text.Yaml;
 using static Fallout.Common.Constants;
 
-namespace Fallout.GlobalTool;
+namespace Fallout.Cli;
 
 partial class Program
 {

src/Fallout.GlobalTool/Program.GetConfiguration.cs → src/Fallout.Cli/Program.GetConfiguration.cs

@@ -12,7 +12,7 @@
 using Fallout.Common.Utilities;
 using Fallout.Common.Utilities.Collections;
 
-namespace Fallout.GlobalTool;
+namespace Fallout.Cli;
 
 partial class Program
 {