AbstractRuntime 0.4.8__tar.gz → 0.4.9__tar.gz

{abstractruntime-0.4.8 → abstractruntime-0.4.9}/ACKNOWLEDGMENTS.md

@@ -7,14 +7,15 @@ The canonical dependency list lives in `pyproject.toml`.
 
 ## Runtime dependencies (core install)
 
-- **abstractsemantics** (`>=0.0.2`) — structured schema registry support (declared in `pyproject.toml`, used in `src/abstractruntime/integrations/abstractmemory/effect_handlers.py` and VisualFlow execution wiring).
+- **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.
 
 ## Optional integrations (extras)
 
 Installed only when you opt in to extras:
-- **abstractcore** (`>=2.11.8`) — LLM + tools integration used by `abstractruntime[abstractcore]` (declared in `pyproject.toml`, implementation under `src/abstractruntime/integrations/abstractcore/*`, docs: `docs/integrations/abstractcore.md`).
+- **abstractcore** (`>=2.13.12`) — LLM + tools integration used by `abstractruntime[abstractcore]` (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.11.8`) — toolchain extra used by `abstractruntime[mcp-worker]` (declared in `pyproject.toml`) and intended to include HTML parsing dependencies (see comments in `pyproject.toml`).
+- **abstractcore[tools]** (`>=2.13.12`) — toolchain extra used by `abstractruntime[mcp-worker]` (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`).
 
 ## Build & test tooling

{abstractruntime-0.4.8 → abstractruntime-0.4.9}/CHANGELOG.md

@@ -7,6 +7,18 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.4.9] - 2026-05-09
+
+### Changed
+- Added `AbstractMemory>=0.2.6` as a base dependency so Runtime's
+  `MEMORY_KG_*` effect contract always has the AbstractMemory TripleStore
+  models available.
+
+### Notes
+- Runtime still does not depend on `AbstractMemory[lancedb]`. Hosts such as
+  AbstractGateway choose the durable/vector memory backend, path, embeddings,
+  and readiness policy.
+
 ## [0.4.8] - 2026-05-08
 
 ### Changed

{abstractruntime-0.4.8 → abstractruntime-0.4.9}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: AbstractRuntime
-Version: 0.4.8
+Version: 0.4.9
 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,6 +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: abstractmemory>=0.2.6
 Requires-Dist: abstractsemantics>=0.0.3
 Provides-Extra: abstractcore
 Requires-Dist: abstractcore>=2.13.12; extra == 'abstractcore'
@@ -49,7 +50,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.8 • **Python:** 3.10+
+**Version:** 0.4.9 • **Python:** 3.10+
 
 **Status:** pre-1.0 (API may evolve). For production use, pin versions and follow `CHANGELOG.md`.
 
