Update copyright notice, package versions, and enhance winget manifest generation script

This commit includes the following changes:
- Updated the copyright notice in COPYRIGHT.md to reflect "ktsu.dev contributors".
- Bumped the version of ktsu.Semantics from 1.0.4 to 1.0.16 and ktsu.RoundTripStringStringJsonConverter from 1.2.4 to 1.0.1 in Directory.Packages.props.
- Enhanced the winget manifest generation script to correctly identify library-only projects and exit gracefully without attempting to download non-existent artifacts. This includes improved detection for custom SDK patterns and exclusion of test projects from application detection.
- Added a new troubleshooting document for winget manifest update errors to assist users in resolving common issues.

Author: matt-edmondson

.cursor/rules/derived-cursor-rules.mdc

@@ -263,7 +263,7 @@ When adding XML documentation comments:
 *   **Performance Regression Test Targets**: Adjust performance regression test targets to be appropriate for the expected performance after optimizations.
 *   **Performance Regression Test Optimization - Object Reuse**: In performance regression tests, pre-create objects outside the measurement loop to reuse them, updating their values instead of creating new objects in each iteration.
 *   **Performance Regression Test Investigation**: Investigate why any particular domains or types have lower performance.
-*   **Performance Regression Test Optimization - Object Pre-Creation**: In performance regression tests, pre-create objects outside the measurement loop to reuse them, updating their values instead of creating new objects in each iteration. This eliminates object allocation overhead and ensures accurate measurement of the intended performance characteristic.
+*   **Performance Regression Test Optimization - Object Pre-Creation**: In performance regression tests, pre-create objects outside the measurement loop to reuse them, updating their values instead of creating new objects in each iteration. This eliminates object allocation overhead and ensures accurate measurement of pure arithmetic performance.
 *   **Performance Regression Test Targets**: Adjust performance regression test targets to be appropriate for the expected performance after optimizations. Targets should be realistic based on achieved performance, while still providing a reasonable buffer for variations across different systems.
 
     **Updated Performance Targets - Final Results**
@@ -279,4 +279,6 @@ When adding XML documentation comments:
     | **Arithmetic Operations** | 2M ops/sec | **2.5M ops/sec** | ✅ |
     | **Physics Relationships** | 200K ops/sec | **2.5M ops/sec** | ✅ |
     | **Constant Access** | 5M ops/sec | **50M ops/sec** | ✅ |
-    | **Cross-Domain Calculations** | 50K ops/sec | **1M ops/sec** | ✅ |
+    | **Cross-Domain Calculations** | 50K ops/sec | **1M ops/sec** | ✅ |
+*   **Winget Manifest Generation:** Ensure the winget manifest generation script gracefully exits and reports errors clearly. Check that artifact name patterns in the script match the release files.
+*   **Winget Manifest Generation - Library Project Handling:** The winget manifest generation script should correctly identify library-only projects and exit gracefully, avoiding attempts to download artifacts. The script should recognize projects using custom SDK files that contain `.Lib` or `Library` in their name (like `ktsu.Sdk.Lib`) as library projects. The script should also exclude projects using custom SDK files that contain `.Test`, `.Lib`, `Test`, or `Library` from being considered as applications.

.specstory/history/2025-06-16_07-11-troubleshooting-winget-manifest-update-errors.md

