Open LLM text
Share with AI
Ask Claude Ask ChatGPT Ask Gemini Ask Copilot
1 min read 244 words

0.7.1

Patch release for HTTP/1 sendfile ownership, public-contract guardrails, and benchmark proof artifacts

Highlights

  • Protocol-owned sendfile — HTTP/1 static-file sendfile framing now stays under protocol ownership, aligning range responses, streaming fallbacks, and ASGI send completion behavior.
  • Public-contract guardrails — API, config, CLI, docs, protocol status, and public claims now have stronger tests and ledgers to keep release wording tied to shipped behavior.
  • Benchmark evidence — Checked-in Bengal and Chirp local benchmark artifacts record workload, command, platform, Python build, and caveats for performance-proof traceability.
  • Release governance cleanup — Steward guidance, planning cleanup, and roadmap updates make release review expectations more explicit without changing runtime dependencies.

Added

  • Bengal and Chirp local benchmark artifacts underbenchmarks/artifacts/2026-05-22/.
  • Benchmark runner tests for artifact metadata and benchmark command behavior.
  • Public-claim and protocol-proof ledger coverage for release-facing docs.

Changed

  • pounce.run(config=...) typing now aligns with ServerConfig.
  • Public docs and README language were narrowed where proof ledgers do not support broader claims.
  • Benchmark artifact policy now records required workload, platform, command, Python build, comparison target, and caveats before public performance numbers are promoted.
  • Steward guidance now spells out release collateral, proof, and escalation expectations across runtime, docs, site, examples, benchmarks, tests, and CI.

Fixed

  • HTTP/1 sendfile response ownership now runs through protocol completion paths instead of splitting framing behavior between static-file helpers and protocol code.
  • Range responses, static streaming fallbacks, and ASGI bridge sendfile paths now share more consistent response completion semantics.

Install

uv add "bengal-pounce==0.7.1"