docs: transcribe the CHANGELOG entries for #1590 through #1676

[gsdali]

Summary

A batch transcription PR, the repair route in
okf/policies/changelog-on-merge.md. It transcribes and
nothing else, and it is the only open PR touching docs/CHANGELOG.md.

python3 Scripts/check-changelog-transcription.py --verify-transcribed reported 226 merges whose PR
body carried an entry that never reached the file. Forty-two of those are the two most recent waves,
and are what this PR closes:

• Fifteen from the second wave, fix(#1642): reachable()'s wrapper-type expansion runs to a fixpoint, not once #1659 through fix(#1638): composeShell takes a real patch grid, so it can actually split a face #1676. docs(#1399): read the booleans family of the unlaned refman-coverage lane #1649's entry was already in the file; the
  audit reported it missing only because the PR body's heading links #1399 and the file's does
  not.
• Twenty-seven from the Swift-layer sweep, docs(#1564): fix stale throughAxis reference-plane doc comment #1590 through fix(#1585): absorbAdditive Skips on total union failure instead of discarding history #1616.

Placed in merge order inside ## Unreleased, which the section keeps newest first: the second wave
above #1657's entry, the sweep below #1618's.

Seven entries are drafted, not transcribed

The policy says the merger transcribes and does not draft. These seven PRs have no
## CHANGELOG entry section in the body at all, so there was nothing to copy and the alternative is
a permanent gap in the release record. Each is written here from the merged diff and the PR's own
Defect/Fix sections, and every claim in them was re-checked against the tree on main:

PR	Why there is nothing to transcribe
#1590	body has Summary/Verification/Change, no entry section
#1591	same
#1593	body has Defect/Fix/Verification, no entry section
#1610	same
#1612	same
#1666	body was replaced in flight with a merge-order note about #1671's conflicting operation count; the original is gone
#1671	same, mirror-image note about #1666

#1666 and #1671 are the two that matter: #1666 removes ExtremaElSS.planeToSphere and
sphereToSphere and changes planeToPlane's return type, which is a MAJOR, and #1671 adds six
ContapContourResult operations. Neither had any release-note text anywhere.

Repunctuation

Three em-dashes in the transcribed text, in #1615's, #1601's and #1599's entries. Repunctuated per
okf/policies/writing-style.md, individually rather than with a
blanket substitution: a comma before an appositive clause, a colon where the clause expands on what
precedes it, a semicolon where both halves stand alone.

Verification

• check-changelog-transcription.py --verify-transcribed: "transcribed late" 33 to 68, "entry in
  the PR body, NOT in the CHANGELOG" 226 to 191. The +35/-35 is exactly the transcribed set; the
  seven drafted ones stay under "no entry section in the PR body", which is a fact about the PR
  body that transcribing cannot change.
• All ten static gates clean, including count-operations.py and check-docs-existence.py.
• Structural check on the file: every ### still has a blank line before it (the one exception is
  pre-existing, at the v1.11.3 release-history heading), and the count of triple-blank runs is
  unchanged at 21, so neither insertion introduced a bad join.

Still open after this

The other 191 untranscribed entries go back to #1119 and are not touched here. Filed separately
so the release does not silently inherit them: #1681.

SemVer impact

None. docs/CHANGELOG.md only.

CHANGELOG entry

None. This PR is the transcription.

[kilo-code-bot]

Code Review Summary

Status: 3 Issues Found | Recommendation: Address before merge

Overview

Severity	Count
CRITICAL	0
WARNING	3
SUGGESTION	0

Issue Details (click to expand)

WARNING

File	Line	Issue
docs/CHANGELOG.md	1119	Em-dash violates writing-style.md policy — use colon instead
docs/CHANGELOG.md	1121	Em-dash violates writing-style.md policy — use colon instead
docs/CHANGELOG.md	1122	Em-dash violates writing-style.md policy — use colon instead

Issue Details

The PR adds 642 lines to docs/CHANGELOG.md with 49 changelog entries (42 transcribed from PR bodies, 7 drafted). The transcription is thorough and well-structured.

However, the last entry (### Curve2D.swift's Gcc/analytic-intersection/extrema families split into their own files (#687)) contains three em-dashes in bullet points:

- `Curve2DGcc.swift` — `Curve2DGcc`, `Curve2DQualifier`, `Curve2DCircleSolution`,
- `IntAna2d.swift` — `Intersection2DPoint`, `IntAna2d`
- `Extrema2d.swift` — `Extrema2DResult`, `Extrema2d`

This violates the project's okf/policies/writing-style.md, which states: "No em-dashes. The em-dash (, ), and -- used as a sentence dash, are banned in every code comment, doc comment, markdown doc, changelog, commit message, and PR body across the ecosystem." Use a colon instead.

Suggested fix: Replace each em-dash with a colon:

- `Curve2DGcc.swift`: `Curve2DGcc`, `Curve2DQualifier`, `Curve2DCircleSolution`,
- `IntAna2d.swift`: `Intersection2DPoint`, `IntAna2d`
- `Extrema2d.swift`: `Extrema2DResult`, `Extrema2d`

Note: These lines are not visible in the GitHub diff (truncated), but exist in the PR head commit (56eb3c3). Inline comments could not be posted due to diff truncation.

Files Reviewed (1 file)

• docs/CHANGELOG.md - 3 issues

Fix these issues in Kilo Cloud

---

_{Reviewed by nemotron-3-ultra-550b-a55b:free · Input: 429.1K · Output: 12.1K · Cached: 2.5M}