fix: resolve UnicodeDecodeError in minimax tests on Windows

[sabya-code03]

Summary

Describe the problem and fix in 2–5 bullets:

• Problem: Running pytest on a Windows environment triggers a UnicodeDecodeError ('charmap' codec can't decode byte...) in tests/unit/test_minimax_example.py.
• Why it matters: Windows uses a different default system encoding (like cp1252), causing failures when Path.read_text() attempts to parse special characters (like emojis or arrows) in the README.md files during tests. This blocks Windows users from successfully running the local test suite.
• What changed: Added explicit encoding="utf-8" arguments to all Path.read_text() calls within tests/unit/test_minimax_example.py.
• What did NOT change (scope boundary): No application logic, agent configurations, or API interactions were modified. This is strictly a test-suite file-reading fix.

Change Type (select all that apply)

• Bug fix
• Feature
• Refactor
• Documentation
• Security hardening
• Tests
• Chore/infra

Scope (select all touched areas)

• Server / API endpoints
• Extensions (DID, x402, etc.)
• Storage backends
• Scheduler backends
• Observability / monitoring
• Authentication / authorization
• CLI / utilities
• Tests
• Documentation
• CI/CD / infra

Linked Issue/PR

• Closes #
• Related #

User-Visible / Behavior Changes

None

Security Impact (required)

• New permissions/capabilities? No
• Secrets/credentials handling changed? No
• New/changed network calls? No
• Database schema/migration changes? No
• Authentication/authorization changes? No
• If any Yes, explain risk + mitigation: N/A

Verification

Environment

• OS: Windows 11
• Python version: 3.12+ (via uv)
• Storage backend: N/A
• Scheduler backend: N/A

Steps to Test

1. Clone the repository on a Windows machine.
2. Run uv sync --dev to set up the environment.
3. Execute the specific test file: uv run pytest tests/unit/test_minimax_example.py

Expected Behavior

• All 24 tests in the file pass successfully (with 3 tests correctly skipping if MINIMAX_API_KEY is not set), and the files are read using UTF-8 encoding.

Actual Behavior

• Tests pass cleanly without UnicodeDecodeError crashing the suite.

Evidence (attach at least one)

• Failing test before + passing after
• Test output / logs
• Screenshot / recording
• Performance metrics (if relevant)

Human Verification (required)

What you personally verified (not just CI):

• Verified scenarios: Executed test_minimax_example.py locally on a Windows environment and verified the elimination of UnicodeDecodeError.
• Edge cases checked: Ensured integration tests correctly skip when the MINIMAX_API_KEY environment variable is not present.
• What you did NOT verify: Execution on Linux/macOS (though explicit UTF-8 encoding is the standard and perfectly safe for POSIX systems).

Compatibility / Migration

• Backward compatible? Yes
• Config/env changes? No
• Database migration needed? No
• If yes, exact upgrade steps: N/A

Failure Recovery (if this breaks)

• How to disable/revert this change quickly: Revert the commit.
• Files/config to restore: tests/unit/test_minimax_example.py
• Known bad symptoms reviewers should watch for: Text parsing failures in the test suite on Unix systems (highly unlikely).

Risks and Mitigations

None

Checklist

• Tests pass (uv run pytest)
• Pre-commit hooks pass (uv run pre-commit run --all-files)
• Documentation updated (if needed)
• Security impact assessed
• Human verification completed
• Backward compatibility considered

Summary by CodeRabbit

• Tests
  • Updated test file handling to consistently use UTF-8 encoding when reading example, environment, and README files.
  • Existing assertions and integration behavior remain unchanged.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: fd2c6017-332f-43d8-9ff3-f502143d13c1

📥 Commits

Reviewing files that changed from the base of the PR and between 7b1ff75 and 7370261.

📒 Files selected for processing (1)

• tests/unit/test_minimax_example.py

---

📝 Walkthrough

Walkthrough

The test suite now specifies UTF-8 when reading MiniMax example, environment, and README files. Test assertions and integration behavior remain unchanged.

Changes

Encoding test updates

Layer / File(s)	Summary
Use explicit UTF-8 encoding tests/unit/test_minimax_example.py	Example-content, environment, model, API URL, API-key, and README tests now read files with explicit UTF-8 encoding. Existing assertions remain unchanged.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: octo-patch

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the Windows UnicodeDecodeError fix in the minimax tests.
Description check	✅ Passed	The description covers the problem, fix, scope, verification, security impact, recovery, risks, and checklist with sufficient detail.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

Warning

⚠️ This pull request shows signs of AI-generated slop (redundant_comments, trivial_assertion, ai_padded_prose). It has been flagged by CodeRabbit slop detection and should be reviewed carefully.