feat!: name the unknown key, expose tail probabilities, flag short fits

Three issues from two downstream consumers, all small, all sharing a
theme: the crate had the information and would not hand it over.

#44 — `UnknownKey { team: 0, member: 0 }` did not say which key. A
consumer upgrading 0.1.2 -> 0.4.1 had every one of 5591 predictions
return this error, fell back to a neutral 0.5, and lost its entire
metadata model for a day. Nothing crashed and nothing logged; it was
found by sweeping an unrelated parameter and noticing the output did not
move. The 0.4.0 change that made unknown keys an error was right — the
error was just too anonymous to act on. It now carries the key's `Debug`
rendering, and its `Display` says what to do about it. The precondition
is documented on every prediction entry point, which the reporter said
would alone have saved the day.

#43 — `cdf` was `pub(crate)`, so a consumer asking "is this competitor
below the cutoff" approximated it with a `mu + z * sigma` band and had no
way to say what confidence any `z` bought. Adds
`Gaussian::probability_below` / `probability_above`. The second is
separate on purpose: `1 - cdf` collapses to exactly zero past ~8.3
sigma, and a stopping rule is evaluated precisely there. Both route
through the survival function added in 0.4.1, so this is visibility
rather than new numerics.

#50 — `ConvergenceReport` was not `#[must_use]`, so the one signal that
a fit stopped short was trivially discarded. It now is, and that
immediately found 78 sites doing exactly that — including this crate's
own ATP example, which was capped at 10 sweeps when the history needs
30. The example now reads the report and says so.

`ITERATIONS = 30` is documented as the floor it is, with the three
measurements to hand: 400 events over 100 competitors already stops
there at ~7e-3 against a 1e-6 tolerance, the ATP example needs 30 at a
much looser one, and a consumer's 2000-node model needs 76 to 161.

BREAKING CHANGE: `InferenceError::UnknownKey` gains a `key` field, and
the prediction methods now require `K: Debug` in order to fill it.

Closes #43, #50. Refs #44 — its third ask, an opt-in `UnknownKeys::Skip`
mode, is a live API question and deliberately not answered here.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011hcFjNDmHXZF8URGLku5zZ

src/lib.rs

@@ -158,6 +158,23 @@ pub const SIGMA: f64 = BETA * 6.0;
 pub const GAMMA: f64 = BETA * 0.03;
 pub const P_DRAW: f64 = 0.0;
 pub const EPSILON: f64 = 1e-6;
+/// Default cap on convergence sweeps.
+///
+/// **This is a floor, not a recommendation.** It is adequate for small
+/// histories and is quickly outgrown: a history of 400 events over 100
+/// competitors already stops here with a final step of ~7e-3 against the 1e-6
+/// default tolerance — four orders of magnitude short — and a dense joint model
+/// of ~2,000 nodes over ~3,300 events has been measured needing 76 to 161.
+///
+/// Overrunning it is not an error, and deliberately so: `converge` returns a
+/// [`ConvergenceReport`] whose `converged` flag says what happened. But a fit
+/// that stopped short is *wrong by a little*, which is the worst available
+/// failure — every rating is finite and ordered sensibly, and nothing in the
+/// numbers themselves says they were still moving. Read the report; the type is
+/// `#[must_use]` for that reason.
+///
+/// Raise it via [`ConvergenceOptions`]. Convergence cost is roughly linear in
+/// the cap, and for anything but a toy the extra sweeps are milliseconds.
 pub const ITERATIONS: usize = 30;
 
 /// Largest team count `History::predict_outcome` will enumerate.