Update README with troubleshooting info and clean up window visibility fix script

- Add troubleshooting section to README with macOS blank screen fix
- Remove perl strategy from apply-window-visibility-fix.sh (has escaping issues)
- Keep Python and sed strategies which are more reliable

Author: Tajudeen

README.md

@@ -14,5 +14,12 @@ The  `.patch` files from VSCodium get rid of telemetry in CortexIDE (the core pu
 
 - If you want to build and compile CortexIDE yourself, you just need to fork this repo and run the GitHub Workflows. If you want to handle auto updates too, just search for caps-sensitive "CortexIDE" and "cortexide" and replace them with your own repo.
 
+## Troubleshooting
+
+If you encounter issues after building and installing CortexIDE:
+
+- **macOS blank screen**: Run `./fix_macos_blank_screen.sh` to diagnose and fix GPU cache issues
+- See [docs/troubleshooting.md](docs/troubleshooting.md) for detailed troubleshooting steps
+
 ## Rebasing
 - We often need to rebase `cortexide` and `cortexide-builder` onto `vscode` and `vscodium` to keep our build pipeline working when deprecations happen, but this is pretty easy. All the changes we made in `cortexide/` are commented with the caps-sensitive word "CortexIDE" (except our images, which need to be done manually), so rebasing just involves copying the `vscode/` repo and searching "CortexIDE" to re-make all our changes. The same exact thing holds for copying the `vscodium/` repo onto this repo and searching "CortexIDE" and "cortexide" to keep our changes. Just make sure the vscode and vscodium versions align.

patches/osx/apply-window-visibility-fix.sh

@@ -177,37 +177,9 @@ PYTHON_SCRIPT
   fi
 fi
 
-# Strategy 2: Use perl with flexible pattern matching
-if [[ "${INSERTION_PATTERN}" == "this\._win\.loadURL" ]]; then
-  # New structure: Insert after loadURL
-  if perl -i.bak -0pe "
-    if (/(this\._win\.loadURL\([^)]+\);\s*)(\n\s*\/\/ Remember that we did load)/s) {
-      \$_ = \$` . \$1 . \"\n${FIX_CODE}\" . \$2 . \$';
-    } elsif (/(this\._win\.loadURL\([^)]+\);)(\s*\n)/s) {
-      \$_ = \$` . \$1 . \"\n${FIX_CODE}\" . \$2 . \$';
-    }
-  " "${WINDOW_TS_FILE}" 2>/dev/null; then
-    if grep -q "Fix for macOS blank screen" "${WINDOW_TS_FILE}"; then
-      echo "✓ Window visibility fix applied successfully (perl strategy - new structure)"
-      rm -f "${WINDOW_TS_FILE}.bak"
-      exit 0
-    fi
-  fi
-else
-  # Old structure: Insert before return this.win
-  if perl -i.bak -0pe "
-    if (/(this\.win\.webContents\.send\(['\"]vscode:windowConfiguration['\"],\s*configuration\);\s*\}\s*)(\n\s*return\s+this\.win;)/s) {
-      \$_ = \$` . \$1 . \"\n${FIX_CODE}\" . \$2 . \$';
-    }
-  " "${WINDOW_TS_FILE}" 2>/dev/null; then
-    if grep -q "Fix for macOS blank screen" "${WINDOW_TS_FILE}"; then
-      echo "✓ Window visibility fix applied successfully (perl strategy - old structure)"
-      rm -f "${WINDOW_TS_FILE}.bak"
-      exit 0
-    fi
-  fi
-fi
-
+# Strategy 2: Use perl with flexible pattern matching (skip - use Python or sed instead)
+# Perl has escaping issues with backticks in bash, so we skip this strategy
+# Python (Strategy 1) and sed (Strategy 3) are more reliable
 # Strategy 3: Use sed as final fallback
 if [[ "${INSERTION_PATTERN}" == "this\._win\.loadURL" ]]; then
   # New structure: Insert after loadURL line