chore: update docs

Author: V3RON

.nx/version-plans/plan-startup-crash-and-physical-device.md

@@ -0,0 +1,5 @@
+---
+__default__: minor
+---
+
+Startup crash detection now monitors apps during launch and reports crashes before the first test even begins, with detailed diagnostics for both iOS and Android. Physical iOS device support is included via `libimobiledevice`. Crash report selection on iOS simulators has been improved with a more reliable algorithm that tolerates timing variations.

website/src/docs/guides/ci-cd.md

@@ -29,7 +29,7 @@ Both actions automatically:
 - Set up and configure the emulator/simulator based on your config
 - Install your app
 - Run the tests
-- Upload persisted crash artifacts from `.harness/crash-reports` when the run produces them
+- Upload crash reports from `.harness/crash-reports/` as workflow artifacts whenever a run produces them
 
 The actions read your `rn-harness.config.mjs` file to determine the device configuration, so you don't need to hardcode emulator settings in your workflow.
 
@@ -43,9 +43,15 @@ Both actions accept the following inputs:
 
 ## Crash Artifacts
 
-When Harness resolves a crash artifact, it persists a copy under `.harness/crash-reports/` in the current working directory. Filenames include the Harness run timestamp and selected runner name so CI downloads stay easy to correlate.
+Harness monitors native crashes throughout the entire test lifecycle — including during **app startup**, before any test code runs. When the app crashes on launch (or at any point during the run), Harness captures the crash report and attaches a parsed stack trace to the failing test or startup error output.
 
-The official GitHub Actions upload `.harness/crash-reports/**/*` automatically with `if-no-files-found: ignore`, so crash reports are available as workflow artifacts whenever a run produces them.
+Crash reports are persisted under `.harness/crash-reports/` in the current working directory. Filenames include the Harness run timestamp and selected runner name so CI downloads are easy to correlate with a specific workflow run.
+
+The official GitHub Actions upload `.harness/crash-reports/**/*` automatically (with `if-no-files-found: ignore`), so crash reports appear as downloadable workflow artifacts whenever a run produces them — no extra configuration needed.
+
+:::tip
+Startup crashes are treated as a first-class failure. If your app crashes before the bridge connects, Harness immediately reports it with the native crash details rather than timing out.
+:::
 
 ## GitHub Actions Example
 

website/src/docs/platforms/android.mdx

@@ -91,3 +91,9 @@ Supported extra value types in v1:
 - `string`
 - `boolean`
 - safe integers
+
+## Native Crash Details
+
+Harness monitors logcat output during both app startup and test execution, looking for fatal exceptions and ANRs in the process matching your `bundleId`. When a native crash is detected, Harness attaches the parsed crash information — including the exception type, message, and full stack trace — to the failing test or startup error.
+
+Crash reports are also persisted under `.harness/crash-reports/` so they remain available for inspection after the test run, and the [official GitHub Actions](../guides/ci-cd) upload them automatically as workflow artifacts.