Fix PSScriptAnalyzer settings path default to ./PSScriptAnalyzerSettings.psd1

The default SettingsPath is not $null — PowerShellBuild automatically
looks for PSScriptAnalyzerSettings.psd1 in the project root. Updated
the configuration reference default value and description, the
real-world example to rely on the convention instead of an explicit
override, and the example filename from .psscriptanalyzer.psd1 to
PSScriptAnalyzerSettings.psd1.

https://claude.ai/code/session_01TU1s3wRx7eGZhMJJXvY5Kz

Author: claude

docs/powershellbuild/configuration.md

@@ -83,15 +83,15 @@ properties {
 |---------|---------|-------------|
 | `Test.ScriptAnalysis.Enabled` | `$true` | Run PSScriptAnalyzer |
 | `Test.ScriptAnalysis.FailBuildOnSeverityLevel` | `'Error'` | Build fails on violations at or above this severity (`'Error'`, `'Warning'`, `'Information'`) |
-| `Test.ScriptAnalysis.SettingsPath` | `$null` | Path to a PSScriptAnalyzer settings file |
+| `Test.ScriptAnalysis.SettingsPath` | `./PSScriptAnalyzerSettings.psd1` | Path to a PSScriptAnalyzer settings file. Defaults to `PSScriptAnalyzerSettings.psd1` in the project root — if the file exists it is used automatically |
 
 ```powershell
 properties {
     # Fail on warnings too
     $PSBPreference.Test.ScriptAnalysis.FailBuildOnSeverityLevel = 'Warning'
 
-    # Use a custom ruleset
-    $PSBPreference.Test.ScriptAnalysis.SettingsPath = "$PSScriptRoot/.psscriptanalyzer.psd1"
+    # Override the default settings file location
+    $PSBPreference.Test.ScriptAnalysis.SettingsPath = "$PSScriptRoot/build/analyzersettings.psd1"
 }
 ```
 

docs/powershellbuild/real-world-example.md

@@ -28,6 +28,7 @@ MyModule/
 │       └── build.yml
 ├── psakeFile.ps1
 ├── build.ps1
+├── PSScriptAnalyzerSettings.psd1  # Auto-detected by PowerShellBuild
 └── requirements.psd1
 ```
 
@@ -120,9 +121,9 @@ properties {
     $PSBPreference.Test.ImportModule       = $true
 
     # Test — PSScriptAnalyzer
+    # SettingsPath defaults to ./PSScriptAnalyzerSettings.psd1 in the project root
     $PSBPreference.Test.ScriptAnalysis.Enabled                = $true
     $PSBPreference.Test.ScriptAnalysis.FailBuildOnSeverityLevel = 'Error'
-    $PSBPreference.Test.ScriptAnalysis.SettingsPath           = "$PSScriptRoot/.psscriptanalyzer.psd1"
 
     # Test — Code Coverage
     $PSBPreference.Test.CodeCoverage.Enabled          = $true
@@ -196,11 +197,11 @@ task Deploy -depends BumpVersion, ValidateReadme, Publish {
 }
 ```
 
-## `.psscriptanalyzer.psd1`
+## `PSScriptAnalyzerSettings.psd1`
 
-A custom PSScriptAnalyzer settings file referenced above:
+PowerShellBuild looks for `PSScriptAnalyzerSettings.psd1` in the project root by default. Place your custom rules here and they will be picked up automatically — no need to set `SettingsPath`.
 
-```powershell title=".psscriptanalyzer.psd1"
+```powershell title="PSScriptAnalyzerSettings.psd1"
 @{
     ExcludeRules = @(
         'PSAvoidUsingWriteHost'    # Write-Host is acceptable in build scripts