···2323- BUG-5: The Unix-socket file is now created under `umask 0o077`, closing the microsecond window where the inode was group/world-readable before `chmod 0o600`.
24242525### Fixes
2626-- Fix `sendData` hanging in Linux namespace containers. The Promise was resolving on the socket's `'close'` event, which requires both sides to half-close; some container network stacks don't reliably trigger the server's auto-half-close, so the client hangs forever. Resolve on `'finish'` instead — the writable side has been flushed to the kernel, which is exactly the guarantee a fire-and-forget send needs. (closes #18)
2626+- Fix fire-and-forget sends hanging in Linux namespace containers. Both the library-side `sendData` (Promise API in `@myobie/pty/client`) and the CLI-side `send` (used by `pty send`) were resolving on the socket's `'close'` event, which requires both sides to half-close; some container network stacks (e.g. Namespace.so runners) don't reliably trigger the server's auto-half-close, so callers hung forever. Both now resolve on `'finish'` — the writable side has been flushed to the kernel, which is exactly the guarantee a fire-and-forget send needs. (closes #18, #19 — thanks @schickling-assistant)
2727- Fix `pty list --remote` not rendering tags or displayName on remote sessions. Remote sessions now go through the same render path as local — displayName in parens, strategy marker, user-facing tags as `#key=value` — whenever the relay includes them in its `ls --json` output.
2828- Fix mouse tracking modes (1000/1002/1003) not being replayed when a client reattaches to a session with mouse tracking already enabled — the server previously only replayed the SGR encoding (1006), cursor visibility, and kitty keyboard flags. Clients (e.g., pty-layout) checking tracking mode to decide whether to forward mouse events will now see the correct state.
2929- Fix `EventFollower` starting at EOF when its directory watcher detected a brand-new `.events.jsonl` — `session_start` was already on disk by the time the dir event fired, so followers were skipping it. New-file detections now start at offset 0 while existing-file watches still start at EOF.