abstractframework 0.9.0__tar.gz → 0.9.1__tar.gz

{abstractframework-0.9.0 → abstractframework-0.9.1}/CHANGELOG.md

@@ -6,6 +6,28 @@ All notable changes to AbstractFramework will be documented in this file.
 
 Nothing yet.
 
+## [0.9.1] - 2026-10-02
+
+### 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).
+
 ## [0.9.0] - 2026-10-01
 
 ### Changed

{abstractframework-0.9.0/abstractframework.egg-info → abstractframework-0.9.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.9.0
+Version: 0.9.1
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,7 +23,7 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.11.0
+Requires-Dist: abstractgateway==0.11.1
 Requires-Dist: abstractassistant==0.12.0
 Requires-Dist: abstractcore==2.23.0
 Requires-Dist: AbstractRuntime==0.8.3
@@ -36,10 +36,10 @@ Requires-Dist: abstractvision==0.3.33
 Requires-Dist: abstractmusic==0.1.15
 Requires-Dist: abstract3d==0.3.2
 Provides-Extra: apple
-Requires-Dist: abstractgateway[apple]==0.11.0; extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.11.1; extra == "apple"
 Requires-Dist: abstractassistant[apple]==0.12.0; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.11.0; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.11.1; extra == "gpu"
 Requires-Dist: abstractassistant[gpu]==0.12.0; extra == "gpu"
 Dynamic: license-file
 
@@ -369,7 +369,7 @@ pip install "abstractframework[gpu]"
 | Apple | `pip install "abstractframework[apple]"` | macOS 14+ on Apple Silicon | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 | GPU | `pip install "abstractframework[gpu]"` | Linux with a CUDA or ROCm GPU; on Windows, use the one-line installer (a plain pip install gets PyPI's CPU-only PyTorch and no llama.cpp) | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 
-### Release matrix (abstractframework 0.9.0)
+### Release matrix (abstractframework 0.9.1)
 
 `abstractframework` pins every Python package with `==`, so one version of the
 meta-package always installs the same stack. The browser apps and Rust tools are
@@ -378,7 +378,7 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.11.0 |
+| PyPI | `abstractgateway` | 0.11.1 |
 | PyPI | `abstractassistant` | 0.12.0 |
 | PyPI | `abstractcore` | 2.23.0 |
 | PyPI | `AbstractRuntime` | 0.8.3 |
@@ -399,7 +399,7 @@ and tested together.
 | crates.io | `abstractgateway-console` | 0.14.0 |
 | crates.io | `abstractcore-console` | 0.7.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.11.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.11.1 (`gpu-latest` / `<version>-gpu` experimental) |
 | GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.23.0 |
 
 `abstract3d` (pinned above) comes with AbstractCore in every profile. The optional add-on that is

{abstractframework-0.9.0 → abstractframework-0.9.1}/README.md

@@ -324,7 +324,7 @@ pip install "abstractframework[gpu]"
 | Apple | `pip install "abstractframework[apple]"` | macOS 14+ on Apple Silicon | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 | GPU | `pip install "abstractframework[gpu]"` | Linux with a CUDA or ROCm GPU; on Windows, use the one-line installer (a plain pip install gets PyPI's CPU-only PyTorch and no llama.cpp) | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 
-### Release matrix (abstractframework 0.9.0)
+### Release matrix (abstractframework 0.9.1)
 
 `abstractframework` pins every Python package with `==`, so one version of the
 meta-package always installs the same stack. The browser apps and Rust tools are
@@ -333,7 +333,7 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.11.0 |
+| PyPI | `abstractgateway` | 0.11.1 |
 | PyPI | `abstractassistant` | 0.12.0 |
 | PyPI | `abstractcore` | 2.23.0 |
 | PyPI | `AbstractRuntime` | 0.8.3 |
@@ -354,7 +354,7 @@ and tested together.
 | crates.io | `abstractgateway-console` | 0.14.0 |
 | crates.io | `abstractcore-console` | 0.7.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.11.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.11.1 (`gpu-latest` / `<version>-gpu` experimental) |
 | GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.23.0 |
 
 `abstract3d` (pinned above) comes with AbstractCore in every profile. The optional add-on that is

{abstractframework-0.9.0 → abstractframework-0.9.1}/abstractframework/__init__.py

@@ -10,7 +10,7 @@ Most implementation functionality still lives in component projects.
 
 from __future__ import annotations
 
-__version__ = "0.9.0"
+__version__ = "0.9.1"
 __author__ = "Laurent-Philippe Albou"
 __license__ = "MIT"
 
@@ -18,7 +18,7 @@ RELEASE_VERSIONS: dict[str, str] = {
     "abstractcore": "2.23.0",
     "abstractruntime": "0.8.3",
     "abstractagent": "0.3.17",
-    "abstractgateway": "0.11.0",
+    "abstractgateway": "0.11.1",
     "abstractskill": "0.3.0",
     "abstractmemory": "0.3.0",
     "abstractsemantics": "0.0.5",

{abstractframework-0.9.0 → abstractframework-0.9.1/abstractframework.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.9.0
+Version: 0.9.1
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,7 +23,7 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.11.0
+Requires-Dist: abstractgateway==0.11.1
 Requires-Dist: abstractassistant==0.12.0
 Requires-Dist: abstractcore==2.23.0
 Requires-Dist: AbstractRuntime==0.8.3
@@ -36,10 +36,10 @@ Requires-Dist: abstractvision==0.3.33
 Requires-Dist: abstractmusic==0.1.15
 Requires-Dist: abstract3d==0.3.2
 Provides-Extra: apple
-Requires-Dist: abstractgateway[apple]==0.11.0; extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.11.1; extra == "apple"
 Requires-Dist: abstractassistant[apple]==0.12.0; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.11.0; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.11.1; extra == "gpu"
 Requires-Dist: abstractassistant[gpu]==0.12.0; extra == "gpu"
 Dynamic: license-file
 
@@ -369,7 +369,7 @@ pip install "abstractframework[gpu]"
 | Apple | `pip install "abstractframework[apple]"` | macOS 14+ on Apple Silicon | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 | GPU | `pip install "abstractframework[gpu]"` | Linux with a CUDA or ROCm GPU; on Windows, use the one-line installer (a plain pip install gets PyPI's CPU-only PyTorch and no llama.cpp) | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 
-### Release matrix (abstractframework 0.9.0)
+### Release matrix (abstractframework 0.9.1)
 
 `abstractframework` pins every Python package with `==`, so one version of the
 meta-package always installs the same stack. The browser apps and Rust tools are
@@ -378,7 +378,7 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.11.0 |
+| PyPI | `abstractgateway` | 0.11.1 |
 | PyPI | `abstractassistant` | 0.12.0 |
 | PyPI | `abstractcore` | 2.23.0 |
 | PyPI | `AbstractRuntime` | 0.8.3 |
@@ -399,7 +399,7 @@ and tested together.
 | crates.io | `abstractgateway-console` | 0.14.0 |
 | crates.io | `abstractcore-console` | 0.7.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.11.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.11.1 (`gpu-latest` / `<version>-gpu` experimental) |
 | GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.23.0 |
 
 `abstract3d` (pinned above) comes with AbstractCore in every profile. The optional add-on that is

{abstractframework-0.9.0 → abstractframework-0.9.1}/abstractframework.egg-info/SOURCES.txt

@@ -186,6 +186,7 @@ scripts/tests/test_af_supervisor.sh
 scripts/tests/test_install_user_path.sh
 scripts/tests/test_inventory.sh
 scripts/tests/test_repo_scripts.sh
+tests/test_install_app_upgrade.py
 tests/test_install_index_lag.py
 tests/test_install_profiles.py
 tests/test_install_ps1_gpu_stack.py

{abstractframework-0.9.0 → abstractframework-0.9.1}/abstractframework.egg-info/requires.txt

@@ -1,4 +1,4 @@
-abstractgateway==0.11.0
+abstractgateway==0.11.1
 abstractassistant==0.12.0
 abstractcore==2.23.0
 AbstractRuntime==0.8.3
@@ -12,11 +12,11 @@ abstractmusic==0.1.15
 abstract3d==0.3.2
 
 [apple]
-abstractgateway[apple]==0.11.0
+abstractgateway[apple]==0.11.1
 
 [apple:platform_system == "Darwin"]
 abstractassistant[apple]==0.12.0
 
 [gpu]
-abstractgateway[gpu]==0.11.0
+abstractgateway[gpu]==0.11.1
 abstractassistant[gpu]==0.12.0

{abstractframework-0.9.0 → abstractframework-0.9.1}/docs/api.md

@@ -55,14 +55,14 @@ The response type returned by `llm.generate(...)`.
 
 ### `__version__`
 
-The meta-package version (`0.9.0` for this release).
+The meta-package version (`0.9.1` for this release).
 
 ### `RELEASE_VERSIONS`
 
-Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.8.0:
-`abstractcore` 2.22.0, `abstractruntime` 0.8.2, `abstractagent` 0.3.17, `abstractgateway` 0.10.0,
+Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.9.1:
+`abstractcore` 2.23.0, `abstractruntime` 0.8.3, `abstractagent` 0.3.17, `abstractgateway` 0.11.1,
 `abstractskill` 0.3.0, `abstractmemory` 0.3.0, `abstractsemantics` 0.0.5, `abstractvoice` 0.13.2, `abstractvision` 0.3.33,
-`abstractmusic` 0.1.15, `abstract3d` 0.3.2, `abstractassistant` 0.11.0.
+`abstractmusic` 0.1.15, `abstract3d` 0.3.2, `abstractassistant` 0.12.0.
 
 ### `PACKAGE_DISTRIBUTIONS`
 
@@ -72,9 +72,9 @@ Maps each package name in `RELEASE_VERSIONS` to its PyPI distribution name (for
 ### `NPM_RELEASE_VERSIONS`
 
 The npm apps released with this version, each runnable with `npx <package>`:
-`@abstractframework/flow` 0.6.0, `@abstractframework/code` 0.9.0,
-`@abstractframework/observer` 0.5.0, `@abstractframework/continuum` 0.6.0 and
-`@abstractframework/entity` 0.5.0. They also appear as `npm_apps` in the install manifest.
+`@abstractframework/flow` 0.7.0, `@abstractframework/code` 0.10.0,
+`@abstractframework/observer` 0.6.0, `@abstractframework/continuum` 0.6.0 and
+`@abstractframework/entity` 0.6.0. They also appear as `npm_apps` in the install manifest.
 
 ### `CRATE_RELEASE_VERSIONS`
 

{abstractframework-0.9.0 → abstractframework-0.9.1}/docs/install.md

@@ -197,7 +197,7 @@ The line always runs the installer of the latest AbstractFramework release. It:
   <latest>`, or `AbstractFramework <yours> found: already up to date` (every part is still checked,
   and repaired when needed). An install made by 0.6.1 or earlier recorded no release, so its first
   upgrade says `AbstractFramework found (abstractgateway 0.7.1; its release was not recorded):
-  upgrading to AbstractFramework 0.9.0` (with the gateway version you have);
+  upgrading to AbstractFramework 0.9.1` (with the gateway version you have);
 - installs the gateway version that release pins, and every library the gateway uses
   (AbstractCore, AbstractRuntime, AbstractAgent, AbstractSkill, AbstractMemory, AbstractSemantics
   and the voice, vision, music and 3D packages) at the exact version released and tested with it ([Check your versions](#check-your-versions) shows
@@ -245,7 +245,7 @@ The line always runs the installer of the latest AbstractFramework release. It:
 
 Installs made by AbstractFramework 0.6.1 or earlier recorded neither their release nor your install
 options. The first re-run says `AbstractFramework found (abstractgateway <version>; its release was
-not recorded): upgrading to AbstractFramework 0.9.0`, and reads your options from what is installed: whether the terminal console and `abstractcode` are
+not recorded): upgrading to AbstractFramework 0.9.1`, and reads your options from what is installed: whether the terminal console and `abstractcode` are
 there, whether the gateway has the tray extra and the AbstractCore commands, whether the compiled
 extras were built (`--full`), and a custom data directory through the gateway pointer. It prints
 what it found (`read from disk: …`) and records it for later runs. An option the installer did not
@@ -355,9 +355,26 @@ Running workflows pause at their next step and continue after the restart.
 
 ### Upgrade the apps
 
-The browser apps (Flow, Code, Observer, Continuum, Entity) and the desktop Assistant are installed
-by the gateway, so the installer does not change them. When npm has a newer version, the app's card
-on the console's **Apps** page offers **Update** under **Technical details**. In a terminal:
+The browser apps (Flow, Code, Observer, Continuum, Entity) are installed by the gateway, and the
+installer keeps them on the release: on every install and upgrade, once the gateway answers, each
+browser app the gateway has installed is brought to this release's version (`--print` lists the
+planned updates) through the gateway's own `abstractgateway apps update <app> --version <version>`,
+so the gateway's apps registry stays right and a running app restarts on the new version. It is a
+command-line call against the running gateway (signed in with `<data dir>/auth/bootstrap-admin-token`),
+so it works the same on a headless or terminal-only machine: no browser or web console is involved. The
+summary's **Apps** line lists each app's version; an app that could not be updated is listed in red
+with the command to retry, and the installer exits 1. A fresh install installs no app: the console's
+**Apps** page installs them.
+
+When no gateway answers (`--no-start` while the gateway is stopped), the installer writes the
+release's versions to `<data dir>/apps-upgrade.pending` instead, and the gateway (0.11.1 and later)
+brings its installed apps to those versions when it next starts, then removes the file. The
+console's **Update** runs the installer with `--no-start` while the gateway is running, so its apps
+are updated right away.
+
+The desktop Assistant is a Python app the gateway installs; the installer leaves it as it is. When
+npm has a newer version of an app, its card on the console's **Apps** page offers **Update** under
+**Technical details**. In a terminal:
 
 ```bash
 abstractgateway apps list                # installed and latest version of every app
@@ -448,7 +465,7 @@ The Mac package, the `.command` files and the one line all run the same script,
    login** switch counts), a first install leaves it off.
 3. Installs [uv](https://docs.astral.sh/uv/) when it is missing, then Python 3.12 through uv.
 4. Installs the gateway as an isolated uv tool, pinned to this release:
-   `uv tool install --python 3.12 "abstractgateway[<profile>,tray]==0.11.0"`, from prebuilt wheels
+   `uv tool install --python 3.12 "abstractgateway[<profile>,tray]==0.11.1"`, from prebuilt wheels
    only (see [No compiler needed](#no-compiler-needed)), and checks that the command starts
    (reinstalling it in place when it does not). Every profile also gets local voice,
    `--with "abstractvoice[supertonic,stt]==0.13.2"` (the release's AbstractVoice): Supertonic
@@ -793,7 +810,7 @@ instead of starting a browser.
 ```bash
 curl -LsSf https://astral.sh/uv/install.sh | sh             # Windows: irm https://astral.sh/uv/install.ps1 | iex
 uv python install 3.12
-uv tool install --python 3.12 "abstractgateway[tray]==0.11.0"    # [apple,tray] or [gpu,tray] for local engines
+uv tool install --python 3.12 "abstractgateway[tray]==0.11.1"    # [apple,tray] or [gpu,tray] for local engines
                        # (add --with and --overrides as shown by `install.sh --print` to avoid compiling)
 uv tool update-shell                                          # puts ~/.local/bin on PATH; open a new terminal
 abstractgateway service install --port 8080                   # or: abstractgateway serve
@@ -920,7 +937,7 @@ Python 3.11 to 3.13), but it gets PyPI's CPU-only PyTorch and no llama.cpp: use
 installer, which adds PyTorch's CUDA build and llama.cpp's prebuilt GPU build
 ([GPU on Windows](#gpu-on-windows-nvidia)).
 
-`abstractframework` 0.9.0 pins `abstractgateway==0.11.0`, `abstractassistant==0.12.0`,
+`abstractframework` 0.9.1 pins `abstractgateway==0.11.1`, `abstractassistant==0.12.0`,
 `abstractcore==2.23.0`, `AbstractRuntime==0.8.3`, `abstractagent==0.3.17`, `abstractskill==0.3.0`,
 `AbstractMemory==0.3.0`, `abstractsemantics==0.0.5`, `abstractvoice==0.13.2`,
 `abstractvision==0.3.33`, `abstractmusic==0.1.15` and `abstract3d==0.3.2`. The `apple` and `gpu` extras select
@@ -1012,14 +1029,14 @@ Run or install them next to the Python stack:
 | Tool | Command | Version released with 0.8.0 |
 |---|---|---|
 | Gateway web console | built into `abstractgateway`: open the link `abstractgateway serve` prints (`http://127.0.0.1:8080/console#claim=…`) | 0.10.0 |
-| Core web console | built into `abstractcore`: open the link `abstractcore serve` prints (`http://127.0.0.1:8000/console#claim=…`) | 2.22.0 |
-| Core terminal console | `cargo install abstractcore-console` (Rust 1.87+), then `abstractcore-console` (uses the `abstractcore` command). The installers do not build it: it is the console of a standalone `abstractcore serve`, and the gateway's terminal console already has its Models and Engines screens | 0.6.0 |
+| Core web console | built into `abstractcore`: open the link `abstractcore serve` prints (`http://127.0.0.1:8000/console#claim=…`) | 2.23.0 |
+| Core terminal console | `cargo install abstractcore-console` (Rust 1.87+), then `abstractcore-console` (uses the `abstractcore` command). The installers do not build it: it is the console of a standalone `abstractcore serve`, and the gateway's terminal console already has its Models and Engines screens | 0.7.0 |
 | Gateway terminal console | built by the installer (`--no-console` skips it), or `cargo install abstractgateway-console` (Rust 1.87+); then `abstractgateway-console --gateway-url http://127.0.0.1:8080 --token <admin token>` | 0.14.0 |
-| Flow Editor | the console's **Apps** page (opens at `/apps/flow/`), or on its own: `npx @abstractframework/flow --gateway-url <url>` | 0.6.0 |
-| Code Web UI | the console's **Apps** page (`/apps/code/`), or `npx @abstractframework/code --gateway-url <url>` | 0.9.0 |
-| Observer | the console's **Apps** page (`/apps/observer/`), or `npx @abstractframework/observer --gateway-url <url>` | 0.5.0 |
+| Flow Editor | the console's **Apps** page (opens at `/apps/flow/`), or on its own: `npx @abstractframework/flow --gateway-url <url>` | 0.7.0 |
+| Code Web UI | the console's **Apps** page (`/apps/code/`), or `npx @abstractframework/code --gateway-url <url>` | 0.10.0 |
+| Observer | the console's **Apps** page (`/apps/observer/`), or `npx @abstractframework/observer --gateway-url <url>` | 0.6.0 |
 | Continuum console | the console's **Apps** page (`/apps/continuum/`), or `npx @abstractframework/continuum --gateway-url <url>` | 0.6.0 |
-| Entity manager | the console's **Apps** page (`/apps/entity/`), or `npx @abstractframework/entity --gateway-url <url>` | 0.5.0 |
+| Entity manager | the console's **Apps** page (`/apps/entity/`), or `npx @abstractframework/entity --gateway-url <url>` | 0.6.0 |
 | AbstractCode terminal client | `cargo install abstractcode`, or a prebuilt binary from the [AbstractCode GitHub release](https://github.com/lpalbou/AbstractCode/releases) | 0.8.0 |
 
 The browser apps need a running gateway. The gateway installs, starts and serves them itself, on

{abstractframework-0.9.0 → abstractframework-0.9.1}/llms-full.txt

@@ -328,7 +328,7 @@ pip install "abstractframework[gpu]"
 | Apple | `pip install "abstractframework[apple]"` | macOS 14+ on Apple Silicon | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 | GPU | `pip install "abstractframework[gpu]"` | Linux with a CUDA or ROCm GPU; on Windows, use the one-line installer (a plain pip install gets PyPI's CPU-only PyTorch and no llama.cpp) | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 
-### Release matrix (abstractframework 0.9.0)
+### Release matrix (abstractframework 0.9.1)
 
 `abstractframework` pins every Python package with `==`, so one version of the
 meta-package always installs the same stack. The browser apps and Rust tools are
@@ -337,7 +337,7 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.11.0 |
+| PyPI | `abstractgateway` | 0.11.1 |
 | PyPI | `abstractassistant` | 0.12.0 |
 | PyPI | `abstractcore` | 2.23.0 |
 | PyPI | `AbstractRuntime` | 0.8.3 |
@@ -358,7 +358,7 @@ and tested together.
 | crates.io | `abstractgateway-console` | 0.14.0 |
 | crates.io | `abstractcore-console` | 0.7.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.11.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.11.1 (`gpu-latest` / `<version>-gpu` experimental) |
 | GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.23.0 |
 
 `abstract3d` (pinned above) comes with AbstractCore in every profile. The optional add-on that is
@@ -611,7 +611,7 @@ Notes for LLMs working in this repo:
 - [abstractframework/__init__.py](abstractframework/__init__.py): `RELEASE_VERSIONS`, `NPM_RELEASE_VERSIONS`, `CRATE_RELEASE_VERSIONS`, `get_release_profile()`, `print_status()`.
 - [docs/installers/install-manifest.json](docs/installers/install-manifest.json): Generated install manifest, schema v2 (pins, profiles, npm apps, `bootstrap` gateway pin/scripts/flags, console-first `post_install`).
 - [scripts/install.sh](scripts/install.sh) / [scripts/install.ps1](scripts/install.ps1): The bootstrap installers.
-- abstractframework 0.8.0 pins (PyPI, `==`): abstractgateway 0.10.0, abstractassistant 0.11.0, abstractcore 2.22.0, AbstractRuntime 0.8.2, abstractagent 0.3.17, abstractskill 0.3.0, AbstractMemory 0.3.0, abstractsemantics 0.0.5, abstractvoice 0.13.2, abstractvision 0.3.33, abstractmusic 0.1.15, abstract3d 0.3.2.
+- abstractframework 0.9.1 pins (PyPI, `==`): abstractgateway 0.11.1, abstractassistant 0.12.0, abstractcore 2.23.0, AbstractRuntime 0.8.3, abstractagent 0.3.17, abstractskill 0.3.0, AbstractMemory 0.3.0, abstractsemantics 0.0.5, abstractvoice 0.13.2, abstractvision 0.3.33, abstractmusic 0.1.15, abstract3d 0.3.2.
 - Released with it: npm `@abstractframework/flow` 0.6.0, `code` 0.9.0, `observer` 0.5.0, `continuum` 0.6.0, `entity` 0.5.0 (opened through the gateway at `/apps/<app>/`, or run with `npx`); crates (`CRATE_RELEASE_VERSIONS`) `abstractgateway-console` 0.13.0 (built by the installer by default), `abstractcore-console` 0.6.0, `abstractcode` 0.8.0, `abstracttui` 0.6.0; images `ghcr.io/lpalbou/abstractgateway:0.10.0`, `ghcr.io/lpalbou/abstractcore-server:2.22.0`.
 - Profiles: light (remote-only), apple (`abstractframework[apple]`, macOS 14+ Apple Silicon), gpu (`abstractframework[gpu]`); Python 3.10-3.13 (F5-TTS voice cloning in apple/gpu needs 3.11+).
 
@@ -640,7 +640,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "abstractframework"
-version = "0.9.0"
+version = "0.9.1"
 description = "Unified installer and documentation hub for the AbstractFramework ecosystem"
 readme = "README.md"
 license = {text = "MIT"}
@@ -684,7 +684,7 @@ requires-python = ">=3.10"
 # - Keep the meta-package aligned with the real per-package profiles (especially `abstractgateway`).
 dependencies = [
     # Durable Gateway control plane (remote-light by default).
-    "abstractgateway==0.11.0",
+    "abstractgateway==0.11.1",
 
     # Workflow authoring UI is distributed through npm as @abstractframework/flow.
     "abstractassistant==0.12.0",
@@ -718,12 +718,12 @@ dependencies = [
 # the stack by selecting the hardware-local dependency aggregates (owned by Gateway),
 # then adds user-facing apps.
 apple = [
-    "abstractgateway[apple]==0.11.0",
+    "abstractgateway[apple]==0.11.1",
     "abstractassistant[apple]==0.12.0; platform_system == \"Darwin\"",
 ]
 
 gpu = [
-    "abstractgateway[gpu]==0.11.0",
+    "abstractgateway[gpu]==0.11.1",
     "abstractassistant[gpu]==0.12.0",
 ]
 
@@ -774,7 +774,7 @@ Most implementation functionality still lives in component projects.
 
 from __future__ import annotations
 
-__version__ = "0.9.0"
+__version__ = "0.9.1"
 __author__ = "Laurent-Philippe Albou"
 __license__ = "MIT"
 
@@ -782,7 +782,7 @@ RELEASE_VERSIONS: dict[str, str] = {
     "abstractcore": "2.23.0",
     "abstractruntime": "0.8.3",
     "abstractagent": "0.3.17",
-    "abstractgateway": "0.11.0",
+    "abstractgateway": "0.11.1",
     "abstractskill": "0.3.0",
     "abstractmemory": "0.3.0",
     "abstractsemantics": "0.0.5",
@@ -3935,7 +3935,7 @@ The line always runs the installer of the latest AbstractFramework release. It:
   <latest>`, or `AbstractFramework <yours> found: already up to date` (every part is still checked,
   and repaired when needed). An install made by 0.6.1 or earlier recorded no release, so its first
   upgrade says `AbstractFramework found (abstractgateway 0.7.1; its release was not recorded):
-  upgrading to AbstractFramework 0.9.0` (with the gateway version you have);
+  upgrading to AbstractFramework 0.9.1` (with the gateway version you have);
 - installs the gateway version that release pins, and every library the gateway uses
   (AbstractCore, AbstractRuntime, AbstractAgent, AbstractSkill, AbstractMemory, AbstractSemantics
   and the voice, vision, music and 3D packages) at the exact version released and tested with it ([Check your versions](#check-your-versions) shows
@@ -3983,7 +3983,7 @@ The line always runs the installer of the latest AbstractFramework release. It:
 
 Installs made by AbstractFramework 0.6.1 or earlier recorded neither their release nor your install
 options. The first re-run says `AbstractFramework found (abstractgateway <version>; its release was
-not recorded): upgrading to AbstractFramework 0.9.0`, and reads your options from what is installed: whether the terminal console and `abstractcode` are
+not recorded): upgrading to AbstractFramework 0.9.1`, and reads your options from what is installed: whether the terminal console and `abstractcode` are
 there, whether the gateway has the tray extra and the AbstractCore commands, whether the compiled
 extras were built (`--full`), and a custom data directory through the gateway pointer. It prints
 what it found (`read from disk: …`) and records it for later runs. An option the installer did not
@@ -4093,9 +4093,26 @@ Running workflows pause at their next step and continue after the restart.
 
 ### Upgrade the apps
 
-The browser apps (Flow, Code, Observer, Continuum, Entity) and the desktop Assistant are installed
-by the gateway, so the installer does not change them. When npm has a newer version, the app's card
-on the console's **Apps** page offers **Update** under **Technical details**. In a terminal:
+The browser apps (Flow, Code, Observer, Continuum, Entity) are installed by the gateway, and the
+installer keeps them on the release: on every install and upgrade, once the gateway answers, each
+browser app the gateway has installed is brought to this release's version (`--print` lists the
+planned updates) through the gateway's own `abstractgateway apps update <app> --version <version>`,
+so the gateway's apps registry stays right and a running app restarts on the new version. It is a
+command-line call against the running gateway (signed in with `<data dir>/auth/bootstrap-admin-token`),
+so it works the same on a headless or terminal-only machine: no browser or web console is involved. The
+summary's **Apps** line lists each app's version; an app that could not be updated is listed in red
+with the command to retry, and the installer exits 1. A fresh install installs no app: the console's
+**Apps** page installs them.
+
+When no gateway answers (`--no-start` while the gateway is stopped), the installer writes the
+release's versions to `<data dir>/apps-upgrade.pending` instead, and the gateway (0.11.1 and later)
+brings its installed apps to those versions when it next starts, then removes the file. The
+console's **Update** runs the installer with `--no-start` while the gateway is running, so its apps
+are updated right away.
+
+The desktop Assistant is a Python app the gateway installs; the installer leaves it as it is. When
+npm has a newer version of an app, its card on the console's **Apps** page offers **Update** under
+**Technical details**. In a terminal:
 
 ```bash
 abstractgateway apps list                # installed and latest version of every app
@@ -4186,7 +4203,7 @@ The Mac package, the `.command` files and the one line all run the same script,
    login** switch counts), a first install leaves it off.
 3. Installs [uv](https://docs.astral.sh/uv/) when it is missing, then Python 3.12 through uv.
 4. Installs the gateway as an isolated uv tool, pinned to this release:
-   `uv tool install --python 3.12 "abstractgateway[<profile>,tray]==0.11.0"`, from prebuilt wheels
+   `uv tool install --python 3.12 "abstractgateway[<profile>,tray]==0.11.1"`, from prebuilt wheels
    only (see [No compiler needed](#no-compiler-needed)), and checks that the command starts
    (reinstalling it in place when it does not). Every profile also gets local voice,
    `--with "abstractvoice[supertonic,stt]==0.13.2"` (the release's AbstractVoice): Supertonic
@@ -4531,7 +4548,7 @@ instead of starting a browser.
 ```bash
 curl -LsSf https://astral.sh/uv/install.sh | sh             # Windows: irm https://astral.sh/uv/install.ps1 | iex
 uv python install 3.12
-uv tool install --python 3.12 "abstractgateway[tray]==0.11.0"    # [apple,tray] or [gpu,tray] for local engines
+uv tool install --python 3.12 "abstractgateway[tray]==0.11.1"    # [apple,tray] or [gpu,tray] for local engines
                        # (add --with and --overrides as shown by `install.sh --print` to avoid compiling)
 uv tool update-shell                                          # puts ~/.local/bin on PATH; open a new terminal
 abstractgateway service install --port 8080                   # or: abstractgateway serve
@@ -4658,7 +4675,7 @@ Python 3.11 to 3.13), but it gets PyPI's CPU-only PyTorch and no llama.cpp: use
 installer, which adds PyTorch's CUDA build and llama.cpp's prebuilt GPU build
 ([GPU on Windows](#gpu-on-windows-nvidia)).
 
-`abstractframework` 0.9.0 pins `abstractgateway==0.11.0`, `abstractassistant==0.12.0`,
+`abstractframework` 0.9.1 pins `abstractgateway==0.11.1`, `abstractassistant==0.12.0`,
 `abstractcore==2.23.0`, `AbstractRuntime==0.8.3`, `abstractagent==0.3.17`, `abstractskill==0.3.0`,
 `AbstractMemory==0.3.0`, `abstractsemantics==0.0.5`, `abstractvoice==0.13.2`,
 `abstractvision==0.3.33`, `abstractmusic==0.1.15` and `abstract3d==0.3.2`. The `apple` and `gpu` extras select
@@ -4750,14 +4767,14 @@ Run or install them next to the Python stack:
 | Tool | Command | Version released with 0.8.0 |
 |---|---|---|
 | Gateway web console | built into `abstractgateway`: open the link `abstractgateway serve` prints (`http://127.0.0.1:8080/console#claim=…`) | 0.10.0 |
-| Core web console | built into `abstractcore`: open the link `abstractcore serve` prints (`http://127.0.0.1:8000/console#claim=…`) | 2.22.0 |
-| Core terminal console | `cargo install abstractcore-console` (Rust 1.87+), then `abstractcore-console` (uses the `abstractcore` command). The installers do not build it: it is the console of a standalone `abstractcore serve`, and the gateway's terminal console already has its Models and Engines screens | 0.6.0 |
+| Core web console | built into `abstractcore`: open the link `abstractcore serve` prints (`http://127.0.0.1:8000/console#claim=…`) | 2.23.0 |
+| Core terminal console | `cargo install abstractcore-console` (Rust 1.87+), then `abstractcore-console` (uses the `abstractcore` command). The installers do not build it: it is the console of a standalone `abstractcore serve`, and the gateway's terminal console already has its Models and Engines screens | 0.7.0 |
 | Gateway terminal console | built by the installer (`--no-console` skips it), or `cargo install abstractgateway-console` (Rust 1.87+); then `abstractgateway-console --gateway-url http://127.0.0.1:8080 --token <admin token>` | 0.14.0 |
-| Flow Editor | the console's **Apps** page (opens at `/apps/flow/`), or on its own: `npx @abstractframework/flow --gateway-url <url>` | 0.6.0 |
-| Code Web UI | the console's **Apps** page (`/apps/code/`), or `npx @abstractframework/code --gateway-url <url>` | 0.9.0 |
-| Observer | the console's **Apps** page (`/apps/observer/`), or `npx @abstractframework/observer --gateway-url <url>` | 0.5.0 |
+| Flow Editor | the console's **Apps** page (opens at `/apps/flow/`), or on its own: `npx @abstractframework/flow --gateway-url <url>` | 0.7.0 |
+| Code Web UI | the console's **Apps** page (`/apps/code/`), or `npx @abstractframework/code --gateway-url <url>` | 0.10.0 |
+| Observer | the console's **Apps** page (`/apps/observer/`), or `npx @abstractframework/observer --gateway-url <url>` | 0.6.0 |
 | Continuum console | the console's **Apps** page (`/apps/continuum/`), or `npx @abstractframework/continuum --gateway-url <url>` | 0.6.0 |
-| Entity manager | the console's **Apps** page (`/apps/entity/`), or `npx @abstractframework/entity --gateway-url <url>` | 0.5.0 |
+| Entity manager | the console's **Apps** page (`/apps/entity/`), or `npx @abstractframework/entity --gateway-url <url>` | 0.6.0 |
 | AbstractCode terminal client | `cargo install abstractcode`, or a prebuilt binary from the [AbstractCode GitHub release](https://github.com/lpalbou/AbstractCode/releases) | 0.8.0 |
 
 The browser apps need a running gateway. The gateway installs, starts and serves them itself, on
@@ -6749,14 +6766,14 @@ The response type returned by `llm.generate(...)`.
 
 ### `__version__`
 
-The meta-package version (`0.9.0` for this release).
+The meta-package version (`0.9.1` for this release).
 
 ### `RELEASE_VERSIONS`
 
-Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.8.0:
-`abstractcore` 2.22.0, `abstractruntime` 0.8.2, `abstractagent` 0.3.17, `abstractgateway` 0.10.0,
+Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.9.1:
+`abstractcore` 2.23.0, `abstractruntime` 0.8.3, `abstractagent` 0.3.17, `abstractgateway` 0.11.1,
 `abstractskill` 0.3.0, `abstractmemory` 0.3.0, `abstractsemantics` 0.0.5, `abstractvoice` 0.13.2, `abstractvision` 0.3.33,
-`abstractmusic` 0.1.15, `abstract3d` 0.3.2, `abstractassistant` 0.11.0.
+`abstractmusic` 0.1.15, `abstract3d` 0.3.2, `abstractassistant` 0.12.0.
 
 ### `PACKAGE_DISTRIBUTIONS`
 
@@ -6766,9 +6783,9 @@ Maps each package name in `RELEASE_VERSIONS` to its PyPI distribution name (for
 ### `NPM_RELEASE_VERSIONS`
 
 The npm apps released with this version, each runnable with `npx <package>`:
-`@abstractframework/flow` 0.6.0, `@abstractframework/code` 0.9.0,
-`@abstractframework/observer` 0.5.0, `@abstractframework/continuum` 0.6.0 and
-`@abstractframework/entity` 0.5.0. They also appear as `npm_apps` in the install manifest.
+`@abstractframework/flow` 0.7.0, `@abstractframework/code` 0.10.0,
+`@abstractframework/observer` 0.6.0, `@abstractframework/continuum` 0.6.0 and
+`@abstractframework/entity` 0.6.0. They also appear as `npm_apps` in the install manifest.
 
 ### `CRATE_RELEASE_VERSIONS`
 

{abstractframework-0.9.0 → abstractframework-0.9.1}/llms.txt

@@ -185,7 +185,7 @@ Notes for LLMs working in this repo:
 - [abstractframework/__init__.py](abstractframework/__init__.py): `RELEASE_VERSIONS`, `NPM_RELEASE_VERSIONS`, `CRATE_RELEASE_VERSIONS`, `get_release_profile()`, `print_status()`.
 - [docs/installers/install-manifest.json](docs/installers/install-manifest.json): Generated install manifest, schema v2 (pins, profiles, npm apps, `bootstrap` gateway pin/scripts/flags, console-first `post_install`).
 - [scripts/install.sh](scripts/install.sh) / [scripts/install.ps1](scripts/install.ps1): The bootstrap installers.
-- abstractframework 0.8.0 pins (PyPI, `==`): abstractgateway 0.10.0, abstractassistant 0.11.0, abstractcore 2.22.0, AbstractRuntime 0.8.2, abstractagent 0.3.17, abstractskill 0.3.0, AbstractMemory 0.3.0, abstractsemantics 0.0.5, abstractvoice 0.13.2, abstractvision 0.3.33, abstractmusic 0.1.15, abstract3d 0.3.2.
+- abstractframework 0.9.1 pins (PyPI, `==`): abstractgateway 0.11.1, abstractassistant 0.12.0, abstractcore 2.23.0, AbstractRuntime 0.8.3, abstractagent 0.3.17, abstractskill 0.3.0, AbstractMemory 0.3.0, abstractsemantics 0.0.5, abstractvoice 0.13.2, abstractvision 0.3.33, abstractmusic 0.1.15, abstract3d 0.3.2.
 - Released with it: npm `@abstractframework/flow` 0.6.0, `code` 0.9.0, `observer` 0.5.0, `continuum` 0.6.0, `entity` 0.5.0 (opened through the gateway at `/apps/<app>/`, or run with `npx`); crates (`CRATE_RELEASE_VERSIONS`) `abstractgateway-console` 0.13.0 (built by the installer by default), `abstractcore-console` 0.6.0, `abstractcode` 0.8.0, `abstracttui` 0.6.0; images `ghcr.io/lpalbou/abstractgateway:0.10.0`, `ghcr.io/lpalbou/abstractcore-server:2.22.0`.
 - Profiles: light (remote-only), apple (`abstractframework[apple]`, macOS 14+ Apple Silicon), gpu (`abstractframework[gpu]`); Python 3.10-3.13 (F5-TTS voice cloning in apple/gpu needs 3.11+).
 

{abstractframework-0.9.0 → abstractframework-0.9.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "abstractframework"
-version = "0.9.0"
+version = "0.9.1"
 description = "Unified installer and documentation hub for the AbstractFramework ecosystem"
 readme = "README.md"
 license = {text = "MIT"}
@@ -48,7 +48,7 @@ requires-python = ">=3.10"
 # - Keep the meta-package aligned with the real per-package profiles (especially `abstractgateway`).
 dependencies = [
     # Durable Gateway control plane (remote-light by default).
-    "abstractgateway==0.11.0",
+    "abstractgateway==0.11.1",
 
     # Workflow authoring UI is distributed through npm as @abstractframework/flow.
     "abstractassistant==0.12.0",
@@ -82,12 +82,12 @@ dependencies = [
 # the stack by selecting the hardware-local dependency aggregates (owned by Gateway),
 # then adds user-facing apps.
 apple = [
-    "abstractgateway[apple]==0.11.0",
+    "abstractgateway[apple]==0.11.1",
     "abstractassistant[apple]==0.12.0; platform_system == \"Darwin\"",
 ]
 
 gpu = [
-    "abstractgateway[gpu]==0.11.0",
+    "abstractgateway[gpu]==0.11.1",
     "abstractassistant[gpu]==0.12.0",
 ]