Audit 3/3: the evidence - red-first tests for every finding - #27
Draft
enoch85 wants to merge 1 commit into
Draft
Conversation
enoch85
marked this pull request as draft
July 15, 2026 14:33
enoch85
force-pushed
the
audit/2-simulator-tooling
branch
from
July 15, 2026 19:58
bc6a256 to
1fc2c9a
Compare
enoch85
force-pushed
the
audit/3-tests
branch
2 times, most recently
from
July 15, 2026 20:11
143cea6 to
f95b008
Compare
enoch85
force-pushed
the
audit/2-simulator-tooling
branch
from
July 15, 2026 20:12
1fc2c9a to
9c36d7a
Compare
Ninety-odd new test files, one per defect or invariant: the billing hour survives the clocks going back; an hour the meter slept through is not a bill; an unloaded integration does not drive the heat pump; the thermostat off switch actually turns it off; a user boost outranks the price optimizer; the pump models match their datasheets; the emitter law matches OpenEnergyMonitor to 0.00 C; the simulated plant obeys physics through bounds that can actually fail; no document misquotes the safety thresholds; no fenced declaration names a constant the code does not have. The two known-open defects stay visible as strict xfails restricted to AssertionError (F-124 saturation trap, F-132b learning ceiling): fixing either turns the suite red until its marker is removed, and a crash can no longer impersonate the finding. Run against main, this suite fails 556 tests and 40 files cannot import - the measured before/after of the audit. The tip of this branch is byte-identical to audit/safety-fixes-and-en442.
enoch85
force-pushed
the
audit/2-simulator-tooling
branch
from
July 15, 2026 20:14
9c36d7a to
06219a4
Compare
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.
The evidence: ~96 new test files, each one written red-first against a defect that was live in production. Stacked on the production and simulator PRs; the tip of this PR is byte-identical to the audit branch.
What they pin, by area:
AssertionError— fixing the layer turns the suite red until the marker is removed; a crash can no longer impersonate the finding.Run against main, this suite fails 556 tests and 40 files cannot import — the measured before/after of the audit.