Claude Code unexpectedly using AWS Bedrock instead of Anthropic API

## Problem

Claude Code is configured to use AWS Bedrock as the API provider instead of the expected Anthropic API direct connection.

## Expected Behavior

Claude Code should connect directly to Anthropic's API, not route through AWS Bedrock.

## Actual Behavior

```
API Configuration
L API Provider: AWS Bedrock
L AWS Region: us-east-1
```

## Additional Context

- Claude Code Status v1.0.52
- Session ID: 8b228663-c540-4944-b432-15a6992f96fc
- Working Directory: `/Users/morgan.joyce/ppv/pillars/dotfiles`
- Model: opus (us.anthropic.claude-opus-4-20250514-v1:0)

## System Status

- MCP servers mostly working (git, github-read/write, brave-search, filesystem ✔)
- Some MCP server warnings (gitlab, gdrive ⚠)
- Config mismatch: running npm-global but config says unknown
- API Error: Could not load credentials from any providers

## Impact

This configuration may be causing:
1. Unexpected routing through AWS instead of direct Anthropic connection
2. Potential credential loading issues
3. Unclear billing/usage attribution

## Keywords

claude-code, bedrock, aws-cli, llm, coding, api-configuration, anthropic

No file, test, or entry point is identified in the issue. Start by locating the dotfiles' Claude Code and AWS/Bedrock configuration, then reproduce the reported provider and credential behavior; done means the configuration uses the direct Anthropic API and the credential-loading error is resolved.

Written by the indexing model from the issue text.