Ops digest #916

Activity

1. github-actions

   added

   ops-digest

   on Jul 19, 2026
2. coderabbitai commented on Jul 19, 2026

   

   coderabbitaiBot

   on Jul 19, 2026 – with coderabbitai

   Last edited by coderabbitai

   Contributor

   More actions

   🔗 Related PRs

   #423 - PR 423 [merged]
   #585 - feat(observability): OpenAI answer spend snapshot on the deep health probe [merged]
   #632 - Reduce cold RAG round trips and reconcile retention controls [merged]
   #1080 - Fail readiness closed on Supabase probe errors [merged]
   #1550 - docs(issues): capture db-query-perf operator follow-ups [merged]

   ---

   📝 Issue Planner

   _{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

   • Create Plan

   ---

   🧪 Issue enrichment is currently in open beta.

   You can configure auto-planning by selecting labels in the issue_enrichment configuration.

   To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

   issue_enrichment:
     auto_enrich:
       enabled: false

   💬 Have feedback or questions? Drop into our discord!
3. BigSimmo

   added

   backlog:report

   on Sep 13, 2026
4. BigSimmo commented on Sep 13, 2026

   

   BigSimmo

   on Sep 13, 2026 – with ChatGPT Codex Connector

   Owner

   More actions

   Reporting classification — 13 September 2026

   Retained as an ongoing monitoring thread, not an unfinished development task. Added backlog:report while preserving ops-digest and the machine-generated body.

   Use is:issue is:open label:"backlog:report" for reports and is:issue is:open label:"backlog:actionable" for the six retained work/verification items. This is label-based organisation, not a new reporting workflow.

   The inspected 13 September snapshot reports readiness checks as okay but zero answered queries and OPS_ANSWER_SLO_UNKNOWN. That observation does not establish answer quality and is not by itself proof of an outage. Preserve the unknown state and investigate against expected traffic/runbook criteria when actionable.

   Future substantive findings should have separately scoped tasks or links to existing tracking. No monitoring schedule, alert threshold, production configuration or workflow was changed by this classification.
5. BigSimmo

   added 2 commits that reference this issue on Sep 17, 2026

   fix(readiness,live-drift): share the cold-start probe, and make a gre…

   ...

   4b59a58

   fix(readiness): share the cold-start probe and start the cache window…

   ...

   1c3fdfb