visualifyjs 2.5.3 → 3.0.0

package/.claude/mem/notes/2026-02-19-visualify-infinite-loop-i18n-fixes.md

@@ -0,0 +1,31 @@
+---
+title: Visualify Infinite Loop & i18n Fixes
+type: note
+tags: [visualify, bugfix, react, useEffect, infinite-loop, i18n, rollup, potential-duplicate:2026-02-19-visualify-build-deployment-architecture-bug-fixes]
+created: 2026-02-19T22:19:34.350Z
+updated: 2026-02-19T22:19:34.350Z
+---
+
+## React useEffect Infinite Loop Fixes in Visualify (2026-02-19)
+
+### Root Cause Pattern
+Components using `props` or `sharedData` (object references) as useEffect dependencies cause infinite re-renders because React compares by reference, not value.
+
+### Fixes Applied:
+
+1. **SearchBar** (`src/core/components/searchbar.js`):
+   - Replaced `[config.source, debug, triggerValue]` with stable primitives: `[sourceUrl, sourceName, isArraySource, debug, triggerValue]`
+   - Used `sourceRef` to access latest config.source without it being a dependency
+   - Fixed trigger key extraction: `typeof triggerKey === 'object' ? triggerKey.name : triggerKey`
+
+2. **Selection** (`src/core/components/selection.js`):
+   - Replaced `[props, setSelectionOptions, sharedData, debug]` with extracted primitives: `[selection, urlval, rm_suffix, nested, entry, entryFirst, debug]`
+   - `entryFirst` tracks `sharedData[entry][0]` as a primitive instead of the whole sharedData object
+
+3. **i18n Initialization** (`src/core/visualify.js`):
+   - `initializeI18n()` was defined in `src/i18n/index.js` but never called
+   - Added call in `CreateApp()` before ReactDOM render: `initializeI18n(config.i18n || {})`
+
+4. **hilbert strict mode fix** (`rollup.config.mjs`):
+   - `hilbert/hilbert3d.js` has bare `debug = false; log = function(){}` — implicit globals break IIFE strict mode
+   - Added `fixImplicitGlobals()` Rollup plugin that prepends `var debug, log;` to hilbert modules

package/.claude/mem/notes/2026-02-19-visualify-v3-bundle-splitting-docs-restructuring.md

