v1.2.0

1.2.0 (2026-11-05)

Added

• muniSegmentIterator_FindBreaksAround gives the boundaries around a
  byte offset, the last at or before it and the first after it, without
  reading the text from its start: what Backspace, the arrow keys and a
  click on a word need. It answers as the iterator would, for grapheme
  clusters, words, sentences and lines at every setting, class
  overrides and a word segmenter included, and leaves the iterator as
  it was. In ordinary text it reads a few code points, so on a long
  paragraph of English prose it takes under half a microsecond for
  clusters, words and lines, where stepping a fresh iterator from the
  start takes milliseconds; sentences back up to the last terminator.
  It needs an iterator given its whole text at init
  (#278).

No results change: the Unicode data is still 18.0.0 and
MUNI_RESULTS_VERSION stays 2, so stored normalized keys, skeletons
and verdicts from 1.1.2 stay valid.