[rahulcrl]

Summary

• Config errors now print a single readable line to stderr with a README link instead of a JSON zap log with full stack traces
• Runtime errors (connection failures, unexpected panics) still get the structured zap treatment
• db.ErrInvalidConfig sentinel marks config-shaped errors (bad DSN, disallowed auth) detected after config.Load so main can route them to the plain-text path

Before

{"level":"error","ts":"...","caller":"main.go:58","msg":"fatal","error":"load config: set CRDB_DATABASE_URL or provide cert env vars; missing: [CRDB_HOST ...]","errorVerbose":"load config: ...\n(1) attached stack trace\n  -- stack trace:\n  | main.run\n  | .../main.go:67\n  ...20 more lines..."}

After

cockroachdb-mcp-server: invalid configuration: CRDB_DATABASE_URL must include sslmode (require, verify-ca, or verify-full)

See the Configuration section of the README:
https://github.com/cockroachdb/cockroachdb-mcp-server#configuration

Test plan

• go test ./... passes (all 8 packages)
• Manually verified all 6 config error paths produce clean output: missing config, bad DSN, missing sslmode, insecure sslmode without opt-in, password without opt-in, bad log path, invalid transport

[rahulcrl]

TFTR @TheComputerM!