Address Copilot nitpick feedback

1. Remove misleading 'null-safety' mention from CHANGELOG
   - The improvement was about matching equality semantics, not null-safety
   - Both old and new implementations use HashCode.Combine which handles nulls

2. Fix misleading comment in byte[] edge case test
   - Comment said Width values are different, but they're actually the same
   - Clarified that Width is same (1000) despite different Size values
   - This is exactly what the test is verifying

Author: jas88

CHANGELOG.md

@@ -17,7 +17,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - **Other types** (bool, int, long, DateTime, TimeSpan, Guid, etc.): Compares only `CSharpType`
   - Fixes round-trip equality when comparing guesser-created and SQL reverse-engineered types
   - Compares backing field `_maxWidthForStrings` instead of computed `Width` property to avoid Size interference
-  - `GetHashCode()` updated to match new equality semantics for consistency and null-safety
+  - `GetHashCode()` updated to match new equality semantics for consistency
   - Added 19 comprehensive tests covering all type-specific equality cases and edge cases
 
 ## [2.0.1] - 2025-11-15

Tests/DatabaseTypeRequestEnhancedTests.cs

@@ -631,7 +631,8 @@ public void Equals_ByteArray_WithSameWidthButDifferentSize_AreEqual()
             var request1 = new DatabaseTypeRequest(typeof(byte[]), 1000, new DecimalSize(20, 0));
             var request2 = new DatabaseTypeRequest(typeof(byte[]), 1000, new DecimalSize(0, 0));
 
-            // Verify the Width property values are different due to Size
+            // Verify the Width property values are the same (1000) despite different Size values,
+            // because Width returns Math.Max(_maxWidthForStrings, Size.ToStringLength())
             Assert.That(request1.Width, Is.EqualTo(1000), "Width should be max of explicit and Size");
             Assert.That(request2.Width, Is.EqualTo(1000), "Width should be just the explicit value");