chore: rename cameleer3 to cameleer

Rename Java packages from com.cameleer3 to com.cameleer, module
directories from cameleer3-* to cameleer-*, and all references
throughout workflows, Dockerfiles, docs, migrations, and pom.xml.

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

.planning/research/ARCHITECTURE.md

@@ -57,7 +57,7 @@ Agents (50+)                        Users / UI
 Agent POST /api/v1/ingest
     |
     v
-[IngestController] -- validates JWT, deserializes using cameleer3-common models
+[IngestController] -- validates JWT, deserializes using cameleer-common models
     |
     v
 [IngestionService.accept(batch)] -- accepts TransactionData/ActivityData
@@ -126,7 +126,7 @@ Each registered SseEmitter sends event to connected agent
 Agent POST /api/v1/diagrams (on startup or route change)
     |
     v
-[DiagramController] -- receives route definition (XML/YAML/JSON from cameleer3-common)
+[DiagramController] -- receives route definition (XML/YAML/JSON from cameleer-common)
     |
     v
 [DiagramService.storeVersion(definition)]
@@ -341,11 +341,11 @@ public record PageCursor(Instant timestamp, String id) {}
 
 ## Module Boundary Design
 
-### Core Module (`cameleer3-server-core`)
+### Core Module (`cameleer-server-core`)
 
 The core module is the domain layer. It contains:
 
-- **Domain models** -- Transaction, Activity, Agent, DiagramVersion, etc. (may extend or complement cameleer3-common models)
+- **Domain models** -- Transaction, Activity, Agent, DiagramVersion, etc. (may extend or complement cameleer-common models)
 - **Service interfaces and implementations** -- TransactionService, AgentRegistryService, DiagramService, QueryEngine
 - **Repository interfaces** -- TransactionRepository, DiagramRepository, AgentRepository (interfaces only, no implementations)
 - **Ingestion logic** -- WriteBuffer, batch assembly, backpressure signaling
@@ -356,7 +356,7 @@ The core module is the domain layer. It contains:
 
 **No Spring Boot dependencies.** Jackson is acceptable (already present). JUnit for tests.
 
-### App Module (`cameleer3-server-app`)
+### App Module (`cameleer-server-app`)
 
 The app module is the infrastructure/adapter layer. It contains:
 
@@ -376,8 +376,8 @@ The app module is the infrastructure/adapter layer. It contains:
 ```
 app --> core (allowed)
 core --> app (NEVER)
-core --> cameleer3-common (allowed)
-app --> cameleer3-common (transitively via core)
+core --> cameleer-common (allowed)
+app --> cameleer-common (transitively via core)
 ```
 
 ## Ingestion Pipeline Detail
@@ -393,7 +393,7 @@ Use a two-stage approach:
 
 - WriteBuffer has a bounded capacity (configurable, default 50,000 items).
 - When buffer is >80% full, respond with HTTP 429 + `Retry-After` header.
-- Agents (cameleer3) should implement exponential backoff on 429.
+- Agents (cameleer) should implement exponential backoff on 429.
 - Monitor buffer fill level as a metric.
 
 ### Batch Size Tuning

.planning/research/PITFALLS.md

@@ -1,6 +1,6 @@
 # Domain Pitfalls
 
-**Domain:** Transaction monitoring / observability server (Cameleer3 Server)
+**Domain:** Transaction monitoring / observability server (Cameleer Server)
 **Researched:** 2026-03-11
 **Confidence:** MEDIUM (based on established patterns for ClickHouse, SSE, high-volume ingestion; no web verification available)
 

.planning/research/STACK.md

@@ -1,6 +1,6 @@
 # Technology Stack
 
-**Project:** Cameleer3 Server
+**Project:** Cameleer Server
 **Researched:** 2026-03-11
 **Overall confidence:** MEDIUM (no live source verification available; versions based on training data up to May 2025)
 

.planning/research/SUMMARY.md

@@ -1,4 +1,4 @@
-# Research Summary: Cameleer3 Server
+# Research Summary: Cameleer Server
 
 **Domain:** Transaction observability server for Apache Camel integrations
 **Researched:** 2026-03-11
@@ -6,7 +6,7 @@
 
 ## Executive Summary
 
-Cameleer3 Server is a write-heavy, read-occasional observability system that receives millions of transaction records per day from distributed Apache Camel agents, stores them with 30-day retention, and provides structured + full-text search. The architecture closely parallels established observability platforms like Jaeger, Zipkin, and njams Server, with the key differentiator being Camel route diagram visualization tied to individual transactions.
+Cameleer Server is a write-heavy, read-occasional observability system that receives millions of transaction records per day from distributed Apache Camel agents, stores them with 30-day retention, and provides structured + full-text search. The architecture closely parallels established observability platforms like Jaeger, Zipkin, and njams Server, with the key differentiator being Camel route diagram visualization tied to individual transactions.
 
 The recommended stack centers on **ClickHouse** as the primary data store. ClickHouse's columnar MergeTree engine provides the exact properties this project needs: massive batch insert throughput, excellent time-range query performance, native TTL-based retention, and 10-20x compression on structured observability data. This is a well-established pattern used by production observability platforms (SigNoz, Uptrace, PostHog all run on ClickHouse).
 
@@ -93,9 +93,9 @@ Based on research, suggested phase structure:
 ## Gaps to Address
 
 - **ClickHouse Java client API:** The clickhouse-java library has undergone significant changes. Exact API, connection pooling, and Spring Boot integration patterns need phase-specific research
-- **cameleer3-common PROTOCOL.md:** Must read the agent protocol definition before designing ClickHouse schema -- this defines the exact data structures being ingested
+- **cameleer-common PROTOCOL.md:** Must read the agent protocol definition before designing ClickHouse schema -- this defines the exact data structures being ingested
 - **ClickHouse Docker setup:** Optimal ClickHouse Docker configuration (memory limits, merge settings) for development and production
 - **Full-text search decision:** ClickHouse skip indexes may or may not meet the "search by any content" requirement. This needs prototyping with realistic data
-- **Diagram rendering library:** Server-side route diagram rendering is a significant unknown; needs prototyping with actual Camel route graph data from cameleer3-common
+- **Diagram rendering library:** Server-side route diagram rendering is a significant unknown; needs prototyping with actual Camel route graph data from cameleer-common
 - **Frontend framework:** No research on UI technology -- deferred to UI phase
-- **Agent protocol stability:** The cameleer3-common protocol is still evolving. Schema evolution strategy needs alignment with agent development
+- **Agent protocol stability:** The cameleer-common protocol is still evolving. Schema evolution strategy needs alignment with agent development