git:20260514.cfb469a to git:20260601.3823104

4 added, 0 removed. Audit A to A.

- Never simplify the run-api reference descriptions of the UNIVER API. They are foundational context for LLMs to understand Univer API behavior and contracts.

- When introducing `univer-cli`, keep the wording concise, elegant, and aligned with the taste of experienced mainstream developers. Avoid verbose, repetitive, or over-explained descriptions.

- Unless a shell behavior is unique to `univer-cli`, avoid explaining obvious shell usage. Assume the LLM is already highly proficient with shell workflows.

+ - For complex project planning, define success criteria before the plan. The success criteria file is

+ a short checklist of user-visible outcomes, preservation constraints, deliverables, validation

+ signals, non-goals, and ambiguities left for the plan. It is not a plan and must not contain pack

+ decomposition, assertion design, or execution strategy.