docs: publish Farrow 0.3.0

Author: Vonng

content/blog/release/farrow-0.2.0.md

@@ -3,13 +3,13 @@ title: "Farrow 0.2.0: selected convergence and release integrity"
 linkTitle: Farrow 0.2.0
 description: VPN-aware network preflight, truly selected scale-out, committed-state integrations, signed multi-platform artifacts, and the 0.1.0 upgrade boundary.
 date: 2026-09-01
-weight: 1
+weight: 2
 categories: [Release]
 tags: [Farrow 0.2.0, QEMU, macOS, Linux, Release, Supply Chain]
 icon: fa-solid fa-rocket
 ---
 
-Farrow 0.2.0 is the current public pre-1.0 release. It keeps the Pigsty
+Farrow 0.2.0 was the public pre-1.0 release superseded by 0.3.0. It keeps the Pigsty
 inventory and on-disk deployment format introduced by 0.1.0 while fixing the
 network and selected-convergence boundaries found during the final native
 replay.
@@ -65,5 +65,4 @@ farrow doctor
 VMs are live to converge any pre-release process-birth identity. Existing
 guests adopt the new `/etc/hosts` marker when recreated.
 
-Because Farrow is still below 1.0, GitHub labels 0.2.0 as a pre-release even
-though it is the published current release.
+Because Farrow is still below 1.0, GitHub labels 0.2.0 as a pre-release.

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

@@ -3,13 +3,13 @@ title: "Farrow 0.2.0：选点收敛与发布完整性"
 linkTitle: Farrow 0.2.0
 description: VPN 感知网络预检、真正的选点扩容、基于 committed state 的集成、CI 多平台构件与 0.1.0 升级边界。
 date: 2026-09-01
-weight: 1
+weight: 2
 categories: [发布]
 tags: [Farrow 0.2.0, QEMU, macOS, Linux, 发布, 供应链]
 icon: fa-solid fa-rocket
 ---
 
-Farrow 0.2.0 是当前公开的 pre-1.0 发布。它保留 0.1.0 引入的 Pigsty Inventory 与
+Farrow 0.2.0 是被 0.3.0 取代的公开 pre-1.0 发布。它保留 0.1.0 引入的 Pigsty Inventory 与
 磁盘 Deployment 格式，同时修复最终真机重放中发现的网络与选点收敛边界。
 
 ## 主要变化
@@ -56,5 +56,4 @@ farrow doctor
 0.1.0 Deployment State 可直接读取。保留 VM 在线时运行一次 `farrow status`，可收敛
 任何发布前进程出生身份；现有 Guest 在重建时采用新的 `/etc/hosts` 标记。
 
-Farrow 尚未达到 1.0，因此 GitHub 会把 0.2.0 标为 Pre-release；它仍是已经公开发布的
-当前版本。
+Farrow 尚未达到 1.0，因此 GitHub 会把 0.2.0 标为 Pre-release。

content/blog/release/farrow-0.3.0.md

