honey-gain

# Honey Gain Report the **committed** benchmark results — never a guessed or per-session number, and never an embedded copy that can drift from the bench. ## Do 1. Recompute from the committed records at use time — don't recite from memory, and prefer the raw records over any rendered table (renderings go stale, the records don't): ```bash cd bench && node src/report.js --stamp full-opus48 --by-type ``` Offline, no API spend. Swap `--stamp full-gpt55` for the cross-provider figure, drop `--by-type` for the whole suite. Hive handoff numbers → [`bench/hive/RESULTS.md`](../../bench/hive/RESULTS.md). 2. Report the tier table terse: **Δ LOC and Δ output, each with its `p`**, judge as win/loss/tie, and the test pass-rate, per variant. The tier split *is* the finding — deepest on code and handoffs, output a statistical tie on user-facing (the polish carve-out). Lead with **Δ LOC**: it measures Lever 1 directly, while output tokens mix code with the prose around it, and the two come apart (Ponytail cuts lines but narrates at length). ## Rules - **Never quote a delta without its p-value**, and call `(ns)` results ties, not wins. Every figure is a paired per-task median; a ratio of arm totals is not quotable. - Prose renderings ([`bench/README.md`](../../bench/README.md#results), `results/combined.md`) are secondary. If one disagrees with a fresh `--stamp` recompute, the recompute wins — say the rendering is out of sync. - Quality is a **ti...