Correct the Enterprise page claims against ThinkWatch v2.1.0

[fylorn]

Every factual claim on the Enterprise page (/thinkwatch, /zh-CN/thinkwatch) was checked against the ThinkWatch source at v2.1.0. Claims that did not hold were rewritten into true ones or removed. English and Chinese say the same thing. Only strings in src/i18n/index.ts change; no components are touched.

Removed items (layout may need to adapt)

• Teams tab goes from 5 cards to 4: "Scoped API keys" and "Per-team spending limits" are removed (API keys have no team; limits and budgets attach only to users, API keys and roles). "Team workspaces" and "Per-team cost attribution" are replaced by "Teams and members" and "Analytics by team", and a new "Roles inherited from a team" card is added.
• All other tabs keep 7 items; the MCP table keeps 8 rows and 4 cards.

Main corrections

• Pipeline: keys identify a user (no user/team/project scoping); authorization comes from roles (including team-inherited) narrowed by the key allowlist; the budget check is described accurately; SSE jargon removed.
• Rate limits and budgets: users, keys or roles; windows from 1 minute to 1 week; budgets count weighted tokens after the response; limits are skipped when Redis is down unless configured to refuse (the "fail closed" claim was wrong).
• Routing: latency, success rate, or both, plus manual weights; no decision log exists.
• Gemini is a fourth API surface; the model allowlist is the intersection of key and roles.
• Prometheus: opt-in, on the console port, bearer-gated; the listed metric names did not exist.
• Readiness also checks ClickHouse and an active provider; the body permission is logs:read_bodies; PII redaction at write is optional (off by default).
• The image is not 2 MB; key hashes are HMAC-SHA256.
• The MCP Store ships 37 templates (seed and registry), and they are not bilingual.
• The setup wizard sets the site name and issues the first API key; it does not add a provider.

🤖 Generated with Claude Code