add profiling info to overview_dev.mdc

Author: lbloder

.cursor/rules/overview_dev.mdc

@@ -53,6 +53,16 @@ Use the `fetch_rules` tool to include these rules when working on specific areas
   - `SentryMetricsEvent`, `SentryMetricsEvents`
   - `SentryOptions.getMetrics()`, `beforeSend` callback
 
+- **`profiling`**: Use when working with:
+  - Continuous profiling (`sentry-async-profiler` module)
+  - `IContinuousProfiler`, `JavaContinuousProfiler`, `AndroidContinuousProfiler`
+  - `ProfileChunk`, chunk rotation and sending
+  - `ProfileLifecycle` (MANUAL vs TRACE modes)
+  - `profilesSampleRate`, `profilingTracesHz`, `profileLifecycle` options
+  - Integration with rate limiting, offline caching, scopes
+  - JFR file handling, async-profiler integration
+  - Platform differences (JVM vs Android profiling)
+
 ### Integration & Infrastructure
 - **`opentelemetry`**: Use when working with:
   - OpenTelemetry modules (`sentry-opentelemetry-*`)
@@ -77,10 +87,11 @@ Use the `fetch_rules` tool to include these rules when working on specific areas
 3. **Multiple rules**: Fetch multiple rules if task spans domains (e.g., `["scopes", "opentelemetry"]` for tracing scope issues)
 4. **Context clues**: Look for these keywords in requests to determine relevant rules:
    - Scope/Hub/forking → `scopes`
-   - Duplicate/dedup → `deduplication` 
+   - Duplicate/dedup → `deduplication`
    - OpenTelemetry/tracing/spans → `opentelemetry`
    - new module/integration/sample → `new_module`
    - Cache/offline/network → `offline`
    - System test/e2e/sample → `e2e_tests`
    - Feature flag/addFeatureFlag/flag evaluation → `feature_flags`
    - Metrics/count/distribution/gauge → `metrics`
+   - Profiling/profiler/ProfileChunk/JFR → `profiling`