v0.8.0

v0.8.0 - a retired gate class, stable refusal codes, exact engine arithmetic

This release follows v0.7.0. It carries the gate the harness serves since 2026-10-04: one class retired, every refusal named by a stable code, stricter checks on caller-built names and on the committed USDe key, and engine functions that compute the split rank exactly.

What is served

• The gate class btc-dir-15m is retired. A call that names it returns 400 with the code task_class_retired; no served class now carries an attestation subject, so a caller-carried attested price is refused on every served class.
• Every 400 answer of the gate carries a stable error code beside its message, from a closed list of 24 codes exported with the harness (HARNESS_ERROR_CODES). A caller can branch on the code; the message text stays human-readable and may change.
• A BYO task class or predictor name that reduces to a committed or reserved name once common ASCII look-alikes are folded (for example l, I and 1; rn and m; 0 and O; _, . and -) is refused with byo_lookalike_confusable. Names reserved for the kata prefix are refused with byo_reserved_kata. Look-alikes outside this closed folding still pass; they are declared as a residual class.
• The committed USDe key of stable-run-velocity-24h takes alpha 0.1 and nMin 50, imposed by the server; any other value returns 400 (policy_alpha_mismatch, policy_nmin_mismatch).
• The gate's description now states that each band edge is yhat - qhat or yhat + qhat rounded to the nearest double, so it can differ from the exact edge by up to half a unit in the last place.

What changes in the code

• @monark/hikae gains an exact split rank computed in rational arithmetic, a one-pass search for the risk-control row, a scaled band and a single canonical writing of a calibration row. The served decisions are unchanged by them: 84 recorded calls, replayed before and after the deploy, differ only where the gate changes listed above apply.
• The site pages that described the retired class now describe it as retired, and the committed copies of what the harness, Narabi and Ukemi serve were re-read from the hosts after the deploy.
• The recorded end-to-end trace of the gate was re-recorded against the served tool list.