Merge pull request #46 from runcycles/chore/runcycles-0.5.0

chore: raise runcycles dependency floor to >=0.5.0

Author: amavashev

AUDIT.md

@@ -3,11 +3,21 @@
 **Date:** 2026-05-10
 **Package:** `langchain-runcycles` v0.2.3
 **LangChain target:** `langchain >= 1.0, < 2.0`, `langchain-core >= 1.0, < 2.0` (tested against `langchain==1.2.18`, `langchain-core==1.3.3`, `langgraph==1.1.10`)
-**Cycles SDK target:** `runcycles >= 0.4.1` (tested against `runcycles==0.4.1`, Python 3.10–3.14)
+**Cycles SDK target:** `runcycles >= 0.5.0` (tested against `runcycles==0.5.0`, Python 3.10–3.14)
 **Server audit:** Cycles protocol conformance is owned by [`cycles-client-python/AUDIT.md`](https://github.com/runcycles/cycles-client-python/blob/main/AUDIT.md). This document audits this package's contract with the LangChain agent middleware API only.
 
 ---
 
+## 2026-07-27 — runcycles floor raised to 0.5.0
+
+`pyproject.toml` raises the `runcycles` dependency floor from `>=0.4.1` to
+`>=0.5.0` (durable commit retries: on-disk journal with replay, POST
+`/v1/events` fallback for expired commits, 429/auth handling that never
+releases spent budget). Dependency-floor change only — no middleware code
+changes; the gates call `commit_reservation` directly, so the SDK's new retry
+engine is not yet engaged here (recommended follow-up). Full suite passed
+against `runcycles==0.5.0`: 174 tests, 99.63% coverage (gate 95%).
+
 ## 2026-07-26 — publishing and security-workflow maintenance
 
 Dependabot PRs #39–#43 update OSSF Scorecard to 2.4.4, the SHA-pinned CodeQL

CHANGELOG.md

@@ -7,6 +7,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Changed
+
+- **`runcycles` dependency floor raised from `>=0.4.1` to `>=0.5.0`.**
+  runcycles 0.5.0 ships durable commit retries (on-disk journal with replay,
+  POST `/v1/events` fallback for expired commits, and 429/auth handling that
+  never releases spent budget). No middleware code changes: both gates call
+  `commit_reservation` directly, so commit-failure handling still follows
+  `settlement_error_policy`; adopting the SDK's commit retry engine for
+  transient settlement failures is a recommended follow-up.
+
 ## [0.3.0] - 2026-05-15
 
 Tool-side actual-cost extraction for `CyclesToolGate` — closes the final "commits at estimate" gap documented after the v0.2.0 model-gate `cost_fn` work.

pyproject.toml

@@ -51,7 +51,7 @@ classifiers = [
     "Typing :: Typed",
 ]
 dependencies = [
-    "runcycles>=0.4.1",
+    "runcycles>=0.5.0",
     "langchain>=1.0,<2.0",
     # Tightened from `>=0.3` per external review — langchain 1.x always pulls
     # langchain-core 1.x transitively; pinning this explicitly avoids a stale