Record the release-note convention that a CVE-bearing fix is cross-referenced between its defects-fixed entry and the security advisory block, with 1.78 as the worked example.

Author: dghgit

docs/claude/conventions.md

@@ -152,6 +152,8 @@ The `iana` arc is *not* dual-located: `org.bouncycastle.asn1.iana.IANAObjectIden
 
 Defects fixed and additional features go into `docs/releasenotes.html` under the **current** unreleased version block (e.g. section 2.1 with header "Release: 1.85"). Each entry is a single `<li>...</li>` referencing the GitHub issue number where applicable. The file is hand-edited HTML; preserve the existing prose style and `<ul>` structure.
 
+A CVE-bearing fix appears **twice** in its release's block: once as the "Defects Fixed" entry describing what was wrong, and once in the "Security Advisories" `<ul>` (`Release <ver> deals with the following CVEs:`) as `<li>CVE-YYYY-NNNNN - <one-line summary>.</li>`, kept in ascending CVE-number order. **Cross-reference the two**: close the Defects Fixed entry with a trailing `(CVE-YYYY-NNNNN)` before the `</li>` so a reader of the defect list can find the advisory, and vice versa. Historically the two lists were left unlinked; the 1.78 block was brought into line retroactively in `b1e21a374d` and is the worked example of the finished shape — all five of its advisory CVEs now carry a cross-reference in both directions. Do the same for new entries from now on. If an advisory has no matching Defects Fixed entry at all, that is a gap to fill rather than a case for skipping the cross-reference: 1.78 was missing entries for both CVE-2024-14041 (KyberSlash) and CVE-2024-29857 (crafted F2m EC parameters), and the fix is to write the defect entry from what the commits actually changed — for CVE-2024-29857, the `m` bound added to `ECCurve.F2m.buildField` in `efc498ca4c` / `fee80dd230` — not to paraphrase the advisory line.
+
 ## Version bumps touch more than the build props — the OpenPGP armor stamp is easy to miss
 
 Changing the BC version (opening a dev cycle, cutting a release) is a fixed, multi-file edit, and the version string is stamped in several places besides the build properties. Update **all** of these together:

docs/releasenotes.html

@@ -717,7 +717,7 @@ <h3>2.10.5 Security Advisories.</h3>
 Release 1.78 deals with the following CVEs:
 </p>
 <ul>
-<li>CVE-2024-14041 - Possible timing based leakage of the private key in ML-KEM (Kyber) decapsulation due to non-constant time division in the ciphertext compression functions ("KyberSlash").</li>
+<li>CVE-2024-14041 - Possible timing based leakage of the private key in ML-KEM (Kyber) decapsulation due to non-constant time division in the message decoding and ciphertext compression functions ("KyberSlash").</li>
 <li>CVE-2024-29857 - Importing an EC certificate with specially crafted F2m parameters can cause high CPU usage during parameter evaluation.</li>
 <li>CVE-2024-30171 - Possible timing based leakage in RSA based handshakes due to exception processing eliminated.</li>
 <li>CVE-2024-30172 - Crafted signature and public key can be used to trigger an infinite loop in the Ed25519 verification code.</li>