docs(#743): address Kimi review — runtime count + support boundary
Address remaining review feedback on PR #743: - Bump supported-runtime count 15 -> 16 across user-facing READMEs (docs/README.md + ja-JP/zh-CN translations) now that Kimi is added. - Add an explicit support-boundary note in the Kimi CLI install section: the kimi --agent-file custom-agent contract targets legacy/Python kimi-cli; newer npm Kimi Code (@moonshot-ai/kimi-code) rejects --agent-file and consumes the same /skill:gsd-* skills via --skills-dir. - Mirror the boundary in the changeset so release notes are unambiguous. Historical ADR/changeset/INVENTORY references to '15 runtimes' are left intact as point-in-time records. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
@@ -15,7 +15,7 @@ Language versions: [English](README.md) · [Português (pt-BR)](pt-BR/README.md)
|
||||
|
||||
## How-to guides
|
||||
|
||||
- [Install on your runtime](how-to/install-on-your-runtime.md) — runtime-specific install steps for all 15 supported runtimes
|
||||
- [Install on your runtime](how-to/install-on-your-runtime.md) — runtime-specific install steps for all 16 supported runtimes
|
||||
- [Install a minimal GSD and add skills later](how-to/install-minimal-and-add-skills.md) — install only the core skills, then grow the surface with profiles and `/gsd:surface`
|
||||
- [Discuss a phase](how-to/discuss-a-phase.md) — capture implementation decisions before planning begins
|
||||
- [Plan a phase](how-to/plan-a-phase.md) — run research, decompose work, and verify plan quality
|
||||
|
||||
Reference in New Issue
Block a user