abstractframework 0.4.0__tar.gz → 0.4.2__tar.gz

{abstractframework-0.4.0 → abstractframework-0.4.2}/CHANGELOG.md

@@ -4,6 +4,96 @@ All notable changes to AbstractFramework will be documented in this file.
 
 ## [Unreleased]
 
+## [0.4.2] - 2026-09-27
+
+A patch release for the uninstaller and two package updates.
+
+### Fixed
+
+- **Uninstall stops the whole gateway before deleting.** Removing the login item does not wait for
+  the gateway to exit, and some of its children (an entity's own-time loop, model downloads, the
+  apps it started, the tray) kept writing into the data dir, so the uninstall failed with
+  "Directory not empty". The uninstaller now waits up to 20 s for the whole gateway process tree to
+  exit, then stops what is left and says which processes it stopped.
+- **Every deletion is verified.** Each location is deleted, retried while something re-creates it,
+  then checked; a folder that cannot be deleted (or comes back) stops the uninstaller with a
+  listing of what remains and the programs holding it. The failure text advises running the
+  uninstaller again, never the installer.
+- **`--purge` removes all your local data**: besides the gateway data dir, its login-item logs and
+  its download cache, it removes the Assistant's sessions, snapshots and preferences
+  (`~/.abstractassistant`, the macOS preferences file and the cached preferences) and
+  AbstractCode's login and preferences (`~/.abstractcode`). Model weights and shared caches are
+  kept and named. The purge question names what it deletes; `--print` lists each command; a
+  second run prints "nothing to do". `install.sh` accepts `--yes`.
+- **Uninstall safety**: `--purge` refuses (exit 2, nothing changed) a data dir that is the root,
+  your home folder or any folder above it, and a hand-given `--data-dir` that is not a gateway data
+  dir (for example `~/Library` or `~/Documents`). A process is stopped only when it runs from this
+  install's tool environment or is one of this data dir's apps; a stale pid file is left alone.
+  `--data-dir` is made absolute once, and paths are resolved before the mount guard
+  (`/tmp` vs `/private/tmp`, a linked home).
+- The one-line uninstaller and the installer package's "Uninstall AbstractFramework.command" both
+  carry these fixes. Known Linux limits: BusyBox `ps` (Alpine) lacks the columns the process scan
+  reads, so only the systemd stop applies there; a relative `XDG_CACHE_HOME` is used as given.
+
+### Changed (pins)
+
+- **abstractagent 0.3.16** (was 0.3.15): the announced-tool-use text heuristic added in 0.3.15 is
+  removed; the loops behave as in 0.3.14 plus the CodeAct/MemAct crash fix from 0.3.15.
+- **abstractassistant 0.7.0** (was 0.6.1): the session list and transcripts come from the gateway;
+  local files are a rebuildable cache. The first launch moves sessions the gateway does not know to
+  `sessions-legacy/` and deletes nothing. The list shows your own sessions by default, with an
+  "All gateway sessions" toggle.
+- The pins apply to the base install and to the `apple` / `gpu` extras
+  (`abstractassistant[apple|gpu]==0.7.0`). Unchanged: abstractgateway 0.5.1, abstractcore 2.16.1,
+  AbstractRuntime 0.5.1, abstractskill 0.3.0, AbstractMemory 0.3.0, abstractsemantics 0.0.5,
+  abstractvoice 0.11.4, abstractvision 0.3.29, abstractmusic 0.1.15, the browser apps, `abstractcode`
+  0.6.0 and `abstractgateway-console` 0.9.0.
+- Container images are unchanged: `ghcr.io/lpalbou/abstractgateway:0.5.1` and
+  `ghcr.io/lpalbou/abstractcore-server:2.16.1`.
+
+## [0.4.1] - 2026-09-26
+
+A patch release for local MLX models and long-running flows.
+
+### Changed (pins)
+
+- **AbstractRuntime 0.5.1** (was 0.5.0): a wait is resumed at most once. A flow whose Agent or
+  subflow node waits on a child could run that child twice when the child finished exactly as the
+  runner ticked, doubling the run's time and tokens; a racing second resume is refused with a
+  typed `StaleResumeError`.
+- **abstractcore 2.16.1** (was 2.16.0): MLX prompts are rendered by the model's own chat template
+  on every MLX lane (mlx-lm, native MTP, vision, JSON-constrained). Earlier turns keep their tool
+  calls, tool results are rendered as the template renders them, and the generation prompt opens
+  thinking when the template does; agent loops on Qwen3.x MLX builds with thinking on used to stop
+  at the third iteration with a one-sentence announcement and no tool call. A malformed tool-call
+  argument in the history never disables that renderer, and each response's metadata names the
+  renderer used. Prompt-cache artifacts rendered by the previous renderer are rebuilt, not reused.
+- **abstractagent 0.3.15** (was 0.3.14): fixes a crash in 0.3.13 and 0.3.14 (CodeAct and MemAct
+  raised `NameError` when a delegated agent's profile set `thinking`). A reply that announces tool
+  use without calling a tool, or whose tool calls could not run, is re-prompted once with the
+  failed reply quoted, and ends with `stop_reason.code = "no_tool_call"` rather than being
+  published as the answer; the long-reply nudge is bounded to once per step.
+- **abstractgateway 0.5.1** (was 0.5.0): requires the three packages above; when two runner paths
+  race to resume the same parent, the losing attempt is logged at debug level instead of as an
+  error.
+- **abstractassistant 0.6.1** (was 0.6.0): the Settings window opens inside the screen; the
+  default screen edge gap is 12 px.
+- The pins apply to the base install and to the `apple` / `gpu` extras
+  (`abstractgateway[apple|gpu]==0.5.1`, `abstractassistant[apple|gpu]==0.6.1`); the bootstrap
+  scripts install `abstractgateway[<profile>,tray]==0.5.1`. Unchanged: abstractskill 0.3.0,
+  AbstractMemory 0.3.0, abstractsemantics 0.0.5, abstractvoice 0.11.4, abstractvision 0.3.29,
+  abstractmusic 0.1.15, the browser apps (flow 0.3.21, code 0.5.0, observer 0.1.13,
+  continuum 0.3.2, entity 0.2.2), `abstractcode` 0.6.0 and `abstractgateway-console` 0.9.0.
+- Container images released with it: `ghcr.io/lpalbou/abstractgateway:0.5.1` (and `0.5.1-gpu`)
+  and `ghcr.io/lpalbou/abstractcore-server:2.16.1`.
+
+### Changed
+
+- The dev build (`scripts/build.sh`) installs the sibling kit packages an app takes from npm
+  (app-server, ui-kit, panel-chat, monitors) from local packs of the checkouts, so an app builds
+  locally even when its kit floor is ahead of the registry. The manifests and lockfiles are left
+  untouched.
+
 ## [0.4.0] - 2026-09-26
 
 A feature release of the whole framework. The gateway picks the agent workflow for AbstractCode
@@ -14,7 +104,6 @@ whole gateway process. This release replaces the 0.3.3 matrix, which was prepare
 published.
 
 ### Changed (pins)
-- The dev build (`scripts/build.sh`) installs the sibling kit packages an app takes from npm (app-server, ui-kit, panel-chat, monitors) from local packs of the checkouts, so an app builds locally even when its kit floor is ahead of the registry. The manifests and lockfiles are left untouched.
 
 - **abstractgateway 0.5.0** (was 0.4.3 on PyPI): the default agent workflow setting
   (`agents.default_workflow`, used by AbstractCode and the Assistant, changeable in the console or

{abstractframework-0.4.0/abstractframework.egg-info → abstractframework-0.4.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.4.0
+Version: 0.4.2
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,11 +23,11 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.5.0
-Requires-Dist: abstractassistant==0.6.0
-Requires-Dist: abstractcore==2.16.0
-Requires-Dist: AbstractRuntime==0.5.0
-Requires-Dist: abstractagent==0.3.14
+Requires-Dist: abstractgateway==0.5.1
+Requires-Dist: abstractassistant==0.7.0
+Requires-Dist: abstractcore==2.16.1
+Requires-Dist: AbstractRuntime==0.5.1
+Requires-Dist: abstractagent==0.3.16
 Requires-Dist: abstractskill==0.3.0
 Requires-Dist: AbstractMemory==0.3.0
 Requires-Dist: abstractsemantics==0.0.5
@@ -35,11 +35,11 @@ Requires-Dist: abstractvoice==0.11.4
 Requires-Dist: abstractvision==0.3.29
 Requires-Dist: abstractmusic==0.1.15
 Provides-Extra: apple
-Requires-Dist: abstractgateway[apple]==0.5.0; extra == "apple"
-Requires-Dist: abstractassistant[apple]==0.6.0; platform_system == "Darwin" and extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.5.1; extra == "apple"
+Requires-Dist: abstractassistant[apple]==0.7.0; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.5.0; extra == "gpu"
-Requires-Dist: abstractassistant[gpu]==0.6.0; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.5.1; extra == "gpu"
+Requires-Dist: abstractassistant[gpu]==0.7.0; extra == "gpu"
 Dynamic: license-file
 
 # AbstractFramework
@@ -190,7 +190,7 @@ ABSTRACTGATEWAY_AUTH_TOKEN=<token> abstractgateway-console --url http://127.0.0.
 ```
 
 Container images are published for the gateway and the AbstractCore server:
-`ghcr.io/lpalbou/abstractgateway:0.5.0` and `ghcr.io/lpalbou/abstractcore-server:2.16.0`.
+`ghcr.io/lpalbou/abstractgateway:0.5.1` and `ghcr.io/lpalbou/abstractcore-server:2.16.1`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -336,7 +336,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 / Windows with a CUDA or ROCm GPU | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 
-### Release matrix (abstractframework 0.4.0)
+### Release matrix (abstractframework 0.4.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
@@ -345,11 +345,11 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.5.0 |
-| PyPI | `abstractassistant` | 0.6.0 |
-| PyPI | `abstractcore` | 2.16.0 |
-| PyPI | `AbstractRuntime` | 0.5.0 |
-| PyPI | `abstractagent` | 0.3.14 |
+| PyPI | `abstractgateway` | 0.5.1 |
+| PyPI | `abstractassistant` | 0.7.0 |
+| PyPI | `abstractcore` | 2.16.1 |
+| PyPI | `AbstractRuntime` | 0.5.1 |
+| PyPI | `abstractagent` | 0.3.16 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
 | PyPI | `abstractsemantics` | 0.0.5 |
@@ -365,8 +365,8 @@ and tested together.
 | crates.io | `abstractgateway-console` | 0.9.0 |
 | crates.io | `abstractcore-console` | 0.2.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.5.0 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.16.0 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.5.1 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.16.1 |
 
 Optional add-ons that are not part of any profile install separately:
 `pip install abstract3d` (0.3.1) and `pip install abstractcamera` (0.2.0). `abstractskill` (pinned above)

{abstractframework-0.4.0 → abstractframework-0.4.2}/README.md

@@ -146,7 +146,7 @@ ABSTRACTGATEWAY_AUTH_TOKEN=<token> abstractgateway-console --url http://127.0.0.
 ```
 
 Container images are published for the gateway and the AbstractCore server:
-`ghcr.io/lpalbou/abstractgateway:0.5.0` and `ghcr.io/lpalbou/abstractcore-server:2.16.0`.
+`ghcr.io/lpalbou/abstractgateway:0.5.1` and `ghcr.io/lpalbou/abstractcore-server:2.16.1`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -292,7 +292,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 / Windows with a CUDA or ROCm GPU | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 
-### Release matrix (abstractframework 0.4.0)
+### Release matrix (abstractframework 0.4.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
@@ -301,11 +301,11 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.5.0 |
-| PyPI | `abstractassistant` | 0.6.0 |
-| PyPI | `abstractcore` | 2.16.0 |
-| PyPI | `AbstractRuntime` | 0.5.0 |
-| PyPI | `abstractagent` | 0.3.14 |
+| PyPI | `abstractgateway` | 0.5.1 |
+| PyPI | `abstractassistant` | 0.7.0 |
+| PyPI | `abstractcore` | 2.16.1 |
+| PyPI | `AbstractRuntime` | 0.5.1 |
+| PyPI | `abstractagent` | 0.3.16 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
 | PyPI | `abstractsemantics` | 0.0.5 |
@@ -321,8 +321,8 @@ and tested together.
 | crates.io | `abstractgateway-console` | 0.9.0 |
 | crates.io | `abstractcore-console` | 0.2.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.5.0 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.16.0 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.5.1 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.16.1 |
 
 Optional add-ons that are not part of any profile install separately:
 `pip install abstract3d` (0.3.1) and `pip install abstractcamera` (0.2.0). `abstractskill` (pinned above)

{abstractframework-0.4.0 → abstractframework-0.4.2}/abstractframework/__init__.py

@@ -10,22 +10,22 @@ Most implementation functionality still lives in component projects.
 
 from __future__ import annotations
 
-__version__ = "0.4.0"
+__version__ = "0.4.2"
 __author__ = "Laurent-Philippe Albou"
 __license__ = "MIT"
 
 RELEASE_VERSIONS: dict[str, str] = {
-    "abstractcore": "2.16.0",
-    "abstractruntime": "0.5.0",
-    "abstractagent": "0.3.14",
-    "abstractgateway": "0.5.0",
+    "abstractcore": "2.16.1",
+    "abstractruntime": "0.5.1",
+    "abstractagent": "0.3.16",
+    "abstractgateway": "0.5.1",
     "abstractskill": "0.3.0",
     "abstractmemory": "0.3.0",
     "abstractsemantics": "0.0.5",
     "abstractvoice": "0.11.4",
     "abstractvision": "0.3.29",
     "abstractmusic": "0.1.15",
-    "abstractassistant": "0.6.0",
+    "abstractassistant": "0.7.0",
 }
 
 PACKAGE_DISTRIBUTIONS: dict[str, str] = {

{abstractframework-0.4.0 → abstractframework-0.4.2/abstractframework.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.4.0
+Version: 0.4.2
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,11 +23,11 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.5.0
-Requires-Dist: abstractassistant==0.6.0
-Requires-Dist: abstractcore==2.16.0
-Requires-Dist: AbstractRuntime==0.5.0
-Requires-Dist: abstractagent==0.3.14
+Requires-Dist: abstractgateway==0.5.1
+Requires-Dist: abstractassistant==0.7.0
+Requires-Dist: abstractcore==2.16.1
+Requires-Dist: AbstractRuntime==0.5.1
+Requires-Dist: abstractagent==0.3.16
 Requires-Dist: abstractskill==0.3.0
 Requires-Dist: AbstractMemory==0.3.0
 Requires-Dist: abstractsemantics==0.0.5
@@ -35,11 +35,11 @@ Requires-Dist: abstractvoice==0.11.4
 Requires-Dist: abstractvision==0.3.29
 Requires-Dist: abstractmusic==0.1.15
 Provides-Extra: apple
-Requires-Dist: abstractgateway[apple]==0.5.0; extra == "apple"
-Requires-Dist: abstractassistant[apple]==0.6.0; platform_system == "Darwin" and extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.5.1; extra == "apple"
+Requires-Dist: abstractassistant[apple]==0.7.0; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.5.0; extra == "gpu"
-Requires-Dist: abstractassistant[gpu]==0.6.0; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.5.1; extra == "gpu"
+Requires-Dist: abstractassistant[gpu]==0.7.0; extra == "gpu"
 Dynamic: license-file
 
 # AbstractFramework
@@ -190,7 +190,7 @@ ABSTRACTGATEWAY_AUTH_TOKEN=<token> abstractgateway-console --url http://127.0.0.
 ```
 
 Container images are published for the gateway and the AbstractCore server:
-`ghcr.io/lpalbou/abstractgateway:0.5.0` and `ghcr.io/lpalbou/abstractcore-server:2.16.0`.
+`ghcr.io/lpalbou/abstractgateway:0.5.1` and `ghcr.io/lpalbou/abstractcore-server:2.16.1`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -336,7 +336,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 / Windows with a CUDA or ROCm GPU | 3.10–3.13 (F5-TTS voice cloning needs 3.11+) |
 
-### Release matrix (abstractframework 0.4.0)
+### Release matrix (abstractframework 0.4.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
@@ -345,11 +345,11 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.5.0 |
-| PyPI | `abstractassistant` | 0.6.0 |
-| PyPI | `abstractcore` | 2.16.0 |
-| PyPI | `AbstractRuntime` | 0.5.0 |
-| PyPI | `abstractagent` | 0.3.14 |
+| PyPI | `abstractgateway` | 0.5.1 |
+| PyPI | `abstractassistant` | 0.7.0 |
+| PyPI | `abstractcore` | 2.16.1 |
+| PyPI | `AbstractRuntime` | 0.5.1 |
+| PyPI | `abstractagent` | 0.3.16 |
 | PyPI | `abstractskill` | 0.3.0 |
 | PyPI | `AbstractMemory` | 0.3.0 |
 | PyPI | `abstractsemantics` | 0.0.5 |
@@ -365,8 +365,8 @@ and tested together.
 | crates.io | `abstractgateway-console` | 0.9.0 |
 | crates.io | `abstractcore-console` | 0.2.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.5.0 (`gpu-latest` / `<version>-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.16.0 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.5.1 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.16.1 |
 
 Optional add-ons that are not part of any profile install separately:
 `pip install abstract3d` (0.3.1) and `pip install abstractcamera` (0.2.0). `abstractskill` (pinned above)

abstractframework-0.4.2/abstractframework.egg-info/requires.txt

@@ -0,0 +1,21 @@
+abstractgateway==0.5.1
+abstractassistant==0.7.0
+abstractcore==2.16.1
+AbstractRuntime==0.5.1
+abstractagent==0.3.16
+abstractskill==0.3.0
+AbstractMemory==0.3.0
+abstractsemantics==0.0.5
+abstractvoice==0.11.4
+abstractvision==0.3.29
+abstractmusic==0.1.15
+
+[apple]
+abstractgateway[apple]==0.5.1
+
+[apple:platform_system == "Darwin"]
+abstractassistant[apple]==0.7.0
+
+[gpu]
+abstractgateway[gpu]==0.5.1
+abstractassistant[gpu]==0.7.0

{abstractframework-0.4.0 → abstractframework-0.4.2}/docs/api.md

@@ -55,14 +55,14 @@ The response type returned by `llm.generate(...)`.
 
 ### `__version__`
 
-The meta-package version (`0.4.0` for this release).
+The meta-package version (`0.4.2` for this release).
 
 ### `RELEASE_VERSIONS`
 
-Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.4.0:
-`abstractcore` 2.16.0, `abstractruntime` 0.5.0, `abstractagent` 0.3.14, `abstractgateway` 0.5.0,
+Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.4.2:
+`abstractcore` 2.16.1, `abstractruntime` 0.5.1, `abstractagent` 0.3.16, `abstractgateway` 0.5.1,
 `abstractskill` 0.3.0, `abstractmemory` 0.3.0, `abstractsemantics` 0.0.5, `abstractvoice` 0.11.4, `abstractvision` 0.3.29,
-`abstractmusic` 0.1.15, `abstractassistant` 0.6.0.
+`abstractmusic` 0.1.15, `abstractassistant` 0.7.0.
 
 ### `PACKAGE_DISTRIBUTIONS`
 

{abstractframework-0.4.0 → abstractframework-0.4.2}/docs/faq.md

@@ -34,7 +34,7 @@ No.
 | Everything at compatible versions | `pip install abstractframework` |
 | A browser app against an existing gateway | `npx @abstractframework/<flow\|code\|observer\|continuum\|entity>` |
 | A terminal client | `cargo install abstractcode`, `cargo install abstractgateway-console` or `cargo install abstractcore-console` |
-| A container deployment | `ghcr.io/lpalbou/abstractgateway:0.5.0` |
+| A container deployment | `ghcr.io/lpalbou/abstractgateway:0.5.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.4.0 → abstractframework-0.4.2}/docs/install.md

@@ -104,15 +104,41 @@ curl -LsSf https://raw.githubusercontent.com/lpalbou/AbstractFramework/main/scri
 
 It asks before removing anything, then asks two more questions, both defaulting to no:
 
-- **Also delete your AbstractFramework data** (settings, users, chats, run history)? This cannot be
-  undone.
+- **Also delete your AbstractFramework data**? This cannot be undone. It deletes:
+
+  | What | macOS | Linux |
+  |---|---|---|
+  | Gateway data: settings, users, chats, run history, artifacts, memory, the tray's preferences | `~/Library/Application Support/AbstractGateway` | `~/.local/share/abstractgateway` |
+  | The login item's logs | `~/Library/Logs/AbstractGateway` | (in the data dir) |
+  | The gateway's download cache (engine installers) | `~/Library/Caches/AbstractGateway` | `~/.cache/abstractgateway` |
+  | The Assistant's sessions, snapshots and preferences | `~/.abstractassistant`, `~/Library/Logs/Assistant/abstractassistant-*` | `~/.abstractassistant` |
+  | AbstractCode's login and preferences | `~/.abstractcode`, `~/.abstractcode-tui` | same |
+
+  It keeps model weights and shared caches: `~/.cache/huggingface`, `~/.abstractcore` (its
+  config and its downloaded models), `~/.abstractframework`, `~/.cache/abstractvoice`, and the
+  models of LM Studio and Ollama. Delete those by hand if you want them gone.
 - **Also remove uv, its Python and its download cache** (about 2.5 GB)? Asked only when the
   installer is what added uv; answer no if you use uv for anything else.
 
-It always removes the login item, stops AbstractFramework and removes the gateway. It keeps Ollama
-and LM Studio (they have their own uninstallers) and the one PATH line uv added to your shell
-profile. Without questions: `sh uninstall.sh --yes` (keeps data), add `--purge` to delete the data
-and `--remove-uv` to remove uv. Windows: `install.ps1 -Uninstall [-Purge]`.
+It always removes the login item, stops AbstractFramework and removes the gateway (and the
+Assistant, which lives in the gateway's environment). Stopping means the whole gateway process
+tree: after the login item is removed it waits up to 20 seconds for every gateway process to exit
+(the server, the tray, an entity's own-time loop, model downloads, the apps it started), then
+stops the rest, and says which processes it stopped. It keeps Ollama and LM Studio (they have
+their own uninstallers) and the one PATH line uv added to your shell profile. Without questions:
+`sh uninstall.sh --yes` (keeps data), add `--purge` to delete the data and `--remove-uv` to remove
+uv; `--print` shows every command and changes nothing. Windows: `install.ps1 -Uninstall [-Purge]`.
+
+**If a folder cannot be deleted**, the uninstaller stops with an error that names the folder,
+lists what is left in it and the programs that hold files there. Quit those programs (or log
+out and back in); on macOS, a file shown with the `uchg` flag is unlocked with
+`chflags -R nouchg <folder>`. Then run the uninstaller again: it skips what is already gone.
+Each deleted location is checked once more a second later; a program that starts writing there
+again after that is not detected (an uninstaller cannot outwait a writer it does not know).
+A `--data-dir` given by hand is purged only when it holds a gateway file (`bootstrap.env`,
+`gateway.sqlite3`, `auth/users.json`, ...) or the note a previous, interrupted purge left in it
+(`.abstractgateway-purge-incomplete`); the root, your home folder and any folder that
+contains it are always refused (exit 2, nothing changed).
 
 ## Advanced: what the installer does
 
@@ -126,7 +152,7 @@ The Mac package, the `.command` files and the one line all run the same script,
    "no" is remembered).
 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.5.0"`, from prebuilt wheels
+   `uv tool install --python 3.12 "abstractgateway[<profile>,tray]==0.5.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).
 5. Optionally installs Node.js for the browser apps, terminal tools, Ollama or LM Studio (flags
@@ -214,7 +240,7 @@ models (above), for Ollama, LM Studio or other endpoint engines, or for cloud pr
 | `--print` | `-Print` (or `-WhatIf`) | Show the plan and every command; change nothing |
 | `--print-versions` | `-PrintVersions` | Print the pinned gateway, npm app and crate versions, then exit |
 | `-v`, `--verbose` | — | Show the full output of every command |
-| `--uninstall [--purge] [--remove-uv]` | `-Uninstall [-Purge]` | Remove the service and uv tools (purge also deletes the data; `--remove-uv` also removes uv, its Python and cache when the installer added uv) |
+| `--uninstall [--purge] [--remove-uv]` | `-Uninstall [-Purge]` | Stop the gateway process tree, remove the service and uv tools (purge also deletes your data: see [Remove AbstractFramework](#remove-abstractframework); `--remove-uv` also removes uv, its Python and cache when the installer added uv) |
 
 Pass options through the one-liner like this:
 
@@ -231,7 +257,7 @@ curl -LsSf https://raw.githubusercontent.com/lpalbou/AbstractFramework/main/scri
 ```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.5.0"    # [apple,tray] or [gpu,tray] for local engines
+uv tool install --python 3.12 "abstractgateway[tray]==0.5.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
@@ -338,8 +364,8 @@ A plain `pip install` of the `apple` or `gpu` profile builds the
 `aec-audio-processing`) from source, so it needs a C/C++ compiler. The one-line install above
 does not.
 
-`abstractframework` 0.4.0 pins `abstractgateway==0.5.0`, `abstractassistant==0.6.0`,
-`abstractcore==2.16.0`, `AbstractRuntime==0.5.0`, `abstractagent==0.3.14`, `abstractskill==0.3.0`,
+`abstractframework` 0.4.2 pins `abstractgateway==0.5.1`, `abstractassistant==0.7.0`,
+`abstractcore==2.16.1`, `AbstractRuntime==0.5.1`, `abstractagent==0.3.16`, `abstractskill==0.3.0`,
 `AbstractMemory==0.3.0`, `abstractsemantics==0.0.5`, `abstractvoice==0.11.4`,
 `abstractvision==0.3.29` and `abstractmusic==0.1.15`. The `apple` and `gpu` extras select
 `abstractgateway[apple|gpu]` and `abstractassistant[apple|gpu]` at the same versions
@@ -423,10 +449,10 @@ 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.4.0 |
+| Tool | Command | Version released with 0.4.2 |
 |---|---|---|
-| Gateway web console | built into `abstractgateway`: open the link `abstractgateway serve` prints (`http://127.0.0.1:8080/console#claim=…`) | 0.5.0 |
-| Core web console | built into `abstractcore`: open the link `abstractcore serve` prints (`http://127.0.0.1:8000/console#claim=…`) | 2.16.0 |
+| Gateway web console | built into `abstractgateway`: open the link `abstractgateway serve` prints (`http://127.0.0.1:8080/console#claim=…`) | 0.5.1 |
+| Core web console | built into `abstractcore`: open the link `abstractcore serve` prints (`http://127.0.0.1:8000/console#claim=…`) | 2.16.1 |
 | Core terminal console | `cargo install abstractcore-console` (Rust 1.87+), then `abstractcore-console` (uses the `abstractcore` command) | 0.2.0 |
 | Gateway terminal console | `cargo install abstractgateway-console` (Rust 1.87+), then `abstractgateway-console --url http://127.0.0.1:8080` | 0.9.0 |
 | Flow Editor | `npx @abstractframework/flow` | 0.3.21 |
@@ -468,7 +494,7 @@ docker run \
   -v "$PWD/runtime:/data" \
   -e ABSTRACTGATEWAY_DATA_DIR=/data \
   -e ABSTRACTGATEWAY_USER_AUTH=1 \
-  ghcr.io/lpalbou/abstractgateway:0.5.0
+  ghcr.io/lpalbou/abstractgateway:0.5.1
 ```
 
 This is the Light container: full framework capabilities through remote/endpoint inference, without
@@ -476,7 +502,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.16.0`.
+`ghcr.io/lpalbou/abstractcore-server:2.16.1`.
 
 ## How installs are designed
 

{abstractframework-0.4.0 → abstractframework-0.4.2}/docs/installers/implementation-plan.md

@@ -19,7 +19,7 @@ comes next.
 
 ## Gateway features the scripts use
 
-The pinned gateway (0.5.0) provides all of them. The scripts still detect each one, so an older
+The pinned gateway (0.5.1) provides all of them. The scripts still detect each one, so an older
 gateway selected with `--pin` falls back as the last column says.
 
 | Feature | Command | Without it (older `--pin`) |