Address mklement0 feedback: throw suppression, Ignore/$Error, advanced escalation

Three corrections based on mklement0's review:

1. throw CAN be suppressed by $ErrorActionPreference when set to
   SilentlyContinue or Ignore. Removed the incorrect claim that throw
   is "always" script-terminating "regardless of $ErrorActionPreference".
   Also documented that -ErrorAction on advanced functions translates
   to a scope-local $ErrorActionPreference, so it suppresses throw too.

2. Added NOTE that $ErrorActionPreference = 'Ignore' still records
   terminating errors in $Error. Ignore only prevents $Error recording
   for non-terminating errors.

3. Escalation section now documents the advanced vs. non-advanced
   distinction: $ErrorActionPreference = 'Stop' produces
   script-terminating errors in non-advanced contexts, but
   statement-terminating errors in advanced contexts ([CmdletBinding()]).
   Summary table updated to reflect both contexts.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Author: 2 people

reference/7.6/Microsoft.PowerShell.Core/About/about_Error_Handling.md

@@ -89,7 +89,8 @@ statement. Script-terminating errors are generated by:
 - The `throw` keyword
 - Parse errors (syntax errors that prevent the script from being compiled)
 - Non-terminating errors **escalated** by `-ErrorAction Stop` or
-  `$ErrorActionPreference = 'Stop'` (see [How escalation works][05])
+  `$ErrorActionPreference = 'Stop'` in non-advanced contexts (see
+  [How escalation works][05])
 - Certain critical engine failures
 
 ```powershell
@@ -103,9 +104,17 @@ Test-Throw
 Write-Output 'This never runs either (unless caught)'
 ```
 
-The `throw` keyword always generates a script-terminating error regardless of
-`$ErrorActionPreference`. Setting `$ErrorActionPreference` to
-`SilentlyContinue` or `Ignore` cannot suppress a `throw`.
+The `throw` keyword generates a script-terminating error by default.
+However, `$ErrorActionPreference` _can_ suppress `throw` when set to
+`SilentlyContinue` or `Ignore`. When calling an advanced function with
+`-ErrorAction SilentlyContinue`, the parameter translates to a scope-local
+`$ErrorActionPreference` value, so it also suppresses `throw` inside that
+function.
+
+> [!NOTE]
+> Even with `$ErrorActionPreference = 'Ignore'`, a `throw` that is suppressed
+> still records an entry in `$Error`. The `Ignore` value only prevents
+> `$Error` recording for **non-terminating** errors.
 
 > [!IMPORTANT]
 > The terms _statement-terminating_ and _script-terminating_ describe scope of
@@ -209,18 +218,38 @@ When `-ErrorAction` is specified on a command, it takes precedence over
 ### How escalation works
 
 When `-ErrorAction Stop` or `$ErrorActionPreference = 'Stop'` is in effect,
-PowerShell converts non-terminating errors into script-terminating errors
-using the following mechanism:
+PowerShell converts non-terminating errors into terminating errors using the
+following mechanism:
 
 1. A cmdlet calls `WriteError()` internally to emit a non-terminating error.
 1. The engine checks the effective `ErrorAction` preference for the command.
 1. Because the preference is `Stop`, the engine creates an
    `ActionPreferenceStopException` that wraps the original error record.
-1. This exception has `SuppressPromptInInterpreter` set to `true`, which
-   causes it to propagate up the call stack like a script-terminating error.
 1. If caught by `catch`, the original error information is accessible through
    `$_.Exception.ErrorRecord`.
 
+The scope of the escalated error depends on context:
+
+- In **non-advanced** scripts, functions, or script blocks,
+  `$ErrorActionPreference = 'Stop'` escalates to a **script-terminating**
+  error. The error propagates up the call stack.
+- In **advanced** functions and script blocks (those with `[CmdletBinding()]`),
+  the error remains **statement-terminating**. Execution continues at the
+  next statement after the call.
+- Passing `-ErrorAction Stop` to an advanced function has the same effect as
+  setting `$ErrorActionPreference = 'Stop'` inside it, because `-ErrorAction`
+  translates to a scope-local `$ErrorActionPreference` value.
+
+```powershell
+# NON-advanced: script-terminating ('after' does NOT print)
+& { param() $ErrorActionPreference = 'Stop'; Get-Item 'NoSuchPath' } 2>$null
+'after'
+
+# ADVANCED: statement-terminating ('after' DOES print)
+& { [CmdletBinding()]param() $ErrorActionPreference = 'Stop'; Get-Item 'NoSuchPath' } 2>$null
+'after'
+```
+
 ```powershell
 try {
     # Without -ErrorAction Stop: non-terminating, catch does not fire
@@ -433,14 +462,14 @@ if (-not $config) {
 
 | Property | Non-terminating | Statement-terminating | Script-terminating |
 |----------|----------------|----------------------|-------------------|
-| Generated by | `Write-Error`, `WriteError()` | `ThrowTerminatingError()`, engine errors, .NET method exceptions | `throw`, parse errors, `-ErrorAction Stop` escalation |
+| Generated by | `Write-Error`, `WriteError()` | `ThrowTerminatingError()`, engine errors, .NET method exceptions, `-ErrorAction Stop` in advanced contexts | `throw`, parse errors, `-ErrorAction Stop` in non-advanced contexts |
 | Scope of impact | Pipeline continues | Current statement stops; script continues | Call stack unwinds |
 | Caught by `catch` | No (unless escalated) | Yes | Yes |
 | Caught by `trap` | No (unless escalated) | Yes | Yes |
 | Added to `$Error` | Yes (unless `Ignore`) | Yes | Yes |
 | Sets `$?` to `$false` | Yes | Yes | Yes |
 | Affected by `-ErrorAction` | Yes | No (`Break` only) | No |
-| Affected by `$ErrorActionPreference` | Yes | Yes (can suppress) | `throw`: No; escalated: No |
+| Affected by `$ErrorActionPreference` | Yes | Yes (can suppress) | `throw`: Yes (can suppress); escalated: depends on context |
 
 ## See also