AbstractRuntime 0.4.34__tar.gz → 0.5.0__tar.gz

{abstractruntime-0.4.34 → abstractruntime-0.5.0}/ACKNOWLEDGMENTS.md

@@ -7,14 +7,15 @@ The canonical dependency list lives in `pyproject.toml`.
 
 ## Runtime dependencies (core install)
 
-- **abstractsemantics** (`>=0.0.3`) — structured schema registry support (declared in `pyproject.toml`, used in `src/abstractruntime/integrations/abstractmemory/effect_handlers.py` and VisualFlow execution wiring).
-- **AbstractMemory** (`>=0.2.6`) — TripleStore models and store contract used by Runtime's `MEMORY_KG_*` effects. Durable/vector backend dependencies such as LanceDB remain selected by hosts.
+- **abstractsemantics** (`>=0.0.5`) — structured schema registry support (declared in `pyproject.toml`, used in `src/abstractruntime/integrations/abstractmemory/effect_handlers.py` and VisualFlow execution wiring).
+- **AbstractMemory** (`>=0.3.0`) — TripleStore models and store contract used by Runtime's `MEMORY_KG_*` effects. Durable/vector backend dependencies such as LanceDB remain selected by hosts.
 
 ## Runtime integrations
-- **abstractcore** (`>=2.13.31`) — LLM, tools, media, and capability integration used by the base `abstractruntime` install (declared in `pyproject.toml`, implementation under `src/abstractruntime/integrations/abstractcore/*`, docs: `docs/integrations/abstractcore.md`).
+- **abstractcore** (`abstractcore[remote,tools,vision,voice,audio,music]>=2.15.1`) — LLM, tools, media, and capability integration used by the base `abstractruntime` install; the `apple` and `gpu` extras select `abstractcore[all-apple]` / `abstractcore[all-gpu]` at the same floor (declared in `pyproject.toml`, implementation under `src/abstractruntime/integrations/abstractcore/*`, docs: `docs/integrations/abstractcore.md`).
   - The AbstractCore integration uses **httpx** for remote mode (`src/abstractruntime/integrations/abstractcore/llm_client.py`) and **pydantic** for structured validation (`src/abstractruntime/integrations/abstractcore/effect_handlers.py`). These are provided by AbstractCore’s dependency set.
-- **abstractcore[tools]** (`>=2.13.31`) — toolchain extra used by the base Runtime and `abstractruntime-mcp-worker` entry point (declared in `pyproject.toml`) and intended to include HTML parsing dependencies (see comments in `pyproject.toml`).
-- **RestrictedPython** (optional) — used for sandboxed execution of VisualFlow “Code” nodes when available (`src/abstractruntime/visualflow_compiler/visual/code_executor.py`).
+  - The `tools` extra of AbstractCore backs the base Runtime toolset and the `abstractruntime-mcp-worker` entry point.
+- **RestrictedPython** (`>=7.0`, core install) — sandbox for VisualFlow “Code” nodes and pin expressions (`src/abstractruntime/visualflow_compiler/visual/code_executor.py`).
+- **pypdf** and **reportlab** — VisualFlow `Read PDF` / `Write PDF` nodes in the base install.
 
 ## Build & test tooling
 

{abstractruntime-0.4.34 → abstractruntime-0.5.0}/CHANGELOG.md

