Alibaba DashScope/Qwen Integration

What was built & why

The `Persona` class hardcoded Anthropic Haiku for default utterances, creating unnecessary cost and vendor lock-in. You built `AlibabaUtteranceClient` with plain `urllib` to hit DashScope’s OpenAI-compatible endpoint directly. This avoids heavy SDK bloat. The `load_alibaba_creds()` function parses `~/.aws/alibaba` for keys, allowing tests to skip integration when configs are missing. `Persona` now defaults to this new client but keeps `AnthropicUtteranceClient` ready for switching.

Principles

• Prefer standard library HTTP clients over heavy SDKs for simple API calls.
• Fail fast on missing credentials to enable clean test skipping.
• Keep alternative providers instantiated to allow runtime swapping.

Patterns

• Strategy Pattern for pluggable LLM backends

• Configuration loading with environment variable overrides

How to apply

• Add retry logic to `AlibabaUtteranceClient` to mitigate `urllib` limitations.

• Validate the `~/.aws/alibaba` file format strictly to prevent whitespace parsing errors.

• Benchmark Qwen latency against Haiku to adjust downstream timeout expectations.

Pitfalls

• Plain `urllib` lacks the automatic retries found in official SDKs.
• Custom credential parsing breaks if the file format changes slightly.
• Qwen may generate different utterance styles, affecting persona consistency.