docs: add changelog-accuracy lesson and pre-tag eval

docs/EVALS.md

@@ -30,7 +30,14 @@
 
 ## Active failure-derived checks
 
-_No failure-derived checks yet. Add one here when a verified regression gives a deterministic trigger — e.g. a guard that fails if the built `content.js` still contains `[LexAI` logs (T-03), or a test asserting the `onMessage` listener returns `true`._
+### E-RELEASE-01 — CHANGELOG version match and spot-check
+
+- **Prevents:** L-RELEASE-01 — false release notes shipped to CWS
+- **How to run:** (1) Extract version from `package.json` (e.g., `jq -r .version package.json`). (2) Grep for `## [version]` in `CHANGELOG.md`. (3) Pick 2–3 user-visible claims (feature name, behavior, action added) and verify against `git log --oneline` or the code (`src/lib/actions.ts`, `entrypoints/*/`).
+- **Pass condition:** (1) CHANGELOG has a section header matching the version; (2) each spot-checked claim is present in code or the latest commit subject(s) describe that feature being added.
+- **Cost:** fast (~2 min).
+- **When to run:** before `git tag v*.*.*`.
+- **Last verified:** 2026-08-12 (caught two false claims in v1.1.0 prep).
 
 ## Eval template