feat: smart update strategy

[Justineo]

Summary

• Introduced the smart-update planner (src/smart-update.ts) and wired it into ECharts.ts so reactive updates automatically choose between merge, replaceMerge, or full rebuild; manual updates and explicit update-options bypass the planner.
• Documented the strategy (English & Chinese README) directly under the option prop, explaining how manual mode and user-provided update-options behave
• Added AGENTS.md to outline contributor workflows for coding agents.
• Added Vitest infrastructure (pnpm test, config files) plus a tests/smart-update.test.ts suite covering signatures, planner heuristics, and real-world option transitions.
• Updated CI and release workflows to run pnpm test alongside lint/typecheck/build.

Smart update details

• We build a minimal signature (arrays, objects, scalars, options/media length) and compare it to the previous one.
• Deletions of objects → inject null; deletions of arrays → inject [] and add replaceMerge.
• ID or anonymous-item removal → replaceMerge; scalar removal or shrinking options/media → notMerge: true.
• Manual setOption and explicit update-options bypass the planner.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
vue-echarts	Ready	Preview	Comment	Sep 20, 2025 2:34pm

[kingyue737]

LGTM👍

[kingyue737]

Vitest has supported rolldown-vite since v3.2.2.

Would it make sense to also use rolldown-vite in tests for consistency with dev and build?

{
  "devDependencies": {
    "vite": "npm:rolldown-vite@latest",
  },
  "pnpm": {
    "overrides": {
      "vite": "npm:rolldown-vite@latest"
    }
  }
}

This would let us dedupe many devDependencies.

[Justineo]

We can do it in a separate PR.