fix: e2e tests

.github/workflows/pr_checks.yaml

@@ -670,13 +670,6 @@ jobs:
           cd extensions/vscode
           rm -rf e2e/.test-extensions/continue*
 
-      - name: Upload e2e test screenshots
-        if: failure()
-        uses: actions/upload-artifact@v4
-        with:
-          name: e2e-failure-screenshots
-          path: extensions/vscode/e2e/storage/screenshots
-
       - name: Sanitize test file name
         id: sanitize_filename
         if: always()
@@ -685,6 +678,13 @@ jobs:
           SANITIZED_FILENAME="${FILENAME//\//-}" # Replace / with - using bash parameter expansion
           echo "sanitized_test_file=${SANITIZED_FILENAME}" >> $GITHUB_OUTPUT
 
+      - name: Upload e2e test screenshots
+        if: failure()
+        uses: actions/upload-artifact@v4
+        with:
+          name: e2e-failure-screenshots-${{ steps.sanitize_filename.outputs.sanitized_test_file || 'unknown' }}-${{ matrix.command == 'e2e:ci:run-yaml' && 'yaml' || 'json' }}
+          path: extensions/vscode/e2e/storage/screenshots
+
       - name: Find e2e log file
         if: always()
         run: |

extensions/vscode/e2e/README.md

@@ -1,20 +1,22 @@
-### Setup
+# E2E Tests
+
+## Setup
 
 When running e2e tests for the first time
 
 ```bash
 npm run e2e:all
 ```
 
-### Run
+## Run
 
 Depending on what code you update, you can use a faster loop to test your changes:
 
 - If you update the e2e test code and/or config.yaml/json, you can run `npm run e2e:quick`
 - If you update the extension code, you can run `npm run e2e:recompile`
 - If you update the gui code, you can run `npm run e2e:rebuild-gui`
 
-### Writing tests
+## Writing tests
 
 All e2e tests are separated (by folder) into