the bridges already knew and threw it away — the usage block was on the wire. it is read per round now (a turn that called a tool paid for two responses), turned into watt-hours from the model's active parameters, and parked on the footer's gauge row beside the viewer count. `/energy` prints the working, and the phone client gets the same number as a chip you can tap. it is an estimate and says so everywhere: nobody publishes per-token energy, so the slope is anchored to the only figures anyone has released (google's 0.24 Wh median prompt, epoch's ~0.3 Wh) and the ratios — which rest on announced active-parameter counts — are the half that can be defended. `/energy` leads with them. carries the rest of this branch's in-flight aesel tree, which is what the 134 passing tests and the PTY run were measured against. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>