tigrbl-concrete 0.4.2.dev4__tar.gz → 0.4.3.dev4__tar.gz

{tigrbl_concrete-0.4.2.dev4 → tigrbl_concrete-0.4.3.dev4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: tigrbl-concrete
-Version: 0.4.2.dev4
+Version: 0.4.3.dev4
 Summary: Concrete Tigrbl implementations for reusable framework behavior, sessions, routes, responses, and base abstraction adapters.
 License: Apache License
                                     Version 2.0, January 2004
@@ -253,7 +253,7 @@ Description-Content-Type: text/markdown
 <a href="https://discord.gg/K4YTAPapjR"><img src="https://img.shields.io/badge/Discord-Join%20chat-5865F2?logo=discord&logoColor=white" alt="Discord community for tigrbl-concrete"/></a>
 <a href="https://github.com/tigrbl/tigrbl/blob/master/pkgs/core/tigrbl_concrete/README.md"><img src="https://hits.sh/github.com/tigrbl/tigrbl/blob/master/pkgs/core/tigrbl_concrete/README.md.svg?label=hits" alt="Repository hits for tigrbl-concrete README"/></a>
 <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache%202.0-525252" alt="Apache 2.0 license"/></a>
-<a href="pyproject.toml"><img src="https://img.shields.io/badge/python-3.10%20%7C%203.11%20%7C%203.12%20%7C%203.13%20%7C%203.14-3776ab" alt="Python versions 3.10 | 3.11 | 3.12 | 3.13 | 3.14 for tigrbl-concrete"/></a>
+<a href="pyproject.toml"><img src="https://img.shields.io/badge/python-3.10%2C%203.11%2C%203.12%2C%203.13%2C%203.14-3776ab" alt="Python versions 3.10 | 3.11 | 3.12 | 3.13 | 3.14 for tigrbl-concrete"/></a>
 <a href="https://github.com/tigrbl/tigrbl/blob/master/docs/README.md"><img src="https://img.shields.io/badge/workspace-core-1f6feb" alt="Workspace group for tigrbl-concrete"/></a>
 </div>
 
@@ -310,7 +310,7 @@ pip install tigrbl-concrete
 | Entry points | `tigrbl.engine_plugins` |
 | Optional extras | none declared |
 | Legal files | `LICENSE`, `NOTICE` |
-| Supported Python | `3.10 | 3.11 | 3.12 | 3.13 | 3.14` |
+| Supported Python | `3.10, 3.11, 3.12, 3.13, 3.14` |
 
 ## What It Owns
 
@@ -319,6 +319,20 @@ pip install tigrbl-concrete
 Implementation orientation:
 - `tigrbl_concrete`: _concrete/, _decorators/, _mapping/, ddl/, decorators, engine/, factories/, resolve/, security/, shortcuts/, system/, transport/
 
+Package catalog:
+- `tigrbl_concrete/_concrete/`: concrete app, router, route, table, column, operation, schema, request, response, headers, body, middleware, background, storage, session, binding, engine, and security classes/adapters.
+- `tigrbl_concrete/_concrete/_security/`: API key, HTTP Basic, HTTP Bearer, mutual TLS, OAuth2, and OpenID Connect security primitives.
+- `tigrbl_concrete/_decorators/` and `tigrbl_concrete/decorators.py`: concrete decorator implementations that attach engine, hook, op, response, schema, session, middleware, allow-anon, and related metadata.
+- `tigrbl_concrete/_mapping/`: app, router, model, column, operation, core, and app-spec lowering helpers that turn specs and model metadata into concrete registrations.
+- `tigrbl_concrete/engine/`: engine builders, binding, capability declarations, plugin discovery, registry, resolver, and collection helpers.
+- `tigrbl_concrete/factories/` and `tigrbl_concrete/shortcuts/`: concrete app and REST shortcut helpers consumed by the facade.
+- `tigrbl_concrete/resolve/`: handler resolution helpers.
+- `tigrbl_concrete/security/`: concrete security dependency helpers.
+- `tigrbl_concrete/system/diagnostics`: `/system/healthz`, `/system/hookz`, `/system/kernelz`, `/system/methodz`, and diagnostic router helpers.
+- `tigrbl_concrete/system/docs`: OpenAPI, OpenRPC, JSON Schema, Swagger, lens, runtime-ops, and surface documentation helpers.
+- `tigrbl_concrete/transport/rest` and `tigrbl_concrete/transport/jsonrpc`: REST route aggregation and JSON-RPC helper/model utilities.
+- `tigrbl_concrete/ddl/` and `tigrbl_concrete/system/static`/`favicon`: DDL and static/docs support surfaces.
+
 ## Public API and Import Surface
 
 - Import roots: `tigrbl_concrete`.
@@ -326,6 +340,78 @@ Implementation orientation:
 - Workspace dependencies: [`tigrbl-atoms`](https://pypi.org/project/tigrbl-atoms/), [`tigrbl-base`](https://pypi.org/project/tigrbl-base/), [`tigrbl-core`](https://pypi.org/project/tigrbl-core/), [`tigrbl-ops-olap`](https://pypi.org/project/tigrbl-ops-olap/), [`tigrbl-ops-oltp`](https://pypi.org/project/tigrbl-ops-oltp/), [`tigrbl-ops-realtime`](https://pypi.org/project/tigrbl-ops-realtime/), [`tigrbl-runtime`](https://pypi.org/project/tigrbl-runtime/), [`tigrbl-typing`](https://pypi.org/project/tigrbl-typing/).
 - External runtime dependencies: `orjson`, `pydantic>=2.0`, `sqlalchemy`, `uvicorn`.
 
+## Concrete Implementation Semantics
+
+`tigrbl-concrete` is where abstract specs and base contracts become usable Python framework objects. It is intentionally below the `tigrbl` facade and above the atom/kernel/runtime internals. Application developers normally import through `tigrbl`; extension authors import this package when they need concrete classes, decorators, engine resolution, docs mounting, or diagnostics without taking the facade dependency.
+
+The package performs four broad jobs:
+
+- Lower core specs and base contracts into concrete app/router/table/operation objects.
+- Register REST and JSON-RPC projections for model operations.
+- Resolve engines, handlers, schemas, responses, security dependencies, middleware, and docs surfaces.
+- Expose operational introspection through system routes.
+
+## REST and JSON-RPC Surfaces
+
+Concrete routing keeps REST and JSON-RPC projections tied to the same operation inventory:
+
+| Surface | Concrete responsibility |
+|---|---|
+| REST | Aggregate route metadata, attach handlers, apply path/method mapping, shape request/response objects, and expose OpenAPI-compatible docs. |
+| JSON-RPC | Resolve method names, validate JSON-RPC request/response models, dispatch through the same operation handlers, and expose OpenRPC-compatible docs. |
+| Docs | Publish OpenAPI, OpenRPC, JSON Schema, Swagger, runtime operation views, and surface/lens outputs from the same concrete registration data. |
+| Diagnostics | Expose `healthz`, `hookz`, `kernelz`, and `methodz` so users can inspect runtime health, hook order, kernel plans, and method inventory. |
+
+Avoid adding one-off framework routes for model behavior when an operation spec can represent the behavior. Ops keep REST, JSON-RPC, docs, hooks, and diagnostics unified.
+
+## Engine and Provider Behavior
+
+The engine subpackage owns concrete engine resolution and plugin discovery. It can build and bind engines from specs, providers, mappings, or decorator metadata, then expose capability information for runtime and tests.
+
+Resolution follows the framework's specificity rule:
+
+```text
+operation > table/model > router > app > defaults
+```
+
+Best practices:
+- Declare engine intent through specs or decorators instead of constructing SQLAlchemy engines inside handlers.
+- Keep engine plugins explicit and capability-aware.
+- Test resolver behavior when adding a new engine package or new engine context shape.
+- Preserve separation between engine resolution and transaction lifecycle; atoms/runtime own transaction phase progression.
+
+## System and Operational Endpoints
+
+Concrete apps can mount system endpoints:
+
+- `/system/healthz` for basic process health.
+- `/system/hookz` for model/operation/phase hook order.
+- `/system/kernelz` for compiled kernel phase plans.
+- `/system/methodz` for exposed method inventory.
+- docs endpoints for OpenAPI, OpenRPC, JSON Schema, Swagger, and runtime operation surfaces.
+
+These endpoints are operational tools. They should reflect registered framework state and compiled plans; do not hard-code documentation that can drift away from actual registrations.
+
+## Security and Middleware
+
+Security primitives include API key, HTTP Basic, HTTP Bearer, mutual TLS, OAuth2, and OpenID Connect helpers. Use them as dependencies or framework-level security specs so security behavior participates in lifecycle ordering and diagnostics. Middleware should be declared through concrete middleware helpers or specs rather than wrapping generated routes in ways the kernel cannot see.
+
+## Extension Guidance
+
+- Use concrete decorators and factories when building public conveniences for the facade.
+- Keep compatibility imports in `tigrbl` thin; implement reusable behavior here or in lower packages.
+- Do not bypass kernel/runtime plans when wiring REST or JSON-RPC handlers.
+- Keep docs, diagnostics, and transport helpers generated from actual registration state.
+- Treat `_concrete` classes as framework implementation surfaces; public application documentation should continue to prefer facade imports.
+
+Authoring BCP for this boundary:
+- Do use `tigrbl-concrete` to lower specs and base contracts into concrete app, router, table, operation, schema, request, response, engine, security, docs, diagnostics, and transport implementations.
+- Do keep REST and JSON-RPC projections tied to the same operation inventory and handler resolution path.
+- Do keep framework-internal ASGI, Starlette-compatible, SQLAlchemy, and engine mechanics behind concrete Tigrbl adapters.
+- Do not teach application users to bypass the `tigrbl` facade and import `_concrete` classes for normal service code.
+- Do not wire one-off handlers around kernel/runtime plans, diagnostics, generated docs, or operation specs.
+- Avoid hard-coded documentation and diagnostics that can drift away from actual registrations.
+
 ## Usage Examples
 
 ### Verify the installed package
@@ -391,6 +477,8 @@ Choose `tigrbl-concrete` when the quick-answer table matches your use case. Choo
 - [Package layout](https://github.com/tigrbl/tigrbl/blob/master/docs/developer/PACKAGE_LAYOUT.md)
 - [Current target](https://github.com/tigrbl/tigrbl/blob/master/docs/conformance/CURRENT_TARGET.md)
 - [Current state](https://github.com/tigrbl/tigrbl/blob/master/docs/conformance/CURRENT_STATE.md)
+- [Next steps](https://github.com/tigrbl/tigrbl/blob/master/docs/conformance/NEXT_STEPS.md)
+- [Documentation pointers](https://github.com/tigrbl/tigrbl/blob/master/docs/governance/DOC_POINTERS.md)
 - [SSOT registry](https://github.com/tigrbl/tigrbl/blob/master/.ssot/registry.json)
 - [Release workflow](https://github.com/tigrbl/tigrbl/actions/workflows/publish.yml)
 
@@ -402,7 +490,7 @@ Choose `tigrbl-concrete` when the quick-answer table matches your use case. Choo
 
 ## Package-local Boundary
 
-This README is the package-local distribution entry point for `tigrbl-concrete`. It answers install, usage, API, ownership, and certification-orientation questions for this package. Broader architectural decisions, release status, and cross-package proof chains remain in the repository-level docs and SSOT registry.
+This file is a package-local distribution entry point. This README is the package-local distribution entry point for `tigrbl-concrete`. It answers install, usage, API, ownership, and certification-orientation questions for this package. Broader architectural decisions, release status, and cross-package proof chains remain in the repository-level docs and SSOT registry.
 
 ## License
 

{tigrbl_concrete-0.4.2.dev4 → tigrbl_concrete-0.4.3.dev4}/README.md

@@ -7,7 +7,7 @@
 <a href="https://discord.gg/K4YTAPapjR"><img src="https://img.shields.io/badge/Discord-Join%20chat-5865F2?logo=discord&logoColor=white" alt="Discord community for tigrbl-concrete"/></a>
 <a href="https://github.com/tigrbl/tigrbl/blob/master/pkgs/core/tigrbl_concrete/README.md"><img src="https://hits.sh/github.com/tigrbl/tigrbl/blob/master/pkgs/core/tigrbl_concrete/README.md.svg?label=hits" alt="Repository hits for tigrbl-concrete README"/></a>
 <a href="LICENSE"><img src="https://img.shields.io/badge/license-Apache%202.0-525252" alt="Apache 2.0 license"/></a>
-<a href="pyproject.toml"><img src="https://img.shields.io/badge/python-3.10%20%7C%203.11%20%7C%203.12%20%7C%203.13%20%7C%203.14-3776ab" alt="Python versions 3.10 | 3.11 | 3.12 | 3.13 | 3.14 for tigrbl-concrete"/></a>
+<a href="pyproject.toml"><img src="https://img.shields.io/badge/python-3.10%2C%203.11%2C%203.12%2C%203.13%2C%203.14-3776ab" alt="Python versions 3.10 | 3.11 | 3.12 | 3.13 | 3.14 for tigrbl-concrete"/></a>
 <a href="https://github.com/tigrbl/tigrbl/blob/master/docs/README.md"><img src="https://img.shields.io/badge/workspace-core-1f6feb" alt="Workspace group for tigrbl-concrete"/></a>
 </div>
 
@@ -64,7 +64,7 @@ pip install tigrbl-concrete
 | Entry points | `tigrbl.engine_plugins` |
 | Optional extras | none declared |
 | Legal files | `LICENSE`, `NOTICE` |
-| Supported Python | `3.10 | 3.11 | 3.12 | 3.13 | 3.14` |
+| Supported Python | `3.10, 3.11, 3.12, 3.13, 3.14` |
 
 ## What It Owns
 
@@ -73,6 +73,20 @@ pip install tigrbl-concrete
 Implementation orientation:
 - `tigrbl_concrete`: _concrete/, _decorators/, _mapping/, ddl/, decorators, engine/, factories/, resolve/, security/, shortcuts/, system/, transport/
 
+Package catalog:
+- `tigrbl_concrete/_concrete/`: concrete app, router, route, table, column, operation, schema, request, response, headers, body, middleware, background, storage, session, binding, engine, and security classes/adapters.
+- `tigrbl_concrete/_concrete/_security/`: API key, HTTP Basic, HTTP Bearer, mutual TLS, OAuth2, and OpenID Connect security primitives.
+- `tigrbl_concrete/_decorators/` and `tigrbl_concrete/decorators.py`: concrete decorator implementations that attach engine, hook, op, response, schema, session, middleware, allow-anon, and related metadata.
+- `tigrbl_concrete/_mapping/`: app, router, model, column, operation, core, and app-spec lowering helpers that turn specs and model metadata into concrete registrations.
+- `tigrbl_concrete/engine/`: engine builders, binding, capability declarations, plugin discovery, registry, resolver, and collection helpers.
+- `tigrbl_concrete/factories/` and `tigrbl_concrete/shortcuts/`: concrete app and REST shortcut helpers consumed by the facade.
+- `tigrbl_concrete/resolve/`: handler resolution helpers.
+- `tigrbl_concrete/security/`: concrete security dependency helpers.
+- `tigrbl_concrete/system/diagnostics`: `/system/healthz`, `/system/hookz`, `/system/kernelz`, `/system/methodz`, and diagnostic router helpers.
+- `tigrbl_concrete/system/docs`: OpenAPI, OpenRPC, JSON Schema, Swagger, lens, runtime-ops, and surface documentation helpers.
+- `tigrbl_concrete/transport/rest` and `tigrbl_concrete/transport/jsonrpc`: REST route aggregation and JSON-RPC helper/model utilities.
+- `tigrbl_concrete/ddl/` and `tigrbl_concrete/system/static`/`favicon`: DDL and static/docs support surfaces.
+
 ## Public API and Import Surface
 
 - Import roots: `tigrbl_concrete`.
@@ -80,6 +94,78 @@ Implementation orientation:
 - Workspace dependencies: [`tigrbl-atoms`](https://pypi.org/project/tigrbl-atoms/), [`tigrbl-base`](https://pypi.org/project/tigrbl-base/), [`tigrbl-core`](https://pypi.org/project/tigrbl-core/), [`tigrbl-ops-olap`](https://pypi.org/project/tigrbl-ops-olap/), [`tigrbl-ops-oltp`](https://pypi.org/project/tigrbl-ops-oltp/), [`tigrbl-ops-realtime`](https://pypi.org/project/tigrbl-ops-realtime/), [`tigrbl-runtime`](https://pypi.org/project/tigrbl-runtime/), [`tigrbl-typing`](https://pypi.org/project/tigrbl-typing/).
 - External runtime dependencies: `orjson`, `pydantic>=2.0`, `sqlalchemy`, `uvicorn`.
 
+## Concrete Implementation Semantics
+
+`tigrbl-concrete` is where abstract specs and base contracts become usable Python framework objects. It is intentionally below the `tigrbl` facade and above the atom/kernel/runtime internals. Application developers normally import through `tigrbl`; extension authors import this package when they need concrete classes, decorators, engine resolution, docs mounting, or diagnostics without taking the facade dependency.
+
+The package performs four broad jobs:
+
+- Lower core specs and base contracts into concrete app/router/table/operation objects.
+- Register REST and JSON-RPC projections for model operations.
+- Resolve engines, handlers, schemas, responses, security dependencies, middleware, and docs surfaces.
+- Expose operational introspection through system routes.
+
+## REST and JSON-RPC Surfaces
+
+Concrete routing keeps REST and JSON-RPC projections tied to the same operation inventory:
+
+| Surface | Concrete responsibility |
+|---|---|
+| REST | Aggregate route metadata, attach handlers, apply path/method mapping, shape request/response objects, and expose OpenAPI-compatible docs. |
+| JSON-RPC | Resolve method names, validate JSON-RPC request/response models, dispatch through the same operation handlers, and expose OpenRPC-compatible docs. |
+| Docs | Publish OpenAPI, OpenRPC, JSON Schema, Swagger, runtime operation views, and surface/lens outputs from the same concrete registration data. |
+| Diagnostics | Expose `healthz`, `hookz`, `kernelz`, and `methodz` so users can inspect runtime health, hook order, kernel plans, and method inventory. |
+
+Avoid adding one-off framework routes for model behavior when an operation spec can represent the behavior. Ops keep REST, JSON-RPC, docs, hooks, and diagnostics unified.
+
+## Engine and Provider Behavior
+
+The engine subpackage owns concrete engine resolution and plugin discovery. It can build and bind engines from specs, providers, mappings, or decorator metadata, then expose capability information for runtime and tests.
+
+Resolution follows the framework's specificity rule:
+
+```text
+operation > table/model > router > app > defaults
+```
+
+Best practices:
+- Declare engine intent through specs or decorators instead of constructing SQLAlchemy engines inside handlers.
+- Keep engine plugins explicit and capability-aware.
+- Test resolver behavior when adding a new engine package or new engine context shape.
+- Preserve separation between engine resolution and transaction lifecycle; atoms/runtime own transaction phase progression.
+
+## System and Operational Endpoints
+
+Concrete apps can mount system endpoints:
+
+- `/system/healthz` for basic process health.
+- `/system/hookz` for model/operation/phase hook order.
+- `/system/kernelz` for compiled kernel phase plans.
+- `/system/methodz` for exposed method inventory.
+- docs endpoints for OpenAPI, OpenRPC, JSON Schema, Swagger, and runtime operation surfaces.
+
+These endpoints are operational tools. They should reflect registered framework state and compiled plans; do not hard-code documentation that can drift away from actual registrations.
+
+## Security and Middleware
+
+Security primitives include API key, HTTP Basic, HTTP Bearer, mutual TLS, OAuth2, and OpenID Connect helpers. Use them as dependencies or framework-level security specs so security behavior participates in lifecycle ordering and diagnostics. Middleware should be declared through concrete middleware helpers or specs rather than wrapping generated routes in ways the kernel cannot see.
+
+## Extension Guidance
+
+- Use concrete decorators and factories when building public conveniences for the facade.
+- Keep compatibility imports in `tigrbl` thin; implement reusable behavior here or in lower packages.
+- Do not bypass kernel/runtime plans when wiring REST or JSON-RPC handlers.
+- Keep docs, diagnostics, and transport helpers generated from actual registration state.
+- Treat `_concrete` classes as framework implementation surfaces; public application documentation should continue to prefer facade imports.
+
+Authoring BCP for this boundary:
+- Do use `tigrbl-concrete` to lower specs and base contracts into concrete app, router, table, operation, schema, request, response, engine, security, docs, diagnostics, and transport implementations.
+- Do keep REST and JSON-RPC projections tied to the same operation inventory and handler resolution path.
+- Do keep framework-internal ASGI, Starlette-compatible, SQLAlchemy, and engine mechanics behind concrete Tigrbl adapters.
+- Do not teach application users to bypass the `tigrbl` facade and import `_concrete` classes for normal service code.
+- Do not wire one-off handlers around kernel/runtime plans, diagnostics, generated docs, or operation specs.
+- Avoid hard-coded documentation and diagnostics that can drift away from actual registrations.
+
 ## Usage Examples
 
 ### Verify the installed package
@@ -145,6 +231,8 @@ Choose `tigrbl-concrete` when the quick-answer table matches your use case. Choo
 - [Package layout](https://github.com/tigrbl/tigrbl/blob/master/docs/developer/PACKAGE_LAYOUT.md)
 - [Current target](https://github.com/tigrbl/tigrbl/blob/master/docs/conformance/CURRENT_TARGET.md)
 - [Current state](https://github.com/tigrbl/tigrbl/blob/master/docs/conformance/CURRENT_STATE.md)
+- [Next steps](https://github.com/tigrbl/tigrbl/blob/master/docs/conformance/NEXT_STEPS.md)
+- [Documentation pointers](https://github.com/tigrbl/tigrbl/blob/master/docs/governance/DOC_POINTERS.md)
 - [SSOT registry](https://github.com/tigrbl/tigrbl/blob/master/.ssot/registry.json)
 - [Release workflow](https://github.com/tigrbl/tigrbl/actions/workflows/publish.yml)
 
@@ -156,7 +244,7 @@ Choose `tigrbl-concrete` when the quick-answer table matches your use case. Choo
 
 ## Package-local Boundary
 
-This README is the package-local distribution entry point for `tigrbl-concrete`. It answers install, usage, API, ownership, and certification-orientation questions for this package. Broader architectural decisions, release status, and cross-package proof chains remain in the repository-level docs and SSOT registry.
+This file is a package-local distribution entry point. This README is the package-local distribution entry point for `tigrbl-concrete`. It answers install, usage, API, ownership, and certification-orientation questions for this package. Broader architectural decisions, release status, and cross-package proof chains remain in the repository-level docs and SSOT registry.
 
 ## License
 

{tigrbl_concrete-0.4.2.dev4 → tigrbl_concrete-0.4.3.dev4}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "tigrbl-concrete"
-version = "0.4.2.dev4"
+version = "0.4.3.dev4"
 description = "Concrete Tigrbl implementations for reusable framework behavior, sessions, routes, responses, and base abstraction adapters."
 readme = "README.md"
 license = { file = "LICENSE" }

{tigrbl_concrete-0.4.2.dev4 → tigrbl_concrete-0.4.3.dev4}/tigrbl_concrete/_concrete/__init__.py

@@ -19,7 +19,31 @@ _EXPORTS = {
     "Schema": "_schema",
     "ForeignKey": "_storage",
     "StorageTransform": "_storage",
+    "BulkCrudTable": "_table",
+    "CrudTable": "_table",
+    "EventStreamTable": "_table",
+    "JsonRpcOlapTable": "_table",
+    "JsonRpcOltpTable": "_table",
+    "JsonRpcTable": "_table",
+    "OlapTable": "_table",
+    "OltpTable": "_table",
+    "RealtimeTable": "_table",
+    "RestJsonRpcOlapTable": "_table",
+    "RestJsonRpcOltpTable": "_table",
+    "RestJsonRpcTable": "_table",
+    "RestOlapTable": "_table",
+    "RestOltpTable": "_table",
+    "RestTable": "_table",
+    "SseTable": "_table",
+    "StreamTable": "_table",
     "Table": "_table",
+    "WebSocketJsonRpcTable": "_table",
+    "WebSocketTable": "_table",
+    "WebTransportBidiTable": "_table",
+    "WebTransportClientStreamTable": "_table",
+    "WebTransportDatagramTable": "_table",
+    "WebTransportServerStreamTable": "_table",
+    "WebTransportTable": "_table",
     "Template": "_response",
     "TableRegistry": "_table_registry",
     "Response": "_response",
@@ -35,6 +59,7 @@ _EXPORTS = {
     "Request": "_request",
     "UploadedFile": "_request",
     "WebSocket": "_websocket",
+    "Webhook": "_webhook",
     "Body": "_body",
     "Depends": "dependencies",
     "APIKey": "_security",
@@ -54,6 +79,9 @@ _EXPORTS = {
 
 __all__ = list(_EXPORTS)
 
+for _symbol in __all__:
+    globals().pop(_symbol, None)
+
 
 def __getattr__(name: str) -> Any:
     module_name = _EXPORTS.get(name)

{tigrbl_concrete-0.4.2.dev4 → tigrbl_concrete-0.4.3.dev4}/tigrbl_concrete/_concrete/_router.py

@@ -3,6 +3,7 @@
 from __future__ import annotations
 
 from contextlib import asynccontextmanager
+from pathlib import Path
 from typing import Any, Callable
 from types import SimpleNamespace
 
@@ -261,6 +262,11 @@ class Router(RouterBase):
         from tigrbl_concrete.system.static import _mount_static
         return _mount_static(self, directory=directory, path=path)
 
+    def mount_well_known(self, resources: Any, **kwargs: Any) -> tuple[str, ...]:
+        from tigrbl_concrete.system.well_known import mount_well_known
+
+        return mount_well_known(self, resources, **kwargs)
+
     def mount_app(self, *, app: Any, path: str) -> Any:
         mount_path = path if str(path).startswith("/") else f"/{path}"
         mounts = list(getattr(self, "_mounted_apps", []) or [])

tigrbl_concrete-0.4.3.dev4/tigrbl_concrete/_concrete/_rust_backend.py

@@ -0,0 +1,36 @@
+from __future__ import annotations
+
+from typing import Any
+import warnings
+
+
+def normalize_execution_backend(value: Any) -> str:
+    if value is None:
+        return "auto"
+    lowered = str(value).strip().lower()
+    if lowered == "rust":
+        raise ValueError(
+            "execution_backend='rust' is deprecated and unavailable; "
+            "Tigrbl runtime execution is Python-only."
+        )
+    if lowered not in {"auto", "python"}:
+        raise ValueError(f"unsupported execution backend: {value!r}")
+    return lowered
+
+
+def ffi_boundary_events() -> list[dict[str, Any]]:
+    warnings.warn(
+        "Rust boundary tracing is deprecated; Tigrbl runtime execution is Python-only.",
+        DeprecationWarning,
+        stacklevel=2,
+    )
+    return []
+
+
+def clear_ffi_boundary_events() -> None:
+    warnings.warn(
+        "Rust boundary tracing is deprecated; Tigrbl runtime execution is Python-only.",
+        DeprecationWarning,
+        stacklevel=2,
+    )
+    return None

{tigrbl_concrete-0.4.2.dev4 → tigrbl_concrete-0.4.3.dev4}/tigrbl_concrete/_concrete/_security/api_key.py

@@ -4,8 +4,8 @@ from __future__ import annotations
 
 from typing import Any, Sequence
 
-from tigrbl_runtime.runtime.status.exceptions import HTTPException
-from tigrbl_runtime.runtime.status.mappings import status
+from tigrbl_typing.status.exceptions import HTTPException
+from tigrbl_typing.status.mappings import status
 from tigrbl_base._base._security_base import OpenAPISecurityDependency
 
 

{tigrbl_concrete-0.4.2.dev4 → tigrbl_concrete-0.4.3.dev4}/tigrbl_concrete/_concrete/_security/http_basic.py

@@ -6,8 +6,8 @@ import base64
 from dataclasses import dataclass
 from typing import Any, Sequence
 
-from tigrbl_runtime.runtime.status.exceptions import HTTPException
-from tigrbl_runtime.runtime.status.mappings import status
+from tigrbl_typing.status.exceptions import HTTPException
+from tigrbl_typing.status.mappings import status
 from tigrbl_base._base._security_base import OpenAPISecurityDependency
 
 

{tigrbl_concrete-0.4.2.dev4 → tigrbl_concrete-0.4.3.dev4}/tigrbl_concrete/_concrete/_security/http_bearer.py

@@ -5,8 +5,8 @@ from __future__ import annotations
 from dataclasses import dataclass
 from typing import Any, Sequence
 
-from tigrbl_runtime.runtime.status.exceptions import HTTPException
-from tigrbl_runtime.runtime.status.mappings import status
+from tigrbl_typing.status.exceptions import HTTPException
+from tigrbl_typing.status.mappings import status
 from tigrbl_base._base._security_base import OpenAPISecurityDependency
 
 

{tigrbl_concrete-0.4.2.dev4 → tigrbl_concrete-0.4.3.dev4}/tigrbl_concrete/_concrete/_streaming_response.py

@@ -4,7 +4,7 @@ from __future__ import annotations
 
 from collections.abc import AsyncIterable, AsyncIterator, Iterable
 
-from tigrbl_runtime.protocol._iterators import iter_items
+from tigrbl_atoms.protocol_runtime import iter_items
 
 from ._response import Response