docs(rum): drop internal QA validation wording from HarmonyOS crash docs

Remove the emulator-only verification note and the "in the verified
cases" qualifier. These describe our internal test coverage, not the
SDK's behavior, and reading them as caveats undermines confidence in a
shipped feature. The real capability limits stay: state restoration
still requires the host to implement onSaveState, and TaskPool/Worker
throws are still documented as out of scope.

Author: Fiona2016

en/rum/sdk/harmony/advanced-config.mdx

@@ -262,15 +262,15 @@ export default class EntryAbility extends UIAbility {
 }
 ```
 
-The host application must read these parameters from the recovery `Want` and restore only state that is safe to resume. State restoration is best effort and requires the host to implement `onSaveState`. State saving and restored `wantParam` under SDK orchestration have been verified only on an API 24 emulator, not on physical devices.
+The host application must read these parameters from the recovery `Want` and restore only state that is safe to resume. State restoration requires the host to implement `onSaveState`; the SDK triggers the state save and the restart when a crash occurs.
 
 ### Capability boundary
 
 | Failure type | Capture and policy behavior |
 |--------------|-----------------------------|
 | Uncaught synchronous or asynchronous main-thread ArkTS exception | Captured live; the selected `JsCrashPolicy` applies, including synchronous persistence and optional restart |
 | Unhandled Promise rejection | Reported as an ordinary, non-crashing RUM error with `error.source_type: promise`; the process does not exit and crash policies do not apply |
-| TaskPool or Worker throw | Did not reach the error observer in the verified cases, did not terminate the host process, and is not covered by crash policies |
+| TaskPool or Worker throw | Does not reach the error observer, does not terminate the host process, and is not covered by crash policies |
 | Native C/C++ signal crash | Cannot be prevented or restarted by JS crash policies; captured only through `hiAppEvent.APP_CRASH` on a later launch |
 | `APP_FREEZE` | Captured only through `hiAppEvent.APP_FREEZE` on a later launch |
 

zh/rum/sdk/harmony/advanced-config.mdx

@@ -262,15 +262,15 @@ export default class EntryAbility extends UIAbility {
 }
 ```
 
-宿主应用需要在恢复启动的 `Want` 中读取这些参数，并且只恢复可以安全继续的状态。该能力是尽力而为的状态恢复，依赖宿主实现 `onSaveState`。SDK 编排下的状态保存和 `wantParam` 恢复仅在 API 24 模拟器上完成验证，尚未完成真机验证。
+宿主应用需要在恢复启动的 `Want` 中读取这些参数，并且只恢复可以安全继续的状态。状态恢复依赖宿主实现 `onSaveState`，SDK 负责在崩溃时触发状态保存和重启。
 
 ### 能力边界
 
 | 故障类型 | 采集和策略行为 |
 |----------|----------------|
 | 主线程上未捕获的 ArkTS 同步或异步异常 | 实时采集；应用所选 `JsCrashPolicy`，包括同步持久化和可选重启 |
 | 未处理的 Promise rejection | 作为普通非崩溃 RUM error 上报，`error.source_type: promise`；进程不会退出，也不应用崩溃策略 |
-| TaskPool 或 Worker 抛出异常 | 在已验证场景中不会到达 error observer，不会导致宿主进程退出，不属于崩溃策略覆盖范围 |
+| TaskPool 或 Worker 抛出异常 | 不会到达 error observer，不会导致宿主进程退出，不属于崩溃策略覆盖范围 |
 | Native C/C++ 信号崩溃 | JS 崩溃策略无法阻止或重启；仅在后续启动时通过 `hiAppEvent.APP_CRASH` 采集 |
 | `APP_FREEZE` | 仅通过 `hiAppEvent.APP_FREEZE` 在后续启动时采集 |