Summary

• expose encodeMouse(event, options) on each terminal instance
• derive the tracking mode and wire format from the child output already fed into Ghostty
• preserve surface-space coordinates and explicit renderer geometry for SGR-pixels correctness
• return raw Buffer bytes suitable for writing to the child PTY
• retain Ghostty motion-dedup state while geometry is unchanged
• document pressed-button state, wheel mappings, and empty output for suppressed events

Coverage

Tests cover X10 tracking, normal tracking with X10 wire format, UTF-8, URXVT, SGR, SGR-pixels, press/release/motion, modifiers, buttons 1 through 11, mode transitions, disabled and suppressed events, out-of-viewport drags, same-cell motion deduplication, invalid input sets, and disposal.

A deliberate mutation that stopped resynchronization after feed() made the negotiated-mode regression test fail. An earlier implementation that reapplied unchanged geometry made the motion-dedup test fail, which is why the binding caches geometry.

Verification

• npm run build:native
• npm run build
• npm run verify
• 2 test files, 12 tests passed on x86_64-linux with Node 26.7.0 and the repository-pinned Ghostty commit