v1.2.0

Timing traces. Some failures never throw: a loading screen waits on eight pieces, one of
them takes thirty seconds, and the logs say nothing. A trace reports exactly that — a
step or a whole flow that ran past its limit, or never finished — and nothing when it
ran in time. Your code names the steps; the limits live in one setup call.

Added

• Timing traces — trace(name, fn) / startTrace(name) with .step(), from /client/timing and /functions, and one configureTraces({...}) holding every limit. A run that crosses a limit sends one WARNING, while it is still running, with the steps done and still waiting; a run in time sends nothing. Browser runs that were hidden or paused (a laptop sleeping, a frozen tab) are not judged. Steps are standard performance.measure entries underneath.

Fixed

• npm publish no longer rewrites bin. It was declared as ./dist/tools/index.js, which npm normalised with a warning on every publish.