From 062544983b8e7b55d6e46f5c2b4d687b727aa5aa Mon Sep 17 00:00:00 2001 From: Josh Allmann Date: Thu, 25 Jun 2026 10:33:27 -0700 Subject: [PATCH 1/2] fix(golden): refresh knob_step reference 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. --- tests/golden/refs.json | 33 +++++++++++---------------------- 1 file changed, 11 insertions(+), 22 deletions(-) diff --git a/tests/golden/refs.json b/tests/golden/refs.json index 1c9f5aa0..0da6b61b 100644 --- a/tests/golden/refs.json +++ b/tests/golden/refs.json @@ -28,31 +28,20 @@ }, "knob_step": { "file": "knob_step.tar.gz", - "sha256": "5289d21984edbf0b0a52f7716802da5944ef4d250dd78e755bfea6a4b3283a6c", - "canonical_sha256": "0b2eac2a326cea51f36c277771adf0de333401a1af026ccce8ab39d81c63e238", + "sha256": "21db75608bf7e2d6d9212108eab6334c72fda79359b28e8f44ad50c9f6d9e1ec", + "canonical_sha256": "95e92b12dd2e6a95052395fc9aeae7c013c4110cfb1442fdac6f283b4338d808", "thresholds": { - "_note": "Calibrated 2026-06-09. knob_step carries a stable, benign cross-build mel offset vs the 06-04 canonical (mel_l2 floor 0.0953, bit-stable across runs; win_cos_min 0.9999, rms 0 dB), distinct from peers because the knob legitimately alters generation after it fires. mel_l2 relaxed above that floor with margin; the cosine/level gates keep their strict defaults so a real regression still trips them.", - "mel_l2": 0.13, - "rms_db_diff": 0.5, - "win_cos_min": 0.995 + "_note": "Refreshed 2026-06-25 from DEMON main after the 06-04 canonical drifted. Same-pod repeat-3 noise stayed tiny (mel_l2 0.00165), while fresh-pod verification runs against the new canonical landed at mel_l2 0.00143 and 0.051. mel_l2 is tightened to cover that observed cross-pod spread with margin; cosine and level gates are reset near their strict defaults.", + "mel_l2": 0.08, + "rms_db_diff": 0.1, + "win_cos_min": 0.999 }, "env": { - "harness_git_sha": "96c57bb", - "pod_url": "ws://127.0.0.1:49676", - "gpu": "NVIDIA GeForce RTX 5090", - "server_info": { - "no_backend": false, - "kiosk": false, - "default_mode": "graph", - "warmup": null, - "server_side_fixtures": [ - "inside_confusion_loop_60s_gsm.wav", - "low_fi_Gm_loop_60s_gnm.wav", - "prog_rock_loop_60s_enm.wav", - "thrash_metal_loop_60s_enm.wav" - ] - }, - "captured_at": "2026-06-04T13:18:37.202829+00:00" + "harness_git_sha": "778caa4", + "pod_url": "wss://pod-a40a4cd3d6fc.daydream.live/", + "gpu": "unknown", + "server_info": {}, + "captured_at": "2026-06-25T17:11:53.497956+00:00" } }, "lora_enable": { From ac9c72d6c9deb6a0a492747aa6418025e1e0ba87 Mon Sep 17 00:00:00 2001 From: Josh Allmann Date: Thu, 25 Jun 2026 11:17:22 -0700 Subject: [PATCH 2/2] docs(golden): clarify refs env semantics 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. --- tests/golden/README.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/tests/golden/README.md b/tests/golden/README.md index 4aad7b1c..c4f4bb04 100644 --- a/tests/golden/README.md +++ b/tests/golden/README.md @@ -24,6 +24,13 @@ identical suite at the refactored build. | `test_golden.py` | Audio matches the canonical reference | | `test_latency.py` | Coarse latency ceilings + per-build report artifact | +The manifest's per-scenario `env` block is provenance only. The golden +contract reads the bundle location/hashes and calibrated thresholds; it +does not gate pass/fail on `env`, nor does it attempt to recreate a run +from those fields. This matters for queued production-pod captures, +where metadata like `server_info`, `gpu`, or the exact signed pod URL +may be unavailable or intentionally normalized. + ## Running On a local GPU box the suite is self-contained: it spawns the server