v1.1.1 — set tools_generated:true so client treats runtime tools/list as authoritative

Without this flag, Claude Desktop and Claude Code cache the tool schema
fetched at install time and validate forever against that snapshot.
When the ES Memory host ships a schema change (e.g. the recent
oneOf-based tags fix, or new include_summary/edge_filter parameters),
the client keeps rejecting requests against the stale schema until the
.mcpb is reinstalled.

tools_generated:true tells the client that the manifest's tools list is
representative only and the runtime tools/list endpoint is the source
of truth — which is exactly the contract for a bridge that forwards to
a separately-versioned host.

No code change to the bridge itself (it was already a pure forwarder).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: apocryphx

bundle/manifest.json

@@ -2,7 +2,7 @@
   "manifest_version": "0.3",
   "name": "es-memory-bridge",
   "display_name": "ES Memory",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "Stdio bridge to the ES Memory MCP server. Provides Claude with persistent memory: store, retrieve, organize, and curate memories across sessions. Requires the ES Memory app to be running locally.",
   "author": {
     "name": "Kolja Wawrowsky"
@@ -16,6 +16,7 @@
       "args": []
     }
   },
+  "tools_generated": true,
   "keywords": ["memory", "persistence", "knowledge"],
   "license": "MIT",
   "compatibility": {