Acknowledge and thank the OpenCode contributors whose work MiMo Code is built on

[HaleTom]

Is your feature request related to a problem? Please describe.

MiMo Code is a fork of OpenCode. The LICENSE file correctly preserves the Copyright (c) 2025 opencode line, and the README has a one-sentence "Relationship to OpenCode" section noting that MiMoCode is "built as a fork."

That satisfies the letter of the MIT license. But it doesn't acknowledge the people who built the asset Xiaomi received for free.

OpenCode represents thousands of hours of engineering by the Anomaly/SST team and community contributors — the same packages/opencode/ tree, TUI, plugin system, provider abstraction, MCP support, and LSP integration that MiMo Code ships under its own brand. None of them are named anywhere in this repo. The only trace of an individual is a leftover dev path (/home/thdxr/...) in drizzle.config.ts.

Describe the solution you'd like

A short, genuine acknowledgment in the README — alongside the existing "Relationship to OpenCode" section — that:

1. Thanks the OpenCode contributors, and
2. Uses the words "acknowledge" / "appreciate" / "thank" explicitly.

Something on the order of:

We gratefully acknowledge the contributors to OpenCode, whose work — the TUI, provider system, plugin architecture, MCP and LSP integration, and core agent loop — forms the foundation MiMo Code is built on. OpenCode is developed by the Anomaly/SST team and community contributors; we thank them for building a product that made this fork possible.

This costs nothing, takes two minutes, and is the bare minimum of open-source etiquette for a corporate fork that has already accrued 10k+ stars under its own brand.

Describe alternatives you've considered

• Do nothing. Technically license-compliant. Signals that Xiaomi views the upstream as a code harvest rather than a community. Not recommended.
• A THANKS.md or AUTHORS file in addition to the README note. Acceptable, but the README is where 99% of readers will look, so the acknowledgment belongs there.
• A blog post. Useful as a supplement, not a substitute — the repo itself should carry the acknowledgment.

Additional context

This is distinct from issue #588 (broad governance/engagement), which covers how MiMo Code engages with its own new community. This issue is specifically about acknowledging the upstream community whose work made the fork possible.

Xiaomi has received a mature, production-grade coding agent for free under a permissive license. The least it can do is say thank you.