Verify default records.yaml matches in-code defaults

## Summary

There appears to be a discrepancy between the default values specified in `records.yaml` and the actual default values defined in the code. These should be verified and synchronized.

## Example Discrepancy

| Configuration | records.yaml Value | In-Code Default |
|---------------|-------------------|-----------------|
| `proxy.config.ssl.client.verify.server.policy` | PERMISSIVE | ENFORCED |

## Suggested Action

1. Audit all configuration defaults in `records.yaml` against their corresponding in-code defaults
2. Determine which value is the intended default
3. Synchronize the values to ensure consistency
4. Consider adding a CI check to prevent future drift between these two sources of truth

## Impact

Configuration mismatches can lead to unexpected behavior when users rely on documented defaults versus actual runtime defaults.