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>

docs/superpowers/specs/2026-03-31-append-only-execution-protocol.md

@@ -68,9 +68,9 @@ Event 2: {type: "EXECUTION_COMPLETED", executionId: "abc", duration: 250, output
 - More flexible: supports any number of state transitions (RUNNING -> PAUSED -> RUNNING -> COMPLETED)
 - Natural fit for event sourcing architectures
 
-### Option C: Hybrid (Current Cameleer3-Server Approach)
+### Option C: Hybrid (Current Cameleer-Server Approach)
 
-Keep the two-phase protocol but handle merging at the server application layer. This is what cameleer3-server implements today with the `ExecutionAccumulator`:
+Keep the two-phase protocol but handle merging at the server application layer. This is what cameleer-server implements today with the `ExecutionAccumulator`:
 
 - RUNNING POST -> hold in `ConcurrentHashMap` (no DB write)
 - COMPLETED POST -> merge with RUNNING in-memory -> single INSERT to DB