Neil 383ae50a35 fix(utf8): stop reading a code point past the end of a sliced string (#13782) ...

Once V8 optimizes the calling function, `String.prototype.codePointAt` on a
sliced string pairs a trailing high surrogate with the code unit that follows
the SLICE inside its parent, returning a code point the string does not
contain. Every UTF-8 byte scan built on `codePointAt` therefore reported one
byte too many for a prefix slice cut mid-pair, but only after tier-up, which
is what made terminal-stream-byte-length.test.ts fail intermittently on the
same commit.

Read the units explicitly with `charCodeAt`, which stays bounds-correct in
every tier, via a shared `readUtf8CodePointAt`.

2026-08-11 02:04:10 -07:00

..

cli

fix(orchestration): release context-only dispatches (#13376)

2026-08-09 14:49:36 -07:00

main

fix(utf8): stop reading a code point past the end of a sliced string (#13782)

2026-08-11 02:04:10 -07:00

preload

refactor usage provider IPC plumbing (#13543)

2026-08-10 20:39:18 -07:00

relay

perf(ssh): cancel abandoned remote port scans (#13548)

2026-08-10 20:49:21 -07:00

renderer

fix(utf8): stop reading a code point past the end of a sliced string (#13782)

2026-08-11 02:04:10 -07:00

shared

fix(utf8): stop reading a code point past the end of a sliced string (#13782)

2026-08-11 02:04:10 -07:00

types

fix(codex): publish Windows system-default sessions (#12611)

2026-08-07 16:53:41 -07:00