@@ -137,7 +138,7 @@ state = rt.resume(
 assert state.status.value == "completed"
 ```
 
-## What’s included (v0.4.8)
+## What’s included (v0.4.9)
 
 Kernel (dependency-light):
 - workflow graphs: `WorkflowSpec` (`src/abstractruntime/core/spec.py`)
@@ -162,6 +163,9 @@ Drivers + distribution:
 
 Optional integrations:
 - AbstractCore (LLM + tools, cached sessions/prompt cache, media inputs, generated media, tool approval waits): `docs/integrations/abstractcore.md`
+- 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`
 
 ## Built-in scheduler (zero-config)

{abstractruntime-0.4.8 → abstractruntime-0.4.9}/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.8 • **Python:** 3.10+
+**Version:** 0.4.9 • **Python:** 3.10+
 
 **Status:** pre-1.0 (API may evolve). For production use, pin versions and follow `CHANGELOG.md`.
 
@@ -92,7 +92,7 @@ state = rt.resume(
 assert state.status.value == "completed"
 ```
 
-## What’s included (v0.4.8)
+## What’s included (v0.4.9)
 
 Kernel (dependency-light):
 - workflow graphs: `WorkflowSpec` (`src/abstractruntime/core/spec.py`)
@@ -117,6 +117,9 @@ Drivers + distribution:
 
 Optional integrations:
 - AbstractCore (LLM + tools, cached sessions/prompt cache, media inputs, generated media, tool approval waits): `docs/integrations/abstractcore.md`
+- 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`
 
 ## Built-in scheduler (zero-config)

{abstractruntime-0.4.8 → abstractruntime-0.4.9}/docs/architecture.md

@@ -1,7 +1,7 @@
 # AbstractRuntime — Architecture
 
 > Updated: 2026-05-08
-> Version: 0.4.8
+> Version: 0.4.9
 > 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.
@@ -12,7 +12,7 @@ AbstractRuntime is the durable execution kernel inside the wider AbstractFramewo
 - AbstractFramework umbrella: [lpalbou/AbstractFramework](https://github.com/lpalbou/AbstractFramework)
 - AbstractCore (LLM + tools): [lpalbou/abstractcore](https://github.com/lpalbou/abstractcore)
 
-The runtime stays dependency-light and delegates LLM/tool execution to integrations (notably AbstractCore): `src/abstractruntime/integrations/abstractcore/*`.
+The runtime stays dependency-light and delegates LLM/tool execution to integrations (notably AbstractCore): `src/abstractruntime/integrations/abstractcore/*`. Runtime also depends on the light AbstractMemory contract so `MEMORY_KG_*` effects always have the TripleStore model types available; hosts still choose the concrete memory backend.
 
 ```mermaid
 flowchart LR
@@ -37,7 +37,7 @@ The boundary is intentionally narrow:
 - Remote chat media is sent to AbstractCore Server as provider-ready content arrays, but persisted provider-request metadata redacts data URLs so checkpoints and ledgers do not embed media bytes.
 - Provider sessions and prompt-cache objects are not runtime state. Runtime may carry stable cache keys, while AbstractCore clients/servers manage warm caches.
 - Local execution can use richer AbstractCore capability plugins. Remote and hybrid execution map the common media cases to AbstractCore Server endpoints and OpenAI-compatible content arrays, while hybrid keeps tool execution local.
-- Gateway and other hosts compose Runtime with the desired Core/capability/memory profile. Runtime's base package does not expose hardware profile extras such as `apple`, `gpu`, `all-apple`, or `all-gpu`; those cascade through AbstractCore when a host selects them.
+- Gateway and other hosts compose Runtime with the desired Core/capability/memory profile. Runtime's base package includes the AbstractMemory contract but not backend extras such as LanceDB; hosts choose storage, embeddings, and readiness policy. Hardware profile extras such as `apple`, `gpu`, `all-apple`, and `all-gpu` cascade through AbstractCore when a host selects them.
 - 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.
 
 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.

{abstractruntime-0.4.8 → abstractruntime-0.4.9}/docs/limits.md

@@ -62,7 +62,7 @@ Returns a structured dict for UI/status display. (`src/abstractruntime/core/runt
 
 Returns a list of `LimitWarning` objects for limits approaching/exceeded. (`src/abstractruntime/core/models.py`, `src/abstractruntime/core/runtime.py`)
 
-As of v0.4.8, warnings are computed for:
+As of v0.4.9, warnings are computed for:
 - `iterations` (`current_iteration` vs `max_iterations`)
 - `tokens` (`estimated_tokens_used` vs `max_tokens`)
 

{abstractruntime-0.4.8 → abstractruntime-0.4.9}/docs/proposal.md

@@ -79,7 +79,7 @@ AbstractRuntime stays dependency-light at the kernel level; concrete integration
 
 ## Status (implemented in this repository)
 
-As of v0.4.8:
+As of v0.4.9:
 - durable kernel: `RunState`, `WaitState`, `Runtime.start/tick/resume`
 - built-in waits + events: `WAIT_EVENT`, `WAIT_UNTIL`, `ASK_USER`, `EMIT_EVENT`
 - persistence backends: in-memory, JSON/JSONL, SQLite

{abstractruntime-0.4.8 → abstractruntime-0.4.9}/docs/provenance.md

@@ -8,7 +8,7 @@ Implementation pointers:
 - model fields: `src/abstractruntime/core/models.py` (`StepRecord.prev_hash`, `StepRecord.record_hash`, `StepRecord.signature`)
 - hash-chain decorator + verifier: `src/abstractruntime/storage/ledger_chain.py`
 
-## What is implemented (v0.4.8)
+## What is implemented (v0.4.9)
 
 - `HashChainedLedgerStore(inner_store)` — wraps any `LedgerStore` to compute hashes on append
 - `verify_ledger_chain(records)` — validates the chain and returns a verification report

{abstractruntime-0.4.8 → abstractruntime-0.4.9}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "AbstractRuntime"
-version = "0.4.8"
+version = "0.4.9"
 description = "AbstractRuntime: a durable graph runner designed to pair with AbstractCore."
 readme = "README.md"
 requires-python = ">=3.10"
@@ -37,6 +37,10 @@ dependencies = [
   # Required to resolve stable structured-output schema refs like:
   # {"$ref":"abstractsemantics:kg_assertion_schema_v0"}
   "abstractsemantics>=0.0.3",
+  # Required for the Runtime-owned MEMORY_KG_* effect contract and TripleStore
+  # model types. Durable/vector backend dependencies such as LanceDB remain
+  # package extras owned by AbstractMemory and selected by hosts such as Gateway.
+  "AbstractMemory>=0.2.6",
 ]
 
 [project.optional-dependencies]

abstractruntime-0.4.9/release-notes.md

@@ -0,0 +1,9 @@
+### Changed
+- Added `AbstractMemory>=0.2.6` as a base dependency so Runtime's
+  `MEMORY_KG_*` effect contract always has the AbstractMemory TripleStore
+  models available.
+
+### Notes
+- Runtime still does not depend on `AbstractMemory[lancedb]`. Hosts such as
+  AbstractGateway choose the durable/vector memory backend, path, embeddings,
+  and readiness policy.

{abstractruntime-0.4.8 → abstractruntime-0.4.9}/tests/test_packaging_extras.py

@@ -43,6 +43,9 @@ def test_runtime_exposes_abstractcore_and_worker_extras_with_gateway_aligned_flo
     pyproject = Path(__file__).resolve().parents[1] / "pyproject.toml"
     text = pyproject.read_text(encoding="utf-8")
 
+    assert '"abstractsemantics>=0.0.3"' in text
+    assert '"AbstractMemory>=0.2.6"' in text
+    assert '"AbstractMemory[lancedb]' not in text
     assert "[project.optional-dependencies]" in text
     assert "abstractcore = [" in text
     assert "mcp-worker = [" in text

abstractruntime-0.4.8/release-notes.md

@@ -1,11 +0,0 @@
-### Changed
-- Minimum `abstractcore` optional dependency increased to `>=2.13.12`, and the
-  semantics floor increased to `abstractsemantics>=0.0.3`.
-- Added explicit hardware-profile cascade extras:
-  `abstractruntime[apple]`, `abstractruntime[gpu]`,
-  `abstractruntime[all-apple]`, and `abstractruntime[all-gpu]`.
-
-### Notes
-- Runtime still owns durable execution, not local model engines. These extras
-  delegate to the matching AbstractCore profile so Gateway and root aggregate
-  installs can compose a single profile vocabulary.