Status StartAsync stopping program, not working

[ghost]

Information

• OS: Linux
• Version: 0.48.0
• Terminal: VSCode Integrated terminal / Alacritty

Describe the bug
While trying to run AnsiConsole.Status().StartAsync(), the spinner doesn't show up, and after a CliWrap function finishes executing, the program exits with no exceptions or prints, despite there being more prints inside the Status function, as well as outside of it.

To Reproduce
Add latest CliWrap and Spectre.Console packages to a .NET 8 project. In a separate function that is called from Main(), put

        var output = await AnsiConsole.Status().StartAsync("Generating files", async ctx =>
        {  
            ctx.Spinner(Spinner.Known.Ascii);
            AnsiConsole.WriteLine("Hey, Wilbrand! Can you help me out real quick?");
            BufferedCommandResult? result = null;
            try {
                result = await Cli.Wrap(Path.Join(Directory.GetParent(Environment.ProcessPath).FullName, "/extra/wilbrand"))
            .WithArguments(new[] { macaddr, DateTime.Now.ToShortDateString(), version, sd })
            .ExecuteBufferedAsync(); //program seems to exit here? no more prints after this
            } catch (Exception e) {
                AnsiConsole.WriteLine(e.ToString());
            }
            
            await Task.Delay(5000);
            if (result.StandardError == "") {
                AnsiConsole.WriteLine("Thanks bro!");
            } else {
                AnsiConsole.MarkupLine("[red]It's alright if you messed up, you tried your best.[/]\n\n[red dim]Try again, maybe?[/]");
                Environment.Exit(1);
            }
            return result.StandardOutput;
        });
        AnsiConsole.Markup($"[grey dim italics]{output}");
        AnsiConsole.MarkupLine("[bright green]Done! Check your SD card for a surprise ;)");

And then run the program, with macaddr, version, and sd variables being strings.
Expected behavior
A spinner to appear as the external program is run, then the output of the program to be printed in the console, as well as the three prints that come after the CliWrap function.

Screenshots

Additional context
N/A