clio-relay 1.5.9

Adds relay-backed native FastMCP 4 task protocol support for SEP-2663.

• Projects existing relay jobs as standard MCP tasks over authenticated streamable HTTP and stdio.
• Preserves relay task identity, lifecycle, replay, reconnect, terminal results, and explicit cancellation.
• Keeps the relay queue as the sole execution and durability authority; FastMCP's Docket executor remains inactive.
• Enables task semantics for the trusted virtual JARVIS MCP tools.
• Gates locked MCP launcher startup on verified cache lifecycle events.

Published release

• Release: https://github.com/iowarp/clio-relay/releases/tag/v1.5.9
• Product commit: ac0e7661f4b0bd390068cb2bbf22f2aaddc771d4
• Merged PR: #141
• Full pre-release CI: https://github.com/iowarp/clio-relay/actions/runs/30489159709
• Release-tag validation: https://github.com/iowarp/clio-relay/actions/runs/30493266384
• Full post-release tag matrix: https://github.com/iowarp/clio-relay/actions/runs/30493266349
• PyPI: https://pypi.org/project/clio-relay/1.5.9/
• Reviewed evidence bundle: https://github.com/JaimeCernuda/cc_dispatch/tree/39a9ce815e94d03424129a36a36bbc80ab34658d/mcp_ui_sciences/evidence/fastmcp-sep2663
• Published wheel asset ID: 494557250
• Published wheel SHA-256: 70f5e450935cb6cf9f17a3e6eed0bcfb5ee245fcbd45c678774a9e6f0dda1a5e

released-asset-attestation.json binds the downloaded wheel, source archive, and
checksum manifest to their public GitHub release assets and the exact product
commit. released-wheel-attestation.json proves the isolated runtime imported
version 1.5.9 from that downloaded wheel, exposed the
io.modelcontextprotocol/tasks extension, and had no Docket executor.
PyPI serves the same wheel and source archive sizes and SHA-256 digests as the
public GitHub Release assets.

Released-wheel live acceptance

The official FastMCP client-only package drove the downloaded public wheel over
real authenticated streamable HTTP and stdio. The recorded run passed:

• SEP-2663 discovery over HTTP and stdio, with anonymous HTTP rejected as 401.
• A real Ares-backed task, client detach, reconstruction by a new client, and
  successful completion under the same relay task identity.
• Six immutable relay-owned artifact records attached to the terminal result.
• A separate task submitted to an isolated relay queue, client detach,
  standards-based cancellation, and canonical convergence to cancelled under
  the same task identity.
• Relay as the only execution and durability authority throughout the run.

The machine-readable results are in released-live-report-v1.5.9.json and
recordings/released-v1.5.9/recording-report.json.

The reviewed recording is
recordings/released-v1.5.9/released-live-acceptance.webm:

• VP8 WebM, 1440 by 1000, 25 fps, 211.96 seconds.
• 16,460,518 bytes.
• SHA-256: a80d81d743f0a363bf176186daec16a659c268e71f4f0ef7b5c87c5d286dbe03.

All five captured interaction states were visually reviewed. They visibly show
the released-wheel identity, inactive Docket executor, transport/auth pass,
reconnected relay task ID and artifact evidence, cancellation pass, and final
campaign state passed.