docs(plan): correct health endpoint path (/health, not /api/v1/healthz)

Smoke test for batch A revealed the actual endpoint is GET /health
returning {"status":"ok"}; /api/v1/healthz returns 404.

docs/superpowers/plans/2026-05-09-smartbotic-automation-debian-packaging.md

@@ -695,7 +695,7 @@ sleep 3
 - [ ] **Step 3: Hit health + auth endpoints**
 
 ```bash
-curl -s http://localhost:8090/api/v1/healthz
+curl -s http://localhost:8090/health
 TOKEN=$(curl -s http://localhost:8090/api/v1/auth/login \
   -H 'Content-Type: application/json' \
   -d '{"username":"admin","password":"admin"}' | jq -r '.accessToken')
@@ -1623,7 +1623,7 @@ Expected: both `active (running)`. If the runner exits because it can't reach th
 - [ ] **Step 1: Health + auth**
 
 ```bash
-curl -s http://localhost:8090/api/v1/healthz
+curl -s http://localhost:8090/health
 TOKEN=$(curl -s http://localhost:8090/api/v1/auth/login \
     -H 'Content-Type: application/json' \
     -d '{"username":"admin","password":"admin"}' | jq -r '.accessToken')