rebrand: Switchboard Core → Armature

- 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>
2026-03-31 21:39:58 +00:00
parent fb5284f667
commit f0dd43144e
287 changed files with 898 additions and 975 deletions
--- a/docs/ARCHITECTURE.md
+++ b/docs/ARCHITECTURE.md
@@ -1,6 +1,6 @@
-# Switchboard Core — Architecture
+# Armature — Architecture

-Switchboard Core is a self-hosted extension platform. It provides identity,
+Armature is a self-hosted extension platform. It provides identity,
 teams, permissions, storage, workflows, notifications, and a package system.
 Everything else — chat, AI providers, personas, knowledge bases, notes,
 tools — ships as installable extensions.
@@ -284,7 +284,7 @@ Single Docker image: Go binary + migrations + frontend assets + vendor
 libs. Kubernetes deployment with 3-node PG cluster. CI via Gitea Actions
 with DaemonSet DinD runners testing both PG and SQLite pipelines.

-Registry: `registry.gobha.me:5000/xcaliber/switchboard-core`
+Registry: `registry.gobha.me:5000/xcaliber/armature`
 Namespace: `gobha-ai-chat`

 ### Cluster Topology
--- a/docs/DEMO-WORKFLOWS.md
+++ b/docs/DEMO-WORKFLOWS.md
@@ -280,7 +280,7 @@ def on_fire(ctx):

    resp = http.post(url, body=payload, headers={
        "Content-Type": "application/json",
-        "X-Switchboard-Event": data.get("event_name", "workflow.notify")
+        "X-Armature-Event": data.get("event_name", "workflow.notify")
    })

    # Log the delivery
--- a/docs/DEPLOYMENT.md
+++ b/docs/DEPLOYMENT.md
@@ -3,14 +3,14 @@
 ## Docker Single-Instance

 ```bash
-docker pull ghcr.io/switchboard-core/switchboard-core:latest
+docker pull ghcr.io/armature/armature:latest
 docker run -p 8080:80 \
-  -e SWITCHBOARD_ADMIN_USERNAME=admin \
-  -e SWITCHBOARD_ADMIN_PASSWORD=changeme \
+  -e ARMATURE_ADMIN_USERNAME=admin \
+  -e ARMATURE_ADMIN_PASSWORD=changeme \
  -e JWT_SECRET="$(openssl rand -hex 32)" \
  -e ENCRYPTION_KEY="$(openssl rand -hex 32)" \
-  -v switchboard-data:/data \
-  ghcr.io/switchboard-core/switchboard-core:latest
+  -v armature-data:/data \
+  ghcr.io/armature/armature:latest
 ```

 This runs with SQLite and PVC storage. Suitable for evaluation and small teams.
@@ -22,22 +22,22 @@ services:
  postgres:
    image: postgres:16
    environment:
-      POSTGRES_DB: switchboard
-      POSTGRES_USER: switchboard
+      POSTGRES_DB: armature
+      POSTGRES_USER: armature
      POSTGRES_PASSWORD: secretpassword
    volumes:
      - pg_data:/var/lib/postgresql/data

-  switchboard:
-    image: ghcr.io/switchboard-core/switchboard-core:latest
+  armature:
+    image: ghcr.io/armature/armature:latest
    ports:
      - "8080:80"
    environment:
-      DATABASE_URL: "postgres://switchboard:secretpassword@postgres:5432/switchboard?sslmode=disable"
+      DATABASE_URL: "postgres://armature:secretpassword@postgres:5432/armature?sslmode=disable"
      JWT_SECRET: "change-me-in-production"
      ENCRYPTION_KEY: "change-me-in-production"
-      SWITCHBOARD_ADMIN_USERNAME: admin
-      SWITCHBOARD_ADMIN_PASSWORD: changeme
+      ARMATURE_ADMIN_USERNAME: admin
+      ARMATURE_ADMIN_PASSWORD: changeme
      STORAGE_BACKEND: pvc
      STORAGE_PATH: /data/storage
    volumes:
