epochly-relay-cli
The rly command-line interface for the Relay agent reliability OS.
This package ships the public Apache 2.0 control surface declared in spec
section P (CLI inventory + contract). The W5 milestone (sub-features w5.1
through w5.5) wires the CLI onto the Python SDK (epochly-relay), the
canonical schemas (epochly-relay-schemas), and the local sidecar
(epochly-relay-sidecar).
Installation (development)
uv sync --all-packages
uv pip install -e packages/cli
After install, rly --version prints version JSON to a piped stdout and a
human-readable form to a TTY. Exit code is always 0 on success.
Why JSON-by-default
Relay is a control-plane CLI consumed by CI runners, gate engines,
auditors, and other automation. Spec section P pins the rule that piped
stdout is machine-parsable JSON; TTY stdout is permitted to render
human-readable text. This package implements the rule via
sys.stdout.isatty() detection at output emit time.
Why Typer + Click pinned to exact versions
Per VAL-W5-002 (eng plan CQ3), Typer and Click are pinned with the exact
operator (==) rather than a range. The CLI's stdout-JSON contract and
cross-shell snapshot fixtures depend on Typer's command dispatch and
--help rendering; an upstream version bump would invalidate the
snapshots. Bumping Typer or Click is a deliberate W5 maintenance feature,
not an unattended dependency upgrade.
Process safety
Per CLAUDE.md keystone invariant #3 and .ops/manifest.yaml, sidecar
lifecycle commands (rly sidecar start|stop|restart|status) read PID and
port from ~/.relay/sidecar.lock and never invoke kill-by-name primitives
(pkill, killall). The full lifecycle implementation lands in W5.2.
Banned product copy
This package and every customer-facing surface produced by its
distribution pipeline (PyPI long_description, npm description, release
notes, embedded sidecar binary string resources) is scrubbed of the
banned tokens enumerated in CLAUDE.md (banned pattern #9, spec J.5).
The scripts/lint-banned-product-copy.py lint runs in tier-1 plumbing
and fails CI on any match.
Metadata
Release files for epochly-relay-cli 0.1.20
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| epochly_relay_cli-0.1.20.tar.gz | 130.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| epochly_relay_cli-0.1.20-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 288.4 kB
Release files / epochly_relay_cli-0.1.20.tar.gz
| Download URL | epochly_relay_cli-0.1.20.tar.gz |
|---|---|
| Size | 130.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
24a636adb5d32da3deaec2d55f8833a29e143b3df8bfc7d5385e4d003a710d50
|
|
BLAKE2b-256 checksum How to use checksums |
7dce8efc818c51a33e9a9f917da53e9fb6b1f78f29d42e568acca1e8e761a7f5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 28, 2026.
Transparency logRelease files / epochly_relay_cli-0.1.20-py3-none-any.whl
| Download URL | epochly_relay_cli-0.1.20-py3-none-any.whl |
|---|---|
| Size | 158.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9b65a75f225d495e48dd8f28b6d9f4df9420d5f5424f88e4fb0faa4d9cdb79ba
|
|
BLAKE2b-256 checksum How to use checksums |
7d29a7e35ec7dd5216a7b0c1762f107df42e7f625ccede1e4d792711dc3e2cce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 28, 2026.
Transparency log