R013: 注释的废弃代码

To detect commented-out dead code in test files, scan `.test.ets`, `.test.ts`, and `.test.js` sources to flag consecutive 3+ line comment blocks containing code-like patterns, mapping each finding to its enclosing `it()` testcase for structured cleanup reporting.

Finding commented-out abandoned code blocks while excluding JSDoc requires filtering consecutive comment lines and skipping blocks with documentation markers like `@tc.*`, `@param`, or `@return`, ensuring only code-like patterns are reported for removal.

Mapping commented-out code issues to test cases involves tracing each detected comment block's location to the nearest surrounding `it()` block, or marking it as `-` if outside, providing precise attribution for code reviews.

Yes, this static analysis tool works with OpenHarmony `.test.ets` files, alongside `.test.ts` and `.test.js` formats, automatically scanning them to identify outdated commented implementations left for reference.

The minimum threshold for detecting dead code blocks is 3 consecutive comment lines, which helps distinguish substantial abandoned code fragments from brief inline explanations or single-line notes.

The structured issue report for commented-out dead code includes the file path, line range, owning `it()` testcase block, and code snippets, providing developers with actionable details for direct cleanup.