@@ -58,7 +58,7 @@ See the `k8s/` directory for example manifests. Key considerations:
 - Liveness probe: `/healthz/live`. Readiness probe: `/healthz/ready`.
 - Mount a PVC at `/data/storage` or configure S3.
 - Store `JWT_SECRET` and `ENCRYPTION_KEY` in Kubernetes Secrets.
- Registry: `registry.gobha.me:5000/xcaliber/switchboard-core`.
+- Registry: `registry.gobha.me:5000/xcaliber/armature`.

 ## Environment Variables

@@ -72,15 +72,15 @@ See the `k8s/` directory for example manifests. Key considerations:
 | `AUTH_MODE` | `builtin` | `builtin`, `mtls`, `oidc` |
 | `STORAGE_BACKEND` | auto | `pvc` or `s3` |
 | `STORAGE_PATH` | `/data/storage` | PVC mount point |
-| `BASE_PATH` | | URL prefix (e.g., `/switchboard`) |
+| `BASE_PATH` | | URL prefix (e.g., `/armature`) |
 | `LOG_FORMAT` | `text` | `text` or `json` |
 | `LOG_LEVEL` | `info` | `debug`, `info`, `warn`, `error` |
 | `CORS_ALLOWED_ORIGINS` | | Comma-separated allowed origins |
 | `BUNDLED_PACKAGES` | (empty) | `""` defaults, `"*"` all, or comma-separated |
 | `SKIP_BUNDLED_PACKAGES` | `false` | Disable bundled package install |
 | `BUNDLED_PACKAGES_DIR` | `/app/bundled-packages` | Custom bundle directory |
-| `SWITCHBOARD_ADMIN_USERNAME` | | Bootstrap admin username |
-| `SWITCHBOARD_ADMIN_PASSWORD` | | Bootstrap admin password |
+| `ARMATURE_ADMIN_USERNAME` | | Bootstrap admin username |
+| `ARMATURE_ADMIN_PASSWORD` | | Bootstrap admin password |
 | `SEED_USERS` | | Dev seed users (ignored in production) |

 ### S3 Storage Variables
@@ -107,14 +107,14 @@ See the `k8s/` directory for example manifests. Key considerations:
 **PostgreSQL** (recommended for production):

 ```bash
-DATABASE_URL="postgres://user:pass@host:5432/switchboard?sslmode=require"
+DATABASE_URL="postgres://user:pass@host:5432/armature?sslmode=require"
 ```

 **SQLite** (dev, test, edge deployments):

 ```bash
 DB_DRIVER=sqlite
-DATABASE_URL=/data/switchboard.db
+DATABASE_URL=/data/armature.db
 ```

 Both databases are first-class -- every query compiles and passes tests on both. The driver is auto-detected from `DATABASE_URL` if `DB_DRIVER` is not set.
--- a/docs/DESIGN-cluster-registry.md
+++ b/docs/DESIGN-cluster-registry.md
@@ -9,7 +9,7 @@

 ## Problem

-Switchboard-core is tightly coupled to PostgreSQL. Scaling horizontally requires instance coordination: peer discovery, health monitoring, ephemeral event routing, and (optionally) leader election. Traditional HA solutions (Raft, etcd, Consul) introduce a second consensus layer on top of PG — doubling operational complexity for a system that already has serializable transactions and LISTEN/NOTIFY.
+Armature-core is tightly coupled to PostgreSQL. Scaling horizontally requires instance coordination: peer discovery, health monitoring, ephemeral event routing, and (optionally) leader election. Traditional HA solutions (Raft, etcd, Consul) introduce a second consensus layer on top of PG — doubling operational complexity for a system that already has serializable transactions and LISTEN/NOTIFY.

 ## Principle

@@ -241,7 +241,7 @@ Pre-MVP: fold `CREATE UNLOGGED TABLE` into existing schema initialization. No ne

 ### Single-Node Behavior

-When only one node is registered, the system behaves identically to pre-cluster switchboard-core. The registry has one row. LISTEN/NOTIFY delivers events back to the same instance. No special-casing required.
+When only one node is registered, the system behaves identically to pre-cluster armature. The registry has one row. LISTEN/NOTIFY delivers events back to the same instance. No special-casing required.

 ### Health Endpoint Integration

