Repository navigation
feat(governance): stale-baseline warning — surface baseline age (F7) - #26
Merged
Merged
Conversation
- staleness.py: check_baseline_staleness() — file mtime age vs threshold, advisory only, missing files are load errors not staleness - CLI diff: --stale-days flag + [cli] stale_baseline_days config (default 30); --explain prints re-record suggestion when the baseline crosses the line - Docs: 'Stale baselines' section in Configuration guide, README flag - 5 new tests (344 total)
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
With
--explain, AgentDiff warns when the baseline file is older thanstale_baseline_days(default 30, flag--stale-days, config[cli] stale_baseline_days):Why
F7 (0.4.0 Honest Gate). Thresholds aren't the only thing that drifts - baselines age too. A golden trace from three sprints ago still anchors every diff; failures get noisy and teams quietly stop trusting the gate. This makes baseline age visible so re-recording is a deliberate act. Advisory only - never blocks.
How
staleness.py:check_baseline_staleness()- mtime age vs threshold; missing files are load errors (not staleness)diff:--stale-daysflag +[cli] stale_baseline_daysconfig key; warning prints in the--explainsection after culpritTesting
5 new tests (344 total): old-baseline warning, fresh no-warning, config-driven threshold, missing-file semantics, fresh-file render.