RELEASE NOTES

Changelog: what shipped, what changed, what is going away.

Public release notes for the connected Ruzzler beta — versioned entries, newest first, with deprecations called out ahead of their sunset dates.

v0.9.62026-07-28

Rate-card-versioned receipts and receipt export

Every settled request now returns a receipt pinned to an explicit rate-card version, so historical spend can be re-audited against the exact prices in force at execution time.

  • Receipts carry a rate-card version field on every settled request.
  • Receipt export for tenant-scoped date ranges is available from the console.
  • Verification status is displayed alongside usage on the request detail view.

Deprecation. CSV receipt export (?format=csv) sunsets on 2026-10-01. Use the JSON receipt export, which includes the rate-card version and verification status fields.

v0.9.52026-07-13

Versioned policies with an auditable acceptance trail

Terms, Privacy, and Refund policies are now versioned as a single dated release, and every acceptance is recorded against the exact text the user agreed to.

  • Policy version 2026-07-13 published across Terms, Privacy, and Refund.
  • Signup and newsletter consent record the policy version at acceptance time.
  • Prior acceptances remain auditable against the text that was in force.
v0.9.42026-06-30

Cumulative-budget checks and abstention release

The connected request path now applies cumulative-budget checks in addition to per-request rate checks, and releases reservations in full when the pipeline abstains unverified.

  • Cumulative-budget checks run before execution alongside rate checks.
  • Unverified abstention releases the full reservation — zero charge, as tested.
  • Budget state is visible per project in the console.
v0.9.32026-06-12

OpenAI-compatible endpoint for supported text workflows

Supported text workflows can be submitted through an OpenAI-compatible governed execution API, with tenant scope applied server-side and provider credentials remaining server-managed.

  • OpenAI-compatible request shape for supported text workflows.
  • Tenant scope, rate checks, and request status returned on the connected path.
  • Server-managed provider credentials; no customer-side provider accounts required.

Deprecation. Legacy batch submission endpoint sunsets on 2026-09-15. Move batch workloads to the governed execution API; per-request receipts replace the batch summary report.

v0.9.22026-05-29

Public status monitor

The operational status of the connected beta path is now published on a public monitor, including current component state and incident history.

  • Public status page for the request path, console, and billing pipeline.
  • Incident entries record start, resolution, and affected components.
  • The marketing footer links to live status.

Building against the beta?

The quickstart covers the current request shape and receipt fields; deprecations always ship with a migration path.