Add root route (/) to proxy and registry

[vrknetha]

Problem

Hitting the base URL of proxy or registry returns confusing responses:

• Proxy (dev.proxy.clawdentity.com/) → returns PROXY_AUTH_MISSING_TOKEN error because the root falls through to auth middleware
• Registry (dev.registry.clawdentity.com/) → returns 404 (no route defined)

Both are confusing for anyone discovering the service URL. A bare GET to the root should not require auth or return cryptic errors.

Expected Behavior

Both services should return a friendly JSON response on GET / without requiring authentication:

{
  "service": "clawdentity-proxy",
  "status": "ok",
  "version": "0.x.x",
  "docs": "https://clawdentity.com/docs"
}

Implementation

• Add app.get("/", ...) route before auth middleware in both:
  • apps/proxy/src/server.ts
  • apps/registry/src/server.ts
• Keep existing /health endpoints as-is (they serve a different purpose for monitoring)
• No auth required on root route

Notes

• The /health endpoint already exists on both services and works fine
• This is purely a UX improvement for anyone hitting the base URL