docs: calibrate 0.7.0 release guidance

Author: Vonng

content/blog/release/farrow-0.7.0.md

@@ -74,10 +74,32 @@ pre-1.0 GitHub pre-release policy; specify `FARROW_VERSION` when installing.
 
 ## Validation
 
-The complete source gate covers unit and race tests, static checks, four-target
-compilation, installer and image-pipeline checks, and licenses. Isolated Ubuntu
-amd64/KVM tests with Ubuntu 24.04 guests exercised disk corruption and resets,
-busy mounts, failed probes, retained-disk recreation, share recovery, and repeated
-healthy `up` calls without process replacement. macOS validation includes CLI
-smoke checks and cross-compilation; this release does not claim a new HVF guest
-replay, host reboot test, or full Pigsty installation.
+The release commit is `9c6d4896d93733d1cb60a7e5d8591e9a06659c9d`. It passed the
+[source CI](https://github.com/pgsty/farrow/actions/runs/35118137961) and the
+independent [packaging snapshot](https://github.com/pgsty/farrow/actions/runs/35118137990)
+before tagging. The [tag workflow](https://github.com/pgsty/farrow/actions/runs/35119206685)
+repeated the gates and produced 20 release assets: 19 checksummed payloads plus
+the checksum manifest. All 20 assets downloaded anonymously with HTTP 200 and
+matched the inspected bytes.
+
+The public macOS arm64 and Linux amd64 installers installed the exact archive
+binaries and reported version `0.7.0` with this commit. On Ubuntu 26.04 amd64
+with KVM/QEMU 10.2.1 and Ubuntu 24.04 guests, the recovery matrix exercised
+ext4/XFS corruption, retained disks, failed probes, busy mounts, read-only share
+fallback, and repeated healthy `up` without replacing the VM process. A public
+0.6.0 bootstrap that failed its management-egress probe was resumed by 0.7.0 in
+3.3 seconds; the existing data disk and UUID survived the probe failure. The old
+0.6.0 binary still completed `status`, `stop`, `start`, and `destroy` after the
+upgrade. A fresh VM from the final 0.7.0 archive started without warnings, and a
+deliberately damaged disposable ext4 disk was reset by the public installer in
+3.2 seconds with an explicit data-loss notice while the VM process stayed in place.
+
+That interrupted 0.6.0 bootstrap may have deleted the staged control-node SSH key
+before installing it. Management SSH recovers, but peer SSH remains an explicit
+`control-ssh` limitation; the key is not reinjected during an in-place retry.
+Recreate the affected control node after reviewing `farrow plan` if peer SSH is
+required. Fresh 0.7.0 guests install the key normally.
+
+macOS validation includes CLI smoke checks and cross-compilation. This release
+does not claim a new HVF guest replay, host reboot test, Linux arm64 run, or full
+Pigsty installation.

content/blog/release/farrow-0.7.0.zh.md

@@ -59,7 +59,21 @@ Formula。沿用 pre-1.0 规则，在 GitHub 标记为 Pre-release，安装时
 
 ## 验证范围
 
-完整源码检查覆盖单元与 race 测试、静态检查、四平台编译、安装器与镜像流水线检查和许可证。
-Ubuntu amd64/KVM 隔离环境实际验证了 Ubuntu 24.04 客机的数据盘损坏重置、忙碌挂载、探测失败、
-持久盘重建、共享目录恢复，以及重复 `up` 保留运行进程。macOS 本轮验证为 CLI 冒烟及编译，
-不宣称新增 HVF 客机重放、宿主重启或完整 Pigsty 安装验收。
+发布提交为 `9c6d4896d93733d1cb60a7e5d8591e9a06659c9d`，通过[源码 CI](https://github.com/pgsty/farrow/actions/runs/35118137961)
+与独立[打包 Snapshot](https://github.com/pgsty/farrow/actions/runs/35118137990)后打 Tag。
+[Tag 工作流](https://github.com/pgsty/farrow/actions/runs/35119206685)重复门禁并生成 20 个发布资产：
+19 个带校验和的载荷及校验清单。检查后，20 个资产均可匿名 HTTP 200 下载，并与检查过的字节一致。
+
+公开 macOS arm64 与 Linux amd64 安装器安装的二进制均与归档一致，并报告版本 `0.7.0` 与上述提交。
+Ubuntu 26.04 amd64、KVM/QEMU 10.2.1、Ubuntu 24.04 Guest 隔离环境实际验证了 ext4/XFS 损坏、持久盘、
+探测失败、忙碌挂载、只读共享降级和重复健康 `up` 保留 VM 进程。公开版 0.6.0 因管理出网探测失败而中断，
+0.7.0 在 3.3 秒内接续，探测失败期间已有数据盘和 UUID 保持不变。升级后 0.6.0 二进制仍能执行
+`status`、`stop`、`start` 与 `destroy`。最终 0.7.0 归档新建的 VM 无警告启动；公开安装器还在 3.2 秒内
+重置了人为损坏的可丢弃 ext4 数据盘，明确提示数据丢失，同时保留 VM 进程。
+
+特定的 0.6.0 中断现场可能在安装前删除暂存的控制节点 SSH 私钥。此升级路径中管理 SSH 会恢复，
+但节点间 SSH 会明确显示 `control-ssh` 限制，原位重试不会重新注入私钥；需要节点间 SSH 时，先查看
+`farrow plan` 再重建受影响的控制节点。全新 0.7.0 Guest 会正常安装该密钥。
+
+本版本 macOS 验证包括 CLI 冒烟与交叉编译；不宣称新增 HVF Guest 重放、宿主重启、Linux arm64 或完整
+Pigsty 安装验收。

content/docs/about/status.md

@@ -40,7 +40,9 @@ Ubuntu amd64/KVM lab; macOS HVF and other results retain their original dates.
 - EL7 through the current native Linux/amd64 lifecycle;
 - current macOS 9p share replay;
 - a complete current Pigsty `configure → farrow up → install.yml` run;
-- clean-host published Homebrew/DEB/RPM consumption.
+- clean-host published Homebrew installation (the current tap formula has a local
+  upgrade and `brew test` pass, but this is not a clean-host replay);
+- clean-host published DEB/RPM consumption.
 
 Current built-in versions are `supported`, except EOL EL7 and the retained
 compatibility versions EL9 9.3/9.6 and EL10 10.0, which are `deprecated`.
@@ -64,6 +66,8 @@ release was made public; all 20 anonymous downloads returned HTTP 200 and matche
 the inspected bytes, including all 19 checksummed payloads. Public installers on
 macOS arm64 and Ubuntu amd64 installed the exact archive binaries. Download tests
 used the host's configured proxy; m3 reached it through a temporary loopback tunnel.
+The `pgsty/infra/farrow` formula was refreshed to `v0.7.0`; a local Homebrew
+upgrade and `brew test` passed, while a clean-host formula install remains open.
 
 The Ubuntu amd64/KVM recovery matrix covered corrupt ext4/XFS filesystems,
 retained disks, failed probes, busy mounts, read-only shares, and repeated healthy

content/docs/about/status.zh.md

@@ -37,7 +37,9 @@ Farrow 仍是 pre-1.0。源码测试、带日期的真机重放、软件包、
 - 当前 Linux/amd64 原生 EL7 生命周期；
 - 当前 macOS 9p share 重放；
 - 完整的 Pigsty `configure → farrow up → install.yml`；
-- 干净宿主上的公开 Homebrew/DEB/RPM 安装。
+- 干净宿主上的公开 Homebrew 安装（当前 Tap Formula 已本地升级并通过 `brew test`，但这不等于
+  干净宿主重放）；
+- 干净宿主上的公开 DEB/RPM 安装。
 
 当前内置版本均为 `supported`，只有 EOL EL7 与保留兼容版本 EL9 9.3/9.6、EL10 10.0
 为 `deprecated`。active/standby Catalog 公钥已经内置，但镜像仓库仍需迁离开发宿主，
@@ -56,6 +58,8 @@ Farrow 仍是 pre-1.0。源码测试、带日期的真机重放、软件包、
 20 个资产的草稿，检查后公开发布。20 个匿名下载均返回 HTTP 200，字节与检查过的草稿
 一致，19 项载荷全部通过摘要校验。macOS arm64 与 Ubuntu amd64 的公开安装器安装结果
 均与发布归档中的二进制一致。下载验证使用宿主现有代理，m3 通过临时回环隧道访问该代理。
+`pgsty/infra/farrow` Formula 已刷新到 `v0.7.0`，本机 Homebrew 升级与 `brew test` 通过；
+干净宿主 Formula 安装仍待重放。
 
 Ubuntu amd64/KVM 故障矩阵覆盖 ext4/XFS 损坏、持久盘、探测失败、忙碌挂载、只读共享
 和重复健康 `up` 保留进程。公开版 0.6.0 因出网探测失败而中断，0.7.0 在 3.3 秒内接续

content/docs/start/_index.md

@@ -1,20 +1,25 @@
 ---
 title: Start
 linkTitle: Start
-description: Start Farrow with two commands; read operations, troubleshooting, images, builds, and cleanup only when needed.
+description: Start Farrow with up, connect with ssh, and read the other guides only when needed.
 weight: 10
 icon: fa-solid fa-rocket
 cascade:
   type: docs
 ---
 
-With Farrow installed, new users only need the [Quick Start](tutorial/):
+With Farrow installed, new users can start a test lab with the [Quick Start](tutorial/):
 
 ```bash
-farrow setup
 farrow up
+farrow ssh
 ```
 
+Interactive `up` creates the default inventory and offers to prepare missing host
+dependencies. Repeat `farrow up` to retry unfinished guest setup without
+restarting healthy VMs. For unattended setup, run `farrow setup --yes` before
+`farrow up`.
+
 Package availability is recorded on [Status](../about/status/); developers and
 source reviewers can use [Build from Source](source-build/).
 

content/docs/start/_index.zh.md

@@ -1,20 +1,24 @@
 ---
 title: 开始使用
 linkTitle: 开始使用
-description: 两条命令启动 Farrow；其余管理、排障、镜像、构建与清理按需阅读。
+description: 用 up 启动 Farrow、用 ssh 进入客机，其余管理、排障、镜像、构建与清理按需阅读。
 weight: 10
 icon: fa-solid fa-rocket
 cascade:
   type: docs
 ---
 
-安装 Farrow 后，新用户只需阅读[快速上手](tutorial/)：
+安装 Farrow 后，新用户只需按[快速上手](tutorial/)启动测试环境：
 
 ```bash
-farrow setup
 farrow up
+farrow ssh
 ```
 
+交互式 `up` 会创建默认配置，并在缺少宿主依赖时提供准备选项。重复执行
+`farrow up` 可重试未完成的客机初始化，不会重启已经健康运行的 VM。无人值守时，
+先执行 `farrow setup --yes`，再执行 `farrow up`。
+
 公开软件包状态见[当前状态](../about/status/)；开发者与源码审查者可使用
 [从源码构建](source-build/)。