@@ -0,0 +1,62 @@
+---
+title: "Farrow 0.3.0: explicit catalogs and actionable readiness"
+linkTitle: Farrow 0.3.0
+description: Explicit image-catalog updates, per-node bootstrap diagnostics, native guest interface names, and a smaller CLI.
+date: 2026-09-02
+weight: 1
+categories: [Release]
+tags: [Farrow 0.3.0, QEMU, Catalog, Readiness, Release]
+icon: fa-solid fa-rocket
+---
+
+Farrow 0.3.0 is the current public pre-1.0 release. It removes implicit
+Catalog refreshes, turns guest bootstrap failures into actionable per-node
+results, and simplifies the CLI without changing the Pigsty Inventory or
+fixed-IP deployment model.
+
+## What changed
+
+- `up`, `plan`, and ordinary `image` commands use one active local Catalog
+  snapshot and never fetch Catalog metadata implicitly. `farrow update`
+  explicitly fetches the configured repository; `image sync` activates an
+  exact URL or file.
+- Guest bootstrap writes an atomic failure stage. Partial operations report
+  every failed node, stage, and error, and readiness failures point directly to
+  `farrow logs <node>`.
+- Already-running guests can be rechecked without restarting QEMU. A partial
+  lifecycle still rebuilds the SSH client configuration from every committed
+  node.
+- Netplan matches deterministic MAC addresses without renaming interfaces.
+  `vm_disks[].fs: auto` prefers XFS and falls back to ext4 when necessary.
+- The redundant `ss` command and ambiguous root/flag shorthands are removed.
+  `image reset` replaces `reset-manifest`, which remains an alias.
+
+## Verification boundary
+
+Source commit `da6d02426da93c677c94c67fec4eb4fcecf4766a` passed the complete local
+source gate and a full GoReleaser snapshot: unit and race tests, vet,
+Staticcheck, `govulncheck`, four target builds, image-pipeline and installer
+boundaries, archive/package parity, dependency licenses, SBOMs, and native
+Linux package verification. The tag workflow repeated those checks before the
+Release was made public.
+
+This release does not claim a new native VM replay. The dated macOS arm64/HVF
+and Ubuntu amd64/KVM evidence remains listed on the [Status](../../docs/about/status/)
+page; source, package, release, and native-host evidence remain separate gates.
+
+## Install or upgrade
+
+Download the installer and assets from the
+[Farrow 0.3.0 GitHub Release](https://github.com/pgsty/farrow/releases/tag/v0.3.0):
+
+```bash
+curl -fLO https://github.com/pgsty/farrow/releases/download/v0.3.0/install.sh
+chmod +x install.sh
+FARROW_VERSION=0.3.0 ./install.sh
+farrow version
+farrow doctor
+```
+
+Homebrew formula and amd64/arm64 DEB/RPM packages are attached to the same
+pre-release. Existing 0.1/0.2 deployment and Catalog state remains readable;
+Catalog refresh is now always explicit.

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

@@ -0,0 +1,53 @@
+---
+title: "Farrow 0.3.0：显式 Catalog 与可操作的就绪诊断"
+linkTitle: Farrow 0.3.0
+description: 显式镜像 Catalog 更新、逐节点 Bootstrap 诊断、发行版原生 Guest 网卡名与更小的 CLI。
+date: 2026-09-02
+weight: 1
+categories: [发布]
+tags: [Farrow 0.3.0, QEMU, Catalog, 就绪, 发布]
+icon: fa-solid fa-rocket
+---
+
+Farrow 0.3.0 是当前公开的 pre-1.0 发布。它移除隐式 Catalog 刷新，把 Guest Bootstrap
+失败变成可操作的逐节点结果，并在不改变 Pigsty Inventory 与固定 IP Deployment 模型的
+前提下简化 CLI。
+
+## 变化
+
+- `up`、`plan` 与普通 `image` 命令只使用一份当前本地 Catalog 快照，绝不隐式获取
+  Catalog 元数据。`farrow update` 显式获取配置仓库；`image sync` 激活精确 URL 或文件。
+- Guest Bootstrap 原子写入失败阶段。部分操作报告每个失败节点、阶段与错误；就绪失败
+  会直接指向 `farrow logs <node>`。
+- 已运行 Guest 可在不重启 QEMU 的情况下复查。生命周期部分失败后，SSH 客户端配置仍会
+  根据全部 committed 节点重建。
+- Netplan 按确定性 MAC 匹配且不再重命名接口。`vm_disks[].fs: auto` 优先 XFS，必要时
+  回退到 ext4。
+- 删除冗余 `ss` 命令与含义模糊的根/参数短写；`image reset` 取代
+  `reset-manifest`，旧名称仍是别名。
+
+## 验证边界
+
+源码 Commit `da6d02426da93c677c94c67fec4eb4fcecf4766a` 通过完整本地源码门禁与
+GoReleaser 全量 Snapshot：单测与 Race、Vet、Staticcheck、`govulncheck`、四目标构建、
+镜像流水线与 Installer 边界、Archive/Package 一致性、依赖许可证、SBOM 和 Linux 原生
+Package 校验。Tag 工作流在公开 Release 前重复执行了这些检查。
+
+本发布不声称新增真机 VM Replay。带日期的 macOS arm64/HVF 与 Ubuntu amd64/KVM 证据
+仍列在[状态页](../../docs/about/status/)；源码、打包、发布与真机证据继续作为独立门禁。
+
+## 安装或升级
+
+从 [Farrow 0.3.0 GitHub Release](https://github.com/pgsty/farrow/releases/tag/v0.3.0)
+下载 Installer 与资产：
+
+```bash
+curl -fLO https://github.com/pgsty/farrow/releases/download/v0.3.0/install.sh
+chmod +x install.sh
+FARROW_VERSION=0.3.0 ./install.sh
+farrow version
+farrow doctor
+```
+
+同一 Pre-release 附带 Homebrew Formula 与 amd64/arm64 DEB/RPM 软件包。现有 0.1/0.2
+Deployment 与 Catalog 状态仍可读取；Catalog 刷新从本版本开始始终显式。

content/docs/_index.md

@@ -17,7 +17,7 @@ Choose the shortest path for your task:
 - **[Start](start/)** — boot the first lab with two commands, then operate and troubleshoot it.
 - **[Reference](reference/)** — exact Inventory fields, commands, flags,
   output, and exit codes.
-- **[About](about/)** — simplified design, native validation, limits, and
+- **[About](about/)** — design, native validation, limits, and
   release gates.
 
 New users should follow the [Quick Start](start/tutorial/). The complete normal

content/docs/_index.zh.md

@@ -16,7 +16,7 @@ Farrow 把一份 Pigsty 兼容的 Inventory 启动成固定 IP 的 QEMU 虚拟
 
 - **[开始使用](start/)**：两条命令启动第一个实验环境，再按需管理与排障。
 - **[参考](reference/)**：Inventory 字段、命令、参数、输出与退出码。
-- **[关于](about/)**：简化设计、真机验证、已知限制与发布门禁。
+- **[关于](about/)**：设计、真机验证、已知限制与发布门禁。
 
 新手直接跟随[快速上手](start/tutorial/)即可。正常路径只有两条命令：`farrow setup`
 和 `farrow up`。

content/docs/about/_index.md

@@ -1,7 +1,7 @@
 ---
 title: About Farrow
 linkTitle: About
-description: The simplified product model, implementation boundaries, native evidence, current limits, and release gates.
+description: The product model, implementation boundaries, native evidence, current limits, and release gates.
 weight: 30
 icon: fa-solid fa-circle-info
 cascade:

content/docs/about/_index.zh.md

@@ -1,7 +1,7 @@
 ---
 title: 关于 Farrow
 linkTitle: 关于
-description: 简化后的产品模型、实现边界、真机证据、当前限制与发布门禁。
+description: 产品模型、实现边界、真机证据、当前限制与发布门禁。
 weight: 30
 icon: fa-solid fa-circle-info
 cascade:

content/docs/about/design.md

@@ -1,6 +1,6 @@
 ---
 title: Design
-description: Farrow's simplified one-deployment architecture, networking, state, safety boundaries, and review conclusion.
+description: Farrow's one-deployment architecture, networking, state, and safety boundaries.
 weight: 10
 icon: fa-solid fa-compass-drafting
 aliases: [/docs/concepts/, /docs/concepts/networking/, /docs/concepts/storage/, /docs/concepts/safety/, /docs/architecture/, /docs/architecture/overview/, /docs/architecture/networking/, /docs/architecture/security/]
@@ -48,22 +48,11 @@ activation-safety scan proves existing units cannot claim a real host link.
 
 On Debian, the helper is temporarily and reversibly scoped to a group the
 caller actually belongs to. A real unprivileged QEMU bridge smoke must pass
-before setup accepts the network; failure triggers manifest-bounded rollback.
+before setup accepts the network; failure rolls the install back automatically.
 
 ## Safety boundary
 
 QEMU and all guest artifacts run as the caller. Root is limited to host
 network setup and the optional hosts publisher. Destruction requires matching
 ownership, containment, node identity, QMP/process identity, and an allowlist
 of artifacts. Ambiguity stops the operation.
-
-## Review conclusion
-
-The pivot away from projects and leases is correct for a one-lab product and
-greatly reduces cognitive and state complexity. Native review was still
-essential: the first implementation had cross-layer gaps in control-node
-keys, sudo policy, Debian helper access, NetworkManager verification, runtime
-preflight, result messages, and failed-install cleanup. Those paths were fixed
-and replayed on macOS and Linux before this documentation was simplified. A
-later adversarial review also caught destructive preflight ordering and signed
-Catalog-baseline upgrade bugs before EL7/EL8 compatibility was committed.

content/docs/about/design.zh.md

@@ -1,6 +1,6 @@
 ---
 title: 设计
-description: Farrow 简化后的单 deployment 架构、网络、状态、安全边界与评审结论。
+description: Farrow 的单 deployment 架构、网络、状态与安全边界。
 weight: 10
 icon: fa-solid fa-compass-drafting
 aliases: [/docs/concepts/, /docs/concepts/networking/, /docs/concepts/storage/, /docs/concepts/safety/, /docs/architecture/, /docs/architecture/overview/, /docs/architecture/networking/, /docs/architecture/security/]
@@ -40,17 +40,9 @@ systemd-networkd，并通过发行版 bridge helper 接入。若 networkd 尚未
 Activation-safety 扫描证明现有 Unit 不会接管真实宿主链路后才启动。
 
 Debian helper 会临时、可逆地限制给调用者真实加入的组。setup 必须通过一次非特权
-QEMU bridge smoke；失败后按 manifest 自动回滚。
+QEMU bridge smoke；失败后自动回滚安装。
 
 ## 安全边界
 
 QEMU 与所有 Guest 工件都以调用者身份运行。root 仅用于宿主网络与可选 hosts publisher。
 销毁必须同时匹配属主、路径包含、节点身份、QMP/进程身份与工件白名单；任何歧义都会停止。
-
-## 评审结论
-
-对单实验室产品而言，删除 project 与 lease 的 pivot 是正确的，显著降低了认知与状态
-复杂度。但真机审查仍不可省略：第一版在控制节点密钥、sudo 策略、Debian helper 权限、
-NetworkManager 验证、运行时 preflight、结果消息与失败清理上存在跨层断裂。这些路径已修复，
-并在 macOS 与 Linux 真机重放后才重写本文档。后续对抗审查又在 EL7/EL8 提交前发现并
-修复了破坏前预检顺序与签名 Catalog 基线升级问题。