Function breakpoints allow entry of a condition / hit count but do not add the condition to the PS breakpoint

Prerequisites

• I have written a descriptive issue title.
• I have searched all open and closed issues to ensure it has not already been reported.
• I have read the troubleshooting guide.
• I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
• I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
• If this is a security issue, I have read the security issue reporting guidance.

Summary

In the breakpoints section of the debug window you can click the + icon and add a 'function' breakpoint (which will also work with aliases, scripts and external executables - trying to step into all of them), these breakpoints get a different icon and when the debugger runs a System.Management.Automation.CommandBreakpoint object is created in the PowerShell session.
Right clicking the breakpoint allows you to edit hit count or function condition. But the when the commandBreakpoint is created the condition is not added as an action as it is with a lineBreakpoint

PowerShell Version

Name                           Value
----                           -----
PSVersion                      7.5.4
PSEdition                      Core
GitCommitId                    7.5.4
OS                             Microsoft Windows 10.0.26200
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0


[DBG] PS>>$host

Name             : Visual Studio Code Host
Version          : 2025.4.0
InstanceId       : 780cf936-5214-4960-8b15-a871508190dd
UI               : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture   : en-GB
CurrentUICulture : en-GB
PrivateData      : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled  : True
IsRunspacePushed : False
Runspace         : System.Management.Automation.Runspaces.LocalRunspace

Visual Studio Code Version

1.105.1
7d842fb85a0275a4a8e4d7e040d2625abbf7f084
x64

Extension Version

ms-vscode.powershell@2025.4.0

Steps to Reproduce

Save the following to a file
function test {
param($p)
process {
write-host $p
}
}

Write-Host "Line 1"
test 123
Write-Host "Line 2"

With debug selected, click the + icon on the breakpoints pane to add a function break point
enter "test"

start the debugger and run the script it should stop on the the process line continue and let the script exit.

Now click the pencil next to the Test function break point and enter $isLinux if you are NOT using linux and $isWindows if you are , to get something we no will evaluate false.

Start the debugger again - the breakpoint should not fire, but it does.
Run Get-PsBreakpoint and not there is no action.

Repeat the process setting a hit count.

For LINE break points actions ARE set for hit count or condition

Visuals

No response

Logs

No response

Start at the extension's debugger handling for function breakpoints and compare it with line breakpoint handling, using the CommandBreakpoint and Get-PSBreakpoint behavior described in the report. Reproduce the condition and hit-count cases from the steps, then verify that the resulting PowerShell breakpoint includes the expected action and does not fire when its condition is false.