v1.3.0

Minor Changes

• #186 52ec7c7 - The react addon now names a hydration mismatch, not just its cost. React's default
  onRecoverableError dispatches a window error event; a mismatch fires one. The pre-app hook counts
  the hydration recoverable errors and stamps hydrationRecoverableErrors + the first message on the
  run span, shown in the React (addon) block of query span run and in --format json. Exact-count
  tier, build-independent (production fires it). An app that supplies its own onRecoverableError
  suppresses the event, so an absent count is not proof of clean hydration.

Patch Changes

• #185 b0f5861 - Docs: AGENTS.md tightened -- same rules, half the words. The counterintuitive-field reference is
  delegated to the README's Consuming-the-JSON section, and the shape is now a documented decision in
  docs/dev/agents-md.md.

• #184 4044c14 - Docs: restructure the README for a first-time reader. Install command and requirements now sit at the
  top, a Troubleshooting index maps each common failure to the section that fixes it, and cold terms
  (CLS, TOON, base::TimeTicks, the .stack trace) are glossed on first use.

• #181 8b2b478 - Release job no longer fails when the current version is already on npm. A push to main with no pending
  changesets re-attempts the current version; the publish step now treats "already published at this
  version" as a no-op success and fails only on a genuine publish error.

• #182 912538e - Three React-debugging fixes:

  • query blame --forced on --breakdown now resolves a forcing read to source. A sampled read-site
    whose executing line falls on a minified bundle line falls back to the leaf function's own column
    (the frame the CPU model resolves), so a bundled app shows app.jsx:8, not dist/app.js:9.
  • query span <step> no longer prints "React (addon): not detected" on a step span. Detection is a
    run-level fact; a step shows its commit count alone. JSON stays honest (detection absent, not fake).
  • The react-dev Performance-Track summary now reports real per-track ms, read from each entry's
    start/end (the instant TimeStamp events carry the span there, not on dur). Tracks nest, so the
    timing is per-track, no grand total.

• #187 d991821 - README wording: the install line now says it installs the wpd command (long form
  web-performance-debugger) instead of "bins", and the "at a glance" contrast names a page score like
  Lighthouse instead of an unexplained "scorecard".