chore(observability): daily snapshot + trends refresh

[github-actions]

Automated daily observability snapshot generated by
docs-observability-snapshot.yml. Includes today's JSON
snapshot under docs/observability/snapshots/ and a
re-rendered docs/observability/trends.md covering the
last 30 days.

Summary by Sourcery

Update observability documentation with the latest daily snapshot and refreshed 30-day trends.

Documentation:

• Refresh observability trends window, metrics, and sparklines to include data through 2026-06-26.

Chores:

• Add the 2026-06-26 JSON observability snapshot to the snapshots directory.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Automated daily observability snapshot update: adds a new JSON snapshot for 2026-06-26 and refreshes the 30‑day observability trends markdown, updating the reporting window, sparkline glyphs, and metric values accordingly.

File-Level Changes

Change	Details	Files
Refresh observability trends markdown to reflect the latest 30‑day window and metrics.	Update the reporting window dates and day-count summary in the trends header to include the latest snapshot date. Regenerate sparkline glyphs for coverage and quality metrics to include the new data point and correct spacing. Update tabular metric values (first, latest, min, max) where the latest snapshot changes them, particularly for alert-related metrics.	docs/observability/trends.md
Add the latest daily observability JSON snapshot produced by the automation.	Create a new dated JSON snapshot file capturing the current observability metrics for 2026-06-26 under the snapshots directory. Ensure the snapshot file name follows the existing YYYY-MM-DD.json convention used by the observability snapshot pipeline.	docs/observability/snapshots/2026-06-26.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[github-actions]

Review-bot acknowledgement summary

• Must-address findings: 0 (0 acknowledged, 0 open)
• Informational findings: 0

All must-address findings are resolved or acknowledged.

[sourcery-ai]

Hey - I've left some high level feedback:

• The _Window: 2026-05-22 -> 2026-06-26 (3 day(s); target 30)_ line appears inconsistent with the date range (which spans more than 3 days); it may be worth checking the generator logic that computes and renders the day count.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The `_Window: 2026-05-22 -> 2026-06-26 (3 day(s); target 30)_` line appears inconsistent with the date range (which spans more than 3 days); it may be worth checking the generator logic that computes and renders the day count.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}