ommlds 0.0.0.dev501__py3-none-any.whl → 0.0.0.dev502__py3-none-any.whl

ommlds/.omlish-manifests.json

@@ -44,9 +44,9 @@
         "model_names": {
           "default": "claude",
           "aliases": {
-            "claude-opus-4-1-20250805": null,
-            "claude-opus-4-1": "claude-opus-4-1-20250805",
-            "claude-opus": "claude-opus-4-1",
+            "claude-opus-4-5-20251101": null,
+            "claude-opus-4-5": "claude-opus-4-5-20251101",
+            "claude-opus": "claude-opus-4-5",
             "claude-sonnet-4-5-20250929": null,
             "claude-sonnet-4-5": "claude-sonnet-4-5-20250929",
             "claude-sonnet": "claude-sonnet-4-5",
@@ -210,7 +210,7 @@
     "module": ".minichain.backends.impls.google.names",
     "attr": "_BACKEND_STRINGS_MANIFEST",
     "file": "ommlds/minichain/backends/impls/google/names.py",
-    "line": 32,
+    "line": 38,
     "value": {
       "!.minichain.backends.strings.manifests.BackendStringsManifest": {
         "service_cls_names": [
@@ -221,6 +221,10 @@
         "model_names": {
           "default": "gemini",
           "aliases": {
+            "gemini-3-pro-preview": null,
+            "gemini-3-pro": "gemini-3-pro-preview",
+            "gemini-3-flash-preview": null,
+            "gemini-3-flash": "gemini-3-flash-preview",
             "gemini-2.5-pro": null,
             "gemini-2.5-flash": null,
             "gemini-2.5-flash-lite": null,

ommlds/minichain/backends/impls/anthropic/names.py

@@ -14,9 +14,9 @@ from ...strings.manifests import BackendStringsManifest
 MODEL_NAMES = ModelNameCollection(
     default='claude',
     aliases={
-        'claude-opus-4-1-20250805': None,
-        'claude-opus-4-1': 'claude-opus-4-1-20250805',
-        'claude-opus': 'claude-opus-4-1',
+        'claude-opus-4-5-20251101': None,
+        'claude-opus-4-5': 'claude-opus-4-5-20251101',
+        'claude-opus': 'claude-opus-4-5',
 
         'claude-sonnet-4-5-20250929': None,
         'claude-sonnet-4-5': 'claude-sonnet-4-5-20250929',

ommlds/minichain/backends/impls/google/names.py

@@ -16,6 +16,12 @@ from ...strings.manifests import BackendStringsManifest
 MODEL_NAMES = ModelNameCollection(
     default='gemini',
     aliases={
+        'gemini-3-pro-preview': None,
+        'gemini-3-pro': 'gemini-3-pro-preview',
+
+        'gemini-3-flash-preview': None,
+        'gemini-3-flash': 'gemini-3-flash-preview',
+
         'gemini-2.5-pro': None,
         'gemini-2.5-flash': None,
         'gemini-2.5-flash-lite': None,

ommlds/minichain/services/README.md

@@ -0,0 +1,154 @@
+The core service abstraction. In general, Services are intended to encapsulate non-trivial, resourceful, effectful
+operations, which are likely to have various implementations, each having their own specific capabilities in addition
+to their common interface, and where wrapping, adapting, and transforming them in a uniform manner is desirable.
+
+For example:
+ - A ChatService is passed a Request with a Chat value and returns a Response with an AiChat value.
+ - A ChatChoicesService is passed a Request with a Chat and returns a Response with a list of AiChoices.
+ - A ChatChoicesServiceChatService is a simple adapter taking a ChatChoicesService which it will invoke with its given
+   Request, expect a single AiChoice value in that Response, and return that single AiChat as its Response - thus acting
+   as a ChatService.
+   - Thus, all chat backends that return choices can be adapted to code expecting a single chat as output.
+ - A ChatStreamService is passed a Request with a Chat value and returns a Response with a value from which AiDeltas
+   may be streamed.
+ - A ChatChoicesStreamService is passed a Request with a Chat value and returns a Response with a value from which
+   AiChoicesDeltas may be streamed.
+ - A ChatChoicesStreamServiceChatChoicesService is an adapter taking a ChatChoicesStreamService and aggregating the
+   AiChoicesDeltas into joined, non-delta AiChoices.
+   - This may then be wrapped in a ChatChoicesServiceChatService to act as a ChatService.
+   - In practice however there are usually dedicated streaming and non-streaming implementations if possible as
+     non-streaming will usually have less overhead.
+ - An OpenaiChatChoicesService can act as a ChatChoicesService, and will accept all generic ChatOptions, in addition to
+   any OpenaiChatOptions inapplicable to any other backend. It may also produce all generic ChatOutputs, in addition to
+   OpenaiChatOutputs that will not be produced by other backends.
+ - Beyond chat, a VectorSearchService is passed a Request with a VectorSearch value and returns a Response with a
+   VectorHits value.
+ - A RetryService wraps any other Service and will attempt to re-invoke it on failure.
+ - A FirstInWinsService wraps any number of other Services and will return the first non-error Response it receives.
+
+The service abstraction consists of 3 interrelated generic types:
+ - Request, an immutable final generic class containing a single value and any number of options.
+ - Response, an immutable final generic class containing a single value and any number of outputs.
+ - Service, a generic protocol consisting of a single async method `invoke`, taking a request and returning a response.
+
+There are 2 related abstract base classes in the parent package:
+ - Option, a non-generic abstract class representing a service option.
+ - Output, a non-generic abstract class representing a service output.
+
+The purpose of this arrangement is to provide the following:
+ - There is only one method - `Service.invoke` - to deal with.
+ - There is no base `Service` class - service types are distinguished only by the requests they accept and responses
+   they return.
+ - It facilitates a clear, introspectable, generally type-safe means for handling 'less-specific' and 'more-specific'
+   service types.
+ - It facilitates generic wrapper and transformation machinery.
+
+The variance of the type parameters of the 3 classes is central:
+ - `Request[V_co, OptionT_co]`
+ - `Response[V_co, OutputT_contra]`
+ - `Service[RequestT_contra, ResponseT_co]`
+
+And to understand this, it's important to understand how Option and Output subtypes are intended to be arranged:
+ - These types are *not* intended to form a deep type hierarchy:
+   - A RemoteChatOption is *not* intended to inherit from a ChatOption: a ChatOption (be it a base class or union alias)
+     represents an option that *any* ChatService can accept, whereas a RemoteChatOption represents an option that *only*
+     applies to a RemoteChatService.
+   - If RemoteChatOption inherited from a base ChatOption, then it would have to apply to *all* ChatService
+     implementations.
+   - For example: were ApiKey to inherit from ChatOption, then it would have to apply to all ChatServices, including
+     LocalChatService, which has no concept of an api key.
+ - Similarly, a RemoteChatOutput is *not* intended to inherit from a ChatOutput: a ChatOutput represents an output that
+   *any* ChatService can produce, whereas a RemoteChatOutput represents an output that *only* applies to a
+   RemoteChatService.
+ - These 2 types are intended to form flat, disjoint, unrelated families of subtypes, and Request and Response are
+   intended to be parameterized by the unions of all such families they may contain.
+ - Because of this, one's visual intuition regarding types and subtypes may be reversed: `int` is effectively a subtype
+   of `int | str` despite `int` being a visually shorter, less complex type.
+   - `int` is a *MORE SPECIFIC* / *STRICT SUBSET* subtype of `int | str`, the *LESS SPECIFIC* / *STRICT SUPERSET*
+     supertype.
+
+Regarding type variance:
+ - Service has the classic setup of contravariant input and covariant output:
+   - A RemoteChatService *is a* ChatService.
+   - A RemoteChatService may accept less specific requests than a ChatService.
+   - A RemoteChatService may return more specific responses than a ChatService.
+ - Request is covariant on its options:
+   - Recall, a RemoteChatOption *is not a* ChatOption.
+   - A ChatRequest *is a* RemoteChatRequest as it will not contain options RemoteChatService cannot accept.
+ - Response is contravariant on its outputs:
+   - Recall, a RemoteChatOutput *is not a* ChatOutput.
+   - A RemoteChatResponse *is a* ChatResponse even though it may contain additional output variants not produced by
+     every ChatService.
+   - Code that calls a ChatService and is given a ChatResponse must be prepared to handle (usually by simply ignoring)
+     outputs not necessarily produced by a base ChatService.
+
+Finally, in addition to a value and either options or outputs, a Request and Response each also contain a collection of
+metadata. Very much unlike the Options and Outputs, the elements of these collections are simply of the types
+`RequestMetadata | CommonMetadata` and `ResponseMetadata | CommonMetadata`, and are not otherwise parameterized. These
+are intended for looser inputs and outputs: a generic unique id, timestamps, metrics, etc., and in general should
+neither affect the behavior of services nor be depended upon by callers.
+
+Below is a representative illustration of these types and their relationships. Note how:
+ - There is no subclassing of Request, Response, or Service - just type aliasing.
+ - There is no deep, shared subclassing of Option or Output.
+ - The type args passed to Request and Response are unions of all the Option and Output subtypes they may contain.
+   - These unions are kept in pluralized type aliases for convenience.
+ - There is no base ChatOption or ChatOutput class - were there, it would not be included in the base classes of any
+   local or remote only option or output.
+ - The local and remote sections take different but equivalent approaches:
+   - There are no base LocalChatOption or LocalChatOutput classes, but there *are* base RemoteChatOption and
+     RemoteChatOutput classes.
+   - Without any common base classes (besides the lowest level Output and Option classes), the local section treats them
+     as each distinct and bespoke, and the pluralized LocalChatOptions and LocalChatOutputs type aliases aggregate them
+     by explicitly listing them.
+   - With the common RemoteChatOption and RemoteChatOutput base classes, the remote section treats them as a related
+     family that any 'RemoteChat'-like service should accept and produce.
+
+```python
+# Common chat
+
+class MaxTokens(Option, tv.UniqueScalarTypedValue[int]): pass
+class Temperature(Option, tv.UniqueScalarTypedValue[float]): pass
+
+ChatOptions: ta.TypeAlias = MaxTokens | Temperature
+ChatRequest: ta.TypeAlias = Request[Chat, ChatOptions]
+
+class TokenUsage(Output, tv.UniqueScalarTypedValue[int]): pass
+class ElapsedTime(Output, tv.UniqueScalarTypedValue[float]): pass
+
+ChatOutputs: ta.TypeAlias = TokenUsage | ElapsedTime
+ChatResponse: ta.TypeAlias = Response[Message, ChatOutputs]
+
+ChatService: ta.TypeAlias = Service[ChatRequest, ChatResponse]
+
+# Local chat
+
+class ModelPath(Option, tv.ScalarTypedValue[str]): pass
+
+LocalChatOptions: ta.TypeAlias = ChatOptions | ModelPath
+LocalChatRequest: ta.TypeAlias = Request[Chat, LocalChatOptions]
+
+class LogPath(Output, tv.ScalarTypedValue[str]): pass
+
+LocalChatOutputs: ta.TypeAlias = ChatOutputs | LogPath
+LocalChatResponse: ta.TypeAlias = Response[Message, LocalChatOutputs]
+
+LocalChatService: ta.TypeAlias = Service[LocalChatRequest, LocalChatResponse]
+
+# Remote chat
+
+class RemoteChatOption(Option, lang.Abstract): pass
+class ApiKey(RemoteChatOption, tv.ScalarTypedValue[str]): pass
+
+RemoteChatOptions: ta.TypeAlias = ChatOptions | RemoteChatOption
+RemoteChatRequest: ta.TypeAlias = Request[Chat, RemoteChatOptions]
+
+class RemoteChatOutput(Output, lang.Abstract): pass
+class BilledCostInUsd(RemoteChatOutput, tv.UniqueScalarTypedValue[float]): pass
+
+RemoteChatOutputs: ta.TypeAlias = ChatOutputs | RemoteChatOutput
+RemoteChatResponse: ta.TypeAlias = Response[Message, RemoteChatOutputs]
+
+RemoteChatService: ta.TypeAlias = Service[RemoteChatRequest, RemoteChatResponse]
+```
+

ommlds/minichain/services/__init__.py

@@ -1,155 +1,4 @@
 # ruff: noqa: I001
-"""
-The core service abstraction. In general, Services are intended to encapsulate non-trivial, resourceful, effectful
-operations, which are likely to have various implementations, each having their own specific capabilities in addition
-to their common interface, and where wrapping, adapting, and transforming them in a uniform manner is desirable.
-
-For example:
- - A ChatService is passed a Request with a Chat value and returns a Response with an AiChat value.
- - A ChatChoicesService is passed a Request with a Chat and returns a Response with a list of AiChoices.
- - A ChatChoicesServiceChatService is a simple adapter taking a ChatChoicesService which it will invoke with its given
-   Request, expect a single AiChoice value in that Response, and return that single AiChat as its Response - thus acting
-   as a ChatService.
-   - Thus, all chat backends that return choices can be adapted to code expecting a single chat as output.
- - A ChatStreamService is passed a Request with a Chat value and returns a Response with a value from which AiDeltas
-   may be streamed.
- - A ChatChoicesStreamService is passed a Request with a Chat value and returns a Response with a value from which
-   AiChoicesDeltas may be streamed.
- - A ChatChoicesStreamServiceChatChoicesService is an adapter taking a ChatChoicesStreamService and aggregating the
-   AiChoicesDeltas into joined, non-delta AiChoices.
-   - This may then be wrapped in a ChatChoicesServiceChatService to act as a ChatService.
-   - In practice however there are usually dedicated streaming and non-streaming implementations if possible as
-     non-streaming will usually have less overhead.
- - An OpenaiChatChoicesService can act as a ChatChoicesService, and will accept all generic ChatOptions, in addition to
-   any OpenaiChatOptions inapplicable to any other backend. It may also produce all generic ChatOutputs, in addition to
-   OpenaiChatOutputs that will not be produced by other backends.
- - Beyond chat, a VectorSearchService is passed a Request with a VectorSearch value and returns a Response with a
-   VectorHits value.
- - A RetryService wraps any other Service and will attempt to re-invoke it on failure.
- - A FirstInWinsService wraps any number of other Services and will return the first non-error Response it receives.
-
-The service abstraction consists of 3 interrelated generic types:
- - Request, an immutable final generic class containing a single value and any number of options.
- - Response, an immutable final generic class containing a single value and any number of outputs.
- - Service, a generic protocol consisting of a single method `invoke`, taking a request and returning a response.
-
-There are 2 related abstract base classes in the parent package:
- - Option, a non-generic abstract class representing a service option.
- - Output, a non-generic abstract class representing a service output.
-
-The purpose of this arrangement is to provide the following:
- - There is only one method - `Service.invoke` - to deal with.
- - There is no base `Service` class - service types are distinguished only by the requests they accept and responses
-   they return.
- - It facilitates a clear, introspectable, generally type-safe means for handling 'less-specific' and 'more-specific'
-   service types.
- - It facilitates generic wrapper and transformation machinery.
-
-The variance of the type parameters of the 3 classes is central:
- - `Request[V_co, OptionT_co]`
- - `Response[V_co, OutputT_contra]`
- - `Service[RequestT_contra, ResponseT_co]`
-
-And to understand this, it's important to understand how Option and Output subtypes are intended to be arranged:
- - These types are *not* intended to form a deep type hierarchy:
-   - A RemoteChatOption is *not* intended to inherit from a ChatOption: a ChatOption (be it a base class or union alias)
-     represents an option that *any* ChatService can accept, whereas a RemoteChatOption represents an option that *only*
-     applies to a RemoteChatService.
-   - If RemoteChatOption inherited from a base ChatOption, then it would have to apply to *all* ChatService
-     implementations.
-   - For example: were ApiKey to inherit from ChatOption, then it would have to apply to all ChatServices, including
-     LocalChatService, which has no concept of an api key.
- - Similarly, a RemoteChatOutput is *not* intended to inherit from a ChatOutput: a ChatOutput represents an output that
-   *any* ChatService can produce, whereas a RemoteChatOutput represents an output that *only* applies to a
-   RemoteChatService.
- - These 2 types are intended to form flat, disjoint, unrelated families of subtypes, and Request and Response are
-   intended to be parameterized by the unions of all such families they may contain.
- - Because of this, one's visual intuition regarding types and subtypes may be reversed: `int` is effectively a subtype
-   of `int | str` despite `int` being a visually shorter, less complex type.
-   - `int` is a *MORE SPECIFIC* / *STRICT SUBSET* subtype of `int | str`, the *LESS SPECIFIC* / *STRICT SUPERSET*
-     supertype.
-
-Regarding type variance:
- - Service has the classic setup of contravariant input and covariant output:
-   - A RemoteChatService *is a* ChatService.
-   - A RemoteChatService may accept less specific requests than a ChatService.
-   - A RemoteChatService may return more specific responses than a ChatService.
- - Request is covariant on its options:
-   - Recall, a RemoteChatOption *is not a* ChatOption.
-   - A ChatRequest *is a* RemoteChatRequest as it will not contain options RemoteChatService cannot accept.
- - Response is contravariant on its outputs:
-   - Recall, a RemoteChatOutput *is not a* ChatOutput.
-   - A RemoteChatResponse *is a* ChatResponse even though it may contain additional output variants not produced by
-     every ChatService.
-   - Code that calls a ChatService and is given a ChatResponse must be prepared to handle (usually by simply ignoring)
-     outputs not necessarily produced by a base ChatService.
-
-Below is a representative illustration of these types and their relationships. Note how:
- - There is no subclassing of Request, Response, or Service - just type aliasing.
- - There is no deep, shared subclassing of Option or Output.
- - The type args passed to Request and Response are unions of all the Option and Output subtypes they may contain.
-   - These unions are kept in pluralized type aliases for convenience.
- - There is no base ChatOption or ChatOutput class - were there, it would not be included in the base classes of any
-   local or remote only option or output.
- - The local and remote sections take different but equivalent approaches:
-   - There are no base LocalChatOption or LocalChatOutput classes, but there *are* base RemoteChatOption and
-     RemoteChatOutput classes.
-   - Without any common base classes (besides the lowest level Output and Option classes), the local section treats them
-     as each distinct and bespoke, and the pluralized LocalChatOptions and LocalChatOutputs type aliases aggregate them
-     by explicitly listing them.
-   - With the common RemoteChatOption and RemoteChatOutput base classes, the remote section treats them as a related
-     family that any 'RemoteChat'-like service should accept and produce.
-
-```
-# Common chat
-
-class MaxTokens(Option, tv.UniqueScalarTypedValue[int]): pass
-class Temperature(Option, tv.UniqueScalarTypedValue[float]): pass
-
-ChatOptions: ta.TypeAlias = MaxTokens | Temperature
-ChatRequest: ta.TypeAlias = Request[Chat, ChatOptions]
-
-class TokenUsage(Output, tv.UniqueScalarTypedValue[int]): pass
-class ElapsedTime(Output, tv.UniqueScalarTypedValue[float]): pass
-
-ChatOutput: ta.TypeAlias = TokenUsage | ElapsedTime
-ChatResponse: ta.TypeAlias = Response[Message, ChatOutput]
-
-ChatService: ta.TypeAlias = Service[ChatRequest, ChatResponse]
-
-# Local chat
-
-class ModelPath(Option, tv.ScalarTypedValue[str]): pass
-
-LocalChatOptions: ta.TypeAlias = ChatOptions | ModelPath
-LocalChatRequest: ta.TypeAlias = Request[Chat, LocalChatOptions]
-
-class LogPath(Output, tv.ScalarTypedValue[str]): pass
-
-LocalChatOutputs: ta.TypeAlias = ChatOutput | LogPath
-LocalChatResponse: ta.TypeAlias = Response[Message, LocalChatOutputs]
-
-LocalChatService: ta.TypeAlias = Service[LocalChatRequest, LocalChatResponse]
-
-# Remote chat
-
-class RemoteChatOption(Option, lang.Abstract): pass
-class ApiKey(RemoteChatOption, tv.ScalarTypedValue[str]): pass
-
-RemoteChatOptions: ta.TypeAlias = ChatOptions | RemoteChatOption
-RemoteChatRequest: ta.TypeAlias = Request[Chat, RemoteChatOptions]
-
-class RemoteChatOutput(Output, lang.Abstract): pass
-class BilledCostInUsd(RemoteChatOutput, tv.UniqueScalarTypedValue[float]): pass
-
-RemoteChatOutputs: ta.TypeAlias = ChatOutput | RemoteChatOutput
-RemoteChatResponse: ta.TypeAlias = Response[Message, RemoteChatOutputs]
-
-RemoteChatService: ta.TypeAlias = Service[RemoteChatRequest, RemoteChatResponse]
-```
-"""
-
-
 from .facades import (  # noqa
     ServiceFacade,
 

ommlds/minichain/services/requests.py

@@ -51,7 +51,7 @@ class Request(  # type: ignore[type-var]  # FIXME: _TypedValues param is invaria
      - a sequence of options of type `OptionT_co`
      - metadata of type `RequestMetadatas`
 
-    Refer to the package docstring for an explanation of its type var variance.
+    Refer to the package README.md for an explanation of its type var variance.
 
     This class is final, but each instance's `__orig_class__` (if present) is significant. It is encouraged to construct
     these through a pre-parameterized type alias, and the provided `with_` methods should be used rather than

ommlds/minichain/services/responses.py

@@ -49,7 +49,7 @@ class Response(  # type: ignore[type-var]  # FIXME: _TypedValues param is invari
      - a sequence of outputs of type `OutputT_contra`
      - metadata of type `ResponseMetadatas`
 
-    Refer to the package docstring for an explanation of its type var variance.
+    Refer to the package README.md for an explanation of its type var variance.
 
     This class is final, but each instance's `__orig_class__` (if present) is significant. It is encouraged to construct
     these through a pre-parameterized type alias, and the provided `with_` methods should be used rather than

ommlds/minichain/services/services.py

@@ -15,7 +15,7 @@ class Service(lang.ProtocolForbiddenAsBaseClass, ta.Protocol[RequestT_contra, Re
     Universal service protocol, comprised of a single method `invoke`, accepting a request of type `RequestT_contra` and
     returning a response of type `ResponseT_co`.
 
-    Refer to the package docstring for an explanation of its type var variance.
+    Refer to the package README.md for an explanation of its type var variance.
 
     This class is final, but each instance's `__orig_class__` (if present) is significant.
     """

{ommlds-0.0.0.dev501.dist-info → ommlds-0.0.0.dev502.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ommlds
-Version: 0.0.0.dev501
+Version: 0.0.0.dev502
 Summary: ommlds
 Author: wrmsr
 License-Expression: BSD-3-Clause
@@ -14,9 +14,9 @@ Classifier: Programming Language :: Python :: 3.13
 Requires-Python: >=3.13
 Description-Content-Type: text/markdown
 License-File: LICENSE
-Requires-Dist: omlish==0.0.0.dev501
+Requires-Dist: omlish==0.0.0.dev502
 Provides-Extra: all
-Requires-Dist: omdev==0.0.0.dev501; extra == "all"
+Requires-Dist: omdev==0.0.0.dev502; extra == "all"
 Requires-Dist: llama-cpp-python~=0.3; extra == "all"
 Requires-Dist: mlx~=0.30; sys_platform == "darwin" and extra == "all"
 Requires-Dist: mlx-lm~=0.29; sys_platform == "darwin" and extra == "all"
@@ -38,7 +38,7 @@ Requires-Dist: mwparserfromhell~=0.7; extra == "all"
 Requires-Dist: wikitextparser~=0.56; extra == "all"
 Requires-Dist: lxml>=5.3; python_version < "3.13" and extra == "all"
 Provides-Extra: omdev
-Requires-Dist: omdev==0.0.0.dev501; extra == "omdev"
+Requires-Dist: omdev==0.0.0.dev502; extra == "omdev"
 Provides-Extra: backends
 Requires-Dist: llama-cpp-python~=0.3; extra == "backends"
 Requires-Dist: mlx~=0.30; sys_platform == "darwin" and extra == "backends"

{ommlds-0.0.0.dev501.dist-info → ommlds-0.0.0.dev502.dist-info}/RECORD

@@ -1,4 +1,4 @@
-ommlds/.omlish-manifests.json,sha256=kLsoDH1Pe7R1m4KgsXa-WxZapb_OyQs3mBi0XYyTn1g,27872
+ommlds/.omlish-manifests.json,sha256=s6qy0XrbNb0iojn6OOLp-nuuELfpYGwX_SB9GFyShqU,28066
 ommlds/README.md,sha256=xhbl2n19GznXrIzAGdlX8PAYJYsOo_Zu63I7G1UFRZE,398
 ommlds/__about__.py,sha256=cdexoZ9J6msGQeIwveAx4JM0WlBDrWdjRkhSI9VHB9Q,1901
 ommlds/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
@@ -262,7 +262,7 @@ ommlds/minichain/backends/impls/sqlite.py,sha256=NOFm_fgr-OZ8mo7etj0zwvxsDnidRwK
 ommlds/minichain/backends/impls/tavily.py,sha256=k67QQF4cL8vMtE5LOXxczNFMGlMeRWV0oGwugLgS-Y0,1986
 ommlds/minichain/backends/impls/anthropic/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 ommlds/minichain/backends/impls/anthropic/chat.py,sha256=e4Kcbjvca_yaZsNB_-h335gSCbz4ma1lMUvuR4WzEFE,4874
-ommlds/minichain/backends/impls/anthropic/names.py,sha256=GPPeYt0CcDcDCR8I6BMd7bMjC_Zk_bjnLLpF9ClwXcg,1099
+ommlds/minichain/backends/impls/anthropic/names.py,sha256=t70dOuzqpSu9LE_MxfOl2mQmwfTkELT7jWduvuEVMbk,1099
 ommlds/minichain/backends/impls/anthropic/protocol.py,sha256=eMqkl7ML5btqJ27_9l6RY2zdTMsQe0k3Kn_keNq0-Mk,3337
 ommlds/minichain/backends/impls/anthropic/stream.py,sha256=jxKzytoYJLK9JftihGhWTcFIoXFgouQR7Yu5Q1j_ku8,8794
 ommlds/minichain/backends/impls/cerebras/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
@@ -276,7 +276,7 @@ ommlds/minichain/backends/impls/dummy/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCe
 ommlds/minichain/backends/impls/dummy/chat.py,sha256=FUTvNPWmb4Hm-axglvPiqbvLwE7sajHOM5H7j9Qj2-c,2283
 ommlds/minichain/backends/impls/google/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 ommlds/minichain/backends/impls/google/chat.py,sha256=lGb5blGLlcBlt9xeDZJvbh5SlV7fgfezd5_As_SPBXo,6499
-ommlds/minichain/backends/impls/google/names.py,sha256=HxHJ31HeKZg6aW1C_Anqp-gamCXpq9pOdKj8_yVgE8Y,871
+ommlds/minichain/backends/impls/google/names.py,sha256=Yt7xL84JZEtPf7CIcBzEBrWAfEUUs2_gXk2W7m5wC3g,1051
 ommlds/minichain/backends/impls/google/search.py,sha256=y5_6seSRU8CFnLA_Ja8XEMbIBWSgwBzE1iBf-qyz0tA,3427
 ommlds/minichain/backends/impls/google/stream.py,sha256=AT8qbP0EqJUnf-D45aTbEQ0h5lvgtIK6XKki0t8RkZE,8029
 ommlds/minichain/backends/impls/google/tools.py,sha256=bP4bqHt1oZTvrcObkjQCNAUJEXrR9fFIRuvjsVFM910,5109
@@ -427,14 +427,15 @@ ommlds/minichain/registries/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMp
 ommlds/minichain/registries/globals.py,sha256=M4-RTsjHfm7FRXqV-4ecWywEF1Di2lnTn3a7OJhtzkU,3224
 ommlds/minichain/registries/manifests.py,sha256=GTWk4lssAk8mmG3ilGK2NvIU-rGS3otOZNuGQUDStMI,362
 ommlds/minichain/registries/registry.py,sha256=wmk88NsM20Kl4PduX3Oy5roHPfNKtXENCITTc7M8gAY,4626
-ommlds/minichain/services/__init__.py,sha256=E31Ly3v-N-cTRNougDBF9BSZyYQvdm-W87ZW4LL5e3Y,9308
+ommlds/minichain/services/README.md,sha256=uHS4Exv-9Wlm3WMDn9myZ_MBPgsjKG_AN1YeCrBn4qo,9428
+ommlds/minichain/services/__init__.py,sha256=Su3p_xIAdTK4uTabmSAEIwnoVq0EL5_OpFi1TROfQ5U,424
 ommlds/minichain/services/_marshal.py,sha256=zIp4WnbGh-e2DS2lN2qi_Y3XO-MJN8sVYGB4HAPOOIU,5321
 ommlds/minichain/services/_origclasses.py,sha256=cUao3vxNzArsHH3RAC3PKHLBWN66oQDvYyGT_agYZ-g,1625
 ommlds/minichain/services/_typedvalues.py,sha256=j3Rw6cZ-xfhzSTOPDe4OLsvzsADuy9r0lVmW9_egvjM,3040
 ommlds/minichain/services/facades.py,sha256=zoTY5GT7yIrFUY3fX7a-sSOvkk1_4GK5FlJJmRL_ems,1734
-ommlds/minichain/services/requests.py,sha256=BZgn91yM2U43S4ihVKMYGBxFEGLOqRfuH8rt6IwyRIk,3422
-ommlds/minichain/services/responses.py,sha256=qJ3d8FM4hB1UuAsMPg9j8guVZJvhc10L0hbMWxQnrGU,3381
-ommlds/minichain/services/services.py,sha256=8axlOnQvI83icwRK0XLha0svSQrLXC1_B6MZXN_mzUc,685
+ommlds/minichain/services/requests.py,sha256=PznUkVISx8PEPtio7KGH0YEvktkBp9FqU_W5KxQDqHM,3422
+ommlds/minichain/services/responses.py,sha256=jSUFUrY0DDnRyimh3pD2ee2ZnOcH8oQxxZnwiLf5p9A,3381
+ommlds/minichain/services/services.py,sha256=c2uHH5Pt0wtUDQgJQEbw6NsS5NVSXMJirWISJ5FaRNg,685
 ommlds/minichain/stream/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
 ommlds/minichain/stream/services.py,sha256=YXfEj3ZXKZ3Svkig6f3hOReHgZnLY2tDn2bgB0RIoRI,5566
 ommlds/minichain/stream/wrap.py,sha256=nQC0aCi49I18nF0Yx8qiiLkhIAECV6s6o4pvOy5Kx98,2041
@@ -512,9 +513,9 @@ ommlds/wiki/utils/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU
 ommlds/wiki/utils/io.py,sha256=UKgDJGtmpnWvIqVd2mJc2QNPOqlToEY1GEveNp6_pMo,7088
 ommlds/wiki/utils/progress.py,sha256=EhvKcMFYtsarCQhIahlO6f0SboyAKP3UwUyrnVnP-Vk,3222
 ommlds/wiki/utils/xml.py,sha256=sNJNkZ9rT8B-kJMO6bRz8J1USy4fyPx0m2PwTX7vxYY,3846
-ommlds-0.0.0.dev501.dist-info/licenses/LICENSE,sha256=B_hVtavaA8zCYDW99DYdcpDLKz1n3BBRjZrcbv8uG8c,1451
-ommlds-0.0.0.dev501.dist-info/METADATA,sha256=5bTbYGDC1rBgqoIHEZ88BxuMkXbxNQXxU4MzM3UjvLg,3495
-ommlds-0.0.0.dev501.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
-ommlds-0.0.0.dev501.dist-info/entry_points.txt,sha256=Z5YWtX7ClfiCKdW-dd_CSVvM0h4yQpJPi-2G3q6gNFo,35
-ommlds-0.0.0.dev501.dist-info/top_level.txt,sha256=Rbnk5d5wi58vnAXx13WFZqdQ4VX8hBCS2hEL3WeXOhY,7
-ommlds-0.0.0.dev501.dist-info/RECORD,,
+ommlds-0.0.0.dev502.dist-info/licenses/LICENSE,sha256=B_hVtavaA8zCYDW99DYdcpDLKz1n3BBRjZrcbv8uG8c,1451
+ommlds-0.0.0.dev502.dist-info/METADATA,sha256=gaDPjUyCBXbQflQQZvorRw3dRZyJ5cDtalsPcM9L-X4,3495
+ommlds-0.0.0.dev502.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
+ommlds-0.0.0.dev502.dist-info/entry_points.txt,sha256=Z5YWtX7ClfiCKdW-dd_CSVvM0h4yQpJPi-2G3q6gNFo,35
+ommlds-0.0.0.dev502.dist-info/top_level.txt,sha256=Rbnk5d5wi58vnAXx13WFZqdQ4VX8hBCS2hEL3WeXOhY,7
+ommlds-0.0.0.dev502.dist-info/RECORD,,