Prompt
Help us integrate redundant logic according to the goals and materials below. [input] Goals and usage situations: I want to resolve the stuck point in integrating redundant logic and decide on my next course of action. Resources to review: Code suspected of being duplicated 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] Make sure the reason for the change is the same, not just the appearance, and avoid excessive abstraction. [Results to be created this time] Find correctness, compatibility, and exception handling issues in changed code that impact users. Present location, occurrence conditions, impact, and improvement plan together, and do not use unfounded possibilities as confirmed defects. Please explain that there is no problem. [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] Please check whether there are reproduction conditions and code basis for each point pointed out. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.