mirror of
https://github.com/pydantic/pydantic-ai-harness.git
synced 2026-07-21 02:45:34 +00:00
David SFandGitHub
310ffadf09
* refactor: graduate capabilities out of `experimental` (ACP excepted) The `experimental` label suppressed the try->fail->report->improve loop we want from real usage, so drop it from the harness. Ten capabilities move to top-level submodules; ACP stays experimental (it may still be reshaped or moved to core, and can't be generic across agents). - Old `pydantic_ai_harness.experimental.<name>` paths keep working as DeprecationWarning shims (via `warn_moved`), so existing imports don't break. - Renames to match capability names: authoring -> runtime_authoring, overflow -> overflowing_tool_output. - Capabilities stay in individual submodules with no top-level re-export, so importing the root package never pulls in a capability's optional deps. - Docs drop the experimental framing and the "may be removed in any release" language in favor of "API subject to change". * docs: tell capability authors to ask the user when unsure about a name Per PR review: a name is a public commitment once shipped, so ask rather than guess.
21 lines
711 B
Python
21 lines
711 B
Python
"""Runtime capability authoring: let an agent write, validate, and register real capabilities."""
|
|
|
|
from pydantic_ai_harness.runtime_authoring._capability import RuntimeAuthoring
|
|
from pydantic_ai_harness.runtime_authoring._store import AuthoredCapability, CapabilityStore
|
|
from pydantic_ai_harness.runtime_authoring._toolset import AuthoringToolset
|
|
from pydantic_ai_harness.runtime_authoring._validate import (
|
|
CapabilityValidationError,
|
|
load_capability_instance,
|
|
validate_capability_file,
|
|
)
|
|
|
|
__all__ = [
|
|
'AuthoredCapability',
|
|
'AuthoringToolset',
|
|
'CapabilityStore',
|
|
'CapabilityValidationError',
|
|
'RuntimeAuthoring',
|
|
'load_capability_instance',
|
|
'validate_capability_file',
|
|
]
|