AbstractRuntime 0.4.33__tar.gz → 0.4.35__tar.gz

{abstractruntime-0.4.33 → abstractruntime-0.4.35}/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.33 → abstractruntime-0.4.35}/CHANGELOG.md

@@ -7,6 +7,39 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [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)` 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
 
 ### Added
@@ -855,7 +888,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.33...HEAD
+[Unreleased]: https://github.com/lpalbou/abstractruntime/compare/v0.4.35...HEAD
+[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
 [0.4.31]: https://github.com/lpalbou/abstractruntime/compare/v0.4.29...v0.4.31

{abstractruntime-0.4.33 → abstractruntime-0.4.35}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: AbstractRuntime
-Version: 0.4.33
+Version: 0.4.35
 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.14.0
+Requires-Dist: abstractcore[audio,music,remote,tools,vision,voice]>=2.15.1
 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.14.0; extra == 'apple'
+Requires-Dist: abstractcore[all-apple]>=2.15.1; 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.14.0; extra == 'gpu'
+Requires-Dist: abstractcore[all-gpu]>=2.15.1; 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.33 • **Python:** 3.10+
+**Version:** 0.4.35 • **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.14.0 or newer with remote provider,
+The base install includes AbstractCore 2.15.1 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.33)
+## What’s included (v0.4.35)
 
 Kernel (import-light):
 - workflow graphs: `WorkflowSpec` (`src/abstractruntime/core/spec.py`)
@@ -189,7 +189,7 @@ 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
@@ -232,7 +232,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 +248,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.33 → abstractruntime-0.4.35}/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.33 • **Python:** 3.10+
+**Version:** 0.4.35 • **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.14.0 or newer with remote provider,
+The base install includes AbstractCore 2.15.1 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.33)
+## What’s included (v0.4.35)
 
 Kernel (import-light):
 - workflow graphs: `WorkflowSpec` (`src/abstractruntime/core/spec.py`)
@@ -139,7 +139,7 @@ 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
@@ -182,7 +182,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 +198,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.33 → abstractruntime-0.4.35}/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.33 → abstractruntime-0.4.35}/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 and locks, 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.33 → abstractruntime-0.4.35}/docs/api.md

@@ -216,7 +216,7 @@ from Core route resolution and persisted from `LLM_CALL` results.
 
 ### AbstractCore (LLM + tools)
 
-Requires: `pip install abstractruntime` (AbstractCore 2.14.0 or newer is part of the base install).
+Requires: `pip install abstractruntime` (AbstractCore 2.15.1 or newer is part of the base install).
 
 Implementation: `src/abstractruntime/integrations/abstractcore/*`.
 

{abstractruntime-0.4.33 → abstractruntime-0.4.35}/docs/architecture.md

@@ -1,7 +1,7 @@
 # AbstractRuntime — Architecture
 
-> Updated: 2026-08-27
-> Version: 0.4.33
+> Updated: 2026-09-25
+> Version: 0.4.35
 > Scope: this describes **what is implemented in this repository**.
 
 AbstractRuntime is a **durable workflow runtime**: it executes workflow graphs as a persisted state machine with explicit waits (user, time, events, jobs, subworkflows). A run can pause for hours/days and resume **without** keeping Python stacks/coroutines alive.
@@ -41,6 +41,49 @@ The boundary is intentionally narrow:
 - Gateway and other hosts compose Runtime with the desired memory and local-inference profile. Runtime's base package includes the AbstractMemory contract, AbstractCore remote/tool capability integration, Runtime-owned permissive PDF read/write and standard-library DOCX write support, and the MCP worker entry point, but not backend extras such as LanceDB, Core media document stacks, or local inferencer stacks. Hosts choose storage, embeddings, readiness policy, and whether to add `abstractruntime[apple]` or `abstractruntime[gpu]`.
 - Remote and hybrid clients use explicit Core server URLs and auth headers supplied by the host. Runtime does not read Gateway auth environment variables for provider/model/auth decisions or treat Gateway bearer tokens as Core server/provider credentials.
 
+### Host-facing facades
+
+Hosts such as AbstractGateway talk to AbstractCore through Runtime-owned facades, so they never import AbstractCore themselves. Durable model work goes through the runtime (effects, ledger, artifacts); host operations (discovery, residency, prompt caches, configuration, models, engines and host jobs) go through the facades, which call AbstractCore in-process or its server.
+
+```mermaid
+flowchart LR
+  subgraph Host["Host (AbstractGateway, apps)"]
+    HostAPI["HTTP routes / UI"]
+  end
+
+  subgraph RT["AbstractRuntime"]
+    Runtime["Runtime
+start / tick / resume"]
+    Handlers["effect handlers
+LLM_CALL / TOOL_CALLS / MODEL_RESIDENCY"]
+    RunFacade["run_facade
+durable media + comms child runs"]
+    HostFacade["host_facade / discovery_facade
+residency, prompt caches, discovery"]
+    ConfigFacade["config_facade
+capability defaults, models, engines, host jobs"]
+    Stores["RunStore / LedgerStore / ArtifactStore"]
+  end
+
+  subgraph AC["AbstractCore"]
+    Providers["providers + tools
+(local or AbstractCore Server)"]
+    CoreConfig["config, model catalog,
+engine installer, host job registry"]
+  end
+
+  HostAPI -->|"WorkflowSpec, resume, cancel"| Runtime
+  HostAPI --> RunFacade
+  HostAPI --> HostFacade
+  HostAPI --> ConfigFacade
+  RunFacade --> Runtime
+  Runtime --> Handlers
+  Runtime --> Stores
+  Handlers -->|"generate / tools"| Providers
+  HostFacade --> Providers
+  ConfigFacade --> CoreConfig
+```
+
 This keeps the runtime usable by `../abstractgateway` and application layers such as `../abstractflow`, `../abstractassistant`, `../abstractobserver`, and `../abstractcode` without embedding provider-specific model logic in the durable kernel.
 
 ## Component map
@@ -77,7 +120,7 @@ flowchart TB
   end
 
   subgraph Integrations["integrations/ (optional wiring)"]
-    AC["abstractcore/\nLLM_CALL, TOOL_CALLS, MCP worker"]
+    AC["abstractcore/\nLLM_CALL, TOOL_CALLS, MCP worker,\nhost / run / discovery / config facades"]
     AM["abstractmemory/\nMEMORY_KG_* handlers"]
   end
 
@@ -116,7 +159,7 @@ flowchart TB
 ### Crash-ordering invariant (reliability)
 
 The run store is truth; the ledger is evidence. Every state transition obeys
-ONE ordering law (backlog 0045; every durable feature is a consumer):
+ONE ordering law ([backlog 0045](backlog/planned/runtime_systemic_reliability/0045_crash_replay_harness_and_ordering_invariant.md); every durable feature is a consumer):
 
 1. **State save is the commit point.** A transition is true when — and only
    when — `RunStore.save(run)` returns. Everything before the save must be

{abstractruntime-0.4.33 → abstractruntime-0.4.35}/docs/getting-started.md

@@ -12,7 +12,7 @@ Remote-light runtime:
 pip install abstractruntime
 ```
 
-This installs AbstractCore 2.14.0 or newer with remote provider, vision,
+This installs AbstractCore 2.15.1 or newer with remote provider, vision,
 voice, audio, music, tool, and MCP-worker support. The base install is
 remote-light: it can route multimodal workflows to hosted or OpenAI-compatible
 endpoints, but it does not select local inferencer stacks such as MLX, vLLM,

{abstractruntime-0.4.33 → abstractruntime-0.4.35}/docs/integrations/abstractcore.md

@@ -16,7 +16,7 @@ Implementation pointers (this repo):
 pip install abstractruntime
 ```
 
-The base install includes AbstractCore 2.14.0 or newer. That is the supported baseline for the current server auth split (`Authorization` for server auth, `X-AbstractCore-Provider-API-Key` for provider overrides), generated-media contracts, image upscaling, capability catalog, prompt-cache control-plane endpoints (including session attribution via `/acore/prompt_cache/key_meta`), host memory snapshots, the host-wide loaded-model sweep used by residency listings, durable bloc prompt-cache helpers, bindings and lifecycle operations, task-aware model residency for text/image/video/TTS/STT, current tool catalog, AbstractCore's public output-selector contract, async/sync text-generation output-selector parity, video generation endpoints, the public local vision-cache catalog helper used by Runtime discovery, vision adapter discovery plus batch/LoRA media controls, and the released shared workspace/file-filter utility surface used by Runtime packaging and integration checks.
+The base install includes AbstractCore 2.15.1 or newer. That is the supported baseline for the current server auth split (`Authorization` for server auth, `X-AbstractCore-Provider-API-Key` for provider overrides), generated-media contracts, image upscaling, capability catalog, prompt-cache control-plane endpoints (including session attribution via `/acore/prompt_cache/key_meta`), host memory snapshots, the host-wide loaded-model sweep used by residency listings, durable bloc prompt-cache helpers, bindings and lifecycle operations, task-aware model residency for text/image/video/TTS/STT, current tool catalog, AbstractCore's public output-selector contract, async/sync text-generation output-selector parity, video generation endpoints, the public local vision-cache catalog helper used by Runtime discovery, vision adapter discovery plus batch/LoRA media controls, and the released shared workspace/file-filter utility surface used by Runtime packaging and integration checks.
 
 The base install also includes the remote-light media/capability plugins needed
 for AbstractCore's multimodal `generate(..., output=...)` path. Local
@@ -669,8 +669,10 @@ result = facade.clear_session_prompt_caches("support-session-1")
 
 ## Models, engines and host jobs (config facade)
 
-AbstractCore 2.14.0 implements the model browser, the local-engine installer and
-a host job registry. `abstractruntime.integrations.abstractcore.config_facade`
+AbstractCore implements the model browser, the local-engine installer and a
+host job registry. These passthroughs need AbstractCore 2.15.1 (the
+base-install floor), the first release that records who cancelled a job.
+`abstractruntime.integrations.abstractcore.config_facade`
 passes them through unchanged, so a host such as AbstractGateway serves the same
 payloads as `abstractcore models|engines … --json` and the `/acore/*` routes
 without importing AbstractCore itself.
@@ -689,7 +691,7 @@ without importing AbstractCore itself.
 | `delete_model_artifact(provider, artifact, dry_run=False, force=False)` | a `host_job_v1` job of kind `delete` |
 | `start_model_download_job(provider, artifact, dry_run=False)` | a `host_job_v1` job of kind `download` (single-flight per artifact) |
 | `host_jobs_list(kind=None, status=None)` | `{"schema": "host_jobs_v1", "jobs": [...]}`, newest first, including jobs started by other processes on the host |
-| `host_job(job_id)` / `host_job_cancel(job_id)` | one job, or `None` when the id is unknown |
+| `host_job(job_id)` / `host_job_cancel(job_id, *, by="api", user=None)` | one job, or `None` when the id is unknown; a cancel records `by` (`api`, `console`) and the signed-in `user` on the job (`cancelled_by`, `cancelled_by_user`, `ended_reason`; AbstractCore 2.15.1+) |
 | `console_fragment(kind)` | AbstractCore's embeddable web screen (`models` or `engines`): `{"html", "js", "css"}` |
 | `models_engines_support()` | `{"available", "abstractcore_version", "required", "missing"}`; never raises |
 

{abstractruntime-0.4.33 → abstractruntime-0.4.35}/docs/troubleshooting.md

@@ -20,7 +20,7 @@ Fix:
 - Install or upgrade the base Runtime package. LLM/tools integration, common
   remote-light multimodal dependencies, and the MCP worker entry point are part
   of the base install.
-- The current AbstractCore integration expects `abstractcore>=2.14.0`.
+- The current AbstractCore integration expects `abstractcore>=2.15.1`.
 
 Verify: