🐛 Fix: Use absolute path for E2E_SUMMARY_OUTPUT

The e2e tests change directories during execution, causing the relative
path to e2e-summary.json to fail. Convert OUTPUT_DIR to an absolute path
before passing it to E2E_SUMMARY_OUTPUT.

This fixes the error:
  'failed to write e2e test summary output: no such file or directory'

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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

Author: tmshort

hack/tools/memory-profiling/run-profiled-test.sh

@@ -20,6 +20,10 @@ TEST_TARGET="${2:-${MEMORY_PROFILE_TEST_TARGET:-test-experimental-e2e}}"
 OUTPUT_DIR="${MEMORY_PROFILE_DIR:-./memory-profiles}/${TEST_NAME}"
 SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 
+# Get absolute path for OUTPUT_DIR
+# This is needed because E2E tests may change directories
+OUTPUT_DIR_ABS="$(cd "$(dirname "${OUTPUT_DIR}")" 2>/dev/null && pwd)/$(basename "${OUTPUT_DIR}")" || OUTPUT_DIR_ABS="${OUTPUT_DIR}"
+
 # Colors for output
 RED='\033[0;31m'
 GREEN='\033[0;32m'
@@ -46,6 +50,9 @@ log_warn() {
 # Create output directory
 mkdir -p "${OUTPUT_DIR}"
 
+# Update OUTPUT_DIR_ABS now that directory exists
+OUTPUT_DIR_ABS="$(cd "${OUTPUT_DIR}" && pwd)"
+
 # PIDs to track
 TEST_PID=""
 COLLECT_PID=""
@@ -83,7 +90,8 @@ log_info "Output directory: ${OUTPUT_DIR}"
 # Start the e2e test
 log_info "Starting e2e test (${TEST_TARGET})..."
 # Set E2E_SUMMARY_OUTPUT to capture prometheus alerts and other test metrics
-E2E_SUMMARY_OUTPUT="${OUTPUT_DIR}/e2e-summary.json" make "${TEST_TARGET}" > "${OUTPUT_DIR}/test.log" 2>&1 &
+# Use absolute path because e2e tests may change directories
+E2E_SUMMARY_OUTPUT="${OUTPUT_DIR_ABS}/e2e-summary.json" make "${TEST_TARGET}" > "${OUTPUT_DIR}/test.log" 2>&1 &
 TEST_PID=$!
 log_info "Test started (PID: ${TEST_PID})"