Document public v0.1.0 release status

Author: willamhou

README.md

@@ -7,9 +7,9 @@ workbench. It is built for the loop you actually use while programming:
 inspect a repository, edit files, run checks, review the result, and keep
 iterating from the same terminal.
 
-> Status: usable for dogfooding and repository work. It is not yet a polished
-> hosted product, and the native PTY supervisor/release channels are still in
-> progress.
+> Status: usable for dogfooding and repository work. `v0.1.0` has GitHub
+> Release binaries and a GHCR image; npm and Homebrew publishing still need
+> registry/tap credentials, and native PTY/product polish remains in progress.
 
 <p align="center">
   <img src="./docs/demo/deepseek-code-tui.svg" alt="DeepSeekCode TUI demo snapshot" width="100%">
@@ -32,8 +32,8 @@ iterating from the same terminal.
 - RLM helpers for recursive/long-input analysis, model-session context, live
   queue status, event replay, cancellation, recovery, and drain controls.
 - LSP-backed and fallback diagnostics runners with JSON/JSONL watch output.
-- Release packaging scaffolding for Cargo, npm wrappers, Docker, Homebrew
-  formula rendering, and GitHub release assets.
+- Release assets for Linux x64, macOS x64, macOS arm64, and Windows x64,
+  plus a GHCR image and npm/Homebrew packaging metadata.
 
 ## Quick Start
 
@@ -45,6 +45,24 @@ deepseek version
 deepseek doctor --json
 ```
 
+Or download a release archive:
+
+```bash
+curl -L -o deepseek-linux-x64.tar.gz \
+  https://github.com/willamhou/DeepSeekCode/releases/download/v0.1.0/deepseek-linux-x64.tar.gz
+curl -L -o deepseek-linux-x64.tar.gz.sha256 \
+  https://github.com/willamhou/DeepSeekCode/releases/download/v0.1.0/deepseek-linux-x64.tar.gz.sha256
+shasum -a 256 -c deepseek-linux-x64.tar.gz.sha256
+tar -xzf deepseek-linux-x64.tar.gz
+./deepseek version
+```
+
+Or run the published container:
+
+```bash
+docker run --rm ghcr.io/willamhou/deepseekcode:0.1.0 version
+```
+
 Or use a local checkout:
 
 ```bash
@@ -83,7 +101,7 @@ Claude Code CLI / Codex CLI polish. The largest remaining gaps are:
 
 - native supervisor-owned PTY attach/stdin/resize/replay/wait/cancel;
 - live external write-fixture validation across real repositories;
-- public release evidence for binary, npm, Homebrew, and container channels;
+- npm registry publishing and a Homebrew tap, both blocked on credentials;
 - product polish around onboarding, auth, model/provider setup, and demos.
 
 ## Demo Asset

README.zh-CN.md

@@ -6,8 +6,9 @@ DeepSeekCode 是一个 DeepSeek-first 的终端代码智能体，也是本地
 TUI/runtime workbench。它面向真实写代码循环：阅读仓库、修改文件、运行检查、
 查看结果，然后继续在同一个终端里迭代。
 
-> 当前状态：已经可以用于 dogfood 和仓库内编码任务，但还不是完全产品化的
-> hosted 工具；原生 PTY supervisor 和正式发布渠道仍在推进中。
+> 当前状态：已经可以用于 dogfood 和仓库内编码任务。`v0.1.0` 已有 GitHub
+> Release 二进制包和 GHCR 镜像；npm 与 Homebrew 发布还需要 registry/tap
+> 凭据，原生 PTY 和产品化打磨仍在推进中。
 
 <p align="center">
   <img src="./docs/demo/deepseek-code-tui.svg" alt="DeepSeekCode TUI demo snapshot" width="100%">
@@ -30,8 +31,8 @@ TUI/runtime workbench。它面向真实写代码循环：阅读仓库、修改
 - 支持 RLM 递归/长输入分析、model-session context、live queue status、
   event replay、cancel、recover 和 drain 控制。
 - 支持 LSP-backed 与 fallback diagnostics，并能输出 JSON/JSONL watch。
-- 已有 Cargo、npm wrapper、Docker、Homebrew formula rendering 和 GitHub
-  release assets 的发布打包脚手架。
+- 已有 Linux x64、macOS x64、macOS arm64、Windows x64 的 Release
+  assets，GHCR 镜像，以及 npm/Homebrew 发布元数据。
 
 ## 快速开始
 
