chore: fix trailing whitespace in release workflow and CLAUDE.md

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

Author: claude

.github/workflows/release.yml

@@ -418,14 +418,14 @@ jobs:
           # Code sign macOS binaries
           if [ "${{ matrix.goos }}" = "darwin" ]; then
             echo "Code signing macOS binary..."
-            
+
             # Debug: List all available certificates
             echo "Available certificates:"
             security find-identity -v -p codesigning
-            
+
             # Find the Developer ID certificate identity
             CERT_IDENTITY=$(security find-identity -v -p codesigning | grep "Developer ID Application" | head -1 | grep -o '"[^"]*"' | tr -d '"')
-            
+
             # Verify we found a valid certificate
             if [ -n "${CERT_IDENTITY}" ]; then
               echo "✅ Found Developer ID certificate: ${CERT_IDENTITY}"
@@ -434,7 +434,7 @@ jobs:
               CERT_IDENTITY="${{ secrets.APPLE_TEAM_ID }}"
               echo "⚠️  Using fallback identity: ${CERT_IDENTITY}"
             fi
-            
+
             # Validate entitlements file formatting (Apple's recommendation)
             echo "=== Validating entitlements file ==="
             if [ -f "scripts/entitlements.plist" ]; then
@@ -445,14 +445,14 @@ jobs:
                 echo "❌ Entitlements file has formatting issues"
                 exit 1
               fi
-              
+
               # Convert to XML format if needed (Apple's recommendation)
               plutil -convert xml1 scripts/entitlements.plist
               echo "✅ Entitlements converted to XML format"
             else
               echo "⚠️  No entitlements file found"
             fi
-            
+
             # Sign both binaries with proper Developer ID certificate, hardened runtime, and timestamp
             echo "=== Signing binaries with hardened runtime ==="
 
@@ -527,7 +527,7 @@ jobs:
               echo "❌ All tray binary signing attempts failed"
               exit 1
             fi
-            
+
             # Verify signing, hardened runtime, and timestamp using Apple's recommended methods
             echo "=== Verifying binary signatures (Apple's recommended verification) ==="
 
@@ -558,7 +558,7 @@ jobs:
               echo "❌ Strict verification FAILED - will not pass notarization"
               exit 1
             fi
-            
+
             # Check for secure timestamp (Apple's recommended check)
             echo "=== Checking for secure timestamp ==="
             TIMESTAMP_CHECK=$(codesign -dvv ${CLEAN_BINARY} 2>&1)
@@ -570,14 +570,14 @@ jobs:
               echo "Full output:"
               echo "$TIMESTAMP_CHECK"
             fi
-            
+
             # Display detailed signature info
             codesign --display --verbose=4 ${CLEAN_BINARY}
-            
+
             # Check entitlements formatting (Apple's recommendation)
             echo "=== Checking entitlements formatting ==="
             codesign --display --entitlements - ${CLEAN_BINARY} | head -10
-            
+
             # Verify with spctl (Gatekeeper assessment) - expected to fail before notarization
             echo "=== Gatekeeper assessment (expected to fail before notarization) ==="
             if spctl --assess --verbose ${CLEAN_BINARY}; then
@@ -586,7 +586,7 @@ jobs:
               echo "⚠️  Gatekeeper assessment: REJECTED (expected - binary needs notarization)"
               echo "This is normal - the binary will pass after Apple completes notarization"
             fi
-            
+
             echo "✅ Binary signed successfully with hardened runtime and timestamp"
           fi
 
@@ -859,7 +859,7 @@ jobs:
           if [ -f .keychain_name ]; then
             TEMP_KEYCHAIN=$(cat .keychain_name)
             echo "Cleaning up keychain: ${TEMP_KEYCHAIN}"
-            
+
             # Remove from search list and delete
             security delete-keychain "$TEMP_KEYCHAIN" 2>/dev/null || echo "Keychain already cleaned up"
             rm -f .keychain_name

CLAUDE.md

@@ -8,7 +8,7 @@ When operating to complete a task, adhere strictly to the following constraints
 
 ### Must-Do (Defaults & Assumptions)
 - **Zero Interruption Policy**: If a decision is needed and no explicit instruction exists, you MUST make an informed, safe assumption based on idiomatic Go best practices and document it in the PR/commit. Do NOT ask for human clarification mid-task.
-- **Test-Driven Progress**: You must write a failing Go test (`_test.go`) for every sub-task before implementing the feature. 
+- **Test-Driven Progress**: You must write a failing Go test (`_test.go`) for every sub-task before implementing the feature.
 - **Graceful Fallbacks**: If an API or dependency lacks documentation, use mock interfaces or a simplified implementation rather than blocking the task.
 - **Continuous Logging**: Document every step completed in an `execution_log.md` within the current working directory to maintain state.