PyPI - abstractframework - Versions diffs - 0.9.1__tar.gz → 0.9.2__tar.gz - Mend

abstractframework 0.9.1tar.gz → 0.9.2tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (199) hide show

{abstractframework-0.9.1 → abstractframework-0.9.2}/CHANGELOG.md RENAMED Viewed

@@ -6,6 +6,17 @@ All notable changes to AbstractFramework will be documented in this file.
 Nothing yet.
+## [0.9.2] - 2026-10-02
+### Changed
+- Installs AbstractCode web 0.10.1 (`@abstractframework/code`, `AF_NPM_APPS` in `install.sh` and
+  `install.ps1`, `NPM_RELEASE_VERSIONS`, the install manifest): New conversation is a "+" in the
+  Conversations header, the run header drops its duplicated workflow text and opens Run settings from
+  a gear icon, the live model progress line stays visible at phone width, and a subflow finishing
+  reads "subflow finished" in the Activity panel. Python pins unchanged from 0.9.1. README matrix,
+  docs and llms regenerated.
 ## [0.9.1] - 2026-10-02
 ### Changed

{abstractframework-0.9.1/abstractframework.egg-info → abstractframework-0.9.2}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.9.1
+Version: 0.9.2
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -219,7 +219,7 @@ abstractgateway-console --gateway-url http://127.0.0.1:8080 --token <admin token
 ```
 Container images are published for the gateway and the AbstractCore server:
-`ghcr.io/lpalbou/abstractgateway:0.10.0` and `ghcr.io/lpalbou/abstractcore-server:2.22.0`.
+`ghcr.io/lpalbou/abstractgateway:0.11.1` and `ghcr.io/lpalbou/abstractcore-server:2.23.0`.
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -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.1)
+### Release matrix (abstractframework 0.9.2)
 `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
@@ -391,7 +391,7 @@ and tested together.
 | PyPI | `abstractmusic` | 0.1.15 |
 | PyPI | `abstract3d` | 0.3.2 |
 | npm | `@abstractframework/flow` | 0.7.0 |
-| npm | `@abstractframework/code` | 0.10.0 |
+| npm | `@abstractframework/code` | 0.10.1 |
 | npm | `@abstractframework/observer` | 0.6.0 |
 | npm | `@abstractframework/continuum` | 0.6.0 |
 | npm | `@abstractframework/entity` | 0.6.0 |

{abstractframework-0.9.1 → abstractframework-0.9.2}/README.md RENAMED Viewed

@@ -174,7 +174,7 @@ abstractgateway-console --gateway-url http://127.0.0.1:8080 --token <admin token
 ```
 Container images are published for the gateway and the AbstractCore server:
-`ghcr.io/lpalbou/abstractgateway:0.10.0` and `ghcr.io/lpalbou/abstractcore-server:2.22.0`.
+`ghcr.io/lpalbou/abstractgateway:0.11.1` and `ghcr.io/lpalbou/abstractcore-server:2.23.0`.
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.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.1)
+### Release matrix (abstractframework 0.9.2)
 `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
@@ -346,7 +346,7 @@ and tested together.
 | PyPI | `abstractmusic` | 0.1.15 |
 | PyPI | `abstract3d` | 0.3.2 |
 | npm | `@abstractframework/flow` | 0.7.0 |
-| npm | `@abstractframework/code` | 0.10.0 |
+| npm | `@abstractframework/code` | 0.10.1 |
 | npm | `@abstractframework/observer` | 0.6.0 |
 | npm | `@abstractframework/continuum` | 0.6.0 |
 | npm | `@abstractframework/entity` | 0.6.0 |

{abstractframework-0.9.1 → abstractframework-0.9.2}/abstractframework/__init__.py RENAMED Viewed

@@ -10,7 +10,7 @@ Most implementation functionality still lives in component projects.
 from __future__ import annotations
-__version__ = "0.9.1"
+__version__ = "0.9.2"
 __author__ = "Laurent-Philippe Albou"
 __license__ = "MIT"