@@ -43,6 +44,24 @@ deepseek version
 deepseek doctor --json
 ```
 
+或者下载 release archive：
+
+```bash
+curl -L -o deepseek-linux-x64.tar.gz \
+  https://github.com/willamhou/DeepSeekCode/releases/download/v0.1.0/deepseek-linux-x64.tar.gz
+curl -L -o deepseek-linux-x64.tar.gz.sha256 \
+  https://github.com/willamhou/DeepSeekCode/releases/download/v0.1.0/deepseek-linux-x64.tar.gz.sha256
+shasum -a 256 -c deepseek-linux-x64.tar.gz.sha256
+tar -xzf deepseek-linux-x64.tar.gz
+./deepseek version
+```
+
+或者运行已发布的容器镜像：
+
+```bash
+docker run --rm ghcr.io/willamhou/deepseekcode:0.1.0 version
+```
+
 或者从本地 checkout 安装：
 
 ```bash
@@ -80,7 +99,7 @@ Codex CLI 的产品成熟度。最大差距集中在：
 
 - 原生 supervisor-owned PTY 的 attach/stdin/resize/replay/wait/cancel；
 - 真实外部仓库上的 live write-fixture 验证；
-- binary、npm、Homebrew、container 等公开发布渠道的实际发布证据；
+- npm registry 发布和 Homebrew tap，这两项还缺少对应凭据；
 - onboarding、auth、model/provider 配置和 demo 展示的产品化打磨。
 
 ## Demo 素材

docs/install.md

@@ -45,7 +45,7 @@ cargo build --release
 
 ```bash
 cargo fmt --check
-cargo test
+cargo test -- --test-threads=1
 cargo package --allow-dirty
 deepseek benchmark
 deepseek version
@@ -78,6 +78,19 @@ deepseek dogfood report --limit 5
 
 ## Release Binary
 
+GitHub Release 已经提供 `v0.1.0` 的 Linux x64、macOS x64、macOS arm64 和
+Windows x64 包，以及对应 `.sha256` 文件。例如 Linux x64：
+
+```bash
+curl -L -o deepseek-linux-x64.tar.gz \
+  https://github.com/willamhou/DeepSeekCode/releases/download/v0.1.0/deepseek-linux-x64.tar.gz
+curl -L -o deepseek-linux-x64.tar.gz.sha256 \
+  https://github.com/willamhou/DeepSeekCode/releases/download/v0.1.0/deepseek-linux-x64.tar.gz.sha256
+shasum -a 256 -c deepseek-linux-x64.tar.gz.sha256
+tar -xzf deepseek-linux-x64.tar.gz
+./deepseek version
+```
+
 本地 release binary 路径固定为：
 
 ```bash
@@ -118,12 +131,12 @@ docker run --rm deepseek-code:local version
 Tag 版 `Release Matrix` workflow 会把同一个 Dockerfile 构建并推送到 GHCR：
 
 ```bash
-docker pull ghcr.io/<owner>/<repo>:<version>
-docker run --rm ghcr.io/<owner>/<repo>:<version> version
+docker pull ghcr.io/willamhou/deepseekcode:0.1.0
+docker run --rm ghcr.io/willamhou/deepseekcode:0.1.0 version
 ```
 
 同一次 tag 发布会写入 `<version>`、`v<version>` 和 `latest` 三个 tag；镜像名会按
-GHCR 要求转成小写。
+GHCR 要求转成小写。`v0.1.0` 的公开镜像已经通过 pull 和 `version` smoke test。
 
 npm wrapper 位于 `npm/`，用于发布时把平台 binary 包装成 `deepseek` 命令。root 包通过 optional dependency 解析当前平台的 binary 包，例如 `@deepseek-code/cli-linux-x64`、`@deepseek-code/cli-macos-arm64`、`@deepseek-code/cli-macos-x64` 和 `@deepseek-code/cli-windows-x64`。发布前至少验证 wrapper 语法、平台包解析和本地 binary 转发：
 
@@ -147,9 +160,9 @@ npm tarball，并在 tag run 且配置 `NPM_TOKEN` 时先发布平台包，再
 齐全；加 `--json` 会输出 `deepseek.publish_status.v1`，便于 CI 或 release
 脚本消费。输出中的 `public_install` 会区分 source checkout、GitHub Release、
 npm、Homebrew、GHCR 和 Cargo registry 当前是 `source_available`、
