@koda-sl/baker-cli 0.328.0 → 0.329.0

package/README.md

@@ -1426,6 +1426,8 @@ baker experiment fold                                            # make the page
 
 **A finished test is a record.** Its counts are frozen when it ends, so it reads the same next year as it did that day; its `learning` is what it taught, in a person's words. `history` returns every finished test — the claim, what was different, the numbers with their interval and confidence, what was kept and whether that went against the numbers, whether the belief held, and the learning — and `plan` returns the same entries as `pastTests` for the page it sizes, so a hypothesis is chosen against the page's record rather than in ignorance of it.
 
+**The verdict is one interval against two numbers.** A 95% anytime-valid interval on the lift, against zero and against the lift the test was built to find (δ): above zero is a `winner` (variant), below zero a `winner` (control), entirely inside ±δ `no_difference`, and under +δ otherwise `cannot_win` — the new version can no longer win by what the test was looking for. Nothing is gated on days; `stillNeeded` says how many more visitors and conversions the test needs if the gap holds, and `earliestDecisionAt` is only that at today's pace.
+
 **The confidence is anytime-valid.** `--full` carries `evidence.confidence`, how sure the numbers are that the two versions differ at all, read off the same construction as the verdict — so it holds however often it is read, and a winner is called exactly when it crosses 95%. Beside it, `probabilityVariantBetter` is the Bayesian chance the new variant is the better one, which is for printing and never for deciding.
 
 **Finishing with the variant takes two beats, and `fold` is the second.** `finish --keep variant` records which version is live and the edge serves it to everyone at once. `baker experiment fold` moves that version into the page's own folder, archives the one that lost as a self-contained snapshot under `src/_variants/<page id>/<n>/`, and deletes the variant folder. Until it runs, the page is served by a rewrite and cannot be tested again. Run `fold` with no arguments after any test ends, then publish; Baker drops the rewrite by itself once the new pages are live.