chore: rename cameleer3 to cameleer

Rename Java packages from net.siegeln.cameleer3 to net.siegeln.cameleer,
update all references in workflows, Docker configs, docs, and bootstrap.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

docs/superpowers/specs/2026-04-04-phase-4-observability-pipeline.md

@@ -7,18 +7,18 @@
 
 ## Context
 
-Phase 3 delivered the managed Camel runtime: customers upload a JAR, the platform builds a container with the cameleer3 agent injected, and deploys it. The agent connects to cameleer3-server and sends traces, metrics, diagrams, and logs to ClickHouse. But there is no way for the user to see this data yet, and customer apps that expose HTTP endpoints are not reachable.
+Phase 3 delivered the managed Camel runtime: customers upload a JAR, the platform builds a container with the cameleer agent injected, and deploys it. The agent connects to cameleer-server and sends traces, metrics, diagrams, and logs to ClickHouse. But there is no way for the user to see this data yet, and customer apps that expose HTTP endpoints are not reachable.
 
 Phase 4 completes the loop: deploy an app, hit its endpoint, see the traces in the dashboard.
 
-cameleer3-server already has the complete observability stack — ClickHouse schemas with `tenant_id` partitioning, full search/stats/diagram/log REST APIs, and a React SPA dashboard. Phase 4 is a **wiring phase**, not a build-from-scratch phase.
+cameleer-server already has the complete observability stack — ClickHouse schemas with `tenant_id` partitioning, full search/stats/diagram/log REST APIs, and a React SPA dashboard. Phase 4 is a **wiring phase**, not a build-from-scratch phase.
 
 ## Key Decisions
 
 | Decision | Choice | Rationale |
 |----------|--------|-----------|
-| Observability UI | Serve existing cameleer3-server React SPA via Traefik | Already built. SaaS management UI is Phase 9 — observability UI is not SaaS-specific. |
-| API access | Traefik routes directly to cameleer3-server with forward-auth | No proxy layer needed. Forward-auth validates user, injects headers. Server API works as-is. |
+| Observability UI | Serve existing cameleer-server React SPA via Traefik | Already built. SaaS management UI is Phase 9 — observability UI is not SaaS-specific. |
+| API access | Traefik routes directly to cameleer-server with forward-auth | No proxy layer needed. Forward-auth validates user, injects headers. Server API works as-is. |
 | Server changes | None | Single-tenant Docker mode works out of the box. `CAMELEER_TENANT_ID` env var already supported. |
 | Agent changes | None | Agent already sends `applicationId`, `environmentId`, connects to `CAMELEER_EXPORT_ENDPOINT`. |
 | Tenant ID | Set `CAMELEER_TENANT_ID` to tenant slug in Docker Compose | Tags ClickHouse data with the real tenant identity from day one. Avoids `'default'` → real-id migration later. |
@@ -27,16 +27,16 @@ cameleer3-server already has the complete observability stack — ClickHouse sch
 ## What's Already Working (Phase 3)
 
 - Customer containers on the `cameleer` bridge network
-- Agent configured: `CAMELEER_AUTH_TOKEN`, `CAMELEER_EXPORT_ENDPOINT=http://cameleer3-server:8081`, `CAMELEER_APPLICATION_ID`, `CAMELEER_ENVIRONMENT_ID`
-- cameleer3-server writes traces/metrics/diagrams/logs to ClickHouse
-- Traefik routes `/observe/*` to cameleer3-server with forward-auth middleware
+- Agent configured: `CAMELEER_AUTH_TOKEN`, `CAMELEER_EXPORT_ENDPOINT=http://cameleer-server:8081`, `CAMELEER_APPLICATION_ID`, `CAMELEER_ENVIRONMENT_ID`
+- cameleer-server writes traces/metrics/diagrams/logs to ClickHouse
+- Traefik routes `/observe/*` to cameleer-server with forward-auth middleware
 - Forward-auth endpoint at `/auth/verify` validates JWT, returns `X-Tenant-Id`, `X-User-Id`, `X-User-Email` headers
 
-## Component 1: Serve cameleer3-server Dashboard
+## Component 1: Serve cameleer-server Dashboard
 
 ### Traefik Routing
 
-Add Traefik labels to the cameleer3-server service in `docker-compose.yml` to serve the React SPA:
+Add Traefik labels to the cameleer-server service in `docker-compose.yml` to serve the React SPA:
 
 ```yaml
 # Existing (Phase 3):
@@ -49,23 +49,23 @@ Add Traefik labels to the cameleer3-server service in `docker-compose.yml` to se
 - traefik.http.services.dashboard.loadbalancer.server.port=8080
 ```
 
-The cameleer3-server SPA is served from its own embedded web server. The SPA already calls the server's API endpoints at relative paths — the existing `/observe/*` Traefik route handles those requests with forward-auth.
+The cameleer-server SPA is served from its own embedded web server. The SPA already calls the server's API endpoints at relative paths — the existing `/observe/*` Traefik route handles those requests with forward-auth.
 
