chore(analytics): display name, test against EmDash 0.40.1 and 0.41.0

.changeset/analytics-display-name.md

@@ -0,0 +1,7 @@
+---
+"@eisbachcode/emdash-plugin-analytics": patch
+---
+
+Gives the plugin the display name **Analytics**, which registry search results and the Plugins list of a registry install show instead of the slug `analytics`. A plugin registered in `plugins: []` still appears as `analytics` in the Plugins list, because EmDash names it after the plugin ID.
+
+Also tested on EmDash 0.40.1 and 0.41.0; neither needed a change.

.github/workflows/compat-matrix.yml

@@ -41,7 +41,7 @@ jobs:
           cache: pnpm
       - run: pnpm install --frozen-lockfile
       - run: pnpm typecheck
-      - run: ./scripts/compat-matrix.sh 0.39.0 0.39.1 0.40.0
+      - run: ./scripts/compat-matrix.sh 0.39.0 0.39.1 0.40.0 0.40.1 0.41.0
 
   latest:
     name: current EmDash (informational)

AGENTS.md

@@ -43,7 +43,7 @@ pnpm install
 pnpm typecheck
 pnpm test        # emdash-plugin validate, then vitest, per package
 pnpm build
-./scripts/compat-matrix.sh 0.39.0 0.39.1 0.40.0   # suites against other EmDash releases
+./scripts/compat-matrix.sh 0.39.0 0.39.1 0.40.0 0.40.1 0.41.0   # suites against other EmDash releases
 ```
 
 ## Releases

packages/analytics/README.md

@@ -9,7 +9,7 @@ entry that earned them rather than to a URL string.
 > **Status: early releases.** Cloudflare Web Analytics plus demo data: a
 > dashboard widget, an Analytics page with a setup check, a per-entry page,
 > an Analytics panel in the entry editor and four read-only MCP tools.
-> Tested on EmDash 0.39 and 0.40. See "Not in this version".
+> Tested on EmDash 0.39 to 0.41. See "Not in this version".
 
 The screenshots show demo data on a site made from EmDash's blog template.
 
@@ -137,7 +137,7 @@ After an update that changes a tool, EmDash stops serving the tools until
 they are approved again, but the switch stays on. Turn it off and on.
 
 **Sandboxed installs only, for now.** A plugin registered in `plugins: []`
-gets none of its MCP tools on EmDash 0.39 and 0.40: the plugin build keeps
+gets none of its MCP tools on EmDash 0.39 to 0.41: the plugin build keeps
 the tool declarations out of the runtime module, and EmDash's in-process
 loader looks for them only there. Under `sandboxed: []` or installed from
 the registry, the tools work. This is an EmDash limitation, not a setting.

packages/analytics/emdash-plugin.jsonc

@@ -27,8 +27,13 @@
 			]
 		}
 	},
-	// Registry search indexes slug and description and has no keywords
-	// field, so every provider this plugin supports has to be named here.
+
+	// Registry results, and the Plugins list of a registry install, show this;
+	// without it they show the slug. In-process installs always show the slug.
+	"name": "Analytics",
+
+	// Registry search matches the description and the keywords, so every
+	// provider this plugin supports is named in both.
 	"description": "Cloudflare Web Analytics on the EmDash dashboard and next to your content: visits, page views, top pages, referrers and countries, with per-entry performance mapped back to the entries that produced it.",
 	"keywords": ["analytics", "cloudflare", "dashboard", "widget", "content"],