diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md
index f73b51b..cf5835d 100644
--- a/DEVELOPMENT.md
+++ b/DEVELOPMENT.md
@@ -478,11 +478,11 @@ kubectl logs deployment/zai-proxy -n mcp | grep -i "fallback"
 kubectl logs deployment/zai-proxy-dashboard -n mcp | grep "scrape"
 
 # Check proxy metrics endpoint
-curl http://zai-proxy.mcp.svc.cluster.local:8080/metrics
+curl http://zai-proxy.devpod.svc.cluster.local:8080/metrics
 
 # Test direct connection from dashboard pod
 kubectl exec -n mcp deployment/zai-proxy-dashboard -- \
-  wget -O- http://zai-proxy.mcp.svc.cluster.local:8080/metrics
+  wget -O- http://zai-proxy.devpod.svc.cluster.local:8080/metrics
 ```
 
 #### High Memory/CPU Usage
@@ -888,7 +888,7 @@ If Docker builds fail in devpod environments:
 - **Issues:** File in repository
 - **Questions:** Contact `jedarden@jedarden.com`
 - **Logs:** `kubectl logs -f deployment/zai-proxy -n mcp`
-- **Metrics:** `http://zai-proxy.mcp.svc.cluster.local:8080/metrics`
+- **Metrics:** `http://zai-proxy.devpod.svc.cluster.local:8080/metrics`
 
 ## Additional Resources
 
