v0.3.0

Knowing when to update, what version you are on, and two numbers that were wrong.

Added

• TurnLens says when a newer version is published. A global install pins
  whatever version was current when you ran it, which is how somebody on 0.1.1
  could miss that 0.2.0 had removed the flag they were using. Once a day,
  before a run starts, TurnLens asks the npm registry what is published and
  prints two lines if it is behind:

  TurnLens 0.3.0 is available. You have 0.2.0.
    npm install -g turnlens@latest
  

  It installs nothing and asks nothing, and silence is the normal outcome. The
  check is skipped under --offline, under NO_UPDATE_NOTIFIER set to any
  value, in CI, and whenever there is no terminal to print to. It adds no runtime
  dependency and no background process: the request rides along with the pricing
  request every run already makes, and it is eighteen bytes.

• --version and -v, printing the bare version and nothing else. The tool
  previously had no way to report which version it was. Every help level names
  it, turnlens --help included, which is where somebody filing a bug report
  looks first.

Fixed

• A narrowed report no longer overstates how many sessions it covers.
  turnlens report --since 2026-08-02 --until 2026-08-02 used to head the table
  35 sessions over 1 day when one session ran that day. Every session on the
  machine has to be opened, because which one holds a given day is knowable only
  by looking, so the count was of files read while the day count beside it
  counted only days that carried a turn. Now 1 of 35 sessions over 1 day, and
  still 35 sessions over 11 days when no date bound narrows anything.

  --json gains coverage.sessionsWithTurns beside coverage.sessions, and the
  same pair per agent. No existing field changed meaning.

• --json is machine-readable under every flag again. Three messages shared
  stdout with the report: the --refresh-pricing result, the notice that pricing
  fell back to cached data, and the update notice. So
  turnlens report --json --refresh-pricing | jq failed on the first line. They
  are diagnostics rather than data and now go to stderr, where they still reach
  the terminal and no longer reach a pipe.

---

Nothing is removed or renamed in this release. Every 0.2.0 command, flag and
--json field works as it did, so upgrading needs no change to anything you have
scripted.

Full diff: v0.2.0...v0.3.0