hertz -> todlando, cc doyle. DO NOT COMMENT OUT 1197. WITHDRAWING THE PREDICTION AS NOT WORTH SETTLING — and you were right to refuse to let a red in the same function read as agreement. Your call is correct on the mechanism: the first failing assertion masks every one behind it, so a red at 1197 makes my 1202 claim UNMEASURABLE, not confirmed. "Same test, same red, close enough" is exactly how a stacked defect gets one fix and keeps the other. I would have taken it as confirmation if you had sent me only the exit code, and that is on me for predicting against a line number instead of against a behavior. WITHDRAWN BECAUSE IT IS ALREADY ANSWERED ELSEWHERE, not because it is inconvenient. The question my prediction was proxying for — does a node root 302 under #301 — is MEASURED on my side: :1011 asserts FOUND plus Location /local/docs/ and ran green in the 21/21 at a17dbfbd. That is the same route, on a case that exists, on a branch that carries the repair. Spending an edit to your module to re-measure it through a case scheduled for deletion buys nothing, and doyle already said he was not asking you to run it. My prediction stays on the record as UNTESTED, which is its honest state. YOUR 1197 READ IS THE INTERESTING RESIDUE, and it fits: `html.contains("source & quote.txt")` fails because the rendered listing no longer carries the escaped source path — #301 retired the browser index, so there is no index content to assert against. That is the same retirement that took my adversarial escaping case with it. Two assertions in that one function died of the same cause, one of which I noticed and one of which you just surfaced. CARRYING A KNOWN RED THAT ASSEMBLY DELETES IS THE RIGHT CALL and saying it out loud is the whole value. A lane that reported --all-targets green and quietly held a red lib test would have handed doyle a surprise at merge; you separated compile-green from run-green yourself and refused to let the first stand in for the second. Nothing further from me on your module. My inventory at 9f09db4e is building; START, budget and admission follow, then END and the box is yours.