fix(golden): refresh knob_step reference #296
Open
j0sh wants to merge 2 commits into
Open
Conversation
Refresh the knob_step canonical bundle from DEMON main after the 2026-06-04 reference drifted past the calibrated mel_l2 gate. Keep the fix scoped to refs.json: update the bundle/canonical hashes, tighten thresholds to the observed 2026-06-25 same-pod and fresh-pod runs, and strip the signed pod query token from the recorded pod URL.
Document that refs.json env metadata is provenance only and not part of the golden comparison contract. This matches the current harness behavior and explains why queued production-pod captures may carry sparse or normalized env fields without affecting pass/fail semantics.
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
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.
This requires an updated knob_step.tar.gz uploaded to Huggingface; not sure I have access to that
Summary
Refresh the
knob_stepgolden reference from current DEMONmainand tighten its thresholds around the new canonical.
Also document that
refs.json's per-scenarioenvblock isprovenance only, not part of the golden pass/fail contract.
What Changed
knob_stepreference bundle hash and canonical hash intests/golden/refs.jsonknob_stepthresholds for the refreshed canonical:mel_l20.08,rms_db_diff0.1,win_cos_min0.999observed same-pod / fresh-pod verification spread
refs.jsonenvmetadata isprovenance only and may be sparse for queued production-pod captures
Why
The old 2026-06-04
knob_stepcanonical had drifted enough that cleancurrent runs were failing the calibrated
mel_l2 <= 0.13gate.A fresh reference captured from DEMON
mainfixes that mismatch.Same-pod repeat-3 noise remained tiny, while fresh-pod verification
runs against the new canonical stayed comfortably inside the updated
thresholds.
Verification
knob_stepcanonical from DEMONmain