deploy github actions fix?

Author: timan-z

additional-docs/sql-observability-metrics-deep-dive.md

@@ -100,7 +100,7 @@ Nothing is implicitly auto-generated or inferred.
 SpringQueuePro tracks the **full lifecycle of task execution** using monotonic counters:
 
 - **`springqpro_tasks_submitted_total`**
-  Incremented when a task enters the system.
+  Incremented when a task is submitted for processing.
 
 - **`springqpro_tasks_claimed_total`**
   Incremented only after a task is *successfully claimed* via an atomic database transition.
@@ -148,30 +148,14 @@ This counter distinguishes:
 
 This separation becomes important in multi-client or multi-ingress systems.
 
-### Legacy & Transitional Metrics
-
-Some metrics exist for transparency during architectural evolution:
-
-- **`springqpro_queue_enqueue_total`**
-- **`springqpro_queue_enqueue_by_id_total`**
-- **`springqpro_queue_memory_size` (Gauge)**
-
-These reflect:
-
-- legacy in-memory queue paths
-- transitional execution models
-- historical debugging needs
-
-They are intentionally preserved but clearly labeled to avoid confusion.
-
 ## Worker Runtime Visibility
 
 SpringQueuePro exposes **worker runtime state** directly from the `ThreadPoolExecutor`.
 
 Rather than guessing or inferring worker behavior, the system reports:
 
 - active worker count
-- idle worker count
+- idle/queued worker count
 - in-flight task count
 
 This data is exposed via:

springqpro-backend/pom.xml

@@ -183,6 +183,9 @@
                 <version>3.2.5</version>
                 <configuration>
                     <excludedGroups>disable_temp</excludedGroups>
+                    <systemPropertyVariables>
+                        <spring.profiles.active>test</spring.profiles.active>
+                    </systemPropertyVariables>
                 </configuration>
             </plugin>
         </plugins>