v0.3.4 — Windows SSH exit handling and published skill guidance

Changes

• Fixed Windows PowerShell SSH commands to forward the native exit code after version preflight and request execution. A missing native exit code fails with exit 1. Complete, validated submission evidence remains available after abnormal transport exits; partial or malformed output remains uncertain and never triggers an automatic resend. (#134)
• Updated four-language guidance to the separately published TypeScript skill 0.2.0, pinned to immutable source 8482cf644507c682915e35c85aa3384c53864906. Runtime 0.3.4 accepts only the explicitly reviewed legacy and successor metadata profiles; metadata compatibility does not authorize sending or prove delivery/ACK. (#134)
• Refreshed installation/version examples and corrected current compiled-version claims in the packaged skill compatibility documents, while preserving historical validation records. (#136, #138)

Upgrade and limitations

Install through your existing package manager:

npm install --global session-peer@0.3.4

SSH requires the same TypeScript client version at both ends. Coordinate endpoint upgrades; upgrading the runtime does not install or update the companion skill automatically.

Windows-client jump support (#20) and remote provisioning limitations (#23) remain open. Draft handoff/observation/app-server work (#106–#109) and the Side Session experiment (#82) are excluded. Queued/posted/submitted does not establish consumption or ACK.

Publication evidence — 2026-10-12

• Published package: session-peer@0.3.4; latest=0.3.4, preview=0.1.0-preview.1 unchanged at verification.
• Exact source: afed4a5a8945012faf1b23d52cffecb70470a5b3.
• Publication workflow 38194048045 succeeded after separate exact-source approval, protected GitHub environment approval and final npm 2FA approval. No protection bypass or upload retry.
• Reviewed local, Actions, staged and public package bytes match. SHA-256: 6c8cb114485e067ac3e7f5792de7febf3680cb14dcda6e2c67df6cab773ca03c. All 18 packaged Markdown files match the approved source.
• Registry integrity, source/run/workflow provenance, npm signature audit, isolated installation/version/list checks and removal passed. Publication verification record.
• Exact-main CI 38193736453 and CodeQL 38193736446 passed, including Windows-native Node 22/24. Local release-preparation tests: 190 total, 185 passed, 0 failed, 5 Windows-only skips.
• Windows 10 x64 / PowerShell 5.1 / Node 24 physical SSH tests for #134 used isolated synthetic native responses at compiled version 0.3.3. They are not a new 0.3.4 physical qualification or evidence of live agent queueing, injection or ACK.
• Fresh Trusted Publisher and package publish-2FA settings reads were waived by the user for this release only. They are not reported as passed; actual protected-environment and final npm 2FA approvals were completed.

The initial preparation artifact was withheld after a documentation finding. Its workflow was cancelled before upload; #138 corrected the documents, and only the newly approved source above was staged and published.

Changes: #134, #136 and #138. No new contributor was added in this release; the three merged commits are authored by @abruption.