[rafaga]

Summary

Prepares release 0.2.2. It adds a way to read the response headers of an ESI call and uses it to expose the hourly kills per system together with the moment ESI computed them. It also brings the docs up to date: the changelog was missing the 0.2.1 release.

What changes

API

• Esi::query_with_headers works like query but also returns the response headers (for Last-Modified, ETag). When the answer comes from the response cache, the headers are those stored with it.
• UniverseGroup::get_system_kills_snapshot returns a SystemKillsSnapshot: the kills per system of the last hour, plus the Last-Modified and ETag of the answer.
  • ESI refreshes this answer once an hour, so Last-Modified marks the end of the hour the data covers. Two hourly answers can be told apart and stored without counting one twice.
  • With the cache enabled (EsiBuilder::enable_cache), calls made before the hour is up cost no request.
  • The existing get_system_kills is unchanged.

Tests

• tests/cache.rs: the headers survive a cached answer (a single request for two calls), and the snapshot carries Last-Modified and ETag.

Docs

• CHANGELOG.md: adds the missing 0.2.1 section (2026-10-26, dependency update) and dates 0.2.2.
• README.md: mentions query_with_headers and the snapshot.
• TODO.md: adds the 0.2.1 and 0.2.2 items to the release housekeeping.
• Cargo.toml: version 0.2.2.

Compatibility

• Additive only: no existing function, type or behavior changes. It is a patch release.
• SystemKillsSnapshot keeps the date as the string ESI sent (an HTTP date), like the rest of the crate.

Before publishing

• cargo fmt --check
• cargo clippy --all-targets -- -D warnings
• cargo test
• cargo deny check