Eval canary regression: nightly golden eval failed

[github-actions]

Nightly eval canary failed on 2026-07-13T19:20:05.795Z.

Run: https://github.com/BigSimmo/Database/actions/runs/29277341469

Triage order (docs/observability-slos.md §3): rerun via workflow_dispatch,
check hybrid_rpc_errors and npm run check:indexing, then bisect code.
A failure can be corpus-state-dependent — confirm before reverting anything.

[coderabbitai]

🔗 Related PRs

#423 - PR 423 [merged]
#437 - fix(ci): unblock deployment boot smoke and pace eval canary [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!

[github-actions]

Dispatched eval canary failed on 2026-08-17T14:27:22.714Z.

Run: https://github.com/BigSimmo/Database/actions/runs/32038751592

Failure class: environment-or-timeout (medium)
Reason: Timeout or runtime process failure; inspect active processes and artifacts.
Step outcomes: {"checkout":"success","preflight":"success","setup_node":"success","install":"success","validate_override":"skipped","project_guard":"success","golden_retrieval":"success","answer_quality":"failure","answer_targeting":"skipped"}

Triage order (docs/observability-slos.md §3): inspect the failed step first.
Resolve provider quota/auth/config failures before rerunning; for completed evals,
check hybrid_rpc_errors and npm run check:indexing, then investigate corpus or code drift.
Do not bisect or revert code until provider health and the failure class are confirmed.

[github-actions]

Dispatched eval canary failed on 2026-08-18T04:12:51.060Z.

Run: https://github.com/BigSimmo/Database/actions/runs/32097916649

Failure class: environment-or-timeout (medium)
Reason: Timeout or runtime process failure; inspect active processes and artifacts.
Step outcomes: {"checkout":"success","preflight":"success","setup_node":"success","install":"success","validate_override":"skipped","project_guard":"success","golden_retrieval":"success","answer_quality":"failure","answer_targeting":"skipped"}

Triage order (docs/observability-slos.md §3): inspect the failed step first.
Resolve provider quota/auth/config failures before rerunning; for completed evals,
check hybrid_rpc_errors and npm run check:indexing, then investigate corpus or code drift.
Do not bisect or revert code until provider health and the failure class are confirmed.

[github-actions]

Dispatched eval canary failed on 2026-08-22T18:07:13.773Z.

Run: https://github.com/BigSimmo/Database/actions/runs/32589154243

Failure class: environment-or-timeout (medium)
Reason: Timeout or runtime process failure; inspect active processes and artifacts.
Step outcomes: {"checkout":"success","preflight":"success","setup_node":"success","install":"success","validate_override":"skipped","project_guard":"success","golden_retrieval":"success","answer_quality":"failure","answer_targeting":"success"}

Triage order (docs/observability-slos.md §3): inspect the failed step first.
Resolve provider quota/auth/config failures before rerunning; for completed evals,
check hybrid_rpc_errors and npm run check:indexing, then investigate corpus or code drift.
Do not bisect or revert code until provider health and the failure class are confirmed.

[github-actions]

Weekly (scheduled) eval canary failed on 2026-08-23T18:12:03.076Z.

Run: https://github.com/BigSimmo/Database/actions/runs/32656925301

Failure class: environment-or-timeout (medium)
Reason: Timeout or runtime process failure; inspect active processes and artifacts.
Step outcomes: {"checkout":"success","preflight":"success","setup_node":"success","install":"success","validate_override":"skipped","project_guard":"success","golden_retrieval":"success","answer_quality":"failure","answer_targeting":"skipped"}

Triage order (docs/observability-slos.md §3): inspect the failed step first.
Resolve provider quota/auth/config failures before rerunning; for completed evals,
check hybrid_rpc_errors and npm run check:indexing, then investigate corpus or code drift.
Do not bisect or revert code until provider health and the failure class are confirmed.

[github-actions]

Weekly (scheduled) eval canary failed on 2026-08-30T18:18:27.849Z.

Run: https://github.com/BigSimmo/Database/actions/runs/33327352850

Failure class: probable-regression (high)
Reason: A completed answer-quality evaluation reported blocking threshold failures.
Step outcomes: {"checkout":"success","preflight":"success","setup_node":"success","install":"success","validate_override":"skipped","project_guard":"success","golden_retrieval":"success","answer_quality":"failure","answer_targeting":"skipped"}

Triage order (docs/observability-slos.md §3): inspect the failed step first.
Resolve provider quota/auth/config failures before rerunning; for completed evals,
check hybrid_rpc_errors and npm run check:indexing, then investigate corpus or code drift.
Do not bisect or revert code until provider health and the failure class are confirmed.

[github-actions]

Dispatched eval canary failed on 2026-09-02T02:25:05.958Z.

Run: https://github.com/BigSimmo/Database/actions/runs/33582708071

Failure class: probable-regression (high)
Reason: A completed answer-quality evaluation reported blocking threshold failures.
Step outcomes: {"checkout":"success","preflight":"success","setup_node":"success","install":"success","validate_override":"skipped","project_guard":"success","golden_retrieval":"success","answer_quality":"failure","answer_targeting":"skipped"}

Triage order (docs/observability-slos.md §3): inspect the failed step first.
Resolve provider quota/auth/config failures before rerunning; for completed evals,
check hybrid_rpc_errors and npm run check:indexing, then investigate corpus or code drift.
Do not bisect or revert code until provider health and the failure class are confirmed.

[github-actions]

Weekly (scheduled) eval canary failed on 2026-09-06T18:18:49.569Z.

Run: https://github.com/BigSimmo/Database/actions/runs/34050934409

Failure class: probable-regression (high)
Reason: A completed answer-quality evaluation reported blocking threshold failures.
Step outcomes: {"checkout":"success","preflight":"success","setup_node":"success","install":"success","validate_override":"skipped","project_guard":"success","golden_retrieval":"success","answer_quality":"failure","answer_targeting":"skipped"}

Triage order (docs/observability-slos.md §3): inspect the failed step first.
Resolve provider quota/auth/config failures before rerunning; for completed evals,
check hybrid_rpc_errors and npm run check:indexing, then investigate corpus or code drift.
Do not bisect or revert code until provider health and the failure class are confirmed.