@@ -46,7 +46,7 @@ PACKAGE_DISTRIBUTIONS: dict[str, str] = {
 NPM_RELEASE_VERSIONS: dict[str, str] = {
     "@abstractframework/flow": "0.7.0",
-    "@abstractframework/code": "0.10.0",
+    "@abstractframework/code": "0.10.1",
     "@abstractframework/observer": "0.6.0",
     "@abstractframework/continuum": "0.6.0",
     "@abstractframework/entity": "0.6.0",

{abstractframework-0.9.1 → abstractframework-0.9.2/abstractframework.egg-info}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.9.1
+Version: 0.9.2
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -219,7 +219,7 @@ abstractgateway-console --gateway-url http://127.0.0.1:8080 --token <admin token
 ```
 Container images are published for the gateway and the AbstractCore server:
-`ghcr.io/lpalbou/abstractgateway:0.10.0` and `ghcr.io/lpalbou/abstractcore-server:2.22.0`.
+`ghcr.io/lpalbou/abstractgateway:0.11.1` and `ghcr.io/lpalbou/abstractcore-server:2.23.0`.
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -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.1)
+### Release matrix (abstractframework 0.9.2)
 `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
@@ -391,7 +391,7 @@ and tested together.
 | PyPI | `abstractmusic` | 0.1.15 |
 | PyPI | `abstract3d` | 0.3.2 |
 | npm | `@abstractframework/flow` | 0.7.0 |
-| npm | `@abstractframework/code` | 0.10.0 |
+| npm | `@abstractframework/code` | 0.10.1 |
 | npm | `@abstractframework/observer` | 0.6.0 |
 | npm | `@abstractframework/continuum` | 0.6.0 |
 | npm | `@abstractframework/entity` | 0.6.0 |

{abstractframework-0.9.1 → abstractframework-0.9.2}/docs/api.md RENAMED Viewed

@@ -55,11 +55,11 @@ The response type returned by `llm.generate(...)`.
 ### `__version__`
-The meta-package version (`0.9.1` for this release).
+The meta-package version (`0.9.2` for this release).
 ### `RELEASE_VERSIONS`
-Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.9.1:
+Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.9.2:
 `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.12.0.
@@ -72,7 +72,7 @@ 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.7.0, `@abstractframework/code` 0.10.0,
+`@abstractframework/flow` 0.7.0, `@abstractframework/code` 0.10.1,
 `@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.

{abstractframework-0.9.1 → abstractframework-0.9.2}/docs/faq.md RENAMED Viewed

@@ -34,7 +34,7 @@ No.
 | Everything at compatible versions | `pip install abstractframework` |
 | A browser app | the gateway console's **Apps** page (served at `/apps/<app>/` on the gateway), or on its own: `npx @abstractframework/<flow\|code\|observer\|continuum\|entity> --gateway-url <url>` |
 | A terminal client | `cargo install abstractcode`, `cargo install abstractgateway-console` or `cargo install abstractcore-console` |
-| A container deployment | `ghcr.io/lpalbou/abstractgateway:0.10.0` |
+| A container deployment | `ghcr.io/lpalbou/abstractgateway:0.11.1` |
 See [Install AbstractFramework](install.md) for the Light / Apple / GPU chooser. Light is
 remote-first, not reduced-functionality: multimodal and embeddings still work through remote or

{abstractframework-0.9.1 → abstractframework-0.9.2}/docs/install.md RENAMED Viewed

@@ -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.1` (with the gateway version you have);
+  upgrading to AbstractFramework 0.9.2` (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.1`, and reads your options from what is installed: whether the terminal console and `abstractcode` are
+not recorded): upgrading to AbstractFramework 0.9.2`, 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
@@ -937,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.1 pins `abstractgateway==0.11.1`, `abstractassistant==0.12.0`,
+`abstractframework` 0.9.2 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
@@ -1033,7 +1033,7 @@ Run or install them next to the Python stack:
 | 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.7.0 |
-| Code Web UI | the console's **Apps** page (`/apps/code/`), or `npx @abstractframework/code --gateway-url <url>` | 0.10.0 |
+| Code Web UI | the console's **Apps** page (`/apps/code/`), or `npx @abstractframework/code --gateway-url <url>` | 0.10.1 |
 | 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.6.0 |
@@ -1080,7 +1080,7 @@ docker run \
   -v "$PWD/runtime:/data" \
   -e ABSTRACTGATEWAY_DATA_DIR=/data \
   -e ABSTRACTGATEWAY_USER_AUTH=1 \
-  ghcr.io/lpalbou/abstractgateway:0.10.0
+  ghcr.io/lpalbou/abstractgateway:0.11.1
 ```
 This is the Light container: full framework capabilities through remote/endpoint inference, without
@@ -1088,7 +1088,7 @@ local MLX/CUDA stacks. On first start it creates `default/admin` and writes the
 `runtime/auth/bootstrap-admin-token`. Use `ghcr.io/lpalbou/abstractgateway:gpu-latest` only on an
 NVIDIA host when you explicitly want the local GPU profile (pinned tags are `<version>-gpu`, published on a best-effort basis; this image is
 experimental). The AbstractCore OpenAI-compatible server is also published as
-`ghcr.io/lpalbou/abstractcore-server:2.22.0`.
+`ghcr.io/lpalbou/abstractcore-server:2.23.0`.
 ## How installs are designed

{abstractframework-0.9.1 → abstractframework-0.9.2}/llms-full.txt RENAMED Viewed

@@ -178,7 +178,7 @@ abstractgateway-console --gateway-url http://127.0.0.1:8080 --token <admin token
 ```
 Container images are published for the gateway and the AbstractCore server:
-`ghcr.io/lpalbou/abstractgateway:0.10.0` and `ghcr.io/lpalbou/abstractcore-server:2.22.0`.
+`ghcr.io/lpalbou/abstractgateway:0.11.1` and `ghcr.io/lpalbou/abstractcore-server:2.23.0`.
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -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.1)
+### Release matrix (abstractframework 0.9.2)
 `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
@@ -350,7 +350,7 @@ and tested together.
 | PyPI | `abstractmusic` | 0.1.15 |
 | PyPI | `abstract3d` | 0.3.2 |
 | npm | `@abstractframework/flow` | 0.7.0 |
-| npm | `@abstractframework/code` | 0.10.0 |
+| npm | `@abstractframework/code` | 0.10.1 |
 | npm | `@abstractframework/observer` | 0.6.0 |
 | npm | `@abstractframework/continuum` | 0.6.0 |
 | npm | `@abstractframework/entity` | 0.6.0 |
@@ -611,8 +611,8 @@ 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.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`.
+- abstractframework 0.9.2 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.7.0, `code` 0.10.1, `observer` 0.6.0, `continuum` 0.6.0, `entity` 0.6.0 (opened through the gateway at `/apps/<app>/`, or run with `npx`); crates (`CRATE_RELEASE_VERSIONS`) `abstractgateway-console` 0.14.0 (built by the installer by default), `abstractcore-console` 0.7.0, `abstractcode` 0.8.0, `abstracttui` 0.6.0; images `ghcr.io/lpalbou/abstractgateway:0.11.1`, `ghcr.io/lpalbou/abstractcore-server:2.23.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+).
 ## Full Context
@@ -640,7 +640,7 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "abstractframework"
-version = "0.9.1"
+version = "0.9.2"
 description = "Unified installer and documentation hub for the AbstractFramework ecosystem"
 readme = "README.md"
 license = {text = "MIT"}
@@ -774,7 +774,7 @@ Most implementation functionality still lives in component projects.
 from __future__ import annotations
-__version__ = "0.9.1"
+__version__ = "0.9.2"
 __author__ = "Laurent-Philippe Albou"
 __license__ = "MIT"
@@ -810,7 +810,7 @@ PACKAGE_DISTRIBUTIONS: dict[str, str] = {
 NPM_RELEASE_VERSIONS: dict[str, str] = {
     "@abstractframework/flow": "0.7.0",
-    "@abstractframework/code": "0.10.0",
+    "@abstractframework/code": "0.10.1",
     "@abstractframework/observer": "0.6.0",
     "@abstractframework/continuum": "0.6.0",
     "@abstractframework/entity": "0.6.0",
@@ -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.1` (with the gateway version you have);
+  upgrading to AbstractFramework 0.9.2` (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.1`, and reads your options from what is installed: whether the terminal console and `abstractcode` are
+not recorded): upgrading to AbstractFramework 0.9.2`, 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
@@ -4675,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.1 pins `abstractgateway==0.11.1`, `abstractassistant==0.12.0`,
+`abstractframework` 0.9.2 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
@@ -4771,7 +4771,7 @@ Run or install them next to the Python stack:
 | 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.7.0 |
-| Code Web UI | the console's **Apps** page (`/apps/code/`), or `npx @abstractframework/code --gateway-url <url>` | 0.10.0 |
+| Code Web UI | the console's **Apps** page (`/apps/code/`), or `npx @abstractframework/code --gateway-url <url>` | 0.10.1 |
 | 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.6.0 |
@@ -4818,7 +4818,7 @@ docker run \
   -v "$PWD/runtime:/data" \
   -e ABSTRACTGATEWAY_DATA_DIR=/data \
   -e ABSTRACTGATEWAY_USER_AUTH=1 \
-  ghcr.io/lpalbou/abstractgateway:0.10.0
+  ghcr.io/lpalbou/abstractgateway:0.11.1
 ```
 This is the Light container: full framework capabilities through remote/endpoint inference, without
@@ -4826,7 +4826,7 @@ local MLX/CUDA stacks. On first start it creates `default/admin` and writes the
 `runtime/auth/bootstrap-admin-token`. Use `ghcr.io/lpalbou/abstractgateway:gpu-latest` only on an
 NVIDIA host when you explicitly want the local GPU profile (pinned tags are `<version>-gpu`, published on a best-effort basis; this image is
 experimental). The AbstractCore OpenAI-compatible server is also published as
-`ghcr.io/lpalbou/abstractcore-server:2.22.0`.
+`ghcr.io/lpalbou/abstractcore-server:2.23.0`.
 ## How installs are designed
@@ -6073,7 +6073,7 @@ No.
 | Everything at compatible versions | `pip install abstractframework` |
 | A browser app | the gateway console's **Apps** page (served at `/apps/<app>/` on the gateway), or on its own: `npx @abstractframework/<flow\|code\|observer\|continuum\|entity> --gateway-url <url>` |
 | A terminal client | `cargo install abstractcode`, `cargo install abstractgateway-console` or `cargo install abstractcore-console` |
-| A container deployment | `ghcr.io/lpalbou/abstractgateway:0.10.0` |
+| A container deployment | `ghcr.io/lpalbou/abstractgateway:0.11.1` |
 See [Install AbstractFramework](install.md) for the Light / Apple / GPU chooser. Light is
 remote-first, not reduced-functionality: multimodal and embeddings still work through remote or
@@ -6766,11 +6766,11 @@ The response type returned by `llm.generate(...)`.
 ### `__version__`
-The meta-package version (`0.9.1` for this release).
+The meta-package version (`0.9.2` for this release).
 ### `RELEASE_VERSIONS`
-Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.9.1:
+Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.9.2:
 `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.12.0.
@@ -6783,7 +6783,7 @@ 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.7.0, `@abstractframework/code` 0.10.0,
+`@abstractframework/flow` 0.7.0, `@abstractframework/code` 0.10.1,
 `@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.

{abstractframework-0.9.1 → abstractframework-0.9.2}/llms.txt RENAMED Viewed

@@ -185,8 +185,8 @@ 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.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`.
+- abstractframework 0.9.2 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.7.0, `code` 0.10.1, `observer` 0.6.0, `continuum` 0.6.0, `entity` 0.6.0 (opened through the gateway at `/apps/<app>/`, or run with `npx`); crates (`CRATE_RELEASE_VERSIONS`) `abstractgateway-console` 0.14.0 (built by the installer by default), `abstractcore-console` 0.7.0, `abstractcode` 0.8.0, `abstracttui` 0.6.0; images `ghcr.io/lpalbou/abstractgateway:0.11.1`, `ghcr.io/lpalbou/abstractcore-server:2.23.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+).
 ## Full Context

