refactor(core): drop AdapterRegistry + BaseAdapter; keep EvaluatorProtocol

The adapter-registry plugin-discovery system in uipath-core was a
parallel keyed-by-agent-type dispatcher for a fact already known
statically: the runtime-factory registry has picked the framework by
the time anything needs an "adapter". The two registries existed only
to support an open-PR pattern (#125/#126) where the runtime layer
sniffed the framework off an opaque agent. With that approach
abandoned in favor of framework plugins wiring governance at their
native seam (callback handlers, hook lists), the registry, the
BaseAdapter abstraction, and their per-package entry-point group are
all dead weight.

Deletions
- src/uipath/core/adapters/base.py — BaseAdapter + GovernedAgentBase.
  No internal consumers; the only external one (uipath-langchain
  PR #899) is unmerged and is being reshaped to consume
  EvaluatorProtocol directly via its factory.
- src/uipath/core/adapters/registry.py — AdapterRegistry,
  get_adapter_registry, reset_adapter_registry, the
  `uipath.governance.adapters` entry-point group, and the
  side-effect discovery on first call.
- tests/adapters/test_base.py and tests/adapters/test_registry.py.

Kept
- src/uipath/core/adapters/evaluator.py — EvaluatorProtocol is the
  one contract framework plugins still consume. Plugin factories
  accept an evaluator at create_runtime() time and wire it into
  their own callback seam.
- tests/adapters/test_evaluator.py — protocol-conformance unchanged.

Net diff: ~960 LOC removed. uipath-core 0.5.22 → 0.5.23. uv.lock files
regenerated in uipath-core, uipath-platform, and uipath (workspace
editable-path deps, so they pick up 0.5.23 immediately).

Verified: ruff clean, mypy clean (45 source files), 230 passed +
1 skipped in uipath-core's test suite. Monorepo grep for
AdapterRegistry / BaseAdapter / GovernedAgentBase / get_adapter_registry
/ reset_adapter_registry returns zero hits outside the deleted files
across .py/.toml/.md/.rst/.json.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: viswa-uipath

packages/uipath-core/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "uipath-core"
-version = "0.5.22"
+version = "0.5.23"
 description = "UiPath Core abstractions"
 readme = { file = "README.md", content-type = "text/markdown" }
 requires-python = ">=3.11"

packages/uipath-core/src/uipath/core/adapters/__init__.py

@@ -2,34 +2,19 @@
 
 This package holds only the abstract contracts — concrete adapter
 implementations live in framework-specific plugin packages (e.g.
-``uipath-langchain``, ``uipath-openai``) that target the framework they
-integrate with. Plugin packages register their concrete adapters with
-the global :class:`AdapterRegistry` via the
-``uipath.governance.adapters`` entry-point group.
+``uipath-langchain``, ``uipath-openai``). A framework plugin is the one
+that knows its own native wiring seam (callback handler list, hook
+registry, …) and installs governance there directly; uipath-core only
+defines the protocol an evaluator must satisfy.
 
 Public surface:
 
-- :class:`BaseAdapter` – abstract base every adapter inherits from.
-- :class:`GovernedAgentBase` – proxy base for governed agent wrappers.
-- :class:`EvaluatorProtocol` – structural protocol the adapter expects
-  from any policy evaluator.
-- :class:`AdapterRegistry` – ordered list of adapters that resolves
-  the first match for a given agent.
+- :class:`EvaluatorProtocol` – structural protocol the framework
+  plugin expects from any policy evaluator.
 """
 
-from .base import BaseAdapter, GovernedAgentBase
 from .evaluator import EvaluatorProtocol
-from .registry import (
-    AdapterRegistry,
-    get_adapter_registry,
-    reset_adapter_registry,
-)
 
 __all__ = [
-    "BaseAdapter",
-    "GovernedAgentBase",
     "EvaluatorProtocol",
-    "AdapterRegistry",
-    "get_adapter_registry",
-    "reset_adapter_registry",
 ]