v1.0.18

Documentation

• Volatile measurements removed from the evergreen docs. The repo's own AGENTS.md rule is to omit them,
  and the docs had drifted a long way from it: resting RAM (~12 MB in three files), the 55–125 ms hold
  range, the JS heap cap, the 300–600 MB transient fetch figure, OOMScoreAdjust=500, the -n 100 /
  -n 200 log tails, the 28×32 checkbox inset and the ~11% chrome band. Each was a number the code
  owns and nobody re-measures, so each was a future drift ticket paid for in review attention.

  They are replaced with the behaviour and a pointer to the live source: browser-agent doctor reports what
  the daemon actually costs on the host it is running on, and the env table owns the config defaults. The
  log-tail commands become time-bounded (--since "10 min ago"), which is better advice for a cold-start
  problem than a line count anyway.

• docs/architecture.md described a design that no longer exists. It explained that the viewport origin
  is derived from the browser window's outer rectangle — which is the fallback, not the mechanism. Since
  1.0.9 the origin is measured once per session by locating a calibration marker, and the geometric estimate
  only runs when that cannot. An agent reading the old text would have looked for a chrome-height constant
  that was deliberately removed, and would have concluded the calibration did not exist. Rewritten to describe
  the measurement first and the estimate as its fallback, including why the estimate is a few pixels off and
  when a calibration is trusted.

• AGENTS.md no longer restates the ruff selectors and line length (they live in [tool.ruff]) or the size
  of the Pillow wheel and trafilatura's dependency count.