docs: audit and clarify the supported devices matrix

[rootsongjc]

Problem

The current supported devices page provides a table without defining what its columns mean or linking to supporting documentation.

Several entries are also inconsistent:

• AWS Neuron has a user guide but is missing from the table.
• Biren appears in Next and the v2.9.0 release post but not the v2.9.0 table.
• Teco is listed as supported while its status says “Checking” and “In progress.”
• Terms such as MemoryIsolation, CoreIsolation, MultiCard Support, and All are ambiguous.

Proposed changes

1. Audit the device list against released code and device guides.
2. Define support statuses such as Stable, Experimental, and Under Validation.
3. Explain every capability column and its limitations.
4. Add links to each device’s setup guide or tracking issue.
5. Record the applicable HAMi version and last verification date.

The English and Chinese pages should contain the same validated information.

[coderabbitai]

🔗 Related PRs

#430 - add documentation for Biren [merged]
#436 - 📝 修改文档 -> 海光DCU全系列已支持HAMi [merged]
#498 - docs: align monitoring metric names with HAMi v2.9 exporters [merged]
#516 - docs: document per-container and per-vGPU real-time metrics [merged]
#523 - fix: make zh terminology consistent for memory isolation and vGPU casing [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[Adii-45]

Hey @rootsongjc, would like to take on this issue and work on a fix for it! Can it be assigned to me?

[rootsongjc]

Hi @Adii-45, thanks for picking this up — assigning to you!

Quick heads-up on scope: the hard part here is domain context rather than code. The matrix needs cross-checking against the device code, the per-device setup guides, and release notes — e.g. AWS Neuron has a guide but isn't in the table; Biren shows in Next + the v2.9.0 release post but not the v2.9.0 table; Teco is listed as supported while its status says "Checking". We also need consistent definitions for the capability columns (MemoryIsolation, CoreIsolation, MultiCard, etc.) and EN/ZH to stay in sync.

To keep the first PR reviewable, I'd suggest doing it in slices rather than one big rewrite:

1. Audit + fix the Neuron/Biren/Teco inconsistencies and define the status terms (Stable / Experimental / Under Validation)
2. Follow-up: capability-column definitions + per-device guide links + version/last-verified dates

Pointers to get oriented: the docs/userguide/<device>/ guides, the release posts under blog/, and the device support code in the HAMi/HAMi repo.

Ping me here whenever a device-specific detail is unclear — I'll review each slice and fill in context as you go. Welcome aboard! 🚀

[Adii-45]

Thanks! I'll start with the first slice (auditing the inconsistencies and defining the status terms) and keep the PR focused... I'll reach out here if I run into any device-specific questions!