AbstractFramework 0.9.1

Changed

• Pins abstractgateway 0.11.1: the gateway never caps an entity's output (the model works at its
  full capacity; the ABSTRACTGATEWAY_ENTITY_MAX_OUTPUT_TOKENS variable is gone and the chat-open
  max_output_tokens field is ignored with a deprecation line), and its boot applies the
  installer's apps-upgrade.pending, and AbstractCode runs get send_email when Agent email tools
  are on (the run input schema serves the effective tools default). Install matrices, the manifest, README and docs regenerated;
  the docs' app and core console version tables now name the 0.9.0 releases (flow 0.7.0, code
  0.10.0, observer 0.6.0, entity 0.6.0, abstractcore 2.23.0, abstractcore-console 0.7.0).

Fixed

• The installer upgrades the browser apps: on every install and upgrade (install.sh, install.ps1,
  and the console's Update, which runs --no-start), each app the gateway has installed is
  brought to the release's pinned version through abstractgateway apps update <app> --version <version> (a running app restarts on the new bundle); --print lists the planned updates, the
  summary lists each app's version, and a failed update is reported in red with exit status 1. With
  no gateway running, the versions go to <data dir>/apps-upgrade.pending for the gateway's next
  start. Before, an upgrade left the apps on their old versions (Code web 0.9.0 after 0.9.0).