@@ -0,0 +1,32 @@
+---
+title: Visualify v3 Bundle Splitting & Docs Restructuring
+type: note
+tags: [architecture, bundle-splitting, v3, rollup, docs, potential-duplicate:2026-02-19-version-300-bump-and-build-fixes]
+created: 2026-02-19T20:02:41.423Z
+updated: 2026-02-19T20:02:41.423Z
+---
+
+## Visualify v3 Bundle Splitting Architecture (2026-02-19)
+
+### New on-demand chunks added to rollup.config.mjs:
+- `visualify-core.js` (733KB) - Core 2D: Recharts, EChartSwitcher, parsers, themes, widgets
+- `visualify-3d.js` (90KB) - 3D: Scatter3D, Bar3D, Surface3D, Line3D, ThreeScene, GL utils
+- `visualify-pages.js` (481KB) - Page mode: all viz components, router, fetch, Plotly
+
+### Entry files:
+- `src/entries/core.js` → VisualifyCore
+- `src/entries/charts3d.js` → Visualify3D
+- `src/entries/pages.js` → VisualifyPages
+
+### Bug fixed: `src/core/modules/threejs/index.js`
+- `await import()` inside ThreeJSManager constructor (invalid syntax)
+- Fixed: set managers to null in constructor, lazy-load in `init()`
+
+### Docs restructuring:
+- Sidebar: Docsify Plugin moved to "Getting Started", "Visualify.Recharts" → "Charts (2D)", 3D split out
+- `rechart-basic-usage.md`: Migrated from `<script defers>` + `<div>` to ```visualify code blocks
+- Chart demo pages (Rechart/*.md) still use LiveEditor pattern (intentionally kept for interactivity)
+
+### Backward compatibility preserved:
+- All existing builds (docs, portal, shared, legacy, docsStatic) unchanged
+- New chunks are additive, not replacements

package/.claude/mem/notes/2026-02-20-bundle-externalization-final-architecture.md

@@ -0,0 +1,29 @@
+---
+title: Bundle Externalization Final Architecture
+type: note
+tags: [visualify, rollup, externalization, iife, echarts, plotly, three, bundle, architecture, potential-duplicate:2026-02-19-visualify-build-deployment-architecture-bug-fixes]
+created: 2026-02-20T04:49:56.003Z
+updated: 2026-02-20T04:49:56.003Z
+---
+
+## Bundle Externalization Final Architecture (2026-02-20)
+
+**Key lesson learned**: You CANNOT externalize a library from an IIFE bundle if a bundled wrapper eagerly imports it at module initialization time. Specifically:
+- `echarts-for-react` does `import * as echarts from 'echarts'` and assigns to `this.echarts` in constructor
+- `react-plotly.js` does `require('plotly.js/dist/plotly')` and passes to factory
+- When externalized, these imports resolve to IIFE parameters which are bare global references
+- If CDN scripts haven't loaded, the globals are `undefined`, causing runtime crashes
+
+**Final config for legacy/docs IIFE builds (rollup.config.mjs)**:
+- `echarts` + `echarts-gl` → externalized (CDN required, bare `echarts` global)
+- `plotly.js` (including deep path `plotly.js/dist/plotly`) → externalized (CDN required, bare `Plotly` global)
+- `three` + `@react-three/*` → BUNDLED (eagerly imported via mapping.js, cannot be deferred with `inlineDynamicImports: true`)
+- Function-based `external` needed for `plotly.js` deep path matching
+- `safeExternalGlobals` typeof guards removed — CDN is required, not optional
+- Bundle: 2.8 MB (down from 9.6 MB)
+
+**Runtime CDN check**: Added to `src/index.js` — warns in console if `window.echarts` or `window.Plotly` missing with instructions.
+
+**OOM risk**: Bundling everything (echarts + plotly + three) causes Node OOM at 4GB heap. Need `NODE_OPTIONS="--max-old-space-size=8192"` if attempting full bundle.
+
+**docs/index.html**: Removed Three.js CDN and ReactThree stubs (now bundled). Kept echarts + plotly CDN scripts.

package/.claude/mem/notes/2026-02-20-chromium-page-fix-unstable-keys-and-double-event-b.md

@@ -0,0 +1,27 @@
+---
+title: Chromium page fix - unstable keys and double event binding
+type: note
+tags: [bugfix, chromium, react, echarts, keys, events, potential-duplicate:2026-02-19-css-grid-layout-fix-displaycontents-on-vcontroller]
+created: 2026-02-20T01:59:59.911Z
+updated: 2026-02-20T01:59:59.911Z
+---
+
+## Chromium Page Fix - Root Cause Analysis (2026-02-19)
+
+### Bug 1: Unstable React keys in Vcontroller (controller.js)
+- `Vcontroller.generateUniqueId()` created random UUIDs during render
+- `VisualifyWithStatePreservation` consumes sharedData context → re-renders on every state change
+- This cascades to Vcontroller re-render → new keys → all child components unmount/remount
+- All local state lost (Macaron selection, ScatterL chart instance, etc.)
+- Fix: Use stable keys from `componentConfig.id || ${type}-${index}`
+
+### Bug 2: Double event binding in ReCharts (echarts.js)
+- `ReactEcharts` component binds `onEvents` internally
+- Manual `useEffect` also binds the same events via `chart.on()`
+- Click handlers fire twice per click
+- Fix: Remove `onEvents` prop from ReactEcharts JSX, let useEffect handle events
+
+### Key Files
+- `src/core/widgets/controller.js` - Vcontroller stable keys
+- `src/core/modules/echarts.js` - ReCharts single event binding
+- `src/core/visualify.js` - VisualifyWithStatePreservation consumes context (causes re-renders)

package/.claude/mem/notes/2026-02-20-console-cleanup-bundle-optimization-commit.md

@@ -0,0 +1,20 @@
+---
+title: Console cleanup + bundle optimization commit
+type: note
+tags: [visualify, commit, bundle-optimization, console-cleanup, docs, potential-duplicate:2026-02-19-visualify-infinite-loop-i18n-fixes]
+created: 2026-02-20T03:48:49.579Z
+updated: 2026-02-20T03:48:49.579Z
+---
+
+## Commit 2726d2f - Console Cleanup + Bundle Optimization (2026-02-19)
+
+### Changes:
+1. **i18n**: Added `debug: false` to suppress `[DEFAULT]: WARN` logger
+2. **Console cleanup**: Removed debug console.logs from parser.scatterBio.js, Scatter.js, ScatterBio.js, recharts.js; changed error-path logs to console.error
+3. **Bundle externalization**: echarts, plotly.js (including deep path plotly.js/dist/plotly), three.js externalized from legacy IIFE + docs static configs using function-based `external` in rollup
+4. **CDN loader**: New `src/loader.js` → `dist/visualify-loader.js` (1.2KB) auto-loads CDN deps before visualify.js
+5. **Docs updated**: coverpage version 2.5.3→3.0.0, changelog with 3.0.0 entry, quickstart with loader usage
+
+### Bundle impact: 9.6MB → 1.8MB (-81%)
+
+### User preference: commit without co-author tag

package/.claude/mem/notes/2026-02-20-dotbio-dot-plot-fix-useeffect-dependency.md

@@ -0,0 +1,21 @@
+---
+title: DotBio Dot Plot Fix - useEffect Dependency
+type: note
+tags: [visualify, bugfix, dotplot, react, useEffect, sharedData, DotBio, replotly, potential-duplicate:2026-02-19-visualify-infinite-loop-i18n-fixes]
+created: 2026-02-20T06:02:42.342Z
+updated: 2026-02-20T06:02:42.342Z
+---
+
+## DotBio Dot Plot Fix (2026-02-20)
+
+**Root cause**: The infinite-loop fix (commit `e16efee`) changed DotBio's useEffect dependency from `[props, sharedData, debug]` to `[genelistSnapshot, debug]`. The `genelistSnapshot` approach broke reactivity because it didn't detect when `sharedData['mmtrbc_genelist']` was populated by the List component.
+
+**Fix**: Reverted dependency to `[sharedData, debug]` (without `props` to avoid unnecessary re-runs). Removed the ref pattern (sharedDataRef/propsRef) since we now depend on sharedData directly.
+
+**Key insight**: DotBio depends on sharedData changing when genes are added to the list. The snapshot approach (JSON.stringify of a single key) was too narrow — it missed the initial population of the key. Using `sharedData` directly as a dependency catches all relevant changes.
+
+**Also fixed in replotly.js**: Added `props.data` priority check — if parent passes data via props (like DotBio does), use that instead of preset.data. This prevents preset.data (empty `[]`) from overwriting actual data.
+
+**Pattern to remember**: When fixing infinite re-render loops, be careful not to narrow useEffect dependencies too much. The genelistSnapshot pattern broke the dot plot because it didn't re-trigger when the key first appeared in sharedData. Test all dependent components after changing useEffect dependencies.
+
+**User preference**: No co-author line in git commits.

package/.claude/mem/notes/2026-02-20-public-folder-cleanup-and-readme-rewrite.md

@@ -0,0 +1,25 @@
+---
+title: Public folder cleanup and README rewrite
+type: note
+tags: [visualify, commit, readme, public-cleanup, changelog, potential-duplicate:2026-02-20-console-cleanup-bundle-optimization-commit]
+created: 2026-02-20T04:09:55.739Z
+updated: 2026-02-20T04:09:55.739Z
+---
+
+## Commit 99a4f26 - Public folder cleanup + README + CHANGELOG move
+
+### Changes:
+1. **CHANGELOG.md** moved from root → `docs/CHANGELOG.md`
+2. **README.md** rewritten: concise 2-mode usage (Charts + Pages), CLI commands, features list
+3. **public/** cleaned to match release branch: removed EsoDev-specific files (chromium.json, visium.json, codex.json, visualify.json, _nav.json, debug/, mainpage.png)
+4. **.gitignore** updated with EsoDev config patterns to prevent accidental re-addition
+5. **CLI verified**: `visualify --version` returns 3.0.0-1.dev, all 5 commands registered (dev, docs, portal, init, edit)
+
+### Public folder now contains (matching release):
+- index.html (simple example with LiveEditor)
+- home.json (Browser component pointing to docs site)
+- editor.html (LiveEditor standalone)
+- manifest.json
+- robots.txt
+
+### User preference: commit without co-author

package/.claude/mem/notes/2026-02-20-v300-release-and-beta-channel-strategy.md

@@ -0,0 +1,29 @@
+---
+title: v3.0.0 Release and Beta Channel Strategy
+type: note
+tags: [visualify, release, v3.0.0, npm, beta-channel, workflow, potential-duplicate:2026-02-20-public-folder-cleanup-and-readme-rewrite]
+created: 2026-02-20T06:29:24.054Z
+updated: 2026-02-20T06:29:24.054Z
+---
+
+## v3.0.0 Release Published
+
+### Release workflow:
+1. Commit on dev → squash merge to release → version bump to `3.0.0` → push release → tag `v3.0.0` → GitHub release → npm publish (manual)
+2. Delete old dev branch (local + remote) → create fresh dev from release → set version `3.0.1-beta.0` → push
+
+### Beta channel strategy:
+- No npm beta publishing — too much version clutter
+- Beta = git dev branch directly: `npm install github:visualify/visualify.js#dev`
+- CDN beta: `https://cdn.jsdelivr.net/gh/visualify/visualify.js@dev/dist/visualify-loader.js`
+- Official = npm registry: `npm install visualifyjs`
+- Documented in README and docs/docs/quickstart.md
+
+### User preferences:
+- No co-author in git commits
+- Prefers simple beta strategy (git branch, not npm tags)
+
+### Git state after release:
+- release branch: v3.0.0 (tag v3.0.0)
+- dev branch: fresh from release, version 3.0.1-beta.0
+- GitHub release: https://github.com/visualify/visualify.js/releases/tag/v3.0.0

package/.claude/mem/notes/2026-02-20-visium-background-image-unknown-legend-fix.md

@@ -0,0 +1,19 @@
+---
+title: Visium Background Image + Unknown Legend Fix
+type: note
+tags: [visualify, bugfix, visium, react, useEffect, ScatterBio, potential-duplicate:2026-02-19-page-mode-docs-update-decisions]
+created: 2026-02-20T00:55:11.181Z
+updated: 2026-02-20T00:55:11.181Z
+---
+
+## Visium Background Image + Unknown Legend Fix (2026-02-19)
+
+**Root cause**: ScatterBio's useEffect dependencies were insufficient. When VisiumPlot updated its props (adding background image, legend:false, hidden axes), ScatterBio re-rendered but its effect didn't re-run because `sharedDataSnapshot` and `visiumCellFraction` didn't change.
+
+**Fix**: Added `configLegend` and `configHasBg` to ScatterBio's useEffect dependencies. This ensures the effect re-runs when:
+- VisiumPlot sets `legend: false` (configLegend: undefined → false)
+- Background image loads (configHasBg: false → true)
+
+**Also**: When `config.legend === false` (Visium spatial mode), skip `itemStyle.color` on scatter series so `visualMap` controls dot coloring instead of forcing all dots to one color.
+
+**Pattern**: When a parent component (VisiumPlot) wraps a child (ScatterBio) and updates props asynchronously, the child's useEffect must track ALL meaningful prop changes in its dependency array — not just sharedData-derived values.

package/.claude/mem/notes/2026-02-20-visualify-cdn-loader-bundle-externalization.md

@@ -0,0 +1,34 @@
+---
+title: Visualify CDN Loader + Bundle Externalization
+type: note
+tags: [visualify, rollup, cdn, bundle-optimization, loader, externalization, potential-duplicate:2026-02-19-visualify-dist-iife-self-contained-build-config]
+created: 2026-02-20T03:26:40.997Z
+updated: 2026-02-20T03:26:40.997Z
+---
+
+## Bundle Optimization (2026-02-19)
+
+### Externalized from legacy IIFE + docs static builds:
+- `echarts` → `window.echarts` (CDN: jsdelivr)
+- `echarts-gl` → `window.echartsGL` (CDN: jsdelivr)
+- `plotly.js` + `plotly.js/dist/plotly` → `window.Plotly` (CDN: cdn.plot.ly)
+- `three` → `window.THREE` (CDN: unpkg)
+- `@react-three/fiber`, `@react-three/drei` → globals (bundled in docs)
+
+### Key: `react-plotly.js` imports `plotly.js/dist/plotly` (deep path)
+- Must use function-based `external` in rollup to match deep paths
+- Must include `plotly.js/dist/plotly` in globals mapping
+
+### React wrappers (`echarts-for-react`, `react-plotly.js`) stay BUNDLED
+- They depend on React internals, can't be loaded as standalone CDN globals
+- They're small (~20KB each), the heavy deps are the core libraries
+
+### CDN Loader (`dist/visualify-loader.js`, 1.2KB)
+- Tiny IIFE bootstrap that auto-loads CDN deps then visualify.js
+- Detects existing globals (skip if already loaded)
+- Supports `window.$visualify.skip` array for opting out of deps
+- Entry: `src/loader.js`, config: `loaderConfig` in rollup.config.mjs
+
+### Bundle size impact:
+- `dist/visualify.js`: 9.6MB → 1.8MB (-81%)
+- `docs/static/js/visualify.js`: ~8MB → 1.8MB (-78%)

package/.claude/mem/sessions/session-2026-02-20-031524.md

@@ -0,0 +1,54 @@
+---
+title: "Session summary 2026-02-20"
+type: session
+tags: [auto-capture, session-end, zhipu]
+created: "2026-02-20T03:15:24.947Z"
+updated: "2026-02-20T03:15:24.947Z"
+---
+
+# Session Summary: Recent Activity
+
+## Key Learnings
+
+### Pattern Observed: Repeated Incomplete Tasks
+- **Issue**: The same optimization request was made 3 times within ~10 minutes without apparent resolution being committed or acknowledged
+- **Learning**: When `/omc-sisyphus` commands are repeated, check if previous attempt made changes before re-working. May indicate a communication gap or tool execution failure.
+
+### Technical Issues to Address (Pending)
+
+#### 1. Python Logging Warning
+- **Problem**: `[DEFAULT]: WARN : Using DEFAULT root logger`
+- **Root Cause**: Code is using Python's root logger (`logging.warning()`) instead of a named logger
+- **Solution Pattern**: Replace with named logger instantiation:
+  ```python
+  import logging
+  logger = logging.getLogger(__name__)  # Use module-specific logger
+  logger.warning("message")  # Instead of logging.warning()
+  ```
+- **Why**: Named loggers allow proper log level configuration per module and prevent the default logger warning
+
+#### 2. Async Listener Error (Browser Extension Context)
+- **Problem**: `Uncaught (in promise) Error: A listener indicated an asynchronous response by...`
+- **Context**: This is a common browser extension (Chrome/Firefox) error
+- **Root Cause**: Usually occurs when:
+  - A `sendResponse` callback is called after the listener returns `true`
+  - A Promise is returned but the async operation takes too long
+  - The message port closes before response is sent
+- **Solution Pattern**:
+  ```javascript
+  // Ensure sendResponse is called synchronously or within timeout
+  browser.runtime.onMessage.addListener((message, sender, sendResponse) => {
+    // Option 1: Return true and call sendResponse in async callback
+    asyncOperation().then(result => {
+      sendResponse(result);
+    });
+    return true; // Keep channel open
+  });
+  ```
+  - Or migrate to `return Promise.resolve(result)` pattern if supported
+
+### Action Items for Next Session
+1. **Check git status** - See if previous attempts made any commits
+2. **Search codebase** for `logging.warning(`, `logging.error(`, `logging.info(` (root logger calls)
+3. **Search extension code** for `onMessage.addListener` patterns that may have async issues
+4. **Consider**: This may be a new codebase - verify logging setup and extension manifest version

package/.claude/settings.local.json

@@ -0,0 +1,21 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(npx tsc:*)",
+      "Bash(node --check:*)",
+      "mcp__oh-my-claude-background__recall",
+      "mcp__oh-my-claude-background__remember",
+      "mcp__Playwright__browser_navigate",
+      "mcp__Playwright__browser_wait_for",
+      "mcp__Playwright__browser_snapshot",
+      "mcp__Playwright__browser_evaluate",
+      "mcp__Playwright__browser_take_screenshot",
+      "mcp__Playwright__browser_console_messages",
+      "Bash(npx rollup:*)",
+      "Bash(npm run build:*)",
+      "mcp__Playwright__browser_network_requests",
+      "mcp__Playwright__browser_click",
+      "mcp__Playwright__browser_run_code"
+    ]
+  }
+}

package/.github/workflows/static.yml.bak

@@ -1,51 +1,51 @@
-name: Build and Deploy Visualify
-
-on:
-  push:
-    branches:
-      - main
-
-permissions:
-  contents: write
-
-jobs:
-  build_and_deploy:
-    runs-on: ubuntu-latest
-
-    steps:
-      - name: Checkout Code
-        uses: actions/checkout@v3
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v3
-        with:
-          node-version: "16"
-
-      - name: Install Dependencies
-        run: npm install
-
-      # You may replace "build" with any specific build command for your application
-      - name: Build Application
-        env:
-          NODE_OPTIONS: --max_old_space_size=4096 # Adjust as needed
-        run: npm run 
-
-      # Ensure the build artifacts are in the `docs` directory
-      - name: Move build artifacts to docs
-        run: mv ./dist ./docs
-
-      #- name: Move build artifacts to docs
-      #  run: rm -rf ./docs/build/dist/visualify.js.map
-
-      - name: Deploy to GitHub Pages
-        uses: peaceiris/actions-gh-pages@v3
-        with:
-          github_token: ${{ secrets.VISUALIFY_BUILD }}
-          publish_dir: ./docs # Changed to docs
-
-      # If you want to upload the build artifact to GitHub
-      - name: Upload Build Artifact
-        uses: actions/upload-artifact@v3
-        with:
-          name: visualify-buildF
-          path: docs # Changed to docs
+name: Build and Deploy Visualify
+
+on:
+  push:
+    branches:
+      - main
+
+permissions:
+  contents: write
+
+jobs:
+  build_and_deploy:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout Code
+        uses: actions/checkout@v3
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v3
+        with:
+          node-version: "16"
+
+      - name: Install Dependencies
+        run: npm install
+
+      # You may replace "build" with any specific build command for your application
+      - name: Build Application
+        env:
+          NODE_OPTIONS: --max_old_space_size=4096 # Adjust as needed
+        run: npm run 
+
+      # Ensure the build artifacts are in the `docs` directory
+      - name: Move build artifacts to docs
+        run: mv ./dist ./docs
+
+      #- name: Move build artifacts to docs
+      #  run: rm -rf ./docs/build/dist/visualify.js.map
+
+      - name: Deploy to GitHub Pages
+        uses: peaceiris/actions-gh-pages@v3
+        with:
+          github_token: ${{ secrets.VISUALIFY_BUILD }}
+          publish_dir: ./docs # Changed to docs
+
+      # If you want to upload the build artifact to GitHub
+      - name: Upload Build Artifact
+        uses: actions/upload-artifact@v3
+        with:
+          name: visualify-buildF
+          path: docs # Changed to docs

package/.sisyphus/boulder.json

@@ -0,0 +1,65 @@
+{
+  "active_plan": "/Users/axibapro/Downloads/gits/visualify.js/.sisyphus/plans/phase-4-advanced-optimizations.md",
+  "started_at": "2026-02-11T13:20:00Z",
+  "session_ids": ["session-003"],
+  "plan_name": "phase-4-advanced-optimizations",
+  "current_phase": "Phase 4",
+  "phases": {
+    "phase1": {
+      "status": "completed",
+      "commits": [
+        "22a19ea - feat(cli): merge CLI into core, add visualify.json config, dual-mode builds",
+        "eff6f6b - chore: add EsoDev showcase dataportal for testing",
+        "6b0a207 - chore: add visualify.json config for EsoDev showcase",
+        "b37dbb4 - chore: add /dist to .gitignore"
+      ]
+    },
+    "phase2": {
+      "status": "completed",
+      "commits": [
+        "ead71c3 - feat(3d): add ECharts GL and Three.js 3D visualization support",
+        "4eec1ae - docs: add 3D visualization documentation and update CHANGELOG"
+      ]
+    },
+    "phase3": {
+      "status": "completed",
+      "name": "Developer Experience Improvements",
+      "commits": [
+        "2a6fca8 - feat(dx): add TypeScript, HMR, Visual Editor, a11y, i18n",
+        "a016d2e - feat(dx): complete Phase 3 Developer Experience features",
+        "b2d3de7 - fix(cli): add 'editor' alias and update CLI documentation"
+      ],
+      "tasks": [
+        "TypeScript migration with full type definitions",
+        "Hot Module Replacement (HMR) for configuration changes",
+        "Visual configuration editor (GUI)",
+        "Accessibility (ARIA labels, keyboard navigation)",
+        "Internationalization (i18n) support"
+      ]
+    },
+    "phase4": {
+      "status": "in_progress",
+      "name": "Advanced Optimizations",
+      "tasks": [
+        "Web Workers for data processing",
+        "IndexedDB caching layer",
+        "Streaming data support (WebSocket)",
+        "Progressive Web App (PWA) support",
+        "WebAssembly integration"
+      ]
+    }
+  },
+  "completed_tasks": [
+    "Phase 1: Critical Breaking Changes - CLI merge, visualify.json, dual-mode builds",
+    "Phase 2: Feature Parity + 3D - ECharts GL, Three.js, Docsify plugin",
+    "Phase 3: Developer Experience - TypeScript, HMR, Visual Editor, a11y, i18n"
+  ],
+  "next_tasks": [
+    "Phase 4: Web Workers for data processing",
+    "Phase 4: IndexedDB caching layer",
+    "Phase 4: Streaming data support (WebSocket)",
+    "Phase 4: Progressive Web App (PWA) support",
+    "Phase 4: WebAssembly integration"
+  ]
+}
+</content>