Repository navigation
v0.3.0 — Remote usability and maintenance
Retrospective GitHub release record added on 2026-10-05 (KST).
Original npm publication: 2026-10-03T05:14:44.917Z (UTC).
Features since 0.2.1
- Ordered repeated --host results, IPv6 destinations, allowlisted SSH options and a hardened typed single-hop --ssh-jump for POSIX clients (#20, #84).
- Verified Claude/Codex sender context, structured return routes, --reply-to, Tailscale routing hints and opt-in doctor --check-return-route (#21, #86).
- update --check queries npm tags and reports installation-manager guidance. Cached notices are opt-in; no update is installed (#22, #85).
- Explicit shell-scoped sp shorthand for Bash/zsh and PowerShell; npm still registers only session-peer (#74, #75).
- Owned POSIX process-group cleanup for bounded external-command timeouts and a longer Windows creation-time probe deadline (#78, #79, #87).
- Add a remote deployment/version-compatibility design ADR (#23, #83); this release does not ship a deployment helper.
Compatibility and known limits
SSH endpoints must both run 0.3.0. Windows-client jump routing remains refused. Windows remote-deployment and newer receipt/recovery cases remain unvalidated. Windows update-notice refresh/failure/forged-field cases remain validation gaps; fixture and CI results are not a live-agent ACK.
The immutable 0.3.0 archive retains a stale PARITY migration sentence claiming multi-host aggregation is absent. Runtime aggregation and its feature section are present. Source correction #91 is packaged in 0.3.1. The demo remains a dated actual 0.2.1 exchange.
Published package and source
- Package: session-peer@0.3.0.
- Tag source:
05418b21fcdef890826325d56b07bb3dabce3bb0, verified against npm provenance. - Publication workflow record; npm attestation metadata.
- Integrity:
sha512-mdtikUMrGmMrdVSvPXdJcZeouTeuixOTzGwFKPhN66ATZqTohu9HKbejgOwXJe0/zrO+nt9asCAzAEhiHWDYGA==. - Dated validation record.
npm install --global --ignore-scripts session-peer@0.3.0posted/queued report submission, not consumption or ACK. An unknown outcome is not safe to retry automatically.