Prompt
Help us align our client state design work with the goals and materials below. [input] Goals and usage situations: I want to resolve a blockage in the client state design and determine the next action. Resources to review: Component structure and state changes 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] Distinguish between server original, local editing, derived values, and shared status. [Results to be created this time] Document the design intent, usage, exceptions, constraints, and verification methods identified in the current code. Do not create an intent that is not provided and leave any unconfirmed parts as questions. Please include a minimal call example and any contracts to be aware of when changing. [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 the interface and examples in the documentation match the actual code. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.