abstractframework 0.1.12__tar.gz → 0.2.1__tar.gz

{abstractframework-0.1.12 → abstractframework-0.2.1}/CHANGELOG.md

@@ -2,7 +2,146 @@
 
 All notable changes to AbstractFramework will be documented in this file.
 
-## [Unreleased]
+## [0.2.1] - 2026-09-24
+
+Patch release: the one-line install works on a machine without a C compiler, and the
+meta-package pins abstractvoice 0.11.4. Everything else is unchanged from 0.2.0.
+
+### Changed
+
+- **abstractvoice 0.11.4** (was 0.11.3). It takes voice activity detection from
+  `webrtcvad-wheels`, which ships prebuilt wheels for macOS arm64, Linux and Windows, instead
+  of `webrtcvad`, which is source-only on PyPI and needs a compiler. This is the pin that made
+  `pip install abstractframework[apple]` build `webrtcvad` from source. The other pins are
+  unchanged: abstractgateway 0.3.0, abstractcore 2.14.0, AbstractRuntime 0.4.33.
+
+### Fixed
+
+- **One-line install needs no compiler.** On a Mac without Xcode Command Line Tools the gateway
+  install failed building `webrtcvad` from source, and `llama-cpp-python`,
+  `stable-diffusion-cpp-python` and `aec-audio-processing` would have failed next. `install.sh` and
+  `install.ps1` now run `uv tool install` with `--with 'webrtcvad-wheels>=2.0.14'`, an overrides
+  file (`uv-overrides.txt` in the gateway data directory) that drops `webrtcvad`, keeps `vllm` to
+  Linux and leaves out the three compiled extras, plus `--no-build-package` for those packages so
+  a missing wheel fails fast instead of starting a compiler. The install runs from the data
+  directory and names the file relatively, because uv splits an `--overrides` value at whitespace
+  (`Application Support`). On macOS, Linux and Windows the preflight says when no compiler is
+  present, and that this is fine; the summary says what was skipped.
+
+### Added
+
+- **`--full` (Windows: `-Full`)** keeps the compiled extras (llama.cpp GGUF, stable-diffusion.cpp,
+  echo cancellation) and builds them from source. It needs a C/C++ compiler and stops before
+  installing when none is found.
+
+## [0.2.0] - 2026-09-23
+
+Install the framework with one line, sign in to the gateway console with a one-time link, and
+manage local models and engines from the console, the terminal or the command line.
+
+### Added
+
+- **One-line install.** `scripts/install.sh` (macOS, Linux) and `scripts/install.ps1` (Windows 10
+  22H2+ / 11, PowerShell 5.1 and 7) install uv and Python 3.12 when needed, install the pinned
+  gateway as a uv tool (`abstractgateway[<profile>,tray]==0.3.0`, profile picked from the machine),
+  register it to start at login (`abstractgateway service install`), start it on `127.0.0.1`,
+  wait for `/api/health`, and open the console through a one-time sign-in link. No admin rights
+  and no system Python are needed:
+
+  ```bash
+  curl -LsSf https://raw.githubusercontent.com/lpalbou/AbstractFramework/main/scripts/install.sh | sh
+  ```
+
+  ```powershell
+  powershell -ExecutionPolicy ByPass -c "irm https://raw.githubusercontent.com/lpalbou/AbstractFramework/main/scripts/install.ps1 | iex"
+  ```
+
+  Options: `--profile`, `--port`, `--with-apps` (Node.js through `nodejs-wheel`), `--with-ollama`,
+  `--with-lmstudio`, `--with-console`, `--with-code-cli`, `--with-core-cli`, `--no-service`,
+  `--no-open`, `--pin`, `--print` (dry run), `--uninstall [--purge]`. Re-running upgrades or
+  repairs in place. See [Install](docs/install.md#quick-start).
+- **First-run wizard.** Through the pinned gateway 0.3.0, a bare `abstractgateway serve` binds
+  `127.0.0.1`, creates the admin user and prints a one-time console link; the console's first-run
+  guide sets up a local engine, a default model that fits the machine, and the apps.
+- **Models and Engines in both entry points.** Through the pinned AbstractCore 2.14.0 and gateway
+  0.3.0, `abstractcore serve` and `abstractgateway serve` both offer **Models** (catalog with a fit
+  verdict for this machine, installed models with sizes, download, delete) and **Engines**
+  (detect and install Ollama, LM Studio, MLX, llama.cpp; every install shows its command first)
+  in their web consoles, their terminal consoles (`abstractcore-console`,
+  `abstractgateway-console`) and on the command line (`abstractcore models|engines`,
+  `abstractgateway models|engines`). `abstractcore serve` gains a web console at `/console`.
+- **Engine installs** from the console or the bootstrap flags (`--with-ollama`,
+  `--with-lmstudio`) use each vendor's official installer.
+- `abstractframework doctor` checks the Python range (3.10–3.13), macOS 14+ on Apple Silicon for the
+  `apple` profile, uv, Node.js 18+ (system or `nodejs-wheel`), free disk, and reads the gateway
+  health (`ABSTRACTGATEWAY_URL`), `abstractgateway-config status --json`, Ollama and LM Studio
+  reachability with read-only requests. New `--no-network` and `--timeout`; checks can report
+  `info`.
+- `CRATE_RELEASE_VERSIONS` lists the crates released with this version; `get_release_profile()`
+  returns them under `crates`.
+- Workspace scripts for source checkouts:
+  - `scripts/lib/packages.txt`: one inventory of the 30 published packages (21 repositories) with
+    registry names, sub-paths, dependency tiers and edges, read by every workspace script.
+    `scripts/deps.sh` prints the tiers with their edges and reverse dependencies (`rdeps`) and
+    validates the inventory against the package files (`check`).
+  - `scripts/push.sh` (dry run by default, `--yes` to push `main`, never forced) and
+    `scripts/pull.sh` (fetch + fast-forward only), grouped by tier.
+  - `scripts/status.sh --registry` compares local versions with PyPI, npm and crates.io;
+    `--versions` and `--tiers` add the local versions and the dependency view.
+  - `scripts/build.sh` builds every package in tier order, including the Rust crates
+    `abstracttui`, `abstractcore-console`, `abstractcode` and `abstractgateway-console`. New
+    `--plan` and `AF_VENV_DIR`; `--python/--npm/--rust` combine; the script exits non-zero when a
+    selected build fails.
+  - See [Workspace scripts](docs/workspace-scripts.md).
+
+### Changed
+
+- The release profile pins the packages released on 2026-09-23. `pip install abstractframework`
+  (and the `apple` / `gpu` extras) installs exactly these versions:
+
+  | Registry | Package | 0.1.12 | 0.2.0 |
+  |---|---|---|---|
+  | PyPI | `abstractgateway` (`[apple]`, `[gpu]` in the profiles) | 0.2.30 | **0.3.0** |
+  | PyPI | `abstractcore` | 2.13.42 | **2.14.0** |
+  | PyPI | `AbstractRuntime` | 0.4.32 | **0.4.33** |
+  | PyPI | `abstractassistant` (`[apple]` on macOS, `[gpu]` in the profiles) | 0.5.0 | 0.5.0 |
+  | PyPI | `abstractagent` | 0.3.13 | 0.3.13 |
+  | PyPI | `AbstractMemory` | 0.3.0 | 0.3.0 |
+  | PyPI | `abstractsemantics` | 0.0.5 | 0.0.5 |
+  | PyPI | `abstractvoice` | 0.11.3 | 0.11.3 |
+  | PyPI | `abstractvision` | 0.3.29 | 0.3.29 |
+  | PyPI | `abstractmusic` | 0.1.15 | 0.1.15 |
+  | npm | `@abstractframework/flow` | 0.3.20 | 0.3.20 |
+  | npm | `@abstractframework/code` | 0.4.2 | 0.4.2 |
+  | npm | `@abstractframework/observer` | 0.1.12 | 0.1.12 |
+  | npm | `@abstractframework/continuum` | 0.2.0 | 0.2.0 |
+  | npm | `@abstractframework/entity` | 0.1.0 | 0.1.0 |
+  | crates.io | `abstractgateway-console` | 0.6.0 | **0.7.0** |
+  | crates.io | `abstractcore-console` | — | **0.2.0** (new) |
+  | crates.io | `abstractcode` | 0.5.1 | 0.5.1 |
+  | crates.io | `abstracttui` | 0.6.0 | 0.6.0 |
+  | GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.2.30 | **0.3.0** |
+  | GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.13.42 | **2.14.0** |
+
+  `RELEASE_VERSIONS`, `NPM_RELEASE_VERSIONS`, `CRATE_RELEASE_VERSIONS`, `abstractframework doctor`,
+  the bootstrap scripts and the generated `docs/installers/install-manifest.json` follow the same
+  matrix.
+- `abstractgateway serve` and `abstractcore serve` bind `127.0.0.1` by default when no auth is
+  configured (pinned packages). See the gateway and AbstractCore changelogs for the details.
+- Install manifest schema version 2: new `bootstrap` section (gateway pin, Python version, extras
+  per profile, script URLs, flags); `post_install` is console-first (`abstractgateway serve` on
+  `127.0.0.1`, `/console`, claim link, service) and no longer lists `abstractcore --config`.
+- `docs/installers/` describes the script bootstrap and the gateway console as the install
+  experience (ADR-0038) instead of a GUI installer manager with signed per-app packages.
+- Linux ARM64 installs no longer need a C compiler with the pinned gateway. Older gateway pins
+  (`--pin 0.2.x`) still need `gcc` to build `psutil`; the installer warns during preflight.
+- The AbstractCore server container image is documented under its published name,
+  `ghcr.io/lpalbou/abstractcore-server`.
+
+### Known limitations
+
+- `install.ps1` is exercised in CI on Windows; the login entry created by
+  `abstractgateway service install` on Windows is experimental.
 
 ## [0.1.12] - 2026-09-23
 

{abstractframework-0.1.12/abstractframework.egg-info → abstractframework-0.2.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: abstractframework
-Version: 0.1.12
+Version: 0.2.1
 Summary: Unified installer and documentation hub for the AbstractFramework ecosystem
 Author-email: Laurent-Philippe Albou <contact@abstractframework.ai>
 License: MIT
@@ -23,21 +23,21 @@ Classifier: Typing :: Typed
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: abstractgateway==0.2.30
+Requires-Dist: abstractgateway==0.3.0
 Requires-Dist: abstractassistant==0.5.0
-Requires-Dist: abstractcore==2.13.42
-Requires-Dist: AbstractRuntime==0.4.32
+Requires-Dist: abstractcore==2.14.0
+Requires-Dist: AbstractRuntime==0.4.33
 Requires-Dist: abstractagent==0.3.13
 Requires-Dist: AbstractMemory==0.3.0
 Requires-Dist: abstractsemantics==0.0.5
-Requires-Dist: abstractvoice==0.11.3
+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.2.30; extra == "apple"
+Requires-Dist: abstractgateway[apple]==0.3.0; extra == "apple"
 Requires-Dist: abstractassistant[apple]==0.5.0; platform_system == "Darwin" and extra == "apple"
 Provides-Extra: gpu
-Requires-Dist: abstractgateway[gpu]==0.2.30; extra == "gpu"
+Requires-Dist: abstractgateway[gpu]==0.3.0; extra == "gpu"
 Requires-Dist: abstractassistant[gpu]==0.5.0; extra == "gpu"
 Dynamic: license-file
 
@@ -56,7 +56,41 @@ AbstractFramework is an ecosystem of composable packages for building AI systems
 
 Think of it as an **agentic OS**: durable runs + replay-first observability + multimodal capabilities — write once, run across providers and deployment modes.
 
-> **Prerequisites**: Python 3.10+. Node.js 18+ for browser UIs. An LLM backend (Ollama, LM Studio, vLLM, or a cloud API key).
+> **Prerequisites**: none for the one-line install below (it provisions Python and, optionally, Node.js). For a manual install: Python 3.10–3.13, Node.js 18+ for browser UIs, and an LLM backend (Ollama, LM Studio, vLLM, or a cloud API key).
+
+---
+
+## Quick start
+
+One line installs the gateway (no admin rights, no system Python), registers it as a login
+service, starts it on `127.0.0.1:8080`, and opens its web console already signed in. A first-run
+guide then sets up a local engine (Ollama, LM Studio, MLX, llama.cpp), downloads a model that fits
+your machine, and lists the apps:
+
+```bash
+# macOS / Linux
+curl -LsSf https://raw.githubusercontent.com/lpalbou/AbstractFramework/main/scripts/install.sh | sh
+```
+
+```powershell
+# Windows 10 22H2+ / 11
+powershell -ExecutionPolicy ByPass -c "irm https://raw.githubusercontent.com/lpalbou/AbstractFramework/main/scripts/install.ps1 | iex"
+```
+
+Add `--with-apps`, `--with-ollama` or `--with-lmstudio` for Node.js and local engines, `--print` to
+see every command first, and `--uninstall` to remove it. Options, the equivalent commands and
+uninstall details: [Install](docs/install.md).
+
+Already have Python? Either entry point works the same way: start it, then open the link it prints.
+
+```bash
+pip install abstractcore && abstractcore serve        # http://127.0.0.1:8000/console#claim=…
+pip install abstractgateway && abstractgateway serve  # http://127.0.0.1:8080/console#claim=…
+```
+
+Both consoles have **Models** (browse models that fit this machine, download, delete) and
+**Engines** (detect and install local engines) tabs; every action also shows its command-line
+equivalent (`abstractcore models …`, `abstractcore engines …`, `abstractgateway models …`).
 
 ---
 
@@ -86,6 +120,12 @@ resp = llm.generate("Explain durable execution in 3 bullets.")
 print(resp.content)
 ```
 
+`abstractcore serve` starts the `/v1` server on `127.0.0.1:8000` and prints a one-time link to its
+web console (Overview, Models, Engines, Providers). The same Models and Engines screens are
+available from the command line (`abstractcore models catalog|list|download|delete`,
+`abstractcore engines status|install`) and in the terminal console
+(`cargo install abstractcore-console`).
+
 AbstractCore gives you one interface for provider switching, tools, structured output, and media — as a Python SDK or via `/v1` for any OpenAI-compatible client.
 
 ### 2) AbstractGateway — durable run control plane (HTTP/SSE APIs)
@@ -100,15 +140,24 @@ Start here if you're building persistent AI applications — agents that run for
 
 ```bash
 pip install abstractgateway
+abstractgateway serve
+```
 
+With no auth configured, `abstractgateway serve` binds `127.0.0.1:8080`, enables user auth,
+creates `default/admin` in the per-user data folder, and prints a one-time sign-in link
+(`http://127.0.0.1:8080/console#claim=…`, valid 10 minutes, this machine only). Open it to reach the
+web console and its first-run guide. `abstractgateway claim` mints a new link;
+`abstractgateway service install` starts the gateway at login.
+
+To choose the data folder, the allowed browser origins or your own workflow bundles, set the
+environment explicitly:
+
+```bash
 export ABSTRACTGATEWAY_USER_AUTH=1
 export ABSTRACTGATEWAY_ALLOWED_ORIGINS="http://localhost:*,http://127.0.0.1:*"
 export ABSTRACTGATEWAY_WORKFLOW_SOURCE=bundle
 export ABSTRACTGATEWAY_DATA_DIR="$PWD/runtime/gateway"
-
-# Optional: set only to serve your own bundle registry instead of the
-# workflows Gateway ships with.
-# export ABSTRACTGATEWAY_FLOWS_DIR="$PWD/bundles"
+# export ABSTRACTGATEWAY_FLOWS_DIR="$PWD/bundles"   # serve your own bundle registry
 
 abstractgateway serve --host 127.0.0.1 --port 8080
 ```
@@ -117,12 +166,10 @@ Out of the box this serves a ready set of workflows — a verify-gated coding
 agent, `deep-research`, and `co-scientist` among them. See
 [shipped workflows](abstractgateway/docs/shipped-workflows.md).
 
-On first local start, Gateway creates `default/admin`, writes the browser-login
-token to `runtime/gateway/auth/bootstrap-admin-token`, and prints the token in
-the terminal. Use that `admin` user token in the built-in web console at
-`http://127.0.0.1:8080/console`, AbstractFlow,
-AbstractCode Web, or AbstractObserver. `ABSTRACTGATEWAY_AUTH_TOKEN` remains a
-legacy server/operator bearer token; it is not a browser sign-in token.
+The `admin` user token is kept in `<data dir>/auth/bootstrap-admin-token`; use it to sign in to
+AbstractFlow, AbstractCode Web or AbstractObserver, or to the console without a claim link.
+`ABSTRACTGATEWAY_AUTH_TOKEN` remains a legacy server/operator bearer token; it is not a browser
+sign-in token.
 
 Monitor runs from a browser, or from a terminal with the gateway console:
 
@@ -134,8 +181,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.2.30` (`0.2.30-gpu` is an experimental NVIDIA
-image) and `ghcr.io/lpalbou/abstractcore:2.13.42`.
+`ghcr.io/lpalbou/abstractgateway:0.3.0` and `ghcr.io/lpalbou/abstractcore-server:2.14.0`.
 
 For artifact and runtime-resource investigation, see
 `docs/guide/runtime-artifacts.md`.
@@ -209,7 +255,8 @@ The ecosystem, grouped by layer. Each name links to the package's own README.
 | [AbstractObserver](abstractobserver/) | Browser UI — monitor, control, and schedule gateway runs | `npx @abstractframework/observer` |
 | [AbstractEntity](abstractentity/) | Summoned-entity manager — roster, blueprint (cognition map + editing), chat drawer, live replay | `npx @abstractframework/entity` |
 | [AbstractContinuum](abstractcontinuum/) | Continuous iterative development and deployment console | `npx @abstractframework/continuum` |
-| **Gateway consoles** | Operator consoles for a running gateway: web at `/console`, terminal via `abstractgateway-console` | built into `abstractgateway`; `cargo install abstractgateway-console` |
+| **Gateway consoles** | Operator consoles for a running gateway: web at `/console` (first-run guide, Models, Engines, providers, users), terminal via `abstractgateway-console` | built into `abstractgateway`; `cargo install abstractgateway-console` |
+| **Core consoles** | Consoles for AbstractCore: web at `/console` of `abstractcore serve`, terminal via `abstractcore-console` (config, Models, Engines) | built into `abstractcore`; `cargo install abstractcore-console` |
 | **Code Web UI** | Browser client of AbstractCode (gateway-backed) | `npx @abstractframework/code` |
 | **Flow Editor** | Visual workflow authoring in the browser | `npx @abstractframework/flow` |
 
@@ -253,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.1.12)
+### Release matrix (abstractframework 0.2.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
@@ -262,14 +309,14 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.2.30 |
+| PyPI | `abstractgateway` | 0.3.0 |
 | PyPI | `abstractassistant` | 0.5.0 |
-| PyPI | `abstractcore` | 2.13.42 |
-| PyPI | `AbstractRuntime` | 0.4.32 |
+| PyPI | `abstractcore` | 2.14.0 |
+| PyPI | `AbstractRuntime` | 0.4.33 |
 | PyPI | `abstractagent` | 0.3.13 |
 | PyPI | `AbstractMemory` | 0.3.0 |
 | PyPI | `abstractsemantics` | 0.0.5 |
-| PyPI | `abstractvoice` | 0.11.3 |
+| PyPI | `abstractvoice` | 0.11.4 |
 | PyPI | `abstractvision` | 0.3.29 |
 | PyPI | `abstractmusic` | 0.1.15 |
 | npm | `@abstractframework/flow` | 0.3.20 |
@@ -278,10 +325,11 @@ and tested together.
 | npm | `@abstractframework/continuum` | 0.2.0 |
 | npm | `@abstractframework/entity` | 0.1.0 |
 | crates.io | `abstractcode` | 0.5.1 |
-| crates.io | `abstractgateway-console` | 0.6.0 |
+| crates.io | `abstractgateway-console` | 0.7.0 |
+| crates.io | `abstractcore-console` | 0.2.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.2.30 (`0.2.30-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore` | 2.13.42 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.3.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.14.0 |
 
 Optional add-ons that are not part of any profile install separately:
 `pip install abstract3d` (0.3.1), `pip install abstractcamera` (0.2.0) and
@@ -304,6 +352,7 @@ See [docs/install.md](docs/install.md) for the full install chooser, `uv`/venv g
 | [docs/glossary.md](docs/glossary.md) | Shared terminology (run, ledger, effect, wait, bundle, …) |
 | [docs/faq.md](docs/faq.md) | Common questions, comparisons, troubleshooting |
 | [docs/api.md](docs/api.md) | Meta-package API (pins, helpers, re-exports) |
+| [docs/workspace-scripts.md](docs/workspace-scripts.md) | Working from source: package tiers, build, status, pull/commit/push scripts |
 
 ---
 
@@ -313,14 +362,21 @@ Clone all sibling repos and build everything in editable mode:
 
 ```bash
 ./scripts/clone.sh           # clone every sibling repository next to this one
-source ./scripts/build.sh    # editable installs into .venv (use `source` to stay in the venv)
+./scripts/deps.sh            # dependency tiers: what builds and installs first, and why
+source ./scripts/build.sh    # Python (editable, into .venv), npm and Rust builds, tier by tier
 ```
 
-Then configure:
+Keep the whole workspace in sync with `./scripts/status.sh` (git overview per tier; `--registry`
+compares local versions with PyPI, npm and crates.io), `./scripts/pull.sh`, `./scripts/commit.sh`
+and `./scripts/push.sh` (a dry run until you add `--yes`). See
+[docs/workspace-scripts.md](docs/workspace-scripts.md) for every script and option.
+
+Then configure providers and models in a console (`abstractcore serve` or
+`abstractgateway serve`, then open the printed link), or from the terminal:
 
 ```bash
-abstractcore --config
-abstractcore --install
+abstractcore --config    # interactive configuration wizard
+abstractcore --install   # check every subsystem and download missing models and dependencies
 ```
 
 ---

{abstractframework-0.1.12 → abstractframework-0.2.1}/README.md

@@ -13,7 +13,41 @@ AbstractFramework is an ecosystem of composable packages for building AI systems
 
 Think of it as an **agentic OS**: durable runs + replay-first observability + multimodal capabilities — write once, run across providers and deployment modes.
 
-> **Prerequisites**: Python 3.10+. Node.js 18+ for browser UIs. An LLM backend (Ollama, LM Studio, vLLM, or a cloud API key).
+> **Prerequisites**: none for the one-line install below (it provisions Python and, optionally, Node.js). For a manual install: Python 3.10–3.13, Node.js 18+ for browser UIs, and an LLM backend (Ollama, LM Studio, vLLM, or a cloud API key).
+
+---
+
+## Quick start
+
+One line installs the gateway (no admin rights, no system Python), registers it as a login
+service, starts it on `127.0.0.1:8080`, and opens its web console already signed in. A first-run
+guide then sets up a local engine (Ollama, LM Studio, MLX, llama.cpp), downloads a model that fits
+your machine, and lists the apps:
+
+```bash
+# macOS / Linux
+curl -LsSf https://raw.githubusercontent.com/lpalbou/AbstractFramework/main/scripts/install.sh | sh
+```
+
+```powershell
+# Windows 10 22H2+ / 11
+powershell -ExecutionPolicy ByPass -c "irm https://raw.githubusercontent.com/lpalbou/AbstractFramework/main/scripts/install.ps1 | iex"
+```
+
+Add `--with-apps`, `--with-ollama` or `--with-lmstudio` for Node.js and local engines, `--print` to
+see every command first, and `--uninstall` to remove it. Options, the equivalent commands and
+uninstall details: [Install](docs/install.md).
+
+Already have Python? Either entry point works the same way: start it, then open the link it prints.
+
+```bash
+pip install abstractcore && abstractcore serve        # http://127.0.0.1:8000/console#claim=…
+pip install abstractgateway && abstractgateway serve  # http://127.0.0.1:8080/console#claim=…
+```
+
+Both consoles have **Models** (browse models that fit this machine, download, delete) and
+**Engines** (detect and install local engines) tabs; every action also shows its command-line
+equivalent (`abstractcore models …`, `abstractcore engines …`, `abstractgateway models …`).
 
 ---
 
@@ -43,6 +77,12 @@ resp = llm.generate("Explain durable execution in 3 bullets.")
 print(resp.content)
 ```
 
+`abstractcore serve` starts the `/v1` server on `127.0.0.1:8000` and prints a one-time link to its
+web console (Overview, Models, Engines, Providers). The same Models and Engines screens are
+available from the command line (`abstractcore models catalog|list|download|delete`,
+`abstractcore engines status|install`) and in the terminal console
+(`cargo install abstractcore-console`).
+
 AbstractCore gives you one interface for provider switching, tools, structured output, and media — as a Python SDK or via `/v1` for any OpenAI-compatible client.
 
 ### 2) AbstractGateway — durable run control plane (HTTP/SSE APIs)
@@ -57,15 +97,24 @@ Start here if you're building persistent AI applications — agents that run for
 
 ```bash
 pip install abstractgateway
+abstractgateway serve
+```
 
+With no auth configured, `abstractgateway serve` binds `127.0.0.1:8080`, enables user auth,
+creates `default/admin` in the per-user data folder, and prints a one-time sign-in link
+(`http://127.0.0.1:8080/console#claim=…`, valid 10 minutes, this machine only). Open it to reach the
+web console and its first-run guide. `abstractgateway claim` mints a new link;
+`abstractgateway service install` starts the gateway at login.
+
+To choose the data folder, the allowed browser origins or your own workflow bundles, set the
+environment explicitly:
+
+```bash
 export ABSTRACTGATEWAY_USER_AUTH=1
 export ABSTRACTGATEWAY_ALLOWED_ORIGINS="http://localhost:*,http://127.0.0.1:*"
 export ABSTRACTGATEWAY_WORKFLOW_SOURCE=bundle
 export ABSTRACTGATEWAY_DATA_DIR="$PWD/runtime/gateway"
-
-# Optional: set only to serve your own bundle registry instead of the
-# workflows Gateway ships with.
-# export ABSTRACTGATEWAY_FLOWS_DIR="$PWD/bundles"
+# export ABSTRACTGATEWAY_FLOWS_DIR="$PWD/bundles"   # serve your own bundle registry
 
 abstractgateway serve --host 127.0.0.1 --port 8080
 ```
@@ -74,12 +123,10 @@ Out of the box this serves a ready set of workflows — a verify-gated coding
 agent, `deep-research`, and `co-scientist` among them. See
 [shipped workflows](abstractgateway/docs/shipped-workflows.md).
 
-On first local start, Gateway creates `default/admin`, writes the browser-login
-token to `runtime/gateway/auth/bootstrap-admin-token`, and prints the token in
-the terminal. Use that `admin` user token in the built-in web console at
-`http://127.0.0.1:8080/console`, AbstractFlow,
-AbstractCode Web, or AbstractObserver. `ABSTRACTGATEWAY_AUTH_TOKEN` remains a
-legacy server/operator bearer token; it is not a browser sign-in token.
+The `admin` user token is kept in `<data dir>/auth/bootstrap-admin-token`; use it to sign in to
+AbstractFlow, AbstractCode Web or AbstractObserver, or to the console without a claim link.
+`ABSTRACTGATEWAY_AUTH_TOKEN` remains a legacy server/operator bearer token; it is not a browser
+sign-in token.
 
 Monitor runs from a browser, or from a terminal with the gateway console:
 
@@ -91,8 +138,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.2.30` (`0.2.30-gpu` is an experimental NVIDIA
-image) and `ghcr.io/lpalbou/abstractcore:2.13.42`.
+`ghcr.io/lpalbou/abstractgateway:0.3.0` and `ghcr.io/lpalbou/abstractcore-server:2.14.0`.
 
 For artifact and runtime-resource investigation, see
 `docs/guide/runtime-artifacts.md`.
@@ -166,7 +212,8 @@ The ecosystem, grouped by layer. Each name links to the package's own README.
 | [AbstractObserver](abstractobserver/) | Browser UI — monitor, control, and schedule gateway runs | `npx @abstractframework/observer` |
 | [AbstractEntity](abstractentity/) | Summoned-entity manager — roster, blueprint (cognition map + editing), chat drawer, live replay | `npx @abstractframework/entity` |
 | [AbstractContinuum](abstractcontinuum/) | Continuous iterative development and deployment console | `npx @abstractframework/continuum` |
-| **Gateway consoles** | Operator consoles for a running gateway: web at `/console`, terminal via `abstractgateway-console` | built into `abstractgateway`; `cargo install abstractgateway-console` |
+| **Gateway consoles** | Operator consoles for a running gateway: web at `/console` (first-run guide, Models, Engines, providers, users), terminal via `abstractgateway-console` | built into `abstractgateway`; `cargo install abstractgateway-console` |
+| **Core consoles** | Consoles for AbstractCore: web at `/console` of `abstractcore serve`, terminal via `abstractcore-console` (config, Models, Engines) | built into `abstractcore`; `cargo install abstractcore-console` |
 | **Code Web UI** | Browser client of AbstractCode (gateway-backed) | `npx @abstractframework/code` |
 | **Flow Editor** | Visual workflow authoring in the browser | `npx @abstractframework/flow` |
 
@@ -210,7 +257,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.1.12)
+### Release matrix (abstractframework 0.2.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
@@ -219,14 +266,14 @@ and tested together.
 
 | Registry | Package | Version |
 |---|---|---|
-| PyPI | `abstractgateway` | 0.2.30 |
+| PyPI | `abstractgateway` | 0.3.0 |
 | PyPI | `abstractassistant` | 0.5.0 |
-| PyPI | `abstractcore` | 2.13.42 |
-| PyPI | `AbstractRuntime` | 0.4.32 |
+| PyPI | `abstractcore` | 2.14.0 |
+| PyPI | `AbstractRuntime` | 0.4.33 |
 | PyPI | `abstractagent` | 0.3.13 |
 | PyPI | `AbstractMemory` | 0.3.0 |
 | PyPI | `abstractsemantics` | 0.0.5 |
-| PyPI | `abstractvoice` | 0.11.3 |
+| PyPI | `abstractvoice` | 0.11.4 |
 | PyPI | `abstractvision` | 0.3.29 |
 | PyPI | `abstractmusic` | 0.1.15 |
 | npm | `@abstractframework/flow` | 0.3.20 |
@@ -235,10 +282,11 @@ and tested together.
 | npm | `@abstractframework/continuum` | 0.2.0 |
 | npm | `@abstractframework/entity` | 0.1.0 |
 | crates.io | `abstractcode` | 0.5.1 |
-| crates.io | `abstractgateway-console` | 0.6.0 |
+| crates.io | `abstractgateway-console` | 0.7.0 |
+| crates.io | `abstractcore-console` | 0.2.0 |
 | crates.io | `abstracttui` | 0.6.0 |
-| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.2.30 (`0.2.30-gpu` experimental) |
-| GHCR | `ghcr.io/lpalbou/abstractcore` | 2.13.42 |
+| GHCR | `ghcr.io/lpalbou/abstractgateway` | 0.3.0 (`gpu-latest` / `<version>-gpu` experimental) |
+| GHCR | `ghcr.io/lpalbou/abstractcore-server` | 2.14.0 |
 
 Optional add-ons that are not part of any profile install separately:
 `pip install abstract3d` (0.3.1), `pip install abstractcamera` (0.2.0) and
@@ -261,6 +309,7 @@ See [docs/install.md](docs/install.md) for the full install chooser, `uv`/venv g
 | [docs/glossary.md](docs/glossary.md) | Shared terminology (run, ledger, effect, wait, bundle, …) |
 | [docs/faq.md](docs/faq.md) | Common questions, comparisons, troubleshooting |
 | [docs/api.md](docs/api.md) | Meta-package API (pins, helpers, re-exports) |
+| [docs/workspace-scripts.md](docs/workspace-scripts.md) | Working from source: package tiers, build, status, pull/commit/push scripts |
 
 ---
 
@@ -270,14 +319,21 @@ Clone all sibling repos and build everything in editable mode:
 
 ```bash
 ./scripts/clone.sh           # clone every sibling repository next to this one
-source ./scripts/build.sh    # editable installs into .venv (use `source` to stay in the venv)
+./scripts/deps.sh            # dependency tiers: what builds and installs first, and why
+source ./scripts/build.sh    # Python (editable, into .venv), npm and Rust builds, tier by tier
 ```
 
-Then configure:
+Keep the whole workspace in sync with `./scripts/status.sh` (git overview per tier; `--registry`
+compares local versions with PyPI, npm and crates.io), `./scripts/pull.sh`, `./scripts/commit.sh`
+and `./scripts/push.sh` (a dry run until you add `--yes`). See
+[docs/workspace-scripts.md](docs/workspace-scripts.md) for every script and option.
+
+Then configure providers and models in a console (`abstractcore serve` or
+`abstractgateway serve`, then open the printed link), or from the terminal:
 
 ```bash
-abstractcore --config
-abstractcore --install
+abstractcore --config    # interactive configuration wizard
+abstractcore --install   # check every subsystem and download missing models and dependencies
 ```
 
 ---

{abstractframework-0.1.12 → abstractframework-0.2.1}/abstractframework/__init__.py

@@ -10,18 +10,18 @@ Most implementation functionality still lives in component projects.
 
 from __future__ import annotations
 
-__version__ = "0.1.12"
+__version__ = "0.2.1"
 __author__ = "Laurent-Philippe Albou"
 __license__ = "MIT"
 
 RELEASE_VERSIONS: dict[str, str] = {
-    "abstractcore": "2.13.42",
-    "abstractruntime": "0.4.32",
+    "abstractcore": "2.14.0",
+    "abstractruntime": "0.4.33",
     "abstractagent": "0.3.13",
-    "abstractgateway": "0.2.30",
+    "abstractgateway": "0.3.0",
     "abstractmemory": "0.3.0",
     "abstractsemantics": "0.0.5",
-    "abstractvoice": "0.11.3",
+    "abstractvoice": "0.11.4",
     "abstractvision": "0.3.29",
     "abstractmusic": "0.1.15",
     "abstractassistant": "0.5.0",
@@ -48,6 +48,15 @@ NPM_RELEASE_VERSIONS: dict[str, str] = {
     "@abstractframework/entity": "0.1.0",
 }
 
+# Terminal tools published on crates.io alongside this release (installed with `cargo install`,
+# or by the bootstrap scripts' --with-console / --with-code-cli flags).
+CRATE_RELEASE_VERSIONS: dict[str, str] = {
+    "abstractgateway-console": "0.7.0",
+    "abstractcore-console": "0.2.0",
+    "abstractcode": "0.5.1",
+    "abstracttui": "0.6.0",
+}
+
 CORE_DEFAULT_EXTRAS = [
     "remote",
     "tools",
@@ -90,6 +99,7 @@ def get_release_profile() -> dict[str, object]:
         "packages": RELEASE_VERSIONS.copy(),
         "distributions": PACKAGE_DISTRIBUTIONS.copy(),
         "npm_packages": NPM_RELEASE_VERSIONS.copy(),
+        "crates": CRATE_RELEASE_VERSIONS.copy(),
         "core_extras": list(CORE_DEFAULT_EXTRAS),
         "install_profiles": {
             "light": "pip install abstractframework",