Update platform-server to use Teams gRPC service

[rowan-stein]

User Request

Remove the filesystem graph entirely from platform-server. Teams service becomes the sole source of truth. No HybridGraphRepository, no FS storage. Remove SlackTrigger, NodeStateService, and GraphPersistController. Migrate variables to Teams RPCs. Add discover-tools endpoint.

Specification (Full FS Graph Removal)

Phase 1: Proto + Client

1. Regenerate proto — Run buf generate to get latest proto with Variables + McpToolFilter from BSR (feat(teams): add variables and MCP tool filter api#25 merged)
2. Update TeamsGrpcClient — Add Variable RPC methods: createVariable, getVariable, updateVariable, deleteVariable, listVariables, resolveVariable
3. Update TeamsGraphSource.mapMcpConfig() — Map tool_filter field to config.toolFilter

Phase 2: GraphRepository Replacement

4. Rewrite graph.repository.ts — Change abstract class: remove upsert(), upsertNodeState(), initIfNeeded(); replace get(name) with load() returning non-null PersistedGraph
5. Create teamsGraph.repository.ts — Concrete TeamsGraphRepository extends GraphRepository wrapping TeamsGraphSource.load() → PersistedGraph
6. Rewire graph-domain.module.ts — Replace HybridGraphRepository/FsGraphRepository factory with TeamsGraphRepository; remove unused imports (ConfigService, ModuleRef, TemplateRegistry from factory)

Phase 3: Consumer Updates

7. liveGraph.manager.ts — Change this.graphs.get('main') → this.graphs.load()
8. memory.service.ts — Change this.graphRepo.get('main') → this.graphRepo.load()

Phase 4: Delete FS Graph Infrastructure

9. Delete files:
   • src/graph/fsGraph.repository.ts
   • src/graph/hybridGraph.repository.ts
   • src/graph/graphSchema.validator.ts
   • src/graph/yaml.util.ts
10. Update src/graph/index.ts — Remove deleted exports, add TeamsGraphRepository

Phase 5: Remove NodeStateService

11. Delete src/graph/nodeState.service.ts
12. Update graph.controller.ts — Remove NodeStateService dependency; remove GET/PUT nodes/:nodeId/state endpoints; add POST nodes/:nodeId/discover-tools endpoint
13. Update localMcpServer.node.ts — Remove NodeStateService usage; tool discovery = in-memory only (this.toolsCache); add public discoverTools() method; enabledTools filtering uses in-memory state only
14. Update graph-api.module.ts — Remove NodeStateService from providers/exports

Phase 6: Remove GraphPersistController + Endpoints

15. Delete src/graph/controllers/graphPersist.controller.ts
16. Update graph-api.module.ts — Remove from controllers

Phase 7: Migrate GraphVariablesService to Teams RPCs

17. Rewrite graphVariables.service.ts — Replace GraphRepository dependency with TEAMS_GRPC_CLIENT; use Teams Variables RPCs for CRUD; keep PrismaService for local overrides (VariableLocal); remove name parameter from all methods
18. Update graphVariables.controller.ts — Remove 'main' args from service calls
19. Update reference-resolver.service.ts — Remove graphName parameter from resolveValue calls

Phase 8: Remove SlackTrigger

20. Delete src/nodes/slackTrigger/ directory
21. Update nodes.module.ts — Remove SlackTrigger from imports/providers/exports
22. Update templates.ts — Remove SlackTrigger registration

Phase 9: Cleanup

23. Remove FS graph config from config.service.ts — graphRepoPath, graphLockTimeoutMs
24. Remove PersistedGraphUpsertRequest/Response from graph.types.ts; remove variables from PersistedGraph
25. Delete fixtures/tools: __fixtures__/graph-migration/, tools/graph-ref-migrate/
26. Update graph.utils.ts comment referencing HybridGraphRepository if any

Phase 10: UI Changes

27. api/modules/graph.ts — Remove saveFullGraph, getFullGraph, putNodeState, getNodeState; add discoverTools(nodeId)
28. features/graph/services/api.ts — Remove fetchGraph, saveGraph, getNodeState, putNodeState
29. features/graph/hooks/useGraphData.ts — Remove graph fetching/saving that uses fetchGraph/saveGraph
30. features/graph/hooks/useNodeTitleMap.ts — Replace fetchGraph() with Teams agents list API
31. features/secrets/hooks/useSecretsData.ts — Replace getFullGraph() with Teams entity scanning (list agents, tools, mcps from Teams API, scan configs for $secret())
32. pages/AgentsThreads.tsx — Replace getFullGraph() with Teams agents list for agentOptions
33. lib/graph/hooks.ts — Remove getNodeState/putNodeState usage; replace with discoverTools for MCP tool state

Phase 11: Test Updates

Delete:

• __tests__/fsGraph.repository.yaml.test.ts
• __tests__/graph.fs.persistence.integration.test.ts
• __tests__/hybridGraph.repository.test.ts
• __tests__/nodes/slack-trigger.node.spec.ts
• __tests__/slack.config.schemas.test.ts
• __tests__/slack.pr.trigger.lifecycle.test.ts
• __tests__/slack.threading.integration.test.ts
• __tests__/slack.trigger.events.test.ts

Update test files that mock GraphRepository.get('main') → GraphRepository.load():

• All tests importing/mocking GraphRepository
• Tests referencing NodeStateService — remove mocks

Keep: __tests__/teamsGraph.source.test.ts

[rowan-stein]

Update: Remove hand-written gRPC service definitions

In addition to the Teams service integration, this issue now includes migrating all gRPC client/server wiring from hand-written ServiceDefinition objects to auto-generated code using Connect-ES.

Files to remove

• packages/platform-server/src/proto/grpc.ts (Runner hand-written service definition)
• packages/platform-server/src/proto/teams-grpc.ts (Teams hand-written service definition)
• packages/docker-runner/src/proto/grpc.ts (Runner server-side hand-written service definition)

Migration approach

• Replace @grpc/grpc-js client usage in platform-server with @connectrpc/connect + createGrpcTransport
• Use auto-generated service descriptors from protoc-gen-es v2 (already in buf.gen.yaml)
• Migrate docker-runner server from @grpc/grpc-js Server.addService() to Connect-Node router
• Zero hand-written gRPC definitions — everything generated from proto via buf generate

[rowan-stein]

Additional Requirements — UI Migration

1. Remove graph page

• Delete /agents/graph route and AgentsGraphContainer
• Remove "Open graph" toolbar button from AgentsListPage
• Remove "Team" sidebar link from RootLayout
• Delete graph canvas components, graph-page-only hooks, graph layout

2. Switch UI entity CRUD to gateway REST API

• Create new API client for /apiv2/team/v1/* endpoints
• Replace useGraphEntities() (full-graph fetch/save) with per-resource hooks calling gateway
• Entity list pages call GET /apiv2/team/v1/{resource} instead of fetching full graph
• Entity create/edit calls POST/PATCH /apiv2/team/v1/{resource}
• Relations managed via GET/POST/DELETE /apiv2/team/v1/attachments

3. Merge latest main (devspace config)

4. Triggers

Triggers have no gateway endpoint — keep trigger pages using existing platform-server API for now (triggers remain in the graph).

5. Templates

Replace TemplatesProvider + useTemplates() with a local registry mapping entity kind → form view + capabilities. The gateway entities are self-describing (no template concept needed).

[rowan-stein]

Runtime Integration: Teams Service → Graph Runtime

Problem

After removing POST /api/graph and migrating entity CRUD to the Teams service, the platform-server's LLM runtime loop still reads agent configs, tool connections, and MCP server edges from the graph filesystem (FsGraphRepository). Since the graph filesystem is no longer updated with entity data, it contains empty/stale configs causing 3 runtime bugs:

1. Threads show "(unknown agent)" — resolveAgentDescriptors() reads agent name/role from graph nodes → empty
2. System prompt falls back to default — AgentNode.setConfig() receives empty config → defaults to "You are a helpful AI assistant."
3. No tools loaded — Tools were connected via graph edges → no tool/MCP nodes or edges exist in graph anymore

Solution: Hybrid GraphRepository

Replace FsGraphRepository with a HybridGraphRepository that merges two data sources:

1. FsGraphRepository — for trigger nodes and any non-Teams nodes (remain on filesystem)
2. TeamsGraphSource (new) — fetches entities + attachments from Teams gRPC, converts them to PersistedGraph fragments (nodes + edges)

Additionally, resolveAgentDescriptors() will query the Teams service directly.

Implementation scope

• New TeamsGraphSource — fetches all Teams entities, converts to graph nodes/edges
• New HybridGraphRepository — composes FsGraphRepo + TeamsGraphSource
• DI wiring: replace GraphRepository provider in GraphDomainModule
• Fix resolveAgentDescriptors() to query Teams directly

[rowan-stein]

Phase 4b: Graph screen deletion + GraphRepository elimination

1. Delete dead graph screen UI code

These files are leftover from the old visual graph builder screen and are no longer imported by any route or page:

Components:

• components/agents/GraphLayout.tsx
• components/agents/edges/GradientEdge.tsx (+ edges/ directory if only file)
• components/GraphCanvas.tsx + __tests__/GraphCanvas.test.tsx
• components/EmptySelectionSidebar.tsx
• components/graph/ (entire directory)

Features/graph dead code:

• features/graph/__tests__/GraphLayout.integration.test.tsx
• features/graph/__tests__/GraphLayout.workspace.env.integration.test.tsx
• features/graph/hooks/useGraphData.ts + test
• features/graph/hooks/useGraphSocket.ts + test

Lib/graph dead code:

• lib/graph/sidebarNodeItems.ts + test

2. Eliminate GraphRepository abstraction

GraphRepository is an unnecessary abstraction layer — single implementation (TeamsGraphRepository), single method (load()), and consumers don't use the vestigial name/version/updatedAt fields.

Delete:

• src/graph/graph.repository.ts
• src/graph/teamsGraph.repository.ts

Refactor:

• graph-domain.module.ts — remove TeamsGraphRepository and GraphRepository binding; export TeamsGraphSource directly
• liveGraph.manager.ts — inject TeamsGraphSource directly instead of GraphRepository
• memory.service.ts — inject TeamsGraphSource directly instead of GraphRepository
• 7 test files — update mocks from GraphRepository to TeamsGraphSource

What stays

• lib/graph/templates.provider.tsx, hooks.ts, socket.ts, types.ts — actively used by entity management, threads, runs
• features/graph/types/, mappers/, services/, hooks/useNodeStatus.ts, hooks/useNodeAction.ts, hooks/useNodeTitleMap.ts — actively used
• GET /api/graph/templates endpoint — core infrastructure for template metadata