--- a/docs/DESIGN-native-mtls.md
+++ b/docs/DESIGN-native-mtls.md
@@ -172,17 +172,17 @@ their own `node-N.key`.

 ### Cert Provisioning Tooling

-A shell script (`scripts/switchboard-ca.sh`) wrapping `openssl` is the
+A shell script (`scripts/armature-ca.sh`) wrapping `openssl` is the
 KISS path. No new binary, no new dependency. Three commands:

 ```
-switchboard-ca init
+armature-ca init
    → generates cluster-ca.crt + cluster-ca.key in ./ca/

-switchboard-ca issue-node --name node-1 --san "node-1.internal,10.0.0.1"
+armature-ca issue-node --name node-1 --san "node-1.internal,10.0.0.1"
    → generates node-1.crt + node-1.key in ./nodes/

-switchboard-ca issue-user --cn jeff [--email jeff@example.com]
+armature-ca issue-user --cn jeff [--email jeff@example.com]
    → generates jeff.crt + jeff.key in ./users/
 ```

@@ -280,7 +280,7 @@ The new code is:
 | `server/auth/mtls_helpers.go` | Shared: `ParseDN`, `FingerprintCert`, `resolveOrProvision` |
 | `server/auth/mtls_native_test.go` | Unit + integration tests |
 | `server/config/tls.go` | `TLSConfig` struct, loader, validation |
-| `scripts/switchboard-ca.sh` | Cert provisioning wrapper |
+| `scripts/armature-ca.sh` | Cert provisioning wrapper |

 `server/auth/mtls.go` (existing) is renamed to `mtls_proxy.go` for
 clarity. No behavioral changes to the proxy provider.
--- a/docs/DISTRIBUTION.md
+++ b/docs/DISTRIBUTION.md
@@ -3,11 +3,11 @@
 ## Quick Start

 ```bash
-docker pull ghcr.io/switchboard-core/switchboard-core:latest
+docker pull ghcr.io/armature/armature:latest
 docker run -p 8080:80 \
-  -e SWITCHBOARD_ADMIN_USERNAME=admin \
-  -e SWITCHBOARD_ADMIN_PASSWORD=changeme \
-  ghcr.io/switchboard-core/switchboard-core:latest
+  -e ARMATURE_ADMIN_USERNAME=admin \
+  -e ARMATURE_ADMIN_PASSWORD=changeme \
+  ghcr.io/armature/armature:latest
 ```

 On first run, bundled packages are automatically installed — workflows, surfaces, and extensions are ready to use immediately.
@@ -66,12 +66,12 @@ Set `BUNDLED_PACKAGES` to control which packages are installed:
 # Install ALL packages (everything in the image)
 docker run -p 8080:80 \
  -e BUNDLED_PACKAGES="*" \
-  ghcr.io/switchboard-core/switchboard-core:latest
+  ghcr.io/armature/armature:latest

 # Install specific packages only
 docker run -p 8080:80 \
  -e BUNDLED_PACKAGES="notes,tasks,schedules" \
-  ghcr.io/switchboard-core/switchboard-core:latest
+  ghcr.io/armature/armature:latest
 ```

 Empty (default) installs the curated default set. Use `*` to install all packages. This is useful for Helm charts where different environments need different packages.
@@ -83,7 +83,7 @@ Set `SKIP_BUNDLED_PACKAGES=true` to prevent bundled packages from being installe
 ```bash
 docker run -p 8080:80 \
  -e SKIP_BUNDLED_PACKAGES=true \
-  ghcr.io/switchboard-core/switchboard-core:latest
+  ghcr.io/armature/armature:latest
 ```

 ### Custom Bundle Directory
@@ -94,7 +94,7 @@ Override the default bundled packages location with `BUNDLED_PACKAGES_DIR`:
 docker run -p 8080:80 \
  -e BUNDLED_PACKAGES_DIR=/custom/packages \
  -v /host/packages:/custom/packages \
-  ghcr.io/switchboard-core/switchboard-core:latest
+  ghcr.io/armature/armature:latest
 ```

 ## Builder Image
