stt/classic-models-agent-assistant
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: consult Approvisionnement

Browse Source 
One entry in the registry and a realm grant, which was the claim the design made
about adding a specialist. Nothing in the graph changed.

What the two specialists have in common, from the orchestrator's side, is
nothing: one is PydanticAI over MCP, the other n8n workflows behind an adapter.
It cannot tell them apart, which is what the protocol is for.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Stéphane Tailland
2026-08-29 13:26:54 +02:00
parent ebf864f7ba
commit 3c44cc63ea
4 changed files with 22 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
k8s/deployment.yaml
+1 -1
View File
@@ -28,7 +28,7 @@ spec:
# gitea's own registry: the image sits beside the source it was built
# from and inherits the repo's public visibility, so the pull needs no
# credentials at all.
image: gitea.sttlab.eu/stt/classic-models-agent-assistant:v0.1.0
image: gitea.sttlab.eu/stt/classic-models-agent-assistant:v0.2.0
ports:
- name: http
containerPort: 8080