Skip to content

fix(lifecycle): park no-baseline drift scores; optional GCP auth for drift-check - #591

Merged
Pigbibi merged 1 commit into
mainfrom
feat/park-score-without-baseline
Sep 7, 2026
Merged

fix(lifecycle): park no-baseline drift scores; optional GCP auth for drift-check#591
Pigbibi merged 1 commit into
mainfrom
feat/park-score-without-baseline

Conversation

@Pigbibi

@Pigbibi Pigbibi commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

Summary

  • resolve_injected_drift_score / production_drift_status_from_result omit scores when baseline_available=False (no-baseline 0.0 must not look healthy for Policy A).
  • reusable-drift-check.yml: optional GCP WIF inputs; if bucket set without WIF, clear bucket env and stay local-only (avoid hard-fail / silent non-persist confusion).

Test plan

  • pytest tests/test_production_drift_score_resolve.py tests/test_production_drift_new_risk.py tests/test_production_drift_health_probe.py
  • CI green
  • Follow-up: configure UES GCP_WORKLOAD_* vars + pin this SHA; soxl/russell still need BacktestOrchestrator baselines before store has real scores

Made with Cursor

Treat baseline_available=False as unavailable for NEW_RISK inject so
no-baseline 0.0 HEALTHY cannot pass as clean. Gate reusable drift-check
cloud writes behind optional WIF inputs; without them keep local-only.

Co-Authored-By: Claude <noreply@anthropic.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@Pigbibi
Pigbibi merged commit bc91e88 into main Sep 7, 2026
1 check passed
@Pigbibi
Pigbibi deleted the feat/park-score-without-baseline branch September 7, 2026 18:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant