boost-backend-module-kagenti — Kagenti provider module (issue 11 of 15)

[gabemontero]

Labels: ready-to-code
Depends on: Issue 2

Create the Kagenti provider module as an independent createBackendModule with KagentiProvider, A2A protocol integration, and all provider caches using cacheService.

Tasks

From openspec/changes/pluggable-ai-platform-architecture/tasks.md sections 2 and 3:

• 2.3 Create boost-backend-module-kagenti package
• 2.4 Implement KagentiProvider and KagentiProviderFactory
• 2.5 Ensure no cross-provider imports
• 3.3 Implement agent card cache via cache.withOptions({ defaultTtl: '5m' })
• 3.4 Implement Keycloak token cache
• 3.7 Implement session maps via cacheService
• 3b.1 Define Kagenti-specific types in module only

Specifications

• openspec/changes/pluggable-ai-platform-architecture/specs/provider-packaging/spec.md — Kagenti module scenarios
• openspec/changes/pluggable-ai-platform-architecture/design.md — Decision 2 (modules not plugins), Decision 3 (cacheService)

[fullsend-ai-triage]

Triage Summary

This issue is blocked by #3298 (boost-backend — Core plugin scaffold, ProviderManager, and security middleware), which is still open.

The Kagenti provider module (boost-backend-module-kagenti) depends on the core plugin scaffold, ProviderManager, and security middleware that #3298 will deliver. Specifically, KagentiProvider and KagentiProviderFactory (tasks 2.4, 2.5) cannot be implemented until the ProviderManager abstraction exists, and the createBackendModule packaging (task 2.3) requires the core backend plugin to be scaffolded first.

Once #3298 is merged, this issue should be unblocked and ready for development.

---

Labels: This is a Kagenti/AI integration feature under the ai-integrations area, maintained by team/pai.