-`ready_to_publish`、`requires_publish` 还是 `source_only_policy`。在没有真实
-tag workflow、registry/tap 发布和外部验证前，不要把 npm/Homebrew/Docker 安装
-路径写成已可用。
+`ready_to_publish`、`requires_publish` 还是 `source_only_policy`。目前 GitHub
+Release 和 GHCR 已有公开验证；npm/Homebrew 在没有 registry/tap 凭据和外部验证前
+不要写成已可用。
 
 ## Runtime 服务模板
 

docs/superpowers/specs/2026-05-14-deepseek-tui-release-gate-parity.md

@@ -8,9 +8,11 @@ Date: 2026-05-14
 DeepSeek-TUI has public release evidence for installable versions. On
 2026-05-14, `Hmbown/DeepSeek-TUI` reported latest release `v0.8.36`, public
 topics `cli`, `deepseek`, `llm`, `rust`, `terminal`, and `tui`, and a public
-Cargo/npm install story. DeepSeekCode is now public with matching core topics,
-but `willamhou/DeepSeekCode` still had no tagged GitHub Release, GHCR image,
-npm package, or Homebrew tap evidence.
+Cargo/npm install story. DeepSeekCode is now public with matching core topics.
+At the start of this work, `willamhou/DeepSeekCode` still had no tagged GitHub
+Release, GHCR image, npm package, or Homebrew tap evidence. The `v0.1.0`
+release now provides public GitHub Release assets and a GHCR image; npm and
+Homebrew remain blocked on registry/tap credentials.
 
 Before creating a public tag, the local release gate exposed a blocker:
 `cargo test` with default parallelism failed due existing process-global test
@@ -47,12 +49,15 @@ gate already used elsewhere is serial test execution.
   after the tag workflow queued indefinitely on `macos-13`.
 - Updated `docs/release.md` to use the same serial test command in the local
   release gate.
+- Published tag `v0.1.0` from commit
+  `2a270e7aae926e11d4cf4f7491ce6c18b66bfb29`.
 
 ## Verification
 
 - `cargo test` with default parallelism reproduced the release blocker:
   `1400 passed; 6 failed`.
-- `cargo test -- --test-threads=1`
+- `cargo test -- --test-threads=1` (`1407 passed`)
+- `cargo check --all-targets`
 - `cargo metadata --no-deps --format-version 1`
 - `cargo package --allow-dirty`
 - `node npm/scripts/check-version-sync.js`
@@ -73,15 +78,22 @@ gate already used elsewhere is serial test execution.
   - `cargo test handle_tui_action_renders_hooks_inventory --lib -- --test-threads=1`
 - `docker build -t deepseek-code:ci .`
 - `docker run --rm deepseek-code:ci version`
+- `gh run watch 25854373712 --repo willamhou/DeepSeekCode --interval 30 --exit-status`
+- `gh release view v0.1.0 --repo willamhou/DeepSeekCode`
+- `git ls-remote https://github.com/willamhou/DeepSeekCode.git HEAD`
+- `docker pull ghcr.io/willamhou/deepseekcode:0.1.0`
+- `docker run --rm ghcr.io/willamhou/deepseekcode:0.1.0 version`
+- `npm view @deepseek-code/cli version` returned `E404`, matching the release
+  workflow log line `NPM_TOKEN is not configured; skipping npm publish.`
 - Local Homebrew formula syntax smoke was not run because `ruby` is not
   installed in this workspace image; the GitHub-hosted release runner still
   performs `ruby -c packaging/homebrew/deepseek.rb`.
+- The `Publish Homebrew Tap` job skipped its tap write because
+  `HOMEBREW_TAP_REPOSITORY` and `HOMEBREW_TAP_TOKEN` were not configured.
 
 ## Remaining Gap
 
-This stabilizes the release gate, but it is not itself public release evidence.
-The next packaging step is to retag `v0.1.0`, let the release workflow publish
-GitHub Release assets and the GHCR image, then re-run `deepseek update
-publish-status --json` against downloaded artifacts. npm and Homebrew still
-require registry/tap credentials before they can match DeepSeek-TUI's public
-install channels.
+DeepSeekCode now has public source, release assets, and a runnable GHCR image.
+npm and Homebrew still require registry/tap credentials before they can match
+DeepSeek-TUI's public install channels. Cargo registry distribution remains
+source-only by policy because `Cargo.toml` has `publish = false`.