diff --git a/dashboard/README.md b/dashboard/README.md
index 122bc47..9c79c3e 100644
--- a/dashboard/README.md
+++ b/dashboard/README.md
@@ -477,7 +477,7 @@ collector initialized with targets: [http://zai-proxy:8080/metrics]
 
 **Check if proxy is reachable:**
 ```bash
-kubectl exec -n devpod deployment/zai-proxy-dashboard -- wget -O- http://zai-proxy.mcp.svc.cluster.local:8080/metrics
+kubectl exec -n devpod deployment/zai-proxy-dashboard -- wget -O- http://zai-proxy.devpod.svc.cluster.local:8080/metrics
 ```
 
 ### SSE connection drops
diff --git a/dashboard/collector/collector.go b/dashboard/collector/collector.go
index 3428724..77ad3b5 100644
--- a/dashboard/collector/collector.go
+++ b/dashboard/collector/collector.go
@@ -6,6 +6,7 @@ import (
 	"fmt"
 	"log"
 	"net/http"
+	"os"
 	"strconv"
 	"strings"
 	"sync"
diff --git a/dashboard/collector/rate_test.go b/dashboard/collector/rate_test.go
index d30189c..533e691 100644
--- a/dashboard/collector/rate_test.go
+++ b/dashboard/collector/rate_test.go
@@ -149,18 +149,6 @@ func sumValues(values []MetricValue, filter map[string]string) float64 {
 	return total
 }
 
-func matchesLabels(labels, filter map[string]string) bool {
-	if filter == nil {
-		return true
-	}
-	for k, v := range filter {
-		if labels[k] != v {
-			return false
-		}
-	}
-	return true
-}
-
 // TestDeltaComputation tests delta computation for counters.
 func TestDeltaComputation(t *testing.T) {
 	tests := []struct {
diff --git a/dashboard/config/config.go b/dashboard/config/config.go
index 3740174..4f3dbc1 100644
--- a/dashboard/config/config.go
+++ b/dashboard/config/config.go
@@ -3,7 +3,6 @@ package config
 
 import (
 	"os"
-	"strings"
 	"time"
 )
 
diff --git a/docs/notes/CANARY_PROMOTION_CHECKLIST.md b/docs/notes/CANARY_PROMOTION_CHECKLIST.md
index 8200922..ae55ef2 100644
--- a/docs/notes/CANARY_PROMOTION_CHECKLIST.md
+++ b/docs/notes/CANARY_PROMOTION_CHECKLIST.md
@@ -159,7 +159,7 @@ kubectl rollout undo deployment/zai-proxy -n mcp
 ### Token Counting
 - [ ] Token metrics are being exported
   ```bash
-  curl -s http://zai-proxy.mcp.svc.cluster.local:8080/metrics | \
+  curl -s http://zai-proxy.devpod.svc.cluster.local:8080/metrics | \
     grep zai_proxy_tokens_total | grep production
   ```
 
@@ -199,7 +199,7 @@ kubectl rollout undo deployment/zai-proxy -n mcp
 
 - [ ] Token counting is working for workers
   ```bash
-  curl -s http://zai-proxy.mcp.svc.cluster.local:8080/metrics | \
+  curl -s http://zai-proxy.devpod.svc.cluster.local:8080/metrics | \
     grep zai_proxy_tokens_total | grep production
   ```
   Expected: Incrementing counters
@@ -325,7 +325,7 @@ watch kubectl get pods -n mcp -l app=zai-proxy,variant=production
 kubectl logs -f -n mcp deployment/zai-proxy
 
 # Check metrics every minute
-watch -n 60 'curl -s http://zai-proxy.mcp.svc.cluster.local:8080/metrics | grep zai_proxy_requests_total'
+watch -n 60 'curl -s http://zai-proxy.devpod.svc.cluster.local:8080/metrics | grep zai_proxy_requests_total'
 ```
 
 ---
diff --git a/docs/notes/CANARY_PROMOTION_PROCEDURE.md b/docs/notes/CANARY_PROMOTION_PROCEDURE.md
index 1d40294..04b0ac3 100644
--- a/docs/notes/CANARY_PROMOTION_PROCEDURE.md
+++ b/docs/notes/CANARY_PROMOTION_PROCEDURE.md
@@ -160,7 +160,7 @@ kubectl get pods -n mcp -l app=zai-proxy,variant=production -w
 kubectl logs -f -n mcp deployment/zai-proxy --tail=100
 
 # Check metrics endpoint directly
-curl -s http://zai-proxy.mcp.svc.cluster.local:8080/metrics | grep zai_proxy
+curl -s http://zai-proxy.devpod.svc.cluster.local:8080/metrics | grep zai_proxy
 ```
 
 ### Step 4: Verify Workers Successfully Use New Version
@@ -195,7 +195,7 @@ kubectl logs -n mcp deployment/zai-proxy --tail=100 | grep "Token usage"
 ```bash
 # Query Prometheus for token usage by workers
 # This verifies workers are successfully using the new version
-curl -s http://zai-proxy.mcp.svc.cluster.local:8080/metrics | \
+curl -s http://zai-proxy.devpod.svc.cluster.local:8080/metrics | \
   grep zai_proxy_tokens_total | \
   grep 'variant="production"'
 ```
@@ -483,7 +483,7 @@ kubectl logs <pod-name> -n mcp
 kubectl get svc -n mcp | grep zai-proxy
 
 # Test from devpod
-curl -s http://zai-proxy.mcp.svc.cluster.local:8080/health
+curl -s http://zai-proxy.devpod.svc.cluster.local:8080/health
 
 # Check worker logs
 tail -f ~/.beads-workers/*.log
diff --git a/docs/notes/CANARY_ROLLBACK_PROCEDURE.md b/docs/notes/CANARY_ROLLBACK_PROCEDURE.md
index b067349..3f46cdd 100644
--- a/docs/notes/CANARY_ROLLBACK_PROCEDURE.md
+++ b/docs/notes/CANARY_ROLLBACK_PROCEDURE.md
@@ -163,7 +163,7 @@ kubectl get pods -n mcp -l app=zai-proxy,variant=production
 kubectl exec -n mcp deployment/zai-proxy -- curl -s http://localhost:8080/health
 
 # Verify production metrics
-curl -s http://zai-proxy.mcp.svc.cluster.local:8080/metrics | grep zai_proxy_requests_total
+curl -s http://zai-proxy.devpod.svc.cluster.local:8080/metrics | grep zai_proxy_requests_total
 ```
 
 ### Step 6: Clean Up Canary Resources
@@ -287,7 +287,7 @@ kubectl get deployment/zai-proxy -n mcp \
 kubectl exec -n mcp deployment/zai-proxy -- curl -s http://localhost:8080/health
 
 # Verify metrics are being exported
-curl -s http://zai-proxy.mcp.svc.cluster.local:8080/metrics | grep zai_proxy_requests_total
+curl -s http://zai-proxy.devpod.svc.cluster.local:8080/metrics | grep zai_proxy_requests_total
 ```
 
 ### Step 6: Document the Rollback
@@ -553,13 +553,13 @@ git push origin main
 kubectl get endpoints -n mcp | grep zai-proxy
 
 # 2. Test service from devpod
-curl -s http://zai-proxy.mcp.svc.cluster.local:8080/health
+curl -s http://zai-proxy.devpod.svc.cluster.local:8080/health
 
 # 3. Check worker configuration
 grep -r "zai-proxy" ~/.beads-workers/*.log
 
 # 4. If workers pointing to canary service, update them
-# Workers should use: http://zai-proxy.mcp.svc.cluster.local:8080
+# Workers should use: http://zai-proxy.devpod.svc.cluster.local:8080
 # NOT: http://zai-proxy-canary.mcp.svc.cluster.local:8080
 
 # 5. Restart affected workers
@@ -644,7 +644,7 @@ kubectl scale deployment/zai-proxy-test -n mcp --replicas=0 --dry-run=server
 kubectl logs -n mcp deployment/zai-proxy --tail=10
 
 # 7. Verify you can access metrics
-curl -s http://zai-proxy.mcp.svc.cluster.local:8080/metrics | head -20
+curl -s http://zai-proxy.devpod.svc.cluster.local:8080/metrics | head -20
 
 # 8. Check service endpoints
 kubectl get endpoints -n mcp zai-proxy
diff --git a/docs/notes/DASHBOARD_API_REFERENCE.md b/docs/notes/DASHBOARD_API_REFERENCE.md
index b2329dd..a5c40b1 100644
--- a/docs/notes/DASHBOARD_API_REFERENCE.md
+++ b/docs/notes/DASHBOARD_API_REFERENCE.md
@@ -80,7 +80,7 @@ No parameters required.
 {
   "scrape_interval": 5,
   "targets": [
-    "http://zai-proxy.mcp.svc.cluster.local:8080/metrics"
+    "http://zai-proxy.devpod.svc.cluster.local:8080/metrics"
   ]
 }
 ```
@@ -96,7 +96,7 @@ No parameters required.
 
 - `LISTEN_ADDR` environment variable (default: `:8080`)
 - `SCRAPE_INTERVAL` environment variable (default: `5s`)
-- `SCRAPE_TARGETS` environment variable (comma-separated URLs, default: `http://zai-proxy.mcp.svc.cluster.local:8080/metrics`)
+- `SCRAPE_TARGETS` environment variable (comma-separated URLs, default: `http://zai-proxy.devpod.svc.cluster.local:8080/metrics`)
 
 #### Example
 
diff --git a/docs/notes/DEPLOYMENT.md b/docs/notes/DEPLOYMENT.md
index 889a3ae..fa5c21c 100644
--- a/docs/notes/DEPLOYMENT.md
+++ b/docs/notes/DEPLOYMENT.md
@@ -8,7 +8,7 @@ The zai-proxy service supports **dual deployment mode** for safe testing and gra
 
 | Deployment | Service Name | Purpose | Endpoint URL |
 |------------|--------------|---------|--------------|
-| **Production** | `zai-proxy.mcp.svc.cluster.local:8080` | Live traffic | `http://zai-proxy.devpod.svc.cluster.local:8080/api/anthropic` |
+| **Production** | `zai-proxy.devpod.svc.cluster.local:8080` | Live traffic | `http://zai-proxy.devpod.svc.cluster.local:8080/api/anthropic` |
 | **Canary** | `zai-proxy-test.mcp.svc.cluster.local:8080` | Testing new versions | `http://zai-proxy-test.devpod.svc.cluster.local:8080/api/anthropic` |
 | **Split Traffic** | `zai-proxy-canary.mcp.svc.cluster.local:8080` | Weighted traffic split | `http://zai-proxy-canary.devpod.svc.cluster.local:8080/api/anthropic` |
 
@@ -119,7 +119,7 @@ cat $CLAUDE_CONFIG_DIR/settings.json | grep ANTHROPIC_BASE_URL
 
 ```bash
 # Test production endpoint
-curl -s http://zai-proxy.mcp.svc.cluster.local:8080/health
+curl -s http://zai-proxy.devpod.svc.cluster.local:8080/health
 # Expected: {"status":"ok"}
 
 # Test canary endpoint
@@ -135,7 +135,7 @@ curl -s http://zai-proxy-canary.mcp.svc.cluster.local:8080/health
 
 ```bash
 # From within a devpod, check DNS resolution
-nslookup zai-proxy.mcp.svc.cluster.local
+nslookup zai-proxy.devpod.svc.cluster.local
 nslookup zai-proxy-test.mcp.svc.cluster.local
 
 # Check service endpoints
@@ -413,7 +413,7 @@ histogram_quantile(0.95,
 
 **Issue: Workers getting connection errors**
 - Verify service is running: `kubectl get svc -n mcp | grep zai-proxy`
-- Check DNS resolution from devpod: `nslookup zai-proxy.mcp.svc.cluster.local`
+- Check DNS resolution from devpod: `nslookup zai-proxy.devpod.svc.cluster.local`
 - Verify endpoint URL in worker settings
 
 **Issue: Workers using wrong deployment**
@@ -433,9 +433,9 @@ histogram_quantile(0.95,
 | Production | `http://zai-proxy.devpod.svc.cluster.local:8080/api/anthropic` | All production traffic |
 | Canary | `http://zai-proxy-test.devpod.svc.cluster.local:8080/api/anthropic` | Testing new versions |
 | Split | `http://zai-proxy-canary.devpod.svc.cluster.local:8080/api/anthropic` | Weighted traffic splitting |
-| Metrics (Prod) | `http://zai-proxy.mcp.svc.cluster.local:8080/metrics` | Production metrics |
+| Metrics (Prod) | `http://zai-proxy.devpod.svc.cluster.local:8080/metrics` | Production metrics |
 | Metrics (Canary) | `http://zai-proxy-test.mcp.svc.cluster.local:8080/metrics` | Canary metrics |
-| Health (Prod) | `http://zai-proxy.mcp.svc.cluster.local:8080/health` | Production health check |
+| Health (Prod) | `http://zai-proxy.devpod.svc.cluster.local:8080/health` | Production health check |
 | Health (Canary) | `http://zai-proxy-test.mcp.svc.cluster.local:8080/health` | Canary health check |
 
 ## Summary
diff --git a/docs/notes/TROUBLESHOOTING.md b/docs/notes/TROUBLESHOOTING.md
index 9109c48..bda1f88 100644
--- a/docs/notes/TROUBLESHOOTING.md
+++ b/docs/notes/TROUBLESHOOTING.md
@@ -40,7 +40,7 @@ Token counting enabled (fallback mode, model: glm-4)
 
 **Command:**
 ```bash
-curl -s http://zai-proxy.mcp.svc.cluster.local:8080/metrics | grep zai_proxy_tokens_total
+curl -s http://zai-proxy.devpod.svc.cluster.local:8080/metrics | grep zai_proxy_tokens_total
 ```
 
 **Expected Output:**
@@ -483,7 +483,7 @@ If you've tried all troubleshooting steps and still have issues:
    kubectl get deployment zai-proxy -n mcp -o yaml > deployment.yaml
 
    # Metrics snapshot
-   curl -s http://zai-proxy.mcp.svc.cluster.local:8080/metrics | grep zai_proxy_token > metrics.txt
+   curl -s http://zai-proxy.devpod.svc.cluster.local:8080/metrics | grep zai_proxy_token > metrics.txt
    ```
 
 2. **Check documentation:**
@@ -518,7 +518,7 @@ kubectl logs -f -n mcp deployment/zai-proxy | grep "Token usage"
 
 **Query token metrics:**
 ```bash
-curl -s http://zai-proxy.mcp.svc.cluster.local:8080/metrics | grep zai_proxy_tokens
+curl -s http://zai-proxy.devpod.svc.cluster.local:8080/metrics | grep zai_proxy_tokens
 ```
 
 **Check latency:**
diff --git a/docs/notes/metrics.md b/docs/notes/metrics.md
index c7bd6ff..c76a64b 100644
--- a/docs/notes/metrics.md
+++ b/docs/notes/metrics.md
@@ -11,7 +11,7 @@ The zai-proxy exports comprehensive metrics for monitoring token consumption, re
 curl http://zai-proxy:8080/metrics
 
 # Query from within Kubernetes cluster
-curl http://zai-proxy.mcp.svc.cluster.local:8080/metrics
+curl http://zai-proxy.devpod.svc.cluster.local:8080/metrics
 ```
 
 ## Token Consumption Metrics
diff --git a/notes/bf-3ik4.md b/notes/bf-3ik4.md
new file mode 100644
index 0000000..1550b05
--- /dev/null
+++ b/notes/bf-3ik4.md
@@ -0,0 +1,57 @@
+# Verification Results: Namespace Fix and Deduping
+
+## Task: bf-3ik4
+
+### 1. Old Namespace References ✓ FIXED
+- **Before**: 20+ occurrences of `zai-proxy.mcp.svc.cluster.local` in documentation files
+- **After**: 0 occurrences - all replaced with `zai-proxy.devpod.svc.cluster.local`
+- **Files fixed**:
+  - dashboard/README.md
+  - DEVELOPMENT.md
+  - docs/notes/CANARY_PROMOTION_CHECKLIST.md
+  - docs/notes/CANARY_PROMOTION_PROCEDURE.md
+  - docs/notes/CANARY_ROLLBACK_PROCEDURE.md
+  - docs/notes/DASHBOARD_API_REFERENCE.md
+  - docs/notes/DEPLOYMENT.md
+  - docs/notes/metrics.md
+  - docs/notes/TROUBLESHOOTING.md
+
+### 2. DefaultConfig Definitions ✓ CORRECT DESIGN
+Found 4 `DefaultConfig()` functions across different packages - this is **NOT** duplicated parsing logic:
+- `collector.DefaultConfig()` → returns `collector.Config`
+- `storage.DefaultConfig()` → returns `storage.Config`
+- `api.DefaultConfig()` → returns `*api.Config`
+- `logger.DefaultConfig()` → returns `logger.Config`
+
+Each wraps the shared `config` package functions:
+- `config.GetScrapeTargets()` → calls `config.SplitTargets()`
+- `config.GetScrapeInterval()`
+- `config.GetScrapeTimeout()`
+- `config.GetListenAddr()`
+
+The central parsing logic in `dashboard/config/config.go` is defined **once** - correct design.
+
+### 3. Dashboard Go Tests ✓ PASSED
+All rate computation tests pass:
+- TestRateComputation_FirstScrape
+- TestRateComputation_NormalDelta
+- TestRateComputation_CounterReset
+- TestRateComputation_ZeroElapsed
+- TestRateComputation_NegativeElapsed
+- TestRateComputation_WithLabelFilter
+- TestRateComputation_MissingMetric
+
+### 4. Comma-Splitting ✓ VERIFIED
+Manual tests confirm `config.SplitTargets()` works correctly:
+- `"a,b,c"` → `[a b c]`
+- `"a,,b"` → `[a b]` (skips empty strings)
+- `",a,"` → `[a]`
+- `""` → `[]`
+- URL lists work correctly
+
+## Summary
+All verification criteria met:
+1. ✓ No `zai-proxy.mcp.svc.cluster.local` references remain
+2. ✓ Default parsing logic defined once in `config` package
+3. ✓ Dashboard Go tests pass
+4. ✓ Comma-splitting verified working correctly