0.46.0

Engine

• Record the connection a particle was parsed from, which a sieve bound to one connection
  fills in.
• Give a connection a label and a description, the description defaulting to the
  docstring of the component field holding it.
• Report the connections stamped on each particle type's records alongside its fields.
• Index each record table's address alongside its timestamp, and alongside the level,
  connection, or direction a record view filters with it, so a filtered listing seeks its rows
  instead of reading back through every newer one. Migration 0010 builds these, holding each
  table closed to writes while it does, which takes minutes on a large history.
• Answer a listing over a component's subtree as one ordered seek per branch, the branches read
  from the records so a decommissioned component's history is still reached.
• Compile SQLite 3.51.3 into the engine, from 3.46.0.

Python API

• Rename Source.label to Source.uri, which every source answers as a URI.
• Accept several connections on @sieve, given separately or as a sequence.

Web Console

• Show the connection a message or particle arrived on.
• Filter a chart series group to one connection, and draw a line per connection for a type
  several of them produce.
• Set how many decimal places a chart or meter reads a value to.
• Fit a chart's Y axis to the shown series or to all of them, with a separate toggle for
  anchoring at zero.
• Choose a connection for a meter.
• Build a messages or particles view from a component's connections, dragged into a workspace
  or created from their context menu.
• Build a particles view from a declared particle type the same way, selecting type headers
  with a held shift or command.
• Build a controls widget from a component's actions, one button per action.
• Peek a workspace into view when it is chosen from a list or from a docked tab strip.

Fixes

• Draw every console icon from the bundle rather than fetching any from a public service,
  which left a console on an isolated network showing none of them.
• Host the engine on the environment's own interpreter when running from a development
  source, rather than whichever one PATH offers.
• Dismiss an inline rename opened from a menu when the pointer goes elsewhere.
• Offer a record view's connection and address choices from the addresses its own filter
  reaches, rather than every one the engine carries.