Skip to content

session-peer v1.4.2

Choose a tag to compare

@abruption abruption released this 05 Nov 09:45
Immutable release. Only release title and notes can be modified.
27b0887

session-peer v1.4.2

Maintenance release covering bounded test-fixture pipe waits and CI guardrails (#372), plus localized operator-guide terminology and documentation verification (#374). Runtime behavior changes only in the version value. Source: 27b088735f065b6785dc6f3892cf132926657bdf.

No new native/SSH/ACK/platform qualification or operational rollout is claimed. The compatibility skill remains separately published v0.5.1 with minimum 0.9.1/full documented coverage 1.4.0; publication does not update independently managed skills or restart services.

Verified publication

  • GitHub stable/Latest, immutable release: 2026-11-05T09:45:30Z.
  • PyPI 1.4.2: wheel uploaded 2026-11-05T09:47:52.170326Z; sdist uploaded 2026-11-05T09:47:54.295391Z. Both are non-yanked and match the locked, attested candidates.
  • Preparation run and publish/PyPI verification run succeeded. All seven asset attestations, exact manifest/provenance/source checks and fresh wheel/sdist installations passed. Required human PyPI approval was retained.
  • Wheel SHA-256: fb9a409603daeca922c325a65c7c1d164d41f517b68af9244d4fd6d806fb9317.
  • Sdist SHA-256: 98a227a6cd9e72f801ba677a453edca8b81317648af456bc6e3bd9845bb0add8.

Frozen preparation record

The dated candidate/authority statements below describe the preparation checkpoint, not current GitHub or PyPI availability. Actual publication evidence is recorded separately; existing source notes and immutable assets are not rewritten.

v1.4.2 maintenance release preparation

Prepared on 2026-11-05 against published v1.4.1 (GitHub, PyPI). At this dated checkpoint, v1.4.2 is an unpublished maintenance candidate. Integrated maintenance base: c265861d5251f8bab65229521444168e23bc13a9, before version preparation, not the final release commit. The owner requested release preparation; this does not authorize merge, tag/draft creation, workflow dispatch, publication or operational rollout.

Scope

  • PR #372 addresses #370 in the handoff watch test fixture: pipe observations have deadlines, helper output is checked before the interrupt finish window, and missing-frame/warm-up failure regressions verify bounded failure and helper cleanup. CI limits each POSIX test-matrix job to 15 minutes and its core-test step to 5 minutes, with faulthandler enabled for fatal-signal tracebacks. These are test/CI repairs, not a product runtime defect fix or proof of the cause of the original CI stall.
  • PR #374 addresses #373 across the Korean, Japanese and Simplified Chinese READMEs and operator guides. It distinguishes handoff confirmation/ACK information, persisted paired-request processing results, historical Control operation results and SSH host-key verification records; corrects related operational terms; clarifies existing English discovery/configuration descriptions; and strengthens heading-hierarchy and wrapped-inline-code checks. Existing queued/submitted, consumption and ACK boundaries are preserved.
  • Runtime behavior is unchanged apart from the version value. The frozen English handoff contract and its golden contract fixture remain unchanged; PR #372 changed the separate watch-test helper. No new feature, native/SSH delivery, Windows 3.14/free-threaded Python, consumption/ACK guarantee or platform-support qualification is claimed.
  • #316 Relay test/shutdown monitoring, #367 paired-device aggregate discovery and Long-term research remain separate. A successful rerun does not establish the cause or resolution of a historical incident.

Compatibility and independent skill

Core Python 3.9, MCP Python 3.10+ and SDK requirement mcp>=1.30,<2 are unchanged.

The prospective SKILL.md support asset remains the published skill v0.5.1, source 95cf5e1dd92654775b2f0ea86c1cb4b6107f49c3, 31688 UTF-8 bytes, SHA-256 922512869577cc3d8b9d305641479e2dd659f0e669298584ca06f1ca15de1d31. Metadata remains skill 0.5.1 / minimum runtime 0.9.1 / documented full coverage 1.4.0; receiver codexBin floor remains 1.0.1. This runtime patch does not raise those floors or release a new skill. Exact source/hash pinning does not itself assert GitHub-enforced immutability. The support skill remains outside wheel/sdist.

Existing tags, immutable assets and dated preparation/publication records are preserved. Package publication does not update independently managed skills or other global MCP environments, restart receivers or deploy Node Control services.

Publication gates

Require successful checks/reviews of the exact preparation head and final protected-main source. Any later authorized publication must verify all 7 frozen assets (including SHA256SUMS and release-provenance.json) and authenticated attestations against the exact tag/source, run current dependency audits and fresh wheel/sdist installation checks, and retain the required human PyPI environment approval. These are pending gates, not completed results claimed by this preparation. Omitting a private login/binding recheck does not waive human approval or permit a protection bypass.

Freeze these publication-neutral dated notes before a later authorized build. Record actual GitHub/PyPI publication evidence separately; do not announce publication early, reuse a version, move an existing tag or replace immutable assets. Release preparation and operational deployment are separate.