smith-agents 0.12.1 → 0.12.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d7b7df9618321378d2d66ef460c4dd085913c08d5fac47367f33b199a1fe62d3
-  data.tar.gz: f0b0eb52fd277e0666f81a90f9347e2bfb9deddfa41e530bb230b6c90f00474a
+  metadata.gz: 0a97b202bc606c58889517b16ffe906f8775d003b9386d371b63ea08dd725dff
+  data.tar.gz: 5ad614925043a70182362086dd2c03e9d3cc3bd6eea645b8d04b4e2d61b93719
 SHA512:
-  metadata.gz: 2cc72ed4a2cc6fa43d598ff5f31e4f0bc264436c72c53a8ddadf4786663d473296072016446694371b4a40aacf5602189a7b2da003f886208ef94f77d5503e0c
-  data.tar.gz: 2ce2632738c8e6c59e6f01cb16972610cf4a2fe144b4435e0e70ea00d6e29f9557330cb40c098c3058f3abcfeada3e90888c1f5eeb183c895b8297738f5227a3
+  metadata.gz: eb8e78bc96e382495c098bbb2f5e794a8efe674d5c662715d18f6d6b1b2445d2ba69198b6e447849f509f5cc58fc06ed001162f18829c485b3a1456eb843cfe0
+  data.tar.gz: 6f6112a5048ab240fe3658b6107d5e2f950945045f4518e2f07f16a72e40cb1b91a2b0ea31278df09c4fde3329132bfd5cf7dceef76040f00d5d007e01ceebea

data/CHANGELOG.md

@@ -4,6 +4,96 @@ All notable changes to Smith are documented in this file.
 
 Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). Versioning follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html). Smith is pre-1.0 and under active development; expect occasional contract tightening between minor versions until 1.0.
 
+## [0.12.3] - 2026-10-12
+
+### Changed
+
+- What identifies a request leaves prompt-cache markers out
+  (`Smith::CacheMarkers`): the response memo's key, a batch request's digest
+  and a seed's drift digest (`seed_validation`). A marker says how a request
+  is billed, never what it asks, so a host may decide call by call whether to
+  cache a part (an agent's instructions, a content part, the whole request)
+  and a replay still finds what the first call got, as long as the part keeps
+  its form (the same text block, with or without its marker). Only the places
+  Anthropic puts `cache_control` are looked at (the request, its system and
+  message blocks, a tool result's blocks, its tools) and Smith's own
+  `"cache" => true` on a seed's content parts; a tool's input or schema, or
+  anything else a request carries as data, is never touched. A batch result
+  for a request that differs from the one sent only in its markers is no
+  longer taken as a changed request.
+
+### Upgrading
+
+- Response memo records kept by 0.12.2 for calls that carried a cache marker
+  are not found after the upgrade (their key took the marker in), so such a
+  call cut by the upgrade's deploy is paid for once more. A batch request
+  captured by 0.12.2, and a run's seed digest taken by 0.12.2, still match as
+  they were taken, cache markers included: one whose markers change after the
+  upgrade counts as changed, as before.
+
+## [0.12.2] - 2026-10-12
+
+### Added
+
+- `Smith.config.interrupting_errors`: subclasses of StandardError that
+  interrupt a step instead of failing it, such as the host's database or
+  queue out of reach. A step that meets one (raised in it, a tool failure
+  handler included, or one of the first 15 causes of an error that was, never
+  through a provider's own failure) stops where it is, as if its worker had
+  stopped: no failure route, no retry, no failure recorded or emitted (a
+  deterministic step's trace says `outcome: :interrupted`), no tool failure
+  handler notified and no failed branch outcome kept. The error itself
+  reaches the caller, and wins over other branch and tool errors but a
+  process-fatal one; the stored run is as the step left it, so a lax run
+  takes the step again when next advanced. Smith does not count
+  interruptions. `Smith::Interruptions.find` answers whether an error is or
+  was raised from one. None by default.
+
+### Changed
+
+- The response memo keeps a reply that calls the tools its request offered
+  as soon as it comes, before its tools run, so a step cut inside a tool (its
+  worker stopped, or an interrupting error) no longer pays again for the reply
+  that called it: on replay that reply answers the call's first request
+  without sending it, its tools run again under the same idempotency keys,
+  and the call goes on. A streamed reply kept so keeps its stream's stop
+  reason and message id. Only such a record is version 2; every other record
+  is still version 1, and version 1 records are read. A Smith before this one
+  ignores version 2 records (paying for that reply again and running its
+  tools, as it did).
+- A request's memo digest covers its tools' descriptions and parameters, not
+  only their names, so a call kept before a tool changed is never replayed
+  against the new tool. Records for calls with tools kept by 0.12.1 are not
+  found after the upgrade (those calls are paid for again once).
+
+### Fixed
+
+- Kept tool results are charged to the agent's `tool_calls` allowance (by
+  tool, for an exact budget) and the workflow's `tool_calls` budget as they
+  were before the cut, so a replay never runs more tools than the step may.
+- A call a tool halted (`halt`) stored a complete record no replay could read
+  (it ended in the tool's result); it now keeps only its progress, which a
+  replay goes on from.
+- A memo record whose tool results do not answer the calls before them (a
+  result for no call, a call left unanswered before the next reply) is ignored instead of continued into a
+  request the provider refuses.
+- A streamed call that failed after replies a memo kept gave the kept replies
+  the stream facts (message id, stop reason) of its live rounds; each keeps
+  its own now.
+
+### Documentation
+
+- The README is a short guide now: what Smith is, installing it, a first
+  workflow, the steps, and each feature in a few lines with an example and a
+  link. Its detailed contracts moved, unchanged, into `docs/`: new
+  `AGENTS.md` (outputs, request shaping, streaming, batch mode),
+  `BUDGETS.md`, `ERRORS_AND_RETRIES.md` (with the response memo),
+  `TESTING.md` (with the doctor), `INSPECTION.md` and `DEVELOPMENT.md`; and
+  sections appended to `PERSISTENCE.md`, `TOOLS_AND_GUARDRAILS.md` and
+  `CONFIGURATION.md`. The README's examples are run by
+  `tmp/probes/readme_probe.rb`; the retries example used an undefined
+  `order`, and several examples left states undeclared.
+
 ## [0.12.1] - 2026-10-11
 
 ### Changed