v0.1.6

Extension contract versions are unchanged: world 5, provider 5, bot 6.

Extension authors

• A config group handed over by a World, a bot package or a provider must have a string id, a
  string owner and schema.properties. A group missing any of them is skipped by the console and
  logged with the fields it does carry; the other groups load and save as usual. The construction
  check (dry mount) reports such a group with its field names (#176).

Console

• One malformed config group from an extension no longer makes every save in the settings fail
  with HTTP 500. POST /api/config returns a JSON error for any remaining failure instead of the
  Express HTML error page (#176, Pal-AI-Lab/Coopanion#52).

Core

• A range query with limit and no lower bound (the console's conversation page, diagnostics
  export) reads segments from the newest backwards until the limit is met instead of loading the
  whole history. Loaded history segments are released after each query, keeping only those the
  query read (#168, Pal-AI-Lab/Coopanion#39).

Worlds

• QQ: qq_read_history, neighbourhood reads by message id or time, the events panel and forwarded
  message recovery read only the slice of events they need, newest first, instead of scanning all
  runs. The events panel's per-conversation counts are rebuilt at startup and then incremented
  (#173).
• Terminal: checking whether anyone has spoken pages back from the newest event and stops at the
  first message instead of reading all history (#173).
• Minecraft: escaping lava while standing only on scorching ground (such as a magma block) no longer
  computes a NaN aim that froze the bot's physics (#172).