[danielmlr]

Tests all three plugins against EmDash 0.42.0 and the 1.0 release candidate (1.0.1-rc.0), and updates the analytics README for the 0.2.1 release: MCP tools work in plugins: [] from EmDash 0.42, and the README gets the install section it never had.

The changeset is a patch and joins the two already in the Version Packages PR (#17). Merge after #18.

Changes

• Compat script: a version can be written as version:harness to override @emdash-cms/plugin-test as well. EmDash 1.0 moved the module the harness loads from emdash/plugin-test-runtime to emdash/internal/plugin-test-runtime. plugin-test 0.2.0, 0.2.3 and 0.2.5 import the old path, so with only emdash overridden every harness-backed test file fails to load against 1.0 ("./plugin-test-runtime" is not exported). This is a harness breakage, not a plugin one. plugin-test 0.2.6-rc.0 imports the new path.
• CI, declared: adds 0.42.0 and 1.0.1-rc.0:0.2.6-rc.0.
• CI, latest: pairs the current EmDash with the current plugin-test. Without this the informational job goes red for every PR once 1.0 becomes latest on npm, which is expected today.
• pnpm-workspace.yaml: release-age exclusions for 0.42.0, 1.0.1-rc.0, plugin-test 0.2.5 and 0.2.6-rc.0, plugin-cli 0.13.0 and the registry packages 1.0 depends on. All were published less than a day ago.
• Analytics README: "Tested on EmDash 0.39 to 0.42 and on the 1.0 release candidate". The "Sandboxed installs only, for now" paragraph now says the tools need EmDash 0.42 or later in plugins: [] (fix(core): register the MCP tools of built plugins listed in plugins: [] emdash-cms/emdash#3468 shipped in 0.42.0). New Install section: pnpm add, plugins: [analytics], one line on sandboxed: [] with a link to EmDash's sandbox guide. Until now the README showed only the beacon's config.
• AGENTS.md (root and analytics): the compat command and the MCP note match the above.

Unchanged on purpose: the dev toolchain stays on EmDash 0.39 / plugin-test 0.2.0 (moving it is for the next minor), and the sandbox budget stays at ten calls. The RC still ships subrequests: 10; the raise to 30 is emdash-cms/emdash#3383, which is open.

Verified

• scripts/compat-matrix.sh 0.42.0 1.0.1-rc.0 from origin/main plus the exclusions: 0.42.0 passes; 1.0.1-rc.0 fails in every package with the export error above.

• The same suites with emdash, @emdash-cms/cloudflare and @emdash-cms/blocks at 1.0.1-rc.0 and @emdash-cms/plugin-test at 0.2.6-rc.0:

  package	baseline	0.42.0	1.0.1-rc.0 (harness 0.2.6-rc.0)
  analytics	312	312	312
  content-freshness	119	119	119
  content-link-check	89	89	89

• The changed script at this branch's head: scripts/compat-matrix.sh 1.0.1-rc.0:0.2.6-rc.0 0.42.0:0.2.5 passes every package (312 / 119 / 89 in both rows). The second row is what the latest job now runs while 0.42.0 is current.

• In-process MCP tools on the RC: a create-emdash 1.0.1-rc.0 node:blog site with emdash@1.0.1-rc.0 and the analytics build from ci: publish plugins to the EmDash registry after npm #18's head in plugins: [analytics]. The admin plugin list shows the four tools. After Agent access is turned on, a token with mcp:tools:analytics gets all four from tools/list, and analytics__site_totals returned demo totals after the first sync. The widget, the Analytics page, the setup check and the per-entry page all render over the plugin route.

[changeset-bot]

🦋 Changeset detected

Latest commit: 5d8882d

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@eisbachcode/emdash-plugin-analytics	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR