v0.5.0 — Platform qualification groundwork

Platform qualification groundwork

session-peer@0.5.0 is published from reviewed source 12f98f2793b78f647107368c06e83286c5026e05.

Changes

• Select native observation profiles by exact platform/version tuples and retain procfs/storage inspection groundwork with a non-selectable Linux arm64 candidate (#153).
• Prepare an unselected Windows process-tree backend and private-storage inspection guard. Production Windows process cleanup retains its direct-child behavior (#156).
• Model Win32-OpenSSH ProxyCommand construction and preserve isolated no-network quoting evidence. Windows-client jump remains refused before effect (#154).
• Preserve the four exact skill metadata profiles accepted by 0.4.0 in a finite 0.5.0 doctor row; retain the separate skill installation pin and refresh current multilingual version examples.
• Exclude the deferred deployment harness (#155). Checklist-first minimum-contract redesign is tracked in #158 under still-open #23.

Qualification and upgrade notes

Native observation retains its documented macOS arm64/native-version/topology scope. Linux native observation, Windows handoff storage/native observation, Windows-client jump and automatic ACK remain unsupported. #130/#131/#20/#23 retain their remaining acceptance criteria. Side Session and steering experiments (#82/#142) are excluded. This release does not complete cross-platform qualification or add new live native/model/ACK evidence.

SSH peers must use exactly the same TypeScript version; update each endpoint with its existing manager. Queued/submitted/posted results do not establish receipt ACK, and an unknown outcome does not permit automatic resend. Runtime publication does not install, publish or repin the independently managed skill. No fleet/global installation is performed by this release process.

Publication verification

• npm 0.5.0: latest=0.5.0; preview=0.1.0-preview.1 is preserved.
• Stage-only workflow 39415871999 used the exact source above; the required human environment and final npm stage approvals were completed.
• Reviewed local, retained Actions and public npm tarballs have identical SHA-256: 50f603d9e5b6db8a99b4bcab464767ad30ff38ecac3fbebc22fc03fdd4c66b1d.
• Registry SHA-512 integrity: sha512-lLc7SFRUydY5TjcX8aE18kgfC88Wi4Mx/OXcbLlk0W9yH+JYLkxGwmZIiC7S1bczFgXzsP3xSe8DqiD7YplpDw==.
• Registry signature/provenance audit and fresh isolated public installation, exact version, empty discovery and removal passed. All 77 archive files match the expected package and all 18 Markdown files match the publication source. Provenance payload/source linkage was independently checked against this repository, main, publish.yml and the publication run.
• Exact-main CI 39414569590, attempt 2, and CodeQL 39414569065 passed. One initial macOS Node22 test returned refused where queued was expected; its detailed cause was not captured. A single failed-job rerun passed without source, timeout or assertion changes; the initial cause remains unproven.
• The package's web publish-2FA-policy lookup was explicitly skipped for this release; it is not a fresh settings audit. Trusted Publisher stage-only permissions and required human gates were separately verified. No settings, protections or credentials were changed.

v0.4.0 — Scoped delivery observation and explicit receipts

Highlights

• Opt-in Handoff v1 correlation, private POSIX prepare/status/wait records and durable sender fencing. Ordinary sends retain their existing result fields and exits.
• Qualified client-ID injection observation for exact Codex 0.160.1/0.162.1 on macOS arm64, with original home/writer generation and an already-warm supported metadata store. Injection observed does not mean understanding, task completion or receipt ACK.
• Explicit operator-confirmed receipts with immutable per-operation deadlines and late-evidence history. operator_confirmed is an operator attestation, not model authentication. Wait/status/confirmation never resubmit the native message.
• Bounded same-version SSH destination preparation and request-matched evidence preservation. Budgets are not renewed remotely; uncertain submissions never trigger fallback or resend.
• Finite skill metadata support for existing profiles plus the reviewed proposed skill 0.3.0/min0.1.0/full0.4.0/probe-help tuple. Runtime publication does not publish, install or update a skill; the existing published skill pin remains unchanged.

Reliability and safety

Prepared Claude/inactive Codex targets retain private continuity bindings. The sender journal protects its message-binding digest with AES-256-GCM and a separate private key; lost/changed/untrusted history never permits automatic recovery or replay. Native queue mechanics check the actual process build, executable identity, deadline and opened SQLite device/inode after the durable fence/final owner check. Literal message-file -, concurrent-wait SIGINT and owned-process cleanup regressions are covered.

Limits

Linux/Windows native observation, Windows private handoff storage and automatic voluntary receipt producer/collector remain follow-ups #130–#132. Required unsupported evidence refuses before submission. Queueing, text replies, turn completion and queue deletion never manufacture ACK. This is not receiver deduplication or a general exactly-once guarantee. Side Session/steering experiments are excluded.

Install or update

npm view session-peer@0.4.0 version dist.integrity
npm install --global --ignore-scripts session-peer@0.4.0
session-peer --version

Expected: session-peer 0.4.0 (typescript). Use the existing package manager and align both SSH endpoints to exactly 0.4.0. Python, remote runtime and separately managed skill updates remain independent.

Publication evidence

Source: dde3923efe116f87f38b1639b29b889d2b832e44.
Actions: https://github.com/abruption/session-peer-ts/actions/runs/39077096491
Tarball SHA-256: 84adc8b50ef8f03a2c2170e3c36a97b573f28a6bcbeb7dbc965e16c3b37a57c9.
Integrity: sha512-mMNJ118atoflhpFTkf2+DtO7MRf7FQnPK3lKWbq/vd8Xvb5DsjUtAgydIBOcd3Xj9BCYGqM50aFhzUr4dDGHSw==.

Public latest=0.4.0 and unchanged preview were verified. Reviewed, fresh merged-source, retained Actions, staged and public tarballs are byte-identical. Registry signature audit, Sigstore signature/certificate/transparency verification with the GitHub workflow identity/issuer policy, and source/subject/run binding checks passed. Isolated install/version/list/uninstall passed. The archive contains 71 allowlisted files; all 18 packaged Markdown files match source bytes. These packaging/provenance checks do not qualify additional native delivery or ACK platforms. Detailed scope and dated native evidence are in PARITY.md and VALIDATION.md.

The fresh Trusted Publisher mapping was checked as stage-only. The user explicitly skipped the separate web package publish-2FA policy read; it was not freshly audited. Actual GitHub environment and final npm approvals were completed.

Contributors

@abruption

Changes since v0.3.6

v0.3.6 — Published skill guidance packaging

Changes

• Package the published TypeScript skill 0.2.1 guidance and immutable source pin from #146.
• Align the four-language installation, update and compatibility guidance with 0.3.6.
• Carry forward the same three reviewed skill profiles (0.1.0, 0.2.0, 0.2.1) in an explicit 0.3.6 metadata row. Historical verdicts remain unchanged; future version ranges are not accepted.

Compatibility

SSH endpoints must both use 0.3.6; 0.3.5 and 0.3.6 refuse each other at preflight. Runtime and skill installation/update remain separate. The companion skill is not installed automatically; its immutable source is 0f494cab. Metadata compatibility does not establish content authentication, send permission, delivery or ACK. No 0.4 handoff/observer/ACK, Side Session or steering feature is included. Existing platform/provisioning limitations remain.

Install

npm install --global --ignore-scripts session-peer@0.3.6
session-peer --version

Expected: session-peer 0.3.6 (typescript).

Verified publication

• Source: 27fc741f.
• Preparation: #148; exact-main CLI/CodeQL passed, Windows Node 22/24 included.
• Stage-only workflow and final user npm approval completed.
• Reviewed, Actions, staged and public tarballs are byte-identical. SHA-256: 510e06ea1e118ceadb4096ec2fe9e564b2832e133aa0a21614d8b12db1764181.
• Registry integrity, provenance source/run/subject, npm signature audit and isolated installation/removal passed. Preview remains 0.1.0-preview.1.
• Fresh Trusted Publisher and web publish-MFA settings reads were explicitly skipped for this publication, as recorded in #148. Protected GitHub environment and final npm approval were completed; the skipped settings are not claimed as freshly audited.

No fleet/global installation or new native/live delivery/ACK test was performed.

v0.3.5 — TS skill profile compatibility

Changes

• Extend the finite TypeScript skill metadata matrix to the exact 0.2.1 profile, alongside existing 0.1.0/0.2.0 profiles. Historical runtime verdicts remain explicit; arbitrary future versions are not accepted.
• Verify the complete reviewed skill candidate through the compiled 0.3.5 default and file inspector. Metadata compatibility does not authenticate instructions or authorize sending, consumption or ACK.
• Align all four language READMEs/guides and the skill-design matrix with merged source, including the Codex review corrections for artifact status and evidence links. Existing CLI behavior, Python reference and published skill pin remain intact.

Upgrade

npm install --global --ignore-scripts session-peer@0.3.5

Both SSH endpoints must use exactly 0.3.5. npm does not update a separately managed skill. The published skill 0.2.0 pin remains valid; successor skill finalization/publication and an immutable install pin remain separate. No 0.4 handoff, general ACK/wait, Side Session or Steer experiment is included.

Verified publication

• npm latest=0.3.5; preview=0.1.0-preview.1 unchanged.
• Source: a2057940ba19056fcaaa5551a7820f7414bd3bfa.
• Stage workflow 38380726060; protected npm environment approval recorded for abruption, followed by user-confirmed npm stage approval.
• Reviewed local, retained Actions and public tarball bytes match. Stage metadata SHA-1 matched the same archive; a pre-approval staged tarball download was not performed because approval occurred before that inspection step. Public raw-byte equality was independently verified afterward.
• SHA-256: 46f4a01f9570034fca49cfa5fad620f3f45b5f33b1a6714f29ea0a3c1e751ac0.
• Integrity: sha512-EJc2B5tcruzHXiHDd7tyJjv2DBLYE7IHJiPVHBzLY9fSVasEQRdwx+ZZmiyBF8WHpQ7+pI3SO2VXwsQTgOWP+Q==.
• Public provenance SHA-512 subject and source/repository/workflow/ref/event/run tuple match; npm signature audit, exact-version isolated installation/removal and 18 packaged Markdown/source byte comparisons passed.
• Exact-main CLI and CodeQL passed, including Windows Node 22/24 CI. Fixture CI is not new live-agent/observer/steering qualification. No fleet/global installation or runtime operations changes.

For this release, the operator explicitly skipped fresh Trusted Publisher mapping and package publish-MFA policy reads. Those settings are not freshly confirmed; actual protected-environment approval and final npm stage approval were not skipped. Historical permissions evidence is not reclassified as a current settings audit.

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.

v0.3.3 — SSH reliability and skill metadata compatibility

Changes

• Strict, bounded SSH response parsing rejects invalid UTF-8, duplicate JSON keys, multiple frames and oversized responses. Diagnostic stderr is decoded separately.
• Complete, request-matched Claude/Codex native submission evidence is retained after SSH exit 255 or collection timeout. Partial, malformed or oversized responses remain uncertain and never trigger an automatic resend. Submitted/queued/posted does not mean consumption or ACK.
• Bounded skill metadata inspection checks file type, read size, observable file stability and the limited metadata grammar. Runtime 0.3.3 accepts the explicitly reviewed legacy and successor profiles; compatible is metadata-only evidence.
• Updated migration and four-language documentation describe the Python/TypeScript contract differences and current SSH return-route behavior.

Upgrade and limitations

Install with npm install --global session-peer@0.3.3 through your existing package manager.

SSH requires the same TypeScript client version at both ends: 0.3.2 and 0.3.3 refuse each other at preflight. Coordinate endpoint upgrades. Windows jump-host support (#20) and remote provisioning limitations (#23) remain open. No 0.4 handoff/ACK implementation, automatic deployment or companion skill publication is included. Skill metadata/pin rollout remains a separate task (#118).

Publication evidence — 2026-10-09

• Source: c0ed30273b9e9c0049df86ae3c38486a94289527.
• Published package: session-peer@0.3.3; latest=0.3.3, preview=0.1.0-preview.1 unchanged.
• Release workflow 37907833518, protected environment approval and final npm 2FA approval completed. No protection bypass or upload retry.
• Actions, staged and downloaded public tarball bytes match. SHA-256: 3469cda6a7b2c89d42ed2a250d2e7b5b774293fee090968a4b261e824be4c075.
• Integrity, exact source/workflow provenance, npm signature audit and isolated install/uninstall verified successfully.
• Exact-main CI and CodeQL passed, including Windows native Node 22/24. Local macOS arm64 Node 24.16.0: 187 tests, 182 passed, 0 failed, 5 Windows-only skips. Fixtures do not establish live delivery/ACK or new platform qualification.

Changes: #125, #126, #127 and release preparation #129.

v0.3.2 — Remote validation and deployment documentation

Original npm publication: 2026-10-07T04:34:36.456Z (UTC). GitHub release record added afterward on 2026-10-07 (KST).

Changes since 0.3.1

• Document Windows SSH destination qualification and explicit, isolated remote provisioning, including remaining validation gaps (#111, #112).
• Reconcile deployment guidance and publication evidence. Runtime code changes are limited to the version marker; no 0.4.0 handoff, ACK, or app-server drafts are included.

Compatibility and validation scope

SSH endpoints must both run 0.3.2. Windows destination qualification used published 0.3.1 on Windows 10 x64, PowerShell 5.1 and Node 24.16.0; it is not a 0.3.2 live-message or ACK test. Windows-client jump (#20), remaining deployment qualification/design work (#23), and fleet upgrades remain outside this release record.

Exact-source CLI CI and CodeQL passed. Actions, staged and public npm tarballs were byte-identical. Integrity/provenance, npm signature audit, and fresh isolated installation/removal were verified. Fresh Trusted Publisher permission and package MFA policy reads were skipped under an explicit operator exception; successful staging/publication does not prove those settings were freshly inspected.

Published package and source

• Package: session-peer@0.3.2.
• Tag source: f335f07352c842f2f6ceb12bd2ca6274b52f69f7, matching npm provenance.
• Publication workflow; npm attestations.
• SHA-256: a1ded0c99765f25d0570aa8a38e2ccf0c1c4760b3e25de2b1f20f56061b90540.
• Public validation record.

npm install --global --ignore-scripts session-peer@0.3.2

posted/queued report submission, not consumption or ACK. Do not automatically resend an unknown outcome.

Full changelog: v0.3.1...v0.3.2

v0.3.1 — Reliability fixes and community contributions

Retrospective GitHub release record added on 2026-10-05 (KST).
Original npm publication: 2026-10-04T14:32:10.826Z (UTC).

Fixes since 0.3.0

• Preserve outcomes per host when SSH send responses are malformed; accept unnamed Claude PID targets with name:null for dry-run/send and JSON/text results (#95, #97).
• Parse Codex sqlite_home with TOML semantics, including escaped root keys. Nested-only keys are not root overrides; inactive opt-in does not bypass the storage guard (#96).
• Reject reserved Codex/nested-URI prefixes in Claude Reply-To routes and block unresolved nested URI transport at the wire receiver before SSH/queue execution (#101).
• Bound Claude registry metadata reads; skip unsafe, oversized or invalid records while preserving healthy sessions, with POSIX FIFO/race coverage (#102).
• Accept a verified numeric UID 0 writer identity and continue refusing missing/malformed/mismatched identities (#103).
• Include the multi-host migration documentation correction missing from the 0.3.0 archive (#91).

New Contributors

Welcome and thank you to @rupayon123 for their first contributions to this repository:

• #95: per-host SSH result isolation and nullable Claude target-name handling.
• #96: TOML-aware Codex sqlite_home detection.

Compatibility and verification

SSH endpoints must both run 0.3.1. Existing Windows-client jump, deployment and update-notice validation limitations remain; no live-agent ACK or fleet upgrade is added by this patch.

Exact-source CI/CodeQL passed. The authenticated stage, Actions artifact, exact-source local pack and public package are byte-identical (190,315 bytes; SHA-256 ba8b85b03229bc99ca30d52251790d7e75b90551de924b99edce22570f7fa401). Provenance binds the source/workflow/run below; signature audit and fresh public installation/removal passed.

Published package and source

• Package: session-peer@0.3.1.
• Tag source: 6b48092a0e42992d2d970dd2ff5cf457f62d3ff2, verified against npm provenance.
• Publication workflow record; npm attestation metadata.
• Integrity: sha512-iZq06dbm6NavHuPZYMIxAnzQN5ksqm66yufpppddVWUYkuaG5TJvktbUXTSX7v3BBFnuybEJekI0KSaDo3Xfbg==.
• Dated validation record.

npm install --global --ignore-scripts session-peer@0.3.1

posted/queued report submission, not consumption or ACK. An unknown outcome is not safe to retry automatically.

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.0

posted/queued report submission, not consumption or ACK. An unknown outcome is not safe to retry automatically.

v0.2.1 — Reliability and hardening

Retrospective GitHub release record added on 2026-10-05 (KST).
Original npm publication: 2026-09-28T23:45:16.923Z (UTC).

Fixes since 0.2.0

• Preserve message bodies starting with a dash by passing one native --message= argument; remove inherited CODEX_SQLITE_HOME and refuse detected relocated sqlite_home configurations (#49, #50).
• Refuse option-name tokens used as option values; preserve verified remote exit codes; require absolute Reply-To codexHome paths (#51–#53).
• Escape bidi/zero-width controls in text output and accept an exact successful SSH version preflight despite unrelated stderr (#54, #55).
• Harden PowerShell quoting; explicitly refuse unsupported Windows .cmd/.bat Codex shims instead of shell-interpreting messages (#56, #57).
• Replace quadratic envelope trimming and increase the Windows compiling owner-inspection deadline while retaining conservative timeout refusals (#59, #64–#66).
• Add weekly dependency/signature auditing (#58, #63).

Compatibility

These are stricter refusals within the existing CLI/transport contract. Use native codex.exe on Windows; doctor reports batch shims as unsupported. SSH endpoints must both run 0.2.1. No self-update, new transport, consumption confirmation or automatic retry is introduced.

Escaped TOML root-key detection is strengthened separately in 0.3.1.

Published package and source

• Package: session-peer@0.2.1.
• Tag source: a9c42334da8f7faf83f0b9bb1fe52f1c695dfe8d, verified against npm provenance.
• Publication workflow record; npm attestation metadata.
• Integrity: sha512-bPjriJZf7OQ5niZafwxNgMYo0DVpZldELEjp640xAfBMjBCAJatT2hPMTG9oV7xDX2ULCPUmox9+vFWc5nw0Mg==.
• Dated validation record.

npm install --global --ignore-scripts session-peer@0.2.1

posted/queued report submission, not consumption or ACK. An unknown outcome is not safe to retry automatically.