readme update

[zekageri]

Summary

• Briefly describe the change and its motivation.
• Link related issues (e.g., closes #123).

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Refactor (code change that neither fixes a bug nor adds a feature)
• Documentation update
• Build/CI

Details

• What does this PR change? Why?
• Any context for reviewers to understand decisions and tradeoffs.

Testing

• Builds locally
• Unit tests added/updated
• Tested on target hardware/device (if applicable)

Describe how you tested the changes. Include commands, logs, or screenshots if helpful.

Compatibility / Breaking Changes

• Describe any API, ABI, or behavior changes.
• Migration steps for users (if any).

Risks and Mitigations

• Potential risks introduced by this change and how they’re mitigated.

Checklist

• Code follows project style and conventions
• All tests pass locally
• Documentation updated (README, examples, comments)
• No secrets, credentials, or sensitive data committed
• Linked issue(s) and relevant context provided

Environment

• Toolchain/SDK versions: (e.g., ESP-IDF/PlatformIO/GCC)
• OS and version:
• Other relevant environment details: