release: 0.21.10

Author: Yogthos

CHANGELOG.md

@@ -4,7 +4,7 @@ All notable changes to dirge are documented here. The format follows
 [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) and the project
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased]
+## [0.21.10] - 2026-08-07
 
 ### Fixed
 - Prompt compression no longer windows source files or the user's own messages.
@@ -53,9 +53,10 @@ adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
   JSX component (32.8 KB) the model kept the first of three edit targets and
   lost the other two. Because the capping is deterministic, re-reading returns
   the same cut view — hence the re-read loop, and the model eventually
-  shelling out to `bash`/python to read the file. File excerpts now get
-  `FILE_EXCERPT_RESULT_CAP_TOKENS` (12000); the aggressive tier still overrides
-  it, since a roomier allowance is worth nothing if the request stops fitting.
+  shelling out to `bash`/python to read the file. File excerpts now get their
+  own cap (`file_excerpt_cap_tokens`, default 12000); the aggressive tier still
+  overrides it, since a roomier allowance is worth nothing if the request stops
+  fitting.
 
   The truncation marker told the model to "call the tool with a narrower scope
   (filter, head, pagination)" — which for a `read` is what it already did. For

Cargo.lock

@@ -3,7 +3,7 @@
 # taken on crates.io. The installed BINARY is still `dirge` (see [[bin]]),
 # so users run: `cargo install dirge-agent` then the `dirge` command.
 name = "dirge-agent"
-version = "0.21.9"
+version = "0.21.10"
 edition = "2024"
 # MSRV: edition 2024 needs 1.85, but the dependency tree (time, serde_with,
 # darling, instability) requires 1.88 — pin there so older toolchains fail

Cargo.toml

@@ -242,7 +242,7 @@ them on:
 |-----|---------|-----------------|
 | `trim_user_text` | `false` | Let windowing touch your own messages too. |
 | `window_code` | `false` | Let windowing fold and window code and file excerpts. |
-| `header` | `"explicit"` | `"legacy"` restores the pre-0.22 elision-header wording. |
+| `header` | `"explicit"` | `"legacy"` restores the pre-0.21.10 elision-header wording. |
 | `verbatim` | `true` | `false` ignores `read(verbatim=true)`'s compression opt-out. |
 
 If you need a guarantee that what you are looking at is byte-for-byte what is