@aeptus/aexeo-emdash 0.8.18 → 0.8.19

package/CHANGELOG.md

@@ -4,16 +4,73 @@ All notable changes to `@aeptus/aexeo-emdash` are listed here.
 The format follows [Keep a Changelog](https://keepachangelog.com/),
 and the project follows [Semantic Versioning](https://semver.org/).
 
-## [Unreleased]
-
-## [0.8.18] - 2026-09-27
+## [0.8.19] - 2026-09-29
 
-Updates the EmDash integration to the current plugin and content APIs.
+Updates the EmDash integration to the current plugin and content APIs, and
+closes three security findings. Everything since 0.8.18 ships in this one
+version, since 0.8.19 had never been published.
 
 **Compatibility target:** EmDash `>=0.41.0 <0.42.0`.
 
+### Security
+
+- **EVAL_TOKEN is stored through the host's encrypted plugin settings.**
+  The sidecar bearer token was written as plaintext into the plugin's KV
+  namespace. EmDash provides `PluginContext.settings` with host-side
+  encryption for fields declared `type: "secret"` in a plugin's
+  `settingsSchema`, which is exactly this case; the descriptor now declares
+  that schema and the token is written there. Installs that predate the
+  change have their plaintext KV copy deleted on the next write, so the
+  credential is not sitting in the database twice. Hosts without
+  `EMDASH_ENCRYPTION_KEY` configured fall back to the previous KV path with
+  a warning that names the missing environment variable and never the
+  token, so the Setup page keeps working instead of failing closed.
+- **Sidecar URL validation is allowlist-backed and HTTPS-only.**
+  `handleSetupSubmit` accepted `http:`, which sent the bearer token in
+  cleartext, and rejected only `localhost` and `127.*` — leaving
+  `0.0.0.0`, `[::1]`, RFC1918, CGNAT, and the `169.254.169.254` cloud
+  metadata address reachable. It now requires HTTPS, rejects the private,
+  loopback, link-local, multicast, and IPv4-mapped-IPv6 ranges, and
+  compares the submitted host against the `allowedHosts` list the plugin
+  already computes at build time, so the form cannot store a URL the
+  plugin's own allowlist would reject later.
+- **Unauthenticated crawl-artifact routes removed from
+  `packages/aexeo-crawl-worker`.** `GET /findings/latest` returned the full
+  body of the customer's `aexeo-cli crawl` artifact and
+  `GET /findings/list` returned R2 key names, timestamps, and sizes.
+  Neither was behind the bearer-token check that guarded `/evaluate`, and
+  neither had any caller in this repository. CORS is not access control, so
+  anyone who learned the worker hostname could read the whole crawl
+  artifact. Both routes, the R2 binding, and the `examples/github-actions.yml`
+  R2 upload workflow that existed only to feed them are gone.
+
+### Removed
+
+- **`src/mcp.ts` and `src/indexnow.ts`.** Both were unreachable. The host
+  reads `PluginDefinition.mcp` as a `Record` of tool definitions keyed by
+  name; the code attached an `mcpTools` array with a different container and
+  a different per-entry shape, and `configured.ts` never attached it at
+  all. No MCP tool this package offered could ever have been invoked.
+
 ### Fixed
 
+- **Suppressions ignored by the Block Kit Refresh button.** In configured
+  mode the /findings "Refresh" button called the sweep without the
+  compiled `suppressionFilter`, so it re-persisted findings the editor
+  had explicitly silenced. The React `/refresh` route always applied
+  them, so the two surfaces disagreed and the documented guarantee
+  ("suppressed findings never reach the dashboard, /findings, or the
+  per-document panel") did not hold on the Block Kit path.
+  Root cause: `configured.ts` and `sandbox-entry.ts` each carried their
+  own near-verbatim copy of the interaction normalizer, the findings
+  page, the score widget, the document panel, and the refresh handler.
+  The copies had already drifted — this missing argument was one of the
+  drifts. Fix: the whole block now lives once in `src/findings-view.ts`,
+  and `RefreshOptions.suppressionFilter` is a **required** property, so a
+  caller cannot silently omit it again.
+- **`/evaluate` no longer 500s when `EVAL_TOKEN` is unset.** The check read
+  `env.EVAL_TOKEN.length` without a guard, so a worker deployed without the
+  secret threw a `TypeError` on every request instead of rejecting it.
 - **Sandbox access declaration:** replace obsolete capability strings with
   `content:read` and conditional `network:request`, scoped to the configured
   evaluator host. Remove unused schema, artifact, KV, and IndexNow host grants.
@@ -32,10 +89,51 @@ Updates the EmDash integration to the current plugin and content APIs.
 
 ### Changed
 
+- Extract the shared Block Kit view layer (`normalizeInteraction`,
+  `BlockInteraction`, `BlockResponse`, the findings page, the score
+  widget, the document panel, and the refresh sweep) out of
+  `configured.ts` and `sandbox-entry.ts` into `src/findings-view.ts`.
+  Behaviour is unchanged apart from the suppression fix above; the two
+  entrypoints keep their own dispatch and their own copy of the three
+  strings that legitimately differ (empty-state copy, score-widget
+  empty copy, hard-refresh banner variant), passed in through
+  `AdminViewTuning`. `BlockInteraction` and `BlockResponse` are
+  re-exported from `sandbox-entry.ts`, so the `./sandbox` entry's
+  public type surface is unchanged.
 - Bump the EmDash peer and development ranges to `0.41.x`; update the README
   and install guide to name the supported range and sandbox save behavior.
-- Add Vitest coverage using EmDash's official plugin runtime test host for
-  sandbox hooks, blocks extraction, resolved URLs, and translation alternates.
+- Add regression tests for `normalizeInteraction` — the ten edge cases
+  the 0.8.17 changelog claimed to have verified but never did — plus
+  entrypoint parity tests that drive both admin routes with the same
+  malformed bodies, and a test that the configured Block Kit refresh and
+  the React `/refresh` route agree on suppressed findings. Vitest coverage
+  now runs against EmDash's official plugin runtime test host for sandbox
+  hooks, blocks extraction, resolved URLs, and translation alternates.
+- Add `tsconfig.test.json` and a `typecheck:tests` script so `tests/`
+  and `vitest.config.ts` are typechecked. `tsconfig.json`'s `include`
+  covered `src/**` only, which meant the suite guarding the 0.8.17
+  production hotfix and the emdash test-host fixture plugin were both
+  unchecked. `npm run typecheck` now runs `typecheck:src` and
+  `typecheck:tests`.
+- `packages/aexeo-crawl-worker` no longer commits its build artifacts. The
+  checked-in `aexeo_emdash_bridge_bg.wasm` and its glue were several
+  releases behind the bridge the plugin actually calls — missing
+  `generateFactsPrompt`, `validateFactsManifest`, the manifest argument on
+  `scoreIntelligence`, and the `__wbg_*` bindings — and nothing in the
+  repository could regenerate them. The hand-written `.d.ts` files had been
+  updated to match the stale binary, which is why it went unnoticed. The
+  binary is now produced by `npm run build:wasm`, chained into `dev` and
+  `deploy`, and only the two declaration files remain tracked. The package
+  also gains a README, which it did not have.
+
+## [Unreleased]
+
+## [0.8.18] - 2026-09-28
+
+### Added
+
+- Include deterministic editorial-policy rules EDT001–EDT003 in the bundled Rust/WASM evaluator. Configured answer summaries, target questions, and evidence-marked claims can now be checked through the serialized Aexeo config.
+
 
 ## [0.8.17] - 2026-05-29
 

package/INSTALL.md

@@ -266,16 +266,25 @@ in this repo. Per-site deploy:
 
 ```bash
 cd aexeo-crawl-worker
-# Edit wrangler.toml: name, R2 bucket name, SITE_URL
+npm ci
+# Edit wrangler.toml: name, SITE_URL
 npx wrangler login
-npx wrangler r2 bucket create <bucket-name>
-npx wrangler deploy
+npm run deploy   # builds the WASM bridge, then deploys
 echo "$(openssl rand -hex 32)" | npx wrangler secret put EVAL_TOKEN
 ```
 
+The Worker's WASM is generated, not committed — `npm run deploy` runs
+`npm run build:wasm` first, which needs the Rust toolchain and
+`wasm-bindgen`. See the template's README.
+
 Then in the admin UI, visit
 `/admin/plugins/aexeo-emdash/setup` and paste the deployed URL +
-the same token.
+the same token. The URL must be `https`, must not point at a
+loopback, private, or link-local address, and must be the host in
+`evaluatorHost` above — the emdash sandbox rejects any other outbound
+host, so the form checks it before storing. The token is written
+through the host's encrypted plugin settings (`admin.settingsSchema`
+declares it `secret`), not to plugin KV.
 
 ## Alternative install sources
 

package/dist/configured.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"configured.d.ts","sourceRoot":"","sources":["../src/configured.ts"],"names":[],"mappings":"AAgCA,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,mBAAmB,CAAC;AA0HrD,MAAM,WAAW,uBAAuB;IACtC;;;OAGG;IACH,WAAW,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAEhC;;;OAGG;IACH,kBAAkB,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAEvC;;;OAGG;IACH,kBAAkB,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAEvC;;;;;OAKG;IACH,YAAY,CAAC,EAAE,SAAS,WAAW,EAAE,CAAC;CACvC;AAED,wBAAgB,YAAY,CAAC,OAAO,GAAE,uBAA4B,GAAG,OAAO,CA0H3E;AAID,eAAe,YAAY,CAAC"}
+{"version":3,"file":"configured.d.ts","sourceRoot":"","sources":["../src/configured.ts"],"names":[],"mappings":"AAqCA,OAAO,KAAK,EAAE,WAAW,EAAqB,MAAM,mBAAmB,CAAC;AA0HxE,MAAM,WAAW,uBAAuB;IACtC;;;OAGG;IACH,WAAW,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAEhC;;;OAGG;IACH,kBAAkB,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAEvC;;;OAGG;IACH,kBAAkB,CAAC,EAAE,SAAS,MAAM,EAAE,CAAC;IAEvC;;;;;OAKG;IACH,YAAY,CAAC,EAAE,SAAS,WAAW,EAAE,CAAC;CACvC;AAED,wBAAgB,YAAY,CAAC,OAAO,GAAE,uBAA4B,GAAG,OAAO,CA2H3E;AAID,eAAe,YAAY,CAAC"}