{abstractframework-0.9.1 → abstractframework-0.9.2}/pyproject.toml RENAMED Viewed

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "abstractframework"
-version = "0.9.1"
+version = "0.9.2"
 description = "Unified installer and documentation hub for the AbstractFramework ecosystem"
 readme = "README.md"
 license = {text = "MIT"}

{abstractframework-0.9.1 → abstractframework-0.9.2}/scripts/install.sh RENAMED Viewed

@@ -127,10 +127,10 @@ AF_GATEWAY_PIN_DEFAULT="0.11.1"
 # minus the gateway itself and the Assistant, a separate app). They go to `uv tool install` as
 # constraints, so an install or an upgrade lands on exactly the tested matrix, never on
 # whatever newer library satisfies the gateway's floors. test_inventory.sh fails on drift.
-AF_FRAMEWORK_VERSION="0.9.1"
+AF_FRAMEWORK_VERSION="0.9.2"
 AF_PY_MATRIX="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"
 AF_PYTHON="3.12"
-AF_NPM_APPS="@abstractframework/flow@0.7.0 @abstractframework/code@0.10.0 @abstractframework/observer@0.6.0 @abstractframework/continuum@0.6.0 @abstractframework/entity@0.6.0"
+AF_NPM_APPS="@abstractframework/flow@0.7.0 @abstractframework/code@0.10.1 @abstractframework/observer@0.6.0 @abstractframework/continuum@0.6.0 @abstractframework/entity@0.6.0"
 AF_CRATE_CONSOLE="abstractgateway-console@0.14.0"
 AF_CRATE_CODE_CLI="abstractcode@0.8.0"
 # The user commands of the gateway's own environment exposed next to `abstractgateway` and