@@ -102,7 +102,7 @@ docker run -p 8080:80 \
 The builder image pre-caches Go modules and Node dependencies for faster custom builds.

 ```bash
-docker pull ghcr.io/switchboard-core/builder:latest
+docker pull ghcr.io/armature/builder:latest
 ```

 ### What It Caches
@@ -117,16 +117,16 @@ docker pull ghcr.io/switchboard-core/builder:latest
 Reference the builder image as a base stage in your Dockerfile:

 ```dockerfile
-FROM ghcr.io/switchboard-core/builder:latest AS builder
+FROM ghcr.io/armature/builder:latest AS builder
 WORKDIR /app
 COPY server/ .
-RUN go build -ldflags="-s -w" -o /bin/switchboard .
+RUN go build -ldflags="-s -w" -o /bin/armature .
 ```

 ### Building Locally

 ```bash
-docker build -f Dockerfile.builder -t switchboard-builder .
+docker build -f Dockerfile.builder -t armature-builder .
 ```

 ## Custom Build Guide
@@ -135,7 +135,7 @@ docker build -f Dockerfile.builder -t switchboard-builder .

 1. Create your package in `packages/your-package/` with a `manifest.json`
 2. Build all packages: `cd packages && bash build.sh all`
-3. Build the Docker image: `docker build -t my-switchboard .`
+3. Build the Docker image: `docker build -t my-armature .`

 The Dockerfile automatically builds all packages in the `packages/` directory and bundles them into the production image.

@@ -148,14 +148,14 @@ To exclude specific packages from the bundle, either:
 ### Forking for Custom Builds

 ```bash
-git clone https://github.com/switchboard-core/switchboard-core.git
-cd switchboard-core
+git clone https://github.com/armature/armature.git
+cd armature

 # Add/modify packages
 cp -r my-extension packages/my-extension/

 # Build with builder image for faster compilation
-docker build -t my-switchboard .
+docker build -t my-armature .
 ```

 ## Production Deployment
@@ -172,7 +172,7 @@ docker build -t my-switchboard .
 | `AUTH_MODE` | `builtin` | `builtin`, `mtls`, or `oidc` |
 | `STORAGE_BACKEND` | (auto) | `pvc` or `s3` |
 | `STORAGE_PATH` | `/data/storage` | PVC mount point |
-| `BASE_PATH` | | URL prefix (e.g. `/switchboard`) |
+| `BASE_PATH` | | URL prefix (e.g. `/armature`) |
 | `SKIP_BUNDLED_PACKAGES` | `false` | Disable auto-install of bundled packages |
 | `BUNDLED_PACKAGES` | (empty = defaults) | `""` curated defaults, `"*"` all, or comma-separated IDs |
 | `BUNDLED_PACKAGES_DIR` | `/app/bundled-packages` | Override bundled packages location |
@@ -186,16 +186,16 @@ PostgreSQL is recommended for production. SQLite is suitable for single-instance
 ```bash
 # PostgreSQL (recommended)
 docker run -p 8080:80 \
-  -e DATABASE_URL="postgres://user:pass@host:5432/switchboard?sslmode=require" \
+  -e DATABASE_URL="postgres://user:pass@host:5432/armature?sslmode=require" \
  -e JWT_SECRET="$(openssl rand -hex 32)" \
  -e ENCRYPTION_KEY="$(openssl rand -hex 32)" \
-  ghcr.io/switchboard-core/switchboard-core:latest
+  ghcr.io/armature/armature:latest

 # SQLite (evaluation only)
 docker run -p 8080:80 \
  -e DB_DRIVER=sqlite \
-  -v switchboard-data:/data \
-  ghcr.io/switchboard-core/switchboard-core:latest
+  -v armature-data:/data \
+  ghcr.io/armature/armature:latest
 ```

 ### Storage