@@ -5,17 +5,147 @@ All notable changes to AbstractRuntime will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased]
+## [0.5.0] - 2026-09-26
+
+### Fixed
+
+- When an LLM call is re-run after a stray kill, its interrupted first run ends with
+  `delta_end` `cancelled` with `detail: "reinvoked"` (the run continues) and the re-run streams
+  under its own call id, so a live view never shows a partial answer followed by the full one.
+- The last batch of a streamed reply is sent before the call's final record is written, never just
+  after it; text arriving once the call has returned is dropped.
+- A streamed reply that only turns out to lack token usage at the end now ends with
+  `reason: "completed"` in the live view (the text did stream); `usage_unavailable` is recorded on
+  the `LLM_CALL` record only.
+- Streamed answers without usage are no longer invisible to the aborted-generation check: it judges
+  them from `finish_reason` and the text, and the record says so with `metadata.usage_estimated`.
+- Servers that reject `stream_options` but still send token usage (LM Studio) stream again.
+  Streaming is refused for missing usage only when the provider reports the rejection AND a
+  streamed answer came back without usage; one call in ten streams again to re-check, and a
+  streamed answer with usage lifts the refusal.
+- A child run or a VisualFlow node can no longer switch off the host's built-in workspace
+  protection: it may add `workspace_builtin_deny_prefixes`, never remove the host's, and cannot
+  widen `workspace_builtin_allow` beyond the parent's (its own folder counts only when it is
+  inside an allowed folder).
+- Harmony-format models (gpt-oss) stream their answers live: the `final` channel is sent as
+  content, `analysis` as reasoning, and tool calls are held back. A call whose whole answer is held
+  back ends with `reason: "unavailable"`, `detail: "tool_envelope_holdback"` instead of a silent
+  empty live view.
+- One streamed answer without token usage no longer turns streaming off for that model until
+  restart. That call is reported (`usage_unavailable`) and the next call streams again; streaming
+  stays off only when the provider reports that its server rejects usage in streams.
+- Host-protected folders no longer grow the system prompt. A host can pass its own protection as
+  `workspace_builtin_deny_prefixes` (for example the gateway's data folder and credential folders)
+  and `workspace_builtin_allow` (the run's own folder inside it). File tools, listings and the
+  shell's starting folder are refused under a denied prefix, except under an allow entry. These
+  entries are enforced but never written into the model's system prompt, which keeps it identical
+  from turn to turn (and the prompt cache warm); only the operator's own `workspace_ignored_paths`
+  are shown to the model. Child runs inherit both lists.
+- MLX calls stream again when they use a prompt-cache key: AbstractCore now puts the prompt-cache
+  record on the stream's last chunk, so the streamed record matches the non-streamed one.
+- Streamed LLM calls now record the same result as non-streamed ones: `raw_response` is present
+  (the provider's terminal chunk), and the last reasoning fragment no longer leaks into
+  `metadata.reasoning_delta`.
+- Changing the default text model no longer leaves the previous model in memory. The previous
+  in-process model (MLX or HuggingFace) is unloaded from the whole process before the new default
+  is loaded, unless the pool still uses it or it is locked. A call still generating on it is not
+  cancelled; the model is unloaded when that call ends. Measured on a 27B MLX model: 17 GB stayed
+  resident after a console switch; now it is freed.
+- Changing the default model in one service never unloads a model another service, user or
+  entity in the same process still uses or has locked. The check covers every owner in the
+  process and runs under one lock with the unload, so a model being loaded again at that moment
+  is not unloaded either.
+- `list_model_residency` diagnostics carry `pending_ejects` (a previous model waiting for its
+  running call to end before it is unloaded) and `last_switch_ejects` (unloaded, kept because
+  something still uses it, or failed, with the reason).
+- A load with `ttl_s` or `keep_alive` on an in-process model, or on a model that was already
+  loaded, now reports them under `unsupported_options` with a warning; provider warnings appear in
+  the response's top-level `warnings`.
+- A model load that fails part-way unloads what it had loaded.
+- Chat compaction summarizes a run with the model the run uses, instead of loading the default
+  model just for the summary. A run with no model of its own is summarized with the current
+  default model, resolved on each call; the summarizer no longer holds the model that was the
+  default at startup.
+- Unloading a model by `runtime_id` alone now works for every task: TTS, STT, image, music and
+  embedding rows, not only text. A backend's own id is looked up in the listing.
+- Listings no longer report a task error on every call for `image_upscale`, `video_generation`,
+  `text_to_video`, `image_to_video` and `text_to_audio`; they are served by the image and music
+  capabilities.
+- Changing a capability default unloads the models the previous capability routes had loaded
+  instead of leaving them in memory.
+- Unloading a local MLX model through the runtime (`model_residency` unload, on
+  a single client or the multi-model pool) now frees it from every holder in
+  the process, not only from the runtime's own instance. Before, the weights
+  could stay in memory when another part of the process still held the model
+  (for example a client created with a per-request override, a chat summarizer
+  built at startup, or a runtime left over after a bundle reload), and the
+  unload still reported success. The unload result now includes a
+  `process_eject` report and names what, if anything, is still held.
+- Model residency listings now show MLX models the process still holds, even
+  when the runtime's own pool no longer references them
+  (`provider_state: "resident_via_other_holders"`). Such a model can be
+  unloaded from the listing like any other.
+
+### Added
+
+- **Live token streaming.** `Runtime.set_live_delta_sink(sink)` lets a host receive the text of an
+  answer while it is generated. For runs started with `_runtime.stream: true`, each LLM call streams
+  and the sink gets `llm.delta` events (`run_id`, `parent_run_id`, `node_id`, `call_id` = the LLM
+  call's step id, `seq`, `text`, `channel` = `content` or `reasoning`) and one `llm.delta_end`
+  (`completed`, `failed`, `cancelled`, or `unavailable` with a `detail`) after the call's final
+  record is written. Deltas are never written to the ledger. Thinking is sent on its own `reasoning`
+  channel, including inline `<think>` markup, and tool-call markup never reaches the live text.
+  A call streams only when its recorded result keeps its usage, `raw_response` and prompt-cache
+  telemetry; otherwise it runs non-streamed and the reason is sent to the client and recorded as
+  `_runtime_observability.stream_unavailable`. Child runs inherit `stream`. `Runtime.start`
+  refuses a non-boolean `_runtime.stream`. Remote mode (AbstractCore server) stays non-streaming.
+  See `docs/integrations/abstractcore.md#live-token-streaming`.
+- Embedding models loaded in the process appear in `list_model_residency` as `task: "embedding"`
+  rows (`local:embedding:huggingface:<model>`, with holders and bytes) and can be unloaded like any
+  other model.
+- HuggingFace models held in the process outside the runtime's pool are listed and unloaded like
+  MLX ones.
+
+### Changed
+
+- Compatibility: AbstractRuntime 0.5.0 requires AbstractCore 2.16.0 or newer (was 2.15.1 in
+  0.4.35) in the base install and in the `apple` and `gpu` extras, and `models_engines_support()`
+  reports 2.16.0 as `required`. The live streaming, process-wide unload and residency features above
+  use modules that first ship in AbstractCore 2.16.0. Upgrading AbstractRuntime upgrades AbstractCore
+  accordingly; if you pin AbstractCore yourself, raise the pin to 2.16.0.
+
+## [0.4.35] - 2026-09-25
+
+### Fixed
+
+- `models_engines_support()` and the `AbstractCoreTooOld` error now name
+  AbstractCore 2.15.1 as the required version (they said 2.14.0), matching the
+  base-install floor. Who is affected: hosts such as AbstractGateway that read
+  `required` to decide whether the models and engines features are usable. They
+  could accept AbstractCore 2.14.x, where `host_job_cancel(by=..., user=...)`
+  fails. No action is needed if you install AbstractRuntime normally: the
+  AbstractCore floor is unchanged at 2.15.1.
+
+### Documentation
+
+- `ROADMAP.md` no longer shows a stale "v0.4.2" status or a priority list; it
+  points to `CHANGELOG.md` and the AbstractFramework backlog.
 
 ## [0.4.34] - 2026-09-24
 
 ### Changed
 
-- `config_facade.host_job_cancel(job_id, *, by="api", user=None)` passes who asked for a cancel to
-  AbstractCore (needs AbstractCore with `HostJobRegistry.cancel(by=, user=)`), so a cancelled
-  download can say who cancelled it.
-- The AbstractCore floor is now 2.15.1 in the base install and in the `apple`
-  and `gpu` extras (the release whose host-job cancel takes `by` and `user`).
+- `config_facade.host_job_cancel(job_id, *, by="api", user=None)` records who
+  cancelled a host job (a model download, delete or engine install): `by`
+  (`api`, or `console` for a click in an embedded console) and the signed-in
+  `user` are stored on the job as `cancelled_by`, `cancelled_by_user` and
+  `ended_reason`. Existing calls without these arguments keep working and are
+  recorded as `by="api"`. Hosts such as AbstractGateway can pass the requesting
+  account to show who cancelled a job.
+- Compatibility: AbstractRuntime 0.4.34 requires AbstractCore 2.15.1 or newer
+  (was 2.14.0) in the base install and in the `apple` and `gpu` extras.
+  Upgrading AbstractRuntime upgrades AbstractCore accordingly; if you pin
+  AbstractCore yourself, raise the pin to 2.15.1 as well.
 
 ## [0.4.33] - 2026-09-23
 
@@ -865,7 +995,9 @@ AbstractRuntime is the durable execution substrate designed to pair with Abstrac
 
 Initial development version with basic proof-of-concept features.
 
-[Unreleased]: https://github.com/lpalbou/abstractruntime/compare/v0.4.34...HEAD
+[Unreleased]: https://github.com/lpalbou/abstractruntime/compare/v0.5.0...HEAD
+[0.5.0]: https://github.com/lpalbou/abstractruntime/compare/v0.4.35...v0.5.0
+[0.4.35]: https://github.com/lpalbou/abstractruntime/compare/v0.4.34...v0.4.35
 [0.4.34]: https://github.com/lpalbou/abstractruntime/compare/v0.4.33...v0.4.34
 [0.4.33]: https://github.com/lpalbou/abstractruntime/compare/v0.4.32...v0.4.33
 [0.4.32]: https://github.com/lpalbou/abstractruntime/compare/v0.4.29...v0.4.32

{abstractruntime-0.4.34 → abstractruntime-0.5.0}/CONTRIBUTING.md

@@ -22,6 +22,9 @@ python -m pip install -e ".[test,docs]"
 python -m pytest -q
 ```
 
+Inside the AbstractFramework workspace, prefer `python -P -m pytest tests -q`: `-P` keeps the current folder off
+`sys.path`, so a workspace folder named like a package (for example `abstractflow/`) cannot shadow it.
+
 If you cloned **only** this repo (without the AbstractFramework workspace), make sure the sibling packages above are importable (install them or clone them next to this repo) before running the full test suite.
 
 ## Repo map (source of truth)
@@ -56,6 +59,12 @@ When behavior changes, update:
 - `docs/architecture.md` (semantics/invariants)
 - `CHANGELOG.md` (user-visible changes)
 
+List every `docs/*.md` page in `docs/README.md`. Keep `llms.txt` (the hand-curated index) and
+`llms-full.txt` in step with the documentation in the same change. `llms-full.txt` is generated:
+run `python scripts/generate_llms_full.py` after editing any page it includes, and
+`python scripts/generate_llms_full.py --check` to confirm it is current (it exits 1 when the file
+is stale). Add a page to the script's `DOCUMENTS` list when it joins the core set.
+
 ## Releases
 
 - Bump `version` in `pyproject.toml`

{abstractruntime-0.4.34 → abstractruntime-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: AbstractRuntime
-Version: 0.4.34
+Version: 0.5.0
 Summary: AbstractRuntime: a durable graph runner designed to pair with AbstractCore.
 Project-URL: AbstractCore (website), https://www.abstractcore.ai/
 Project-URL: AbstractRuntime (GitHub), https://github.com/lpalbou/abstractruntime
@@ -20,7 +20,7 @@ Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Requires-Python: >=3.10
-Requires-Dist: abstractcore[audio,music,remote,tools,vision,voice]>=2.15.1
+Requires-Dist: abstractcore[audio,music,remote,tools,vision,voice]>=2.16.0
 Requires-Dist: abstractmemory>=0.3.0
 Requires-Dist: abstractsemantics>=0.0.5
 Requires-Dist: anyio<5.0.0,>=4.12.1
@@ -35,14 +35,14 @@ Requires-Dist: reportlab<5.0.0,>=4.0.0
 Requires-Dist: restrictedpython>=7.0
 Requires-Dist: unstructured[docx,odt,pptx,rtf,xlsx]<0.19.0,>=0.18.32
 Provides-Extra: apple
-Requires-Dist: abstractcore[all-apple]>=2.15.1; extra == 'apple'
+Requires-Dist: abstractcore[all-apple]>=2.16.0; extra == 'apple'
 Requires-Dist: setuptools<82.0.0,>=80.10.2; extra == 'apple'
 Provides-Extra: docs
 Requires-Dist: mkdocs-material>=9.0.0; extra == 'docs'
 Requires-Dist: mkdocs>=1.6.0; extra == 'docs'
 Requires-Dist: pymdown-extensions>=10.0; extra == 'docs'
 Provides-Extra: gpu
-Requires-Dist: abstractcore[all-gpu]>=2.15.1; extra == 'gpu'
+Requires-Dist: abstractcore[all-gpu]>=2.16.0; extra == 'gpu'
 Requires-Dist: setuptools<82.0.0,>=77.0.3; extra == 'gpu'
 Provides-Extra: test
 Requires-Dist: pytest>=7.0.0; extra == 'test'
@@ -54,7 +54,7 @@ Description-Content-Type: text/markdown
 
 It is designed for long-running workflows that must survive restarts and explicitly model blocking (human input, timers, external events, subworkflows) without keeping Python stacks alive.
 
-**Version:** 0.4.34 • **Python:** 3.10+
+**Version:** 0.5.0 • **Python:** 3.10+
 
 **Status:** pre-1.0 (API may evolve). For production use, pin versions and follow `CHANGELOG.md`.
 
@@ -82,7 +82,7 @@ Remote-light runtime:
 pip install abstractruntime
 ```
 
-The base install includes AbstractCore 2.15.1 or newer with remote provider,
+The base install includes AbstractCore 2.16.0 or newer with remote provider,
 tool, vision, voice, audio, and music integration, plus the
 `abstractruntime-mcp-worker` entry point. It keeps inference remote/light by
 default: local engines such as MLX, vLLM, HuggingFace/Torch, Diffusers, and
@@ -146,7 +146,7 @@ state = rt.resume(
 assert state.status.value == "completed"
 ```
 
-## What’s included (v0.4.34)
+## What’s included (v0.5.0)
 
 Kernel (import-light):
 - workflow graphs: `WorkflowSpec` (`src/abstractruntime/core/spec.py`)
@@ -179,7 +179,7 @@ Drivers + distribution:
   Core media controls, including `count`/`n`, `seeds`, ordered
   `lora_adapters`, and video `flow_shift`, while keeping provider/model/task
   truth in AbstractCore and AbstractVision.
-- `history_bundle` now exports replay-safe `resolved_actions` summaries derived
+- `history_bundle` exports replay-safe `resolved_actions` summaries derived
   from Core request/output route resolution, so thin clients can reconstruct
   what capability ran without reverse-engineering prompt prose.
 - VisualFlow structured LLM/Agent results preserve `response` as text and expose
@@ -189,12 +189,15 @@ Drivers + distribution:
 
 Runtime-owned integrations:
 - AbstractCore (LLM + tools, `MODEL_RESIDENCY` with residency locks and context estimates, public discovery/host/run facades, cached sessions with per-session prompt-cache listing/clearing, host memory snapshots, local-only prompt-cache export/import admin, durable bloc prompt-cache controls, bindings, lifecycle operations, generated image/video/voice/music outputs with progress events, host email helpers, Telegram host wrappers, and tool approval waits): `docs/integrations/abstractcore.md`
-- AbstractCore models and engines for hosts (AbstractCore 2.14.0+): `config_facade` passes through the host profile, local-engine status and installs, the model catalog with fit verdicts, installed models, deletes, host jobs and the embeddable console screens: `docs/integrations/abstractcore.md#models-engines-and-host-jobs-config-facade`
+- AbstractCore models and engines for hosts: `config_facade` passes through the host profile, local-engine status and installs, the model catalog with fit verdicts, installed models, deletes, host jobs (with who-cancelled attribution) and the embeddable console screens: `docs/integrations/abstractcore.md#models-engines-and-host-jobs-config-facade`
 - For outbound comms, use the durable run facade when the send belongs to a run: `get_abstractcore_run_facade(...).send_email(...)` / `send_telegram_message(...)`. If that child run pauses for approval or passthrough execution, resume it through `resume_tool_calls(...)`. Direct host-facade send helpers and the standalone email comms facade remain host-local and nondurable.
 - AbstractMemory TripleStore integration for `MEMORY_KG_*` effects. Runtime
   depends on the light AbstractMemory contract; hosts choose storage backends
   such as LanceDB, SQLite, or in-memory stores.
 - comms toolset gating (email/WhatsApp/Telegram): `docs/tools-comms.md`
+- live token streaming: `Runtime.set_live_delta_sink(sink)` plus `_runtime.stream: true` delivers `llm.delta` / `llm.delta_end` events while an answer is generated, outside the ledger (`docs/integrations/abstractcore.md#live-token-streaming`)
+- model switching in a shared process: changing the default model unloads the previous in-process model unless another owner in the process still uses it (`docs/integrations/abstractcore.md#unloading-and-switching-models`)
+- workspace-scoped file and shell tools driven by `workspace_*` run vars, including host-only protected folders that are enforced without being shown to the model (`docs/integrations/abstractcore.md#workspace-scoped-tools`)
 
 ## Built-in scheduler (zero-config)
 
@@ -232,7 +235,11 @@ sr = create_scheduled_runtime(
 | [Troubleshooting](docs/troubleshooting.md) | Symptom-oriented setup, runtime, and integration fixes |
 | [Architecture](docs/architecture.md) | Component map + diagrams |
 | [Overview](docs/proposal.md) | Design goals, core concepts, and scope |
-| [Integrations](docs/integrations/) | Integration guides (AbstractCore) |
+| [AbstractCore Integration](docs/integrations/abstractcore.md) | `LLM_CALL` / `TOOL_CALLS`, host facades, models/engines/host jobs |
+| [Artifacts](docs/artifacts.md) | Artifact identity, descriptors, catalog search and access stats |
+| [Tool Approval](docs/tool-approval.md) | Tool risk tiers, run-policy ceiling, per-call refiners |
+| [Comms Toolset](docs/tools-comms.md) | Opt-in email/WhatsApp/Telegram tools |
+| [Entity Runtime](docs/entity-runtime.md) | Per-entity runtimes, homes, leases, visit waits |
 | [Snapshots](docs/snapshots.md) | Named checkpoints for run state |
 | [Provenance](docs/provenance.md) | Tamper-evident ledger documentation |
 | [Evidence](docs/evidence.md) | Artifact-backed evidence capture for web/command tools |
@@ -244,7 +251,7 @@ sr = create_scheduled_runtime(
 | [Code of Conduct](CODE_OF_CONDUCT.md) | Contributor conduct expectations |
 | [Security](SECURITY.md) | Responsible vulnerability reporting |
 | [Acknowledgments](ACKNOWLEDGMENTS.md) | Credits |
-| [ROADMAP](ROADMAP.md) | Prioritized next steps |
+| [ROADMAP](ROADMAP.md) | Current status and longer-term direction |
 
 ## Development
 

{abstractruntime-0.4.34 → abstractruntime-0.5.0}/README.md

@@ -4,7 +4,7 @@
 
 It is designed for long-running workflows that must survive restarts and explicitly model blocking (human input, timers, external events, subworkflows) without keeping Python stacks alive.
 
-**Version:** 0.4.34 • **Python:** 3.10+
+**Version:** 0.5.0 • **Python:** 3.10+
 
 **Status:** pre-1.0 (API may evolve). For production use, pin versions and follow `CHANGELOG.md`.
 
@@ -32,7 +32,7 @@ Remote-light runtime:
 pip install abstractruntime
 ```
 
-The base install includes AbstractCore 2.15.1 or newer with remote provider,
+The base install includes AbstractCore 2.16.0 or newer with remote provider,
 tool, vision, voice, audio, and music integration, plus the
 `abstractruntime-mcp-worker` entry point. It keeps inference remote/light by
 default: local engines such as MLX, vLLM, HuggingFace/Torch, Diffusers, and
@@ -96,7 +96,7 @@ state = rt.resume(
 assert state.status.value == "completed"
 ```
 
-## What’s included (v0.4.34)
+## What’s included (v0.5.0)
 
 Kernel (import-light):
 - workflow graphs: `WorkflowSpec` (`src/abstractruntime/core/spec.py`)
@@ -129,7 +129,7 @@ Drivers + distribution:
   Core media controls, including `count`/`n`, `seeds`, ordered
   `lora_adapters`, and video `flow_shift`, while keeping provider/model/task
   truth in AbstractCore and AbstractVision.
-- `history_bundle` now exports replay-safe `resolved_actions` summaries derived
+- `history_bundle` exports replay-safe `resolved_actions` summaries derived
   from Core request/output route resolution, so thin clients can reconstruct
   what capability ran without reverse-engineering prompt prose.
 - VisualFlow structured LLM/Agent results preserve `response` as text and expose
@@ -139,12 +139,15 @@ Drivers + distribution:
 
 Runtime-owned integrations:
 - AbstractCore (LLM + tools, `MODEL_RESIDENCY` with residency locks and context estimates, public discovery/host/run facades, cached sessions with per-session prompt-cache listing/clearing, host memory snapshots, local-only prompt-cache export/import admin, durable bloc prompt-cache controls, bindings, lifecycle operations, generated image/video/voice/music outputs with progress events, host email helpers, Telegram host wrappers, and tool approval waits): `docs/integrations/abstractcore.md`
-- AbstractCore models and engines for hosts (AbstractCore 2.14.0+): `config_facade` passes through the host profile, local-engine status and installs, the model catalog with fit verdicts, installed models, deletes, host jobs and the embeddable console screens: `docs/integrations/abstractcore.md#models-engines-and-host-jobs-config-facade`
+- AbstractCore models and engines for hosts: `config_facade` passes through the host profile, local-engine status and installs, the model catalog with fit verdicts, installed models, deletes, host jobs (with who-cancelled attribution) and the embeddable console screens: `docs/integrations/abstractcore.md#models-engines-and-host-jobs-config-facade`
 - For outbound comms, use the durable run facade when the send belongs to a run: `get_abstractcore_run_facade(...).send_email(...)` / `send_telegram_message(...)`. If that child run pauses for approval or passthrough execution, resume it through `resume_tool_calls(...)`. Direct host-facade send helpers and the standalone email comms facade remain host-local and nondurable.
 - AbstractMemory TripleStore integration for `MEMORY_KG_*` effects. Runtime
   depends on the light AbstractMemory contract; hosts choose storage backends
   such as LanceDB, SQLite, or in-memory stores.
 - comms toolset gating (email/WhatsApp/Telegram): `docs/tools-comms.md`
+- live token streaming: `Runtime.set_live_delta_sink(sink)` plus `_runtime.stream: true` delivers `llm.delta` / `llm.delta_end` events while an answer is generated, outside the ledger (`docs/integrations/abstractcore.md#live-token-streaming`)
+- model switching in a shared process: changing the default model unloads the previous in-process model unless another owner in the process still uses it (`docs/integrations/abstractcore.md#unloading-and-switching-models`)
+- workspace-scoped file and shell tools driven by `workspace_*` run vars, including host-only protected folders that are enforced without being shown to the model (`docs/integrations/abstractcore.md#workspace-scoped-tools`)
 
 ## Built-in scheduler (zero-config)
 
@@ -182,7 +185,11 @@ sr = create_scheduled_runtime(
 | [Troubleshooting](docs/troubleshooting.md) | Symptom-oriented setup, runtime, and integration fixes |
 | [Architecture](docs/architecture.md) | Component map + diagrams |
 | [Overview](docs/proposal.md) | Design goals, core concepts, and scope |
-| [Integrations](docs/integrations/) | Integration guides (AbstractCore) |
+| [AbstractCore Integration](docs/integrations/abstractcore.md) | `LLM_CALL` / `TOOL_CALLS`, host facades, models/engines/host jobs |
+| [Artifacts](docs/artifacts.md) | Artifact identity, descriptors, catalog search and access stats |
+| [Tool Approval](docs/tool-approval.md) | Tool risk tiers, run-policy ceiling, per-call refiners |
+| [Comms Toolset](docs/tools-comms.md) | Opt-in email/WhatsApp/Telegram tools |
+| [Entity Runtime](docs/entity-runtime.md) | Per-entity runtimes, homes, leases, visit waits |
 | [Snapshots](docs/snapshots.md) | Named checkpoints for run state |
 | [Provenance](docs/provenance.md) | Tamper-evident ledger documentation |
 | [Evidence](docs/evidence.md) | Artifact-backed evidence capture for web/command tools |
@@ -194,7 +201,7 @@ sr = create_scheduled_runtime(
 | [Code of Conduct](CODE_OF_CONDUCT.md) | Contributor conduct expectations |
 | [Security](SECURITY.md) | Responsible vulnerability reporting |
 | [Acknowledgments](ACKNOWLEDGMENTS.md) | Credits |
-| [ROADMAP](ROADMAP.md) | Prioritized next steps |
+| [ROADMAP](ROADMAP.md) | Current status and longer-term direction |
 
 ## Development
 

{abstractruntime-0.4.34 → abstractruntime-0.5.0}/ROADMAP.md

@@ -1,6 +1,8 @@
 # AbstractRuntime Roadmap
 
-## Current status (v0.4.2)
+## Current status
+
+What changed in each release is in [CHANGELOG.md](CHANGELOG.md); planned work is tracked in the [AbstractFramework backlog](https://github.com/lpalbou/abstractframework/tree/main/docs/backlog).
 
 AbstractRuntime provides a durable workflow kernel plus optional integrations:
 - durable execution: `Runtime.start/tick/resume`, explicit `WaitState` (`src/abstractruntime/core/runtime.py`)
@@ -13,22 +15,6 @@ AbstractRuntime provides a durable workflow kernel plus optional integrations:
 - VisualFlow compiler + WorkflowBundles (`src/abstractruntime/visualflow_compiler/*`, `src/abstractruntime/workflow_bundle/*`)
 - AbstractCore integration for `LLM_CALL` / `TOOL_CALLS` (`docs/integrations/abstractcore.md`)
 
-## Near-term priorities
-
-These are tracked in `docs/backlog/planned/`:
-
-1. **Signatures and keys** — non-forgeable provenance (beyond tamper-evidence)  
-   `docs/backlog/planned/008_signatures_and_keys.md`
-
-2. **Remote tool worker executor** — first-class worker boundary for tool execution  
-   `docs/backlog/planned/014_remote_tool_worker_executor.md`
-
-3. **Limit warnings + observability events** — surface `_limits` warnings durably/streaming  
-   `docs/backlog/planned/017_limit_warnings_and_observability.md`
-
-4. **Agent integration improvements** — reduce friction for external agent loops building on runtime  
-   `docs/backlog/planned/015_agent_integration_improvements.md`
-
 ## Longer-term (not scheduled)
 
 - distributed scheduling primitives (beyond in-process polling)

{abstractruntime-0.4.34 → abstractruntime-0.5.0}/docs/README.md

@@ -24,14 +24,13 @@ In this repo, the AbstractCore wiring lives under `src/abstractruntime/integrati
 ## Guides
 
 - `faq.md` — common questions (recommended)
-- `troubleshooting.md` — symptom-oriented setup, runtime, and integration fixes
 - `manual_testing.md` — manual smoke tests and how to run the test suite
 - `artifacts.md` — Runtime artifact identity, descriptors, provenance, catalog search, and access stats
-- `integrations/abstractcore.md` — wiring `LLM_CALL` / `TOOL_CALLS`, cached sessions with per-session prompt-cache listing/clearing, host memory snapshots, model-residency listings and locks, durable bloc prompt-cache control, media inputs, generated media outputs, video progress events, and tool approval waits via AbstractCore
-- run history bundle replay now also exports `resolved_actions` summaries for cross-client capability replay; see `api.md` and `integrations/abstractcore.md`
+- `integrations/abstractcore.md` — wiring `LLM_CALL` / `TOOL_CALLS`, the `config_facade` models/engines/host-jobs passthroughs for hosts, cached sessions with per-session prompt-cache listing/clearing, host memory snapshots, model-residency listings, locks and model switching, live token streaming, workspace-scoped tools, durable bloc prompt-cache control, media inputs, generated media outputs, video progress events, and tool approval waits via AbstractCore
 - `tools-comms.md` — enabling the optional comms toolset (email/WhatsApp/Telegram)
 - `tool-approval.md` — tool risk tiers, the run-policy rank ceiling, and per-call refiners (the `send_email` self-recipient rule)
 - `api.md#workflowbundles-flow-and-visualflow-distribution` — VisualFlow compiler APIs, media nodes, and document nodes (`read_pdf` / `write_pdf` / `write_docx`)
+- `api.md#run-history-bundle-export-portable-replay-artifact` — run history bundles, including `resolved_actions` summaries for cross-client capability replay
 
 ## Features (reference)
 
@@ -50,6 +49,6 @@ In this repo, the AbstractCore wiring lives under `src/abstractruntime/integrati
 - `../CONTRIBUTING.md` — how to build/test and submit changes
 - `../SECURITY.md` — responsible vulnerability reporting
 - `../ACKNOWLEDGMENTS.md` — credits
-- `../ROADMAP.md` — prioritized next steps
+- `../ROADMAP.md` — current status and longer-term direction
 - `adr/README.md` — architectural decisions (why)
 - `backlog/README.md` — implemented and planned work items (what/how)

{abstractruntime-0.4.34 → abstractruntime-0.5.0}/docs/api.md

@@ -75,6 +75,8 @@ Implementation: `src/abstractruntime/core/runtime.py`.
   - persists `CANCELLED`, then signals every effect of that run (and its in-flight descendants) executing in this process; the running attempt is recorded as `cancelled` (`StepStatus.CANCELLED`, never retried) with `cancelled_by` and `reason`, and no further effect starts
 - `Runtime.set_default_provider_model(provider=..., model=...)`
   - re-points the default provider/model seeded into new runs; pair it with the pooled client's `set_default_provider_model(...)` so both agree
+- `Runtime.set_live_delta_sink(sink)` where `sink(event: dict) -> None`, or `None` to remove it
+  - receives live token deltas (`llm.delta`, `llm.delta_end`) for LLM calls of runs started with `_runtime.stream: true` (a boolean; `start` refuses any other value); nothing is written to the ledger. See [Live token streaming](integrations/abstractcore.md#live-token-streaming)
 
 Effect cancellation helpers (`src/abstractruntime/core/effect_cancellation.py`):
 - `inflight_effects(run_ids=None)` lists executing effects (run, step, provider, model, elapsed time)
@@ -216,7 +218,7 @@ from Core route resolution and persisted from `LLM_CALL` results.
 
 ### AbstractCore (LLM + tools)
 
-Requires: `pip install abstractruntime` (AbstractCore 2.15.1 or newer is part of the base install).
+Requires: `pip install abstractruntime` (AbstractCore 2.16.0 or newer is part of the base install).
 
 Implementation: `src/abstractruntime/integrations/abstractcore/*`.
 
@@ -231,6 +233,7 @@ Entry points:
 - tool executors: `MappingToolExecutor`, `AbstractCoreToolExecutor`, `PassthroughToolExecutor`, `ApprovalToolExecutor`, `ToolApprovalPolicy` (`src/abstractruntime/integrations/abstractcore/tool_executor.py`)
 - discovery-facade delegation is implemented by the configured AbstractCore LLM clients in `src/abstractruntime/integrations/abstractcore/llm_client.py` (`list_providers`, `list_provider_models`, `get_voice_catalog`, `list_tts_models`, `list_stt_models`, `list_music_providers`, `list_music_models`, `list_vision_provider_models`, `list_cached_vision_models`, `list_vision_adapters`)
 - host-facade client delegation is implemented by the configured AbstractCore LLM clients in `src/abstractruntime/integrations/abstractcore/llm_client.py` (`get_prompt_cache_capabilities`, `get_prompt_cache_stats`, `prompt_cache_set`, `prompt_cache_update`, `prompt_cache_fork`, `prompt_cache_clear`, `prompt_cache_prepare_modules`, `upsert_text_bloc`, `get_bloc_record`, `list_blocs`, `get_bloc_kv_manifest`, `ensure_bloc_kv_artifact`, `load_bloc_kv_artifact`, `list_bloc_kv_artifacts`, `delete_bloc_kv_artifact`, `prune_bloc_kv_artifacts`, `delete_bloc`, `get_model_residency_capabilities`, `list_model_residency`, `load_model_residency`, `unload_model_residency`, `get_memory_snapshot`, `list_session_prompt_caches`, `clear_session_prompt_caches`, `lock_model_residency`, `unlock_model_residency`, `get_context_estimate`); the last six are optional in the client contract, and the facade returns `{"ok": false, "supported": false, ...}` when the configured client does not implement one
+- switching the default model (`set_default_provider_model` on the pooled client) unloads the previous in-process model unless an owner in the process still uses it; `list_model_residency` diagnostics report `pending_ejects` and `last_switch_ejects`, and `unload_model_residency(runtime_id=...)` accepts any listed `local:<task>:<provider>:<model>` id, including `local:embedding:<provider>:<model>` rows (see `integrations/abstractcore.md#unloading-and-switching-models`)
 - `lock_model_residency`, `unlock_model_residency`, and `get_context_estimate` accept an optional payload mapping and/or keyword arguments (keyword arguments win on conflicts); a lock requires provider-verified residency — locking a non-resident pair refuses with a structured `model_not_resident` payload (load with `lock: true` instead; remotely the Core server's HTTP 409 refusal is converted to the same payload), while unlock never requires residency so a locked-but-evicted pair is always releasable; a locked model refuses `unload_model_residency` with a structured `model_locked` payload — locally as a client-side per-`(provider, model)` lock, remotely by converting the Core server's HTTP 409 refusal — and unloads only with `force=true`, releasing the lock only after the unload succeeds
 - the `MODEL_RESIDENCY` effect supports `list_loaded`, `load`, `unload`, `lock`, and `unlock` operations with the same soft-fail semantics; on `unload`, `force` is forwarded only when authored in the effect payload
 - local `list_model_residency` merges AbstractCore's host-wide loaded-model sweep into text-generation listings (sweep-only rows carry `source: "provider_server"` and no `task` label), and residency rows normalize provider size extras to `size_bytes` / `size_vram_bytes` while keeping the originals; local text rows also carry registry-declared `modalities` (omitted on a registry miss), host identity (`host_id` / `host_name`), and runtime-owned lock truth (`locked` / `lockable`, with `pinned` a truthful alias of `locked` — never the default-identity flag, which `default` alone carries), while remote listings keep the Core server's row identity
@@ -275,6 +278,9 @@ Prompt cache / cached sessions:
 - local Runtime owns the bloc root policy: `~/.abstractruntime/blocs` by default, `<base_dir>/blocs` for `create_local_file_runtime(...)`, and explicit `bloc_root_dir=...` overrides when needed
 - provider cache/session handles are not durable runtime state and should not be stored in `RunState.vars`
 
+Workspace scope:
+- run vars `workspace_root`, `workspace_access_mode`, `workspace_allowed_paths`, `workspace_ignored_paths`, and the host-only `workspace_builtin_deny_prefixes` / `workspace_builtin_allow` scope file and shell tools; child runs inherit them (see `integrations/abstractcore.md#workspace-scoped-tools`)
+
 Attachment registration limits:
 - `TOOL_CALLS.payload.max_attachment_bytes`, `run.vars["_runtime"]["max_attachment_bytes"]`, or `ABSTRACTRUNTIME_MAX_ATTACHMENT_BYTES` bound the bytes Runtime stores when local `read_file` outputs are captured as session attachments