---
name: risk-release-notes-unverified-claims
description: Release-note/CHANGELOG entries in LexAI have been written from commit messages and feature-list intuition rather than verified against code — check counts and surface claims against source.
metadata:
  type: project
---

CHANGELOG/release-note prose in this repo has shipped factual errors that came from trusting commit subjects instead of the code.

Proven instances (2026-08-12 review of the v1.1.0 release prep):
- `CHANGELOG.md` 1.0.1 said Prompt Builder was "a new tab in the popup **and Options**", copying commit `acea99d`'s subject. `git show acea99d:entrypoints/options/Options.tsx` has zero prompt-builder references, and current `entrypoints/options/Options.tsx` still has none.
- `CHANGELOG.md` 1.1.0 said "12 named prompting patterns ... plus Auto" (implying 13). `PROMPT_PATTERNS` in `src/lib/actions.ts` has 12 entries *including* `auto` → 11 named + Auto.

**Why:** release bodies are generated from `CHANGELOG.md` by `.gitea/workflows/release.yml`, so an unverified claim becomes a permanent public artifact on a tag push that also publishes live to the Chrome Web Store.

**How to apply:** when reviewing any CHANGELOG/release-note change, verify every countable and every "where it appears" claim against the source file (grep the array, grep the entrypoint), and check the commit window with `git log <prev-bump>..<bump>` for user-visible features that were omitted. Do not accept a commit subject as evidence for a user-facing claim. Related: [[risk-release-workflow-untestable-pre-tag]].