docs(#1125): transcribe nine missed CHANGELOG entries, and stop the audit reporting a correct one

[gsdali]

What & why

Nine merges landed with a CHANGELOG entry written in the PR body that nobody copied into
docs/CHANGELOG.md. okf/policies/changelog-on-merge.md names this as the failure the policy
introduces, and names a batch transcription PR as the repair route, subject to two conditions this
PR meets: it transcribes and does nothing else, and it was the only open PR touching the file when
it was opened (checked against every open PR's file list, not assumed).

Transcribed, newest merge first: #1122, #1112, #1097, #1079, #1069, #1053, #1043, #961, #870.
#961 and #963 carry byte-identical entries, since #963 is the reapply of #961, so they land as one.

After this the audit reports 0 entries in a PR body but not in the file, down from 9.

Closes #1125

CHANGELOG entry

None, this PR is the transcription. Adding an entry describing the act of transcribing entries would
be the loop the policy's "the PR must transcribe and nothing else" condition exists to prevent.
docs/CHANGELOG.md is expected in this diff: changelog-on-merge.md lists a batch transcription PR
as one of its three exceptions.

SemVer impact

NONE. Documentation and one report script. No Sources/ change, nothing a consumer can observe.

Checklist

• New or changed behavior is covered by a unit test in the same PR (not just manual
  verification), see SecondMouseAU/OCCTReconstruct#397
  for the ecosystem-wide test-coverage standard this is piloting.
• Every new test and every new --self-test case was run once with its subject broken, and the
  failure is reported here, see okf/policies/prove-the-test-fails.md.
• The CHANGELOG entry above is complete, and docs/CHANGELOG.md is not in this diff.
  This is the batch-transcription exception, named in changelog-on-merge.md; the file is
  in the diff by design and the section above says why there is no entry of its own.
• The SemVer impact above is stated, and docs/SEMVER.md is not in this diff.

The two entries that could not be copied verbatim

#870 and #961 carry 17 em-dashes between them. okf/policies/writing-style.md bans em-dashes
"in every code comment, doc comment, markdown doc, changelog, commit message, and PR body", and
instructs clearing them from any file you are already editing. docs/CHANGELOG.md contains zero
today, so a verbatim transcription would have introduced the file's first ones. Each was
repunctuated individually rather than by blanket substitution, using the replacements the policy
itself names: a comma where the clause is parenthetical, a colon where it expands on what precedes
it, a semicolon where both halves stand alone, and real parentheses for the one interrupted clause
in #870.

Two headings were normalised. #961/#963 led with a bold line where every entry in the file uses
a ### heading, which is what the page navigation keys on. #870's heading had no issue number and,
after the em-dash repair, read with two colons; the trailing clause became its own sentence. The
issue numbers added to both (#382, #384) come from the branch names the merges themselves record
(refactor/382-pass2a, reapply/384-pass3), not from a guess.

These are the only departures from verbatim, and they are the reason this PR touches the detector
as well.

The detector fix, and why it belongs here

entry_is_present() matches an entry by looking for its first ### or - line as a substring of
the changelog. Repunctuating a heading is therefore indistinguishable from never transcribing it,
so #870 would have been reported as missing forever, for having been transcribed correctly. That
is a report that cries wolf, and the next person either re-transcribes #870 (producing a duplicate)
or starts ignoring the report.

entry_is_present() now falls back to the part of the line before the first em-dash, and only when
the PR body's own line contains one. The prefix must be at least 24 characters after the marker to
count, so a heading that is mostly em-dash clause does not qualify and is still reported: a stub
prefix would match almost anything and turn the relaxation into a rubber stamp.

Prove-the-test-fails

Two --self-test cases added, 23 to 25, both run with their subject broken:

Injected defect	Result
the em-dash fallback removed entirely	FAIL #1125: a heading repunctuated to drop a banned em-dash is still found (22/25)
MIN_DISTINCTIVE_PREFIX dropped to 0, so any stub matches	FAIL #1125: a heading with nothing distinctive before the em-dash is still MISSING (22/25)

Each injection also trips the two pre-existing bucket-membership assertions, which is correct: those
assert the exact contents of the late and missing sets, so a misclassified fixture has to show
up in both places. 25/25 with neither defect.

Scripts/git-hooks/pre-commit (every gate, both censuses, and the clang-format check) exits 0.

Verification of the transcription itself

The entries were extracted from the PR bodies programmatically rather than retyped, then checked:

• no assembled heading duplicates one already in docs/CHANGELOG.md
• triple-backtick fences balanced across the assembled block
• em-dash count in docs/CHANGELOG.md after the change: 0, unchanged
• the resulting ## Unreleased heading order is reverse-chronological by merge

Spot-checked against the shipped tree rather than trusting the prose, since a wrong entry is worse
than a missing one: Shape.selfIntersects exists and carries @available(*, deprecated) naming
#1088 (Shape+Topology.swift:92), Surface.nlPlateDeformed and its siblings exist, and
Tests/OCCTXCAFTests/Issue1030DatumLookupGuardTests.swift exists.

Notes for the reviewer

16 merges have no entry section in the PR body at all, so there is nothing to transcribe and
they are deliberately not in this PR. Writing those is drafting, which changelog-on-merge.md
explicitly assigns to the PR author rather than the merger ("The merger transcribes; they do not
draft"). Classified, for whoever picks it up:

• 9 legitimately None: docs(okf): add the upstream OCCT patch process, start to finish #858, docs: require a GTest by default on every upstream OCCT PR #856, docs(okf): merge upstream-occt-style and patch-process, add format.patch technique #874, docs: sync the context-first policy with the ecosystem canonical #1091, docs: document Pass 4a coverage audit for 8 OCCT classes (#1021), #1120, Fix #1093: Remove empty Swift fences in FeatureRecognition.md private-helper section #1114 (docs and okf policy), chore: report-only file-size-check.py nudge for code-structure.md (#906) #907
  (report-only script), fix(#829, #877): add #595 to SEMVER.md v2.0.0 break table; remove orphaned doc comment #939 (SEMVER table plus an orphaned doc comment), Add test for PocketFeature.isOpen on compound where solidGroups cannot partition (#1089) #1115 (test-only).
• 1 already covered: Merge fix/1023-circle-involute-placement and fix/1068-self-intersecting-timeout to main #1103 is the merge of Geom2dEval_CircleInvoluteCurve: placement hardcoded to identity, and the curve itself is unwrapped #1023 and isSelfIntersecting(timeout:) never completes on an ordinary bevel gear solid: nil at every timeout from 1ms to 20s, full budget consumed each time #1068, whose entries are both in the file.
• 5 internal refactors, the same family that Pass 2a: Shape/Topology core duplication audit (#382 + #796) — 26 findings resolved #870 and Pass 3: XDE/Assembly duplication audit (closes #384) #961 did get entries for: fix(#792): deduplicate three bridge wrapper pairs #932, fix(#801): replace deprecated Convert_* per-index accessors with batch forms #934,
  fix(#794): factor shared scaffolding for 4 sibling-entry-point pairs #935, fix(#930): fix four over-coverage findings + sibling from Pass 2b retro #937, Merge PR #933: fix(#793) share int->TopAbs_Orientation decoder (with review fixes) #940.
• 1 real behaviour change with no entry anywhere: fix: Add null-wire guards to 19 ShapeAnalysis_Wire bridge functions (closes #1099) #1113, null-wire guards on 19
  ShapeAnalysis_Wire bridge functions, a refusal where there was a crash. This one should not ship
  in a release with no entry.

6 more are "transcribed late" and are correct in the file; the commit-level check asks what the
merge did, so they are not retroactively fixable and need nothing.

1 is unverifiable: e6fdb4e8 has no PR number in its subject.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (2 files)

• Scripts/check-changelog-transcription.py
• docs/CHANGELOG.md

---

_{Reviewed by nemotron-3-ultra-550b-a55b:free · Input: 206.2K · Output: 1.9K · Cached: 185.8K}