stack-sh · konojunya · Sep 5, 2026 · Sep 5, 2026
diff --git a/content/cli-release.json b/content/cli-release.json
@@ -1,5 +1,5 @@
 {
   "repository": "stack-sh/cli",
-  "revision": "6bad86702096bc9d9f10641675eed57203ae4467",
-  "version": "0.5.0"
+  "revision": "1d5f64cc699e42f9ce52ac537903e40c0eb91432",
+  "version": "0.5.1"
 }
diff --git a/content/site/guide/getting-started.md b/content/site/guide/getting-started.md
@@ -6,6 +6,14 @@ The fastest way to use Stack is the browser [Playground](https://stack-diagram.c
 
 For terminal workflows and local automation, install the owner-maintained Homebrew formula with `brew install stack-sh/tap/stack`. It uses the canonical Stack CLI {{cliVersion}} release archive and supports Apple Silicon macOS plus glibc-based Linux on arm64 and x86_64 when the host meets Homebrew's current tier-1 requirements. Homebrew owns upgrades through `brew upgrade stack-sh/tap/stack`; uninstalling the formula leaves your Stack configuration and icon store in place. See the [CLI distribution contract](https://github.com/stack-sh/cli/blob/main/docs/distribution.md#homebrew-installation) for the exact platform matrix, direct-install alternative, and recovery policy.
 
+Rust users can install the same CLI from crates.io with a working Rust 1.85 or newer toolchain and native linker:
+
+`cargo install stack-diagram-cli --version {{cliVersion}} --locked`
+
+`stack --version`
+
+This builds the `stack` binary from registry-only dependencies on macOS or glibc Linux, on arm64 or x86_64. Cargo owns upgrades: run the install command with the desired released version; uninstall with `cargo uninstall stack-diagram-cli`. Choose one installer for a given binary location to avoid competing copies on `PATH`; Stack does not update itself. Cargo does not install shell completion or manual files automatically; see the [Cargo installation contract](https://github.com/stack-sh/cli/blob/main/docs/distribution.md#cargo-installation) for prerequisites and optional shell integration. Aqua users can use the [owner registry](https://github.com/stack-sh/cli/blob/main/aqua/README.md).
+
 ## Write your first document
 
 Replace the editor content with this example:

diff --git a/content/site/ja/guide/getting-started.md b/content/site/ja/guide/getting-started.md
@@ -6,6 +6,14 @@
 
 Terminal workflowとlocal automationでは、owner管理のHomebrew formulaを`brew install stack-sh/tap/stack`でinstallします。CanonicalなStack CLI {{cliVersion}} release archiveを使用し、Homebrewの現行Tier 1要件を満たすApple Silicon macOSと、arm64 / x86_64のglibc Linuxをsupportします。UpgradeはHomebrewが`brew upgrade stack-sh/tap/stack`で管理し、formulaをuninstallしてもStackのconfigとicon storeは保持されます。正確なplatform matrix、direct install、recovery policyは[CLI distribution contract](https://github.com/stack-sh/cli/blob/main/docs/distribution.md#homebrew-installation)を参照してください。
 
+Rustを利用している場合は、Rust 1.85以降のtoolchainとnative linkerを用意し、crates.ioから同じCLIをinstallできます。
+
+`cargo install stack-diagram-cli --version {{cliVersion}} --locked`
+
+`stack --version`
+
+macOSまたはglibc Linuxのarm64 / x86_64で、registry由来の依存だけを使ってbinary `stack`をbuildします。Upgradeは目的の公開versionを指定してinstall commandを実行し、uninstallは`cargo uninstall stack-diagram-cli`です。同じbinaryの配置先には1つのinstallerを選び、`PATH`上の競合を避けてください。Stack自身は自己更新しません。Cargoはshell completionやmanualを自動配置しないため、前提条件と任意のshell連携は[Cargo installation contract](https://github.com/stack-sh/cli/blob/main/docs/distribution.md#cargo-installation)を参照してください。Aquaでは[owner registry](https://github.com/stack-sh/cli/blob/main/aqua/README.md)を利用できます。
+
 ## 最初のdocumentを書く
 
 Editorを次のexampleへ置き換えます。

diff --git a/content/site/ko/guide/getting-started.md b/content/site/ko/guide/getting-started.md
@@ -6,6 +6,14 @@ Stack을 가장 빠르게 사용하는 방법은 브라우저 [Playground](https
 
 터미널 워크플로와 로컬 자동화에서는 `brew install stack-sh/tap/stack`으로 Stack이 관리하는 Homebrew formula를 설치합니다. 이 formula는 표준 Stack CLI {{cliVersion}} 릴리스 아카이브를 사용하며, Homebrew의 현재 Tier 1 요구 사항을 충족하는 Apple Silicon macOS와 arm64 / x86_64 glibc Linux를 지원합니다. 업그레이드는 Homebrew가 `brew upgrade stack-sh/tap/stack`으로 관리하며, formula를 제거해도 Stack 설정과 아이콘 저장소는 유지됩니다. 정확한 플랫폼 매트릭스, 직접 설치 방법 및 복구 정책은 [CLI 배포 계약](https://github.com/stack-sh/cli/blob/main/docs/distribution.md#homebrew-installation)을 참고하세요.
 
+Rust 사용자는 Rust 1.85 이상의 도구 체인과 네이티브 링커를 준비한 뒤 crates.io에서 같은 CLI를 설치할 수 있습니다.
+
+`cargo install stack-diagram-cli --version {{cliVersion}} --locked`
+
+`stack --version`
+
+macOS 또는 glibc Linux의 arm64 / x86_64에서 registry 의존성만으로 `stack` 바이너리를 빌드합니다. 업그레이드는 원하는 공개 버전을 지정해 설치 명령을 다시 실행하고, 제거는 `cargo uninstall stack-diagram-cli`를 사용합니다. 같은 바이너리 위치에는 하나의 설치 방식을 선택해 `PATH` 충돌을 피하세요. Stack은 자체 업데이트하지 않습니다. Cargo는 shell completion이나 매뉴얼 파일을 자동 배치하지 않으므로 사전 조건과 선택적 연동은 [Cargo 설치 계약](https://github.com/stack-sh/cli/blob/main/docs/distribution.md#cargo-installation)을 참고하세요. Aqua 사용자는 [공식 관리 registry](https://github.com/stack-sh/cli/blob/main/aqua/README.md)를 사용할 수 있습니다.
+
 ## 첫 문서 작성
 
 에디터 내용을 다음 예제로 바꿉니다.

diff --git a/content/site/zh/guide/getting-started.md b/content/site/zh/guide/getting-started.md
@@ -6,6 +6,14 @@
 
 对于终端工作流和本地自动化，请使用 `brew install stack-sh/tap/stack` 安装由 Stack 维护的 Homebrew formula。它使用规范的 Stack CLI {{cliVersion}} 发布归档，并支持符合 Homebrew 当前 Tier 1 要求的 Apple Silicon macOS，以及 arm64 / x86_64 的 glibc Linux。Homebrew 通过 `brew upgrade stack-sh/tap/stack` 管理升级；卸载 formula 不会删除 Stack 配置和图标存储。有关准确的平台矩阵、直接安装方式和恢复策略，请参阅 [CLI 分发约定](https://github.com/stack-sh/cli/blob/main/docs/distribution.md#homebrew-installation)。
 
+Rust 用户也可以使用 Rust 1.85 或更高版本的工具链及原生链接器，从 crates.io 安装同一个 CLI：
+
+`cargo install stack-diagram-cli --version {{cliVersion}} --locked`
+
+`stack --version`
+
+在 macOS 或 glibc Linux 的 arm64 / x86_64 上，它仅使用 registry 依赖构建 `stack` 二进制。升级时用目标已发布版本重新运行安装命令；卸载使用 `cargo uninstall stack-diagram-cli`。请为同一个二进制位置选择一种安装方式，避免 `PATH` 冲突；Stack 不会自行更新。Cargo 不会自动安装 shell 补全或手册文件，前提条件和可选集成请参阅 [Cargo 安装约定](https://github.com/stack-sh/cli/blob/main/docs/distribution.md#cargo-installation)。Aqua 用户可以使用[官方维护的 registry](https://github.com/stack-sh/cli/blob/main/aqua/README.md)。
+
 ## 编写第一份文档
 
 将编辑器内容替换为下面的示例：

diff --git a/generated/guide/agent-workflow.md b/generated/guide/agent-workflow.md
@@ -6,9 +6,9 @@ Deliver editable `.stack` source and, when rendering is available, an SVG. Prese
 
 ## Start with the available tools
 
-Run `stack --version` and `stack help` before selecting commands. Use the installed binary's help, not unreleased repository instructions. This workflow is tested with published CLI 0.5.0. The commands below use human-readable output; `check`, `fmt`, and `render` also accept `--json` for structured diagnostics, artifacts, and operational errors. Read the [versioned JSON output contract](https://github.com/stack-sh/cli/blob/v0.5.0/docs/machine-readable-output.md) before parsing it, and verify options using `stack help <command>`.
+Run `stack --version` and `stack help` before selecting commands. Use the installed binary's help, not unreleased repository instructions. This workflow is tested with published CLI 0.5.1. The commands below use human-readable output; `check`, `fmt`, and `render` also accept `--json` for structured diagnostics, artifacts, and operational errors. Read the [versioned JSON output contract](https://github.com/stack-sh/cli/blob/v0.5.1/docs/machine-readable-output.md) before parsing it, and verify options using `stack help <command>`.
 
-If the CLI is missing, consult the [installation guide](https://stack-diagram.com/docs/guide/getting-started.md) and [release distribution contract](https://github.com/stack-sh/cli/blob/v0.5.0/docs/distribution.md). Install only when the user's authorization allows it. Otherwise provide source with an explicit validation gap; do not report it as checked. No remote source upload is required. Upgrade with the package manager that installed Stack, or verify and manually replace a direct download; `stack update` has been removed. For local configuration problems, `stack doctor` and `stack config path` provide read-only diagnosis.
+If the CLI is missing, consult the [installation guide](https://stack-diagram.com/docs/guide/getting-started.md) and [release distribution contract](https://github.com/stack-sh/cli/blob/v0.5.1/docs/distribution.md). Install only when the user's authorization allows it. Otherwise provide source with an explicit validation gap; do not report it as checked. No remote source upload is required. Upgrade with the package manager that installed Stack, or verify and manually replace a direct download; `stack update` has been removed. For local configuration problems, `stack doctor` and `stack config path` provide read-only diagnosis.
 
 ## Read only the relevant reference
 

diff --git a/generated/manifest.json b/generated/manifest.json
@@ -2,17 +2,17 @@
   "schemaVersion": "1.0",
   "cli": {
     "repository": "stack-sh/cli",
-    "revision": "6bad86702096bc9d9f10641675eed57203ae4467",
-    "version": "0.5.0"
+    "revision": "1d5f64cc699e42f9ce52ac537903e40c0eb91432",
+    "version": "0.5.1"
   },
   "files": [
     {
       "path": "skills/stack-diagrams/SKILL.md",
-      "sha256": "94ccbe80586569369f35cc2f4d090e55cd0ef0906482b07654aca53399f9e0ae"
+      "sha256": "af399eb4277fa4563f5126cce04e9a4a38feea31880db97c1eb904539a06669c"
     },
     {
       "path": "guide/agent-workflow.md",
-      "sha256": "3e70bef63e2e381d6a930224062a878d4dfff2b8358645c680c7447b6073fd45"
+      "sha256": "b92225a66840f094e02ee42f32131f075287044e2d2f0a73ad60335e906ccf86"
     },
     {
       "path": "site/examples/index.md",
@@ -24,7 +24,7 @@
     },
     {
       "path": "site/guide/getting-started.md",
-      "sha256": "ab20aa8280483326f8e93a9552d28ba1a099da382ebb9729a34392738736574b"
+      "sha256": "1162aa9d07c7ac323ef877e0f971cc2a5b47ec5da97e650e0daa571040edb232"
     },
     {
       "path": "site/guide/playground.md",
@@ -52,7 +52,7 @@
     },
     {
       "path": "site/ja/guide/getting-started.md",
-      "sha256": "4a561f5db209c51bf48c0ed225b2961503806d9b80fced6a0c78e266e7a8cd76"
+      "sha256": "20546c410668abce3011fe18daed34cc86ab4c317bae8ab19b5b9ee8a7626e4b"
     },
     {
       "path": "site/ja/guide/playground.md",
@@ -108,7 +108,7 @@
     },
     {
       "path": "site/ko/guide/getting-started.md",
-      "sha256": "60cd75eebfcf4e1089feebe8cbf294975a0226a68e8e2aa0b52f6828edce13b9"
+      "sha256": "d45714fdb4a3c873e1a26803f6e4505c613e193ee854f89d226f9e4f4c5e8ace"
     },
     {
       "path": "site/ko/guide/playground.md",
@@ -192,7 +192,7 @@
     },
     {
       "path": "site/zh/guide/getting-started.md",
-      "sha256": "8ac4cb6f87158569f587ff4a4a63d68e0c312b707aece5023b0a8d8ac1ffee9b"
+      "sha256": "b2b851390a21c8534112c3691e9007dd49bd035c6fe7d5181ed43cfd865e075d"
     },
     {
       "path": "site/zh/guide/playground.md",
@@ -240,19 +240,19 @@
     },
     {
       "path": "site/guide/agent-workflow.md",
-      "sha256": "a62497914c1648494c22009b3e16a96e3f5190e73fb0b67225bef64f3063c0e4"
+      "sha256": "50e2396e950ae319dbfd26a3dbb06c3a1163cec3cbcb7dac8eb8ca01b618bfd8"
     },
     {
       "path": "site/ja/guide/agent-workflow.md",
-      "sha256": "a62497914c1648494c22009b3e16a96e3f5190e73fb0b67225bef64f3063c0e4"
+      "sha256": "50e2396e950ae319dbfd26a3dbb06c3a1163cec3cbcb7dac8eb8ca01b618bfd8"
     },
     {
       "path": "site/zh/guide/agent-workflow.md",
-      "sha256": "a62497914c1648494c22009b3e16a96e3f5190e73fb0b67225bef64f3063c0e4"
+      "sha256": "50e2396e950ae319dbfd26a3dbb06c3a1163cec3cbcb7dac8eb8ca01b618bfd8"
     },
     {
       "path": "site/ko/guide/agent-workflow.md",
-      "sha256": "a62497914c1648494c22009b3e16a96e3f5190e73fb0b67225bef64f3063c0e4"
+      "sha256": "50e2396e950ae319dbfd26a3dbb06c3a1163cec3cbcb7dac8eb8ca01b618bfd8"
     },
     {
       "path": "machine/v1.0.0/manifest.json",

diff --git a/generated/site/guide/agent-workflow.md b/generated/site/guide/agent-workflow.md
@@ -6,9 +6,9 @@ Deliver editable `.stack` source and, when rendering is available, an SVG. Prese
 
 ## Start with the available tools
 
-Run `stack --version` and `stack help` before selecting commands. Use the installed binary's help, not unreleased repository instructions. This workflow is tested with published CLI 0.5.0. The commands below use human-readable output; `check`, `fmt`, and `render` also accept `--json` for structured diagnostics, artifacts, and operational errors. Read the [versioned JSON output contract](https://github.com/stack-sh/cli/blob/v0.5.0/docs/machine-readable-output.md) before parsing it, and verify options using `stack help <command>`.
+Run `stack --version` and `stack help` before selecting commands. Use the installed binary's help, not unreleased repository instructions. This workflow is tested with published CLI 0.5.1. The commands below use human-readable output; `check`, `fmt`, and `render` also accept `--json` for structured diagnostics, artifacts, and operational errors. Read the [versioned JSON output contract](https://github.com/stack-sh/cli/blob/v0.5.1/docs/machine-readable-output.md) before parsing it, and verify options using `stack help <command>`.
 
-If the CLI is missing, consult the [installation guide](https://stack-diagram.com/docs/guide/getting-started.md) and [release distribution contract](https://github.com/stack-sh/cli/blob/v0.5.0/docs/distribution.md). Install only when the user's authorization allows it. Otherwise provide source with an explicit validation gap; do not report it as checked. No remote source upload is required. Upgrade with the package manager that installed Stack, or verify and manually replace a direct download; `stack update` has been removed. For local configuration problems, `stack doctor` and `stack config path` provide read-only diagnosis.
+If the CLI is missing, consult the [installation guide](https://stack-diagram.com/docs/guide/getting-started.md) and [release distribution contract](https://github.com/stack-sh/cli/blob/v0.5.1/docs/distribution.md). Install only when the user's authorization allows it. Otherwise provide source with an explicit validation gap; do not report it as checked. No remote source upload is required. Upgrade with the package manager that installed Stack, or verify and manually replace a direct download; `stack update` has been removed. For local configuration problems, `stack doctor` and `stack config path` provide read-only diagnosis.
 
 ## Read only the relevant reference
 

diff --git a/generated/site/guide/getting-started.md b/generated/site/guide/getting-started.md
@@ -4,7 +4,15 @@ The fastest way to use Stack is the browser [Playground](https://stack-diagram.c
 
 ## Install the native CLI
 
-For terminal workflows and local automation, install the owner-maintained Homebrew formula with `brew install stack-sh/tap/stack`. It uses the canonical Stack CLI 0.5.0 release archive and supports Apple Silicon macOS plus glibc-based Linux on arm64 and x86_64 when the host meets Homebrew's current tier-1 requirements. Homebrew owns upgrades through `brew upgrade stack-sh/tap/stack`; uninstalling the formula leaves your Stack configuration and icon store in place. See the [CLI distribution contract](https://github.com/stack-sh/cli/blob/main/docs/distribution.md#homebrew-installation) for the exact platform matrix, direct-install alternative, and recovery policy.
+For terminal workflows and local automation, install the owner-maintained Homebrew formula with `brew install stack-sh/tap/stack`. It uses the canonical Stack CLI 0.5.1 release archive and supports Apple Silicon macOS plus glibc-based Linux on arm64 and x86_64 when the host meets Homebrew's current tier-1 requirements. Homebrew owns upgrades through `brew upgrade stack-sh/tap/stack`; uninstalling the formula leaves your Stack configuration and icon store in place. See the [CLI distribution contract](https://github.com/stack-sh/cli/blob/main/docs/distribution.md#homebrew-installation) for the exact platform matrix, direct-install alternative, and recovery policy.
+
+Rust users can install the same CLI from crates.io with a working Rust 1.85 or newer toolchain and native linker:
+
+`cargo install stack-diagram-cli --version 0.5.1 --locked`
+
+`stack --version`
+
+This builds the `stack` binary from registry-only dependencies on macOS or glibc Linux, on arm64 or x86_64. Cargo owns upgrades: run the install command with the desired released version; uninstall with `cargo uninstall stack-diagram-cli`. Choose one installer for a given binary location to avoid competing copies on `PATH`; Stack does not update itself. Cargo does not install shell completion or manual files automatically; see the [Cargo installation contract](https://github.com/stack-sh/cli/blob/main/docs/distribution.md#cargo-installation) for prerequisites and optional shell integration. Aqua users can use the [owner registry](https://github.com/stack-sh/cli/blob/main/aqua/README.md).
 
 ## Write your first document
 

diff --git a/generated/site/ja/guide/agent-workflow.md b/generated/site/ja/guide/agent-workflow.md
@@ -6,9 +6,9 @@ Deliver editable `.stack` source and, when rendering is available, an SVG. Prese
 
 ## Start with the available tools
 
-Run `stack --version` and `stack help` before selecting commands. Use the installed binary's help, not unreleased repository instructions. This workflow is tested with published CLI 0.5.0. The commands below use human-readable output; `check`, `fmt`, and `render` also accept `--json` for structured diagnostics, artifacts, and operational errors. Read the [versioned JSON output contract](https://github.com/stack-sh/cli/blob/v0.5.0/docs/machine-readable-output.md) before parsing it, and verify options using `stack help <command>`.
+Run `stack --version` and `stack help` before selecting commands. Use the installed binary's help, not unreleased repository instructions. This workflow is tested with published CLI 0.5.1. The commands below use human-readable output; `check`, `fmt`, and `render` also accept `--json` for structured diagnostics, artifacts, and operational errors. Read the [versioned JSON output contract](https://github.com/stack-sh/cli/blob/v0.5.1/docs/machine-readable-output.md) before parsing it, and verify options using `stack help <command>`.
 
-If the CLI is missing, consult the [installation guide](https://stack-diagram.com/docs/guide/getting-started.md) and [release distribution contract](https://github.com/stack-sh/cli/blob/v0.5.0/docs/distribution.md). Install only when the user's authorization allows it. Otherwise provide source with an explicit validation gap; do not report it as checked. No remote source upload is required. Upgrade with the package manager that installed Stack, or verify and manually replace a direct download; `stack update` has been removed. For local configuration problems, `stack doctor` and `stack config path` provide read-only diagnosis.
+If the CLI is missing, consult the [installation guide](https://stack-diagram.com/docs/guide/getting-started.md) and [release distribution contract](https://github.com/stack-sh/cli/blob/v0.5.1/docs/distribution.md). Install only when the user's authorization allows it. Otherwise provide source with an explicit validation gap; do not report it as checked. No remote source upload is required. Upgrade with the package manager that installed Stack, or verify and manually replace a direct download; `stack update` has been removed. For local configuration problems, `stack doctor` and `stack config path` provide read-only diagnosis.
 
 ## Read only the relevant reference