[Bug] Console output prompt lacks newline when running scripts in install.ps1

[Lutra-Fs]

Bug Report

Discussed in #6347

Current Behavior

When running a script in Scoop/lib/install.ps1, the line

Write-Host "Running $HookType script..." -NoNewline

outputs a prompt without a newline, which can cause the next command output to appear directly after the prompt, resulting in unclear or hard-to-read console output. For example:

Running pre_install script...OK

Expected Behavior

The prompt should appear clearly separated from subsequent output. Typically, this is achieved by omitting the -NoNewline parameter, so the user can easily distinguish the prompt from the command result.

Expected output example:

Running pre_install script...
OK

Additional context/output

• The relevant code is here:
  

  Scoop/lib/install.ps1

  Line 734 in 859d1db

  Write-Host "Running $HookType script..." -NoNewline

• This behaviour was discussed [here](Why run script prompt no-newlines? #6347).
• This may affect the overall readability and user experience, especially for users running scripts in terminals that don’t visually separate outputs well.

Possible Solution

Consider removing the -NoNewline flag from Write-Host at this location, or adding a newline character after the message. This will make the output easier to read and more consistent with typical command-line UX.

System details

Windows version: [Please fill in, e.g. 10, 11]
OS architecture: [Please fill in, e.g. 64bit, arm64]
PowerShell version: [Output of "$($PSVersionTable.PSVersion)"]
Additional software: [(optional) e.g. ConEmu, Git]

Scoop Configuration

// Paste your configuration here
N/A

---

Summary:
This issue is about improving console output clarity by adjusting a Write-Host usage in install.ps1 (line 734). See the discussion for more context: #6347

[Lutra-Fs]

Scoop/lib/install.ps1

Lines 526 to 530 in 5af29e1

	if($installer.script) {
	write-output "Running installer script..."
	iex $installer.script
	return
	}

Scoop/lib/install.ps1

Lines 1035 to 1056 in dd0f514

	function Invoke-HookScript {
	[CmdletBinding()]
	param(
	[Parameter(Mandatory = $true)]
	[ValidateSet('pre_install', 'post_install',
	'pre_uninstall', 'post_uninstall')]
	[String] $HookType,
	[Parameter(Mandatory = $true)]
	[ValidateNotNullOrEmpty()]
	[PSCustomObject] $Manifest,
	[Parameter(Mandatory = $true)]
	[ValidateSet('32bit', '64bit')]
	[String] $Arch
	)
	$script = arch_specific $HookType $Manifest $Arch
	if ($script) {
	Write-Output "Running $HookType script..."
	Invoke-Command ([scriptblock]::Create($script -join "`r`n"))
	}
	}

I did a bit of digging and it looks like the explicit -NoNewline flag wasn’t part of the original behavior - it was introduced in PR #5968 commit 2544745, which I would like to ping the commit author @niheaven for comments or any design choice around why -NoNewline was introduced here? Since the requested behaviour (with newline) feels more readable.
If there’s no strong reason to keep it, I’d be happy to open a small PR to drop that flag.

cc: @Ra2-IFV