-**Note:** If the cameleer3-server SPA expects to be served from `/` rather than `/dashboard`, a Traefik StripPrefix middleware may be needed:
+**Note:** If the cameleer-server SPA expects to be served from `/` rather than `/dashboard`, a Traefik StripPrefix middleware may be needed:
 
 ```yaml
 - traefik.http.middlewares.dashboard-strip.stripprefix.prefixes=/dashboard
 - traefik.http.routers.dashboard.middlewares=forward-auth,dashboard-strip
 ```
 
-This depends on how the cameleer3-server SPA is configured (base path). To be verified during implementation.
+This depends on how the cameleer-server SPA is configured (base path). To be verified during implementation.
 
 ### CAMELEER_TENANT_ID Configuration
 
-Set `CAMELEER_TENANT_ID` on the cameleer3-server service so all ingested data is tagged with the real tenant slug:
+Set `CAMELEER_TENANT_ID` on the cameleer-server service so all ingested data is tagged with the real tenant slug:
 
 ```yaml
-cameleer3-server:
+cameleer-server:
   environment:
     CAMELEER_TENANT_ID: ${CAMELEER_TENANT_SLUG:-default}
 ```
@@ -76,7 +76,7 @@ Add `CAMELEER_TENANT_SLUG` to `.env.example`.
 
 ## Component 2: Agent Connectivity Verification
 
-New endpoint in cameleer-saas to check whether a deployed app's agent has successfully registered with cameleer3-server and is sending data.
+New endpoint in cameleer-saas to check whether a deployed app's agent has successfully registered with cameleer-server and is sending data.
 
 ### API
 
@@ -100,15 +100,15 @@ public record AgentStatusResponse(
 
 ### Implementation
 
-`AgentStatusService` in cameleer-saas calls cameleer3-server's agent registry API:
+`AgentStatusService` in cameleer-saas calls cameleer-server's agent registry API:
 
 ```
-GET http://cameleer3-server:8081/api/v1/agents
+GET http://cameleer-server:8081/api/v1/agents
 ```
 
 This returns the list of registered agents. The service filters by `applicationId` matching the app's slug and `environmentId` matching the environment's slug.
 
-If the cameleer3-server doesn't expose a public agent listing endpoint, the alternative is to query ClickHouse directly for recent data:
+If the cameleer-server doesn't expose a public agent listing endpoint, the alternative is to query ClickHouse directly for recent data:
 
 ```sql
 SELECT max(timestamp) as last_seen
@@ -212,17 +212,17 @@ cameleer:
 
 ### Startup Verification
 
-On application startup, cameleer-saas verifies that cameleer3-server is reachable:
+On application startup, cameleer-saas verifies that cameleer-server is reachable:
 
 ```java
 @EventListener(ApplicationReadyEvent.class)
 public void verifyConnectivity() {
-    // HTTP GET http://cameleer3-server:8081/actuator/health
-    // Log result: "cameleer3-server connectivity: OK" or "FAILED: ..."
+    // HTTP GET http://cameleer-server:8081/actuator/health
+    // Log result: "cameleer-server connectivity: OK" or "FAILED: ..."
 }
 ```
 
-This is a best-effort check, not a hard dependency. If cameleer3-server is not yet running (e.g., starting up), the SaaS platform still starts. The check is logged for diagnostics.
+This is a best-effort check, not a hard dependency. If cameleer-server is not yet running (e.g., starting up), the SaaS platform still starts. The check is logged for diagnostics.
 
 ### ClickHouse Data Verification
 
@@ -259,10 +259,10 @@ This requires cameleer-saas to query ClickHouse directly (the `clickHouseDataSou
 
 ## Docker Compose Changes
 
-### cameleer3-server labels (add dashboard route)
+### cameleer-server labels (add dashboard route)
 
 ```yaml
-cameleer3-server:
+cameleer-server:
   environment:
     CAMELEER_TENANT_ID: ${CAMELEER_TENANT_SLUG:-default}
   labels:
@@ -304,18 +304,18 @@ cameleer:
 1. Deploy a sample Camel REST app with `exposedPort: 8080`
 2. `curl http://order-svc.default.acme.localhost` hits the Camel app
 3. The Camel route processes the request
-4. cameleer3 agent captures the trace and sends to cameleer3-server
+4. cameleer agent captures the trace and sends to cameleer-server
 5. `GET /api/apps/{appId}/agent-status` shows `registered: true, state: ACTIVE`
 6. `GET /api/apps/{appId}/observability-status` shows `hasTraces: true`
-7. Open `http://localhost/dashboard` — cameleer3-server SPA loads
+7. Open `http://localhost/dashboard` — cameleer-server SPA loads
 8. Traces visible in the dashboard for the deployed app
 9. Route topology graph shows the Camel route structure
 10. `CAMELEER_TENANT_ID` is set to the tenant slug in ClickHouse data
 
 ## What Phase 4 Does NOT Touch
 
-- No changes to cameleer3-server code (works as-is for single-tenant Docker mode)
-- No changes to the cameleer3 agent
-- No new ClickHouse schemas (cameleer3-server manages its own)
+- No changes to cameleer-server code (works as-is for single-tenant Docker mode)
+- No changes to the cameleer agent
+- No new ClickHouse schemas (cameleer-server manages its own)
 - No SaaS management UI (Phase 9)
 - No K8s-specific changes (Phase 5)