@aeptus/aexeo-emdash 0.8.13 → 0.8.15

package/CHANGELOG.md

@@ -6,6 +6,109 @@ and the project follows [Semantic Versioning](https://semver.org/).
 
 ## [Unreleased]
 
+## [0.8.15] - 2026-05-06
+
+Plugin-only release tracking EmDash 0.11.x compatibility. The
+CLI workspace stays at 0.0.19 because the Rust crates aren't
+affected.
+
+### Added
+
+- **`@emdash-cms/plugin-types` declared as optional peerDep.**
+  EmDash 0.11.x split plugin manifest types into a dedicated
+  package; declaring it now (alongside `@emdash-cms/core`,
+  also optional) signals awareness of the split and removes
+  one step from the eventual migration when we touch the
+  manifest surface. No source-code change yet — all
+  manifest-shaped imports still come from the `emdash`
+  umbrella, which is still valid.
+
+### EmDash 0.11.x compatibility notes (no code change)
+
+- **Native locale-aware menu writes.** EmDash 0.11.x menu
+  automation is first-class locale-aware upstream with fail-
+  loud behavior on ambiguous writes. The plugin doesn't write
+  menus today, so no change is forced — the constraint matters
+  if we ever add menu-writing helpers (the read-side
+  constraint was already covered when 0.10's native i18n
+  shipped: never infer locale from menu names, always resolve
+  through `translation_group`).
+- **Seed/export/apply improvements for translated menu items.**
+  Doesn't affect Aexeo (no seed flows).
+- **Stricter sandbox bundle caps.** Doesn't affect today's
+  workspace-local install at Aeptus; matters if Aexeo ever
+  ships through an EmDash marketplace. Current bundle sizes
+  (configured.js 54KB, admin.js 43KB, sandbox-entry.js 27KB,
+  WASM kept external) remain lean — no action needed.
+- **Field-level `allowedTypes`.** Not relevant; no Aexeo rule
+  defines schema helpers for media fields.
+
+## [0.8.14] - 2026-05-06
+
+Two regressions Aeptus surfaced after running the v0.0.18 CLI
+release against their preview deployment, plus a new opt-in
+agent-discovery audit axis.
+
+### Added
+
+- **New `agent_discovery` rule group** with two opt-in checks
+  for the well-known machine-readable artifacts that signal a
+  site's agent-facing capabilities. Off by default since the
+  underlying specs (RFC 9727 api-catalog, SEP-1649 MCP server-
+  card) have nascent adoption and would otherwise generate
+  false positives across the long tail of sites that don't
+  publish them yet. Adopters opt in via:
+  ```toml
+  [agent_discovery]
+  enabled = true
+  ```
+  - `AGT001` (warning, policy/medium): missing
+    `/.well-known/api-catalog` (RFC 9727, finalized April
+    2025). The JSON Linkset format that lets agents enumerate
+    public APIs without crawling documentation.
+  - `AGT002` (warning, policy/medium): missing
+    `/.well-known/mcp/server-card.json` (SEP-1649, draft).
+    Lets MCP clients discover the site's MCP server endpoint
+    and capabilities without prior configuration.
+- **AGT layer mapping**: Retrievability primary (these files
+  exist so agents can *find* the site's surfaces), Absorbability
+  secondary (the surfaces they point at feed agent absorption
+  of the site's content).
+- **Post-crawl artifact probe extended** to HEAD-check the AGT
+  paths during live `aexeo-cli crawl` so AGT findings respect
+  the same presence signals as facts.json / llms-full.txt.
+  Probe runs unconditionally — the cost is two extra HEAD
+  requests, and sites that don't enable AGT just see the paths
+  recorded on `CrawlMeta` without any rule-side effect.
+
+### Fixed
+
+- **A11Y findings now use `severity: "warning"` (not `"warn"`).**
+  `Finding::is_error()` is implemented as `severity != "warning"`,
+  so the four-letter form was bucketed as an error in audit
+  summaries and made `success: false` even when the only
+  findings were warning-grade A11Y heuristics (heading-jump,
+  alt-equals-filename, missing-main-landmark). The three A11Y
+  rules emitted `"warn"` (A11Y004, A11Y005, A11Y006);
+  switched all three to `"warning"` to match the rest of the
+  rule corpus. No new `is_error` semantics — just severity-
+  string normalization.
+- **SRF030 now actually finds the homepage's markdown-mirror
+  alternates.** The 0.8.13 fix introduced
+  `homepage_advertises_markdown_mirror_discovery(site)` which
+  looked up `site.page("/")` — but the home page's route is
+  the empty string `""` in this codebase (per
+  `capture_route_for_relative_path`'s mapping for
+  `index.html`), not `"/"`. The lookup always returned None,
+  the helper always returned false, and SRF030 fired anyway
+  on Aeptus's preview despite the homepage carrying
+  `<link rel="alternate" type="text/markdown" href="/index.md.txt">`.
+  Switched to `site.route_pages().find(|p| p.route.is_empty())`
+  to match the rest of the crate's home-page convention.
+  Locked in by two new unit tests
+  (srf030_recognizes_markdown_mirror_discovery_on_home,
+  srf030_skips_unrelated_alternate_types).
+
 ## [0.8.13] - 2026-05-06
 
 Closes four false-positive paths Aeptus surfaced while running

package/dist/configured.js

@@ -1215,7 +1215,7 @@ function globToMatcher(pattern) {
 }
 
 // src/version.ts
-var PACKAGE_VERSION = "0.8.13";
+var PACKAGE_VERSION = "0.8.15";
 
 // src/configured.ts
 import { definePlugin } from "emdash";

package/dist/index.js

@@ -23,7 +23,7 @@ function buildAllowedHosts(evaluatorHost) {
 }
 
 // src/version.ts
-var PACKAGE_VERSION = "0.8.13";
+var PACKAGE_VERSION = "0.8.15";
 
 // src/sandbox.ts
 function aexeoPluginSandboxed(options = {}) {

package/dist/version.d.ts

@@ -1,2 +1,2 @@
-export declare const PACKAGE_VERSION = "0.8.13";
+export declare const PACKAGE_VERSION = "0.8.15";
 //# sourceMappingURL=version.d.ts.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@aeptus/aexeo-emdash",
-  "version": "0.8.13",
+  "version": "0.8.15",
   "description": "Aexeo SEO/GEO content evaluator as an emdash plugin",
   "license": "MIT",
   "author": "Aeptus",
@@ -65,6 +65,7 @@
   },
   "peerDependencies": {
     "@emdash-cms/core": "*",
+    "@emdash-cms/plugin-types": "*",
     "emdash": ">=0.7.0",
     "react": "^18.0.0 || ^19.0.0"
   },
@@ -72,6 +73,9 @@
     "@emdash-cms/core": {
       "optional": true
     },
+    "@emdash-cms/plugin-types": {
+      "optional": true
+    },
     "emdash": {
       "optional": true
     },