PR Review Comments

Apply this format to each review comment without changing the review's judgment or scope:

**P1: {{title}}**

{{finding}}

Use the appropriate level in place of P1, based on the context and the following definitions:

• P1 — Critical: A blocker requiring the highest priority. Do not merge or release until fixed. Examples: serious security vulnerabilities, data corruption risks, broken builds or crashing tests, and system-wide defects.
• P2 — High: Normally address before merge. Fix in this PR or make an alternative or follow-up issue explicit. Examples: core functionality that fails its specification, unhandled edge-case errors, and significant performance degradation.
• P3 — Medium: An improvement recommended when practical; handle flexibly according to release schedules and other constraints. Examples: refactoring, deduplicating code, and restructuring error handling for clarity.
• P4 — Low: An optional, minor nitpick that does not prevent merging. Examples: typos, inconsistent wording, supplementary comments, and style suggestions based on personal preference.
• P5 — Informational: Information sharing that requires no correction, such as questions, praise, or ideas for future reference.

Use the review's level when already assigned; otherwise classify the comment using these definitions. Do not introduce comments merely to fill a level. Make each comment understandable without the AI conversation, and link to any information needed to understand it.