feat(calibration): nightly config-drift sentinel — stale config becomes a push alert#8261
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
loopover-ui | b976a54 | Commit Preview URL Branch Preview URL |
Jul 23 2026, 04:09 PM |
Contributor
|
Superagent didn't find any vulnerabilities or security issues in this PR. |
…es a push alert (#8213) Epic #8211 track A capstone wiring over the contributor-delivered evaluator (#8212): on the calibration tick, behind its own default-off CONFIG_DRIFT_SENTINEL_ENABLED var, replay each live knob's CURRENT value against the trailing corpus and alert when a TIGHTER alternative (or a revert to shipped) Pareto-dominates it — the stale-config wrongness the Looser-dominating findings are suppressed (the loosening loop owns that direction). One alert per episode via a system_flags fingerprint: standing drifts never re-alert, changed drifts do, recovery clears. ALERT-ONLY — the sentinel never writes a knob value. The knobs status endpoint now computes each knob's current drift report on read, deliberately not flag-gated: a standing drift is visible even while the sentinel is off. Docs section added; 100% line+branch on the module including the non-Error alert-formatter arm and the report-only-knob skip. Closes #8213
JSONbored
force-pushed
the
feat/config-drift-sentinel
branch
from
July 23, 2026 16:05
3b29d2f to
b976a54
Compare
Bundle ReportChanges will increase total bundle size by 2.44kB (0.03%) ⬆️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: loopover-uiAssets Changed:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8261 +/- ##
==========================================
- Coverage 92.14% 92.14% -0.01%
==========================================
Files 785 785
Lines 78728 78764 +36
Branches 23760 23771 +11
==========================================
+ Hits 72544 72576 +32
Misses 5062 5062
- Partials 1122 1126 +4
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Epic #8211 track A capstone (#8213), wired over the contributor-delivered evaluator (#8212): stale configuration — measured by the #8170 retro analysis as the operator's largest wrongness source — becomes a push notification instead of a discovery-through-frustration.
How
CONFIG_DRIFT_SENTINEL_ENABLEDvar: replay each live knob's CURRENT value against the trailing corpus (evaluateKnobDrift— same splits, same Pareto floor, same never-on-noise minimums) and alert when a tighter alternative or a revert to shipped dominates it. Looser-dominating findings are suppressed — the loosening loop owns that direction.system_flagsfingerprint: a standing unchanged drift never re-alerts, a changed one does, recovery clears the episode. Same Workers-Logs + Sentry notify path and per-knobevdiscipline as the loosening alerts.Validation
Full
npm run test:cigreen (TEST_CI_EXIT=0, zero failed files); 100% line+branch on the module — episode lifecycle (alert → standing → recovery → re-alert), looser suppression with stale-fingerprint cleanup, empty-corpus clean, per-knob fail-safe incl. the non-Error formatter arm, report-only-knob skip, and dispatch wiring both flag states.Closes #8213