You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
0.198.0 — The showcase frame on the front page shows the product at work rather than an empty launch. The frame carries the essence itself: the hard gate that refused to count green tests without a proven reproduction of the bug, the verdict with the real test score, and the minted receipt with its re-verification command. Every fact in the frame comes from a real run on a local model; captured from the live interface.
0.197.0 — The resume check names the STEP, not just the clock. It performs two full runs and a resume where its neighbours perform one, and on expiry it reported only that time had run out — which cannot tell a stalled first run from a stalled resume, and invites raising the number instead of learning which. Its outer budget now sits BEHIND the sum of its own bounds rather than in front of them.
0.196.0 — When the suite reported no numbers at all, the RUN itself now speaks — its exit code and last lines. "Zero passed" looks identical for three different findings: the suite shrank, the suite never started, the run was cut off part-way. Its budget is raised to twenty-five minutes; the same suite takes about twelve on a quiet runner, and this criterion runs beside the whole rest of the matrix.
0.195.0 — The final sweep is bounded by TIME, not by a number of attempts. A count is a bound on the wrong quantity: each attempt costs a forced garbage collection and a pause, so raising it to outlast a stubborn handle pushed the sweep past the suite's own budget — and a sweep that times out fails the run as loudly as one that throws, with nothing to read. Both targets now fit inside the budget with room to spare.