Luis Mendes
3f5ca4e869
feat(plugin): register spec-defined extension points in PluginManager
...
CI / benchmark-publish (pull_request) Has been skipped
CI / build (pull_request) Successful in 20s
CI / helm (pull_request) Successful in 22s
CI / lint (pull_request) Failing after 27s
CI / security (pull_request) Failing after 41s
CI / quality (pull_request) Successful in 3m41s
CI / typecheck (pull_request) Successful in 3m56s
CI / coverage (pull_request) Has been skipped
CI / benchmark-regression (pull_request) Has been skipped
CI / unit_tests (pull_request) Successful in 4m1s
CI / integration_tests (pull_request) Failing after 4m2s
CI / docker (pull_request) Has been skipped
CI / e2e_tests (pull_request) Successful in 20m59s
CI / status-check (pull_request) Failing after 1s
Registered all 30 spec-defined extension points in the ExtensionPointRegistry
with typed Protocol interfaces for each category: context strategies (12),
output renderers (3), validation runners (2), tool providers (2),
skill providers (2), resource handlers (2), A2A transports (2),
event handlers (2), config sources (2), and safety guardrails (1).
Added extension_protocols.py with Protocol definitions and
extension_catalog.py with the registration catalog. Wired context
subsystem to query context.* extension points at initialization.
ISSUES CLOSED : #939
2026-03-31 03:58:43 +00:00