fix: bump @hono/node-server to fix Node 24 'Failed to find Response internal state key'

[linus-codes]

Fixes ANY-6889.

Every boot of the gateway on Node 24 prints Failed to find Response internal state key (visible in escher local dev as portkey: Failed to find Response internal state key via the compose service prefix). @hono/[email protected] predates undici's Node 24 change to Response internal state (known upstream: Portkey-AI#1604, fixed in node-server 1.14.2 via honojs/node-server#241 — upstream's own bump PR is unmerged, so the patched branch never inherited it). Besides the log noise, the missing state key disables node-server's fast Response path and is the defect behind upstream's reported intermittent Node 24 crashes.

One-line fix: @hono/node-server ^1.3.3 (locked 1.13.5) → ^1.19.17. npm also canonically re-sorted two adjacent dep lines; the lockfile diffs as binary per this repo's .gitattributes.

Verified on Node v24.18.0 (same major as the node:24-alpine prod image):

• 1.13.5 emits the error at import; 1.19.17 clean — minimal repro serving a fetch Response through serve().
• npm run build green; node build/start-server.js --headless boots to ready with zero occurrences.
• requestContext suite differential vs untouched patched: identical results (2 pre-existing ambient failures, 53 passed) — the bump changes no test outcome. The other red suites are ambient on patched (stale jest.mock paths, plugin tests needing live external services).

After merge: escher apps/shared/portkey pin bump to the squash commit follows as its own PR.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
gateway	Error		Aug 15, 2026 2:10am