https://gitlab.synchro.net/main/sbbs/-/commit/653e414fd1364d2f24e3fcb6
Modified Files:
src/doors/termgfx/termgfx_termio.c
Log Message:
termgfx: stop reporting the dirty-rect share as unavailable on SyncTERM

The Ctrl-S strip showed "dr n/a" for every SyncTERM session, on every
tier, while patching was in fact running -- so the one number that says
whether the door is patching or repainting has never been readable on the client most callers use.

The readout was keyed on the terminal having REPORTED a pixel cell size (ESC[16t). SyncTERM never reports one: CTerm implements no xterm window
ops and uses CSI t as a private palette command, so the query fails its parameter-count check and is dropped. The patch path does not need that
value in any case -- the diff runs on a fixed tile grid in framebuffer
space, and placement derives its cell from canvas over grid -- so the
condition described a dependency that does not exist.

Measured against a SyncTERM-alike answering the grid CPR but no window
ops: the strip now reads "dr 100%" where it read "dr n/a", with partial
frames on the wire the whole time. A terminal that does report a cell
size is unaffected.

SyncRetro keeps its own version of this check: it derives the cell size
itself, so the state is reachable there for a genuinely unknown geometry.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/e6742dcb3a7878ae2abfaedb
Modified Files:
src/doors/termgfx/termgfx_termio.c
Log Message:
termgfx: resolve a pending lone ESC after the read, not before

termgfx_termio_pump() already drained the client each pump, so a sequence
split by the 256-byte read buffer completed in the same pump and the lone-ESC timer never saw it. What it could still see was a sequence split across pumps: the ESC read while the socket was empty, its tail arriving afterwards, the
next pump more than TERMGFX_ESC_TIMEOUT_MS later. The check ran first, so that tail was decoded as ordinary keys behind an Escape the client never sent.

Move the check below the loop and leave the loop by break rather than return, so only the "nothing left to read" exit reaches it. The hard-error and EOF exits still return -- the peer is gone and an Escape would go nowhere.

Behavior for a genuinely lone Escape is unchanged, which matters: SyncTERM sends a bare 0x1b for that key, and the doors on this path are driven from its menus. Affects SyncRPG, SyncSCUMM and SyncRetro.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)