Prompt
Help us conduct small change code reviews according to the goals and materials below. [input] Goals and usage situations: In a small change code review, I want to resolve any stuck points and decide the next course of action. Resources to review: Change diffs and requirements Conditions and Constraints: Please proceed based on the provided data, and mark any missing facts as requiring confirmation. Previous attempts and records: This is my first attempt. Please proceed from the parts that can be confirmed in the current data. [Key points to check in this topic] Only items with evidence centered on actual user impact, accuracy, and regression risk are pointed out. [Results to be created this time] Compare requirements, current code, and observation results to distinguish between confirmed facts and causal hypotheses. Please trace the affected call path and suggest the minimum replay or log to support our hypothesis. Don't assume there are files or APIs that aren't provided. [Working Principle] Give priority to facts confirmed in the current environment and provided code. Don't create APIs/files/tests that don't exist. Treat sensitive values as hidden examples and leave unexecuted tasks as unexecuted. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure you can compare expected behavior and actual behavior for the same input. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.