v1.1.0

Changed

• npm installs now receive a ready-to-run file instead of the plugin's source,
  so OpenCode no longer has to prepare the plugin while it starts. Installing
  from a folder still uses the source. Nothing to do on your side: update the
  version and restart OpenCode as usual.

Fixed

• Installing from npm no longer crashes OpenCode, and the line now appears.
  When the plugin was installed from npm — the way the README recommends — the
  status line stayed blank, and a few minutes into a session OpenCode could
  close itself with Error: Failed to create TextBuffer. OpenCode prepared the
  plugin while starting, and the plugin then drew with its own copy of the
  drawing library instead of OpenCode's; that drawing failed, and every failed
  attempt used up a little of the renderer's fixed supply of drawing objects.
  Once the supply ran out, OpenCode stopped. The plugin now arrives ready to
  run and draws with OpenCode's own library, so nothing is prepared or guessed
  at start-up. Installing from a folder (a checkout) was never affected and
  behaves exactly as before.
• One thing going wrong while drawing no longer costs you the line — or your
  session. Each part of the line now fails on its own and falls back to
  something simpler: a colour that cannot be worked out is left to your
  terminal, a reading that cannot be worked out is skipped while the rest of
  the line stays, figures that cannot be refreshed stay on screen from the last
  successful draw (dimmed, so you can see they are not new), and a row that
  cannot be drawn properly is drawn as plain text. If nothing at all can be
  drawn, the line shows a single ⚠ instead of vanishing. And if the drawing
  is broken past that point, the plugin stops after three attempts and writes
  one warning instead of retrying forever — the retries were what drained the
  renderer and closed OpenCode.