abstractframework 0.6.0__tar.gz → 0.6.1__tar.gz

{abstractframework-0.6.0 → abstractframework-0.6.1}/CHANGELOG.md

@@ -4,6 +4,65 @@ All notable changes to AbstractFramework will be documented in this file.
 
 ## [Unreleased]
 
+## [0.6.1] - 2026-09-28
+
+Every terminal command lands on your PATH, AbstractCode's terminal client says how to sign in, and
+Run now explains itself the same way in every client.
+
+### Changed
+
+- **The installer puts every command line on PATH by default**, in one folder, uv's tool bin
+  directory (`~/.local/bin` on macOS and Linux, `%USERPROFILE%\.local\bin` on Windows), next to
+  `abstractgateway`:
+  - AbstractCode's terminal client, `abstractcode`, is built whenever the terminal console is, with
+    the same cargo. `--no-code-cli` (`-NoCodeCli`) skips it; a failed build never fails the install.
+    With `--no-console` it is built only when a cargo of Rust 1.87 or later already exists.
+  - The library commands come from the gateway's own environment: AbstractCore's (`abstractcore`,
+    `abstractcore-config`, `abstractcore-chat`, `abstractcore-endpoint` and its apps `summarizer`,
+    `extractor`, `judge`, `intent`, `deepsearch`, also as `abstractcore-<app>`), `abstractvoice`,
+    `abstractvoice-prefetch`, `abstractvision` and `abstractmusic`. `--no-core-cli` (`-NoCoreCli`)
+    leaves them out.
+  - A package's commands come all together or not at all: when another program already has one of
+    its names, that package is left out with a warning naming the file, and the rest installs.
+  - `--with-code-cli` and `--with-core-cli` stay accepted (they are the default now).
+  - The summary lists every command with what it does (`abstractgateway-config`: the gateway's
+    admin command). See [Commands you get](docs/install.md#commands-you-get).
+- **Signing AbstractCode's terminal client in.** The summary prints
+  `Sign in (terminal, once): abstractcode login --token <token>` with your admin token, then
+  `abstractcode`, and the way without a token on the gateway's computer,
+  `abstractgateway apps tui-command code`. The installer never saves the token for you. Started
+  without a sign-in, `abstractcode` 0.7.1 says so and prints the same lines instead of opening
+  with an empty workflow.
+- **Terminal apps share one folder with the gateway** (AbstractGateway 0.7.1). The console's
+  **Apps** page installs and updates `abstractcode` in the same folder as the installer, so it runs
+  by name. A re-run of the installer keeps an `abstractcode` newer than its pin. On Windows,
+  `install.ps1` builds `abstractgateway-console` and `abstractcode` into `%USERPROFILE%\.local\bin`
+  (an existing copy in `%USERPROFILE%\.cargo\bin` is left in place).
+- **Uninstall** removes `abstractcode` like the console, and also the copy older gateways put in
+  `<data dir>/apps/bin` (removing that folder when it is empty; other files there are kept).
+
+### Added
+
+- **Run now reads the same everywhere** (ui-kit 0.1.16, Observer 0.2.1, Assistant 0.9.1,
+  AbstractCode terminal 0.7.1 and web 0.6.1). Every client draws Run now with the same play-in-a-circle icon and explains
+  it with the same text: it runs the automation once now instead of waiting; the next scheduled run
+  keeps its time (or starts right after this run if its time comes first); it does not count toward
+  a run limit; it works while paused, which stays paused; and it is not available while a run is in
+  progress. Pause, Resume, Stop, Edit, Archive and Discuss carry the same kind of hint. See
+  [Automations](docs/automations.md).
+
+### Changed (pins)
+
+- **abstractgateway 0.7.1** (was 0.7.0): terminal apps in the uv tool bin folder.
+- **abstractassistant 0.9.1** (was 0.9.0): the shared Run now icon and hints.
+- npm: **@abstractframework/observer 0.2.1** and **@abstractframework/code 0.6.1** (both with the
+  shared Run now hints, ui-kit 0.1.16).
+- crates.io: **abstractcode 0.7.1** (sign-in report, "not signed in" state, Run now line).
+- Unchanged: abstractcore 2.18.0, AbstractRuntime 0.7.1, abstractagent 0.3.17, abstractvoice 0.13.0,
+  abstractskill 0.3.0, AbstractMemory 0.3.0, abstractsemantics 0.0.5, abstractvision 0.3.30,
+  abstractmusic 0.1.15, flow 0.4.0, continuum 0.4.0, entity 0.3.0, `abstractgateway-console` 0.11.0,
+  `abstractcore-console` 0.4.0 and `abstracttui` 0.6.0.
+
 ## [0.6.0] - 2026-09-28
 
 Remote and headless machines work like a Mac: one address and one SSH tunnel reach the console, the

{abstractframework-0.6.0/abstractframework.egg-info → abstractframework-0.6.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.6.0
+Version: 0.6.1
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,8 +23,8 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.7.0
-Requires-Dist: abstractassistant==0.9.0
+Requires-Dist: abstractgateway==0.7.1
+Requires-Dist: abstractassistant==0.9.1
 Requires-Dist: abstractcore==2.18.0
 Requires-Dist: AbstractRuntime==0.7.1
 Requires-Dist: abstractagent==0.3.17
@@ -35,11 +35,11 @@ Requires-Dist: abstractvoice==0.13.0
 Requires-Dist: abstractvision==0.3.30
 Requires-Dist: abstractmusic==0.1.15
 Provides-Extra: apple
-Requires-Dist: abstractgateway[apple]==0.7.0; extra == "apple"
-Requires-Dist: abstractassistant[apple]==0.9.0; platform_system == "Darwin" and extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.7.1; extra == "apple"
+Requires-Dist: abstractassistant[apple]==0.9.1; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.7.0; extra == "gpu"
-Requires-Dist: abstractassistant[gpu]==0.9.0; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.7.1; extra == "gpu"
+Requires-Dist: abstractassistant[gpu]==0.9.1; extra == "gpu"
 Dynamic: license-file
 
 # AbstractFramework
@@ -198,7 +198,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.7.0` and `ghcr.io/lpalbou/abstractcore-server:2.18.0`.
+`ghcr.io/lpalbou/abstractgateway:0.7.1` and `ghcr.io/lpalbou/abstractcore-server:2.18.0`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -344,7 +344,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.6.0)
+### Release matrix (abstractframework 0.6.1)
 
 `abstractframework` pins every Python package with `==`, so one version of the
 meta-package always installs the same stack. The browser apps and Rust tools are
@@ -353,8 +353,8 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.7.0 |
-| PyPI | `abstractassistant` | 0.9.0 |
+| PyPI | `abstractgateway` | 0.7.1 |
+| PyPI | `abstractassistant` | 0.9.1 |
 | PyPI | `abstractcore` | 2.18.0 |
 | PyPI | `AbstractRuntime` | 0.7.1 |
 | PyPI | `abstractagent` | 0.3.17 |
@@ -365,15 +365,15 @@ and tested together.
 | PyPI | `abstractvision` | 0.3.30 |
 | PyPI | `abstractmusic` | 0.1.15 |
 | npm | `@abstractframework/flow` | 0.4.0 |
-| npm | `@abstractframework/code` | 0.6.0 |
-| npm | `@abstractframework/observer` | 0.2.0 |
+| npm | `@abstractframework/code` | 0.6.1 |
+| npm | `@abstractframework/observer` | 0.2.1 |
 | npm | `@abstractframework/continuum` | 0.4.0 |
 | npm | `@abstractframework/entity` | 0.3.0 |
-| crates.io | `abstractcode` | 0.7.0 |
+| crates.io | `abstractcode` | 0.7.1 |
 | crates.io | `abstractgateway-console` | 0.11.0 |
 | crates.io | `abstractcore-console` | 0.4.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.7.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.7.1 (`gpu-latest` / `<version>-gpu` experimental) |
 | GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.18.0 |
 
 Optional add-ons that are not part of any profile install separately:

{abstractframework-0.6.0 → abstractframework-0.6.1}/README.md

@@ -154,7 +154,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.7.0` and `ghcr.io/lpalbou/abstractcore-server:2.18.0`.
+`ghcr.io/lpalbou/abstractgateway:0.7.1` and `ghcr.io/lpalbou/abstractcore-server:2.18.0`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -300,7 +300,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.6.0)
+### Release matrix (abstractframework 0.6.1)
 
 `abstractframework` pins every Python package with `==`, so one version of the
 meta-package always installs the same stack. The browser apps and Rust tools are
@@ -309,8 +309,8 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.7.0 |
-| PyPI | `abstractassistant` | 0.9.0 |
+| PyPI | `abstractgateway` | 0.7.1 |
+| PyPI | `abstractassistant` | 0.9.1 |
 | PyPI | `abstractcore` | 2.18.0 |
 | PyPI | `AbstractRuntime` | 0.7.1 |
 | PyPI | `abstractagent` | 0.3.17 |
@@ -321,15 +321,15 @@ and tested together.
 | PyPI | `abstractvision` | 0.3.30 |
 | PyPI | `abstractmusic` | 0.1.15 |
 | npm | `@abstractframework/flow` | 0.4.0 |
-| npm | `@abstractframework/code` | 0.6.0 |
-| npm | `@abstractframework/observer` | 0.2.0 |
+| npm | `@abstractframework/code` | 0.6.1 |
+| npm | `@abstractframework/observer` | 0.2.1 |
 | npm | `@abstractframework/continuum` | 0.4.0 |
 | npm | `@abstractframework/entity` | 0.3.0 |
-| crates.io | `abstractcode` | 0.7.0 |
+| crates.io | `abstractcode` | 0.7.1 |
 | crates.io | `abstractgateway-console` | 0.11.0 |
 | crates.io | `abstractcore-console` | 0.4.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.7.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.7.1 (`gpu-latest` / `<version>-gpu` experimental) |
 | GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.18.0 |
 
 Optional add-ons that are not part of any profile install separately:

{abstractframework-0.6.0 → abstractframework-0.6.1}/abstractframework/__init__.py

@@ -10,7 +10,7 @@ Most implementation functionality still lives in component projects.
 
 from __future__ import annotations
 
-__version__ = "0.6.0"
+__version__ = "0.6.1"
 __author__ = "Laurent-Philippe Albou"
 __license__ = "MIT"
 
@@ -18,14 +18,14 @@ RELEASE_VERSIONS: dict[str, str] = {
     "abstractcore": "2.18.0",
     "abstractruntime": "0.7.1",
     "abstractagent": "0.3.17",
-    "abstractgateway": "0.7.0",
+    "abstractgateway": "0.7.1",
     "abstractskill": "0.3.0",
     "abstractmemory": "0.3.0",
     "abstractsemantics": "0.0.5",
     "abstractvoice": "0.13.0",
     "abstractvision": "0.3.30",
     "abstractmusic": "0.1.15",
-    "abstractassistant": "0.9.0",
+    "abstractassistant": "0.9.1",
 }
 
 PACKAGE_DISTRIBUTIONS: dict[str, str] = {
@@ -44,18 +44,18 @@ PACKAGE_DISTRIBUTIONS: dict[str, str] = {
 
 NPM_RELEASE_VERSIONS: dict[str, str] = {
     "@abstractframework/flow": "0.4.0",
-    "@abstractframework/code": "0.6.0",
-    "@abstractframework/observer": "0.2.0",
+    "@abstractframework/code": "0.6.1",
+    "@abstractframework/observer": "0.2.1",
     "@abstractframework/continuum": "0.4.0",
     "@abstractframework/entity": "0.3.0",
 }
 
 # Terminal tools published on crates.io alongside this release (installed with `cargo install`,
-# or by the bootstrap scripts: the gateway console by default, abstractcode with --with-code-cli).
+# or by the bootstrap scripts: the gateway console and abstractcode by default).
 CRATE_RELEASE_VERSIONS: dict[str, str] = {
     "abstractgateway-console": "0.11.0",
     "abstractcore-console": "0.4.0",
-    "abstractcode": "0.7.0",
+    "abstractcode": "0.7.1",
     "abstracttui": "0.6.0",
 }
 

{abstractframework-0.6.0 → abstractframework-0.6.1}/abstractframework/install_manifest.py

@@ -38,10 +38,14 @@ BOOTSTRAP_FLAGS: list[dict[str, str]] = [
      "summary": "Skip the terminal console. By default abstractgateway-console is built "
                 "with cargo (install.sh adds Rust through rustup when cargo is missing; "
                 "needs a C compiler)."},
-    {"sh": "--with-code-cli", "ps": "-WithCodeCli", "env": "",
-     "summary": "cargo install abstractcode (terminal client) when cargo exists."},
-    {"sh": "--with-core-cli", "ps": "-WithCoreCli", "env": "",
-     "summary": "Also expose the abstractcore command (--with-executables-from abstractcore)."},
+    {"sh": "--no-code-cli", "ps": "-NoCodeCli", "env": "",
+     "summary": "Skip AbstractCode's terminal client. By default abstractcode is built with "
+                "the terminal console's cargo, into the same folder (--with-code-cli, the "
+                "old opt-in, is accepted)."},
+    {"sh": "--no-core-cli", "ps": "-NoCoreCli", "env": "",
+     "summary": "Do not expose AbstractCore's commands (abstractcore, its apps) and "
+                "abstractvoice, abstractvision, abstractmusic next to the gateway's "
+                "(--with-core-cli, the old opt-in, is accepted)."},
     {"sh": "--with-ollama", "ps": "-WithOllama", "env": "",
      "summary": "Run Ollama's official installer (Linux/macOS may ask for sudo)."},
     {"sh": "--with-lmstudio", "ps": "-WithLmStudio", "env": "",

{abstractframework-0.6.0 → abstractframework-0.6.1/abstractframework.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.6.0
+Version: 0.6.1
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,8 +23,8 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.7.0
-Requires-Dist: abstractassistant==0.9.0
+Requires-Dist: abstractgateway==0.7.1
+Requires-Dist: abstractassistant==0.9.1
 Requires-Dist: abstractcore==2.18.0
 Requires-Dist: AbstractRuntime==0.7.1
 Requires-Dist: abstractagent==0.3.17
@@ -35,11 +35,11 @@ Requires-Dist: abstractvoice==0.13.0
 Requires-Dist: abstractvision==0.3.30
 Requires-Dist: abstractmusic==0.1.15
 Provides-Extra: apple
-Requires-Dist: abstractgateway[apple]==0.7.0; extra == "apple"
-Requires-Dist: abstractassistant[apple]==0.9.0; platform_system == "Darwin" and extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.7.1; extra == "apple"
+Requires-Dist: abstractassistant[apple]==0.9.1; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.7.0; extra == "gpu"
-Requires-Dist: abstractassistant[gpu]==0.9.0; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.7.1; extra == "gpu"
+Requires-Dist: abstractassistant[gpu]==0.9.1; extra == "gpu"
 Dynamic: license-file
 
 # AbstractFramework
@@ -198,7 +198,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.7.0` and `ghcr.io/lpalbou/abstractcore-server:2.18.0`.
+`ghcr.io/lpalbou/abstractgateway:0.7.1` and `ghcr.io/lpalbou/abstractcore-server:2.18.0`.
 
 For artifact and runtime-resource investigation, see
 [Runtime artifacts and retrieval](docs/guide/runtime-artifacts.md).
@@ -344,7 +344,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.6.0)
+### Release matrix (abstractframework 0.6.1)
 
 `abstractframework` pins every Python package with `==`, so one version of the
 meta-package always installs the same stack. The browser apps and Rust tools are
@@ -353,8 +353,8 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.7.0 |
-| PyPI | `abstractassistant` | 0.9.0 |
+| PyPI | `abstractgateway` | 0.7.1 |
+| PyPI | `abstractassistant` | 0.9.1 |
 | PyPI | `abstractcore` | 2.18.0 |
 | PyPI | `AbstractRuntime` | 0.7.1 |
 | PyPI | `abstractagent` | 0.3.17 |
@@ -365,15 +365,15 @@ and tested together.
 | PyPI | `abstractvision` | 0.3.30 |
 | PyPI | `abstractmusic` | 0.1.15 |
 | npm | `@abstractframework/flow` | 0.4.0 |
-| npm | `@abstractframework/code` | 0.6.0 |
-| npm | `@abstractframework/observer` | 0.2.0 |
+| npm | `@abstractframework/code` | 0.6.1 |
+| npm | `@abstractframework/observer` | 0.2.1 |
 | npm | `@abstractframework/continuum` | 0.4.0 |
 | npm | `@abstractframework/entity` | 0.3.0 |
-| crates.io | `abstractcode` | 0.7.0 |
+| crates.io | `abstractcode` | 0.7.1 |
 | crates.io | `abstractgateway-console` | 0.11.0 |
 | crates.io | `abstractcore-console` | 0.4.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.7.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.7.1 (`gpu-latest` / `<version>-gpu` experimental) |
 | GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.18.0 |
 
 Optional add-ons that are not part of any profile install separately:

{abstractframework-0.6.0 → abstractframework-0.6.1}/abstractframework.egg-info/requires.txt

@@ -1,5 +1,5 @@
-abstractgateway==0.7.0
-abstractassistant==0.9.0
+abstractgateway==0.7.1
+abstractassistant==0.9.1
 abstractcore==2.18.0
 AbstractRuntime==0.7.1
 abstractagent==0.3.17
@@ -11,11 +11,11 @@ abstractvision==0.3.30
 abstractmusic==0.1.15
 
 [apple]
-abstractgateway[apple]==0.7.0
+abstractgateway[apple]==0.7.1
 
 [apple:platform_system == "Darwin"]
-abstractassistant[apple]==0.9.0
+abstractassistant[apple]==0.9.1
 
 [gpu]
-abstractgateway[gpu]==0.7.0
-abstractassistant[gpu]==0.9.0
+abstractgateway[gpu]==0.7.1
+abstractassistant[gpu]==0.9.1

{abstractframework-0.6.0 → abstractframework-0.6.1}/docs/api.md

@@ -55,14 +55,14 @@ The response type returned by `llm.generate(...)`.
 
 ### `__version__`
 
-The meta-package version (`0.6.0` for this release).
+The meta-package version (`0.6.1` for this release).
 
 ### `RELEASE_VERSIONS`
 
-Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.6.0:
-`abstractcore` 2.18.0, `abstractruntime` 0.7.1, `abstractagent` 0.3.17, `abstractgateway` 0.7.0,
+Dictionary mapping each ecosystem package name to the pinned version for this release. In 0.6.1:
+`abstractcore` 2.18.0, `abstractruntime` 0.7.1, `abstractagent` 0.3.17, `abstractgateway` 0.7.1,
 `abstractskill` 0.3.0, `abstractmemory` 0.3.0, `abstractsemantics` 0.0.5, `abstractvoice` 0.13.0, `abstractvision` 0.3.30,
-`abstractmusic` 0.1.15, `abstractassistant` 0.9.0.
+`abstractmusic` 0.1.15, `abstractassistant` 0.9.1.
 
 ### `PACKAGE_DISTRIBUTIONS`
 
@@ -72,16 +72,16 @@ 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.6.0,
-`@abstractframework/observer` 0.2.0, `@abstractframework/continuum` 0.4.0 and
+`@abstractframework/flow` 0.4.0, `@abstractframework/code` 0.6.1,
+`@abstractframework/observer` 0.2.1, `@abstractframework/continuum` 0.4.0 and
 `@abstractframework/entity` 0.3.0. They also appear as `npm_apps` in the install manifest.
 
 ### `CRATE_RELEASE_VERSIONS`
 
 The Rust terminal tools released with this version, installed with `cargo install <crate>`:
-`abstractgateway-console` 0.11.0, `abstractcore-console` 0.4.0, `abstractcode` 0.7.0 and the
+`abstractgateway-console` 0.11.0, `abstractcore-console` 0.4.0, `abstractcode` 0.7.1 and the
 `abstracttui` engine 0.6.0. The bootstrap scripts build `abstractgateway-console` at this version by default
-(`--no-console` skips it) and `abstractcode` with `--with-code-cli`.
+(`--no-console` skips it) and `abstractcode` next to it (`--no-code-cli` skips it).
 
 ### `CORE_DEFAULT_EXTRAS`
 

{abstractframework-0.6.0 → abstractframework-0.6.1}/docs/automations.md

@@ -397,14 +397,19 @@ Every control is a command, `POST /api/gateway/automations/{id}/commands` with a
 | Control | Command | What happens |
 |---|---|---|
 | **Pause** | `automation.pause` | No scheduled run until you resume. A run in progress finishes. |
-| **Run now** | `automation.run_now` | One run at once, **also while paused** (the automation stays paused). Refused (409 `automation_busy`) while an occurrence is running or queued; there is no queue. |
+| **Run now** | `automation.run_now` | One run at once, instead of waiting for the schedule, **also while paused** (the automation stays paused). **The schedule does not move**: the next scheduled run keeps its time; if that time comes while this run is still going, the scheduled run starts as soon as it ends (missed times coalesce into one run). A manual run does not count toward a schedule's run limit (`count`); once that limit is reached the automation has ended and Run now is refused. In a Growing automation, later runs see it in their history. Refused (409 `automation_busy`) while an occurrence is running or queued; there is no queue. |
 | **Resume** | `automation.resume` | Back on the schedule from the next tick after now. It never fires on resume and never catches up the time spent paused. |
 | **Edit** / **Revise…** | `PATCH` with `expected_revision` and `changes` | Title, interval and context in the apps; also `target` and `policy` through the API. Creates the next revision, used from the next run; an occurrence already running keeps the inputs it started with. A changed schedule never fires a past tick. |
 | **Stop current** | `automation.stop_current` | Cancels the run in progress (quietly). |
 | **Archive** | `automation.archive` | No further runs; the current one finishes. **The history is kept** and stays readable; the only remaining control is Discuss. |
 | **Discuss** | `POST …/discuss` `{request_id, occurrence_index, prompt}` | A new conversation forked at that occurrence: its context is the automation's whole timeline up to and including it; it works in its own writable workspace (`workspace_root` in the response) with the automation's folder mounted read-only (`mounted_workspace`); see [the mental model](#the-mental-model). Continue it like any chat (`POST /api/gateway/runs/start` with its `session_id`). |
 
-The Assistant and the Observer disable a control that does not apply and say why in its tooltip.
+Every client explains each control in its tooltip with the same text, and draws Run now with the
+same play-in-a-circle icon: the Observer, the web panels and AbstractCode's browser client use the
+ui-kit's `CONTROL_HINTS`; the Assistant and AbstractCode's terminal client carry a byte-identical
+copy of the kit's `automation_controls.json` (`scripts/check_identity_sync.py` fails on drift).
+Run now's tooltip adds the next scheduled time when there is one. A control that does not apply is
+disabled, and its tooltip first says why.
 
 ## What notifies you, and when
 

{abstractframework-0.6.0 → abstractframework-0.6.1}/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.7.0` |
+| A container deployment | `ghcr.io/lpalbou/abstractgateway:0.7.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.6.0 → abstractframework-0.6.1}/docs/getting-started.md

@@ -44,7 +44,34 @@ browser apps, which the gateway serves at `http://127.0.0.1:8080/apps/<app>/`. T
 builds the terminal console, `abstractgateway-console`, which offers the same guide on a server
 without a browser (its **Network** screen, `N`, decides who can reach the gateway); over SSH the
 installer offers to open it at the end, and its summary prints the command (see
-[Headless or remote machine](install.md#headless-or-remote-machine)). Then
+[Headless or remote machine](install.md#headless-or-remote-machine)).
+
+The commands it puts on PATH (in `~/.local/bin`; open a new terminal), each listed in its summary:
+
+- `abstractgateway`: the gateway itself (`serve`, `service`, `network`, `models`, `engines`).
+- `abstractgateway-config`: the gateway's admin and configuration command: `status`, `claim-url`
+  (a new one-time console sign-in link), `set-default` (which model each capability uses),
+  `get` / `set` (runtime settings), `bootstrap-admin`.
+- `abstractgateway-console`: the terminal console; the summary prints it ready to paste, with
+  `--gateway-url` and `--token`.
+- `abstractcode`: AbstractCode's terminal client. Sign it in once with
+  `abstractcode login --token <admin token>` (the summary prints this line with your token), then
+  run `abstractcode`; or, on the gateway's computer, `abstractgateway apps tui-command code` opens
+  it signed in without a token.
+- AbstractCore's commands: `abstractcore` (also `abstractcore-config`: setup wizard, models,
+  engines, `serve`), `abstractcore-chat` (a chat in the terminal), `abstractcore-endpoint` (a
+  single-model `/v1` server), and its apps `summarizer` (summarize a document), `extractor`
+  (entities and relationships as a knowledge graph), `judge` (LLM-as-a-judge scoring), `intent`
+  (intent analysis) and `deepsearch` (a research agent that writes a sourced report), each also as
+  `abstractcore-<app>`.
+- `abstractvoice` (a spoken chat, `tts`, `web`) and `abstractvoice-prefetch` (download voice
+  models), `abstractvision` (generate or edit images and video: `t2i`, `i2i`, `t2v`, …) and
+  `abstractmusic` (`t2m`: text to music).
+
+A package puts all of the commands it declares on PATH (uv cannot pick a subset). `--no-console`,
+`--no-code-cli` and `--no-core-cli` leave them out, and a package whose command name another
+program already has is left out with a warning naming that file; see
+[Commands you get](install.md#commands-you-get). Then
 continue with [Monitor runs](#4-monitor-runs-with-abstractobserver) or
 [AbstractFlow](#author-orchestration-with-abstractflow). Step by step, what to do when something
 fails, and how to remove it: [Install](install.md); fixes for common problems:
@@ -298,8 +325,11 @@ the gateway default then runs at its next turn. See [Agent sessions](agent-sessi
 
 ### AbstractCode (terminal and browser)
 
-A coding client for durable agentic sessions on the gateway you started above. Install the Rust
-terminal client from crates.io (or download a prebuilt binary from the
+A coding client for durable agentic sessions on the gateway you started above. The installer
+already built the Rust terminal client, `abstractcode`; sign it in once with
+`abstractcode login --token <admin token>` (the installer summary prints the line with your token),
+or open it signed in on the gateway's computer with `abstractgateway apps tui-command code` (see
+[Commands you get](install.md#commands-you-get)). Otherwise install it from crates.io (or download a prebuilt binary from the
 [AbstractCode GitHub release](https://github.com/lpalbou/AbstractCode/releases)), or run the
 browser client (the gateway console's **Apps** page opens it at `/apps/code/`, or run it with
 `npx`):

{abstractframework-0.6.0 → abstractframework-0.6.1}/docs/glossary.md

@@ -264,7 +264,9 @@ real address in `X-Forwarded-For` so the gateway can tell local from remote call
 
 The descriptor `identity/abstractframework.json` (in this repository) that every About screen
 renders; each rendering package vendors a byte-identical copy, checked by
-`scripts/check_identity_sync.py`.
+`scripts/check_identity_sync.py`. The same script checks the shared contract fixtures and the
+automation controls' names, hints and Run now icon (`automation_controls.json`, canonical in the
+ui-kit).
 
 ---