# Changelog

## 1.3.1

- refine the bundled ER editor so empty tables show clearer multi-line guidance, using a cleaner line-broken message for both column creation and relation creation
- auto-open the ER inspector on selection, keep the show / hide context-menu wording aligned with the actual visible state after outside-close, and preserve the correct label on relation anchor / segment handles
- switch ER-only toolbar wording from node-oriented labels to table-oriented labels and add a bottom-right zoom controls overlay in the bundled local editor
- add regression coverage for the ER inspector toggle flow, handle-context-menu path, and zoom overlay interactions so the npm-shipped editor bundle keeps the new behavior stable

## 1.3.0

- refresh the hosted Japanese / English demo videos and regenerate the English GIF used by the npm package README so the public workflow demo stays shorter and current
- keep the bundled local editor usable when stretching or editing edges beyond the visible viewport by auto-panning edge interactions just like node drag
- soften the bundled editor's circular node depth shading so round nodes feel more like a natural surface than a dark blot while staying visually aligned with ER cards and other node shapes
- add flowchart / ER off-screen edge auto-pan regression coverage so the npm-shipped editor bundle keeps that behavior stable

## 1.2.0

- replace the README video embed with an animated English GIF demo so the round-trip editor flow is visible immediately on the npm package page

## 1.1.0

- keep repo-source local editor runs aligned with the latest built web bundle by preferring the freshest local editor asset copy when multiple local bundle directories exist
- make the root `npm run build` flow rebuild and sync the localhost editor bundle into `packages/zuiku-mcp/editor-app`, so repo-local MCP usage no longer depends on a separately stale copy
- align local acceptance/build tooling around that same bundle-sync path before packaging `zuiku-mcp`

## 1.0.0

- finalize the `zuiku-mcp` package/license/release-surface positioning for a stable 1.0.0 line
- align built-in current-open guidance so clients get consistent host-aware/open-flow expectations in release-facing usage

## 0.3.13

- add an optional Antigravity compatibility mode that lists underscore tool names such as `zuiku_open` while still routing them to the canonical `zuiku.*` handlers internally
- rewrite tool descriptions, built-in guides, prompts, and error/success text to the active alias set when that compatibility mode is enabled, so Antigravity does not learn dot-form names it cannot call

## 0.3.12

- clarify `zuiku.apply` hash conflicts as optimistic concurrency conflicts, not local editor startup failures
- tell clients to call `zuiku.read(path)` again, take the returned `hash`, and pass it as `expectedHash` when retrying `zuiku.apply`
- refresh preview install / release docs and logs for `zuiku-mcp@0.3.12`

## 0.3.11

- scope the localhost editor host registry by workspace/session root so one bridge does not silently reuse another workspace's host after a shared default-port collision
- keep `zuiku.open` / `zuiku.apply` from taking down the local editor host when browser auto-open fails, so the returned `editorUrl` / `healthUrl` stay usable even when the launcher command is missing
- make `zuiku.apply` hash conflicts explain that they are optimistic concurrency conflicts, not local editor startup failures, and point clients back to `zuiku.read(path)` before retrying
- refresh the preview install / release docs for `zuiku-mcp@0.3.11`

## 0.3.10

- improve localhost editor host startup so `zuiku.open` / `zuiku.apply` can fall back to a free port when the default port is occupied, with clearer guidance about when MCP bridge or IDE restarts are needed after a port change
- refresh built-in MCP guidance and related tests so AI clients get clearer coverage around `format-guide`, existing-diagram editing, and ER-from-DDL flows
- normalize flowchart routing handling so orthogonal is the stable default across import/export while explicit polyline settings are still preserved

## 0.3.9

- expand the built-in MCP guide set so prompts/resources now cover `format-guide`, `flowchart-example`, `edit-existing-guide`, and `er-from-ddl-guide` in addition to the existing quick-start entrypoints
- harden the npm release flow around tag-gated build/publish job separation, artifact SHA256 verification, and GitHub OIDC trusted publishing while keeping provenance disabled for the current private repository
- align install and release docs with the current built-in guide coverage, security hardening steps, and the pinned preview version `zuiku-mcp@0.3.9`

## 0.3.8

- keep the returned exact `editorUrl` usable by bootstrapping the local editor host as a standalone process when needed, so the bridge survives MCP stdio shutdown
- tighten the built-in MCP guidance so first-pass sample creation prefers one diagram per `zuiku.open` call unless canonical Zuiku Markdown is being supplied
- add npm release-context logging to smoke / workflow runs so `zuiku-mcp` and the paired IDE extension version are visible together during release operations

## 0.3.7

- keep the local editor host alive after MCP stdio disconnects so an opened `editorUrl` does not immediately die with `ERR_CONNECTION_REFUSED`
- pin preview install examples to `zuiku-mcp@0.3.7` and quote `$(pwd)` in shell snippets for more reproducible client setup

## 0.3.6

- add built-in MCP guides `zuiku://guide/start-here` and `zuiku://guide/temp-session-vs-file` so AI clients can orient themselves before opening or updating diagrams
- clarify `zuiku.open` / `zuiku.apply` tool descriptions around temp sessions, real `.md` files, exact `editorUrl`, and first-open wait time
- make open/apply result messages more natural for humans and AI, especially when no save path was provided yet
- refresh npm-facing docs so the built-in guide entrypoints are visible without adding long external documentation
- refresh the npm-facing description and README so the package reads closer to the stronger extension positioning around AI ↔ Markdown ↔ Diagram round-tripping
- expand npm keywords with `editor`, `ai`, `er`, and `flowchart` while keeping the package scoped as the MCP server artifact
- add the official X link to the npm README link set
- add an npm-facing note that package removal and IDE MCP workspace-config cleanup are separate steps

## 0.3.5

- switch the standard editor entry from `https://zuiku.dev/editor` to the bundled local-origin editor at `http://127.0.0.1:<port>/editor`
- bundle the local editor app inside the npm package and serve it from the localhost session host
- allow `zuiku.open(path, markdown, ...)` to create a new real file when the save path is already decided
- return `healthUrl` alongside `editorUrl` and refresh docs / guidance around exact local editor recovery
- tighten package smoke and acceptance coverage around the local editor flow
- keep WSL private-bridge handling and browser-bridge error guidance aligned with the new standard flow

## 0.3.4

- open or reuse the web editor after `zuiku.apply` saves by default when browser auto-open is enabled
- accept `mode: "save"` as a compatibility alias for `replace` in `zuiku.apply`
- improve browser launch handling for WSL, Windows, macOS, and Linux and soften MCP messaging to report open attempts more accurately
- refresh install and AI guidance around the default-open flow, `.md` / `.markdown` paths, and avoiding `.zmd`

## 0.3.3

- change the default editor URL from the dev-local `http://localhost:5173/editor` to `https://zuiku.dev/editor`
- clarify that `zuiku.open` should use the returned exact `editorUrl`, not a bare `/editor`
- refresh npm-facing metadata so the npm homepage points to the install guide and the package page explains the GitHub links it shows
- replace `UNLICENSED` package metadata with package-local public preview terms via `LICENSE.txt` and README notice

## 0.3.2

- initial public `zuiku-mcp` npm package release
