@casys/mcp-erpnext 3.1.0-beta.9 → 3.2.0-beta.1

package/README.md

@@ -4,19 +4,20 @@ English | [繁體中文](README.zh-TW.md)
 
 [![JSR](https://jsr.io/badges/@casys/mcp-erpnext)](https://jsr.io/@casys/mcp-erpnext)
 [![npm](https://img.shields.io/npm/v/@casys/mcp-erpnext?logo=npm&color=cb3837)](https://www.npmjs.com/package/@casys/mcp-erpnext)
-[![CI](https://github.com/Casys-AI/mcp-erpnext/actions/workflows/test.yml/badge.svg)](https://github.com/Casys-AI/mcp-erpnext/actions/workflows/test.yml)
+[![CI](https://github.com/superWorldSavior/mcp-erpnext/actions/workflows/test.yml/badge.svg)](https://github.com/superWorldSavior/mcp-erpnext/actions/workflows/test.yml)
 [![MCP](https://img.shields.io/badge/MCP-server-1f6feb?logo=modelcontextprotocol&logoColor=white)](https://modelcontextprotocol.io)
 [![M8ven Score](https://m8ven.ai/badge/mcp/casys-ai-mcp-erpnext-1kev4k)](https://m8ven.ai/mcp/casys-ai-mcp-erpnext-1kev4k)
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](LICENSE)
 
 > [!IMPORTANT]
-> **Installing the 3.1 beta:** for npm/Node use
+> **Installing the 3.2 beta:** for npm/Node use
 > `npx -y @casys/mcp-erpnext@next`; for Deno use
-> `deno run -A jsr:@casys/mcp-erpnext@^3.1.0-beta/server`. Both follow the
-> current prerelease — JSR has no dist-tags, hence the range there. Exact
-> versions are in the [CHANGELOG](CHANGELOG.md). The beta adds the generic
-> document viewer and attachment workflows, so test it with the MCP host your
-> users actually run before replacing a stable deployment.
+> `deno run -A jsr:@casys/mcp-erpnext@3.2.0-beta.1/server`. npm's `next` tag
+> follows the current prerelease; the JSR command pins this exact beta because
+> JSR has no dist-tags. Stable **3.1.0** is available through npm's `latest`
+> tag. The beta retains the generic document viewer and attachment workflows, so
+> test it with the MCP host your users actually run before replacing a stable
+> deployment. See the [CHANGELOG](CHANGELOG.md) for release history.
 
 Let any MCP-compatible AI agent operate your [ERPNext](https://erpnext.com) /
 Frappe instance — documents, workflows, and interactive viewers inside the host
@@ -24,9 +25,10 @@ Frappe instance — documents, workflows, and interactive viewers inside the hos
 
 Works with **self-hosted** and **ERPNext Cloud** (frappe.cloud) instances.
 
-> Built on **[@casys/mcp-server](https://github.com/Casys-AI/mcp-server)** — the
-> MCP server framework (concurrency, auth, MCP Apps, observability) that powers
-> this project.
+> Built on
+> **[@casys/mcp-server](https://github.com/superWorldSavior/mcp-platform)** —
+> the MCP server framework (concurrency, auth, MCP Apps, observability) that
+> powers this project.
 
 ## Screenshots
 
@@ -79,16 +81,16 @@ results.
 ## What's New
 
 See the [CHANGELOG](CHANGELOG.md) for the full release history, or the
-[latest release](https://github.com/Casys-AI/mcp-erpnext/releases/latest) for
-the current version's highlights.
+[latest release](https://github.com/superWorldSavior/mcp-erpnext/releases/latest)
+for the current version's highlights.
 
-> **3.1 beta preview:** the beta keeps the 3.0 tool surface and adds a generic
-> document viewer, child tables, document attachments, in-view navigation, and
-> active context. **3.1.0-beta.9** adds read-only Buy evidence capture and an
-> immutable recorded-session viewer. Features remain capability-gated by the MCP
-> host. In particular, downloads require both proxied server tools and the MCP
-> Apps `downloadFile` capability. Buy evidence does not purchase or qualify a
-> live ERP.
+> **3.2.0-beta.1 preview:** the beta includes the creation-error guidance,
+> ERPNext 16 Opportunity compatibility and calendar-date fixes carried into
+> stable 3.1.0, alongside its generic document viewer, child tables,
+> attachments, in-view navigation and recorded Buy evidence. KPI percentage
+> changes, funnel currencies and context clearing on unsupported hosts are also
+> corrected. Features remain capability-gated by the MCP host; Buy evidence does
+> not purchase or qualify a live ERP.
 
 ## Documentation
 
@@ -242,7 +244,7 @@ tool is never replayed automatically. Overlapping or stale responses are ignored
 when a newer host payload or mutation has already won. A confirmed document
 change marks every potentially derived snapshot in the current navigation stack
 as stale; each marker is removed only when that surface has actually been read
-again. Separate MCP Apps are not synchronized automatically in the 3.1 beta.
+again. Separate MCP Apps are not synchronized automatically in the 3.2 beta.
 
 ### Building UI viewers
 
@@ -265,7 +267,7 @@ live ERPNext instance.
   caller cannot pass `sourceInstance`, URL, credentials, `capturedAt`, or a
   digest. Digital Thread stores those bytes in its own CAS; this server does not
   keep a second CAS.
-- App: `io.casys.mcp-erpnext.buy-evidence` `3.1.0-beta.9`, resource
+- App: `io.casys.mcp-erpnext.buy-evidence` `3.2.0-beta.1`, resource
   `ui://mcp-erpnext/buy-evidence-viewer` (`text/html;profile=mcp-app`), manifest
   `ui://mcp-erpnext/buy-evidence-manifest` (`application/json`),
   `acceptedActions` = `viewer.session.apply` only. Complete, partial,
@@ -274,8 +276,12 @@ live ERPNext instance.
   Digital Thread artefact (`provenance.bundleRef`), not a hash of the displayed
   projection.
 - Schemas: `io.casys.mcp-erpnext.buy-source-capture/1.0`,
-  `io.casys.mcp-erpnext.buy-recorded-result/1.0`,
+  `io.casys.mcp-erpnext.buy-recorded-result/1.0` and `/2.0`,
   `io.casys.mcp-erpnext.buy-recorded-session/1.0`.
+- Result `/2.0` carries bounded `excludedLines` metadata for selected lines
+  absent from priced `lines`: exact line ID, quantity, unit, and stated reason.
+  It carries no amount, currency, or price source; covered subtotals remain
+  sealed values and unresolved lines remain visible.
 - The viewer is built with the other MCP Apps
   (`cd src/ui && npm ci && node
   build-all.mjs`). Published JSR/npm artifacts
@@ -369,3 +375,12 @@ started, and [AGENTS.md](AGENTS.md) for the full architecture and conventions.
 ## License
 
 MIT
+
+Viewers and Buy result fields use the host locale: English, French, Simplified
+Chinese, Traditional Chinese, Hindi, Bengali, Tamil and Urdu. Chinese script
+tags take precedence over region tags; `zh-TW`, `zh-HK` and `zh-MO` select
+Traditional Chinese when no script is specified. Urdu uses right-to-left
+document direction, and a later host locale change updates the language and
+direction without reloading the viewer. App-level waiting and rejection screens
+retain English labels in this beta; host-context support for those shared
+surface screens remains an upstream MCP View follow-up.