R002: 错误码断言必须是number类型

What problem does it solve?

It prevents test failures and fragile logic caused by asserting OpenHarmony error.code with string literals instead of numbers.

Core Features & Use Cases

• Detect common assertion patterns: flags string-literal usage in expect/assertEqual/assertTrue and if-condition comparisons involving xxx.code.
• Validate numeric-only error codes: only reports cases where the asserted string is a pure numeric literal (e.g., "401", "14000011").
• Supports basic variable tracking: identifies string-typed variables/constants/parameters that are later used to compare against error.code, including catch-block alias cases (e.g., err as error alias).

Quick Start

Use this rule to scan your OpenHarmony test files and automatically list every place where error.code is compared or asserted using numeric strings, then convert those assertions to number literals.