# Release-artifact waivers (#356) — read by scripts/check_release_artifacts.sh.
#
# The release gate fails when a version-stamped derived artifact (the benchmark
# baseline or the blind-eval snapshot) isn't stamped for the release being cut.
# If an artifact genuinely can't be refreshed for a release (e.g. a CI/docs-only
# release with no perf or tool-surface change), record a waiver here instead of
# refreshing — so the skip is deliberate and tracked, never silent.
#
# Format (one per waived artifact):
#   v<version> <benchmark|eval> #<issue> <reason>
# Example:
#   v0.10.2 benchmark #999 CI-only release; no perf-relevant change
#
# Entries are per-release; prune old ones freely. See
# docs/guides/RELEASE_ARTIFACTS.md.

v0.10.1 benchmark #354 maintenance release; only runtime change (#341 IMAP login resolution) touches no benchmarked hot path, so numbers would reproduce
v0.10.1 eval #355 maintenance release; tool surface unchanged (still 24 tools), so blind-eval scores would reproduce
