Add Copilot review suggestions

Author: liamjpeters

Engine/Commands/TestScriptAnalyzerSettingsFileCommand.cs

@@ -583,10 +583,12 @@ private static bool IsValueCompatible(object value, Type targetType)
                 return value is string s && int.TryParse(s, out _);
             }
 
-            // String property — almost anything is acceptable since ToString works.
+            // String property — only accept actual strings so that non-string
+            // values for constrained options (with PossibleValues) are caught by
+            // the type check rather than silently skipping enum validation.
             if (targetType == typeof(string))
             {
-                return true;
+                return value is string;
             }
 
             // Array property — accept arrays or a single element of the right kind.

docs/Cmdlets/New-ScriptAnalyzerSettingsFile.md

@@ -26,9 +26,7 @@ configuration defined by the given preset.
 
 When **BaseOnPreset** is not provided, the generated file includes all current rules in the
 `IncludeRules` list and populates the `Rules` section with all configurable properties, set to their
-default values. Both modes also include `CustomRulePath`, `RecurseCustomRulePath`, and
-`IncludeDefaultRules` keys with descriptive comments so the file is immediately ready for
-customization.
+default values.
 
 If a settings file already exists at the target path, the cmdlet emits a terminating error unless
 the **Force** parameter is specified - in which case it's overwritten.
@@ -41,7 +39,7 @@ the **Force** parameter is specified - in which case it's overwritten.
 New-ScriptAnalyzerSettingsFile
 ```
 
-Creates `PSScriptAnalyzerSettings.psd1` in the current working directory incluindg all rules and
+Creates `PSScriptAnalyzerSettings.psd1` in the current working directory including all rules and
 all configurable options set to their defaults.
 
 ### EXAMPLE 2 - Create a settings file based on a preset