Console.exe output file is not correctly predicted for .NET console projects

[snorrk]

The predicted output from a .NET console project is missing the exe file (and potentially the intermediate apphost.exe).

1. "dotnet new console"
2. Run predictors on the newly created project (see "Predicted output")
3. "dotnet build"
4. Compare actual output to predicted output

Files after build:

bin\debug\net8.0\DotnetConsole.deps.json
bin\debug\net8.0\DotnetConsole.dll
bin\debug\net8.0\DotnetConsole.exe
bin\debug\net8.0\DotnetConsole.pdb
bin\debug\net8.0\DotnetConsole.runtimeconfig.json
obj\debug\net8.0.NETCoreApp,Version=v8.0.AssemblyAttributes.cs
obj\debug\net8.0\apphost.exe
obj\debug\net8.0\DotnetConsole.AssemblyInfo.cs
obj\debug\net8.0\DotnetConsole.AssemblyInfoInputs.cache
obj\debug\net8.0\DotnetConsole.assets.cache
obj\debug\net8.0\DotnetConsole.csproj.CoreCompileInputs.cache
obj\debug\net8.0\DotnetConsole.csproj.FileListAbsolute.txt
obj\debug\net8.0\DotnetConsole.dll
obj\debug\net8.0\DotnetConsole.GeneratedMSBuildEditorConfig.editorconfig
obj\debug\net8.0\DotnetConsole.genruntimeconfig.cache
obj\debug\net8.0\DotnetConsole.pdb
obj\debug\net8.0\ref\DotnetConsole.dll
obj\debug\net8.0\refint\DotnetConsole.dll
obj\dotnetConsole.csproj.nuget.dgspec.json
obj\DotnetConsole.csproj.nuget.g.props
obj\DotnetConsole.csproj.nuget.g.targets
obj\project.assets.json
obj\project.nuget.cache

Predicted output:

bin\debug\net8.0\DotnetConsole.deps.json
bin\debug\net8.0\DotnetConsole.dll
bin\debug\net8.0\DotnetConsole.pdb
bin\debug\net8.0\DotnetConsole.runtimeconfig.json
bin\debug\net8.0\DotnetConsole.xml
obj\debug\net8.0\DotnetConsole.dll
obj\debug\net8.0\DotnetConsole.pdb
obj\debug\net8.0\DotnetConsole.xml
obj\debug\net8.0\ref\DotnetConsole.dll
obj\debug\net8.0\refint\DotnetConsole.dll
publish\debug\DotnetConsole.deps.json

Potentially missing from predicted output:

bin\debug\net8.0\DotnetConsole.exe
obj\debug\net8.0\apphost.exe

[dfederm]

Just checking, what's the scenario you're targeting that requires such accuracy? Obvious it would be ideal to get predictions as close as possible, but I'm not sure what lacking this specific prediction would prevent in any existing scenarios I'm aware of.