feat(#93): implement agent spawn via federation
Implements FED-010: Agent Spawn via Federation feature that enables spawning and managing Claude agents on remote federated Mosaic Stack instances via COMMAND message type. Features: - Federation agent command types (spawn, status, kill) - FederationAgentService for handling agent operations - Integration with orchestrator's agent spawner/lifecycle services - API endpoints for spawning, querying status, and killing agents - Full command routing through federation COMMAND infrastructure - Comprehensive test coverage (12/12 tests passing) Architecture: - Hub → Spoke: Spawn agents on remote instances - Command flow: FederationController → FederationAgentService → CommandService → Remote Orchestrator - Response handling: Remote orchestrator returns agent status/results - Security: Connection validation, signature verification Files created: - apps/api/src/federation/types/federation-agent.types.ts - apps/api/src/federation/federation-agent.service.ts - apps/api/src/federation/federation-agent.service.spec.ts Files modified: - apps/api/src/federation/command.service.ts (agent command routing) - apps/api/src/federation/federation.controller.ts (agent endpoints) - apps/api/src/federation/federation.module.ts (service registration) - apps/orchestrator/src/api/agents/agents.controller.ts (status endpoint) - apps/orchestrator/src/api/agents/agents.module.ts (lifecycle integration) Testing: - 12/12 tests passing for FederationAgentService - All command service tests passing - TypeScript compilation successful - Linting passed Refs #93 Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
This commit is contained in:
@@ -67,6 +67,7 @@ The search endpoint already exists with most features implemented:
|
||||
Successfully implemented tag filtering in the search API endpoint:
|
||||
|
||||
**What was already there:**
|
||||
|
||||
- Full-text search using PostgreSQL `search_vector` column (from issue #65)
|
||||
- Ranking with `ts_rank`
|
||||
- Snippet generation and highlighting with `ts_headline`
|
||||
@@ -74,6 +75,7 @@ Successfully implemented tag filtering in the search API endpoint:
|
||||
- Pagination
|
||||
|
||||
**What was added (issue #66):**
|
||||
|
||||
- Tags parameter in `SearchQueryDto` (supports comma-separated values)
|
||||
- Tag filtering in `SearchService.search()` method
|
||||
- SQL query modification to join with `knowledge_entry_tags` when tags provided
|
||||
@@ -82,6 +84,7 @@ Successfully implemented tag filtering in the search API endpoint:
|
||||
- Documentation updates
|
||||
|
||||
**Quality Metrics:**
|
||||
|
||||
- 25 tests pass (16 service + 9 controller)
|
||||
- All knowledge module tests pass (209 tests)
|
||||
- TypeScript type checking: PASS
|
||||
@@ -90,6 +93,7 @@ Successfully implemented tag filtering in the search API endpoint:
|
||||
|
||||
**Performance Note:**
|
||||
Response time < 200ms requirement will be validated during integration testing with actual database load. The implementation uses:
|
||||
|
||||
- Precomputed tsvector with GIN index (from #65)
|
||||
- Efficient subquery for tag filtering with GROUP BY
|
||||
- Result caching via KnowledgeCacheService
|
||||
|
||||
Reference in New Issue
Block a user