session-peer v1.0.0-beta.1

session-peer v1.0.0-beta.1

The first 1.0 beta advances the authenticated relay toward a stable contract
while preserving the dependency-free local and SSH workflows.

Highlights

• Freeze the v1 compatibility contract for reply URIs, JSON results, relay and
  control protocols, backup manifests, migrations and deprecation policy.
• Replace implicit control database setup with ordered, transactional first-party
  migrations and backup metadata that records the applied schema revision.
• Expose bounded relay capacity, admission rejection and rate-limit metrics
  without user, device, token, session or message identifiers.
• Support WSL relay receivers that explicitly target native Windows Codex while
  preserving receiving-side policy and ownership checks.
• Reorganize reusable deployment examples and operator-only artifacts so the
  source distribution excludes private operational configuration.

Install the beta

Python package managers do not normally select prereleases. Opt in explicitly:

pipx install 'session-peer[relay]==1.0.0b1'
# or
uv tool install 'session-peer[relay]==1.0.0b1'

Use the same package version on both paired endpoints. The core supports Python
3.9+; the optional relay runtime requires Unix or WSL and Python 3.11+.

• Project overview
• Paired-device guide
• v1 compatibility contract
• Security policy

Beta boundaries

• This is a prerelease for explicit testers. Normal stable upgrades continue to
  select v0.9.1.
• Hosted relay availability and OAuth provider policy remain operational
  services separate from package publication.
• WSL support covers a Unix relay receiver targeting native Windows Codex; the
  receiver and optional relay runtime do not run natively on Windows.
• Control migrations are forward-only. Back up persistent state and follow the
  documented compatibility contract before upgrading or rolling back.
• Pairing and OAuth never grant native agent access by themselves. The receiving
  endpoint still enforces local policy and users verify the actual agent result.

Report bugs through GitHub issues and security problems through the repository's
private advisory channel. Do not include tokens, device keys, certificates,
session IDs or conversation content in reports.