chore: sync fork with upstream microsoft/node-pty

[bwp91]

What this is

A full sync of this fork with upstream microsoft/node-pty, done as a true git merge so GitHub reports the fork as 0 commits behind upstream. The fork point was October 2023 — this brings in ~284 upstream commits while keeping the fork's packaging and multiarch prebuild distribution intact.

⚠️ This PR must be merged with a merge commit ("Create a merge commit"), not squash or rebase. A squash/rebase would discard the upstream commit history and put the fork straight back to "284 commits behind".

What we gain from upstream

Bug fixes relevant to real users:

• macOS: /dev/ptmx file-descriptor leak fixed (fix: /dev/ptmx leak on macOS microsoft/node-pty#882) and kqueue fd leak fixed (fix: close kqueue fd in SetupExitCallback on macOS microsoft/node-pty#931) — long-running processes no longer slowly exhaust file handles as terminals open/close
• Linux: inherited file descriptors are closed in child processes
• Proper handling of partial writes / kernel back-pressure (EAGAIN), fixing potential data loss when large amounts of data are written fast
• Several crash fixes during Node.js shutdown while a pty is open
• Windows: use-after-free fix (fix(win): use-after-free from unsynchronized access to ptyhandles microsoft/node-pty#922), CreateProcessW failures surfaced as exit events instead of uncaught exceptions (fix: surface CreateProcessW failures as 'exit' instead of uncaughtException on Windows microsoft/node-pty#934), handle/attribute-list cleanup on failed conpty spawns (fix: close pipe handles and free attribute list when conpty spawn fails microsoft/node-pty#935), pid set correctly after agent connection (freeze when using debugger on windows microsoft/node-pty#763)
• Avoids excessive listeners on data and other events (Avoid excessive listeners on data and other events microsoft/node-pty#841)

Features (all additive):

• write() accepts Buffer as well as strings
• resize() supports optional pixel dimensions
• Optional useConptyDll mode with bundled conpty 1.25 (third_party/conpty)

Structural:

• winpty is removed (Remove support for winpty microsoft/node-pty#868) — the deps/winpty tree (185 files) is gone. Windows uses conpty only, which requires Windows 10 1809+ (October 2018). Older builds are long EOL and Node 18+ barely runs there; noted as a footnote rather than a breaking change
• Modern toolchain: TypeScript 5, ESLint 10 flat config, node-gyp 11, stricter native compile flags (/sdl, -fstack-protector-strong)

Merge policy used

Area	Resolution
src/, typings/, binding.gyp, scripts/post-install.js, eslint config	upstream, wholesale
deps/winpty, src/win/winpty.cc, .eslintrc.js, .npmrc, azure-pipelines.yml	deleted (accepted upstream deletions)
README.md, package identity, release workflows, .prebuild/	ours
package.json	hand-merged — see below

package.json: keeps the fork's name/version, prebuild-install install chain (check-prebuild → prebuild-install → node-gyp), bundled linux prebuilds in files, engines, overrides, and allowScripts; adopts upstream's devDependency toolchain; drops deps/ from files (winpty is gone); ships upstream's third_party/ conpty payload.

The one deliberate code divergence: upstream centralised native loading in loadNativeModule() (src/utils.ts), which only looks for plain names like pty.node. This fork's bundled linux prebuilds use prebuildify's abi-tagged names (e.g. node.abi127.node). loadNativeModule() gained a small, clearly-commented fork preamble that consults the existing prebuild-file-path helper first, then falls through to upstream's search order. src/prebuild-loader.ts became orphaned as a result and is removed in a follow-up commit.

Impact on homebridge-config-ui-x

None expected. The UI uses spawn() + onData/onExit/write/resize/kill, all unchanged. Linux prebuild coverage (incl. armv6/v7 and musl) is produced by this repo's own workflows, which are untouched. macOS continues to build from source for now (#92 — which becomes much easier after this merge, since upstream's loader already reads plain-named binaries from prebuilds/<platform>-<arch>/; bundling darwin/win32 prebuilds in the published package is the planned follow-up).

Testing done (macOS arm64)

• Fresh npm install with regenerated lockfile — clean
• tsc build and eslint (flat config) — clean
• node-gyp rebuild from merged native source, then 24/24 mocha tests pass, including upstream's new ptmx/kqueue fd-leak regression tests
• Live smoke test: spawned a pty through the built package, verified output + exit code
• Note for local testing: npm install pulls the published v0.13.1 prebuild via prebuild-install, which masks merged native changes — rebuild with npx node-gyp rebuild before running tests

Other platforms need CI + the prebuild workflows to validate. Suggest releasing the next version as a beta and soaking it in a config-ui-x beta before stable.

🤖 Generated with Claude Code

[Copilot]

Copilot wasn't able to review this pull request because it exceeds the maximum number of lines (20,000). Try reducing the number of changed lines and requesting a review from Copilot again.