abstractframework 0.7.1__tar.gz → 0.7.2__tar.gz

{abstractframework-0.7.1 → abstractframework-0.7.2}/CHANGELOG.md

@@ -4,6 +4,48 @@ All notable changes to AbstractFramework will be documented in this file.
 
 ## [Unreleased]
 
+## [0.7.2] - 2026-09-30
+
+Every screen works on phones, tablets and any window size. Pins: AbstractGateway 0.9.0 and
+AbstractCore 2.21.0 (responsive web consoles); the browser apps Flow 0.5.0, Code 0.8.0, Observer
+0.4.0, Continuum 0.5.0 and Entity 0.4.0 (responsive layouts, on `@abstractframework/ui-kit` 0.3.2
+and `panel-chat` 0.2.1). Every other version is unchanged from 0.7.1.
+
+### Changed
+
+- **Responsive everywhere.** The gateway and AbstractCore web consoles and the five browser apps
+  follow one responsive system: the framework breakpoints (480, 768, 1024 and 1440 px wide, plus
+  500 px tall for phone landscape), sidebars that become drawers below 1024 px, dialogs that open
+  as bottom sheets on small screens, 44 px touch targets and 16 px form fields on touch screens, and
+  pages that respect the notch and home-indicator areas. See each app's changelog for details.
+
+### Fixed
+
+- **A new email automation reacts to the mail you send to test it.** Mail sent right after
+  creating a "When an email arrives" automation could be missed: the mail watcher, which reads
+  nothing until an email automation exists, marked where new mail starts up to a minute later and
+  treated that minute's mail as already there. Creating an email automation now wakes it and the
+  mark is taken within seconds.
+- **A new or resumed email automation no longer runs on old mail.** After a time with no email
+  automation active, the next one received everything that had arrived meanwhile as new mail. That
+  mail is now treated as already there (mail that arrives while the gateway itself is down is
+  still read when it is back).
+- **An upgrade right after a release no longer installs less.** When one of PyPI's mirrors had not
+  yet listed a version the release pins, uv answered `there is no version of
+  abstractgateway[gpu]==0.8.1`, and the installer took that for a system without the voice
+  wheels: the 0.7.1 upgrade of a Linux machine went through without local voice (a second run was
+  clean). install.sh and install.ps1 (and so the consoles' **Update** action, which runs install.sh) now recognise that
+  case from uv's exit code 1, its resolution failure, and its exact-pin wording for a package the
+  installer itself pinned (or from a download of that pinned version's own file that answers 404:
+  the list shows it, the file is not served yet), and run the same install again, with every feature, after 15 s, 30 s,
+  60 s and 120 s waits (8 attempts, about 10 minutes), printing `PyPI hasn't published
+  abstractgateway 0.8.1 to every mirror yet; retrying in 30 s (attempt 3/8)`. After that they stop
+  with the cause and what to do, never with a smaller install. The fallbacks for systems without
+  the voice or llama.cpp wheels are unchanged. The voice requirement now carries the release's
+  AbstractVoice version (`abstractvoice[supertonic,stt]==0.13.2`), which the release matrix already
+  enforced, so uv names a missing AbstractVoice in the same exact-pin form. See
+  [Right after a release](docs/install.md#right-after-a-release).
+
 ## [0.7.1] - 2026-09-30
 
 A patch release. Pins: AbstractCore 2.20.2, AbstractRuntime 0.8.1 and AbstractGateway 0.8.1; every

{abstractframework-0.7.1/abstractframework.egg-info → abstractframework-0.7.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.7.1
+Version: 0.7.2
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,9 +23,9 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.8.1
+Requires-Dist: abstractgateway==0.9.0
 Requires-Dist: abstractassistant==0.10.0
-Requires-Dist: abstractcore==2.20.2
+Requires-Dist: abstractcore==2.21.0
 Requires-Dist: AbstractRuntime==0.8.1
 Requires-Dist: abstractagent==0.3.17
 Requires-Dist: abstractskill==0.3.0
@@ -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.8.1; extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.9.0; extra == "apple"
 Requires-Dist: abstractassistant[apple]==0.10.0; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.8.1; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.9.0; extra == "gpu"
 Requires-Dist: abstractassistant[gpu]==0.10.0; extra == "gpu"
 Dynamic: license-file
 
@@ -217,7 +217,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.8.1` and `ghcr.io/lpalbou/abstractcore-server:2.20.2`.
+`ghcr.io/lpalbou/abstractgateway:0.9.0` and `ghcr.io/lpalbou/abstractcore-server:2.21.0`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -363,7 +363,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.7.1)
+### Release matrix (abstractframework 0.7.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
@@ -372,9 +372,9 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.8.1 |
+| PyPI | `abstractgateway` | 0.9.0 |
 | PyPI | `abstractassistant` | 0.10.0 |
-| PyPI | `abstractcore` | 2.20.2 |
+| PyPI | `abstractcore` | 2.21.0 |
 | PyPI | `AbstractRuntime` | 0.8.1 |
 | PyPI | `abstractagent` | 0.3.17 |
 | PyPI | `abstractskill` | 0.3.0 |
@@ -384,17 +384,17 @@ and tested together.
 | PyPI | `abstractvision` | 0.3.33 |
 | PyPI | `abstractmusic` | 0.1.15 |
 | PyPI | `abstract3d` | 0.3.2 |
-| npm | `@abstractframework/flow` | 0.4.0 |
-| npm | `@abstractframework/code` | 0.7.0 |
-| npm | `@abstractframework/observer` | 0.3.0 |
-| npm | `@abstractframework/continuum` | 0.4.0 |
-| npm | `@abstractframework/entity` | 0.3.0 |
+| npm | `@abstractframework/flow` | 0.5.0 |
+| npm | `@abstractframework/code` | 0.8.0 |
+| npm | `@abstractframework/observer` | 0.4.0 |
+| npm | `@abstractframework/continuum` | 0.5.0 |
+| npm | `@abstractframework/entity` | 0.4.0 |
 | crates.io | `abstractcode` | 0.7.1 |
 | crates.io | `abstractgateway-console` | 0.12.0 |
 | crates.io | `abstractcore-console` | 0.5.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.8.1 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.20.2 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.9.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.21.0 |
 
 `abstract3d` (pinned above) comes with AbstractCore in every profile. The optional add-on that is
 not part of any profile installs separately: `pip install abstractcamera` (0.2.1). `abstractskill` (pinned above)

{abstractframework-0.7.1 → abstractframework-0.7.2}/README.md

@@ -172,7 +172,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.8.1` and `ghcr.io/lpalbou/abstractcore-server:2.20.2`.
+`ghcr.io/lpalbou/abstractgateway:0.9.0` and `ghcr.io/lpalbou/abstractcore-server:2.21.0`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -318,7 +318,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.7.1)
+### Release matrix (abstractframework 0.7.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
@@ -327,9 +327,9 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.8.1 |
+| PyPI | `abstractgateway` | 0.9.0 |
 | PyPI | `abstractassistant` | 0.10.0 |
-| PyPI | `abstractcore` | 2.20.2 |
+| PyPI | `abstractcore` | 2.21.0 |
 | PyPI | `AbstractRuntime` | 0.8.1 |
 | PyPI | `abstractagent` | 0.3.17 |
 | PyPI | `abstractskill` | 0.3.0 |
@@ -339,17 +339,17 @@ and tested together.
 | PyPI | `abstractvision` | 0.3.33 |
 | PyPI | `abstractmusic` | 0.1.15 |
 | PyPI | `abstract3d` | 0.3.2 |
-| npm | `@abstractframework/flow` | 0.4.0 |
-| npm | `@abstractframework/code` | 0.7.0 |
-| npm | `@abstractframework/observer` | 0.3.0 |
-| npm | `@abstractframework/continuum` | 0.4.0 |
-| npm | `@abstractframework/entity` | 0.3.0 |
+| npm | `@abstractframework/flow` | 0.5.0 |
+| npm | `@abstractframework/code` | 0.8.0 |
+| npm | `@abstractframework/observer` | 0.4.0 |
+| npm | `@abstractframework/continuum` | 0.5.0 |
+| npm | `@abstractframework/entity` | 0.4.0 |
 | crates.io | `abstractcode` | 0.7.1 |
 | crates.io | `abstractgateway-console` | 0.12.0 |
 | crates.io | `abstractcore-console` | 0.5.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.8.1 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.20.2 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.9.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.21.0 |
 
 `abstract3d` (pinned above) comes with AbstractCore in every profile. The optional add-on that is
 not part of any profile installs separately: `pip install abstractcamera` (0.2.1). `abstractskill` (pinned above)

{abstractframework-0.7.1 → abstractframework-0.7.2}/abstractframework/__init__.py

@@ -10,15 +10,15 @@ Most implementation functionality still lives in component projects.
 
 from __future__ import annotations
 
-__version__ = "0.7.1"
+__version__ = "0.7.2"
 __author__ = "Laurent-Philippe Albou"
 __license__ = "MIT"
 
 RELEASE_VERSIONS: dict[str, str] = {
-    "abstractcore": "2.20.2",
+    "abstractcore": "2.21.0",
     "abstractruntime": "0.8.1",
     "abstractagent": "0.3.17",
-    "abstractgateway": "0.8.1",
+    "abstractgateway": "0.9.0",
     "abstractskill": "0.3.0",
     "abstractmemory": "0.3.0",
     "abstractsemantics": "0.0.5",
@@ -45,11 +45,11 @@ PACKAGE_DISTRIBUTIONS: dict[str, str] = {
 }
 
 NPM_RELEASE_VERSIONS: dict[str, str] = {
-    "@abstractframework/flow": "0.4.0",
-    "@abstractframework/code": "0.7.0",
-    "@abstractframework/observer": "0.3.0",
-    "@abstractframework/continuum": "0.4.0",
-    "@abstractframework/entity": "0.3.0",
+    "@abstractframework/flow": "0.5.0",
+    "@abstractframework/code": "0.8.0",
+    "@abstractframework/observer": "0.4.0",
+    "@abstractframework/continuum": "0.5.0",
+    "@abstractframework/entity": "0.4.0",
 }
 
 # Terminal tools published on crates.io alongside this release (installed with `cargo install`,

{abstractframework-0.7.1 → abstractframework-0.7.2/abstractframework.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.7.1
+Version: 0.7.2
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,9 +23,9 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.8.1
+Requires-Dist: abstractgateway==0.9.0
 Requires-Dist: abstractassistant==0.10.0
-Requires-Dist: abstractcore==2.20.2
+Requires-Dist: abstractcore==2.21.0
 Requires-Dist: AbstractRuntime==0.8.1
 Requires-Dist: abstractagent==0.3.17
 Requires-Dist: abstractskill==0.3.0
@@ -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.8.1; extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.9.0; extra == "apple"
 Requires-Dist: abstractassistant[apple]==0.10.0; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.8.1; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.9.0; extra == "gpu"
 Requires-Dist: abstractassistant[gpu]==0.10.0; extra == "gpu"
 Dynamic: license-file
 
@@ -217,7 +217,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.8.1` and `ghcr.io/lpalbou/abstractcore-server:2.20.2`.
+`ghcr.io/lpalbou/abstractgateway:0.9.0` and `ghcr.io/lpalbou/abstractcore-server:2.21.0`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -363,7 +363,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.7.1)
+### Release matrix (abstractframework 0.7.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
@@ -372,9 +372,9 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.8.1 |
+| PyPI | `abstractgateway` | 0.9.0 |
 | PyPI | `abstractassistant` | 0.10.0 |
-| PyPI | `abstractcore` | 2.20.2 |
+| PyPI | `abstractcore` | 2.21.0 |
 | PyPI | `AbstractRuntime` | 0.8.1 |
 | PyPI | `abstractagent` | 0.3.17 |
 | PyPI | `abstractskill` | 0.3.0 |
@@ -384,17 +384,17 @@ and tested together.
 | PyPI | `abstractvision` | 0.3.33 |
 | PyPI | `abstractmusic` | 0.1.15 |
 | PyPI | `abstract3d` | 0.3.2 |
-| npm | `@abstractframework/flow` | 0.4.0 |
-| npm | `@abstractframework/code` | 0.7.0 |
-| npm | `@abstractframework/observer` | 0.3.0 |
-| npm | `@abstractframework/continuum` | 0.4.0 |
-| npm | `@abstractframework/entity` | 0.3.0 |
+| npm | `@abstractframework/flow` | 0.5.0 |
+| npm | `@abstractframework/code` | 0.8.0 |
+| npm | `@abstractframework/observer` | 0.4.0 |
+| npm | `@abstractframework/continuum` | 0.5.0 |
+| npm | `@abstractframework/entity` | 0.4.0 |
 | crates.io | `abstractcode` | 0.7.1 |
 | crates.io | `abstractgateway-console` | 0.12.0 |
 | crates.io | `abstractcore-console` | 0.5.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.8.1 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.20.2 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.9.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.21.0 |
 
 `abstract3d` (pinned above) comes with AbstractCore in every profile. The optional add-on that is
 not part of any profile installs separately: `pip install abstractcamera` (0.2.1). `abstractskill` (pinned above)

{abstractframework-0.7.1 → abstractframework-0.7.2}/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_index_lag.py
 tests/test_install_profiles.py
 tests/test_install_ps1_gpu_stack.py
 tests/test_install_ps1_own_gateway.py

{abstractframework-0.7.1 → abstractframework-0.7.2}/abstractframework.egg-info/requires.txt

@@ -1,6 +1,6 @@
-abstractgateway==0.8.1
+abstractgateway==0.9.0
 abstractassistant==0.10.0
-abstractcore==2.20.2
+abstractcore==2.21.0
 AbstractRuntime==0.8.1
 abstractagent==0.3.17
 abstractskill==0.3.0
@@ -12,11 +12,11 @@ abstractmusic==0.1.15
 abstract3d==0.3.2
 
 [apple]
-abstractgateway[apple]==0.8.1
+abstractgateway[apple]==0.9.0
 
 [apple:platform_system == "Darwin"]
 abstractassistant[apple]==0.10.0
 
 [gpu]
-abstractgateway[gpu]==0.8.1
+abstractgateway[gpu]==0.9.0
 abstractassistant[gpu]==0.10.0

{abstractframework-0.7.1 → abstractframework-0.7.2}/docs/api.md

@@ -55,12 +55,12 @@ The response type returned by `llm.generate(...)`.
 
 ### `__version__`
 
-The meta-package version (`0.7.1` for this release).
+The meta-package version (`0.7.2` for this release).
 
 ### `RELEASE_VERSIONS`
 
-Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.7.1:
-`abstractcore` 2.20.2, `abstractruntime` 0.8.1, `abstractagent` 0.3.17, `abstractgateway` 0.8.1,
+Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.7.2:
+`abstractcore` 2.21.0, `abstractruntime` 0.8.1, `abstractagent` 0.3.17, `abstractgateway` 0.9.0,
 `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.10.0.
 
@@ -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.4.0, `@abstractframework/code` 0.7.0,
-`@abstractframework/observer` 0.3.0, `@abstractframework/continuum` 0.4.0 and
-`@abstractframework/entity` 0.3.0. They also appear as `npm_apps` in the install manifest.
+`@abstractframework/flow` 0.5.0, `@abstractframework/code` 0.8.0,
+`@abstractframework/observer` 0.4.0, `@abstractframework/continuum` 0.5.0 and
+`@abstractframework/entity` 0.4.0. They also appear as `npm_apps` in the install manifest.
 
 ### `CRATE_RELEASE_VERSIONS`
 

{abstractframework-0.7.1 → abstractframework-0.7.2}/docs/faq.md

@@ -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.8.1` |
+| A container deployment | `ghcr.io/lpalbou/abstractgateway:0.9.0` |
 
 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.7.1 → abstractframework-0.7.2}/docs/install.md

@@ -100,8 +100,38 @@ where it stopped.
 | `the gateway did not answer … within 180 s` | Restart the computer (the login item starts it) or run the installer again, then open `http://127.0.0.1:8080/console`. |
 | The browser page asks for a token | The one-time sign-in link lasts 10 minutes. Run the installer again: it opens a fresh link. |
 | `another AbstractFramework installer is already running` | An installer, or an **Update** from a console or the menu-bar icon, is running for this data directory. Wait until it finishes, then run the line again. |
+| `PyPI hasn't published abstractgateway 0.8.1 to every mirror yet; retrying in 30 s (attempt 3/8)` | Nothing to do: a release published minutes ago has not reached every PyPI mirror yet. The installer waits and runs the same install again (see [Right after a release](#right-after-a-release)). |
+| `PyPI still does not list … after 8 attempts over about 10 minutes` | The package index this computer reads has not caught up after 10 minutes (often a company package mirror set in `UV_INDEX_URL`, `PIP_INDEX_URL` or `uv.toml`). Nothing was left out and the previous install is unchanged. Run the installer again in a few minutes; with a mirror, ask its administrator to refresh the package the message names. |
 | Anything else | Run the installer again. If it stops at the same step, report it with the log file named at the end of the message (`~/Library/Application Support/AbstractGateway/logs/install-….log`). |
 
+### Right after a release
+
+For a few minutes after a release, some of PyPI's mirrors can still serve a package list without
+the new versions. uv then answers `there is no version of abstractgateway==0.8.1` even though the
+release is published. The installer (install.sh and install.ps1; the **Update** action of the
+consoles and the menu-bar icon runs install.sh on macOS and Linux, and gives the install.ps1 line to
+paste on Windows) treats that as a delay:
+
+- it runs the **same** install again, with every part it was asked for (local voice, llama.cpp,
+  PyTorch's CUDA build): a delay never makes it install less;
+- it waits 15 s, 30 s, 60 s, then 120 s between attempts, 8 attempts over about 10 minutes, and
+  says so: `PyPI hasn't published abstractgateway 0.8.1 to every mirror yet; retrying in 30 s
+  (attempt 3/8)`;
+- if the version is still missing after that, it stops with the cause and what to do. uv stops
+  before it changes anything, so the previous install keeps working.
+
+Only these cases wait, for a package at the exact version this release pins (the gateway and the
+release's libraries: AbstractCore, AbstractRuntime, AbstractVoice, ...): uv exits with code 1, its
+output contains uv's resolution failure (`No solution found when resolving dependencies`) and it
+says `there is no version of <package>==<version>`; or the download of that version's own file
+answered `HTTP status client error (404` (`Failed to fetch: .../<package>-<version>-py3-none-any.whl`:
+the package list already shows the new version but the file is not served yet; uv exits with code
+1, or 2 when even the file's metadata answered 404). A server error (5xx) or a refused download
+(403) is not a delay and is handled as before. The voice
+requirement carries its pinned version for this reason. Every other failure is handled as before: a system
+without the voice or llama.cpp wheels still installs without them and the summary says so. An
+install with `--pin latest` or `--from` pins nothing, so nothing is waited for.
+
 ## Upgrade
 
 ### Upgrade everything (recommended)
@@ -132,7 +162,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.7.1` (with the gateway version you have);
+  upgrading to AbstractFramework 0.7.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
@@ -160,7 +190,8 @@ The line always runs the installer of the latest AbstractFramework release. It:
   so a gateway of this data directory that you started yourself on the install's port is taken for
   the login item and left running (stop it, then re-run the installer, to have the login item's);
 - asks PyPI again for the packages it pins (`uv tool install --refresh-package ...`), so a release
-  published minutes earlier installs without clearing uv's cache;
+  published minutes earlier installs without clearing uv's cache, and waits for PyPI's mirrors when
+  they have not caught up yet ([Right after a release](#right-after-a-release));
 - never leaves the gateway stopped: when the login item cannot be registered, the gateway starts in
   the background and the summary says how to turn start at login on;
 - ends with what changed, old -> new, under **Changes** (`Changes: none` when nothing moved), and
@@ -172,7 +203,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.7.1`, and reads your options from what is installed: whether the terminal console and `abstractcode` are
+not recorded): upgrading to AbstractFramework 0.7.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. You can also repeat your
@@ -294,7 +325,7 @@ The terminal console and an `abstractcode` built by the installer are upgraded b
 
 ```bash
 abstractgateway --version                    # the installed gateway
-uv tool list --show-version-specifiers       # the gateway uv tool and its pin ([required: ==0.8.1])
+uv tool list --show-version-specifiers       # the gateway uv tool and its pin ([required: ==0.9.0])
 abstractgateway-console --version            # the terminal console
 abstractcode --version                       # AbstractCode's terminal client
 abstractgateway apps list                    # the apps: installed and latest
@@ -370,13 +401,15 @@ 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.8.1"`, from prebuilt wheels
+   `uv tool install --python 3.12 "abstractgateway[<profile>,tray]==0.9.0"`, 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]"`: Supertonic text-to-speech and Whisper speech-to-text,
-   both on CPU (skipped on musl Linux and macOS before 13, where no wheels exist; Windows ARM64 gets
-   Supertonic only). If those packages do not install on a system (for example glibc older than
-   2.28), the gateway is installed without them and the summary says so. The same install puts
+   `--with "abstractvoice[supertonic,stt]==0.13.2"` (the release's AbstractVoice): Supertonic
+   text-to-speech and Whisper speech-to-text, both on CPU (skipped on musl Linux and macOS before
+   13, where no wheels exist; Windows ARM64 gets Supertonic only). If those packages do not install
+   on a system (for example glibc older than 2.28), the gateway is installed without them and the
+   summary says so. A release that PyPI has not yet published to every mirror never causes that:
+   see [Right after a release](#right-after-a-release). The same install puts
    AbstractCore's commands and those of its voice, vision and music packages on PATH next to the
    gateway's (`--with-executables-from`; `--no-core-cli` leaves them out): see
    [Commands you get](#commands-you-get).
@@ -720,7 +753,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.8.1"    # [apple,tray] or [gpu,tray] for local engines
+uv tool install --python 3.12 "abstractgateway[tray]==0.9.0"    # [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
@@ -840,8 +873,8 @@ 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.7.1 pins `abstractgateway==0.8.1`, `abstractassistant==0.10.0`,
-`abstractcore==2.20.2`, `AbstractRuntime==0.8.1`, `abstractagent==0.3.17`, `abstractskill==0.3.0`,
+`abstractframework` 0.7.2 pins `abstractgateway==0.9.0`, `abstractassistant==0.10.0`,
+`abstractcore==2.21.0`, `AbstractRuntime==0.8.1`, `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
 `abstractgateway[apple|gpu]` and `abstractassistant[apple|gpu]` at the same versions
@@ -929,17 +962,17 @@ Then run `abstractframework doctor`.
 The browser apps and the Rust terminal tools are not Python packages, so no profile installs them.
 Run or install them next to the Python stack:
 
-| Tool | Command | Version released with 0.7.1 |
+| Tool | Command | Version released with 0.7.2 |
 |---|---|---|
-| Gateway web console | built into `abstractgateway`: open the link `abstractgateway serve` prints (`http://127.0.0.1:8080/console#claim=…`) | 0.8.1 |
-| Core web console | built into `abstractcore`: open the link `abstractcore serve` prints (`http://127.0.0.1:8000/console#claim=…`) | 2.20.2 |
+| Gateway web console | built into `abstractgateway`: open the link `abstractgateway serve` prints (`http://127.0.0.1:8080/console#claim=…`) | 0.9.0 |
+| Core web console | built into `abstractcore`: open the link `abstractcore serve` prints (`http://127.0.0.1:8000/console#claim=…`) | 2.21.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.5.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.12.0 |
-| Flow Editor | the console's **Apps** page (opens at `/apps/flow/`), or on its own: `npx @abstractframework/flow --gateway-url <url>` | 0.4.0 |
-| Code Web UI | the console's **Apps** page (`/apps/code/`), or `npx @abstractframework/code --gateway-url <url>` | 0.7.0 |
-| Observer | the console's **Apps** page (`/apps/observer/`), or `npx @abstractframework/observer --gateway-url <url>` | 0.3.0 |
-| Continuum console | the console's **Apps** page (`/apps/continuum/`), or `npx @abstractframework/continuum --gateway-url <url>` | 0.4.0 |
-| Entity manager | the console's **Apps** page (`/apps/entity/`), or `npx @abstractframework/entity --gateway-url <url>` | 0.3.0 |
+| Flow Editor | the console's **Apps** page (opens at `/apps/flow/`), or on its own: `npx @abstractframework/flow --gateway-url <url>` | 0.5.0 |
+| Code Web UI | the console's **Apps** page (`/apps/code/`), or `npx @abstractframework/code --gateway-url <url>` | 0.8.0 |
+| Observer | the console's **Apps** page (`/apps/observer/`), or `npx @abstractframework/observer --gateway-url <url>` | 0.4.0 |
+| Continuum console | the console's **Apps** page (`/apps/continuum/`), or `npx @abstractframework/continuum --gateway-url <url>` | 0.5.0 |
+| Entity manager | the console's **Apps** page (`/apps/entity/`), or `npx @abstractframework/entity --gateway-url <url>` | 0.4.0 |
 | AbstractCode terminal client | `cargo install abstractcode`, or a prebuilt binary from the [AbstractCode GitHub release](https://github.com/lpalbou/AbstractCode/releases) | 0.7.1 |
 
 The browser apps need a running gateway. The gateway installs, starts and serves them itself, on
@@ -983,7 +1016,7 @@ docker run \
   -v "$PWD/runtime:/data" \
   -e ABSTRACTGATEWAY_DATA_DIR=/data \
   -e ABSTRACTGATEWAY_USER_AUTH=1 \
-  ghcr.io/lpalbou/abstractgateway:0.8.1
+  ghcr.io/lpalbou/abstractgateway:0.9.0
 ```
 
 This is the Light container: full framework capabilities through remote/endpoint inference, without
@@ -991,7 +1024,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.20.2`.
+`ghcr.io/lpalbou/abstractcore-server:2.21.0`.
 
 ## How installs are designed