@@ -204,12 +204,12 @@ Object storage is required for file uploads and package asset extraction.

 ```bash
 # PVC (auto-detected if path is writable)
-docker run -v switchboard-storage:/data/storage ...
+docker run -v armature-storage:/data/storage ...

 # S3-compatible (MinIO, AWS S3, Ceph)
 docker run \
  -e STORAGE_BACKEND=s3 \
-  -e S3_BUCKET=switchboard \
+  -e S3_BUCKET=armature \
  -e S3_ENDPOINT=https://minio.corp:9000 \
  -e S3_ACCESS_KEY=... \
  -e S3_SECRET_KEY=... \
--- a/docs/GETTING-STARTED.md
+++ b/docs/GETTING-STARTED.md
@@ -20,10 +20,10 @@ docker compose down -v

 ## First Boot

-On first start, Switchboard Core will:
+On first start, Armature will:

 1. Run database migrations (SQLite by default in compose).
-2. Create the admin user from `SWITCHBOARD_ADMIN_USERNAME` / `SWITCHBOARD_ADMIN_PASSWORD` env vars.
+2. Create the admin user from `ARMATURE_ADMIN_USERNAME` / `ARMATURE_ADMIN_PASSWORD` env vars.
 3. Auto-install the curated default package set (notes, chat-core, dashboard, workflow demos, etc.).

 No manual setup steps are required.
@@ -67,8 +67,8 @@ You can also upload `.pkg` archives through the Admin > Packages page.
 | `AUTH_MODE` | `builtin` | `builtin`, `mtls`, or `oidc` |
 | `STORAGE_BACKEND` | auto | `pvc` or `s3` |
 | `STORAGE_PATH` | `/data/storage` | PVC mount point |
-| `SWITCHBOARD_ADMIN_USERNAME` | | Bootstrap admin username |
-| `SWITCHBOARD_ADMIN_PASSWORD` | | Bootstrap admin password |
+| `ARMATURE_ADMIN_USERNAME` | | Bootstrap admin username |
+| `ARMATURE_ADMIN_PASSWORD` | | Bootstrap admin password |
 | `BUNDLED_PACKAGES` | (empty) | `""` = curated defaults, `"*"` = all, or comma-separated IDs |
 | `SKIP_BUNDLED_PACKAGES` | `false` | Disable auto-install entirely |
 | `LOG_LEVEL` | `info` | `debug`, `info`, `warn`, `error` |
@@ -77,7 +77,7 @@ You can also upload `.pkg` archives through the Admin > Packages page.
 ## From Source

 ```bash
-git clone <repo-url> && cd switchboard-core
+git clone <repo-url> && cd armature
 cp server/.env.example server/.env   # edit DB credentials
 cd server && go run .
 # Backend on http://localhost:8080
--- a/docs/PACKAGE-FORMAT.md
+++ b/docs/PACKAGE-FORMAT.md
@@ -1,6 +1,6 @@
 # Package Format

-Switchboard packages are distributed as `.pkg` files -- ZIP archives with a standard internal structure.
+Armature packages are distributed as `.pkg` files -- ZIP archives with a standard internal structure.

 ## ZIP Structure

@@ -125,6 +125,6 @@ To bundle custom packages into a Docker image:

 1. Place your package in `packages/your-package/` with a `manifest.json`.
 2. Run `cd packages && bash build.sh all`.
-3. Build the image: `docker build -t my-switchboard .`
+3. Build the image: `docker build -t my-armature .`

 The Dockerfile builds all packages and copies them into the bundled packages directory.
--- a/docs/PACKAGE-REGISTRY.md
+++ b/docs/PACKAGE-REGISTRY.md
@@ -15,7 +15,7 @@ The registry is a static JSON file matching the `RegistryResponse` struct:
      "title": "Notes",
      "version": "0.8.0",
      "description": "Markdown notes with backlinks and graph view",
-      "author": "switchboard",
+      "author": "armature",
      "type": "extension",
      "tier": "core",
      "download_url": "https://cdn.example.com/pkg/notes.pkg",
--- a/docs/TUTORIAL-FIRST-EXTENSION.md
+++ b/docs/TUTORIAL-FIRST-EXTENSION.md
@@ -1,9 +1,9 @@
 # Build Your First Browser Extension

 This tutorial walks through building a browser extension that renders custom
-code blocks, modeled on the CSV Table Viewer that ships with Switchboard.
+code blocks, modeled on the CSV Table Viewer that ships with Armature.

-**Prerequisites:** A running Switchboard instance, a text editor, and `zip`.
+**Prerequisites:** A running Armature instance, a text editor, and `zip`.

 ## Step 1: Create the Directory