feat(evaluation): write regressions, budget checks, site changes and comparisons (#8) #10

Merged
KofTwentyTwo merged 2 commits from feature/regressions-budgets into develop 2026-10-14 16:03:58 +00:00
2 Commits
Author SHA1 Message Date
james.maes e8d226bd69 Merge remote-tracking branch 'origin/develop' into feature/regressions-budgets
# Conflicts:
#	src/main/java/com/kingsrook/qbits/webperf/metadata/WebPerfMetaData.java
2026-10-14 11:01:38 -05:00
james.maesandClaude Opus 5.5 0745f331f4 feat(evaluation): write regressions, budget checks, site changes and comparisons
The regression, budget, change event and comparison tables had list
screens but nothing wrote them; the open regression count was a
hard-coded 0 and budgets were never evaluated.

- Change events: new build ids from the DeployProbe and ChangeEventSource
  events become durable, idempotent change_event rows (event_key);
  lab runs record the deployment (change event) and CDN stage.
- Budgets are evaluated after lab runs and field imports; breaches open
  or refresh regressions.
- Regression detection compares new results with the baseline per page,
  strategy and metric as the design describes, links the likely change,
  confirms before opening, and resolves on recovery. The open regression
  count is real.
- Before/after comparisons are written per change event.
- Dismiss and Mark resolved are standard record actions on regressions.
- Optional alerts through core QAlerts (logging sink without the Alerts
  qbit). QQQ BOM moves to the released 4.1.0-RC.6 for core alerts.
- Changeset 11 adds the progress and identity columns.

Refs #8

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-14 11:00:41 -05:00