refactor: simplify cgo release-marker check logic

Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>

Author: Copilot

.github/workflows/cgo.yml

@@ -527,12 +527,13 @@ jobs:
           # Release-compiled lock files can be identified by either:
           # 1. Header marker with version suffix (legacy): "...generated by gh-aw (vX.Y.Z)."
           # 2. Metadata marker: compiler_version field in gh-aw-metadata.
-          if grep -E '# This file was automatically generated by gh-aw \([v0-9]' "$file" > /dev/null 2>&1 || \
-             grep -E '^# gh-aw-metadata: .*"compiler_version":' "$file" > /dev/null 2>&1; then
+          HEADER_MARKER=$(grep -E '^# This file was automatically generated by gh-aw \([v0-9]' "$file" || true)
+          METADATA_MARKER=$(grep -E '^# gh-aw-metadata: .*"compiler_version":' "$file" || true)
+          if [ -n "$HEADER_MARKER$METADATA_MARKER" ]; then
             echo "❌ ERROR: Found release-compiled lock file: $file"
             echo ""
             echo "Release-build marker(s):"
-            grep -E '# This file was automatically generated by gh-aw \([v0-9]|^# gh-aw-metadata: .*"compiler_version":' "$file" || true
+            printf '%s\n%s\n' "$HEADER_MARKER" "$METADATA_MARKER" | sed '/^$/d'
             echo ""
             FOUND_RELEASE=1
           fi