- Rename Go module switchboard-core → armature (155+ files) - Rename Docker image → gobha/armature - Rename K8s resources, secrets, deployments - Rename Prometheus metrics switchboard_* → armature_* - Rename env vars SWITCHBOARD_ADMIN_* → ARMATURE_ADMIN_* - Rename DB names switchboard_core* → armature* - Update all frontend branding, notification templates, docs - Update CI scripts, e2e tests, Keycloak realm, nginx conf - Rename scripts/switchboard-ca.sh → scripts/armature-ca.sh - Rename k8s/switchboard.yaml → k8s/armature.yaml - Rename chart alerting/dashboard files - Fix: DockerHub push uses env: binding for secret injection - Helm chart updated (name, labels, template functions, dashboard, alerting) - Replace favicon/icon assets with Armature brand No functional changes. Pure mechanical rename + CI fix. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Workflow Chat Integration
Creates scoped chat conversations when workflow stages require team collaboration.
Setup
- Install the
workflow-chatandchat-corepackages. - In your workflow stage with
audience: team, setstage_config:
{
"on_advance": {
"package_id": "workflow-chat",
"entry_point": "on_advance"
}
}
- When the workflow advances to that stage, ensure
stage_dataincludes:
{
"title": "Bug Triage Discussion",
"team_members": [
{"id": "user-1", "display_name": "Alice"},
{"id": "user-2", "display_name": "Bob"}
],
"creator_id": "user-1",
"creator_display_name": "Alice"
}
The hook will:
- Create a group conversation titled
"Bug Triage Discussion [abcd1234]"(suffixed with instance ID) - Add all team members as participants
- Send a system message linking to the workflow instance
- Enrich
stage_datawith theconversation_id
Idempotency
If stage_data already contains a conversation_id, the hook returns None (no-op).