AbstractRuntime 0.13.0__tar.gz → 0.13.1__tar.gz

{abstractruntime-0.13.0 → abstractruntime-0.13.1}/CHANGELOG.md

@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.13.1] - 2026-10-27
+
+### Added
+
+- `email_facade.resolve_srv_default` (AbstractCore's mailbox SRV lookup) is re-exported, so a host's mail code imports
+  it from the runtime facade like every other mail name.
+
 ## [0.13.0] - 2026-10-27
 
 Requires AbstractCore 2.30.0 or newer. Personal voice stores need AbstractVoice 0.19.0.

{abstractruntime-0.13.0 → abstractruntime-0.13.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: AbstractRuntime
-Version: 0.13.0
+Version: 0.13.1
 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

abstractruntime-0.13.1/docs/adr/0008_integration_facades_are_the_complete_host_surface.md

@@ -0,0 +1,74 @@
+# ADR 0008: Runtime integration facades are the complete host surface for AbstractCore
+
+Status: Accepted.
+Date: 2026-10-27
+
+## Context
+
+Hosts (AbstractGateway first) depend on AbstractRuntime, and AbstractRuntime owns the
+AbstractCore integration (ADR 0001, 0004-0007). The gateway enforces its side with a test that
+fails on any direct `abstractcore` import. That rule only holds if every AbstractCore name a host
+legitimately needs is reachable through a runtime facade. On 2026-10-27 the gateway's mailbox
+code needed AbstractCore's SRV lookup (`resolve_srv_default`), the email facade did not re-export
+it, and the host imported AbstractCore directly: the boundary test went red and stayed red
+across a release line. The hole was not the import; it was a facade that lagged behind what the
+host needed, with no rule saying whose job it was to close the gap.
+
+## Decision
+
+1. The modules under `abstractruntime.integrations.abstractcore` whose name ends in `_facade`
+   (discovery, host, config, run, email, structured, voice, telegram, comms, mcp, tool inventory,
+   server, data registry) are the ONLY surface through which a host reaches AbstractCore. They
+   are complete by contract: a name a host needs and cannot import from a facade is a runtime
+   defect, fixed by adding the re-export or method in the runtime and cutting a patch release.
+2. A host never works around a missing name by importing `abstractcore` directly, vendoring the
+   code, or guessing a replacement. It raises the gap to the runtime (backlog item or PR) and
+   pins the runtime floor that carries the fix.
+3. A re-export is unchanged in identity (`facade.name is abstractcore.module.name`) and listed in
+   the facade's `__all__`; the facade documents which AbstractCore version introduced the name.
+4. The facades are additive within a minor line: a name, once exported, is not removed without
+   a deprecation note and a major or minor bump.
+
+## Consequences
+
+### Positive
+- The host's boundary test is a true gate: green means every AbstractCore access is a runtime
+  facade, so a Core change breaks at most one package.
+- Version floors stay layered: a host pins the runtime, the runtime pins Core.
+
+### Negative
+- A host feature that needs one new Core name waits for a runtime patch release (about 20
+  minutes with the release workflow), and the host's runtime floor moves with it.
+- The runtime carries thin re-exports it does not use itself.
+
+### Neutral
+- Patch releases of the runtime for facade additions are normal, not exceptional.
+
+## Enforcement
+- Code review: a runtime PR that adds a host-facing Core name adds it to the facade's `__all__`
+  (and to a names list such as `email_facade.GATEWAY_NAMES` where one exists) with a one-line
+  comment naming the Core version and the host need.
+- Hosts cite this ADR in their own boundary rule (AbstractGateway ADR 0001) and never add an
+  exemption to their import-boundary test for a name a facade could carry.
+- A facade gap found during host work becomes a runtime backlog item or PR before the host
+  ships; the host's changelog names the runtime version that closes it.
+
+## Validation
+- `tests/test_email_review_fixes.py`: the email facade's export set equals Core's plus the
+  runtime's additions, every `GATEWAY_NAMES` entry imports, and re-exports keep identity.
+- AbstractGateway `tests/test_gateway_import_boundary.py` stays green against the released
+  runtime floor the gateway pins.
+- Release check: the runtime's docs list each facade's host-facing names
+  (`docs/integrations/abstractcore.md`, `docs/api.md`).
+
+## Backlog links
+- Originating: AbstractGateway backlog 1044 (mailbox Read and write access) needed
+  `resolve_srv_default`; closed by runtime 0.13.1 (`email_facade.resolve_srv_default`).
+- Adoption: AbstractGateway `tests/test_gateway_import_boundary.py` (backlog 0059).
+
+## Related
+- ADR 0001 (layered coupling), 0004 (media execution), 0005 (discovery queries), 0006 (bloc
+  prompt cache): the per-area facades this ADR generalises.
+- `src/abstractruntime/integrations/abstractcore/email_facade.py`, `voice_facade.py`,
+  `discovery_facade.py`.
+- AbstractGateway ADR 0001: AbstractCore access goes through AbstractRuntime facades.

{abstractruntime-0.13.0 → abstractruntime-0.13.1}/docs/adr/README.md

@@ -20,6 +20,7 @@ When you ask "why is it designed this way?", the answer is in an ADR. ADRs are:
 | 0005 | [Runtime Owns AbstractCore Host Discovery Queries](0005_runtime_owns_abstractcore_host_discovery_queries.md) | Accepted | 2026-05-20 | Hosts should ask Runtime for Core discovery/catalog snapshots |
 | 0006 | [Runtime Owns Durable AbstractCore Bloc Prompt-Cache Control](0006_runtime_owns_durable_abstractcore_bloc_prompt_cache.md) | Accepted | 2026-05-20 | Hosts should use Runtime for durable bloc/KV controls and binding-aware execution |
 | 0007 | [Runtime Relays Core-Owned Model Residency Truth](0007_runtime_relays_core_owned_model_residency_truth.md) | Accepted | 2026-05-21 | Runtime reports loaded state only from AbstractCore residency truth |
+| 0008 | [Integration Facades Are the Complete Host Surface](0008_integration_facades_are_the_complete_host_surface.md) | Accepted | 2026-10-27 | Every AbstractCore name a host needs is a runtime facade re-export; a gap is a runtime patch, never a host import |
 
 ## Relationship to Backlog
 
@@ -34,6 +35,7 @@ ADRs explain *why*. Backlog items explain *what* and *how*.
 | 0005 | `backlog/completed/026_runtime_host_discovery_facade_for_core_catalogs.md` |
 | 0006 | `backlog/completed/027_runtime_durable_bloc_prompt_cache_facade.md` |
 | 0007 | `backlog/completed/0035_model_residency_provider_truth_for_local_http_clients.md`, `backlog/proposed/0036_local_media_residency_bridge_to_core_residency.md` |
+| 0008 | AbstractGateway backlog 1044 (mailbox access) and `tests/test_gateway_import_boundary.py`; runtime 0.13.1 `email_facade.resolve_srv_default` |
 
 ## Adding New ADRs
 

{abstractruntime-0.13.0 → abstractruntime-0.13.1}/llms-full.txt

@@ -6287,6 +6287,7 @@ When you ask "why is it designed this way?", the answer is in an ADR. ADRs are:
 | 0005 | [Runtime Owns AbstractCore Host Discovery Queries](0005_runtime_owns_abstractcore_host_discovery_queries.md) | Accepted | 2026-05-20 | Hosts should ask Runtime for Core discovery/catalog snapshots |
 | 0006 | [Runtime Owns Durable AbstractCore Bloc Prompt-Cache Control](0006_runtime_owns_durable_abstractcore_bloc_prompt_cache.md) | Accepted | 2026-05-20 | Hosts should use Runtime for durable bloc/KV controls and binding-aware execution |
 | 0007 | [Runtime Relays Core-Owned Model Residency Truth](0007_runtime_relays_core_owned_model_residency_truth.md) | Accepted | 2026-05-21 | Runtime reports loaded state only from AbstractCore residency truth |
+| 0008 | [Integration Facades Are the Complete Host Surface](0008_integration_facades_are_the_complete_host_surface.md) | Accepted | 2026-10-27 | Every AbstractCore name a host needs is a runtime facade re-export; a gap is a runtime patch, never a host import |
 
 ## Relationship to Backlog
 
@@ -6301,6 +6302,7 @@ ADRs explain *why*. Backlog items explain *what* and *how*.
 | 0005 | `backlog/completed/026_runtime_host_discovery_facade_for_core_catalogs.md` |
 | 0006 | `backlog/completed/027_runtime_durable_bloc_prompt_cache_facade.md` |
 | 0007 | `backlog/completed/0035_model_residency_provider_truth_for_local_http_clients.md`, `backlog/proposed/0036_local_media_residency_bridge_to_core_residency.md` |
+| 0008 | AbstractGateway backlog 1044 (mailbox access) and `tests/test_gateway_import_boundary.py`; runtime 0.13.1 `email_facade.resolve_srv_default` |
 
 ## Adding New ADRs
 

{abstractruntime-0.13.0 → abstractruntime-0.13.1}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "AbstractRuntime"
-version = "0.13.0"
+version = "0.13.1"
 description = "AbstractRuntime: a durable graph runner designed to pair with AbstractCore."
 readme = "README.md"
 requires-python = ">=3.10"

abstractruntime-0.13.1/release-notes.md

@@ -0,0 +1,4 @@
+### Added
+
+- `email_facade.resolve_srv_default` (AbstractCore's mailbox SRV lookup) is re-exported, so a host's mail code imports
+  it from the runtime facade like every other mail name.

{abstractruntime-0.13.0 → abstractruntime-0.13.1}/src/abstractruntime/integrations/abstractcore/email_facade.py

@@ -23,6 +23,9 @@ from __future__ import annotations
 import abstractcore.comms.email as _core_email
 from abstractcore.comms.email import *  # noqa: F401,F403 - re-exported unchanged
 from abstractcore.comms.email import legacy  # noqa: F401 - re-exported module
+# Mailbox server discovery (AbstractCore 2.28.0+): the SRV lookup a host's "Read and write"
+# mailbox access uses to find a provider's outgoing server (AbstractGateway mail/accounts.py).
+from abstractcore.comms.email.discovery import resolve_srv_default  # noqa: F401 - re-exported unchanged
 
 # The names AbstractGateway imports (framework backlog 0992, WP3 request).
 GATEWAY_NAMES = (
@@ -30,7 +33,7 @@ GATEWAY_NAMES = (
     "EmailInvalidSettings", "EmailNotConfigured", "EmailOAuthFailed", "EmailOAuthPending", "EmailRateLimited",
     "EmailSecret", "ImapSettings", "LoopbackAuthorization", "MailCursor", "OAuthSettings", "OAuthTokenClient",
     "OutgoingMessage", "SearchCriteria", "SecretVault", "SmtpSettings", "builtin_client", "evaluate", "guarded_send",
-    "legacy", "parse_recipients", "provider_preset", "resolve_oauth_client", "tls_context",
+    "legacy", "parse_recipients", "provider_preset", "resolve_oauth_client", "resolve_srv_default", "tls_context",
 )
 
-__all__ = [*_core_email.__all__, "legacy", "GATEWAY_NAMES"]
+__all__ = [*_core_email.__all__, "legacy", "resolve_srv_default", "GATEWAY_NAMES"]

{abstractruntime-0.13.0 → abstractruntime-0.13.1}/tests/test_email_review_fixes.py

@@ -531,7 +531,10 @@ def test_email_facade_mirrors_core_mail_package():
     import abstractcore.comms.email as core_email
     from abstractruntime.integrations.abstractcore import email_facade
 
-    assert set(email_facade.__all__) == set(core_email.__all__) | {"legacy", "GATEWAY_NAMES"}
+    assert set(email_facade.__all__) == set(core_email.__all__) | {"legacy", "resolve_srv_default", "GATEWAY_NAMES"}
+    from abstractcore.comms.email.discovery import resolve_srv_default as core_resolve
+
+    assert email_facade.resolve_srv_default is core_resolve
     for name in core_email.__all__:
         assert getattr(email_facade, name) is getattr(core_email, name), name
     from abstractcore.comms.email import legacy

abstractruntime-0.13.0/release-notes.md

@@ -1,25 +0,0 @@
-Requires AbstractCore 2.30.0 or newer. Personal voice stores need AbstractVoice 0.19.0.
-
-### Added
-
-- The voice library runs on the capability registry the runtime's synthesis uses (same voice manager, settings and
-  stores); a model pool manages voices on its media host. `clone_voice(..., language=)` forwards the recording's language;
-  `clone_voice` answers the stored record, flat, with its `voice_id`, locally and remotely; a remote refusal keeps the
-  server's status (400, 401, 403, 404, 409, 413, 422, 429, 501, 503); an empty voice id is refused (422).
-- **Per-runtime voice stores**: `voice_store_dir` and `voice_library_dirs` in a runtime's AbstractCore client settings give
-  it a personal voice store in front of read-only libraries; its synthesis, voice catalog and voice library use the same
-  stores. `deploy_voice_to_library(voice_id)` on the voice library facade (local runtimes). See
-  [Voice library](docs/integrations/abstractcore.md#voice-library).
-
-- **Voice library facade**: `get_abstractcore_voice_facade(runtime)` (`AbstractCoreVoiceFacade`, `VoiceLibraryError`) lists the languages each voice engine accepts, lists cloned voices (designed and built-in ones included, optionally by language), reads, renames, replaces the reference transcript of and deletes a cloned voice, creates a voice from a recording (`clone_voice`) or from a written description (`design_voice`), and returns the capability catalog (which engine and model supports `speed`, `one_shot`, design... and how). Local runtimes run it in process; remote runtimes call the AbstractCore server's `/v1` voice routes. Refusals carry an HTTP-like `status_code`. See [Voice library](docs/integrations/abstractcore.md#voice-library).
-- **Voice catalog by language**: `get_voice_catalog(..., language=)` keeps the voices that can speak a language, native speakers first (local and remote).
-- **`one_shot` on remote TTS**: a remote runtime forwards `one_shot` on buffered speech, as local runtimes already did.
-
-### Changed
-
-- A voice request the voice plugin refuses (a plain `ValueError` or `KeyError` on a `modality: voice` output, such as
-  `one_shot` over an engine's length limit or an unknown voice id) and a missing capability
-  (`CapabilityUnavailableError`) fail the `LLM_CALL` effect at once instead of being retried: one engine call, the same
-  message. Other media lanes keep their retries.
-- A remote AbstractCore server's 4xx refusal (other than 408, 409, 425, 429) is no longer retried: the status is read from
-  the HTTP error's response.