feat: profiling_drift vitals leg — pinned-value drift from autolens_profiling#38
Merged
Merged
Conversation
…rofiling (#37) autolens_profiling's runtime cells record pinned likelihood/evidence drift into result JSONs (pinned_expected/pinned_drift) instead of crashing (autolens_profiling#54). Close the loop on Heart's side: - heart/checks/profiling_drift.py: observer-only scan of autolens_profiling/results/**/*.json for non-empty pinned_drift; writes ~/.pyauto-heart/profiling_drift.json; repo absent -> observed: false, tick skips gracefully - snapshot key in heart/state.py; tick.sh invocation mirroring the script_timing guard; readiness YELLOW reason per drifted result (capped at 5 + "+N more", weight (10, 30)); dashboard section; LOCAL_ONLY_FAMILIES entry - tests/test_profiling_drift.py: 7 cases (clean/drifted/ignored/absent + readiness yellow/cap/clean); suite 217/217 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Summary
Closes #37. autolens_profiling's runtime cells record pinned likelihood/evidence drift into their result JSONs (
pinned_expected/pinned_drift) instead of crashing (autolens_profiling#54, merged). This PR closes the loop on Heart's side: a drifted result is a health finding — library regression or stale pin, either way the profiling baselines are non-comparable until a human resolves it.Changes
heart/checks/profiling_drift.py(new) — observer-only scan ofautolens_profiling/results/**/*.jsonfor non-emptypinned_drift; writes~/.pyauto-heart/profiling_drift.json; repo absent →observed: falseand the tick skips gracefully (mirrors the script_timing guard)heart/state.py— snapshot key;heart/tick.sh— invocation with dir guardheart/readiness.py— YELLOW reason per drifted result (capped at 5 + "+N more"), weight(10, 30)heart/dashboard.py—profiling_driftsection +LOCAL_ONLY_FAMILIESentrytests/test_profiling_drift.py(new) — 7 cases: clean / drifted / fields-absent+corrupt-JSON ignored / repo absent / readiness yellow / cap / clean-adds-nothingTest Plan
Validation checklist (--auto run — plan on the issue)
🤖 Generated with Claude Code