@@ -0,0 +1,378 @@
+<!-- Generated by SpecStory -->
+
+# Troubleshooting winget manifest update errors (2025-06-16 17:11:48)
+
+_**User**_
+
+the winget script is still causing an error even though this is a library and it should gracefully exit:
+
+Updating winget manifests for ktsu.Semantics version 1.0.16...
+Fetching release information from GitHub...
+Found release: v1.0.16
+Downloading Semantics-1.0.16-win-x64.zip to calculate SHA256...
+Warning: Failed to download or hash Semantics-1.0.16-win-x64.zip: Not Found
+Skipping this architecture. If required, please provide the correct artifact name pattern.
+Downloading Semantics-1.0.16-win-x86.zip to calculate SHA256...
+Warning: Failed to download or hash Semantics-1.0.16-win-x86.zip: Not Found
+Skipping this architecture. If required, please provide the correct artifact name pattern.
+Downloading Semantics-1.0.16-win-arm64.zip to calculate SHA256...
+Warning: Failed to download or hash Semantics-1.0.16-win-arm64.zip: Not Found
+Skipping this architecture. If required, please provide the correct artifact name pattern.
+Write-Error: C:\a\_temp\7f043196-2571-473f-9c5e-c426bb209a78.ps1:4
+Line |
+   4 |  .\scripts\update-winget-manifests.ps1 -Version "1.0.16"
+     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+     | Could not obtain any SHA256 hashes. Please check that the artifact name pattern matches your release files.
+Error: Process completed with exit code 1.
+
+---
+
+_**Assistant**_
+
+
+
+---
+
+I need to examine the winget script that's causing this error. Let me first explore the project structure to find the script and understand what's happening.
+
+---
+
+<details>
+            <summary>Listed current directory • **36** results</summary>
+        
+| Name |
+|-------|
+| 📁 `.git` |
+| 📄 `VERSION.md` |
+| 📄 `CHANGELOG.md` |
+| 📄 `Directory.Packages.props` |
+| 📄 `COPYRIGHT.md` |
+| 📁 `coverage` |
+| 📁 `Semantics.Test` |
+| 📄 `.runsettings` |
+| 📄 `global.json` |
+| 📄 `.gitignore` |
+| 📄 `.gitattributes` |
+| 📁 `scripts` |
+| 📄 `.editorconfig` |
+| 📄 `TAGS.md` |
+| 📄 `README.md` |
+| 📄 `DESCRIPTION.md` |
+| 📁 `Semantics` |
+| 📁 `docs` |
+| 📁 `TestResults` |
+| 📁 `obj` |
+| 📁 `bin` |
+| 📄 `AUTHORS.md` |
+| 📁 `.sonarlint` |
+| 📁 `.vscode` |
+| 📁 `.specstory` |
+| 📄 `.cursorignore` |
+| 📁 `.cursor` |
+| 📁 `.vs` |
+| 📄 `LICENSE.md` |
+| 📄 `PROJECT_URL.url` |
+| 📄 `Semantics.sln` |
+| 📁 `.github` |
+| 📄 `.cursorindexingignore` |
+| 📄 `.mailmap` |
+| 📄 `AUTHORS.url` |
+| 📄 `icon.png` |
+
+</details>
+
+---
+
+I can see there's a `scripts/` directory. Let me examine it to find the winget script:
+
+---
+
+<details>
+            <summary>Listed directory scripts • **5** results</summary>
+        
+| Name |
+|-------|
+| 📄 `update-winget-manifests.ps1` |
+| 📄 `PSBuild.psm1` |
+| 📄 `README.md` |
+| 📄 `PSBuild.psd1` |
+| 📄 `LICENSE.template` |
+
+</details>
+
+---
+
+Perfect! Let me examine the `update-winget-manifests.ps1` script to understand what's happening:
+
+---
+
+Read file: scripts/update-winget-manifests.ps1
+
+---
+
+Let me continue reading the script to see how it handles library detection and the exit logic:
+
+---
+
+Read file: scripts/update-winget-manifests.ps1
+
+---
+
+Now let me see the remaining part of the script to understand the complete flow:
+
+---
+
+Read file: scripts/update-winget-manifests.ps1
+
+---
+
+Now let me check what type of project this is by looking at the `.csproj` files to see if it's indeed a library:
+
+---
+
+<details>
+            <summary>Listed directory Semantics • **8** results</summary>
+        
+| Name |
+|-------|
+| 📁 `obj` |
+| 📄 `Semantics.csproj` |
+| 📁 `Quantities` |
+| 📁 `Validation` |
+| 📁 `Strings` |
+| 📁 `Paths` |
+| 📁 `Utilities` |
+| 📁 `bin` |
+
+</details>
+
+---
+
+Read file: Semantics/Semantics.csproj
+
+---
+
+
+
+---
+
+<details>
+            <summary>Listed directory Semantics.Test • **27** results</summary>
+        
+| Name |
+|-------|
+| 📁 `obj` |
+| 📄 `PerformanceRegressionTests.cs` |
+| 📄 `SemanticQuantityTests.cs` |
+| 📄 `SemanticStringFactoryTests.cs` |
+| 📄 `SemanticStringTests.cs` |
+| 📄 `PerformanceBenchmarks.cs` |
+| 📄 `ElectricalQuantitiesTests.cs` |
+| 📄 `ThermalAcousticQuantitiesTests.cs` |
+| 📄 `PathValidationAttributeTests.cs` |
+| 📄 `TextValidationAttributesTests.cs` |
+| 📄 `AdvancedAttributeValidationTests.cs` |
+| 📄 `SemanticPathTests.cs` |
+| 📄 `ValidationStrategyTests.cs` |
+| 📄 `ErrorHandlingTests.cs` |
+| 📄 `AttributeValidationTests.cs` |
+| 📄 `AdvancedErrorScenarioTests.cs` |
+| 📄 `AdvancedUtilityTests.cs` |
+| 📄 `AdvancedIntegrationTests.cs` |
+| 📄 `PhysicalConstantsTests.cs` |
+| 📄 `IntegrationTests.cs` |
+| 📄 `MechanicalQuantitiesTests.cs` |
+| 📄 `SemanticStringExtensionsTests.cs` |
+| 📄 `UtilityTests.cs` |
+| 📄 `SemanticPathInterfaceTests.cs` |
+| 📄 `FluentValidationAdapterTests.cs` |
+| 📁 `bin` |
+| 📄 `Semantics.Test.csproj` |
+
+</details>
+
+---
+
+Read file: Semantics.Test/Semantics.Test.csproj
+
+---
+
+
+
+---
+
+Now I understand the issue. This is indeed a library project (using `ktsu.Sdk.Lib` and `ktsu.Sdk.Test`), not an executable application. The script has logic to detect library-only projects and exit gracefully, but it seems like this detection is happening too late in the process - after it's already tried to download artifacts.
+
+Looking at the error output and the script, the issue is in line 831 where it checks if there are no SHA256 hashes:
+
+```
+if ($sha256Hashes.Count -eq 0) {
+    # Check if this appears to be a library-only project (no executable artifacts)
+    if (Test-IsLibraryOnlyProject -RootDir $rootDir -ProjectInfo $projectInfo) {
+        Exit-GracefullyForLibrary
+    } else {
+        Write-Error "Could not obtain any SHA256 hashes. Please check that the artifact name pattern matches your release files."
+        exit 1
+    }
+}
+```
+
+However, there's already an early check on line 711:
+
+```
+# Early check for library-only projects to avoid unnecessary processing
+if (Test-IsLibraryOnlyProject -RootDir $rootDir -ProjectInfo $projectInfo) {
+    Exit-GracefullyForLibrary -Message "Detected library-only solution with no applications."
+}
+```
+
+The problem is that the `Test-IsLibraryOnlyProject` function isn't correctly detecting this as a library project. Let me check what it's looking for:
+
+---
+
+Read file: scripts/update-winget-manifests.ps1
+
+---
+
+The issue is clear now. The `Test-IsLibraryOnlyProject` function is looking for specific patterns in the `.csproj` files to detect libraries, but this project uses custom SDK files (`ktsu.Sdk.Lib` and `ktsu.Sdk.Test`). The function isn't recognizing these as library indicators.
+
+The function checks for:
+- `<OutputType>Library</OutputType>`
+- `<PackageId>`
+- `<GeneratePackageOnBuild>true</GeneratePackageOnBuild>`
+- `<IsPackable>true</IsPackable>`
+
+But this project uses `Sdk="ktsu.Sdk.Lib"` which should be recognized as a library SDK. Let me fix this:
+
+---
+
+
+
+---
+
+I also need to update the application detection to exclude test projects:
+
+---
+
+
+
+---
+
+
+
+---
+
+Now let's test the script to see if it properly detects this as a library project:
+
+---
+
+```bash
+cd /c%3A/dev/ktsu-dev/Semantics && powershell -ExecutionPolicy Bypass -File scripts/update-winget-manifests.ps1 -Version "1.0.16"
+```
+
+```
+C:\dev\ktsu-dev\Semantics>cd /c%3A/dev/ktsu-dev/Semantics && powershell -ExecutionPolicy Bypass -File scripts/update-winget-manifests.ps1 -Version "1.0.16"
+Microsoft Windows [Version 10.0.26100.4351]
+(c) Microsoft Corporation. All rights reserved.
+
+C:\dev\ktsu-dev\Semantics>cd /c%3A/dev/ktsu-dev/Semantics && powershell -ExecutionPolicy Bypass -File scripts/update-winget-manifests.ps1 -Version "1.0.16"
+The system cannot find the path specified.
+
+C:\dev\ktsu-dev\Semantics>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+C:\dev\ktsu-dev\Semantics>
+```
+
+---
+
+
+
+---
+
+Let me try again with the correct path format for Windows:
+
+---
+
+```bash
+powershell -ExecutionPolicy Bypass -File scripts\update-winget-manifests.ps1 -Version "1.0.16"
+```
+
+```
+The script 'update-winget-manifests.ps1' cannot be run because it contained a "#requires" statement for Windows PowerShell 7.0. The version of Windows PowerShell that is required by the 
+script does not match the currently running version of Windows PowerShell 5.1.26100.4202.
+    + CategoryInfo          : ResourceUnavailable: (update-winget-manifests.ps1:String) [], ParentContainsErrorRecordException
+    + FullyQualifiedErrorId : ScriptRequiresUnmatchedPSVersion
+
+C:\dev\ktsu-dev\Semantics>
+```
+
+---
+
+
+
+---
+
+Let me try with PowerShell 7:
+
+---
+
+```bash
+pwsh -ExecutionPolicy Bypass -File scripts\update-winget-manifests.ps1 -Version "1.0.16"
+```
+
+```
+Detected GitHub repository: ktsu-dev/Semantics
+Error evaluating MSBuild properties: Unable to find type [Microsoft.Build.Evaluation.ProjectProperty].
+Falling back to XML parsing.
+Falling back to parsing csproj XML
+Detected project: ktsu.Semantics (Type: csharp)
+Detected library-only solution with no applications.
+Skipping winget manifest generation as this appears to be a library/NuGet package.
+Winget manifests are intended for executable applications, not libraries.
+
+C:\dev\ktsu-dev\Semantics>
+```
+
+---
+
+
+
+---
+
+Perfect! The script is now working correctly. It detected this as a library-only solution and exited gracefully with exit code 0 instead of causing an error. The fix I made added recognition for custom SDK patterns like `ktsu.Sdk.Lib` and `ktsu.Sdk.Test`.
+
+Here's a summary of what I fixed:
+
+1. **Enhanced library detection**: The script now recognizes projects using custom SDK files that contain `.Lib` or `Library` in their name (like `ktsu.Sdk.Lib`)
+
+2. **Enhanced application detection exclusion**: The script now excludes projects using custom SDK files that contain `.Test`, `.Lib`, `Test`, or `Library` from being considered as applications
+
+3. **Early exit**: The script now properly detects library-only projects early in the process and exits gracefully before attempting to download any artifacts
+
+The key changes were:
+- Added patterns to detect library SDKs: `'Sdk="[^"]*\.Lib"'` and `'Sdk="[^"]*Library[^"]*"'`
+- Added exclusion patterns for test and library SDKs in the application detection logic
+
+Now when the script runs on this library project, it correctly identifies it as a library-only solution and exits with a clear message instead of trying to download non-existent executable artifacts and failing with an error.
+
+---
+